[Nezil]

I got my LCI M2 serviced yesterday at 1,250 miles, and because I was a little worried about the dealer objecting to things I'd coded, I set everything back to default the night before I took it in.

When I got the car back, all of my presets had been lost, so clearly more than just the instrument cluster had been updated. Once I got home I started the process of putting the coding that I wanted back on, but before I made any changes, i took a full read and backup of the FA, SVT and Coding data post updates.

Once I had the new 'factory' backup, I compared this to a few things:

• A set of default coding data created by E-Sys using my updated FA and SVT - Result was exactly the same, as expected
• The original factory coding data - Quite a few changes, which surprised me
• A set of default coding data created by E-Sys using a modified version of my updated FA with 8S4 removed
• A set of default coding data created by E-Sys using a modified version of my updated FA with 8S4 removed and EU model set

Below is a list of the modules that received updates, and their version numbers before and after:

Module - Version Before - Version After
SM2 [6d] - 002 - 004
SM2 [6e] - 005 - 006
DME2 [12] - 100_001 - 105_001
AMPH [37] - 000 - 001
HU_NBT2 [63] - 028_105 - 030_168
KOMBI2 [60] - 004 - 061
REM [72] - 005 - 007
IHKA3 [78] - 014 - 016
FLE [44] - 030_001 - 040_000
ACSM [1] - 073 - 074
FEM_BODY [40] - 066_012 - 064_014

Most of the modules that were updated only had things like Coding Date, Dealer Number, Factory Number or CAF_ID changes, which I think is basically irrelevant, but a few modules had more interesting changes.

DME2 [12] had 3300 BSR-Config -> VMAX-Codierung changed from C3 to CB
HU_NBT2 [63] had two new sections that weren't present before; I'm not sure what they do
KOMBI2 [60] had three new sections that weren't present before; I'm not sure what they do
FEM_BODY [40] had a lot of changes to things related to lighting:

Section -> Sub-section: Coding Before - Coding After
3073 LaMaster1 -> LUT_BLC_FORE_X: F020_Xenon/LEDlow = 05 23 50 - UNK_PARAM_0 = 0A 32 50
3073 LaMaster1 -> LUT_BLC_FORE_Y: F020_Xenon/LEDlow = 05 14 30 - F030_F32/F33/F36/F80/F82/F83_vor_1407/Xenon = 05 19 28
3073 LaMaster1 -> LUT_BLC_TAU_P_RED_X: F020_Codierwert = 06 1D 3B 96 - F030_F30/F31/F34/F35_LED = 0A 28 50 82
3073 LaMaster1 -> LUT_BLC_TAU_P_RED_Y: F020_Xenon/LEDlow = 00 28 3C 00 - UNK_PARAM_0 = 00 1E 29 00
3073 LaMaster1 -> LUT_BLC_HOR_POS_PAR_X: F020_Codierwert = 28 2D 46 50 - UNK_PARAM_0 = 28 2D 64 6E
3073 LaMaster1 -> LUT_BLC_HOR_POS_SYM_X: F020_Codierwert = 28 2D 46 50 - F030_F30/F31/F34/F35_LED = 28 2D 64 6E
3074 LaMaster2 -> C_HBA_HOR_OFF_VEL_H: F020_Codierwert = 55 - F030_F30/F31/F34/F35_LED = 9A
3074 LaMaster2 -> C_LA_HOR_VEL_MAX: F020_Xenon_LEDlow = C8 - F030_F32/F33/F36/F80/F82/F83_vor_1403 = DD
3074 LaMaster2 -> C_HBA_HOR_VEL_SWITCH_TO_FULL_HB: F020_Codierwert = 96 - UNK_PARAM = 9A

The lighting changes surprised me, which is why I compared this to the result of what VO coding would have achieved, but indeed, the result was the same.

I don't have any take away from this, but I thought it was interesting, so I'm posting it in case anyone else is...

[horsepower_and_hounds]

But you see no relevant differences as of yet. Could they be some de-buging?

[beppeM3+123d]

Originally Posted by Nezil

I got my LCI M2 serviced yesterday at 1,250 miles, and because I was a little worried about the dealer objecting to things I'd coded, I set everything back to default the night before I took it in.

When I got the car back, all of my presets had been lost, so clearly more than just the instrument cluster had been updated. Once I got home I started the process of putting the coding that I wanted back on, but before I made any changes, i took a full read and backup of the FA, SVT and Coding data post updates.

Once I had the new 'factory' backup, I compared this to a few things:

• A set of default coding data created by E-Sys using my updated FA and SVT - Result was exactly the same, as expected
• The original factory coding data - Quite a few changes, which surprised me
• A set of default coding data created by E-Sys using a modified version of my updated FA with 8S4 removed
• A set of default coding data created by E-Sys using a modified version of my updated FA with 8S4 removed and EU model set

Below is a list of the modules that received updates, and their version numbers before and after:

Module - Version Before - Version After
SM2 [6d] - 002 - 004
SM2 [6e] - 005 - 006
DME2 [12] - 100_001 - 105_001
AMPH [37] - 000 - 001
HU_NBT2 [63] - 028_105 - 030_168
KOMBI2 [60] - 004 - 061
REM [72] - 005 - 007
IHKA3 [78] - 014 - 016
FLE [44] - 030_001 - 040_000
ACSM [1] - 073 - 074
FEM_BODY [40] - 066_012 - 064_014

Most of the modules that were updated only had things like Coding Date, Dealer Number, Factory Number or CAF_ID changes, which I think is basically irrelevant, but a few modules had more interesting changes.

DME2 [12] had 3300 BSR-Config -> VMAX-Codierung changed from C3 to CB
HU_NBT2 [63] had two new sections that weren't present before; I'm not sure what they do
KOMBI2 [60] had three new sections that weren't present before; I'm not sure what they do
FEM_BODY [40] had a lot of changes to things related to lighting:

Section -> Sub-section: Coding Before - Coding After
3073 LaMaster1 -> LUT_BLC_FORE_X: F020_Xenon/LEDlow = 05 23 50 - UNK_PARAM_0 = 0A 32 50
3073 LaMaster1 -> LUT_BLC_FORE_Y: F020_Xenon/LEDlow = 05 14 30 - F030_F32/F33/F36/F80/F82/F83_vor_1407/Xenon = 05 19 28
3073 LaMaster1 -> LUT_BLC_TAU_P_RED_X: F020_Codierwert = 06 1D 3B 96 - F030_F30/F31/F34/F35_LED = 0A 28 50 82
3073 LaMaster1 -> LUT_BLC_TAU_P_RED_Y: F020_Xenon/LEDlow = 00 28 3C 00 - UNK_PARAM_0 = 00 1E 29 00
3073 LaMaster1 -> LUT_BLC_HOR_POS_PAR_X: F020_Codierwert = 28 2D 46 50 - UNK_PARAM_0 = 28 2D 64 6E
3073 LaMaster1 -> LUT_BLC_HOR_POS_SYM_X: F020_Codierwert = 28 2D 46 50 - F030_F30/F31/F34/F35_LED = 28 2D 64 6E
3074 LaMaster2 -> C_HBA_HOR_OFF_VEL_H: F020_Codierwert = 55 - F030_F30/F31/F34/F35_LED = 9A
3074 LaMaster2 -> C_LA_HOR_VEL_MAX: F020_Xenon_LEDlow = C8 - F030_F32/F33/F36/F80/F82/F83_vor_1403 = DD
3074 LaMaster2 -> C_HBA_HOR_VEL_SWITCH_TO_FULL_HB: F020_Codierwert = 96 - UNK_PARAM = 9A

The lighting changes surprised me, which is why I compared this to the result of what VO coding would have achieved, but indeed, the result was the same.

I don't have any take away from this, but I thought it was interesting, so I'm posting it in case anyone else is...

Hi dear, can you kindly share kombi2 cafd file? I want to try to compare with pre lci to have some feature considering that the lcd part is same size and resolution...my email is gdenora@me.com I will post result here to see if is possible make these 2 coding also in the old

[cookiesowns]

Does your car have the M drivers package? The CB coding is for cars with the increased speed limiter which I believe is applied via coding and FSC code on break in service.

[Nezil]

Originally Posted by beppeM3+123d

Can you kindly share kombi2 cafd file? I want to try to compare with pre lci to have some feature considering that the lcd part is same size and resolution...my email is gdenora@me.com I will post result here to see if is possible make these 2 coding also in the old

Will do. Please remind me if I forget. PM me tomorrow if I don't send it tonight.

[Nezil]

Originally Posted by cookiesowns

Does your car have the M drivers package? The CB coding is for cars with the increased speed limiter which I believe is applied via coding and FSC code on break in service.

No it doesn't... Is it possible that the dealer removed the limit by accident? Is there any way to check?

That would be pretty cool if the limit was removed, though I don't think I'll actually ever get a chance to test it, let alone make use if it!

[Nezil]

Originally Posted by Nezil

Will do. Please remind me if I forget. PM me tomorrow if I don't send it tonight.

I had a few minutes this morning, so sent. Let me know if you need anything else.

[cookiesowns]

Originally Posted by Nezil

No it doesn't... Is it possible that the dealer removed the limit by accident? Is there any way to check?

That would be pretty cool if the limit was removed, though I don't think I'll actually ever get a chance to test it, let alone make use if it!

Can you PM me your cafd for the DME? I need to compare. Its possible I wiped my M drivers package when doing a software update. I'll dbl check the next time I throw ESYS on.