[ifr]

Originally Posted by 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

KAFAS HBA FSC listed. Guess you need both for anti-dazzle.

If you don't have access to ISTA, use esys:
Comfort Mode-FSC-Read VIN-Check FSC status

[Trojanlaw]

Thanks. I am out of town but will check on my car as soon as I return on Sunday and report back. This makes sense since my car received the 3/2020 software update with 5AP before I purchased it.

[Trojanlaw]

I think you nailed it.

AppID 429(0x1AD)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available
----------
AppID 336(0x150)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available

I do not have an approved FSC for either High Assist Premium or Right of way warner. This would explain why my coding doesn't work. This would also mean it shouldn't work for any US car after the 03/2020 update.

Is there a way to enter an FSC?

[ifr]

What I'm theorising is that BMW decided to sell aftermarket upgrades for certain software activated features. So they make the hardware available, and then sell the capability aftermarket, similar to the Tesla model.

The programming notes for the latest i-step state that there was a technical campaign to import an FSC code for 07/2019.x that required the FSC code to be imported for HBA. Whats not clear is if that is just standard HBA or Anti-Dazzle. It's possible that the 03/2020 i-step locks the Anti-Dazzle feature unless the FSC is installed. The same applies for 1CR remote start - can be coded but needs an FSC.

Either way, you need a premium HBA FSC, and a nice to have would be the right of way warning FSC. These have to come from BMW. Exception is NAV FSC which can be cracked, but not HBA AFAIA.

Your issue is that Anti-Dazzle is not available in your region so not sure if your dealer would provide. The alternative is to see out a 3rd party intermediary who could source one from another region. I have never done this, and don't know anyone, but I do know they frequent the cartechnology forums so maybe try enquiring there?

[Trojanlaw]

Is it possible that someone who activated anti-dazzle prior to the software update would not need the FSC code for it to continue to work? Or is it possible that VO coding prior to update resulted in one being issued? If not, I am not sure how anyone in the US with 3/2020 has working anti-dazzle.

[mandomedic122]

Originally Posted by Trojanlaw

Is it possible that someone who activated anti-dazzle prior to the software update would not need the FSC code for it to continue to work? Or is it possible that VO coding prior to update resulted in one being issued? If not, I am not sure how anyone in the US with 3/2020 has working anti-dazzle.

I too have looked for the FSC Codes as stated and have the last two missing from my X5.

My anti-dazzle lights were working like a European car before they updated me to 03/2020.58. No they hardly move, in fact they only turn off when it senses a vehicle is approaching. So it seems the update does require you to have those FSC for it to work.

BMWNA just wants to nickel and dime their customers.

Armando

[Trojanlaw]

Thanks for confirming Armando. It appears the mystery is solved. This also means that anyone in the US will lose their Anti-Dazzle as soon as they upgrade to 3/2020.40 or above.

Now the search for an FSC Code Solution!!

[LexxM3]

Originally Posted by Trojanlaw

Thanks for confirming Armando. It appears the mystery is solved. This also means that anyone in the US will lose their Anti-Dazzle as soon as they upgrade to 3/2020.40 or above.

Now the search for an FSC Code Solution!!

Wow, if this continues be confirmed and remains true, I am never updating again from 11/2019.40 until getting rid of the car (which based on this alone so far may well be earlier than previously planned).

[Trojanlaw]

Okay - Back to the drawing board. According to Shawn Sheridan:

These FSC Codes have nothing to do with GFHD (Anti Dazzle).

AppID 429 (0x1AD) - HIGH VFW - Visual Front Warning - (VFW GiveWayWarner)

AppID 336 (0x150) - HIGH WWA - Wrong Way Assist

[Trojanlaw]

Further update from Shawn -

"I know all FSC codes and none relate to anti-dazzle. No code has been added for European spec cars. FDL coding would be required."

Now I truly do not have an answer. Let me know if anyone figures it out. I have compared more files than I care to admit and have even programmed by KAFA to full Euro spec. There is a specific combo required with the Euro spec settings. I just can't figure out which ones.

JP

[ifr]

0x1B0 is definitely HBA

0x150 is described in ISTA as 'High Assist Premium', which is ambiguous.

The other FSC is irrelevant.

We could have misinterpreted what 'High assist premium' means.

Assume you have 0x1B0? If so back to the drawing board.

You might want to get ISTA+ and see if any errors are reported after VO coding.

[ifr]

Also, what you may have inadvertently done is explain why some region cars don't support coding for give way warning (stop signs and traffic light recognition) and wrong way assist (wwa).

Small comfort I'm sure

[Trojanlaw]

Your assumption is correct I do have the FSC for HBA. You are also correct that it is a small comfort.

BMW added something to the software updates from 3/2020.40 on that may now also do a region check. Curious to see if the 2021s even have 5AP listed. May not matter anymore.

[ifr]

Originally Posted by Trojanlaw

Your assumption is correct I do have the FSC for HBA. You are also correct that it is a small comfort.

BMW added something to the software updates from 3/2020.40 on that may now also do a region check. Curious to see if the 2021s even have 5AP listed. May not matter anymore.

The region locks via land masks are a more efficient way for BMW to meet regulatory compliance than using FA codes. If the car is driven to a region where the feature is allowed, then it will activate.

If that's what they have done with 03/2020 then it could be fixed in FDL coding by maxing (FFFFFFFF) the relevant land/country mask. This is how I unlocked aSLA and NHA for any region.

If that is the case then it could be good news, as an FSC requirement would have been a right pain.

Start with KAFAS VFW_ and I'll take a look for any other likely candidates in 03/2020 tomorrow. VFW is a huge mask, so could be used for all sorts, and not just gww/wwa/tlr

[Trojanlaw]

In addition to VO Coding without 5AP, changing the following files in KAFAS4 40F9 will get it to work again even with the software update:

COUNTRY_VARIATION: Europe_RC [01]
C_FLA_BS_ENTER_THRESH: Rest of world [03]
C_FLA_BS_EXIT_THRESH: Rest of world [02]
C_FLA_CC_MESSAGE_3: no_CC_message [00]
C_FLA_US_SENSITIVITY_MODE: Normal [00]

Thanks to everyone that helped solve this!!!

JP

[ifr]

Originally Posted by Trojanlaw

In addition to VO Coding without 5AP, changing the following files in KAFAS4 40F9 will get it to work again even with the software update:

COUNTRY_VARIATION: Europe_RC [01]
C_FLA_BS_ENTER_THRESH: Rest of world [03]
C_FLA_BS_EXIT_THRESH: Rest of world [02]
C_FLA_CC_MESSAGE_3: no_CC_message [00]
C_FLA_US_SENSITIVITY_MODE: Normal [00]

Thanks to everyone that helped solve this!!!

JP

Congrats mate. 10/10 for persistence

Can you narrow it down to 1 specific code or more, and I'll highlight in the HBA spreadsheet and make it public again.

Guessing it's just country_variation?

This isn't a land mask, so I'm not even 100% sure BMW have deliberately locked this.

[jeet]

Originally Posted by ifr

The region locks via land masks are a more efficient way for BMW to meet regulatory compliance than using FA codes. If the car is driven to a region where the feature is allowed, then it will activate.

If that's what they have done with 03/2020 then it could be fixed in FDL coding by maxing (FFFFFFFF) the relevant land/country mask. This is how I unlocked aSLA and NHA for any region.

If that is the case then it could be good news, as an FSC requirement would have been a right pain.

Start with KAFAS VFW_ and I'll take a look for any other likely candidates in 03/2020 tomorrow. VFW is a huge mask, so could be used for all sorts, and not just gww/wwa/tlr

Hi ifr,

Is it possible to share your Kafas file and I can compare mine to get GWW working.

Thanks
Jeet

[ifr]

Originally Posted by jeet

Hi ifr,

Is it possible to share your Kafas file and I can compare mine to get GWW working.

Thanks
Jeet

hi,

do you have the necessary FSC for GWW and WWA?

See the screenshot of KAFAS FSC above - 0x01AD for GWW, and 0x150 for WWA.

Probably wasting your time if you don't have at least the 0x01AD FSC.

WWA is practically useless.

Edit - you don't need my KAFAS ncd to figure out what coding you need. Assuming your AUSY is a car type ECE (should be), then all you have to do is modify your offline FA so that the country version is changed from 810 (oz) to 812 (GB).

In coding this will change the activation condition from 120 to 121 and assign codes accordingly.

With a GB FA and an OZ FA you can then do coding verification for each, using the same SVT, output to FWL, and compare the different folders with something like winmerge.

This assumes you are using esysx and not LP. If the latter you will probably have to output to ncd and then manually convert to FWL. Not an issue with only one ECU (40F8), but a mare when doing a full car compare. This is another reason why I always recommend esysx over LP.

[jeet]

Originally Posted by ifr

hi,

do you have the necessary FSC for GWW and WWA?

See the screenshot of KAFAS FSC above - 0x01AD for GWW, and 0x150 for WWA.

Probably wasting your time if you don't have at least the 0x01AD FSC.

WWA is practically useless.

Hi ifr,

I checked the FSC codes and it is missing so GWW not available on Aussie Cars.

AppID 429(0x1AD)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available
----------
AppID 336(0x150)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available

[ifr]

Originally Posted by jeet

Hi ifr,

I checked the FSC codes and it is missing so GWW not available on Aussie Cars.

AppID 429(0x1AD)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available
----------
AppID 336(0x150)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus not available
FSCCertStatus not available

Thought that might be the case. That's why I pulled the previous coding sheet/post. Too many support queries that couldn't be fixed in coding pointing to another issue.

Most of the codes for GWW are enabled for ECE cars anyway, and once the VFW country code is set to all it should just work.

Make a note of the coding verification process I outlined as edit above. Will save you some time in future. It can also be used to compare option changes, build changes to later i-step, etc. Very powerful for code discovery.

[ifr]

Originally Posted by mandomedic122

I too have looked for the FSC Codes as stated and have the last two missing from my X5.

My anti-dazzle lights were working like a European car before they updated me to 03/2020.58. No they hardly move, in fact they only turn off when it senses a vehicle is approaching. So it seems the update does require you to have those FSC for it to work.

BMWNA just wants to nickel and dime their customers.

Armando

When you do your testing with the new codes, can you start with the region one and work down one at a time please?

So VO Code, then change the COUNTRY_VARIATION code in KAFAS to EU, and see if that works.

The less changes required in KAFAS the better.

[mandomedic122]

Originally Posted by ifr

When you do your testing with the new codes, can you start with the region one and work down one at a time please?

So VO Code, then change the COUNTRY_VARIATION code in KAFAS to EU, and see if that works.

The less changes required in KAFAS the better.

I will code it tonight and follow your advise to see which code actually makes the change.

Armando