+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: Solved ✔ F10 coding problem (/showthread.php?tid=47437)
F10 coding problem - BobbySD - 03-03-2019
Hello,
I got here F10 from 2012 (DX33176) and the customer hit a deer whit it whitch ended up with destroyes headlight. Car went to dealer and they change the headlight, told the owner that they also change unspecified ecu + idrive controler due to short circuit from headlight...
Now car as it is works but... lane departure is not working, cruise control is not working and in idrive car status there is a newly adblue.
As far I was able to determine changed ecu it was zgw but Im not sure about that... zgw was flashed 2 weeks ago. After first scan with ista there were 5 errors
802A07 - drivers seat adjustment switch block (LIN): wrong equipment specification
802C07 - same for passanger
D35426 - signal (total braking torque request 60.1.4) invalid, transmiter ICM
D3553E - signal (roadway inclination, 56.1.2) invalid, transmiter ICM
E0D410 - no message (status of stepless high-beam headlight assist, 0x96), receiver FLA, transmitter BDC/FEM/FRM
Highbeam assist is working. I tried to code SMFA/B with esys but errors remains. Its unable to code / flash the car with ista because it want to uninstal TBX and want instal CON so I did everything with esys. I also tried flash to 18-11-520 istep and it was done ok BUT after that many ecu's showed in ista as re disconnected. Why? Why car things that there is adblue and why it is looking for acc radar? I also reload the FA to the car but its still the same. How can I code it to original working state without adblue and acc?
In attachement you can find ista protocol and FA.xml from esys. This is really strange how this car behaving.
I will be thankful for any advice.
RE: F10 coding problem - lagunasec - 03-03-2019
In your FA.xml time criteria is 07/14 and the car was produced in 10/12.
Someone modified the FA (maybe the car has some retrofit done).
You should modify time criteria in FA (change to 1012) and flash the car again.
RE: F10 coding problem - BobbySD - 03-03-2019
nope there is no retrofit done only changed zgw and idrive controler. Will try thank you
RE: F10 coding problem - KaiO - 03-03-2019
Why you don't go to dealer again? It's their fault...
RE: F10 coding problem - bmwcoder75 - 03-03-2019
(03-03-2019, 09:57 AM)KaiO Wrote: Why you don't go to dealer again? It's their fault...
Cause getting a 7 years old out of warranty at dealer was an expensive mistake in the first place and the dealer probably wants to charge an extra few thousands now to replace more parts...
Just a wild guess
RE: F10 coding problem - BobbySD - 03-03-2019
I can only guess, its customer choice
anyway when I change time criteria to 1012 I get error when calculating FP that not all elements were found for 1012
RE: F10 coding problem - BobbySD - 03-03-2019
idrive touch controller is retrofited, thats why criteria is 713... i dont have thenols one so cant really flash it with ista. Any ideas?
RE: F10 coding problem - BobbySD - 03-03-2019
hehe again I figured out by myself xD I put back old controller (it was in trunk), disconnected TBX and flash/code car with ista. Connected back tbx with touch controller, coded, done.