Xmel&#96 wrote  

Hi can you please confirm that DSC_VIP should be coded for normal aSLA working? Or it is not necessarily?
I am on 03/2020.24 now. Using esys with launcher pro 3.7.0.315
And coding of DSC_VIP ends with error.
But aSLA activates and seems to be working.
Please help. What can be the problem?

LexxM3 wrote

In some tests in Feb 2020, @ifr and a few of us confirmed that DSC_VIP can remain stock for aSLA. So that explains why your coding without DSC_VIP works.

Independent of that, any ESys coding errors are worrying. One possibility is that you are not using quite the latest psdzdata that supports your very recent ISTEP version. Another is that Launcher Pro is not keeping up with mapping changes; ESysX appears to be a bit better with that. Anyway, some ideas — if you get to root cause, it would be valuable to report.

Xmel` wrote

My I-step is 20-03-524 and Im use PSdZData_Lite_v4.22.14
I also don`t like that DSC error.
But is it possible that some sistems will not work correct especially braking?

ifr wrote

Xmel&#96 wrote  

My I-step is 20-03-524 and Im use PSdZData_Lite_v4.22.14
I also don`t like that DSC error.
But is it possible that some sistems will not work correct especially braking?

What error do you get with VIP? Is it a seed authentication error by any chance?

Xmel` wrote

I've finally coded it. And esys returned with no errors. But it took me several attempts. Thanks for your help.
Is possible to add eTJA somehow to EU cars?

ifr wrote

Did you do anything to get DSC_VIP2 to code, or just leave as is? You don't need to code it for aSLA.

eTJA can be coded by adding 5AR to FA and VO Code SAS and HU_MGU, or FDL code:
HU_MGU:
Lenkassistent_DCS: gen_1

SAS2:
C_HOO_Vorhanden: NR001_Vorhanden_Standby (if on i-step 1911 or later)

C_HOO_Vorhanden: NR002_Vorhanden_NoStandby (if on i-step < 1911)

I'm not making an assumption on the value to set C_HOO* to. It's actually build version that it is referring to, so if there is a hardware change and its not just software updates, then NoStandby would be the right choice. No idea on the difference between the two options, which leads to me next point.

It doesn't work for me. It's not because the coding is incorrect, its not, its because the car checks which region it is in and if not supported then doesn't activate. I have not been able to find a land mask or similar that would allow EU country support.

lufan wrote

Hello IFR, I'm in China. My definition of G05 is that it can only be used on the highway and the speed is lower than 60km / h to start the full automatic driving aid without taking over the steering wheel. I want it to work on any road and speed. I tried to change C_hoo_vorhanden but it didn't work. Do you have a good way

ifr wrote

No. The codes that worked on the G30 and similar do not work on the G05.

Honestly I think this a good thing. I have held back similar codes as releasing them is irresponsible. The DA system does not currently work well enough to operate on any road at any speed. DA will even disengage when driving on highways if the speed and curve radius is out of tolerance. If your hands are not on or near the wheel at that time, then you are in BIG trouble.

I have also observed that removal of the requirement to regularly touch the wheel causes significant driver disengagement, to the point that they cannot react quickly enough in an emergency situation.

ifr wrote

Xmel&#96 wrote  

I've finally coded it. And esys returned with no errors. But it took me several attempts. Thanks for your help.
Is possible to add eTJA somehow to EU cars?

Did you do anything to get DSC_VIP2 to code, or just leave as is? You don't need to code it for aSLA.

eTJA can be coded by adding 5AR to FA and VO Code SAS and HU_MGU, or FDL code:
HU_MGU:
Lenkassistent_DCS: gen_1

SAS2:
C_HOO_Vorhanden: NR001_Vorhanden_Standby (if on i-step 1911 or later)

C_HOO_Vorhanden: NR002_Vorhanden_NoStandby (if on i-step < 1911)

I'm not making an assumption on the value to set C_HOO* to. It's actually build version that it is referring to, so if there is a hardware change and its not just software updates, then NoStandby would be the right choice. No idea on the difference between the two options, which leads to me next point.

It doesn't work for me. It's not because the coding is incorrect, its not, its because the car checks which region it is in and if not supported then doesn't activate. I have not been able to find a land mask or similar that would allow EU country support.

Xmel` wrote

I've coded DSC_VIP/3D14.
aSLA worked without coding that ECU.
But I was afraid that some braking options will not work.
Finally I have got it.

Do you think it is possible to downgrade firmware of some ECU's to make eTJA work in most of regions? As I have read it was possible on some older firmware.

I also agree that hands free drive is not really safe all the time. The system is not really stable. And in difficult situations it just turns off immediately.

But is it possible to activate full functionality of aSLA with out seatbelt fastened? What are the parameters for that?

ifr wrote

Xmel&#96 wrote  

I've coded DSC_VIP/3D14.
aSLA worked without coding that ECU.
But I was afraid that some braking options will not work.
Finally I have got it.

Do you think it is possible to downgrade firmware of some ECU's to make eTJA work in most of regions? As I have read it was possible on some older firmware.

I also agree that hands free drive is not really safe all the time. The system is not really stable. And in difficult situations it just turns off immediately.

But is it possible to activate full functionality of aSLA with out seatbelt fastened? What are the parameters for that?

eTJA has never worked in all regions on the G05, if anything more regions have been added with later i-step e.g. Japan. If you are talking about downgrading ECU's (!) to a firmware prior to that supported on the G05 then that's a hard no.

I didn't know there was an issue with aSLA and seat belts? I always where my seat belt when driving so wouldn't notice, nor would I look into coding around it.

There must be a method that BMW is using to add extra regions to eTJA as and when a region gets regulatory approval for the hands off function. I just haven't been able to find it and testing is really hard.

Xmel` wrote

So there's no problem with testing it. I can do it easily. If you could help with parameters? I mean the mask of the region or dome others.

Sorry for the off top but may be you know parameters to code X off road functionality (xsand, xsnow, xrock and so on)?
I have an Msport differential on my m50d and it should be enough for that function. The only thing I don't have is that trigger on central console near that level trigger.
I have also coded that parameters in hu_mgu but they do not show in idrive setting.
Is it possible to manage it with some VO coding?

ifr wrote

VO Code would be 3E3 to FA and Code 7083, 3E52, 3D0E

Quite a few codes changed but not sure how you can switch modes without a rocker, even assuming you have GHAS?

ifr wrote

Xmel&#96 wrote  

I've finally coded it. And esys returned with no errors. But it took me several attempts. Thanks for your help.
Is possible to add eTJA somehow to EU cars?

Did you do anything to get DSC_VIP2 to code, or just leave as is? You don't need to code it for aSLA.

eTJA can be coded by adding 5AR to FA and VO Code SAS and HU_MGU, or FDL code:
HU_MGU:
Lenkassistent_DCS: gen_1

SAS2:
C_HOO_Vorhanden: NR001_Vorhanden_Standby (if on i-step 1911 or later)

C_HOO_Vorhanden: NR002_Vorhanden_NoStandby (if on i-step < 1911)

I'm not making an assumption on the value to set C_HOO* to. It's actually build version that it is referring to, so if there is a hardware change and its not just software updates, then NoStandby would be the right choice. No idea on the difference between the two options, which leads to me next point.

It doesn't work for me. It's not because the coding is incorrect, its not, its because the car checks which region it is in and if not supported then doesn't activate. I have not been able to find a land mask or similar that would allow EU country support.

ifr wrote

Xmel&#96 wrote  

I've finally coded it. And esys returned with no errors. But it took me several attempts. Thanks for your help.
Is possible to add eTJA somehow to EU cars?

Did you do anything to get DSC_VIP2 to code, or just leave as is? You don't need to code it for aSLA.

eTJA can be coded by adding 5AR to FA and VO Code SAS and HU_MGU, or FDL code:
HU_MGU:
Lenkassistent_DCS: gen_1

SAS2:
C_HOO_Vorhanden: NR001_Vorhanden_Standby (if on i-step 1911 or later)

C_HOO_Vorhanden: NR002_Vorhanden_NoStandby (if on i-step < 1911)

I'm not making an assumption on the value to set C_HOO* to. It's actually build version that it is referring to, so if there is a hardware change and its not just software updates, then NoStandby would be the right choice. No idea on the difference between the two options, which leads to me next point.

It doesn't work for me. It's not because the coding is incorrect, its not, its because the car checks which region it is in and if not supported then doesn't activate. I have not been able to find a land mask or similar that would allow EU country support.

Xmel` wrote

On i-step 2003 I had only these values

ifr wrote

Xmel&#96 wrote  

On i-step 2003 I had only these values

I guess you are using Launcher Pro and not esysx?

You are missing the accurate mappings.
Standby is Werte=01
NoStandby is Werte=02

Just use whichever matches

Xmel&#96 wrote  

ifr wrote

Xmel&#96 wrote  

On i-step 2003 I had only these values

I guess you are using Launcher Pro and not esysx?

You are missing the accurate mappings.
Standby is Werte=01
NoStandby is Werte=02

Just use whichever matches

Yes, I use Launcher Pro.
Anyway I have tried them both.
But it doesn't work ((

homerrr wrote

Following link for aSLA coding. Verified on US model with 7/2019.55:

https://drive.google.com/file/d/1U9haplnUiKFYIwrRtBChHZmMds3cFmzt/view

Anyone with questions, answers or recommendations feel free to post...

Credit goes to Eaglesrest...