Blind spot monitoring looks like a mirror upgrade and behaves like a bumper-off job. On MQB cars the two radar slaves sit behind the rear bumper skin, talk on the extended CAN bus, and report to a control module at address 3C that most cars never had coded. What follows is the order of work: kit contents, mounting geometry, the wiring that catches first-timers, and the coding sequence that stops the cluster from filling with fault lamps.
Why the Bumper Has to Come Off
Side Assist is a radar system, and radar needs a defined aperture. The two sensors are mounted low in the rear bumper carrier, angled outward at roughly 45 degrees, so they can see the blind spot beside the rear door and the lane behind it. There is no equivalent shortcut through the tail light cavity, and no version of this retrofit works with the sensors behind a trim panel.
The good news is that most MQB rear bumper carriers are stamped for both configurations, so the bracket bolts to existing bosses even on a car that left the factory without the option. Check that before you buy anything: aftermarket bumper skins and insurance repair sections sometimes omit the bosses entirely, and a bumper with no mounting points turns a four-hour job into a fabrication job.
One more constraint that gets ignored: radar-transparent paint. Metallic and metal-flake refinish layers attenuate the signal enough to cause intermittent dropouts, and a skin that has been repaired with metal reinforcement mesh will block the sensor outright.
What the Kit Contains, and What It Does Not
A proper kit is two radar units, a left and a right, plus the sub-harness that links them and runs forward to the CAN splice. The Golf 7 kit built around 5Q0907685 and 5Q0907686 follows that pattern, and the Audi A3 8V kit using 4G0907566M and 4G0907568M does the same for the PQ35-derived A3 electrical platform. Both are master and slave pairs, and the two units are not interchangeable side to side — the connectors and the internal addressing differ.
What a kit almost never contains: mirror caps with the warning lamp, the lamp pigtails, door harness sections, and the gateway. If your car has base mirrors with no lamp aperture, budget for caps or complete mirror assemblies. If you are already planning power folding, the Golf 8 folding mirror set is the point where the two jobs overlap, and both share the same door card removal.
Mounting the Slaves
Bolt the brackets down before you run any wiring. Three things decide whether the system will ever report clean angles: bracket flatness, bracket torque, and clearance to metal.
- Torque the bracket bolts to spec and in sequence. A bracket pulled down on one corner tilts the sensor by a degree or two, which is enough to throw the angle reading out of tolerance.
- Never shim a bent bracket. The sensor has no software offset large enough to compensate, and a shimmed bracket is a permanent intermittent fault.
- Keep roughly 100 mm of clear space around the sensor face. Tow bar brackets, parking sensor wiring and aftermarket reversing camera looms routed through the same area all show up as reduced range.
- Do not paint the sensor face or wrap it in anti-stone film. The housing is sealed; the face is not a surface to be protected.
Wiring: Fused Supply, Extended CAN and the Lamp Circuit
Three circuits matter. The supply is terminal 15 through a fused feed, not a permanent live tapped from the tail light. The bus is the extended CAN pair at the gateway, twisted, with the splice kept short. The lamp circuit is the one that varies by platform: on some cars the warning LED in the mirror is driven by the door control module at address 42 or 52, on others the kit harness carries the lamp signal forward to the A-pillar connector and the door module only has to be coded to accept it.
Whatever the platform, do not run the radar sub-harness alongside the trailer module wiring or the rear camera coax. Induced noise on the CAN pair produces exactly the symptom people misdiagnose as a failed sensor: “side assist currently unavailable” every few minutes, no stored fault in 3C.
Coding Order That Works
Order matters more than the individual bits. Do it in this sequence and you avoid the loop where 3C refuses coding because the gateway has not accepted it yet.
- Address 19, gateway installation list: tick 3C. If the gateway is a base unit that does not carry the extended bus, this is where the job stops. A 3Q0907530AC Highline gateway is the usual fix on MQB, and the BCM and gateway activation service exists precisely because the coding half is often sold separately from the hardware.
- Address 3C: long coding for body style, left or right hand drive, and whether a trailer module is fitted. Trailer coding is not cosmetic — an uncoded tow bar makes the system mute itself whenever the trailer socket sees a load.
- Address 17: enable the assistant menu so the driver can actually turn the system off.
- Address 5F: enable the display bits if the head unit is to show the warning graphic.
- Address 09: set the lane change assist installed bit. On cars using a 5Q0937084DH BCM this bit is what tells the body computer the lamps exist; without it the LEDs stay dark even though 3C is happy.
Then clear faults in 3C, 09, 19 and both door modules, cycle terminal 15 off and back on, and re-read. Faults that survive a terminal cycle are real; faults that clear were coding order artefacts.
Angles, Not Calibration Boards
Contrary to a lot of forum advice, there is no VCDS-side alignment routine for 3C on these platforms. The sensors are aligned mechanically by the bracket, and the module reports the horizontal and vertical angle in its measuring blocks. After a straight 200 m drive on a level road the values should sit close to zero and match left to right within a small window.
If one side reads outside tolerance, the bracket is bent, the carrier is deformed, or the wrong side sensor is fitted. Replace the mechanical part; do not attempt to correct it in software. If both sides read clean but the system still refuses to arm, re-check the body style coding before you suspect the hardware.
Failure Modes You Will Actually Meet
- 3C does not communicate. CAN pins swapped in the sub-harness, or a gateway that never had the extended bus populated. Check the installation list before chasing the sensor.
- Lamps on permanently. Door module not coded for the lamp circuit, or the LED pigtail landed on the illumination pin instead of the signal pin.
- Works on one side only. Master and slave harness connectors swapped. They will plug in, and they will not work.
- Intermittent in rain and cold. Usually genuine blockage — dirt film, snow, or a bike rack. Clear the skin and re-test before quoting a sensor.
- Menu missing in the cluster. Coding in 17 not written, or written while 3C was still reporting a fault, which causes the cluster to drop the menu on the next terminal cycle.
Can I fit Side Assist to a car with base mirrors?
Yes, but the caps have to change. The warning lamp needs a moulded aperture and a reflector; a solid cap cannot be drilled cleanly enough to look factory, and the lamp will wash out in daylight. Price the caps or the complete mirror assemblies into the quote before you commit to the job.
Do I need a Highline gateway for Side Assist?
Usually yes. The radar pair sits on the extended CAN bus, and base gateways on MQB frequently do not populate it. Confirm by reading the gateway part number and the installation list on the actual car rather than by model year, because VAG mixed gateway levels within the same production year.
Will the dealer refuse to code a retrofit?
Some will, some will not, and it depends on the market. The coding itself is ordinary long coding and adaptation, not a security-relevant function, so an independent shop with VCDS or ODIS can complete it. The one step that may need online access is a later firmware flash if the gateway needs a newer dataset to offer 3C in the installation list.