Seat Leon Cupra MY19 - ACC Retrofit
- Thread starter stefan147
- Start date
- Status
Calibration was done remotely by the guy that activated the radar (I think he just copies some values according to the model). And it worked fine for a week or so but then yesterday I got a warning and a fault for misalignment. All this having done just 200-250km since we have a lockdown here.
Anyway I did the calibration successfully after a few attempts with ODIS and without touching the two screws on the radar housing. The guy suggested I go in front of a straight wall with 2.5m distance from the wheel centers and then run the ODIS procedure. Thing is that the manual suggests 1.2m from the radar to the calibration mirror so I went with the manual plan. Fortunately ODIS was not so picky and did the calibration as soon as I placed my "mirror" correctly. That's good and bad at the same time because I would like a safety feature like this to be calibrated to factory standards and not randomly in a house parking spot. For the record my calibration set up was this (that's a dishwasher part) -->
dnd roll
Anyway I did the calibration successfully after a few attempts with ODIS and without touching the two screws on the radar housing. The guy suggested I go in front of a straight wall with 2.5m distance from the wheel centers and then run the ODIS procedure. Thing is that the manual suggests 1.2m from the radar to the calibration mirror so I went with the manual plan. Fortunately ODIS was not so picky and did the calibration as soon as I placed my "mirror" correctly. That's good and bad at the same time because I would like a safety feature like this to be calibrated to factory standards and not randomly in a house parking spot. For the record my calibration set up was this (that's a dishwasher part) -->
dnd roll
So a new windscreen was fitted and the A5 camera took its place. Golf parameters were uploaded and all faults were erased except for the expected "missing Calibration" fault. Time for ODIS then and the VAS6430 board...calibration was done "successfully" in the very first time and all faults disappeared and then I took the car for a short test drive. For the first time Lane Assist could be selected from the menu but the lane sign remained yellow. I thought it might need the dynamic calibration in order to get fully functional but after a few miles I got a "Lane Assist not available" warning. The scan showed this:
So I'm guessing I need to repeat the static calibration, right? Is it one of those faults that may go away on its own? Probably not...
Code:
Address A5: Frt Sens. Drv. Assist (R242) Labels:| 3Q0-980-65X-A5.clb
Part No SW: 3Q0 980 654 H HW: 3Q0 980 654 A
Component: MQB_B_MFK H09 0272
Serial number: 20091815P24296
Coding: 0303070300000405002213448150A90098000E200020
Shop #: WSC 00020 999 12345
ASAM Dataset: EV_MFKBoschMQBB 001001
ROD: EV_MFKBoschMQBB_001_SE37.rod
VCID: 3C20C126F6E713CB4EB-8068
1 Fault Found:
0662 - Dynamic Calibration
C1106 F0 [009] - Limit Exceeded
[Online_calibration_out_of_range]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 4
Fault Frequency: 1
Reset counter: 105
Mileage: 28491 km
Date: 2020.11.29
Time: 12:12:42
Control Module temperature: 35 °C
Outside air temperature: 17.0 °C
Vehicle speed: 0.00 km/h
System run time: 682.8 s
Voltage terminal 15: 14.1 V
mid: 00 1D
Status of camera: limited
Engine_Running_Info: 1
Software_Info_4: 2
Software_Info_3: 7
Software_Info_2: 2
Software_Info_1: 0So I'm guessing I need to repeat the static calibration, right? Is it one of those faults that may go away on its own? Probably not...
Last edited by a moderator:
I repeated the calibration, this time paying some more attention to the numbers. It seems that ODIS is not very picky and just calibrates successfully within a reasonable range of measurements. I checked with a friend with a Passat who has done the same retrofit and he said that the most crucial number is that of pitch angle and so I run a couple of fine tuning calibrations in order to get as close to 0 as possible.
Camera height was never asked for. Just the 4 corners height. It seems that it calculates the exact camera height on its own. Of course I knew the camera height in order to place the board but the exact height was given after calibration.
Finally I did a 30km test drive, mainly highway, and everything seems to work fine. The car is kept in place between the lanes, acc has become a bit more accurate and traffic sign recognition is on point. I may have a HBA issue but I couldn't find the necessary conditions to test it properly. As soon as I make sure that everything is working perfectly under all circumstances I will post a new detailed scan.
Camera height was never asked for. Just the 4 corners height. It seems that it calculates the exact camera height on its own. Of course I knew the camera height in order to place the board but the exact height was given after calibration.
Finally I did a 30km test drive, mainly highway, and everything seems to work fine. The car is kept in place between the lanes, acc has become a bit more accurate and traffic sign recognition is on point. I may have a HBA issue but I couldn't find the necessary conditions to test it properly. As soon as I make sure that everything is working perfectly under all circumstances I will post a new detailed scan.
- Joined
- May 27, 2017
- Messages
- 3,357
- Reaction score
- 2,100
- Location
- Finland
- VCDS Serial number
- C?ID=280813
I think the camera height is on the parameters.
As per my understanding you have fixed camera position height. Let's say 1400mm. Then you measure the wheel arch heights and that creates and offset it takes into account in the calibration. So the wheel arch height measurements makes sure that if the car has been lowered, raised or whatever, that is taken into account.
Very nice setup for the ACC calibration
As per my understanding you have fixed camera position height. Let's say 1400mm. Then you measure the wheel arch heights and that creates and offset it takes into account in the calibration. So the wheel arch height measurements makes sure that if the car has been lowered, raised or whatever, that is taken into account.
Very nice setup for the ACC calibration
Indeed! Great setup! 
But what can you do? I went to the dealership to replace the windscreen and of course I asked if they would calibrate my ACC & Lane Assist system and the answer was a big fat NO since they are not factory installed. So I will have to bear with these homemade patents until I find a professional with the right equipment.
So question now is...should I bother and upgrade the A5 sw to the letter L? It seems that 3Q0980654H is the last Gen2 sw and after that is 654L and it's Gen3 sw. What's not clear to me is if the L supports TJA (which the H does and I want it). Any other serious improvements I should know of?
Also pACC is under SWaP or is it just coding? I haven't found anything on this and of course the hackers ask for more money about it.
But what can you do? I went to the dealership to replace the windscreen and of course I asked if they would calibrate my ACC & Lane Assist system and the answer was a big fat NO since they are not factory installed. So I will have to bear with these homemade patents until I find a professional with the right equipment.So question now is...should I bother and upgrade the A5 sw to the letter L? It seems that 3Q0980654H is the last Gen2 sw and after that is 654L and it's Gen3 sw. What's not clear to me is if the L supports TJA (which the H does and I want it). Any other serious improvements I should know of?
Also pACC is under SWaP or is it just coding? I haven't found anything on this and of course the hackers ask for more money about it.
- Joined
- May 27, 2017
- Messages
- 3,357
- Reaction score
- 2,100
- Location
- Finland
- VCDS Serial number
- C?ID=280813
I've upgraded my 3Q0 980 654 H to L index and works fine. There's also dataset available with TJA for it (At least for Tiguan there was).
L has much improved lane tracking over H. I think that's the biggest improvement on it. But remember, if you go to L, you cannot go back to H. It will brick the HW.
And pACC is SWaP to my knowledge. There are coding options on the radar for predictive route data and traffic signs but they don't work.
And interesting that your dealers are not interested in calibration. If the devices are per factory standard installed, they shouldn't care. Here they've calibrated my retrofit ACC just fine, no objections or complaints about it.
L has much improved lane tracking over H. I think that's the biggest improvement on it. But remember, if you go to L, you cannot go back to H. It will brick the HW.
And pACC is SWaP to my knowledge. There are coding options on the radar for predictive route data and traffic signs but they don't work.
And interesting that your dealers are not interested in calibration. If the devices are per factory standard installed, they shouldn't care. Here they've calibrated my retrofit ACC just fine, no objections or complaints about it.
So I did another test drive now. I have a fault that keeps coming back. If I erase it everything works great but if I turn off/on the car then it's back and causes ACC & Lane Assist unavailable.
It's this:
Any ideas? It appears with a TSR fault on the VC but I cannot understand if TSR is causing it or it's just there because of limited functionality of camera. TSR is coded to "fusion" since I got MIB2 Navi STD.
It's this:
Code:
Address A5: Frt Sens. Drv. Assist Labels: 3Q0-980-65X-A5.clb
Control Module Part Number: 3Q0 980 654 H HW: 3Q0 980 654 A
Component and/or Version: MQB_B_MFK H09 0272
Software Coding: 0303070300000405002213448150A90098000E200020
Work Shop Code: WSC 00020 999 12345
ASAM Dataset: EV_MFKBoschMQBB 001001 (SE37)
ROD: EV_MFKBoschMQBB_001_SE37.rod
VCID: 3C20C126F6E713CB4EB-8068
1 Fault Found:
1293 - Camera Interference
C1104 00 [009] - -
[Imager_A_BIST_error_on_Zynq_0]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 4
Fault Frequency: 1
Reset counter: 108
Mileage: 28560 km
Date: 2020.11.30
Time: 12:41:44
Control Module temperature: 40 °C
Outside air temperature: 15.5 °C
Vehicle speed: 0.00 km/h
System run time: 2.8 s
Voltage terminal 15: 11.6 V
mid: 00 30
Status of camera: operational
Engine_Running_Info: 0
Software_Info_4: 2
Software_Info_3: 7
Software_Info_2: 2
Software_Info_1: 0Any ideas? It appears with a TSR fault on the VC but I cannot understand if TSR is causing it or it's just there because of limited functionality of camera. TSR is coded to "fusion" since I got MIB2 Navi STD.
Haven't tried that yet. Waiting to see if it's known fault with a known solution although I haven't found anything on my search.
Next thing I try will be to deactivate TSR from everywhere and see what happens but then again I can't think of anything that could disturb TSR with the existing coding.
Next thing I try will be to deactivate TSR from everywhere and see what happens but then again I can't think of anything that could disturb TSR with the existing coding.
- Joined
- May 27, 2017
- Messages
- 3,357
- Reaction score
- 2,100
- Location
- Finland
- VCDS Serial number
- C?ID=280813
Faulty camera hardware. Let me guess, you bought it from a Polish dealer in eBay?
Quote from another forum :
I've already bought at least 30 of the cameras and until the penultimate one I never had a problem. The last 2 plus the replacement camera from today that I bought all had a problem but was the first from another dealer. A few weeks ago a friend of mine had bought a camera from Poland with the same problem. Seems to be a series, the defective parts must come from somewhere
This person has been vouched to be a reliable seller : https://www.ebay.co.uk/usr/miguelgilito
But unfortunately he doesn't have 3Q0 cameras in stock at the moment.
I did buy it from a Polish dealer but not from Ebay. I bought it from Allegro. But I dont't get it...this was a used camera from a T-Roc, how can it be faulty hw? Maybe I should go for a 654L straight away if I need to replace it.
Before ordering a new camera, any other ideas for the fault?
Before ordering a new camera, any other ideas for the fault?
- Joined
- Dec 16, 2014
- Messages
- 8,044
- Reaction score
- 7,873
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
Why did they replace the camera on the T-Roc? Because the camera was faulty, because the T-Roc was scrapped, some other reason???
Of course these might be the cases but I always thought scrapped car thus OK camera. Anyway I start searching for new and preferably from Greece so I can be in touch with the dealer easier in case of a problem.
- Joined
- May 27, 2017
- Messages
- 3,357
- Reaction score
- 2,100
- Location
- Finland
- VCDS Serial number
- C?ID=280813
Fab254 as the seller?
They replace faulty cameras at VW and for some reason these replaced cameras end up in circulation through the used market, and in Poland usually. This is only hearsay now, I cannot verify that naturally with proof. But there's been many threads on this problem on the other forum with the same failure.
I've certainly seem a similar theme with Skoda Octavia 9.2" Columbus screens.
There is a hardware issue that causes vertical lines to appear on them, the TPI states they should be replaced with a new display. Now eBay is filled with the rejects that have been replaced...
Oh - actually I just remembered, Skoda TPI 2049715/6 relates to fault A5 cameras so I imagine there is a matching VW and Seat TPI:
Given the faulty units are replaced, that could be a likely source for your camera
There is a hardware issue that causes vertical lines to appear on them, the TPI states they should be replaced with a new display. Now eBay is filled with the rejects that have been replaced...
Oh - actually I just remembered, Skoda TPI 2049715/6 relates to fault A5 cameras so I imagine there is a matching VW and Seat TPI:
Given the faulty units are replaced, that could be a likely source for your camera
OK that explains a lot. This forum is so helpful as always! Thanks!
I will be looking for a 654L then with a manufacture date after July 2019 to be as safe as possible. I have also found datasets for Golf and Leon for this camera so I should be OK given that I have a good one.
I will be looking for a 654L then with a manufacture date after July 2019 to be as safe as possible. I have also found datasets for Golf and Leon for this camera so I should be OK given that I have a good one.
So I'm trying to understand if HBA coding is OK but I can't get myself in the proper conditions although I suspect that it should have worked a couple of times. Is this correct for a Leon with simple LED front lights?
(sorry for the format but it's the most recent scan I got)
(sorry for the format but it's the most recent scan I got)
Last edited by a moderator:
- Status