[jroberts86]

Thank you Obeisance.

Of the threads I reviewed, I think one noted a 2006 car, but that half of them are Canadian, half US. That might be part of my problem.

I have done as you suggested with these results:
09 02 [before your instruction set]: SCCPC11107HA30000
09 02 [after your instruction set: SCCPC11107HA30056

So it did something! And, the Cal ID and CVN fields are now populated and here is the diagnostic log as best I could get it:
[forgive my poor IOS image capture and downsizing skills. It is a borrowed phone for OBD only...]

I think you are a guinea pig.. i don't know if I've heard of anyone trying this on a MY06 or MY07 car. I know that this strategy works for the MY05, and doesn't work for the MY08+ (those use CAN OBD). It should probably work for the 06/07, but we won't know until someone tries.

Can you share what the 0902 command returns, as well as the commands that you sent? If not, i prepared a sequence below that should let me see what i am curious about. I wonder if the vin mask is the same as on the '05 cars.

The below commands should be all that are needed as a test case. I substituted the ASCII number sequence 0 1 2 3 4 5 6 7 8 9 so that i can see where the car puts the characters that are sent in the commands.

AT SP 3
3B00
3B013031323334
3B023536373839
03
04
0902

Those are:
Set protocol to iso-9141-2
Ask which pids are supported by obd mode 0x3B
Set vin, 1st message
Set vin, 2nd message
Read stored diagnostic trouble codes
Clear stored diagnostic trouble codes
Read vin from ecu

 

[Catsailr27]

Thank you Obeisance.

Of the threads I reviewed, I think one noted a 2006 car, but that half of them are Canadian, half US. That might be part of my problem.

I have done as you suggested with these results:
09 02 [before your instruction set]: SCCPC11107HA30000
09 02 [after your instruction set: SCCPC11107HA30056

So it did something! And, the Cal ID and CVN fields are now populated and here is the diagnostic log as best I could get it:
[forgive my poor IOS image capture and downsizing skills. It is a borrowed phone for OBD only...]
View attachment 1297660
View attachment 1297661

View attachment 1297659
View attachment 1297658

Thanks for reporting back! Good to know it works on other than '05

 

[jroberts86]

Thanks for reporting back! Good to know it works on other than '05

Well, happy to report back. But it isn't fixed yet! I still can't set the VIN correctly. If I get that fixed mayed the car will run great again! (It ran great until this)

 

[Catsailr27]

Ah sorry when I saw "it did something fields are populated" I assumed the VIN had been taken properly.

 

[Obeisance]

It looks like the two obd command messages should work for you if you keep trying.

The second one responded with an affirmative and the last two vin digits changed as they should.

The first command message looked malformed; i believe you sent
3B 01 30 31 23 33 4
That last byte was missing a nibble of data, so i don't know what the serial terminal does.

I recommend trying over to send the commands for your vin until you get the affirmative response (7B01 or 7B02). Sometimes the ecu didn't seem to get the commands that i was sending when I've practiced this, so i can only recommend tenacity.

 

[jroberts86]

awesome. manana! I have a winery to run in the middle of crush!

It looks like the two obd command messages should work for you if you keep trying.

The second one responded with an affirmative and the last two vin digits changed as they should.

The first command message looked malformed; i believe you sent
3B 01 30 31 23 33 4
That last byte was missing a nibble of data, so i don't know what the serial terminal does.

I recommend trying over to send the commands for your vin until you get the affirmative response (7B01 or 7B02). Sometimes the ecu didn't seem to get the commands that i was sending when I've practiced this, so i can only recommend tenacity.

 

[Obeisance]

I suppose i should point out that this route won't change the year '7' digit. I'm order to change that, one would need to either reprogram the ecu entirely, or one would need to use a CAN tool to manually write to RAM. I can only give help on this route for the 2005 cars, since that's all I've seen code for.

Maybe @alcantor could help for the t4e ecu cars.

 

[jroberts86]

Curious as to how it got changed to 2007? I have a lot to learn about all this. Ready to put in the sport tune ecu and send the OEM ECU away...

I suppose i should point out that this route won't change the year '7' digit. I'm order to change that, one would need to either reprogram the ecu entirely, or one would need to use a CAN tool to manually write to RAM. I can only give help on this route for the 2005 cars, since that's all I've seen code for.

Maybe @alcantor could help for the t4e ecu cars.

 

[alcantor]

Double post... sorry...

 

[alcantor]

But when I enter the vin, I get no acknowledgement the write line was received or accepted. After many attempts I was able to get the VIN 09 02, and now that shows an incorrect/incomplete VIN. But, model year 2007.

Hum, I never try it myself.... But I can if you didn't get it to work...

The first command message looked malformed; i believe you sent
3B 01 30 31 23 33 4
That last byte was missing a nibble of data, so i don't know what the serial terminal does.

I didn't see it at first, but that's the error.

 

[Obeisance]

If someone wanted to use the 'arbitrary address write' CAN message on a t4e, do you think you could find the address needed to overwrite the vin?

 

[alcantor]

If someone wanted to use the 'arbitrary address write' CAN message on a t4e, do you think you could find the address needed to overwrite the vin?

To change the year digit, on 06-07 ECU? 0x2F81E1

The OBD mode 3B is writting to 0x2F81E0, 0x2F81E3-0x2F81E8

 

[jroberts86]

Thanks to all of you. Tenacity, yes, that is certainly required.

Yes, I had an error in the test string. Correcting that I was able through trial and error to get the last 5 of the VIN correct, and the HL.

I used 3B 01 48 4C 33 31 33
and
3B 02 31 37 FF FF FF
to get VIN SCCPC111H7HL31317

So I still need ideas on how to change the H7 to 06.

I ran out of battery and will try more tomorrow.
I'll note that clearing the codes gives an accepted response, but then the codes are back. The only device set that I can get to write is the KIWI BT and IOS.

And by way of more explanation on how I got here. I have had the car for 11 years and no engine mods. But lots of suspension and track upgrades! Always passed smog. The battery would run down from time to time but a C-Tek recondition or charge made it ok. This last time, when I charged the battery and took the car out, it started running rough and threw the CEL. And here we are.

Again, thanks for your patience and assistance.

Jeff

 

[alcantor]

So I still need ideas on how to change the H7 to 06.

I think you have a F121E10H Software revision. Since revision D (the first letter, you have F), it seems that Lotus has put a trick to address this specific problem. You should try something like this, to change from 07 to 06 and then put your VIN:

AT SP 3
3B 01 01 48 4C 36 30
3B 02 30 30 FF FF FF
0902

Bulletin TSB 2007-07 06MY Reflash:

 

[jroberts86]

Update. First thanks to you kind folks for good suggestions. I will say this was challenging.

I now have all of the VIN correct except an "H" in front of the year as in "H6" not "06". but, the car now seems to run ok and the CEL is cleared. I will take it out for a test drive today to verify. I wonder if it will pass smog as is...

The service bulletin was a key piece and I finally got the 6000 last four entered (but could not see it because it did report an error). Then, I sent multiple commands to get to where I am now. An odd thing was that sometimes they would be received, sometimes not. Trying the exact same thing did work, but each time I had to reboot the software app and connect with the correct protocols. Also, it seemed to matter if I put a space between the command 'elements' as sometimes
3B01484C333133
would work, other times
3B 01 48 4C 33 31 33 was good.

new battery, full tank, no CEL, wine grapes harvested and fermenting. All systems go.

JB

 

[alcantor]

An odd thing was that sometimes they would be received, sometimes not. Trying the exact same thing did work, but each time I had to reboot the software app and connect with the correct protocols.

It seems really annoying... For the next time, I highly recommend to use a Laptop with a Bluetooth connection. Once your ELM327 is connected to your laptop (per Bluetooth), it will appears as a COM port, then use a Windows serial terminal application. A full size keyboard is much more convenient to type all those numbers and copy-paste much more easier.

 

[jroberts86]

It seems really annoying... For the next time, I highly recommend to use a Laptop with a Bluetooth connection. Once your ELM327 is connected to your laptop (per Bluetooth), it will appears as a COM port, then use a Windows serial terminal application. A full size keyboard is much more convenient to type all those numbers and copy-paste much more easier.

Thanks, I guess I can try the laptop again but I could not get the ELM to write, only read. I gave up on it quickly, focusing on what seemed to work. Luckily my friend lent me his IOS burner phone and kiwi BT.

 

[jroberts86]

Additional quick update.

Took the car out, it ran fine, just like normal. No CEL, all good as long as I pass smog. What a fun car.

Cheers all

 

[DaveM]

Like others, I’m getting a good response to the AT commands, but not the 3B, or any other command mentioned here, like 0902. Have tried SP 3 and 4, and all versions of the 3B spaces, no spaces, and quotes. Any other ideas?

Using Bluetooth Veepeak and Android ELM BT terminal on an 05 federal Elise.

 

[Obeisance]

That sounds like your phone to obd communication works, but not the obd tool to car communication. I've experienced that from time to time with my vag com cable too, and wasn't sure if it was the fault of my software or of the ecu. Sometimes i go so far as to power cycle the obd device (disconnect from laptop and car.. since you aren't using a laptop you don't need to worry about that connection) as well as the ecu- i toggle my battery disconnect switch to fully remove power from the ecu for a bit. After that things worked again. I think my whole procedure reeks of superstition, though.