amarinos13 wrote

I've used this guide and Shawn's files to code my X3 F25 (especially the HU, since BimmerCode throws an error when trying to code it) and it has been smooth sailing every second since my first try. I did a few things, such as iD5 -> iD6Light, changed numerous settings, added SLI (along with the necessary hardware ofcourse) etc, and just wanted to say "thanks"

AAG 71 - tl_1

ACSM 01 - tl_17 ,tl_33

ATM 61 - tl_11 ,tl_27 ,tl_45

BDC_BODY 40 - tl_6 ,tl_16 ,tl_32

BDC_GW 10 - tl_4 ,tl_14

EGS 18 - tl_22 ,tl_39

FLE 43 - tl_38

FLE 44 - tl_44

FZD 56 - tl_25 ,tl_42

HC2 08 - tl_2 ,tl_3 ,tl_13 ,tl_30

HKFM2 0D - tl_12 ,tl_28 ,tl_46

HU_NBT2 63 - tl_8 ,tl_20 ,tl_36 ,tl_29

ICAM 06 - tl_9 ,tl_21 ,tl_37

KAFAS2 5D - tl_10 ,tl_23 ,tl_40

PMA2 2C - tl_24 ,tl_41

RSE_HIGH_NBT2 26 - tl_5 ,tl_15 ,tl_31

SM2 6E - tl_19 ,tl_35

SM2 6D - tl_26 ,tl_43

ZBE4 67 - tl_7 ,tl_18 ,tl_34

nholmes wrote

Hey all, first time coding my US 2018 F15 with ESYS and I'm just trying to first flash my AAG/AHM module to my car (I bought it used on ebay) and then add K235 to the SALAPA-Element so my car will see and use the reflashed towing module. All of the hardware is installed and iDrive is giving me the "tow lighting error" as expected now that the wiring harness and module is installed.

I'm currently running SYS 3.35.3 & Plus3.8.1 with FULL PSdZData for reference.

I followed the E-Sys - Flashing ECU Guide v.1.0.1 and got stuck on step 15 because my car has completely different ECUs. The guide is asking for HU_CIC, CMB_MEDIA, KOMBI and ZGW but because my car is different ECU architecture, I wasn't sure what to do next. Here's what ESYS shows for my car:

AAG 71 - tl_1

ACSM 01 - tl_17 ,tl_33

ATM 61 - tl_11 ,tl_27 ,tl_45

BDC_BODY 40 - tl_6 ,tl_16 ,tl_32

BDC_GW 10 - tl_4 ,tl_14

EGS 18 - tl_22 ,tl_39

FLE 43 - tl_38

FLE 44 - tl_44

FZD 56 - tl_25 ,tl_42

HC2 08 - tl_2 ,tl_3 ,tl_13 ,tl_30

HKFM2 0D - tl_12 ,tl_28 ,tl_46

HU_NBT2 63 - tl_8 ,tl_20 ,tl_36 ,tl_29

ICAM 06 - tl_9 ,tl_21 ,tl_37

KAFAS2 5D - tl_10 ,tl_23 ,tl_40

PMA2 2C - tl_24 ,tl_41

RSE_HIGH_NBT2 26 - tl_5 ,tl_15 ,tl_31

SM2 6E - tl_19 ,tl_35

SM2 6D - tl_26 ,tl_43

ZBE4 67 - tl_7 ,tl_18 ,tl_34

I'm very paranoid about bricking my car so I decided to post in here to ask for advice.

shawnsheridan wrote

For your car, AAG, BDC_BODY, DSC2, ICM, FZD, ICAM, PMA2, DKOMBI, and HU_NBT2.

AAG 71 - tl_1

ACSM 01 - tl_17 ,tl_33

ATM 61 - tl_11 ,tl_27 ,tl_45

BDC_BODY 40 - tl_6 ,tl_16 ,tl_32

BDC_GW 10 - tl_4 ,tl_14

EGS 18 - tl_22 ,tl_39

FLE 43 - tl_38

FLE 44 - tl_44

FZD 56 - tl_25 ,tl_42

HC2 08 - tl_2 ,tl_3 ,tl_13 ,tl_30

HKFM2 0D - tl_12 ,tl_28 ,tl_46

HU_NBT2 63 - tl_8 ,tl_20 ,tl_36 ,tl_29

ICAM 06 - tl_9 ,tl_21 ,tl_37

KAFAS2 5D - tl_10 ,tl_23 ,tl_40

PMA2 2C - tl_24 ,tl_41

RSE_HIGH_NBT2 26 - tl_5 ,tl_15 ,tl_31

SM2 6E - tl_19 ,tl_35

SM2 6D - tl_26 ,tl_43

ZBE4 67 - tl_7 ,tl_18 ,tl_34

nholmes wrote

Based on the list generated by ESYS and your list, my car appears to be missing

DSC2
ICM
DKOMBI

AAG 71 - tl_1

ACSM 01 - tl_17 ,tl_33

ATM 61 - tl_11 ,tl_27 ,tl_45

BDC_BODY 40 - tl_6 ,tl_16 ,tl_32

BDC_GW 10 - tl_4 ,tl_14

EGS 18 - tl_22 ,tl_39

FLE 43 - tl_38

FLE 44 - tl_44

FZD 56 - tl_25 ,tl_42

HC2 08 - tl_2 ,tl_3 ,tl_13 ,tl_30

HKFM2 0D - tl_12 ,tl_28 ,tl_46

HU_NBT2 63 - tl_8 ,tl_20 ,tl_36 ,tl_29

ICAM 06 - tl_9 ,tl_21 ,tl_37

KAFAS2 5D - tl_10 ,tl_23 ,tl_40

PMA2 2C - tl_24 ,tl_41

RSE_HIGH_NBT2 26 - tl_5 ,tl_15 ,tl_31

SM2 6E - tl_19 ,tl_35

SM2 6D - tl_26 ,tl_43

ZBE4 67 - tl_7 ,tl_18 ,tl_34

Is that a problem?

nholmes wrote

nholmes wrote

Sorry, I should clarify that in my ECU ID Base window, I do not see those options when attempting to complete step 15 in the E-Sys - Flashing ECU Guide v.1.0.1.pdf

I was going to check the appropriate boxes as called out in the .pdf and noticed they were missing.

Also, is this the best approach for this? I just want to flash my module for my car and then add K235 to the SALAPA-Element.

I'm curious if what I'm doing is even the correct or best approach to do this so it's the least invasive as possible.

Do I need to update the I-Step dates and flash all of these modules?

Apologies if there's something I'm not understanding with flashing and this process, this is all new to me and all of the software is pretty overwhelming for something I'm going to do once so I can start towing with my car.

I won't be coding in the future if I can help it

shawnsheridan wrote

They are not in your Flash TAL and they do not have any newer firmware files in your psdzdata than what they already have.

I don't think you need to flash anything. I would add K235 to the SALAPA-Element, then load the modified FA into the coding module and inject CAFD into AAG and VO Code it:

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Left-Click on AAG => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown (bottom one) => Select OK => Right-Click on AAG (the ECU itself not the underlying CAFD) => Select CODE.

Then I would VO all the other ECU's I listed:

Using the same modified FA, Right-Click on each ECU (the ECU itself not the underlying CAFD) => Select CODE.

nholmes wrote

Okay, I'll see if I'm smart enough to figure this out and then report back

I appreciate it

It's hard for me when information is scattered across the internet and various docs reference different software versions or are for different platforms, etc so as soon as I hit something that deviates from what's expected, I freeze haha

shawnsheridan wrote

nholmes wrote

Sorry, I should clarify that in my ECU ID Base window, I do not see those options when attempting to complete step 15 in the E-Sys - Flashing ECU Guide v.1.0.1.pdf

I was going to check the appropriate boxes as called out in the .pdf and noticed they were missing.

Also, is this the best approach for this? I just want to flash my module for my car and then add K235 to the SALAPA-Element.

I'm curious if what I'm doing is even the correct or best approach to do this so it's the least invasive as possible.

Do I need to update the I-Step dates and flash all of these modules?

Apologies if there's something I'm not understanding with flashing and this process, this is all new to me and all of the software is pretty overwhelming for something I'm going to do once so I can start towing with my car.

I won't be coding in the future if I can help it

They are not in your Flash TAL and they do not have any newer firmware files in your psdzdata than what they already have.

I don't think you need to flash anything. I would add K235 to the SALAPA-Element, then load the modified FA into the coding module and inject CAFD into AAG and VO Code it:

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Left-Click on AAG => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown (bottom one) => Select OK => Right-Click on AAG (the ECU itself not the underlying CAFD) => Select CODE.

Then I would VO all the other ECU's I listed:

Using the same modified FA, Right-Click on each ECU (the ECU itself not the underlying CAFD) => Select CODE.

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Left-Click on AAG => Click on "Detect CAF for SWE"

nholmes wrote

shawnsheridan wrote

They are not in your Flash TAL and they do not have any newer firmware files in your psdzdata than what they already have.

I don't think you need to flash anything. I would add K235 to the SALAPA-Element, then load the modified FA into the coding module and inject CAFD into AAG and VO Code it:

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Left-Click on AAG => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown (bottom one) => Select OK => Right-Click on AAG (the ECU itself not the underlying CAFD) => Select CODE.

Then I would VO all the other ECU's I listed:

Using the same modified FA, Right-Click on each ECU (the ECU itself not the underlying CAFD) => Select CODE.

I'm busy M-F so I can only chip away at this project on the weekends.
Okay so I got as far as

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Left-Click on AAG => Click on "Detect CAF for SWE"

and then I get this error:


This is where I was trying to do all of this:


Wow the forums are drastically different from last week lol

Anyway, I did confirm I have the full version of the psdzdata, do I need to mess with the i-step target?

1. On ID Base Row for HU_CIC, CMB_MEDIA, KOMBI and ZGWcheck the boxes in blFlash, swDeploy, cdDeploy, and ibaDeploy (please see Appendix C) columns.16.Press Check software availability(this, among other, ensures that you have the correct PSdZdata and the FULL version of them)

Sorry, I should clarify that in my ECU ID Base window, I do not see those options when attempting to complete step 15 in the E-Sys - Flashing ECU Guide v.1.0.1.pdf

AAG, BDC_BODY, DSC2, ICM, FZD, ICAM, PMA2, DKOMBI, HU_NBT2 and HC2.

They are not in your Flash TAL and they do not have any newer firmware files in your psdzdata than what they already have.

nholmes wrote

Okay, so we're back to this part?

1. On ID Base Row for HU_CIC, CMB_MEDIA, KOMBI and ZGWcheck the boxes in blFlash, swDeploy, cdDeploy, and ibaDeploy (please see Appendix C) columns.16.Press Check software availability(this, among other, ensures that you have the correct PSdZdata and the FULL version of them)

Sorry, I should clarify that in my ECU ID Base window, I do not see those options when attempting to complete step 15 in the E-Sys - Flashing ECU Guide v.1.0.1.pdf

AAG, BDC_BODY, DSC2, ICM, FZD, ICAM, PMA2, DKOMBI, HU_NBT2 and HC2.

They are not in your Flash TAL and they do not have any newer firmware files in your psdzdata than what they already have.

I'll go through this part again from earlier with your comments. Appreciate the help! Still trying to grok all of this.

shawnsheridan wrote

Just flash AAG, nothing more.

nholmes wrote

shawnsheridan wrote

Just flash AAG, nothing more.

Okay, so I went through the guide again and it looks like the AAG boxes are greyed out and I cannot select them to flash them?


Oh wait, do I have to select it in the ALL column first?