[Loliceman]

Hey all!

I have a huge problem with this F11 2012-01 currently in our workshop.

I need urgent remote help or professional experience/input on how to proceed..

Used NBT + used 6WB has been fitted.


-6WB cluster is from EU 2016 car with late 2016 software update and approximately 6000km. It has been "virginized" by a local guy who works with ECU programing, we have unfortunately had bad experiences with this guy before..

-NBT is from EU 2015 car.


I have not been alone working with this car, before I started to work with it this has been done:
-CHAMP2 has been replaced by NBT. Kcan2 from ZBE and TBX to Quadlock pin 9 and 11 -> spliced into ZGW pin 48+49
-Replaced ZGW ZGW with MOST -> Used ZGW02-4SK without MOST.
-6WB cluster has been put instead of old KOMBI_low.

What works and what does not work:
-NBT Boots up and works like it should, however , its not possible to use FSC pack on this NBT. When we store + check SIG cert, we get a strange error like "message ID has been used multiple times".

-6WB has faulty vin and possibly also mileage, on "hidden menu" vin displays just a few dots.. and in Tool32 it reads "000000000000"

-Fault codes for incorrect VIN and checksum, signals due to vin etc. Every faultcode is related to mileage and VIN is present in most modules in the car. (ICM,DSC,JBBF,KOMBI etc).

-Fault codes in KOMBI is present, it has something to do with faulty EEPROM and checksums.

-KOMBI cant be coded in Esys, After injecting CAFD from SWE then "CODE", it returns "WBDI_CPS" error and we get "FinishedWithError". So apparently VIN is messing with us. CPS is YYYYYYYYY


I would like to get some help from someone who has seen similar issues before and perhaps have more knowledge than me. I have done quite a few retrofits like this, but never encountered any of these errors..
Im not yet that experienced in EEPROM manipulation/virginization etc.

My guess is that the "virginization" of the 6WB is faulty.. But would that really effect DSC/ICM and also NBT FSC input?
I will be available for remote session whenever during the day if anyone could be kind and take a look. I really appreciate any input or suggestion here.

Best Regards
Loliceman

[lynxbmw]

I can take a look.

[gt678]

I had this fault with Kombi some times, when I was´t able to code a Kombi the EEPROM was´t soldered correctly.
After resoldering everything was fine.

[Thorsten]

Hi,

First solution should be to reinstall the original cluster, to have only one problem to fix.
ZGW change wasn't needed, on 2012-1 cars, ZGW2 with MOST was installed, flashing the ZGW should be enough.
But ok, you changed it and it should work.
NBT is from F10 or perhaps another unit from other car, like F30?


Thorsten

[temsky740]

What eeprom in kombi now? Let me know.
Write here numbers of faults in kombi , and nbt too if it has.

[navigatepark]

Hi
what is EEprom from 6WB?
is it EEprom to 35160WT ?

[Loliceman]

Hi
what is EEprom from 6WB?
is it EEprom to 35160WT ?

Yes
EEPROM was 35160WT, 6WB HW 73
part no 6821074

[temsky740]

And still we dont know numbers and texts of mistakes.
I think he didnt do 35160 !!WT!! , thats why such problems with kombi.

[paskuale]

With 35160WT you can't reset the mileage of Kombi.
It can be a test put inside dump with original mileage (6000KM) but without VIN and see if E-sys will code anyway.
If not you need to install a 35160WT emulator inside cluster.

[temsky740]

With 35160WT you can't reset the mileage of Kombi.
It can be a test put inside dump with original mileage (6000KM) but without VIN and see if E-sys will code anyway.
If not you need to install a 35160WT emulator inside cluster.

He can reset 35160WT