[bradsm87]

After region change coding, I get KAFAS 800AD0: No enabling code

Everything in the car seems to work like assisted driving etc. I have not tried driving at night yet.

The exact same KAFAS4 f5сs are still all showing as accepted after the changes:

AppID 432(0x1B0) - HBA High-Beam assi5тдnt
AppID 333(0x14D) - LDW Lane deрдятure warning
AppID 334(0x14E) - SLI Speed Limit Info
AppID 336(0x150) - High assist premium

The coding changes were minimal. I just VO coded it with a slightly modified FA, only changing 3 minor regional codes. The SVT Toolbox screenshot attached shows the coding differences.

Has anybody seen something like this before? Any ideas what to try? Maybe disconnect and reconnect the car battery?

It seems something similar happened here: https://cartechnology.co.uk/showthread.php?tid=72255

Maybe I should VO code it again with the original FA and see if it goes away, then see how many of the parameters I can FDL code without the fault coming back?

   

[dasi]

After region change coding, I get KAFAS 800AD0: No enabling code

Everything in the car seems to work like assisted driving etc. I have not tried driving at night yet.

The exact same KAFAS4 f5сs are still all showing as accepted after the changes:

AppID 432(0x1B0) - HBA High-Beam assi5тдnt
AppID 333(0x14D) - LDW Lane deрдятure warning
AppID 334(0x14E) - SLI Speed Limit Info
AppID 336(0x150) - High assist premium

The coding changes were minimal. I just VO coded it with a slightly modified FA, only changing 3 minor regional codes. The SVT Toolbox screenshot attached shows the coding differences.

Has anybody seen something like this before? Any ideas what to try? Maybe disconnect and reconnect the car battery?

It seems something similar happened here: https://cartechnology.co.uk/showthread.php?tid=72255

Maybe I should VO code it again with the original FA and see if it goes away, then see how many of the parameters I can FDL code without the fault coming back?

There's really clear answer in your post. You answered yourself with changes between FA. Hint, it's WWA

[bradsm87]

There's really clear answer in your post. You answered yourself with changes between FA. Hint, it's WWA

I disabled wrong way assi5тдnt as per the default coding for my Country. Are you saying DISABLING features via coding, can trigger this f5с fault? Have you seen this before to know it's the WWA and not the Country coding or BCM coding?

One noteworthy thing is that Australian cars don't have this f5с accepted:

AppID 336(0x150) - High assist premium

Do we know which specific option codes call for the 0x150 high assist premium f5с?

I'm starting to wonder if this fault can be triggered not just from missing f5сs, but also from accepted f5сs for features that aren't enabled.

[dasi]

yes, I did seen this before.

[bradsm87]

yes, I did seen this before.

So can I just re-enable WWA on the KAFAS only without enabling it on the BDC, just to get rid of this error?

[dasi]

yes, try it please.

[marcdts]

After region change coding, I get KAFAS 800AD0: No enabling code

Everything in the car seems to work like assisted driving etc. I have not tried driving at night yet.

The exact same KAFAS4 f5сs are still all showing as accepted after the changes:

AppID 432(0x1B0) - HBA High-Beam assi5тдnt
AppID 333(0x14D) - LDW Lane deрдятure warning
AppID 334(0x14E) - SLI Speed Limit Info
AppID 336(0x150) - High assist premium

The coding changes were minimal. I just VO coded it with a slightly modified FA, only changing 3 minor regional codes. The SVT Toolbox screenshot attached shows the coding differences.

Has anybody seen something like this before? Any ideas what to try? Maybe disconnect and reconnect the car battery?

It seems something similar happened here: https://cartechnology.co.uk/showthread.php?tid=72255

Maybe I should VO code it again with the original FA and see if it goes away, then see how many of the parameters I can FDL code without the fault coming back?

This happens when trying wrong  to code reg change on KAFAS4

[bradsm87]

This happens when trying wrong  to code reg change on KAFAS4

What do you mean sorry?

[DEJMIEN]

VO coding for Kafas4 and BDC3 is always a bad idea when performing a market conversion, due to the issues that will inevitably appear later. IMHO, when performing a market conversion, it is better to do individual FDL coding rather than VO coding the entire vehicle.

[bradsm87]

VO coding for Kafas4 and BDC3 is always a bad idea when performing a market conversion, due to the issues that will inevitably appear later. IMHO, when performing a market conversion, it is better to do individual FDL coding rather than VO coding the entire vehicle.

I carefully researched it and checked what should be able to be VO coded and what needed FDL coding.

I FDL coded the ACSM and BDC_BODY modules because there are differences in airbags and seat occupancy sensors in the car that needed to stay and a couple of small antenna things in the BDC.

There were a lot of coding changes in some of the modules so VO coding was much easier for them.

I just tested the adaptive headlights including anti-dazzle and literally everything works. This KAFAS fault presence when checking for faults in i5тд is the only issue. It can stay forever if I need but I’m more interested to fїж it due to curiosity.