[ifr]

This guide is specifically focused on VO Coding auto Lane Change Assistant, but will work for any VO Coding.

Note: the FA will not be saved to the car, which mitigates some risk of dealer warranty issues. The trade off is that the process will need to be repeated after each i-step upgrade that modifies HU_MGU, SAS and/or BDC.

Pre-reqs
- Windows PC - I use Windows 10 x64 VM on macOS VMware Fusion
- OBD-II to Ethernet cable
- E-Sys 3.27.1 or later - I use 3.36.2
- psdzdata - currently at 03/2021.57. You need a version that supports at least the same or newer than your car's i-step version.

Coding Steps for auto Lane Change Assistant (SWA)

1. Connect OBD2 cable to car
2. Start E-Sys
3. Start Car Diagnostic Mode (3 quick presses of the ignition button). Diag mode is preferred, but you need to be aware of your battery health and level of charge. Ideally connect a battery charger or voltage regulator.
4. Plug OBD2 cable into Ethernet Port and wait a few seconds
5. Switch to Expert Mode-Coding in E-sys
6. Click on the Connect Icon
7. Target Selector: choose the i-step that most closely matches your car version e.g. S18A_21_03_557. Under Interface, select 'Connection by VIN' If your VIN is not listed you have an issue. Usually wait longer, or check the PC network card is set to use TCP/IP 4 DHCP (not static), or cable not working, etc. Do not select *_DIRECT
8. Hit Connect button
9. Under 'Vehicle Order' click on Read
10. Under 'Vehicle Order' right-click on FA and choose Activate FA if required
11. Under 'SVT Actual', click on Read (ECU)
    If it's the first time you have coded, right-click on ECU under the SVT tree and choose 'Read Coding Data'. Use Windows File Explorer to backup your CAF directory which by default is C:\Data\CAF
12. Save your FA and SVT
13. Under Editors and Viewers - select ‘FA Editor’ and load your saved FA
14. Click on SALAPA-Element find and remove 8TR from the list. Click on Apply Changes
15. Click on File-Save As Give it a name such as FA_032021557_no8TR
16. Switch back to Expert Mode-Coding Load the FA you just created with no 8TR and do Read (ECU) again.
17. Select the following 3 ECU’s in the SVT pane. Note these may vary by model:
    1. BDC_BODY\CAFD_*7083*
    2. HU_MGU\CAFD_*3E52*
    3. SAS3\CAFD_*42C1*
18. With the 3 x ECU selected, click on Code (not Code Default Values)
19. Check the report is Green for all 3 ECU. Warnings are OK, but the text should be Green
20. Done!! Go into i-drive Car-Settings-Driver Assistance-Steering Assistant and make sure ‘Lane Change Assistant’ is ticked

Enjoy!

If you find the lane changes are slower than you would like, almost hesitant, then there is a fix for that, but it requires FDL coding and is not covered here.

[Andy3661]

Originally Posted by ifr

This guide is specifically focused on VO Coding auto Lane Change Assistant, but will work for any VO Coding.

Note: the FA will not be saved to the car, which mitigates some risk of dealer warranty issues. The trade off is that the process will need to be repeated after each i-step upgrade that modifies HU_MGU, SAS and/or BDC.

Pre-reqs
- Windows PC - I use Windows 10 x64 VM on macOS VMware Fusion
- OBD-II to Ethernet cable
- E-Sys 3.27.1 or later - I use 3.36.2
- psdzdata - currently at 03/2021.57. You need a version that supports at least the same or newer than your car's i-step version.

Coding Steps for auto Lane Change Assistant (SWA)

1. Connect OBD2 cable to car
2. Start E-Sys
3. Start Car Diagnostic Mode (3 quick presses of the ignition button). Diag mode is preferred, but you need to be aware of your battery health and level of charge. Ideally connect a battery charger or voltage regulator.
4. Plug OBD2 cable into Ethernet Port and wait a few seconds
5. Switch to Expert Mode-Coding in E-sys
6. Click on the Connect Icon
7. Target Selector: choose the i-step that most closely matches your car version e.g. S18A_21_03_557. Under Interface, select 'Connection by VIN' If your VIN is not listed you have an issue. Usually wait longer, or check the PC network card is set to use TCP/IP 4 DHCP (not static), or cable not working, etc. Do not select *_DIRECT
8. Hit Connect button
9. Under 'Vehicle Order' click on Read
10. Under 'SVT Actual', click on Read (ECU)
    If it's the first time you have coded, right-click on ECU under the SVT tree and choose 'Read Coding Data'. Use Windows File Explorer to backup your CAF directory which by default is C:\Data\CAF
11. Save your FA and SVT
12. Under Editors and Viewers - select 'FA Editor' and load your saved FA
13. Click on SALAPA-Element find and remove 8TR from the list. Click on Apply Changes
14. Click on File-Save As Give it a name such as FA_032021557_no8TR
15. Switch back to Expert Mode-Coding Load the FA you just created with no 8TR and do Read (ECU) again.
16. Select the following 3 ECU's in the SVT pane. Note these may vary by model:
    1. BDC_BODY\CAFD_*7083*
    2. HU_MGU\CAFD_*3E52*
    3. SAS3\CAFD_*42C1*
17. With the 3 x ECU selected, click on Code (not Code Default Values)
18. Check the report is Green for all 3 ECU. Warnings are OK, but the text should be Green
19. Done!! Go into i-drive Car-Settings-Driver Assistance-Steering Assistant and make sure 'Lane Change Assistant' is ticked

Enjoy!

If you find the lane changes are slower than you would like, almost hesitant, then there is a fix for that, but it requires FDL coding and is not covered here.

Hi

Thanks for this. When I get to the SALAPA-Element it's empty?

[zazzau]

Originally Posted by Andy3661

Hi

Thanks for this. When I get to the SALAPA-Element it's empty?

Yes you have to activate FA first. It is not included in the instruction (so perhaps OP can modify the instruction.)

Oh! And I didn't get any options after clicking on the drop-down to select I-step. So I continued without selecting an I-step. I was able to code a bunch of stuff without any issues. As for the DHCP, I am running a Windows VM on MacOS, so I set static IP on MacOS and I placed the VM in bridged mode. Hopefully this helps others.

[ifr]

Originally Posted by zazzau

Yes you have to activate FA first. It is not included in the instruction (so perhaps OP can modify the instruction.)

Oh! And I didn't get any options after clicking on the drop-down to select I-step. So I continued without selecting an I-step. I was able to code a bunch of stuff without any issues. As for the DHCP, I am running a Windows VM on MacOS, so I set static IP on MacOS and I placed the VM in bridged mode. Hopefully this helps others.

I've not had to activate an FA since 2014, maybe linked to older esys?

How did you connect to the car without selecting a target connector?

You have to select the connector for your target vehicle type e.g. S18A, and then the i-step that most closely matches the car's i-step.

Can you post screenshots of your connection to the car without connecting to the car? unless you are completely misinterpreting it?

[zazzau]

I'm on 3.27.1. I had the same problem as the last poster and I had to activate FA and that fixed the issue. I think for first time programming that may be required but I could be wrong (I'm completely new to this and this was my first time coding.)

I do not have any of those I-step version showing in mine — weirdly. I gave up after trying multiple times and simply connected using "Connection via VIN" without selecting I-step and it did not complain. See what mine looks like (in the pic below.) I don't have it hooked to the car now because the car is in the shop. I don't use any launcher just E-sys. What I'm I missing? Where can I find target selector? I VO coded anti-dazzle and got 0 errors after coding all 4 ECUs. So in my case, it would appear target selector was not needed. But then again I'm new to this. Thanks.

[ifr]

Originally Posted by zazzau

I'm on 3.27.1. I had the same problem as the last poster and I had to activate FA and that fixed the issue. I think for first time programming that may be required but I could be wrong (I'm completely new to this and this was my first time coding.)

I do not have any of those I-step version showing in mine — weirdly. I gave up after trying multiple times and simply connected using "Connection via VIN" without selecting I-step and it did not complain. See what mine looks like. I don't have it hooked to the car now because the car is in the shop. I don't use any launcher just E-sys. There's a slight difference between mine and yours — for example mine does not have the "refresh" shown in yours and clearly it does not have the target selector. What I'm I missing? I coded out anti-dazzle and got 0 errors after coding all 4 ECUs. So in my case, it would appear target selector was not needed. But then again I'm new to this. Thanks.

Ta, I've updated the instructions for belt and braces.

That display is a new one on me. Personally I'd scrub your install and psdzdata folder, and start again with esys 3.36 and latest psdzdata (supports up to 03/2021.567).

If you want to stick with 3.27 then at least make sure the options are set correctly for psdzdata and data folder, and replace the psdzdata folder as something is not correct.

[zazzau]

Originally Posted by ifr

Ta, I've updated the instructions for belt and braces.

That display is a new one on me. Personally I'd scrub your install and psdzdata folder, and start again with esys 3.36 and latest psdzdata (supports up to 03/2021.567).

If you want to stick with 3.27 then at least make sure the options are set correctly for psdzdata and data folder, and replace the psdzdata folder as something is not correct.

Should I be concerned that I coded without selecting any target selector? I would have expected some errors when coding the ECUs. I know it worked because it cleared all my previous coding to those ECUs although I have not tested the anti-dazzle in real-time until I get my car back. I have the latest psdzdata file from shawnsheridan which I used. Everything looks good, I have also checked all "dist" folders and they are all empty. Not sure what else I'm missing.

RE: "at least make sure the options are set correctly for psdzdata and data folder."

What options are you referring to? See my directory setting:

[ifr]

I wouldn't code with that environment, but your call. Seems to have worked for you somehow. Looks like you also have the display bug. Google for fixes for that.

esys 3.36.2 has options for psdzdata specifically, but in your case you'd need to make sure that your folder structure is c:\data\psdzdata\* (no nesting of psdzdata) and that your folder is not corrupted.

I cant advise on anything else as you dont have the same setup as me.

[zazzau]

I went ahead and changed DPI scaling settings and everything is now being rendered correctly. Very interesting how I was able to code this without setting the target selector previously. If the software really cares about it; I would have expected an error to be thrown while coding the ECU modules. Anyhow, with the display settings now "fixed" I do see the target selector option and all the other misaligned tabs/menu options are now showing properly.

[ifr]

Originally Posted by zazzau

I went ahead and changed DPI scaling settings and everything is now being rendered correctly. Very interesting how I was able to code this without setting the target selector previously. If the software really cares about it; I would have expected an error to be thrown while coding the ECU modules. Anyhow, with the display settings now "fixed" I do see the target selector option and all the other misaligned tabs/menu options are now showing properly.

Good news.

I'm guessing you connected as an F01. As long as you didn't get any errors when coding, like 'ethernet ecu' connect errors, then you should be good. Probably worst case it just wouldn't have coded at all.

[zazzau]

Originally Posted by ifr

Good news.

I'm guessing you connected as an F01. As long as you didn't get any errors when coding, like 'ethernet ecu' connect errors, then you should be good. Probably worst case it just wouldn't have coded at all.

That would be my guess. I'm just wondering what the repercussions are for using the wrong target selector. VO coding anti-dazzle cleared all previous coding related to the ECU modules from before; so I know it worked. I had to code them back individually. Of course I'll be using the target selector now that I have ESYS rendering as it should; I was just curious why it worked with the wrong target (assuming it defaulted to F001.)

[toronto_m50i]

Can this be coded on any G05 or do you need specific hardware to be able to have this feature?

[ifr]

Originally Posted by toronto_m50i

Can this be coded on any G05 or do you need specific hardware to be able to have this feature?

You need Drive Assistant Professional to use ADV

[toronto_m50i]

Originally Posted by ifr

You need Drive Assistant Professional to use ADV

thank you!

[Portocale]

Hi, it s out of topic but someone have informations when will be available at dealer 07/2021 software upgrade?

[ifr]

Originally Posted by Portocale

Hi, it s out of topic but someone have informations when will be available at dealer 07/2021 software upgrade?

Next couple of weeks.

I'm on 03/2021.567 currently

[Andy3661]

Originally Posted by zazzau

Yes you have to activate FA first. It is not included in the instruction (so perhaps OP can modify the instruction.)

Oh! And I didn't get any options after clicking on the drop-down to select I-step. So I continued without selecting an I-step. I was able to code a bunch of stuff without any issues. As for the DHCP, I am running a Windows VM on MacOS, so I set static IP on MacOS and I placed the VM in bridged mode. Hopefully this helps others.

Thanks. I activated the FA but the SALAPA-Element is still empty, I don't understand what I'm doing wrong.

[ifr]

have you tried expanding it out

[Andy3661]

Originally Posted by ifr

have you tried expanding it out

Wow, how thick am I lol.

But now I have no 8TR in the list?

[zazzau]

Originally Posted by Andy3661

Wow, how thick am I lol.

But now I have no 8TR in the list?

What package did you get for your car?

[Andy3661]

Originally Posted by zazzau

What package did you get for your car?

As far as I know it has all options including the driving assistance pro.

[ifr]

Originally Posted by Andy3661

Wow, how thick am I lol.

But now I have no 8TR in the list?

What does mdecoder say for your vin? Is 8tr listed?