How to install Sagitar IQ.Light tail lights on a MK7 Jetta

Written by the EuroCustomAutos workshop — Mississauga, ON. Last updated August 2026. We fit and code Sagitar IQ.Light conversions for customers across the GTA.

Why this one is different

The Sagitar is Volkswagen's Chinese-market Jetta, and the facelift got the IQ.Light treatment North America never received — an X-shaped illuminated signature, amber sequential signals and a startup animation. This is that exact conversion, and it's a four-piece job: the two outer lights plus two inner trunk-lid pieces that replace the blank filler panels your Jetta came with. That second pair is what turns the rear into one wide connected signature instead of two lamps at either end.

Mechanically it's one of the easier retrofits we do. The harness is plug-and-play — no de-pinning, no repinning, no cut wires. What the job really asks of you is the coding. Every rear lamp position has to be told what it now is, what load type it draws, and which fault byte belongs to it, and then the sweep has to be switched on in six separate parameters. Get the coding right and every function works; get one channel wrong and you'll be chasing a bulb-out warning or a signal that flashes on both sides at once. The tables below are the complete list.

Tools you'll need

• VCDS or OBDeleven — not optional on this install. Every value in Steps 4 and 5 goes in with one of these.
• Trim removal tools — for the trunk panels that cover the tail light harnesses
• Basic automotive electrical knowledge — you'll be pinning terminals into a connector by wire colour
• Electrical or cloth tape for tidying the loom on reassembly

What's in the box

• 2 × outer tail lights — these replace your factory lamps in the quarter panels
• 2 × inner trunk-lid pieces — these go where your blank filler panels are now, and carry the white LED reverse lights
• Inner and outer adapter harnesses — supplied de-pinned and wrapped in protective tape so they route cleanly
• 3-pin connectors — one per side, for joining the inner and outer harness wires by colour

Count everything against this list before you start. A missing connector is much easier to deal with before the trunk is in pieces.

Step 1 — Preparation

1. Turn the vehicle ignition off.
2. Open the trunk and carefully remove the interior panels to access the tail light harnesses. Work the clips with a trim tool rather than levering on the panel edge.

Step 2 — Route and connect the harness

Both the inner and outer harness wires come de-pinned and wrapped in protective tape. That's deliberate: the taped bundle slides through the grommets far more easily than loose terminals, and the tape keeps the pins from catching and bending on the way through.

1. Route the outer harness wires carefully through the existing rubber grommets.
2. Do not remove the tape until the harness is fully routed. This is the step people rush, and a bent terminal means a lamp that reads as failed later.
3. Once routed, remove the protective tape from both the inner and outer harness ends.
4. Colour match the wires from the inner and outer harnesses using the supplied 3-pin connector, pushing each terminal into the slot that matches its wire colour. Push until it clicks.
5. Check sides before you go any further: left harness to the left tail light, right harness to the right tail light.

Step 3 — Final assembly

1. Confirm all connectors and pins are properly seated. A terminal that is 90% home will work on the bench and fail over a speed bump.
2. Reinstall all removed trunk panels and interior trim, checking that no harness is pinched under a clip or trapped where the trunk lid closes.

Leave the coding until the car is back together — you'll want to open and close the trunk and cycle the lights while testing, and it's easier with the panels in.

Step 4 — Code the car (VCDS or OBDeleven)

Each rear lamp position in the car is a Leuchte channel, and each one needs four things set: the load type it should expect (Lasttyp), the bit position it reports failures on (Lampendefektbitposition), the middle DTC byte (Fehlerort mittleres Byte DTC-DFCC), and the light function it performs (Lichtfunktion A, and on the running lights, B as well). Here's what each channel becomes:

Brake lights and turn signals

Note the brake and turn channels use different Lasttyp numbers — 34 on the brake lamps, 38 on the turn signals — even though both read as "LED Blinkleuchten" in the tool.

Running lights, dynamic power and reverse

Leuchte 28 and 27 aren't lights. They're the permanent 12 V feed (Klemme 30G) the lights need to run their animations, which is why they're set as a plain 12 W bulb load rather than an LED. Leave them at Lampendefektbitposition 0 and DTC byte 1 so the car never expects a lamp there. On Leuchte 29 the Lasttyp entry your tool offers may read slightly differently between software versions — pick the general-LED-to-12 W entry.

2019 cars only — switch off Leuchte 18 and 19

On a 2019 Jetta the old left and right turn channels are still live and will fight the new ones. Set both to inactive. On 2020 and newer cars these channels are already off by default — check them, but you shouldn't need to change anything.

Step 5 — Turn on the sweeping signals

The sweep is enabled in six separate parameters, each covering a different trigger. Active means that trigger sweeps; not active means it just blinks. Set all six for the full effect, or pick and choose — plenty of people run the turn signals sweeping and leave the lock and unlock animations off.

Final checks

• Clear the fault codes with your diagnostic tool once the coding is done. Codes stored during the install will otherwise sit there and light the cluster.
• Then test, thoroughly, one at a time:
  • Brake lights
  • Running lights
  • Turn signals, both sides
  • Reverse lights
  • Sweeping animation, on each trigger you activated
• Re-scan for faults after testing. A clean scan with everything working is the point at which the job is finished.

Tips & common problems

Almost everything that goes wrong on this install is either a connector or one coding value — the lights themselves are rarely at fault.

• Both turn signals flash at the same time. The classic one, and it's always the left/right coding. Check that Leuchte 17 is set to Blinken links Hellphase and Leuchte 16 to Blinken rechts Hellphase — not both to the same value. Then confirm the left harness actually went to the left light.
• Signals blink but never sweep. The six Außenlicht parameters in Step 5 haven't been set to Active. If the search comes up empty, remember the ß is "ss".
• Bulb-out warning in the cluster. A Lasttyp that doesn't match what's actually fitted, or a Lampendefektbitposition left on the factory value. Work back through the Step 4 tables channel by channel — the bit position and DTC byte are different for every lamp and are easy to transpose between left and right.
• A function is dead on one side only. Go back to the 3-pin connector on that side. A terminal that isn't fully clicked in is the usual cause, and it often passes a quick tug test.
• Turn signals behave oddly on a 2019 car. Leuchte 18 and 19 are still active and competing with 16 and 17. Switch them off using the 2019-only table.
• No animation at all, everything else fine. Check Leuchte 27 and 28 — that's the Klemme 30G power feed. Without it the lights work but never animate.
• Nothing codes at all on a 2024+ car. That's SFD2. It isn't a fault, and it isn't something a different tool solves yet — these lights can't be enabled on 2024 and newer Jettas.
• Condensation inside a light. A little clears on its own; standing water means a bad seal and the light should be swapped.

Other guides

On a Golf instead? See MK7.5 tail lights on a MK7, MK8 Euro tail lights, or the MK8.5 tail light guide. Not sure which generation your car is? Start with MK7 vs MK7.5 vs MK8. Or browse all our DIY guides.