CarTechnoloGY
F32 6WB weird behaviour - Printable Version

+- 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: F32 6WB weird behaviour (/showthread.php?tid=78968)



F32 6WB weird behaviour - solidss - 17-05-2023

Hello mates!

So...6WB retrofit in a F32 with 6WA...first dismantled 6WB and erased long and short VIN in 95320 and replaced 35160WT with VVDI one...also erased mileage and short VIN and installed on car, VO coded it with 0317 and 6WB and everything was fine. After a while decided to do some FDL coding...but that caused the DKOMBI to lose LONG VIN in 95320 eeprom...strange I thought, so I entered again LONG VIN in 95320 and installed the KOMBI again, coded and everything's fine again!

But...I was curius to do FDL coding to see if the same thing occurs again. And it did!
DKOMBI seems like uncoded, with red dot...So again dismantled it and read both eeproms but to my surprise no VIN is erased! Eproms are intact. If you try to read CAFD from esys you dont see any VIN (yyyyyy). Also in ISTA there is fault code for instrument cluster VIN mismatch...but where is it since all 3 VINS are intact in both eeproms.

Has any of you encountered something like this before?