G05
BMW X5
80.1KVIEWS
158REPLIES
45APPRECIATES
47ACTIVE PEOPLE
03-30-2026LAST POST
01-18-2020
I'd be interested in feedback on the following points:

- Is coding DSC_VIPx necessary - worth trying without first
- I'm not sure if STRECKEN_VERLAUF is strictly needed for aSLA. Suspect it activates predicted deceleration for junctions/roundabouts, etc.

VOFFSET* introduces an additional option to set the manual speed adjustment up to 40mph and also above 40mph. This gives me control over the manual adjustments e.g. I set the first param to + 2mph up to 40mph, and +5 above 40 mph. This ensures there is no chance of a speeding ticket while maintaining a reasonable speed. This additional capability is not available with aSLA even in countries where its supported, so might be worth coding even if you already have aSLA.

Can confirm working on US G05/G07, CA G05 and AUSY G05. i-step >= 07/2019.x

Some potential behaviour changes in some regions on i-step 11/2019.x
01-18-2020
Only thing I noticed different from descriptions on my April 2019 CA build now on 11/2019.40 is that two of the original country bitmaps were different from @ifr's table. Looks like more countries got aSLA enabled stock on 11/2019.40.

Also all my stuff is properly in km/h and the 40mph threshold is 65km/h on mine. Max over/under you can set is 15km/h, which for me is not enough (those driving 401 within 100km of TO will understand).

I coded all parameters indicated. All functions work, including predictive slow down/speed ups.
01-18-2020
I have successfully coded it. I am on 2019/11, AUSY car.

I changed two options from the list VOFFSET to gen_2.


I see the option to "Adjust to route" which enables roundabout, turns... this can be turned on/off as well if not required.

Everything works fine.
01-18-2020
jeet wrote
I have successfully coded it. I am on 2019/11, AUSY car.

I changed two options from the list VOFFSET to gen_2.


I see the option to "Adjust to route" which enables roundabout, turns... this can be turned on/off as well if not required.

Everything works fine.
Thanks for the feedback.

On 07/2019.x, changing voffset to gen2 limited the adjustable speed to 5mph instead of 10mph.

Gen2 is not designed for the g05, I think it was g01 only as I recall. Would need to double check.
01-19-2020
I did change it back to Gen 1 and yes now it is 15 KMph instead of 10.
01-19-2020
Is aSLA showing in your (US/CA/AU) iDrive menu before this coding? For me (FI, 07/2019.59), automatic speed limit adjustment and speed adjustment to route are visible menu options but selecting them results in a message about them not being available in this country and later warnings when activating any assisted driving features.

Manual adjustment for speeds up to 60 km/h and separately for over 60 km/h is available for me without coding and works fine.

I am trying to estimate the minimal amount of coding required to have aSLA.
01-19-2020
perikifi wrote
Is aSLA showing in your (US/CA/AU) iDrive menu before this coding? For me (FI, 07/2019.59), automatic speed limit adjustment and speed adjustment to route are visible menu options but selecting them results in a message about them not being available in this country and later warnings when activating any assisted driving features.

Manual adjustment for speeds up to 60 km/h and separately for over 60 km/h is available for me without coding and works fine.

I am trying to estimate the minimal amount of coding required to have aSLA.
The 'Automatic' option doesn't show for their cars prior to coding. I guess you will have some of the aSLA coding enabled but falling foul of the land mask restrictions i.e. your car supports aSLA but GPS/NAV is showing as in an unsupported region. I expect if you drove to the UK, for example, it would work without any additional coding.

Best bet is simply to set what you don't have, and absolutely set the land masks to FFFFFFFF at the minimum.
01-19-2020
Excuse my lack of knowledge, what is aSLA?
01-19-2020
mattsrs wrote
Excuse my lack of knowledge, what is aSLA?
automatic Speed Limit Assistant - changes the cars cruise control speed to the posted and/or navigation stored speed limit (plus/minus X MPH/KPH as defined by the user), automatically, without any input from the driver.
01-19-2020
ifr wrote
automatic Speed Limit Assistant - changes the cars cruise control speed to the posted and/or navigation stored speed limit (plus/minus X MPH/KPH as defined by the user), automatically, without any input from the driver.
nice! this is a great feature. Can anyone coded it for US models? I am on latest iDrive (I believe 11/2019.40?) . Can I code using Bimmercode app expert mode?
01-19-2020
mattsrs wrote
ifr wrote
automatic Speed Limit Assistant - changes the cars cruise control speed to the posted and/or navigation stored speed limit (plus/minus X MPH/KPH as defined by the user), automatically, without any input from the driver.
nice! this is a great feature. Can anyone coded it for US models? I am on latest iDrive (I believe 11/2019.40?) . Can I code using Bimmercode app expert mode?
At the moment I don't think you can access all required ECUs with BimmerCode, you'll need esys or esysx.
01-20-2020
Are all the default values 100%? I’m finding on my US model that some of the required values are already in place.
01-20-2020
maczrool wrote
Are all the default values 100%? I’m finding on my US model that some of the required values are already in place.
My defaults were not quite the same as per this spreadsheet either. That could be for a variety of reasons, one being that @ifr is on 07/2019.xx you and I are on 11/2019.xx. I reported my defaults back to @ifr.
01-20-2020
I’m on 7/2019.53 but thank you for confirming there are differences.
01-20-2020
Here’s a general esys/esysx coding question since the aSLA function affects so many modules. Can you perform changes to multiple modules and then do the Code ncd step once rather than having to do it for each module individually? Thought I saw somewhere it wouldn’t work with esysx. Thanks!
02-01-2020
After a lot of reading and some trial and error, I got Esys+EsysX working and was able check the aSLA settings on my MY20 October 2019 build Euro 45e with 07/2019.59 factory software.

All the other listed keys had the correct values, only the six *_Land_Aktiv keys had non-0xFFFFFFFF values, keeping me from using aSLA, as one of the 0 bits is for Finland (or Nordic or something else). Note that I have been able to select aSLA in iDrive since start but it has produced a 'This feature is not supported in your country' message and later warnings every time you activate adaptive driving.

Having coded all six land keys to 0xFFFFFFFF I am able to set SLA as Adjust automatically, as well as check on Adapt to route, without any messages. So everything is great, but due to this weekend's schedule I will not be fully field testing this before Monday.

A few final notes:
  • The coding how-tos and many URLs in them are badly outdated, confusing and contradictory. After visiting many deadends the steps required for successful coding were not that many or complex, and it is possible to get going with the instructions, only a bit time-consuming and painful. With more time at hand, I would be tempted to write my own how-to based on my experiences.
  • EsysX installation instructions advised to create anti-malware software exceptions for two IspiHost program directories. I chose not to do that. Installing EsysX produced a Windows Defender alert for a known trojan. I quarantined the file in question. However, EsysX seems to work fine for FDL coding without the file. I feel a bit uncomfortable leaving this software installed on my primary laptop but the license is now tied to that machine.
02-03-2020
perikifi wrote
After a lot of reading and some trial and error, I got Esys+EsysX working and was able check the aSLA settings on my MY20 October 2019 build Euro 45e with 07/2019.59 factory software.

All the other listed keys had the correct values, only the six *_Land_Aktiv keys had non-0xFFFFFFFF values, keeping me from using aSLA, as one of the 0 bits is for Finland (or Nordic or something else). Note that I have been able to select aSLA in iDrive since start but it has produced a 'This feature is not supported in your country' message and later warnings every time you activate adaptive driving.

Having coded all six land keys to 0xFFFFFFFF I am able to set SLA as Adjust automatically, as well as check on Adapt to route, without any messages. So everything is great, but due to this weekend's schedule I will not be fully field testing this before Monday.

A few final notes:
  • The coding how-tos and many URLs in them are badly outdated, confusing and contradictory. After visiting many deadends the steps required for successful coding were not that many or complex, and it is possible to get going with the instructions, only a bit time-consuming and painful. With more time at hand, I would be tempted to write my own how-to based on my experiences.
  • EsysX installation instructions advised to create anti-malware software exceptions for two IspiHost program directories. I chose not to do that. Installing EsysX produced a Windows Defender alert for a known trojan. I quarantined the file in question. However, EsysX seems to work fine for FDL coding without the file. I feel a bit uncomfortable leaving this software installed on my primary laptop but the license is now tied to that machine.
Thanks for confirming. That was my expectation.

There are basically 3 scenarios:
1) Car is coded to allow aSLA, region vehicle is physically located is NOT allowed to use aSLA
2) Car is coded to allow aSLA, region vehicle is physically located IS allowed to use aSLA
3) Car is not coded to allow aSLA, region vehicle is physically located may or may not allow use of aSLA but wont work regardless

The codes should address all scenarios give or take a setting or two, plus add the adaptive driving, slowing for roundabouts etc

Technically the land bitmask could be modified to allow additional 'specific' regions, but no need when FFFFFFFF does the trick.
02-03-2020
And it works like charm! :happyanim: aSLA is important to me as I really want to avoid accidental speeding tickets from the increasing numbers of automatic speed cameras around here (the cheapest ticket is around $200 and I only ever got one of them). Thanks LexxM3's user avatarLexxM3, ifr's user avatarifr and homerrr's user avatarhomerrr for your examples, encouragement and warnings ;)
02-03-2020
I love it too. I was constantly setting, adjusting and readjusting the active cruise on my previous X5, which is rarely necessary with this feature. Just turn it on and let it do the work.

The fact its safer and almost eliminates the risk of a speeding ticket is even better.

BMW just need to sort the occasional aggressive deceleration, and improve the false positive recognition from discarded/offset speed limit signs. Cloud connected machine learning will help with that.
04-13-2020
Got this coded. What does the “Set” icon with the green bars above and below it that shows on the dash and HUD indicate?
04-13-2020
ifr wrote
Thanks for confirming. That was my expectation.

There are basically 3 scenarios:
1) Car is coded to allow aSLA, region vehicle is physically located is NOT allowed to use aSLA
2) Car is coded to allow aSLA, region vehicle is physically located IS allowed to use aSLA
3) Car is not coded to allow aSLA, region vehicle is physically located may or may not allow use of aSLA but wont work regardless

The codes should address all scenarios give or take a setting or two, plus add the adaptive driving, slowing for roundabouts etc

Technically the land bitmask could be modified to allow additional 'specific' regions, but no need when FFFFFFFF does the trick.
when i turn on speed limit the dash displays "LIMIT" all the time which i guess is due to me being in a region not enabled by the current coding.

Does the coding below above cover fix this issue for me? im in ksa would love to enable automatic sign recognition.