[Wires]

I coded a couple or ECU's, and all went fine, everything is working fine, but now I get a "red car on lift" that pops up every couple seconds of driving.

There is no service due, and "check control" isn't showing anything but the car on the lift.

I coded the CAS, NFRM, 2JBBF, KOMBO and FZD. All worked fine without errors, and then the dash popped up with the error.

Can INPA tell me what is causing the error?

[Peertwelve]

Originally Posted by Wires

I coded a couple or ECU's, and all went fine, everything is working fine, but now I get a "red car on lift" that pops up every couple seconds of driving.

There is no service due, and "check control" isn't showing anything but the car on the lift.

I coded the CAS, NFRM, 2JBBF, KOMBO and FZD. All worked fine without errors, and then the dash popped up with the error.

Can INPA tell me what is causing the error?

Does your tachometer work? It sounds like you used an old version of EDIABAS. Has this car's software been updated by the dealer lately? Here is a good way to read errors with INPA. good luck! http://www.e90post.com/forums/showpo...postcount=2560

[Wires]

I just checked, and no, no tach no fuel gauge.

I'm thinking I used 6.4.3 instead of 6.4.7. Crap.... The last update was for thye HPFP last year.

The INPA link works, according to the car, it's a KOMBI error. Is there a way to reload the defaults back in with the newer version?

[Wires]

Ok, figured it out. On the BMW coding site, similar issue with another guy.

Turns out my daten's were out of date. Updated to v46.2, and problem fixed. Phew... just need new underwear!

Always good to mess it up just out of warranty!

[Peertwelve]

Yeah updating dates fixes the issue by updating the files that ediabas uses. Guess how I learned about this....

[Wires]

I don't mind learning by doing, but breaking something that was fine, and then thinking this might end up being a "dealer bent over table moment" wasn't making me feel very good!

Thanks for the general poke in the right direction, much appreciated.

[patrickkc]

This happened to me before as well when I coded my friend's brand new car. Shat bricks that night when his tachometer suddenly stopped working after I coded it.

easy fix though, but was a terrifying experience for sure.

[rentonrider]

Just curious, what version daten were you using before?

[patrickkc]

Was using V39. Upgraded to V46 and everything works well

[Wires]

I don't know what I was using (whatever comes with the RAR off the web for the full software package). The update to v46 fixed it for me as well.

One FYI, I had to upgrade to BMW Standard Tools v2.1 to read the NFRM after the v46 daten's though.

I did also notice that it's a good idea to follow the INPA link above to check if you have any module errors. When I first did it (after butchering a bunch of modules with the old datens), there were a lot of modules with errors (all I touched for sure). So I updated with the new datens, but I couldn't do the NFRM due to the older software. Even though there was no indication on the dash, NFRM had 2 errors.

I updated the datens, cleared the errors, and all is fine now.

I'd recommend checking the modules for errors after the coding as a santity check. If the module gives an error, then something you loaded was wrong.

[Elliott@DetailAddict]

This issue is a sticky already.

[Wires]

Sorry, must have missed that when I was filling my underwear as the dash lit up like a Christmas tree, and the warranty ended 2 weeks ago....