Hello everyone,
I have a problem while retrofitting 6WB into F07
First of all sorry for the long post...

So, I'm using:

ICOM connected by Ethernet
E-sys 3.23.4 and E.25.3 with psdz 51.3
6WB with already cleared odometer and VIN
F07 I-step ship.: F001-09-08-532​

What I'm doing:

connect to car
read FA, save FA, edit FA (adding 6WB and changing ZeitKrit. to 1112 (also tried 0312, 0712))
again save FA, go back to TAL-calculating, activate edited FA

Read SVT, save SVT
Load saved SVT (I think this step is not needed)
Select "Calculation Strategy" to "Complete Flash"
Select I-Step ship. to F001-XX-XX-XXX
I-Step target is already F001-13-11-504
Calculate
HW-IDs from actual SVT (also tried skipping this step)
Save new SVT

Calculate TAL
Execute TAL

Deselect All
select DKOMBI blFlash, swDeploy, cdDeploy, ibaDeploy
"Check Software availability" - might be, that I forgot this step, but, as I understand, this function only "Checks". Later, without a car, I tried to check sw availability and got "OK ...." message, so that's OK.​

I tried to do the job with these Zeitkriterium: 1112, 0312, 0712
also with these F001-xx.. I-Step ship. and got the following results:

10-09-500, 12-03-500, calculated SVT includes KOMBI, so TAL suggests me to replace DKOMBI to KOMBI. OK, increasing I-Step ship...

12-07-510 - 12-11-501: I get this error when calculating SVT:

com.bmw.esys.domain.psdz.PsdzException: Generating target SVT with strategy complete flash and integration level "F001-13-11-504" (target) and "F001-12-11-501" (shipment) failed. [C324]
	at com.bmw.esys.domain.psdz.Psdz.generateSollverbauungGesamtflash(Psdz.java:759)
	at com.bmw.esys.domain.svt.SvtLogic.generateSvtTargetFromModel(SvtLogic.java:269)
	at com.bmw.esys.gui.svt.SvtCompareController.generateSvt(SvtCompareController.java:631)
	at com.bmw.esys.gui.svt.SvtTargetView$GenerateTargetSvtAction.doActionPerformed(SvtTargetView.java:408)
	at com.bmw.esys.gui.AbstractView$AbstractGuiProgressAction$1.init(AbstractView.java:425)
	at com.bmw.esys.gui.component.DialogProgress$2.construct(DialogProgress.java:152)
	at com.bmw.esys.gui.component.SwingWorker$2.run(SwingWorker.java:145)
	at java.lang.Thread.run(Unknown Source)
Caused by: KIS error: Die Werksverbauung enthält an der Diagnoseadresse 0x39 mehrere 100%-BNTN [010000003F040500, 08000003B5140501, 0600000312050000, 08000003B6140501, 08000003B7140501].
Timestamp: Wed Feb 19 18:30:47 EET 2014
ErrorCategory: SYSTEM_ERROR ID: 1283
Class: com.bmw.psdz.vehicle.softwarelogistik.kis.SollverbauungGenerator
ExecutionContext={category=KIS, ecuid=(UNKNOWN,?)}
	at com.bmw.psdz.vehicle.softwarelogistik.kis.SollverbauungGenerator.generateSollverbauungGesamtflash(SollverbauungGenerator.java:596)
	at com.bmw.psdz.vehicle.softwarelogistik.bf.SollverbauungsGeneratorBF.generateSollverbauungGesamtflash(SollverbauungsGeneratorBF.java:64)
	at com.bmw.psdz.uc.LogicImpl.generateSollverbauungGesamtflash(LogicImpl.java:726)
	at com.bmw.psdz.api.impl.bf.LogicBF.generateSollverbauungGesamtflash_aroundBody70(LogicBF.java:255)
	at com.bmw.psdz.api.impl.bf.LogicBF.generateSollverbauungGesamtflash_aroundBody71$advice(LogicBF.java:67)
	at com.bmw.psdz.api.impl.bf.LogicBF.generateSollverbauungGesamtflash(LogicBF.java:1)
	at com.bmw.esys.domain.psdz.Psdz.generateSollverbauungGesamtflash(Psdz.java:753)
	... 7 more

as I understand, NewFA and selected I-Step does not like ICM-V[39] module. So, increasing I-Step...

12-11-503 - 13-07-500: SVT calculation runs fast, then in new SVT I could found only these modules: 4x RK, TV MODUL, VSW
In calculated TAL to all other modules (also to DKOMBI) are given job hwDeinstal. Nevertheless I select everything as needed (blFlash...) and start this TAL. Everything goes in a minute (without flashing) and E-sys writes new VCM to car. After that I'm restoring original FA FP to car.​

Any ideas? I cannot find what I'm doing wrong.
Is there any way to directly flash/reflash ecu like in a good old WinKFP with any PN?
EDIT: OK, it should be possible by manualy editing TAL. So how could I determine, which HWAP is needed by my ecu, if it is HWAP_FFFFFFFF_255_255_255, or I could skip this step.
On the other hand, in that way I could flash DKOMBI - write VIN into it, but my DKOMBI will be left outdated with unknown CAFD...

P. S.
My "new" DKOMBI info:
production date (Hestelldatum) 04.02.11
programming date 30.03.11
BTLD_00001057_002_002_000
CAFD_00001060_001_000_003 <- this CAFD does not exist in 49.4 and 51.3 versions
FLSL_0000105F_002_002_003
HWAP_FFFFFFFF_255_255_255 <- is it normal?
HWEL_00001058_001_000_000
HWEL_00001059_001_000_000
SWFL_0000105A_002_002_003
SWFL_0000105B_002_002_003
SWFL_0000105C_002_002_003
SWFL_0000105D_002_002_003
SWFL_0000105E_002_002_003

----------------------------------------------------------------------------------------------
Conclusion.
As I know another master was able to start flashing procedure after writing new VIN to DKOMBI's EEPROM. Nevertheless flashing procedure was failing.
At the end this DKOMBI is not retrofited to the car.

 

No, HWAP_FFFFFFFF_255_255_255 is not normal. This means it is corrupt. It usually happens due to inadequate voltage / loss of power while flashing.

Was this 6WB new (virgin) or used kombi?

 

This 6WB is used, but it looks like that it was used for development or testing. It does not have any warranty labels outside, also I found inside ticks on the processors with hand-written numbers.
I haven't reached flashing procedure yet. These sw and app versions also could be read with INPA, so dkombi is not dead. Otherwise I use 45A power supply while flashing.
Also I noticed, while 6WB is connected on the bench, only background light comes up (after button press), but screen is black. In the car this screen comes up.

 

Used Kombi isn't just Plug-N-PLay. Far from it. First you need to use an EEPROM Programmer and blank the VIN and Mileage on the EEPROM, and then you need to flash it to write the car VIN to it.

 

I've desoldered and checked EEPROM. Mileage was blanked to 00, and All other data were already FF.
I am unable to flash dkombi...

 

Why can't you flash DKombi?

 

I cannot calculate valid Target SVT for this car because of several problems mentioned above.

I think, that it is possible to create custom TAL for flashing, but:
-I don't know DKOMBI's HWAP;
-I never tried to create custom TAL and flash ecu with it;
-current E-sys version can't code this dkombi because of unknown CAFD, so, I think, it also will not have BTLD and FLSL. And I don't studied yet how to determine, which firmware belongs to specified hardware in E-sys.

Nevertheless, yesterday another person also tried to code/flash dkombi with no success.
Currently this dkombi was given to service which works on instrument clusters. So we are waiting for an answer.

 

Ok. Good luck!

 

shawnsheridan,

i hava 2010 f10 pre lci with standart cluster no 6WA.
If i will buy new one 6WB, install process will be same like yours or without 6WA it will be more problems?
thanks for info !

I finally got around to installing my 6WB MFID Instrument Cluster.

Since mine was a brand new virgin Kombi, no EEPROM work was necessary to blank the donor car's mileage and VIN. Install was a breeze, and Coding was just a matter of adding 6WB to the VO, changing VO Production date to 1211, and VO Coding DKombi and HU_CIC.

Since my car does not have ECO Pro, I get just the Comfort and Sport mode displays.

Upgrading from the basic Kombi to either 6WA or 6WB is a dramatic improvement, and worth every penny. If I already had 6WA though, I personally would stick with it rather than invest in 6WB.

View attachment 379892

View attachment 379893

View attachment 379894

View attachment 379895

View attachment 379896

 

It will be the same as mine. I did not have 6WA either, only Basic Kombi.

 

nice ! looking to order new one cluster!

 

Hi Shawn,
I retrofit my 650i F13 with this 6WB around a year ago and it working great. I'll get a X5 F15 very soon, since they don't have 6WB as an option, I'm thinking about moving my 6WB from F13 to F15. Do you think it will work? Same coding process?
I asked bimmer-tech a month ago regarding retrofit 6WB for X15 F15 and I don't know why they said it won't work with F15

Here is his email
"Unfortunately it won't work for the F15 just yet.

Kind regards,
Patryk Matysiak"

 

I'll let you know if it works in a few days.

 

I don't know of any reason 6WB wouldn't work in F15, but Patryk is the real expert, and if he wrote that, I have to believe he had good reason. If F15 has CAS built into BDC, maybe there is some issue related to that.

Besides the VIN, be damn sure to blank the 6WB mileage, which may require removal of the EEPROM, and bench test / verify 0 miles it before installing it.

 

I dug a little deeper and yes, it's due to CAS being combined into BDC. So for now, no 6WB in the F15. I cancelled my order just in time.

 

I finally got around to installing my 6WB MFID Instrument Cluster.

Since mine was a brand new virgin Kombi, no EEPROM work was necessary to blank the donor car's mileage and VIN. Install was a breeze, and Coding was just a matter of adding 6WB to the VO, changing VO Production date to 1211, and VO Coding DKombi and HU_CIC.

Since my car does not have ECO Pro, I get just the Comfort and Sport mode displays.

Upgrading from the basic Kombi to either 6WA or 6WB is a dramatic improvement, and worth every penny. If I already had 6WA though, I personally would stick with it rather than invest in 6WB.

View attachment 379892

View attachment 379893

View attachment 379894

View attachment 379895

View attachment 379896

edit the IcmKod_B_ECONOMIC to verbaut can get the ECO mode display. i tested it on my 523LI

 

Eco Mode Display



Hi wenlian_wang,
Please provide details on this code. My car doesn't have Eco mode by default.

Thank you.

 

Hi Shawn,
May I have the link of full psdzdata 52.2?
I asked flashing all ECUs to my local Dealer but they could not do that because of my 6WB cluster.
The ISTA/P required "Please change the cluster" and I changed mine back to Original cluster and removed 6WB code from my FA but flashing was not started.

I am going to try flashing using E-Sys according to this thread http://www.bimmerfest.com/forums/showthread.php?t=762988

Thanks in advance.

 

Hi Shawn,
May I have the link of full psdzdata 52.2?...

PM sent.

 

Anyone know what is the BMW part no. for the 6WB Full LCD Instrument Cluster retrofit for F10 2013 (pre-lci)?

I plan to get this from my local BMW parts distributor but they need me to provide the Part No.

 

Enter your VIN number into this site http://realoem.com/bmw/select.do?lang=en and select the cluster.
So can get the latest parts number available for your car.

 

Yes, I did that previously but I am not sure whether I got the right Part No. The picture from the RealOEM website showed the old instrument cluster (not the LCD Type).

http://realoem.com/bmw/showparts.do?model=XG12&mospid=53589&btnr=62_0551&hg=62&fg=05&lang=en
From the my selection, if I choose KM/H, 6WBA = Yes, HUD (S610A) = Yes, I get 62109319002. Can someone confirm is this the right Part No. for the 6WB Full LCD Instrument cluster?

And does it matters if I get the instrument cluster with HUD support (6WB) despite that I dun have HUD? I plan to retrofit HUD later.

 

The picture is just a sample.
Your 6WB cluster number is 62109319002 because 6WB = Yes, HUD = Yes.
The 6WB cluster has both KM/H and MPH functions in it.

 

The 6WB cluster with HUD function is available for no HUD car.
The difference between the 6WB with HUD and the 6WB without HUD is just the connector which links to the HUD modules.
Though I think it is very hard to retrofit the HUD function later...

 

Hi Tom2325, thanks for the input. Very much appreciated.

 

Yes, I am running 6WB Cluster with HUD Connection in a non-HUD car. No issues doing so.

 

Greetings,
Where can i get 6WB instrument cluster for good price
i want it used in good condition

 

Desperately needing assistance with 6WB

I just got my brand new 6wb Cluster. I am not able to find a CAFD under the KOMBI. When I finally think I am to the right place I get a RED line item in under the FA list. Can someone please assist.
This is a brand new 2014 LCI 535d xdrive. Can someone assist?

 

What do you mean? What is wrong with the CAFD shown in the pictures? Insert it, and then VO Code DKombi (Right-Click on DKombi ECU and select CODE).

 

Hello!

That's exactly the same issue I had with the 6WB. The car i-step is 13-11-504 and I can only inject CAFD not higher than 13-03-505. In that case no entertainment lists were possible cause therefore you need 50.x (13-07-50x) or higher. Flashing the Kombi to a higher i-step ended in a msm ethernet error and was not possible.

Next problem. I got two 6WA from a 740i and 750i from 2008. The curcuit board is different from the 6WA I had before. From the first cluster the Eeprom was deleted but E-Sys told me that the cluster is not in the KIS database and so I was not able to detect any CAFD for this cluster. The second cluster is a hard thing cause the Eeprom is not on the known place and it's not easy to find the small 8-pin Eeprom on the board.

CU Oliver

 

Hello!

Please take a look into the ECU Dkombi for SLI. This should be activated and (if I remember right) set to the correct generation.

Just another question. Which i-level could you detect for the 6WB? Someone higher than 13-03-505?

CU Oliver

 

Hi, today is arrived used petrol 6wb kombi, I did the retrofit, just no problem converting petrol-diesel as I expected. This time I decided to enter in eprom my VIN, the flash went well at first shot... with a warning! Maintenance service doesn't work (Red Dot Tamper), as in my retrofit of 6WA.
The first time the cause was that in EPROM isn't erased the short VIN, this time I checked and rechecked, we note that the map is different I found only 2 short VIN and not long VIN, can it be?
My car is 0911 i used 0312 for flash
Tomorrow desolder eprom and see...

 

Shawn I think I understood, the used Kombi was bungled, I checked the "original" file there is a VIN that belongs to a frame 535 d Xdrive Germany, In the photo you see that the car was petrol and the icon showed 7 Series F01
I understand that they have canceled the initial part of the Long Vin