[boldorider4]

Hi everyone!

So, I got a used and virginized 6WA cluster kombi made on 2013-04-09 and retrofitted it to my 2015-03 F22.
I found out that the old BKOMBI entry in the SVT had to be deleted and written into the car VCM SVT-Target so E-Sys can correctly display the KOMBI in the ECU list. I think someone is already familiar with this issue because it was discussed in other forums, so thanks everybody for those useful posts!

So I finally managed to code the Kombi to my car FA and also got the selected gear to show on the cluster (which was also a common issue...SPA_IST_GANG_ENABLE --> nicht_aktiv!!!).

Now I have one new issue, namely the directions on the cluster display are not shown in the correct color table: at intersections you will see the roads displayed in gray but the arrow pointing into the direction to go are also displayed in gray, making them basically invisible.

After a bit of research, I figured the problem is the parameter:

KOMBI CAFD:
NAVICOLOR_TABLE --> from neue_farbtabelle to farbwelt_id5

but because my CAFD does not show farbwelt_id5 as an option (it only shows neue_farbtabelle and alte_farbtabelle), I guess the issue is that the 13-03 firmware of the cluster is too old. Do you guys agree with this theory? Or maybe the firmware of the NBTevo (which was retrofitted and updated) is just too new (22-11) and therefore only supports 6WB?

So I guess the only thing I can try is flash the cluster with newer firmware than 13-03. But I also read that the I-Step gap between FEM and KOMBI shouldn't be too big otherwise the FEM (and possibly more ECUs) would need to get flashed as well. My current FEM firmware is still stock, therefore on I-Step 15-03.

So my question to you guys: does anyone have an old enough PSDzData Full that doesn't deviate too much from 15-03? Maybe from 2016 or 2017?

[boldorider4]

TheNine90 , shawnsheridan your inputs would me most appreciated

[shawnsheridan]

Originally Posted by boldorider4

TheNine90 , shawnsheridan your inputs would me most appreciated

I do not have any older psdzdata version. Just the latest. You can laways flash FEM also.

First, make sure you have FDL Coded HU_NBT2 => KOMBI_CIC = kombi_mid for 6WA to ensure that is not your issue.

[boldorider4]

Originally Posted by shawnsheridan

I do not have any older psdzdata version. Just the latest. You can laways flash FEM also.

First, make sure you have FDL Coded HU_NBT2 => KOMBI_CIC = kombi_mid for 6WA to ensure that is not your issue.

Hi Shawn,

thanks so much about the great suggestion!
I actually have KOMBI_CIC=kombi_high in my case.
Do you think a 6WA kombi w/ production date 2013-04-09 and I-Step 13-03 would correspond to KOMBI_CIC=kombi-mid on the HU_NBT2? Mind you, every single other function on the kombi works 100%.

[shawnsheridan]

Originally Posted by boldorider4

Hi Shawn,

thanks so much about the great suggestion!
I actually have KOMBI_CIC=kombi_high in my case.
Do you think a 6WA kombi w/ production date 2013-04-09 and I-Step 13-03 would correspond to KOMBI_CIC=kombi-mid on the HU_NBT2? Mind you, every single other function on the kombi works 100%.

I believe it is this:

kombi_low = Basic Kombi
kombi-mid = 6WA Kombi
kombi-High= 6WB Kombi

Just change it to kombi-mid and test it. You can always change it back.

[boldorider4]

Originally Posted by shawnsheridan

I believe it is this:

kombi_low = Basic Kombi
kombi-mid = 6WA Kombi
kombi-High= 6WB Kombi

Just change it to kombi-mid and test it. You can always change it back.

By the way, I also have KOMBI_RES = 'high' and other possible values are 'mid' and 'nicht_aktiv'. The comment reads "Most or can combi", so I'm guessing this also needs to be set accordingly.

[shawnsheridan]

Originally Posted by boldorider4

By the way, I also have KOMBI_RES = 'high' and other possible values are 'mid' and 'nicht_aktiv'. The comment reads "Most or can combi", so I'm guessing this also needs to be set accordingly.

Start with KOMBI_CIC FDL Code and go from there.

[boldorider4]

Hi shawnsheridan ,

unfortunately all my attempts were unsuccessful. I tried setting one at a time and finally altogether the following:

KOMBI_CIC --> kombi_mid
KOMBI_RES --> mid
KI_KOMBI_VARIANT --> mid_35up_apix, mid_35up_oabr, rr_35up

and then I also trying switching on and off all FPK-related values, namely:

FPK_COMING_ROAD_BMP --> aktiv/nicht_aktiv
CALMING_KOMBI --> aktiv/nicht_aktiv
DRIVE_MODE_KOMBI --> aktiv/nicht_aktiv
LOUPE_TACHO_KOMBI --> aktiv/nicht_aktiv
MFID_KOMBI_VARIANT --> aktiv/nicht_aktiv
KOMBI_AUFLOESUNG --> aktiv/nicht_aktiv

I guess it really could be a SW (like the I-Step) or HW issue with the kombi. Or maybe the 'neue_farbtabelle' (new color table), which is older than farbwelt_id5, is simply not supported on 11-22 NBTevo.

[shawnsheridan]

Originally Posted by boldorider4

Hi shawnsheridan ,

unfortunately all my attempts were unsuccessful. I tried setting one at a time and finally altogether the following:

KOMBI_CIC --> kombi_mid
KOMBI_RES --> mid
KI_KOMBI_VARIANT --> mid_35up_apix, mid_35up_oabr, rr_35up

and then I also trying switching on and off all FPK-related values, namely:

FPK_COMING_ROAD_BMP --> aktiv/nicht_aktiv
CALMING_KOMBI --> aktiv/nicht_aktiv
DRIVE_MODE_KOMBI --> aktiv/nicht_aktiv
LOUPE_TACHO_KOMBI --> aktiv/nicht_aktiv
MFID_KOMBI_VARIANT --> aktiv/nicht_aktiv
KOMBI_AUFLOESUNG --> aktiv/nicht_aktiv

I guess it really could be a SW (like the I-Step) or HW issue with the kombi. Or maybe the 'neue_farbtabelle' (new color table), which is older than farbwelt_id5, is simply not supported on 11-22 NBTevo.

Ok, flash it is then.

[boldorider4]

Originally Posted by shawnsheridan

Ok, flash it is then.

Cool!

I think I’d still like to be a little conservative and flash 03-18 on the KOMBI so the deviation with FEM is minimal (FEM is 03-15).

NBTevo is on 11-22 but it was VO-Coded with Zeitkriterium 03-18 (I know it doesn’t make a great deal of difference), but as far as I know, in 2018 cars were already sold with an NBTevo and also still with a non-black panel 6WA.

If that still doesn’t work, I can still flash the KOMBI again to 11-22.

Thanks, Shawn!

[boldorider4]

Oh, shawnsheridan, I almost forgot:

If I look at the TAL Pre-requisites for the KOMBI ECU, does it mean that I also have to flash the Pre-requisites with the same I-Step as the KOMBI?

[shawnsheridan]

Originally Posted by boldorider4

Oh, shawnsheridan, I almost forgot:

If I look at the TAL Pre-requisites for the KOMBI ECU, does it mean that I also have to flash the Pre-requisites with the same I-Step as the KOMBI?

I can't say. There is no way to know. Personally, I don't worry about any Prerequisites. I flash ECU i need to and then only is something is not working will I go back and flash any other ECU.

[boldorider4]

By the way shawnsheridan,

Is it safe to flash via HTTP for every ECU? Or is forcing UDS safer albeit slower? I didn’t use UDS for NBTevo cause it would take ages but for other modules the difference should not be dramatic.

Also, is flashing KOMBI after connecting through VIN ok? Because I know that for FEM_GW I have to connect through ZGW IP.

[shawnsheridan]

Originally Posted by boldorider4

By the way shawnsheridan,

Is it safe to flash via HTTP for every ECU? Or is forcing UDS safer albeit slower? I didn’t use UDS for NBTevo cause it would take ages but for other modules the difference should not be dramatic.

Also, is flashing KOMBI after connecting through VIN ok? Because I know that for FEM_GW I have to connect through ZGW IP.

I flash using HTTP and only if it fails will I go back and set it to UDS. Usually you can set just BTLD for UDS and keep SWFL at HTTP. I flash via VIN myself.

[boldorider4]

Originally Posted by shawnsheridan

I flash using HTTP and only if it fails will I go back and set it to UDS. Usually you can set just BTLD for UDS and keep SWFL at HTTP. I flash via VIN myself.

Cool, thanks as always! You flash via VIN also the FEM_GW?

[shawnsheridan]

Originally Posted by boldorider4

Cool, thanks as always! You flash via VIN also the FEM_GW?

Never flashed FEM_GW before.