[valley_nomad]

Originally Posted by shawnsheridan

Except for FEM_Body, I am not aware of any of ECU's with similar issues.

But to answer your question, that is up to TokenMaster really. But it is impossible to expect to have a CAFD Mapping Tool that both a) keeps up with new CAFD changes for which no known mapping data exists outside BMW AG and b) one that also maintains backwards compatibility with all previous versions of same CAFD to support all cars.

As I wrote when Trimmed PSdZData first arrived, CAFD Mapping based on historical data was based on assumptions that over time would no longer hold true, and it was a band-aid on borrowed time. The only true solution is to use Untrimmed PSdZData, but getting ones hands on it is near impossible.

Unfortunately among all the coding I need to do, about 60% of them are in FEM_BODY. With the current issue of missing function value for mirror auto folding, will it be ok to try other coding in FEM_BODY?

In addition to the issue of FEM_BODY, as I mentioned earlier, I couldn't find C_ZSW_Aktivierunggeschwindigkeit_Funktion_low in ICM (CAFD_0000067B_002_003_139.ncd). So at least two ECUs have the issue.

Does it look like the beginning of the end for the current approach of coding? If so, it will definitely make people think twice about re-programming their cars during service.

[shawnsheridan]

Originally Posted by valley_nomad

..Does it look like the beginning of the end for the current approach of coding? If so, it will definitely make people think twice about re-programming their cars during service.

The beginning of the end was Nov 2014 beginning with F020-14-11-502. E-Sys Launcher is merely a workaround with a limited useful life.

[marcospoffo]

I have a torrent file from version 54.0
Can be? Send me a private message sent to you by e-mail.

Originally Posted by jp0202

Can anyone please point me to 54.1 PSdZData, I'm trying to find it online and failing.

[Sii770i7]

Hi Shaw,
Could you PM me link for latest E-Sys software, datafiles, and other related stuffs for coding my 2012 F30 320i?

Cheers & thank you so much

Simon

[shawnsheridan]

Originally Posted by Sii770i7

Hi Shaw,
Could you PM me link for latest E-Sys software, datafiles, and other related stuffs for coding my 2012 F30 320i?

Cheers & thank you so much

Simon

PM sent.

[dinnef30]

Does someone have a download link for Rheingold (ISTA/D) for me?

[valley_nomad]

I just noticed that the cafd_0000067b.caf.002_003_139 of 3.56.1 is different from the cafd_0000067b.caf.002_003_139 of 2.49.4. Is this normal? I thought that they would be the same file.

I was looking for the parameter for lowering the Blind Spot Detection activation speed. Two years ago with 2.49.4 I changed ICM -> 3000 Daten,F8 -> HcSwcCPar_i_Hc2_Aktiv_v_low. Now for 3.56.1 in the ICM cafd file with the same name I can not find it as the function parameter. But I did find it in the the comment of another function parameter C_ZSW_SensHellkUmgebEna:

3000 Daten (Data), F8

C_ZSW_SensHellkUmgebEna

Comment = yw130314: auscodiert yw120703: umbenennen C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low->C_ZSW_SensHellkUmgebEna yw120417: F25 30kmh yw120412: Codierwert 00,01 yw120411: umbenennen von HcSwcCPar_i_Hc2_Aktiv_v_low ->C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low,we rte von 20 auf 2 reduziert. re090904: DoorsName:HcSwcCPar_i_Hc2_Aktiv_v_low re091012: rename von L6alt-Name:Hc2_i_CPar_Aktiv_v_low

OPTIONS
false = 00
true = 01
Unknown (UNKNOWN) = 02
Unknown (UNKNOWN) = 03
Unknown (UNKNOWN) = 04
Unknown (UNKNOWN) = 05
Unknown (UNKNOWN) = 06
Unknown (UNKNOWN) = 07
Unknown (UNKNOWN) = 08
Unknown (UNKNOWN) = 09
Unknown (UNKNOWN) = 0A
Unknown (UNKNOWN) = 0B
Unknown (UNKNOWN) = 0C
Unknown (UNKNOWN) = 0D
Unknown (UNKNOWN) = 0E
Unknown (UNKNOWN) = 0F
Unknown (UNKNOWN) = 10
Unknown (UNKNOWN) = 11
Unknown (UNKNOWN) = 12
Unknown (UNKNOWN) = 13

it seems to be the one I am looking for.

[GuMiMoRo]

I have upgraded de brake front system to 340MM about an year, we're do I code this hardware upgrade?

Thanks

[shawnsheridan]

Originally Posted by valley_nomad

I just noticed that the cafd_0000067b.caf.002_003_139 of 3.56.1 is different from the cafd_0000067b.caf.002_003_139 of 2.49.4. Is this normal? I thought that they would be the same file.

Again, this is a CAFD Mapping issue. HcSwcCPar_i_Hc2_Aktiv_v_low does exist in cafd_0000067b.caf.002_003_139. It was removed beginning with cafd_0000067b.caf.002_004_082. As I previously wrote, the CAFD Mapping in E-Sys Launcher 2.x is based on the highest CAFD version in the last Untrimmed PSdZData set, which is 54.1, so it is mapping, incorrectly in this case, based on the newer CAFD. This is why cars with I-Levels <= 54.1 (F020-14-11-502) should not use newer PSdZData and E-Sys Launcher 2.x with CAFD Mapping. They should use 54.1 PSdZData and E-Sys Launcher 1.x without CAFD Mapping.

[shawnsheridan]

Originally Posted by GuMiMoRo

I have upgraded de brake front system to 340MM about an year, we're do I code this hardware upgrade?

Thanks

If comparable to BMW Sport Brake Option, I would add to FA HO-Word SPBR, and VO Code DSC.

[valley_nomad]

Originally Posted by shawnsheridan

Again, this is a CAFD Mapping issue. HcSwcCPar_i_Hc2_Aktiv_v_low does exist in cafd_0000067b.caf.002_003_139. It was removed beginning with cafd_0000067b.caf.002_004_082. As I previously wrote, the CAFD Mapping in E-Sys Launcher 2.x is based on the highest CAFD version in the last Untrimmed PSdZData set, which is 54.1, so it is mapping, incorrectly in this case, based on the newer CAFD. This is why cars with I-Levels <= 54.1 (F020-14-11-502) should not use newer PSdZData and E-Sys Launcher 2.x with CAFD Mapping. They should use 54.1 PSdZData and E-Sys Launcher 1.x without CAFD Mapping.

Do you mean that all descriptive text (including names of function parameters and comment text) I saw in the current (i.e.56.1) ICM's CAFD file cafd_0000067b.caf.002_003_139 when using NCD/CAFD tools (v 0.3.6) is actually the text from cafd_0000067b.caf.002_003_139 in 54.1? if so, then the two afd_0000067b.caf.002_003_139 files in 46.4 and 54.1 are different. I believe BMW at least changed the name of that specific function parameter for several times as described in the comment:

yw130314: auscodiert
yw120703: umbenennen (rename) C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low->C_ZSW_SensHellkUmgebEna
yw120417: F25 30kmh
yw120412: Codierwert 00,01
yw120411: umbenennen von (renaming) HcSwcCPar_i_Hc2_Aktiv_v_low -> C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low,wer te von 20 auf 2 reduziert
re090904: DoorsName (name):HcSwcCPar_i_Hc2_Aktiv_v_low
re091012: rename von L6alt-Name:Hc2_i_CPar_Aktiv_v_low

All in all, C_ZSW_SensHellkUmgebEna should replace C_ZSW_Aktivierunggeschwindigkeit_Funktion_low or HcSwcCPar_i_Hc2_Aktiv_v_low in Coding Cheat Sheet for F020-15-07-502

[shawnsheridan]

Originally Posted by valley_nomad

Do you mean that all descriptive text (including names of function parameters and comment text) I saw in the current (i.e.56.1) ICM's CAFD file cafd_0000067b.caf.002_003_139 when using NCD/CAFD tools (v 0.3.6) is actually the text from cafd_0000067b.caf.002_003_139 in 54.1? if so, then the two afd_0000067b.caf.002_003_139 files in 46.4 and 54.1 are different. I believe BMW at least changed the name of that specific function parameter for several times as described in the comment:

yw130314: auscodiert
yw120703: umbenennen (rename) C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low->C_ZSW_SensHellkUmgebEna
yw120417: F25 30kmh
yw120412: Codierwert 00,01
yw120411: umbenennen von (renaming) HcSwcCPar_i_Hc2_Aktiv_v_low -> C_ZSW_Aktivierungsgeschwindigkeit_Funktion_low,wer te von 20 auf 2 reduziert
re090904: DoorsName (name):HcSwcCPar_i_Hc2_Aktiv_v_low
re091012: rename von L6alt-Name:Hc2_i_CPar_Aktiv_v_low

All in all, C_ZSW_SensHellkUmgebEna should replace C_ZSW_Aktivierunggeschwindigkeit_Funktion_low or HcSwcCPar_i_Hc2_Aktiv_v_low in Coding Cheat Sheet for F020-15-07-502

Yes, the CAFD changed. I wrote in my post that beginning with cafd_0000067b.caf.002_004_082, the original function was removed (and replaced with new one).

[valley_nomad]

Originally Posted by shawnsheridan

Yes, the CAFD changed. I wrote in my post that beginning with cafd_0000067b.caf.002_004_082, the original function was removed (and replaced with new one).

I think I now have a bit clearer picture about this issue. It seems that the mapping for the trimmed cafd_0000067b.caf.002_003_139 in 56.1 is done with the untrimmed cafd_0000067b.caf.002_004_082 in 54.1 instead of the untrimmed cafd_0000067b.caf.002_003_139 in 54.1. This got me to believe that the file was changed while in fact it wasn't.

If this is the case, it certainly poses some issues for coding ECUs that still uses previous versions of trimmed CAFDs, e.g. my 2013 328 now has I-level of F020-15-07-502 after service in July 2015 and still uses cafd_0000067b_002_003_139 instead of cafd_0000067b_002_004_048. Not only do some function parameters' names change, but also some useful ones are not properly displayed (i.e. shown only as daten items) and some bogus ones are incorrectly added by the mapping. Hopefully the new release of tools will solve the issue.

One quick fix in this case is to just simply replace the trimmed CAFD file with the untrimmed version of that same file in previous versions (e.g. 54.1) of psdzdata, which can be done automatically with some simple PC tools if many files needs to be replaced.

[valley_nomad]

Attachment 1258454

Originally Posted by kromix

Coding a friends car ran into an issue where coding folding mirrors wasn't working, did BMW re-map the location of the ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN code?


Basically as seen in the screen shots I observed the following:

1. ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN is not under FEM_BODY:3110
2. ASP_BEIKLAPPEN_BEI_KOMFORTSCHLIESSEN was there, however, it was nicht_aktiv and there was no way to change it to aktiv with dropdown, unless you manually edited werte value from 00 to 01.

Any Ideas?

As we discussed in this thread, the problem is caused by the incorrect dynamic mapping in the current version of E-Sys Launcher. Before it is fixed by next release of E-Sys Launcher, here is the workaround:

1. For coding ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN, changing the value of PfExternalMirrorMaster_7_7_255 from 04 to 05

2. As you already found out, manually changing the value of BEIKLAPPEN_BEI_KOMFORTSCHLIESSEN from 00 to 01

Update: I thought I located the correct location of ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN by assuming that its position in ncd had not been changed -- i.e. the LSB of 8th (no. 7) byte of 3110. However, it didn't work I checked by reading back from ECU and verified that the coding is ok because that bit has been indeed set to 1. So either BMW changed the location of ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN in ncd or the updated firmware no longer has the feature...

Update 2: After some more digging (see http://f30.bimmerpost.com/forums/sho...postcount=9135), here is the real workaround (when editing CAFD_00000794_014_040_122.ncd with ESysLauncherPremium V2.1.2 Build 63):

1. For ASP_BEIKLAPPEN_BEI_KOMFORTSCHLIESSEN:
PfExternalMirrorMaster_1_1_1 -> aktiv

2. For ASP_AUSKLAPPEN_NACH_KOMFORTSCHLIESSEN:
PfExternalMirrorMaster_8_8_1 -> aktiv

[GuMiMoRo]

Originally Posted by shawnsheridan

If comparable to BMW Sport Brake Option, I would add to FA HO-Word SPBR, and VO Code DSC.

DSC VO code?

[shawnsheridan]

Originally Posted by GuMiMoRo

DSC VO code?

Yes, that is what I wrote.

[valley_nomad]

Hi Shawn, Can I get the link for 54.1 Light? One way to solve mapping issue for older CAFDs is to just simply replace the trimmed CAFD files in new psdzdata with the corresponding untrimmed CAFD files in 54.1. Thanks

[Spikey]

Shawn,

Can you hook me up once again with stuff for coding. I'm wanting to code my F30 328 (i-step = F020-13-11-502) and my friend's F20 M135 (nov 2014 build) (i-step = F20-14-11-502? i think??)

Just looking at doing some coding via esys? ... hoping the lite PSdZData will do? can you send me links for the data and esys exe, hoping to use on win10

Thanks in advance~!

[shawnsheridan]

Originally Posted by Spikey

Shawn,

Can you hook me up once again with stuff for coding. I'm wanting to code my F30 328 (i-step = F020-13-11-502) and my friend's F20 M135 (nov 2014 build) (i-step = F20-14-11-502? i think??)

Just looking at doing some coding via esys? ... hoping the lite PSdZData will do? can you send me links for the data and esys exe, hoping to use on win10

Thanks in advance~!

PM sent.

PSdZData Lite is all that is needed for coding. Win 10 works fine.

[F10 Fanatic]

Hi Shawn,

Looking to learn how to code my 2013 F10 and hoping you can direct me to the necessary files including the Psdzdata, e-sys software, launcher and other programs/files needed to get it to work. I just bought a cable and looking to tinker around and learn more about the vehicle. Thanks in advance!

[shawnsheridan]

Originally Posted by F10 Fanatic

Hi Shawn,

Looking to learn how to code my 2013 F10 and hoping you can direct me to the necessary files including the Psdzdata, e-sys software, launcher and other programs/files needed to get it to work. I just bought a cable and looking to tinker around and learn more about the vehicle. Thanks in advance!

PM sent.

[shawnsheridan]

Originally Posted by valley_nomad

Hi Shawn, Can I get the link for 54.1 Light? One way to solve mapping issue for older CAFDs is to just simply replace the trimmed CAFD files in new psdzdata with the corresponding untrimmed CAFD files in 54.1. Thanks

PM sent.