(Side Assist) / (Blind Spot Detection & Rear Cross Traffic Alert) retrofit

Is there any place where I could find which dataset name / flash is for which car?
I was today in a vcp/vcds workshop and technican that was trying to upload dataset had a problem with figuring out whitch dataset set is for Kodiaq (Kodiaq with 2Q0* radars was missing on his matching list). He gave me this screenshot. I currently have SK4820EUK0BA dataset for Superb 3V so it is not even on his list. Maybe he don't have all of them?

IMG_20240228_154029.jpg
 
Last edited:
Here, xml for usage with vcp.
Hi @dnoermann,

It seems my VCP (genuine, just purchased a few weeks ago) does not like this file. I'm getting an Error writing memory : 19 Operation CAN_RequestDownloadUDS 13 Incorrect message length-wrong format message. Any idea why that might be?
 
Hi @dnoermann,

It seems my VCP (genuine, just purchased a few weeks ago) does not like this file. I'm getting an Error writing memory : 19 Operation CAN_RequestDownloadUDS 13 Incorrect message length-wrong format message. Any idea why that might be?

Sorry, i have no idea
 
Hi

Is there someone who can help with the swap for the retrofit 2Q0980653C, to make PACC , travelassist , VZE work ?
 
Hi

Is there someone who can help with the swap for the retrofit 2Q0980653C, to make PACC , travelassist , VZE work ?

For a T6 this will not work, theoretically possible in T6.1 and there i dont know if already someone did it
 
Discover Media on T6 is a PQ35 unit which makes it 100% compatible with 5Q0 radars(they can be configured to operate as PQ35).
But to display the actual visual RTA warning, the PDC unit has to be upgraded.

There are 2 choices:
1. 1K8 919 472 C
2. 5Q0 919 294 K

Installed the 1K8919472B and flashed to 1K8919472C (was a D option too but same SW)
It works as the 7E0919475 AA
In the coding Byte 1 Bit 6 is the option for the direction ABS sensor installed

I have 7E0 919 475 L / 7N0 919 475 PARKHILFE 8K H06 0106 PDC installed on my T5.1
2Q0 radars already fitted and rear axle ABS sensors replaced for bi-di ones.

I want visual RTA warning to be displayed on a screen of my Composition Media
Does it work with 7E0919475AA PDC module?
Or this one 1K8919472C compatible with tailgate opening from a key fob?
Thx
 
Last edited:
...MB12_VW32... is the data set that worked for me :cool:
Additionally I can confirm that this particular one works on MQB as well as PQ platform vehicles :thumbsup:

This one 03C_7100_2G0_MB12_VW3260EUK0BA for 2Q0907686B 0150 right? With coding 5294C420 ?
Didn't find onother MB12_VW32 at mibsolution.one
 
I have 7E0 919 475 L / 7N0 919 475 PARKHILFE 8K H06 0106 PDC installed on my T5.1
2Q0 radars already fitted and rear axle ABS sensors replaced for bi-di ones.

I want visual RTA warning to be displayed on a screen of my Composition Media
Does it work with 7E0919475AA PDC module?
Or this one 1K8919472C compatible with tailgate opening from a key fob?
Thx
Based on my experience (I have a T6):
You will need to upgrade to 1k8 to get this to work (see older posts on this thread)
When I upgraded, I lost the ability to open the boot with the key fob (closing works). I'm hoping that it's a coding/parametrisation issue, but have not found a solution as of yet
 
I want visual RTA warning to be displayed on a screen of my Composition Media
Does it work with 7E0919475AA PDC module?
I don't remember if I got RCTA system tested with my factory PDC module.
Or this one 1K8919472C compatible with tailgate opening from a key fob?
Thx
Tailgate opening via key fob remote is fully configurable via ADAPTATIONS of 6D and I didn't see any difference after upgrading my PDC to 1K8.
This one 03C_7100_2G0_MB12_VW3260EUK0BA for 2Q0907686B 0150 right? With coding 5294C420 ?
Didn't find onother MB12_VW32 at mibsolution.one
See below the exact details of the dataset I have used.
IMG-20240313-WA0024.jpg

Coding wise, VCDS seems to get confused when coding 2Q0(it shows more than 8 bits per Byte o_O).

VCP works 100% problem free, see coding show below -> 5294C4A0
IMG-20240313-WA0025.jpg
 
Based on my experience (I have a T6):
You will need to upgrade to 1k8 to get this to work (see older posts on this thread)
When I upgraded, I lost the ability to open the boot with the key fob (closing works). I'm hoping that it's a coding/parametrisation issue, but have not found a solution as of yet
Have you checked these?
Change your 6D coding to 1933098003
and adjust your 6D adaptations as per below.

IDE02134-MAS04214-Activation using rear lid remote unlocking switch-Tap function for opening,active ,1
IDE02134-MAS04215-Activation using rear lid remote unlocking switch-Tap function for closing,active ,1
IDE02134-MAS04216-Activation using rear lid remote unlocking switch-Touch function for opening,not active ,1
IDE02134-MAS04217-Activation using rear lid remote unlocking switch-Touch function for closing,not active ,1
IDE02136-MAS04214-Activation using rear lid opening button in remote key-Tap function for opening,active ,1
IDE02136-MAS04215-Activation using rear lid opening button in remote key-Tap function for closing,active ,1
IDE02136-MAS04216-Activation using rear lid opening button in remote key-Touch function for opening,not active ,1
IDE02136-MAS04217-Activation using rear lid opening button in remote key-Touch function for closing,not active ,1

And then change your 09 coding to
22F2F9BE0A61348381288F032DEB8EDD0FA4660F60C93E003204033F0840
 
Based on my experience (I have a T6):
You will need to upgrade to 1k8 to get this to work (see older posts on this thread)
When I upgraded, I lost the ability to open the boot with the key fob (closing works). I'm hoping that it's a coding/parametrisation issue, but have not found a solution as of yet
Do you have some persistant errors with 1k8 like no communication with hex 16 (as it exists on MQB not PQ) or not? What coding do you use?
 
Last edited:
Yes, I have this error about the missing electric steering like everyone here. My coding for the 1k8 module is 0001151151. I do not have the RTA system installed (yet?) and have not swapped my ABS sensors. What is also relevant is the adaptation you'll find in the post above your last.
 
Have you checked these?
Yest, the adaptations are set correctly. My current 09 coding is B8DBF9BB4A61340393288FC07C8B9FF4F094730960CD79E03204033F0860. I'll check if anything changes with the two suggested modifications sometime this weekend and report back.
 
Yest, the adaptations are set correctly. My current 09 coding is B8DBF9BB4A61340393288FC07C8B9FF4F094730960CD79E03204033F0860. I'll check if anything changes with the two suggested modifications sometime this weekend and report back.
Just tested it, it does not work. My new coding for 09 is B8D2F9BB4A61348393288FC07C8B9FF4F094730960CD79E03204033F0860
 
I don't remember if I got RCTA system tested with my factory PDC module.

Tailgate opening via key fob remote is fully configurable via ADAPTATIONS of 6D and I didn't see any difference after upgrading my PDC to 1K8.

See below the exact details of the dataset I have used.

Coding wise, VCDS seems to get confused when coding 2Q0(it shows more than 8 bits per Byte o_O).

VCP works 100% problem free, see coding show below -> 5294C4A0
Btw, which position of radars you used on your car, plugs inside or outside?
If plugs turned inside then data set for Tiguan may fit
If outside then data set for Passat (that's my case I guess, see photo)

And the error about missing electric steering somehow could be shut or not?

photo_2024-03-22_00-59-33.jpg
 
Btw, which position of radars you used on your car, plugs inside or outside?
Radar connectors pointing outwards.
The same as @n10n setup below.
Radars attached and loom routed to cargo area.

Couldn’t find such posture for brackets that they wouldn’t bob at all in any direction so in the end I just searched the position of minimal bobbing and popped the brackets there.

I think at least in vertical direction the autocalibration has to be pretty forgiving as the tail height might vary pretty wildly depending on wheels, cargo weight, suspension etc.

Edit: drill the lowest bracket attachment point very carefully, there’s about 1cm gap and another sheet of metal, very easy to scratch that by pushing too much

View attachment 195283
View attachment 195284

And the error about missing electric steering somehow could be shut or not?
I guess you are reffing to 1K8 PDC module.
This fault is still present. I really didn't have time but the challenge is to crack down PDC data set and change the source of steering angle data from module 16 to 04.
 
challenge is to crack down PDC data set and change the source of steering angle data from module 16 to 04

:thumbsup: Oh my, hadn’t even thought about this… but I had a bypassing thought about what would happen if an entrepreneous little device like ESP32 or Raspberry PI would echo all CAN messages received from module 04 as if it was module 16 :whistle:
 
Last edited:
Who is going to guess what I will be doing this evening?

View attachment 70579
Have you finally changed all 4 sensors with ABS last Byte coding 0xF0 or just rear sensors with conding 0x50?
This fault is still present. I really didn't have time but the challenge is to crack down PDC data set and change the source of steering angle data from module 16 to 04.
Looked through 1K8919472C xml data set file searching 0x16 (match 4 times), not sure which one to change for 0x04 ))

I also have info that mZAS message is about klemmers that switched-on at the moment (ignition key position), so the Gate should generate id572 packet to CAN-drive.
It is PQ35 feature, but not PQ25
 
Last edited:
I also have info that mZAS message is about klemmers that switched-on at the moment (ignition key position), so the Gate should generate id572 packet to CAN-drive.
It is PQ35 feature, but not PQ25

Interesting, thank you! If it's only about terminal status it should be fairly straightforward to generate such a packet and send it repeatedly to keep PDC happy.

I will definitely try this at some point, no promises about when though.

EDIT: can confirm 0x572 (1394) message is not present in T6 drivetrain or convenience CAN buses
 
Last edited:
Back
Top