New Kombi module not working properly

dextuar · 03-16-2017, 02:50 PM

Hi guys,

I have the following issue. I have a 320d from 2006. In one sentence - I bricked my perfectly working KOMBI. I bought a used one and paid a guy to write my VIN and mileage on it. Everything works fine on the "new" one except there is now no indication when the cruise control gets activated. I also do not have an option to code the current fuel consumption. I found out that the "new" KOMBI is from a 320d from 2005 and did not previously have a cruise control. I thought the issue was that the new module has had never been updated in contrast to my old one which was updated back in 2010, therefore I updated the new KOMBI with WINKFP and the latest DATEN (v60.1). But the issue still persists. Nevertheless I saw, that the old KOMBI updated back in 2010 had a software version of 9XXXXX, but the new updated one has version 6XXXXXX. How is this possible? Is there a way how I could update the new KOMBI so that it also has version 9XXXXXX, maybe this is the reason it is not working right now? Attached you can find info about the old configuration and the new one. Any help would be highly appreciated.

NEW KOMBI

OLD KOMBI

Dtype · 03-16-2017, 03:54 PM

Update it with winkpf

dextuar · 03-16-2017, 04:27 PM

Quote:

Originally Posted by Dtype

Update it with winkpf

I already did. See the date - 06.03.2017

Dtype · 03-16-2017, 05:55 PM

Quote:

Originally Posted by dextuar

Quote:

Originally Posted by Dtype

Update it with winkpf

I already did. See the date - 06.03.2017

Now code to default with expert profile.
If doesn't work, try to force same zb as tou have on old kombi.

dextuar · 03-16-2017, 06:52 PM

Quote:

Originally Posted by Dtype

Now code to default with expert profile.
If doesn't work, try to force same zb as tou have on old kombi.

Is this safe, updating with another ZB number? Won't that brick the module if it fails? In the new Daten i cannot find any ZB number in KOMBL2 with 9Xxxxx, they are all with 6Xxxxx

808AWD325xi · 03-16-2017, 08:24 PM

Quote:

Originally Posted by dextuar

Hi guys,

I have the following issue. I have a 320d from 2006. In one sentence - I bricked my perfectly working KOMBI. I bought a used one and paid a guy to write my VIN and mileage on it. Everything works fine on the "new" one except there is now no indication when the cruise control gets activated. I also do not have an option to code the current fuel consumption. I found out that the "new" KOMBI is from a 320d from 2005 and did not previously have a cruise control. I thought the issue was that the new module has had never been updated in contrast to my old one which was updated back in 2010, therefore I updated the new KOMBI with WINKFP and the latest DATEN (v60.1). But the issue still persists. Nevertheless I saw, that the old KOMBI updated back in 2010 had a software version of 9XXXXX, but the new updated one has version 6XXXXXX. How is this possible? Is there a way how I could update the new KOMBI so that it also has version 9XXXXXX, maybe this is the reason it is not working right now? Attached you can find info about the old configuration and the new one. Any help would be highly appreciated.

NEW KOMBI

OLD KOMBI

Your new kombi doesn't support dynamic cruise control or active cruise control.

They are from two different ECU families, hence why the ZB numbers are different. The new one is KOMBL2 and the old one is BKOML2.

Dtype · 03-17-2017, 02:32 AM

Didn't notice the ecu family.

dextuar · 03-17-2017, 03:47 AM

Quote:

Originally Posted by 808AWD325xi

Your new kombi doesn't support dynamic cruise control or active cruise control.

They are from two different ECU families, hence why the ZB numbers are different. The new one is KOMBL2 and the old one is BKOML2.

So there is no way how I can fix it? My car has just the normal cruise control without breaking function.

Is there at least a way how to activate again DIGITAL_KVA ? I do not find it as an option to activate

808AWD325xi · 03-17-2017, 10:11 AM

Quote:

Originally Posted by dextuar

So there is no way how I can fix it? My car has just the normal cruise control without breaking function.

Is there at least a way how to activate again DIGITAL_KVA ? I do not find it as an option to activate

The current firmware is for a RHD vehicle, flashing to a LHD version will probably help.

Which CDB file does NCS-Expert use to code your kombi?

What are the last 7 digits of your VIN?

If you found this information useful, please click on the Appreciate button at the bottom of this post.

808AWD325xi · 03-17-2017, 03:13 PM

Based on your VIN, I recommend flashing your new kombi with ZB number 6984974. It matches your vehicle steering and was qualified for your chassis type.

Unfortunately, it probably won't correct the cruise control issue. Your vehicle was not originally optioned for cruise control.

Can you post your FA/VO?

dextuar · 03-17-2017, 03:49 PM

Quote:

Originally Posted by 808AWD325xi

Based on your VIN, I recommend flashing your new kombi with ZB number 6984974. It matches your vehicle steering and was qualified for your chassis type.

Unfortunately, it probably won't correct the cruise control issue. Your vehicle was not originally optioned for cruise control.

Can you post your FA/VO?

Yep, I retrofitted the cruise control myself a few months ago and everything worked fine, I will check the FA/VO, would a screenshot of NCS Expert be enough or should I do it with Toolset32? I have never really used toolset32, therefore I have no idea if it should be done that way. Cruise control is not a big deal for me, however I used to always use the digital KVA and miss it a lot. I will update KOMBI with winkfp and ZB number 6984974 and report back.

Thank you once again for your help!

808AWD325xi · 03-17-2017, 04:33 PM

Quote:

Originally Posted by dextuar

Yep, I retrofitted the cruise control myself a few months ago and everything worked fine, I will check the FA/VO, would a screenshot of NCS Expert be enough or should I do it with Toolset32? I have never really used toolset32, therefore I have no idea if it should be done that way. Cruise control is not a big deal for me, however I used to always use the digital KVA and miss it a lot. I will update KOMBI with winkfp and ZB number 6984974 and report back.

Thank you once again for your help!

You're welcome!

You can display the FA/VO with INPA...E90 -> Select E90 -> Functional Jobs -> <Shift> + <F2> Vehicle data. Be sure to scroll down to display any E-words, HO-words, etc.

Sensible_ · 03-17-2017, 06:29 PM

Quote:

Originally Posted by dextuar

Quote:

Originally Posted by 808AWD325xi

Based on your VIN, I recommend flashing your new kombi with ZB number 6984974. It matches your vehicle steering and was qualified for your chassis type.

Unfortunately, it probably won't correct the cruise control issue. Your vehicle was not originally optioned for cruise control.

Can you post your FA/VO?

Yep, I retrofitted the cruise control myself a few months ago and everything worked fine, I will check the FA/VO, would a screenshot of NCS Expert be enough or should I do it with Toolset32? I have never really used toolset32, therefore I have no idea if it should be done that way. Cruise control is not a big deal for me, however I used to always use the digital KVA and miss it a lot. I will update KOMBI with winkfp and ZB number 6984974 and report back.

Thank you once again for your help!

If you run into problems, cruise control can be activated via nettodat coding.

Sensible_ · 03-17-2017, 06:30 PM

Quote:

Originally Posted by dextuar

Quote:

Originally Posted by 808AWD325xi

Based on your VIN, I recommend flashing your new kombi with ZB number 6984974. It matches your vehicle steering and was qualified for your chassis type.

Unfortunately, it probably won't correct the cruise control issue. Your vehicle was not originally optioned for cruise control.

Can you post your FA/VO?

Yep, I retrofitted the cruise control myself a few months ago and everything worked fine, I will check the FA/VO, would a screenshot of NCS Expert be enough or should I do it with Toolset32? I have never really used toolset32, therefore I have no idea if it should be done that way. Cruise control is not a big deal for me, however I used to always use the digital KVA and miss it a lot. I will update KOMBI with winkfp and ZB number 6984974 and report back.

Thank you once again for your help!

If you run into problems, cruise control can be activated via nettodat coding.

Levanime · 03-17-2017, 10:01 PM

assuming that kombi has needle,
but i guess all e9X kombi-s have it

i know there are differences on e60, low versions dont have needle at all

dextuar · 03-18-2017, 12:58 PM

Quote:

Originally Posted by 808AWD325xi

You're welcome!

You can display the FA/VO with INPA...E90 -> Select E90 -> Functional Jobs -> <Shift> + <F2> Vehicle data. Be sure to scroll down to display any E-words, HO-words, etc.

Hi again,

I updated the module with the suggested ZB but still no change both in KVA and cruise control display.

Here a screenshot from NCS Expert.

I have attached the TRC and NETTODAT from after the update with Winkfp.

This is the info from INPA in regard to FA/VO.

I-step plant: E89X-06-03-510
I-step dealer: E89X-10-03-502
I-step backup: E89X-10-03-502
-----------------------------------------------------------------
Model: E90_
Model code: VC31
Coding date: 0306
Paint code: 0668
Upholstery code: ALAT
Nos. of SA: 39
1CA 200 249 320 321 322 358 418 423 428
430 431 441 465 493 494 4AG 502 508 520
521 522 534 540 548 609 612 620 633 6AA
710 735 761 7R9 801 843 855 863 879
Nos. of E word: 1
B080
Nos. of HO word: 0
================================================== ===============

Sensible_ · 03-18-2017, 01:58 PM

So have you now coded the KOMBI to default???? Can't see you mentioning it in previous posts...

Sensible_ · 03-18-2017, 02:13 PM

If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat.

In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess.

Choose the job codierdaten_lesen and in the arguments section write: 0x3101

Run the job and paste the results here...

dextuar · 03-18-2017, 02:38 PM

Quote:

Originally Posted by Sensible_

If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat.

In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess.

Choose the job codierdaten_lesen and in the arguments section write: 0x3101

Run the job and paste the results here...

After the update, I coded it to default, I do that after every update with Winkfp, just forgot to mention it

I will try and report back

808AWD325xi · 03-18-2017, 03:14 PM

Quote:

Originally Posted by dextuar

Hi again,

I updated the module with the suggested ZB but still no change both in KVA and cruise control display.

Here a screenshot from NCS Expert.

I have attached the TRC and NETTODAT from after the update with Winkfp.

This is the info from INPA in regard to FA/VO.

I-step plant: E89X-06-03-510
I-step dealer: E89X-10-03-502
I-step backup: E89X-10-03-502
-----------------------------------------------------------------
Model: E90_
Model code: VC31
Coding date: 0306
Paint code: 0668
Upholstery code: ALAT
Nos. of SA: 39
1CA 200 249 320 321 322 358 418 423 428
430 431 441 465 493 494 4AG 502 508 520
521 522 534 540 548 609 612 620 633 6AA
710 735 761 7R9 801 843 855 863 879
Nos. of E word: 1
B080
Nos. of HO word: 0
================================================== ===============

Sorry that it didn't help. CDB KMBI_PL2.C05 doesn't contain the keyword DIGITAL_KVA and ZB number 6984974 is the latest for that kombi.

Quote:

Originally Posted by Sensible_

If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat.

In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess.

Choose the job codierdaten_lesen and in the arguments section write: 0x3101

Run the job and paste the results here...

Hopefully Sensible_ can help you get the cruise control working. He's a pro at that stuff!

dextuar · 03-19-2017, 07:44 AM

Quote:

Originally Posted by Sensible_

If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat.

In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess.

Choose the job codierdaten_lesen and in the arguments section write: 0x3101

Run the job and paste the results here...

Here is the result:

apiJob("KOMB87","codierdaten_lesen","0x3101","")

Satz : 0
OBJECT = komb87
SAETZE = 1
JOBNAME = codierdaten_lesen
VARIANTE = KOMB87
JOBSTATUS =
UBATTCURRENT = -1
UBATTHISTORY = -1
IGNITIONCURRENT = -1
IGNITIONHISTORY = -1
Satz : 1
JOB_STATUS = OKAY
CODIERDATENBLOCK = 23 Bytes
0000 : 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .yyyyyyy yyyyyyyy
0010 : FF FF FF FF FF FF FE yyyyyy?
_TEL_ANTWORT = 30 Bytes
0000 : 9A F1 60 62 31 01 01 FF FF FF FF FF FF FF FF FF ?n`b1..y yyyyyyyy
0010 : FF FF FF FF FF FF FF FF FF FF FF FF FE 69 yyyyyyyy yyyy?i

Sensible_ · 03-19-2017, 08:04 AM

Quote:

Originally Posted by dextuar

Quote:

Originally Posted by Sensible_

If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat.

In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess.

Choose the job codierdaten_lesen and in the arguments section write: 0x3101

Run the job and paste the results here...

Here is the result:

apiJob("KOMB87","codierdaten_lesen","0x3101","")

Satz : 0
OBJECT = komb87
SAETZE = 1
JOBNAME = codierdaten_lesen
VARIANTE = KOMB87
JOBSTATUS =
UBATTCURRENT = -1
UBATTHISTORY = -1
IGNITIONCURRENT = -1
IGNITIONHISTORY = -1
Satz : 1
JOB_STATUS = OKAY
CODIERDATENBLOCK = 23 Bytes
0000 : 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .yyyyyyy yyyyyyyy
0010 : FF FF FF FF FF FF FE yyyyyy?
_TEL_ANTWORT = 30 Bytes
0000 : 9A F1 60 62 31 01 01 FF FF FF FF FF FF FF FF FF ?n`b1..y yyyyyyyy
0010 : FF FF FF FF FF FF FF FF FF FF FF FF FE 69 yyyyyyyy yyyy?i

Hmm,

Coding block is empty. Have you physically taken apart the KOMBI to see if the CC slider/indicator is present?

is this a KOMBI high or low? (Big lower screen or small screen?)

I can make you a nettodat.man for CC activation but if the physical motor and slider aren't there it won't work.

03-16-2017, 03:54 PM	#2
Dtype Lieutenant 39 Rep 400 Posts Drives: BMW F30 320d Join Date: Aug 2013 Location: Lisbon iTrader: (0)	Update it with winkpf
	Appreciate 0 Quote

03-17-2017, 02:32 AM	#7
Dtype Lieutenant 39 Rep 400 Posts Drives: BMW F30 320d Join Date: Aug 2013 Location: Lisbon iTrader: (0)	Didn't notice the ecu family.
	Appreciate 0 Quote

03-17-2017, 03:13 PM	#10
808AWD325xi Ballin' out of control. 529 Rep 1,289 Posts Drives: 2009 335i Join Date: Jul 2007 Location: Moline, IL iTrader: (0)	Based on your VIN, I recommend flashing your new kombi with ZB number 6984974. It matches your vehicle steering and was qualified for your chassis type. Unfortunately, it probably won't correct the cruise control issue. Your vehicle was not originally optioned for cruise control. Can you post your FA/VO? __________________ Alpina B3 Flash/BMS OCC/ER CP/ETS 5/HKS BOV/M3 Control Arms
	Appreciate 1 dextuar9.00 Quote

03-17-2017, 10:01 PM	#15
Levanime BimECU 193 Rep 760 Posts Drives: BMW Join Date: Dec 2014 Location: SD iTrader: (0) Garage List 2007 BMW 335 [0.00]	assuming that kombi has needle, but i guess all e9X kombi-s have it i know there are differences on e60, low versions dont have needle at all
	Appreciate 0 Quote

03-18-2017, 01:58 PM	#17
Sensible_ Colonel 535 Rep 2,503 Posts Drives: 2008 E90 Join Date: Feb 2012 Location: London iTrader: (1)	So have you now coded the KOMBI to default???? Can't see you mentioning it in previous posts...
	Appreciate 0 Quote

03-18-2017, 02:13 PM	#18
Sensible_ Colonel 535 Rep 2,503 Posts Drives: 2008 E90 Join Date: Feb 2012 Location: London iTrader: (1)	If you have coded the KOMBI to default and CC is till now working I suggest activating by nettodat. In tool32 choose the KOMBI prg file - KOMB87.prg for your KOMBI I guess. Choose the job codierdaten_lesen and in the arguments section write: 0x3101 Run the job and paste the results here...
	Appreciate 2 dextuar9.00 808AWD325xi529.00 Quote