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

[n10n]

Weather will still be way too awful to start the retrofit installation for the foreseeable future, will be doing it outdoors.

However now I should have most everything sourced plus done some bench testing, setup in picture above, mainly to verify my 2nd hand modules actually work. I seem to be able to talk to them with VCDS just fine, although it complains about missing rod files. The modules are from t-roc apparently, no idea at this point if I will need different parameters or not, but I guess I’ll find out eventually

 

[n10n]

Baby steps… added PDC module today. Quick random coding and no errors. OPS and auto mute on P works (this is a life saver really!) but auto activation on approach does not. Or maybe I should go on a drive first, this was a quick test moving the car just couple of meters back and forth.

 

[Robert]

Have you got it ticked in your Instrument Cluster settings menu?

 

[n10n]

Have you got it ticked in your Instrument Cluster settings menu?

Thanks @Robert, I had that ticked actually and with little bit more testing seems the auto activation does work although it didn’t seem like that yesterday evening.

Two things in play:

1. I had totally forgotten I’ve blocked two middle front sensors due to light bar (Deactivating front parking sensors?). That obviously reduces the sensitivity seriously as relying mostly on corner sensors :facepalm:

2. Still, #1 doesn’t completely explain why I get detection if I manually enable OPS but not always in auto mode - it looks like there’s some threshold levels, eg if I park relatively quickly it seems to enable OPS much more easily than crawling in.

Anyway, it’s all good . I think relocating the front middle sensors should be the first step if I wanted to improve the automatic activation reliability.

 

[n10n]

Today, while switching from winter to summer tyres I decided to quickly swap the ABS sensors to bidirectional ones on the same go. Or so I thought. Few hours and some intense dremel action later I have one of them swapped and had to give up on the other one for the day. Not so Good Friday. I'm not sure why VW bothers with the screw at all, these things are rock solid in place even from new, could just spare couple of cents there...

Not sure yet if I will need to remove brake shield to get a better attack angle with a proper drill tomorrow. Anyhow, I will spend rest of the evening thinking how I would rank this job in Maslow's hierarchy of needs

 

[n10n]

Not sure yet if I will need to remove brake shield to get a better attack angle with a proper drill tomorrow.

Got that son of a … finally . I for sure hope I don’t need to redo this anytime soon, I’m pretty sure I would not be able to get the brand new sensors out in one piece even today.

ATE 360330/360331 sensors seem to work fine

 

[n10n]

On to the scary part

7LA937147/8 T6.1 brackets do not sit well with positioning that came with Kufatec instructions - I guess those would be for earlier modules and brackets. These brackets seem to want to go 4 cm lower… hope the auto calibration forgives me!

 

[n10n]

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

 

[n10n]

Who has left such a mess to my BCM area?

Seems I have to do bit of spring cleaning here before adding yet another lump of wires

 

[n10n]

Need a bit of guidance here.

2Q0 modules installed into vehicle and added 3C to gateway list. I can read the modules, there’s 6 static databus missing message errors U112100. When I try to clear the errors both side assist leds glow amber for a bit but errors remain - I believe wiring is good though.

I tried to code the modules, especially vehicle class is now MQB KI15. Attempted to change it to PQ35 without and with Security Access, no success - OBD11 says function not available to this and other codings.

I can ofc use VCDS to interrogate more, and I have never used VCP available as well. But my question is do you guys think this is a parameter issue or something else?

Thanks, any tips appreciated!

 

[mmi]

My guess is the main issue for the databus errrors is the MQB/PQ35 discrepancy.
I would try VCDS to change the coding to PQ35.

 

[n10n]

Unfortunately could not code it with VCDS either, request out of range errors. I guess this means I need to change something else in addition to the vehicle class for it to be compatible with PQ25 ie something in existing coding prevents reapplying. I tried to change the automatic emergency braking function as it was set.

Do you think resetting to factory settings could help? I'm on to googling for possible codings now

Sunday,16,April,2023,20:52:08:11176
VCDS Version: Release 23.3.0 (x64)
                Address 3C: Lane Change
Control Module Part Number: 2Q0 907 686 B
  Component and/or Version: HRE3_Kl15_Mst H06 0150
           Software Coding: 62954620
            Work Shop Code:
                      VCID: B924C58EB9DBA84288D-80ED

Advanced Identification/FAZIT
     Serial number: 14520003843805
     Identification: HLV-HLT
     Date: 09.09.20
     Manufacturer number: 6CD2
     Test stand number: 2965
Flash Status
     Programming Attempts(application): 1/1/0/0/1
     Flash Date: 00.01.01
Misc.
     Hardware number: 2Q0 907 686 B
     Workshop System Name: J1086
     Dataset Number: V03935322RL
     Dataset Version: 0001
     ASAM Dataset: EV_HREntryHellaGen3Kl15
     ASAM Dataset Revision: 002001
VCDS Info:
       VCID: B924C58EB9DBA84288D-80ED
       Labels: NONE
       ROD: EV_HREntryHellaGen3Kl15_002_VW27.rod*

 

[mmi]

Unfortunately I don't know.
Anyways, for future reference a bunch of scans from vehicles equipped with 2Q0 907 686 B -

Google Search

 

[n10n]

Unfortunately could not code it with VCDS either, request out of range errors. I guess this means I need to change something else in addition to the vehicle class for it to be compatible with PQ25 ie something in existing coding prevents reapplying. I tried to change the automatic emergency braking function as it was set.

Coding mystery turned out to be relatively simple issue. As opposed to most modules where you can just flick the bits these modules seem to require you always write full coding and then it's accepted. Also, reading back the coding is different to what was just written so I think some of bits are used as a sort of "checksum" or confirmation the write data is correct.

I got many 3C errors go away by reconnecting the rain and light sensor and minimizing all other module errors I had due to having bunch of modules, switches, airbag etc not connected.

So, currently I'm having a coding which at least has PQ35 part right but might miss on towing hook etc and down to one error on 3C for which there doesn't seem to be much known by the internet. But being ESP -related I suspect something is newer in T-Roc where my 2Q0 modules are from.

Friday,21,April,2023,17:18:37:11176
VCDS Version Release 23.3.0 (x64) Running on Windows 10 x64(VMWare)
www.Ross-Tech.com

                Address 3C: Lane Change       Labels: None
Control Module Part Number: 2Q0 907 686 B    HW: 2Q0 907 686 B
  Component and/or Version: HRE3_Kl15_Mst H06 0150
           Software Coding: 5294C4A0
            Work Shop Code:  
              ASAM Dataset: EV_HREntryHellaGen3Kl15 002001 (VN75)
                       ROD: EV_HREntryHellaGen3Kl15_002_VW27.rod*
                      VCID: B924C58EB9DBA84288D-80ED
1 Fault Found:

2232343 - Databus
          U1121 00 [009] - Missing Message
          [databus message missing - ESP_33]
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 4
                    Fault Frequency: 1
                    Reset counter: 40
                    Mileage: 71955 km
                    Date: 2061.14.26
                    Time: 22:41:09

Also, on PDC module I have the "expected" error mentioned somewhere earlier in the thread - did anyone ever find a fix for this one?

Address 10: Park/Steer Assist (J446)       Labels:| 5Q0-919-294.clb
   Part No SW: 1K8 919 472 C    HW: 5Q0 919 294 A
   Component: PARKHILFE 8K  H03 0480
   Revision: --------    Serial number: 39361714406064
   Coding: 0051151151
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_EPHVA18VW364GP00 001007
   ROD: EV_EPHVA18VW364GP00_VW32.rod
   VCID: B720C3B68FCFBE327E9-80E3

1 Fault Found:
12718592 - Databus
          U1121 00 [009] - Missing Message
          [Steuergerät für Lenksäulenelektronik-J527/BCM - mZAS_1 - kein Signal/keine Kommunikation]
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 197
                    Mileage: 71955 km
                    Date: 2023.04.21
                    Time: 23:04:24

 

[Robert]

Have you tried this coding?

5294C420

Address 3C: Lane Change Labels: None
Control Module Part Number: 2Q0 907 686 B HW: 2Q0 907 686 B
Component and/or Version: HRE3_Kl15_Mst H06 0150
Software Coding: 5294C4A0

Quite alike, quite close

 

[n10n]

Quite alike, quite close

Thanks, quite close indeed.

I collected every coding I was able to find and have been trying to find the magic one that would be right for me - no luck yet. That’s why I now sort of lean towards either parametrization or some other component in the vehicle being the culprit.

This is the full set I’ve played with:

• A2954640 (T6.1 Help T6.1; Loads of fault Codes unable to clear!)
• 5294C420 (Robert’s suggestion)
• 52A54640 (Passat Variant B8)
• 62954640 (Touran, Superb 3)
• 52954CA0 (Tiguan)
• 92A54640 (Seat Ateca)
• A2A54640 (Tiguan R)
• 5294C640 (Tiguan)
• 92954620 (T Cross Life)
• 92A54640 (Tiguan R)
• 92954640
• 62A54640 (Seat Tarraco)
• 5294C4A0 (Passat PQ35)
• 5294C620 (Jetta GLI)

 

[Fluff34567]

Anyone here that's changed from blind spot to cross traffic and willing to sell the RH side blind spot module?

 

[n10n]

Holy s**t BSD is actually working in a complete surprise!

Yesterday, I was updating random parameter files to the radars and playing with their coding as yet another attempt to solve that ESP_33 communication issue. I hadn’t even considered the system working to any extent as the leds don’t light up on ignition.

Anyway, this morning on motorway lo and behold, yellow lights start to light up - hooray!

Seems my left radar (right handed traffic so offside for me) works perfectly. Right one is a bit of hit and miss, I noticed passing other cars it lights up maybe 50% of time.

Great to have something working and I think it’s just the RCTA I have an issue with - this is definitely something I can live with at least for time being.

 

[Robert]

Holy s**t BSD is actually working in a complete surprise!

Yesterday, I was updating random parameter files to the radars and playing with their coding as yet another attempt to solve that ESP_33 communication issue. I hadn’t even considered the system working to any extent as the leds don’t light up on ignition.

Anyway, this morning on motorway lo and behold, yellow lights start to light up - hooray!

Seems my left radar (right handed traffic so offside for me) works perfectly. Right one is a bit of hit and miss, I noticed passing other cars it lights up maybe 50% of time.

Great to have something working and I think it’s just the RCTA I have an issue with - this is definitely something I can live with at least for time being.

Have you already tried to set Byte 16 bit 7 to 1 for "RCTA with brake intervention" in ABS Coding?

 

[n10n]

Have you already tried to set Byte 16 bit 7 to 1 for "RCTA with brake intervention" in ABS Coding?

Thanks so much @Robert, this was the missing bit!

I had ofc looked at 18-byte MK100 ABS codings but did not find anything in relation to RCTA - so, once again, thank you!





Also thanks for everyone who have contributed to this thread over the years - it’s easy standing on the shoulders of giants. I wouldn’t ever had come up with the idea without this thread.