Skoda Octavia MK4 2023, 2.0TDi DSG Ambition

[ciclo]

Have you previously studied and prepared the codifications + adaptations of all the units involved?
This will save you a lot of time and prevent you from making mistakes when doing it.
For example, copying and pasting the right long coding in the involved control units of your Octavia is better than searching for the appropriate Bits in them.

[giannis20vt]

I have found information about what changes need to be made to each module involved in the process of installing and configuring them.
Ι copy them from a guy who already did that retrofit to his SEAT LEON MK$ (also a MQB Evo based car)
thanx to mysticscalex from Seatcupra.net
https://www.seatcupra.net/forums/thread ... st-5060818
These are the changes that need to be made.

1) GATEWAY
Register 3C modules

2) Control unit: 03 Brakes (ABS)
Long coding:
Byte 18 activate bit 3
Byte 30 activate bit 4
Adaptations:
-Delay management:
Rear cross traffic assistant: Not activated --> Activated

3) Control unit: 17 Dashboard
Long coding:
Lane change assistance: No --> Yes
Lane change assistant, BAP distance: No --> YES
Lane retention assistant, BAP distance: No --> YES
Lane_change_assistent: no —> yes
Blind_spot_detection: no —> yes

4) Control unit: 5F Multimedia
Adaptations:
-Vehicle function list BAP:
SWA_0x1A: Not activated --> Activated
SWA_0x1A_msg_bus: Not activated --> Terminal 15
-Vehicle menu operation:
menu_display_lane_assistant: Not activated --> Activated
menu_display_lane_assistant_over_threshold_high: Not activated --> Activated

5) Control unit: A5 Driver Assistance
Long coding:
SWA: Not_coded --> Coded
blind_spot_detection: Not_coded --> Coded
HC_Mob_line: Not_coded —> Coded (this is for automatic lane change)
HC_var(this is for automatic lane change)

6) Control unit: 19 Gateway
Long coding:
PaCo_Rear_Cross_Traffic_Alest: not installed --> installed


7) Control unit: 75 Telematics
Adaptations:
-Vehicle function list BAP:
Lane change assistance: Not activated --> Activated
SWA_0x1A: Not activated —> Activated

Control Unit: 44 steering assistance
Adaptions:
Qfk_ma_function: Not_active —> Active (this is for automatic lane change)

9) Control Unit: 13 ACC
Long Coding:
Lane_change_support: not activated —> activated

Is going to be a try and error procedure, i am sure about that.

[patil]

I am very much interested in how you approach the CP removal and dataset flashing process for the BSD radars. Looking forward eagerly

[giannis20vt]

New toy



I haven't tried it yet. On the weekend I will play with it.

[giannis20vt]

First attempt to view the 03C modules





I used the Self-Diagnosis mode. I couldn't find the 03C so i went to Networking Diagram, found the 03C and then read the DTC

I so the errors, and then i read the module

So i suppose that the Remove CP "line" is at the Diagnosis Mode.

[ciclo]

Go to your friend's workshop and have him remove the CP with his VAS via an online connection.
He will show you how to remove the CP... this can be done directly from the special functions or via the guided function that can be selected from the control modules.

ODIS S has a progress bar with ongoing and informative activities at the bottom and you must let it finish the reading processes when starting the Diagnosis, it is a bit slow and you must have some patience.

The ODIS S self-diagnosis is, in my humble opinion, the worst diagnostic program I have ever used. It is a part of ODIS S that serves as support.
With ODIS E you can do better everything that can be done with the ODIS S self-diagnosis.

Learn how to use the programs before you do something wrong.

[giannis20vt]

Go to your friend's workshop and have him remove the CP with his VAS via an online connection.
He will show you how to remove the CP... this can be done directly from the special functions or via the guided function that can be selected from the control modules.

Okay, that's the plan.
I'm just playing around with my new "game" and trying to learn a little bit about programming.

ODIS S has a progress bar with ongoing and informative activities at the bottom and you must let it finish the reading processes when starting the Diagnosis, it is a bit slow and you must have some patience.

This was excellent information. With the old 5054A I had tried to do a diagnosis and waited for over 10 minutes without success. So I thought that this function would only be successful when there is an Online connection.
I will try it with the 6154 cable

The ODIS S self-diagnosis is, in my humble opinion, the worst diagnostic program I have ever used. It is a part of ODIS S that serves as support.
With ODIS E you can do better everything that can be done with the ODIS S self-diagnosis.

Learn how to use the programs before you do something wrong.

that's what I'm trying to do.
Thanks!

[ciclo]

ODIS S has a progress bar with ongoing and informative activities at the bottom and you must let it finish the reading processes when starting the Diagnosis, it is a bit slow and you must have some patience.

This was excellent information. With the old 5054A I had tried to do a diagnosis and waited for over 10 minutes without success. So I thought that this function would only be successful when there is an Online connection.
I will try it with the 6154 cable

With ODIS S, once you have entered the VIN (if test bench) and vehicle data in the prompt (pop-up window), in the next window you select 'without job' and wait patiently for the program to do a thorough reading of the entire vehicle. From here, by selecting the control units, you can then play around with the basic settings, guided functions, etc.
It is possible to access all the functions more quickly by selecting 'without job' from the start (for experts in using the program and for those who are in a hurry for whatever reason), but I think it is better for the program to be aware of the entire environment, so I prefer to wait patiently...

With VAS5054A, with old ODIS S versions, the waiting process is even slower, but in no case 10 minutes...

[giannis20vt]

ODIS S has a progress bar with ongoing and informative activities at the bottom and you must let it finish the reading processes when starting the Diagnosis, it is a bit slow and you must have some patience.

This was excellent information. With the old 5054A I had tried to do a diagnosis and waited for over 10 minutes without success. So I thought that this function would only be successful when there is an Online connection.
I will try it with the 6154 cable

With ODIS S, once you have entered the VIN (if test bench) and vehicle data in the prompt (pop-up window), in the next window you select 'without job' and wait patiently for the program to do a thorough reading of the entire vehicle. From here, by selecting the control units, you can then play around with the basic settings, guided functions, etc.
It is possible to access all the functions more quickly by selecting 'without job' from the start (for experts in using the program and for those who are in a hurry for whatever reason), but I think it is better for the program to be aware of the entire environment, so I prefer to wait patiently...

With VAS5054A, with old ODIS S versions, the waiting process is even slower, but in no case 10 minutes...

With the old 5054A I waited 10 minutes and it still wasn't finished. Maybe the cable had some problem with the program and it couldn't do the diagnosis.
With the 6154A the job was done in less than a minute (it completed the diagnosis)

Now I feel ready to go to my friend's workshop. I just have to find the time.

[ciclo]

I remember that with my VAS5054, besides finding the right drivers (an odyssey), I had to make some modifications to the root file to make it work well and as fast as lightning, it was a real feat.
I have it stored among the good devices because it has a powerful HW, it had greater reading capacity than the old VAS6154.
These were the difficulties that there were years ago with the VAS 5054/6154 before the new and powerful VAS6154A with original drivers recently arrived.

[giannis20vt]

hi,
just a stupid question

How can I register BSD (3C) in my car's installation list using ODIS?

Using VCDS is easy (I'm already testing it and it works even when the radars are still in component protection)

[patil]

Address 19
Coding 06
Coding bus master 06.03
Select address 3c from the list and accept

[giannis20vt]

So ODIS E is the key.

Thank you very much.

[giannis20vt]

Well, i have some news.
Υesterday I went to my friend with the online connection to unlock the sensors. But it didn't work.
He has only the ODIS S 24.1.2 version.
At first we went into the sensors and did the procedure to Remove the Component Protection. Unfortunately I don't have any photos of the procedure.
The unlocking procedure seemed to be completing and we got a message that it was completed.
So I told him to try the coding. There it seemed that the procedure could not be completed. I went in with VCDS and declared 03C in 019. It accepted it. We went in again with ODIS and immediately an error appeared in the sensors.
We did the unlocking procedure again, but we got the message that it could not be completed.
After trying again and again, we gave up because I had to leave.
I don't know if we did something wrong. I'll try again in a little while when I find time to go again.

[ciclo]

Let's hope it works this time. Let's wait for the results.

Hmm... seems VW group is trying hard to make good friends...
My driving profiles (FPA) were not transferred when I tried to change/upgrade to a new GW (Hardware), which in my opinion is a CRIME for THEFT and FRAUD. Rules of corrupt thieves made in EUROPE.