However, the incompetent dealer just physically replaced the controller but did not program the software to the vehicle, as prescribed by BMW, so the fault below continued to persist. I took my vehicle to dealer to have the iDrive controller replaced due to unrelated issue and assumed that when they replaced the controller and programmed it, the error would be eliminated. What happen was, the error was lingering in my vehicle's mapping. I did exactly the same change and the fault says control unit is not coded. I didn't understand finally what did he coded to remove this "fault" ? Old post but would be great if you see the message. I'm happy, everything is working now and I didn't lose any of my coding, so whatever. My first question to the service advisor was "did you guys have to update the vehicle's firmware" and he looked at me confused, like I had three ass cheeks or something. To close out this thread and answer my own question, the dealer replaced iDrive controller but did not have to update any of the vehicle's core data. Might be helpful to someone in the future, as there is nothing related to this subject anywhere on Bimmerpost. My appointment is this Friday, I will update this thread when they're done with my vehicle. I just want the iDrive controller fault removed, as I'm not trying to rock the boat, as far as updates are concern. Not to mention I have a European headlight switch installed, which would also produce a fault code, since that was also re-coded it to adapted to my US-spec vehicle. I don't mind getting a full software update but my concern is if the dealer updates all the modules, it would revert the "bulbs checks" I removed for my LCI LED taillights and produce an error message, since they would be programmed back to factory set parameters. Thanks you for your response, your contributions are always helpful You're probably in the same boat!Īll correct, but just so you know, there is no issue with upgrading the entire I-Step. From I-Step F020 17-11-530 to I-Step F020 19-07-539 the DME receives coding only, so presumably something minor and nothing that would affect my Bootmod3 flash. I'm running Bootmod3, and flashed back to stock and locked the DME before I started, but even that may not have been necessary.įortunately, calculating the list of updates in E-Sys shows you exactly what is going to be updated, showing each module and columns for Bootloader, Software, and Coding. One concern I had before flashing was that my DME might get updated during the process. Obviously I lost all of my coding, but had backups of the settings, and with E-Sys this is pretty easy to do. The process took 49 mins, and after all errors were cleared, and the Airbag re-enabled, the car was good to go on the newer I-Step. I did mine late last week to get Fullscreen CarPlay (working great by the way), and though I could have updated only the NBT2 unit, I was concerned about pre-requisites and so did the whole car. No need to use ISTA and program the whole car.Īll correct, but just so you know, there is no issue with upgrading the entire I-Step. Yes, you need to use E-Sys and program/code only controller(ZBE module).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |