[VTENGR]

It even wiped my VO coding for anti-dazzle. Just an FYI for any others out there.

[LexxM3]

Originally Posted by VTENGR

It even wiped my VO coding for anti-dazzle. Just an FYI for any others out there.

Interesting. After the update, does your FA now have 5AP back in?

[VTENGR]

Originally Posted by LexxM3

Interesting. After the update, does your FA now have 5AP back in?

Yep.

[LexxM3]

Originally Posted by VTENGR

Yep.

Ok, then at least it makes sense. OTA update includes FA restore per your VIN. That actually seems prudent for a hands-off update, even if annoying for coders. Good to know.

[RayoVac]

Heck I would be just fine with having to re-code everything if it means OTA actually takes place and works.

[VTENGR]

Originally Posted by LexxM3

Ok, then at least it makes sense. OTA update includes FA restore per your VIN. That actually seems prudent for a hands-off update, even if annoying for coders. Good to know.

In doing a bit more research into this, I'm not sure if the OTA wiped my AntiDazzle. It definitely wiped all the FDL codes I did via bimmercode.

When I VO coded my anti-dazzle, I followed Token Masters steps, which doesn't involve writing the the new FA to the car. You just remove 5AP and code the necessary ECUs. If I'm not mistaken, when you VO code this way, the next time you read the FA, it will show the 5AP on the list.

However, if the OTA update "CODES" all the ecus, then it will revert the ECU back to the FA with the 5AP - so that may be an advantage to writing the FA back to the car after you edit out the 5AP.

I'm too novice to know which is the best way to go moving forward.

[LexxM3]

Originally Posted by VTENGR

In doing a bit more research into this, I'm not sure if the OTA wiped my AntiDazzle. It definitely wiped all the FDL codes I did via bimmercode.

When I VO coded my anti-dazzle, I followed Token Masters steps, which doesn't involve writing the the new FA to the car. You just remove 5AP and code the necessary ECUs. If I'm not mistaken, when you VO code this way, the next time you read the FA, it will show the 5AP on the list.

However, if the OTA update "CODES" all the ecus, then it will revert the ECU back to the FA with the 5AP - so that may be an advantage to writing the FA back to the car after you edit out the 5AP.

I'm too novice to know which is the best way to go moving forward.

Oh, that's a great point. I am going to double check a few things on my car and report back further.

[ifr]

Originally Posted by VTENGR

In doing a bit more research into this, I'm not sure if the OTA wiped my AntiDazzle. It definitely wiped all the FDL codes I did via bimmercode.

When I VO coded my anti-dazzle, I followed Token Masters steps, which doesn't involve writing the the new FA to the car. You just remove 5AP and code the necessary ECUs. If I'm not mistaken, when you VO code this way, the next time you read the FA, it will show the 5AP on the list.

However, if the OTA update "CODES" all the ecus, then it will revert the ECU back to the FA with the 5AP - so that may be an advantage to writing the FA back to the car after you edit out the 5AP.

I'm too novice to know which is the best way to go moving forward.

That is exactly how it would work.

When you get an i-step update, whether via ISTA, esys or OTA, it programs each ECU and then codes the ECU. It uses your car FA when doing the ECU code, and its the same as VO Coding.

Obviously any FDL coding will be wiped, and the coding will reflect what is set in the car FA - model type, build version, options (inc 5AP if still in the cars FA), language, etc

[LexxM3]

Originally Posted by ifr

That is exactly how it would work.

When you get an i-step update, whether via ISTA, esys or OTA, its programs each ECU and then codes the ECU. It uses your car FA when doing the ECU code, and its the same as VO Coding.

Obviously any FDL coding will be wiped, and the coding will reflect what is set in the car FA - model type, build version, options (inc 5AP if still in the cars FA), language, etc

That makes sense. Is it expected that the car FA is never re-written by any update (OTA or dealer) based on, say, the car configuration per VIN?

[ifr]

Originally Posted by LexxM3

That makes sense. Is it expected that the car FA is never re-written by any update (OTA or dealer) based on, say, the car configuration per VIN?

I've never heard of the FA being rewritten. The only times it might get changed is for a dealer retrofit of an option such as remote start, or when dodgy owners start coding.

[Espejo]

I had the same issue with OTA software update and now my ASS does not maintain last setting which I coded with Bimmercode. I just tried recoding it back in and now I get an error message and it will not code. Any one else run into this problem? The ASS was the biggest benefit.

[VTENGR]

Originally Posted by Espejo

I had the same issue with OTA software update and now my ASS does not maintain last setting which I coded with Bimmercode. I just tried recoding it back in and now I get an error message and it will not code. Any one else run into this problem? The ASS was the biggest benefit.

Are you trying to code with the engine running? Engine must be off to code ASS.

[Espejo]

Originally Posted by VTENGR

Are you trying to code with the engine running? Engine must be off to code ASS.

Ugh! Yes the engine was running. It's hot in Texas today and I had the AC running while I was coding.

Thanks. I will try it now.

[Espejo]

Thanks VTENGR, that was it. I kept car off, put in in coding mode and worked like a champ.

[VTENGR]

Originally Posted by Espejo

Thanks VTENGR, that was it. I kept car off, put in in coding mode and worked like a champ.

Glad to help - now get that AC back pumping!!

[Jank]

Same here, last OTA update reset all of my Bimmercode settings and more. Happened just today, back to square one. Will have to go through it all again...

[Jank]

Even the hatch opening height was reset to max. I'm glad I caught it before I opened it inside the garage.