[VTENGR]

Originally Posted by Trojanlaw

No luck yet. Have even coded the FLMs to full ECE Spec.

Maybe take the car to the dealer and say you're having issues with CarPlay so they'll update your istep version to a newer one. That should put you on the same level as everyone else and probably be able to VO code w/o issues.

[Trojanlaw]

After spending more hours than I would like to admit, I think the issue actually is the most recent software. I have compared files and tried every setting imaginable and have even coded FLMs and KAFAS to full ECE spec - no luck. FYI, coding KAFAS to full ECE spec will cause problems with the early warning systems, unless you later FDL code all measurements to MPH.

I purchased the car as a CPO on 4/30. Although it was built on 11/18, the dealer installed software version 03/2020.40 when they did the CPO certification. I have confirmed that a car built on 8/18 was able to VO Code Anti-Dazzle so the age appears to be out. On the flip side, I have yet to identify a US car that has the most recent software where the Anti-Dazzle is working. As many have noted, some of our coding features no longer work after certain upgrades. I can only suspect that is what I am dealing with and why no one has been able to solve otherwise.

Accordingly, folks with this software may not be able to activate Anti-Dazzle. If you have coded previously and update to this software, I have no idea what will happen.

If someone has this software and has been successful activating it, please pm me and I will continue to evaluate. Otherwise, I am giving up for now and will just enjoy the effectiveness of the lights with the VLD activated.

Thanks to all that helped me on this project, especially VTEGNR.

[VTENGR]

Originally Posted by Trojanlaw

After spending more hours than I would like to admit, I think the issue actually is the most recent software. I have compared files and tried every setting imaginable and have even coded FLMs and KAFAS to full ECE spec - no luck. FYI, coding KAFAS to full ECE spec will cause problems with the early warning systems, unless you later FDL code all measurements to MPH.

I purchased the car as a CPO on 4/30. Although it was built on 11/18, the dealer installed software version 03/2020.40 when they did the CPO certification. I have confirmed that a car built on 8/18 was able to VO Code Anti-Dazzle so the age appears to be out. On the flip side, I have yet to identify a US car that has the most recent software where the Anti-Dazzle is working. As many have noted, some of our coding features, such as the dash logo no longer work after certain upgrades. I can only suspect that is what I am dealing with and why no one has been able to solve otherwise.

Accordingly, folks with this software may not be able to activate Anti-Dazzle. If you have coded previously and update to this software, I have no idea what will happen.

If someone has this software and has been successful activating it, please pm me and I will continue to evaluate. Otherwise, I am giving up for now and will just enjoy the effectiveness of the lights with the VLD activated.

Thanks to all that helped me on this project, especially VTEGNR.

You got it bud!

I wonder if the issue could lie with the PSdZData file. Have you checked to make sure you have the most recent one?

What's VLD?

[Trojanlaw]

VLD is Variable Light Distribution. The following are located in BDC_Body3 in 1DF8. It resulted in my lights being much more active, even without Anti-Dazzle.:

C_AFS_ECO_LEVEL_3_ENA: enable [01]
C_AFS_ENA: enable [01]
C_BLC_PRE_ENA: enable [01]
C_CLC_BLINK_ENA: enable [01]
C_CLC_CURV_V2: ECE [23]
C_CLC_CURV_V3: ECE [28]
C_CLC_EXT_ENA: enable_roundabout [01]
C_CLC_REV_ENA: enable [01]
C_HBA_GFHBA_ENA_V_HI: standard [3C]
LUT_AFS_CODRV_HOR: G05_Laser_ECE [00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 03 00 00 00 03 03 00 00 00 00 00 00 00 00 00 00]
LUT_AFS_DRV_HOR: G05_Laser_ECE [00 00 00 33 00 00 00 00 00 00 00 00 00 00 FD FD 00 00 00 FD FD 00 00 00 00 00 00 00 00 00 00]
LUT_FLC_FORWARDLIGHTING_Y: AFS [00 00 00]

I will double check psdz but it was the most up to date on April 6 when I downloaded it from Shawn. Version v.4.22.41_PSdZData_Lite. What is the latest?

[LexxM3]

See here (and follow on posts) for a Canadian member removing anti-dazzle 5AP decode with successful results on 03/2020.30: https://www.bimmerpost.com/forums/sh...php?p=26373670

Not quite Trojanlaw's 03/2020.40 and Canadian, but I can't see there being a minor version discrepancy and Canadian and US cars are identical in this presence of 5AP decode.

[LexxM3]

Originally Posted by Trojanlaw

I will double check psdz but it was the most up to date on April 6 when I downloaded it from Shawn. Version v.4.22.41_PSdZData_Lite. What is the latest?

Checking latest supported ISTEP on a particular psdzdata version is a pain as I think you pretty much have to download and install that specific psdzdata to check. You can check your own on (for example) the Connect function of your ESys installation.

However, I can tell you that 4.23.12 supports up and including 03/2020.41. Therefore, chances are really high that your 4.22.41 is too old to support 03/2020.40 that you have installed in your car.

Good lesson for all of us: second check upon failed coding should always be to check the psdzdata version (first check is the coding itself, of course).

[VTENGR]

Originally Posted by LexxM3

Checking latest supported ISTEP on a particular psdzdata version is a pain as I think you pretty much have to download and install that specific psdzdata to check. You can check your own on (for example) the Connect function of your ESys installation.

However, I can tell you that 4.23.12 supports up and including 03/2020.41. Therefore, chances are really high that your 4.22.41 is too old to support 03/2020.40 that you have installed in your car.

Good lesson for all of us: second check upon failed coding should always be to check the psdzdata version.

Where can you go to verify you have the latest and greatest PSdZData file?

[LexxM3]

Originally Posted by VTENGR

Where can you go to verify you have the latest and greatest PSdZData file?

The "usual suspects that shall remain unnamed" :-). I don't know what the protocol here is for that, but "Shawn" is usually in the loop and I think you just assumed that something you got in April would still be recent after that. But there are other sources that tend to be really quick, like that UK car forum and others. psdzdata (or more precisely minor ISTA+ versions) seem to come out fast and furious out of BMW.

[VTENGR]

Originally Posted by LexxM3

The "usual suspects that shall remain unnamed" :-). I don't know what the protocol here is for that, but "Shawn" is usually in the loop and I think you just assumed that something you got in April would still be recent after that. But there are other sources that tend to be really quick, like that UK car forum and others. psdzdata (or more precisely minor ISTA+ versions) seem to come out fast and furious out of BMW.

So just head on over to bimmerfest and ask Shawn?

[LexxM3]

Originally Posted by VTENGR

So just head on over to bimmerfest and ask Shawn?

That usually works and you do have to ask for an update if car gets updated. I am certain now that Shawn has a bot or a helper monkey running that constantly replies "PM sent" as no human could bear those requests all these years.

[Trojanlaw]

FYI I updated to 4.23.13 and no change.

I will keep searching for an answer.

[LexxM3]

Originally Posted by Trojanlaw

FYI I updated to 4.23.13 and no change.

I will keep searching for an answer.

And just to double-check, you are sure that with your updated setup there are no ECUs now remaining that were coded with the wrong psdzdata from before?

[Trojanlaw]

Yes I did.

[LexxM3]

Originally Posted by Trojanlaw

Yes I did.

Crap. Does that then just leave the very early build date and/or some kind of a weird defect as remaining theories?

Update: never mind the early build date, you seemed to have ruled that out earlier in the thread. Frustrating.

[Trojanlaw]

Still have the 03/2020.40 software theory but am checking that out further.

[LexxM3]

Originally Posted by Trojanlaw

Still have the 03/2020.40 software theory but am checking that out further.

You did notice this, however, right? https://www.bimmerpost.com/forums/sh...php?p=26373670

It's reported success on 03/2020.30, so not quite .40, but I really don't see something as big as this being a minor version change, even accidentally.

[Trojanlaw]

Did not see. Thank you.

[ifr]

I think you can now buy HBA retrospectively via Connected Drive Store (where allowed), and as such there was a technical campaign to import the KAFAS FSC in support of vehicles programmed to i-step 07/2019 and later.

Hypothesis is if you never purchased HBA/had in your FA at the time your i-step was upgraded then they would not have imported the FSC and your coding will not work.

It's a possibility. Maybe worth checking your KAFAS FSC and compare with a known good.

[LexxM3]

Originally Posted by ifr

I think you can now buy HBA retrospectively via Connected Drive Store (where allowed), and as such there was a technical campaign to import the KAFAS FSC in support of vehicles programmed to i-step 07/2019 and later.

Hypothesis is if you never purchased HBA/had in your FA at the time your i-step was upgraded then they would not have imported the FSC and your coding will not work.

It's a possibility. Maybe worth checking your KAFAS FSC and compare with a known good.

That would be very interesting if turns out to be true. It would put another notch into the not-ready column of the "BMW is nowhere near ready for non-trivial feature subscription model" debate.

[Trojanlaw]

What is my KAFAS FSC? Sorry if this is a dumb question. Moreover, can I import it?

[Trojanlaw]

That would not explain how a car produced prior to mine in the US was able get it working. That said, I would love to research this issue further. Please advise how to check.

Thanks

[ifr]

I'll check the code tomorrow.

My dealer messed up with the DSC VIP FSC as part of the 11/2019 upgrade and now I can't code that.

Kind of hard explaining to them why it needs fixing, but the point is it can also be human error.

The programming release notes explain the HBA/KAFAS issue