which basically means that you need to change your bits 4 and 6 from 0 to 1.
Thank you!
(Side Assist) / (Blind Spot Detection & Rear Cross Traffic Alert) retrofit
- Thread starter Robert
- Start date
Thank you!
And final thing is coding.
CAN gateway 19 installation list:
add 3C
then enter
Side Assist 3C and apply the following coding:
030311 for vehicles with trailer
030321 for vehicles without trailer
There is also LHD and RHD selection which effectively allows for handy mirror lights functionality swap-over just in case their wiring got mixed up during installation
Can you please tell me your Coding for the 5Q0 Sensor
LED illumination is a good indication and yes calibration indeed starts automatically.
Also you can check the progress of your dynamic calibration in Advanced Measuring Values.
So my suggestion is, take your vehicle for a good drive(maybe Autobahn
) for let's say 50km and see if your calibration has completed.Remember every time you change the coding calibration starts again.
There is another useful piece of information.
On higher range of ICs "RTA & BSD" grey out (become unavailable) if there is any serious fault in the system.
But on lower range of ICs "RTA & BSD" both actually disappear from Assistant Menu.
Credit to @mmi for help in working this out.
Last edited:
Yes they disapper at my IC after turn on ignition and first come when i delete the fault code.LED illumination is a good indication and yes calibration indeed starts automatically.
Also you can check the progress of your dynamic calibration in Advanced Measuring Values.
So my suggestion is, take your vehicle for a good drive(maybe Autobahn
Remember every time you change the coding calibration starts again.
There is another useful piece of information.
On higher range of ICs "RTA & BSD" grey out (become unavailable) if there is any serious fault in the system.
But on lower range of ICs "RTA & BSD" both actually disappear from Assistant Menu.
Credit to @mmi for working this out.
After turn off and on ignition again it is gone in IC again...
I will do a test ride and see if callibration will be finished.
Thank you Robert for your Information!
A bit curious about this. Indeed the both revisions 0080 and 0081 have been on the master software 5Q0907686C. Interestingly I can't find any flashfile for the slave 5Q0907685C alone - are they flashed as a pair? (so all would have been included in master -686 package??)
How do you try to start the calibration - VCDS adaptations? I'm asking as I can't run even output tests on VCDS - either correct procedures are not in place in the VCDS or I have associated wrong label-file for the 3C (a derivative of VW37). However, OBDeleven runs the output tests without errors.
Anyways, I didn't initiate the calibration - it completed itself somewhere in range of 50-80 km's. Here's a screenshot somewhat before that. Van parked, thus blind spot detection passive and steering wheel angle "steep'ish".
EDIT: My setup at the moment. LWB, LHD, trailer capable.
Last edited:
I also tried this coding on mine and when I changed ABS Byte 18 to hex 50 without replacing the actual rear sensors I got these two faults (as expected
).Thanks @dnoermann for your fabulous work. I am pretty sure that decoding of MK100 ABS cost you a lot of time and effort, well done
!
Do the calibration needs to be done in one time or can it be done in parts?
I drove about 20km today and Live Data in Obdeleven said:
3 km Master
0% Slave
2% Distance of object 4
I tried with Odbeleven, the Output test was working well
I bought mine on ebay seperate, not as a pair. The Master(Software 81) was brand new and the Slave(Software 80) used.
Do I have to flash something here so that they work as a pair?
C was never made for PQ - only for MQB
so you must downgrate them to B + proper data set
Are you shure?
I can chooce in Coding of 5Q0907686C between Vehicle Class MQB, PQ35 or PQ35LC
look to ETKA
I did the calibration in parts - I think it was total of 3-4 drives before it was complete 2 x 100%. I saw no change in first 20 km (=all stayed at "0"). I think it is a good sign that you already have some non-zero values. Also the "x km Master" counts up much slower than actuals kms - the same is seen on OEM installed modules (in a Skoda Octavia).Do the calibration needs to be done in one time or can it be done in parts?
I drove about 20km today and Live Data in Obdeleven said:
3 km Master
0% Slave
2% Distance of object 4
I tried with Odbeleven, the Output test was working well
I bought mine on ebay seperate, not as a pair. The Master(Software 81) was brand new and the Slave(Software 80) used.
Do I have to flash something here so that they work as a pair?
MIne came as a pair (as above both with software -C) both with same software revision 0081 - so can't say anything about the "mismatch 0080/0081".
I also have revision C and it works 100% on PQ25 when PQ35 is selected.
...something is wrong with my system.
Today a 30km drive:
4 km Master
0% Slave
4% Distance of object 4
km Masters starts again at 0, Distance starts at 2%
I now order a Slave with Software 0081...
Today a 30km drive:
4 km Master
0% Slave
4% Distance of object 4
km Masters starts again at 0, Distance starts at 2%
I now order a Slave with Software 0081...
What are those parametisation Files? Do I have to upload it to my brand new Master first? Is this my mistake?
