[kinko]

Not that I know of.

Or [ having made the mistake in the CIC code ]? The CIC code was changed how?

 

[shawnsheridan]

Sorry, I do not understand your question.

 

[kinko]

Sorry, I do not understand your question.

I'm sorry.
What is the code of coding of HU_ClC?

 

[shawnsheridan]

It needs to match your actual Kombi:

 

[kinko]

It needs to match your actual Kombi:

View attachment 421833

Thank you. it tries -- mid and low.

My car. FA to build a date in 1112. ok?

 

[shawnsheridan]

Thank you. it tries -- mid and low.

My car. FA to build a date in 1112. ok?

It should be fine. I used 1211 in my VO when I VO Coded mine.

 

[ejs lt]

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.

 

[shawnsheridan]

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?

 

[ejs lt]

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.

 

[shawnsheridan]

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.

 

[ejs lt]

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...

 

[shawnsheridan]

Why can't you flash DKombi?

 

[ejs lt]

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.

 

[shawnsheridan]

Ok. Good luck!

 

[greicioforma]

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

 

[shawnsheridan]

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

 

[greicioforma]

nice ! looking to order new one cluster!

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

 

[secany]

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"

 

[wdimagineer]

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

 

[shawnsheridan]

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.