G05
BMW X5
8.1KVIEWS
21REPLIES
6APPRECIATES
11ACTIVE PEOPLE
04-13-2026LAST POST
11-17-2020
Hi All - So I finally took my X5 in for its first scheduled service appointment. While taking it in, I also let the service advisor know of the error I continue to receive when ever I try to engage the full autonomous driving mode while in stop and go traffic on the highway (via Assisted Driving Plus). I showed him the error message (below). Net-Net, he said that the car had to be recoded, because the module that controls the Drivers Attention Camera Module was changed/altered. Essentially, something I had coded via the Bimmercode app caused this feature to disable. I suspect any coding tied to the drivers attention camera caused the coding error. The only things I coded that could be tied to this would be:

1 - Removing the legal disclaimers (cameras, startup, etc) OR
2 - Video In Motion

Only other things I've coded were M logo on start-up, rear hatch, mirrors, no honk when car locked while running, etc ... none of which should have anything to do with the drivers attention camera.

Just checking in to see if anyone knows definitively what coding option would have cause the Drivers Attention Camera module to change + to warn others that this could happen if you have Assisted Driving Plus. I want to re-code all of the other features, so hoping someone can shed light on this.

Appreciate it.
An image attached to this post, provided by the poster
11-17-2020
HU_MGU\LENKASSISTENT_DCS must be gen1/aktiv
SASx\C_HOO_Vorhanden should be standby or nostandby, but not 'nicht_vorhanden'

Don't activate LENKASSISTENT_PLUS in HU_MGU or the camera will deactivate

You cant code SAS with BC so not likely to be that code

Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?
11-18-2020
ifr wrote
HU_MGU\LENKASSISTENT_DCS must be gen1/aktiv
SASx\C_HOO_Vorhanden should be standby or nostandby, but not 'nicht_vorhanden'

Don't activate LENKASSISTENT_PLUS in HU_MGU or the camera will deactivate

You cant code SAS with BC so not likely to be that code

Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?
ifr wrote
HU_MGU\LENKASSISTENT_DCS must be gen1/aktiv
SASx\C_HOO_Vorhanden should be standby or nostandby, but not 'nicht_vorhanden'

Don't activate LENKASSISTENT_PLUS in HU_MGU or the camera will deactivate

You cant code SAS with BC so not likely to be that code

Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?
I appreciate the response. I'm using BimmerCode via iOS app, feels like your reco's would only be an option via eSys? Or perhaps in BimmerCode expert mode?

Any idea if any of the feature options in BimmerCode would directly alter any of those modules you referenced? I basically just want to avoid them if they do, while coding the others.
11-18-2020
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
11-18-2020
Maybe weird and a little bit offtopic but is it possible to Enable this feature in Europe ?
11-18-2020
xigolle wrote
Maybe weird and a little bit offtopic but is it possible to Enable this feature in Europe ?
I haven't figured out how to do it.

The feature can be enabled in coding, but there is a hard region block based on the cars gps location that prevents it from activating.

It's also a nightmare to test for obvious reasons.
11-18-2020
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
Yes, I have it enabled.

It was working for some time... and then I did some coding via BC, and it started giving me the error. I'm only going by the dealer stating that the module for the camera had changed.
An image attached to this post, provided by the poster
11-18-2020
martinf79 wrote
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
Yes, I have it enabled.

It was working for some time... and then I did some coding via BC, and it started giving me the error. I'm only going by the dealer stating that the module for the camera had changed.
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
I just think there may be some contingencies on the legal disclaimers and/or video in motion that require the camera to be disabled in order for them to work... that's the only thing (ie if condition A is met, disable B)? Or does it not work that way?
11-18-2020
martinf79 wrote
martinf79 wrote
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
Yes, I have it enabled.

It was working for some time... and then I did some coding via BC, and it started giving me the error. I'm only going by the dealer stating that the module for the camera had changed.
ifr wrote
The SAS settings would only be applicable with esys, the HU_MGU would need BC in expert mode.

I don't use BC but I find it highly unlikely that any of the stock coding would break the DAC. Did you check the idrive settings I mentioned?

"Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?"

The actual Driver Camera configuration ECU is DCS01 (475C) but I can't see BC touching that?
I just think there may be some contingencies on the legal disclaimers and/or video in motion that require the camera to be disabled in order for them to work... that's the only thing (ie if condition A is met, disable B)? Or does it not work that way?
Lots of people have turned on video in motion and turned off disclaimers with no ill side effects whatsoever. Using both Bimmercode and direct ESys coding. In fact, I think this is the first assertion ever that there was a DAC effect. It may be that coding changed, but at this point it is overwhelmingly likely that was due to a BMW bug than Bimmercode. The dealer could easily be just taking a flying guess since updating fixed it — it's not like service techs have a culture or any motivation to get to actual root causes.
11-18-2020
Yep unlikely to be coding.

Of course you could back out your BC changes to stock, and see if the issue persists.
11-18-2020
Thanks all ... I still don't actually know if Assisted Driving Plus now works, as its hard to get the conditions right to test it.
11-19-2020
ifr wrote
I haven't figured out how to do it.

The feature can be enabled in coding, but there is a hard region block based on the cars gps location that prevents it from activating.

It's also a nightmare to test for obvious reasons.
Aaaah to bad if you haven't found out how to get it working nobody did I think :)
Hopefully this comes to europe one day because my previous car actually had this kind of functionality.
So I would find it strange that it would be a "legal thing".
11-19-2020
xigolle wrote
Aaaah to bad if you haven't found out how to get it working nobody did I think :)
Hopefully this comes to europe one day because my previous car actually had this kind of functionality.
So I would find it strange that it would be a "legal thing".
It's definitely a legal block for the EU.
Which of your previous cars had the functionality? Even Tesla's force hands on every X seconds in the EU.
11-20-2020
ifr wrote
It's definitely a legal block for the EU.
Which of your previous cars had the functionality? Even Tesla's force hands on every X seconds in the EU.
My previous Audi A5 Sportback from 2018.
It has a feature call traffic jam assist and is actived under the 65km.
It still prompts you to keep your hands on the wheel after an extended period of time.
But instead of after 30-40s it can easily take a few minutes until you need to juggle the wheel.
In this mode it will more actively steer/control the car.
As also you can keep your hands longer of the steering wheel.
Which sounds like the same function as what BMW is offering in the US.
Here is a piece of the manual:
5pddSMX.png
11-20-2020
xigolle wrote
My previous Audi A5 Sportback from 2018.
It has a feature call traffic jam assist and is actived under the 65km.
It still prompts you to keep your hands on the wheel after an extended period of time.
But instead of after 30-40s it can easily take a few minutes until you need to juggle the wheel.
In this mode it will more actively steer/control the car.
As also you can keep your hands longer of the steering wheel.
Thanks.

No it's not the same and thats the rub. The BMW system will drive for hours/indefinitely without any user interaction on either the steering wheel or pedals as long as the speed remains under 40mph.

The Audi system may have increased tolerances and length of time before engagement, but the user has to take control at set intervals. Indeed it's encouraged that the user keeps their hands on the wheel at all times - a note to the regulators no doubt ;)
With the BMW eTJA the user does not have to take control.

There are talks in the UK to change legislation to allow indefinite hands-free up to 70mph, which would unblock this and some future features.
11-20-2020
ifr wrote
Thanks.

No it's not the same and thats the rub. The BMW system will drive for hours/indefinitely without any user interaction on either the steering wheel or pedals as long as the speed remains under 40mph.

The Audi system may have increased tolerances and length of time before engagement, but the user has to take control at set intervals. Indeed it's encouraged that the user keeps their hands on the wheel at all times - a note to the regulators no doubt ;)
With the BMW eTJA the user does not have to take control.

There are talks in the UK to change legislation to allow indefinite hands-free up to 70mph, which would unblock this and some future features.
I certainly wouldn’t feel comfortable not having my hands on an Audi steering wheel....I’ve got a Q8 and it’s steering assistant is pretty ropey....bend management is several generations behind BMW’s....it gets itself in to trouble (ie mid bend) and then hands back control...BMW is better at anticipating a layout beyond its capability. It’s one of the few annoying aspects on what is otherwise a fantastic vehicle.
01-13-2024
I had this problem pop up after using BimmerCode on my X7. It was due to a change in one of the parameters in the Receiver Audio Module. I went back and restored the original backup file and the issue went away.
01-14-2024
Must be issue with new idrive update. I also had many issues with coding Reciever Audio Moudle.
01-29-2024
for anyone experiencing this,

Receiver Audio Module

changing to rolls royce broke it for me

Changing back to standard solved
07-31-2025
MARKPRIOR wrote
for anyone experiencing this,

Receiver Audio Module

changing to rolls royce broke it for me

Changing back to standard solved
Sorry to revive this thread, but I'm gett the same "Driver's Assistance features permanently disabled on my 2025 M340ix, only on startup. It doesn't seem to effect anything, but it's an annoying message.

While I did code in ambient lighting, window lifter interruption, and no horn on lock while the car's running, I also did Rolls-Royce tones for PDC/etc.

If swapping back to BMW2021 tones works, you're my hero.
12-23-2025
Bump.

Was anyone successful in activation driving assistant plus in Germany/ EU?

Is coding only done in the HU for that feature?
04-13-2026
ifr wrote
HU_MGU\LENKASSISTENT_DCS must be gen1/aktiv
SASx\C_HOO_Vorhanden should be standby or nostandby, but not 'nicht_vorhanden'

Don't activate LENKASSISTENT_PLUS in HU_MGU or the camera will deactivate

You cant code SAS with BC so not likely to be that code

Do you have the DAC enabled in idrive main settings, and does it appear listed in Settings-Driver Assistance-Steering?
I'm experiencing this issue on my 2020 M340, could you elaborate a bit more of the camera coding?

Looking at my SAS3\C_HOO_Vorhanden, there is no option like you mentioned:

An image attached to this post, provided by the poster

I don't have LENKASSISTENT_PLUS activated, how can I get my DAC back?