[05Lotusguy]

AT SP 3 did the trick for me, also I needed to still clear the code out with my reader, but is does not appear to be coming back. FYI the check engine light would not go way until I manually cleared the code.

 

[Obeisance]

7B 01 is the affirmative response from the ECU (the full message is [48 6B 10 7B 01 sum], but the elm device doesn't show it all to you). that should result in a different vin being programmed (except for the last two characters- those come from the mode 3B, pid 02 3B02xxxx... command). the car evaluates the mil condition upon ecu boot cycles. so, you'll need to key-off for a bit (don't pull battery power, the ecu needs time to save the parameters and shut down). I'm not sure how long to wait, but after some time, key on again and then read the vin with the mode 9 pid 02 query.

if for some reason the vin changed from the default 'sccpc11105ha30000', but the cel persists, you can try sending a mode 03/04 command set to read and clear the cel.

 

[kwinklesOFFICIAL]

I was lazy and just reused the supplied hex version of the VIN. I tried a couple different combinations of inputting the values. I may trigger the code again so I can verify the EXACT commands that did the trick.

Steps:

1. Purchase (iOS version. There is also an Android Version) https://www.amazon.com/gp/product/B078K54MT5/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1
2. Install https://apps.apple.com/us/app/elm327-wifi-terminal-obd/id1041700672
3. Follow instructions above

It should me a couple tries to get the correct commands but it 100% let me clear the check engine code. Highly recommend trying this out and investing in the Bluetooth ODBII reader

First let me say this thread has been really helpful, saved me a drive up to the dealer to get my inspection done for this year.

I’d really recommend using your own VIN, as a different one might lead to some problems. For example, in Texas the inspection system is pretty automated. They inspection report gets uploaded to a state database and you need a valid inspection in that database to register your car. Having the wrong VIN might lead to that upload breaking and mean you have to go register the car in person with the inspection report in hand. That’s a pain.

Also, it seems like automated systems might report ODB milage numbers, etc, to the carfax of the VIN used in the example. That could get flagged as odometer rollback, or even multiple odometer rollbacks in multiple states, and that be a huge headache for whatever poor bastard has the car with that VIN in the OP of this if it exists.

That just seems cruel 😂.

Also, getting it right is pretty easy. Here is the exact sequence I used to set my vin to L-12345:

ASCI numbers in hexadecimal are really simple, you don’t even need a tool or a lookup table, just put a 3 before the number you want to write in hex.

1, 2, 3 ... 9, 0
becomes
31, 32, 33 ... 39, 30

And the L becomes 4C, which most cars will have. All those extra 30 values in the commands are zero padding to put the other digits in the right order. Swap out 12345 in that screenshot with the last five digits of your actual VIN in the commands in that log and you’re done.

Also, in that photo above the command 09 02 prints out the VIN, so you can see L-12345 showing up in the new VIN there in the log. You can pretty easily confirm that the new VIN has been written with that command before you taje out the key and reset the trouble code.

One more tip is that the free app for iOS doesn’t have a great interface, the keyboard and log are not designed very well and you can’t always see what you are typing before you hit send.

That screenshot is from this app, which is $2.99, but has a much better interface, and has a bunch of built in commands: ‎OBD Terminal for ELM327

 

[ZakkAttack86]

First let me say this thread has been really helpful, saved me a drive up to the dealer to get my inspection done for this year.

I’d really recommend using your own VIN, as a different one might lead to some problems. For example, in Texas the inspection system is pretty automated. They inspection report gets uploaded to a state database and you need a valid inspection in that database to register your car. Having the wrong VIN might lead to that upload breaking and mean you have to go register the car in person with the inspection report in hand. That’s a pain.

Also, it seems like automated systems might report ODB milage numbers, etc, to the carfax of the VIN used in the example. That could get flagged as odometer rollback, or even multiple odometer rollbacks in multiple states, and that be a huge headache for whatever poor bastard has the car with that VIN in the OP of this if it exists.

That just seems cruel 😂.

Also, getting it right is pretty easy. Here is the exact sequence I used to set my vin to L-12345:

View attachment 1276275

ASCI numbers in hexadecimal are really simple, you don’t even need a tool or a lookup table, just put a 3 before the number you want to write in hex.

1, 2, 3 ... 9, 0
becomes
31, 32, 33 ... 39, 30

And the L becomes 4C, which most cars will have. All those extra 30 values in the commands are zero padding to put the other digits in the right order. Swap out 12345 in that screenshot with the last five digits of your actual VIN in the commands in that log and you’re done.

Also, in that photo above the command 09 02 prints out the VIN, so you can see L-12345 showing up in the new VIN there in the log. You can pretty easily confirm that the new VIN has been written with that command before you taje out the key and reset the trouble code.

One more tip is that the free app for iOS doesn’t have a great interface, the keyboard and log are not designed very well and you can’t always see what you are typing before you hit send.

That screenshot is from this app, which is $2.99, but has a much better interface, and has a bunch of built in commands: ‎OBD Terminal for ELM327

Thank you so much! Your instructions were by far the easiest to follow. I did it with my Elise and it worked. I just have one question...

When you said swap out the 12345, were you talking about these numbers? If so, I did it right. If not, I guess I'll need to fix it :\

 

[kwinklesOFFICIAL]

Thank you so much! Your instructions were by far the easiest to follow. I did it with my Elise and it worked. I just have one question...

When you said swap out the 12345, were you talking about these numbers? If so, I did it right. If not, I guess I'll need to fix it :\

View attachment 1277813

Yep if you have a US car, I think that’s all you need to do.

 

[ZakkAttack86]

Yep if you have a US car, I think that’s all you need to do.

Yep, it's a Federal 111. Cool deal, thanks!

 

[CarGuyKevin]

Trying to get the vin programmed in one of my cars and was hoping for some help. From the app I can't get anything to connect with the vehicle. Do you have to input of the commands just to establish a link with the vehicle? It just pops up a message that says something like "device not found". I have another app just for code reading and the elm device works fine with that. Hopefully this makes sense. Here is a screen shot of what I see when I try to connect with the Lotus.

 

[ZakkAttack86]

Trying to get the vin programmed in one of my cars and was hoping for some help. From the app I can't get anything to connect with the vehicle. Do you have to input of the commands just to establish a link with the vehicle? It just pops up a message that says something like "device not found". I have another app just for code reading and the elm device works fine with that. Hopefully this makes sense. Here is a screen shot of what I see when I try to connect with the Lotus.
View attachment 1292543

Kevin, I can give you a play by play. Hit me up through FB Messenger. "Zakk Farkas", should only be one. I've got all the info saved on my phone to include screenshots. I'm only going to tell you what worked for me and many others, you don't have to trust me. With that, you'll need to purchase two apps. OBD Terminal and OBD Fusion. I'll send you all the info if you hit me up.

 

[kfennell]

Hopefully there's some action on this thread still. Trying to do this on an 05 elise and get the following

 

[kfennell]

Oops saw 2nd page... I'll try sp 3 when I have enough battery

 

[kfennell]

Perfect, now how do I reprogram the SRS unit after the airbags went off?

 

[ScottN]

I have the dreaded "lost VIN" problem. I have:

BAFX Products 34t5 Bluetooth OBDII Scan Tool
ElmBasic for Android
Tourque Pro

I can pair and get to the ECU. But I can't get the ElmBasic connection to entering the codes. What am I missing? Thanks

 

[kfennell]

I have the dreaded "lost VIN" problem. I have:

BAFX Products 34t5 Bluetooth OBDII Scan Tool
ElmBasic for Android
Tourque Pro

I can pair and get to the ECU. But I can't get the ElmBasic connection to entering the codes. What am I missing? Thanks

Did you read the wntire thread? the first post isnt really right, the better directions are later on.

 

[ScottN]

I took a shot using the example above. After a few restarts, I got to the end >09 02 , I ran out of instructions. Do I hit enter again, wait..... I use Torque Pro should I then clear the codes (ignition with off the engine/off). Since this is not my car it's a pain to run back and forth with questions. Thanks

 

[Obeisance]

If the '0902' returns the ascii for the VIN that you changed to, you shouldn't have to do anything other than power cycle the ecu in order to get the code to clear. That being said, clearing the cel with mode 04 wouldn't hurt, in case you want to be certain that the mil is off

 

[ScottN]

If the '0902' returns the ascii for the VIN that you changed to, you shouldn't have to do anything other than power cycle the ecu in order to get the code to clear. That being said, clearing the cel with mode 03 wouldn't hurt, in case you want to be certain that the mil is off

Just to make sure the sequence after I have after the successful download:
Switch over to Torque
Clear the codes including CEL
Shut off the ignition
Start the engine and make sure there are now codes
Sound right? Thanks again

 

[Obeisance]

That sounds mostly correct. I do not think you need to start the engine, though.

I have also observed that a short ignition on-off-on cycle may not be sufficient to restart the ecu.. depending on what the ecu is doing it may take a few minutes for it to shut down and save the newly programmed vin from ram to rom/flash.

I mean, if it hasn't fully gone through its shutdown it'll keep using the value in ram and from the outside diagnostic tool's perspective everything will look complete. The issue isn't fully resolved until the ecu saves the vin to flash. So when you're finished, make sure not to disconnect the battery for a while so that the ecu has a chance to fully save data. I keep harping on this point because i have a battery cut off switch and I'm too aggressive at disconnecting power.

 

[ScottN]

Thanks, finally got the VIN to stick....

 

[jroberts86]

I am having the same issue on my 2006 Elise. I have read this thread and the others, no success so far. If someone has ideas, that is awesome!

I have tried an Innova OBDII, BT (Kiwi) IOS, and BT Android (ELM). With the IOS I can get to

AT SP 0

OK

AT SP 4 (and tried 3)

OK

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.

What to try next? I have another ECU with the Sport tune, I will try that. But, to pass smog I assume I need the stock ECU with correct VIN.

Again, ideas much appreciated.

Thanks

 

[Obeisance]

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