BMW Coding Thread

[MattBianco]

The little red light, if for fog, would usually be on the left tail light in LHD cars. They are not illegal, but BMW for each market chooses either fog or to instead have that feature where the lights get really bright if you brake hard. You cannot have both features simultaneously.

I believe to get them to behave as fog involves both coding, and a new switch. That said, there are some threads about hacking the switch. Sorry....cannot point to them now.

[opasha]

Originally Posted by MattBianco

The little red light, if for fog, would usually be on the left tail light in LHD cars. They are not illegal, but BMW for each market chooses either fog or to instead have that feature where the lights get really bright if you brake hard. You cannot have both features simultaneously.

I believe to get them to behave as fog involves both coding, and a new switch. That said, there are some threads about hacking the switch. Sorry....cannot point to them now.

Ah, good to know. Thanks for the clarification, Niko .

[CatFlap]

Originally Posted by opasha

@skalberti checked and said they are in fact very different in regards to the part numbers. I compared my 50i US to the Europe M50D right hand drive.

50i: http://www.realoem.com/bmw/showparts...78&hg=63&fg=05

M50D: http://www.realoem.com/bmw/showparts...78&hg=63&fg=05

This is not surprising to me because the airbags are the same way. I even looked and the M-Sport steering wheel has an extra white plug for the Euro airbag as opposed to the single plug for US airbag.

See attached pictures of the labels on my EEC headlamps, the numbers / decoded barcodes (7003080046052914B0108 / 741631501) don't bear any resemblance to the BMW part numbers on realoem.com though.

[opasha]

Originally Posted by CatFlap

See attached pictures of the labels on my EEC headlamps, the numbers / decoded barcodes (7003080046052914B0108 / 741631501) don't bear any resemblance to the BMW part numbers on realoem.com though.

That's really strange. Hmm... leave it to BMW to make things harder for no reason.

[Hokie 335i]

So I removed 5AP and 8S4 from the FA and coded KAFAS2, BDC_BODY, LHM, and TMS in order to get the Variable Light Distribution. I then coded quite a bit of FDL coding. Now I see conflicting information where it says to do this (remove 5AP and 8S4), but also says you only need to remove 8S4 and code BDC body. What I want to know is if I need to add back in 5AP and if so what I would need to VO code again? I'm really hoping I don't need to do any more VO coding as it'll wipe all of my FDL coding, correct?

[opasha]

Originally Posted by Hokie 335i

So I removed 5AP and 8S4 from the FA and coded KAFAS2, BDC_BODY, LHM, and TMS in order to get the Variable Light Distribution. I then coded quite a bit of FDL coding. Now I see conflicting information where it says to do this (remove 5AP and 8S4), but also says you only need to remove 8S4 and code BDC body. What I want to know is if I need to add back in 5AP and if so what I would need to VO code again? I'm really hoping I don't need to do any more VO coding as it'll wipe all of my FDL coding, correct?

From what I know, 5AP deals with Anti-Dazzle feature only, so you may have to do BDC_Body for this as well. However, do this first. Add 5AP back to your FA, then VO Code KAFAS2, LHM, and TMS only. See if your anti-dazzle goes away. Just redo the same tests you've done by driving with someone in front of you or something similar in a back road to make sure it is working correctly (not activating and blinding someone). If it is not, then obviously you need to VO Code BDC_Body as well.

For 8S4 (strictly for VLD), BDC_Body is the only thing you must VO Code. I have researched this extensively and found that LED and Bi-Xenon act the same way for this feature. If anyone has further information, feel free to correct me.

Also, any time you VO Code a specific ECU folder, you will lose all fdl coding you have done in that specific ECU folder only.

[skalberti]

Originally Posted by CatFlap

See attached pictures of the labels on my EEC headlamps, the numbers / decoded barcodes (7003080046052914B0108 / 741631501) don't bear any resemblance to the BMW part numbers on realoem.com though.

The numbers on my headlights are different than yours CatFlap

[Hokie 335i]

Originally Posted by opasha

From what I know, 5AP deals with Anti-Dazzle feature only, so you may have to do BDC_Body for this as well. However, do this first. Add 5AP back to your FA, then VO Code KAFAS2, LHM, and TMS only. See if your anti-dazzle goes away. Just redo the same tests you've done by driving with someone in front of you or something similar in a back road to make sure it is working correctly (not activating and blinding someone). If it is not, then obviously you need to VO Code BDC_Body as well.

For 8S4 (strictly for VLD), BDC_Body is the only thing you must VO Code. I have researched this extensively and found that LED and Bi-Xenon act the same way for this feature. If anyone has further information, feel free to correct me.

Also, any time you VO Code a specific ECU folder, you will lose all fdl coding you have done in that specific ECU folder only.

So I've never actually had a chance to test the Anti Dazzle, just coded it. (not a lot of opportunities in DC) I guess adding in 5AP and VO coding KAFAS2, LHM, and TMS isn't a big deal as it won't wipe any of my FDL coding, but BDC_Body would be a huge PITA. Wishing I had never even tried to code the Anti Dazzle.

[opasha]

Originally Posted by Hokie 335i

So I've never actually had a chance to test the Anti Dazzle, just coded it. (not a lot of opportunities in DC) I guess adding in 5AP and VO coding KAFAS2, LHM, and TMS isn't a big deal as it won't wipe any of my FDL coding, but BDC_Body would be a huge PITA. Wishing I had never even tried to code the Anti Dazzle.

Yeah, that's why I have in the OP that the Anti-Dazzle currently doesn't work. I might as well remove it because too many people seem to not read the OP.

I've recoded BDC_Body about 5 times already, so I know how you feel, lol .

[Hang0ver]

@opasha @skalberti @shawnsheridian

does anyone know what module in F15 is equal to REM in F30?

I'm trying to find out how to enable all cameras in all speeds and I have codes for F30 from its cheat sheet

[r33_RGSport]

Originally Posted by Hang0ver

@opasha @skalberti shawnsheridian

does anyone know what module in F15 is equal to REM in F30?

I'm trying to find out how to enable all cameras in all speeds and I have codes for F30 from its cheat sheet

Try to search in BCD_BODY.
F15 uses 1 big module, the BCD_BODY, while other F series are separated into smaller modules.

[skalberti]

F30 uses FEM_BODY if I'm not mistaken.

[opasha]

Originally Posted by skalberti

F30 uses FEM_BODY if I'm not mistaken.

You are correct.

@Hang0ver - For F15, BDC_BODY encompasses REM, FEM_BODY, and CAS.

[Hang0ver]

thanks guys. will give a look at it.

[Hang0ver]

@opasha @skalberti @r33

so, i have been going through these for a while trying to find out .. finally able to figure out where these live.

As per F30 coding, we need to configure below values in REM.

V_SCHWELLE_1 werte = FF
V_SCHWELLE_2 werte = FF
D_SCHWELLE_1 werte = FF
D_SCHWELLE_2 werte = FF

I did a search on each CAFD and found that these are now located in PDC under 300D(PKM) section.. atleast for me. I need to code this and test it out. Will report back.

However, I didn't find codes for Front Panoramic camera in F30. So, I was digging through different modules and finally found some in iCAM module.

There is one config called FV Panoramic Viewport in 3007 section with below comment

Kommentar=- Update the Camera Banding Filter value to 50.
- Rename the members from activationSpeedForward_kmh and activationSpeedBackward_kmh to deactivationSpeed_kmh and reactivationSpeed respectively.
- Update the deactivationSpeed_kmh to 3.6 and change the type to Float for both CTA-F and CTA-R.

Just want to get your thoughts on it.

I know these cameras coding is useless, but I just want to find something new and which is kind of fun

[skalberti]

The camera values listed are in icam and another ECU I believe it's FZL or FZH. I'd have to go back and look for sure. I'm just going off the top of my head, and givin my track record I wouldn't trust that!

[opasha]

Originally Posted by Hang0ver

@opasha @skalberti @r33

so, i have been going through these for a while trying to find out .. finally able to figure out where these live.

As per F30 coding, we need to configure below values in REM.

V_SCHWELLE_1 werte = FF
V_SCHWELLE_2 werte = FF
D_SCHWELLE_1 werte = FF
D_SCHWELLE_2 werte = FF

I did a search on each CAFD and found that these are now located in PDC under 300D(PKM) section.. atleast for me. I need to code this and test it out. Will report back.

However, I didn't find codes for Front Panoramic camera in F30. So, I was digging through different modules and finally found some in iCAM module.

There is one config called FV Panoramic Viewport in 3007 section with below comment

Kommentar=- Update the Camera Banding Filter value to 50.
- Rename the members from activationSpeedForward_kmh and activationSpeedBackward_kmh to deactivationSpeed_kmh and reactivationSpeed respectively.
- Update the deactivationSpeed_kmh to 3.6 and change the type to Float for both CTA-F and CTA-R.

Just want to get your thoughts on it.

I know these cameras are useless, but I just want to find something new and which is kind of fun

That's awesome. I wasn't able to find V_SCHWELLE_1 werte = FF, V_SCHWELLE_2 werte = FF, D_SCHWELLE_1 werte = FF,D_SCHWELLE_2 werte = FF in the BDC_Body where I looked for them a while ago. I wonder what sort of codes are within the whole PDC folder since no one seems to comment on them. If your cameras get activated, that would be a very cool feature to have! Thanks for your efforts and keep us posted, my friend .

[Hang0ver]

Originally Posted by skalberti

The camera values listed are in icam and another ECU I believe it's FZL or FZH. I'd have to go back and look for sure. I'm just going off the top of my head, and givin my track record I wouldn't trust that!

let me know what you find.

Originally Posted by opasha

That's awesome. I wasn't able to find V_SCHWELLE_1 werte = FF, V_SCHWELLE_2 werte = FF, D_SCHWELLE_1 werte = FF,D_SCHWELLE_2 werte = FF in the BDC_Body where I looked for them a while ago. I wonder what sort of codes are within the whole PDC folder since no one seems to comment on them. If your cameras get activated, that would be a very cool feature to have! Thanks for your efforts and keep us posted, my friend .

PDC ofcourse as it stands for, Park Distance Control has all configs related to how it warns, how it detects, how the lines appear, how they move, etc.. so its pretty much related to all the sensors and cameras on side and back..

I think the iCAM is pretty much the front and side camera speed settings.

[hyde]

Is the blind spot monitoring speed independent from lane departure & collusion warning speeds?

[opasha]

Originally Posted by hyde

Is the blind spot monitoring speed independent from lane departure & collusion warning speeds?

I believe so, but @skalberti feel free to explain further .

[skalberti]

Originally Posted by hyde

Is the blind spot monitoring speed independent from lane departure & collusion warning speeds?

Yes it's independent and its located in the ICM ECU.

[hyde]

Originally Posted by skalberti

Yes it's independent and its located in the ICM ECU.

Thanks, do they all have the same minimum like blind spot throwing error at 10?