Every MQB cluster swap eventually hits the same wall: the hardware fits, the coding looks right, and the car still refuses to start or throws a component protection message on the dash. The reason is that the cluster is not a display. It owns the immobilizer, holds the vehicle’s equipment map, and on newer cars sits behind an online authorisation step that a diagnostic cable cannot perform. Here is how the variants differ and what each one actually blocks.
What the instrument cluster actually owns
Installers still talk about clusters as if they were gauges. On MQB they are three things at once. First, they are the immobilizer carrier: the matched key data and the vehicle’s identity live in the cluster, which is why a used cluster from a donor car shows SAFE and cranks without firing. Second, they hold the equipment map — which driver assistance systems are fitted, whether the car has direct TPMS, whether it is DSG or manual, what the service interval regime is. Third, they render, and on the digital units that means a display panel, a graphics dataset and, on later cars, an Ethernet link to the head unit.
That combination is why a cluster that “works” can still be wrong. A unit that lights up, shows the right dials and clears its faults may still be coded for a car with different assistance systems, which shows up weeks later as a dead ACC display or a TPMS menu that cannot be opened.
The variant split: why 5A and 5C are not interchangeable
VAG cluster part numbers carry an immobilizer and architecture generation in the description, and on Passat B8 hardware you will see both families side by side. The 3GB920790 digital cluster for Passat B8 is the 5A immobilizer variant on the CAN-based architecture. The 3GB920320A digital cluster with Ethernet is the 5C variant, built for cars where the cluster talks to the head unit over Ethernet — which is what allows map data and media artwork to appear in the cluster rather than only in the centre screen.
They are not interchangeable, and the distinction is not cosmetic. Fitting a 5C cluster into a car wired for 5A leaves you with a cluster that powers up but has no data link to the infotainment, and the reverse leaves Ethernet pins unterminated. Before ordering, read the label on your existing cluster and match the variant, then confirm with the VIN. Model years vary by market, and the same nameplate often carries both architectures depending on build date.
- 5A family, CAN: most Golf 7 and 7.5 virtual cockpit cars — for example the 5G1920791B digital cluster for Golf 7/7.5 — plus Kodiaq and Superb units such as the 56G920790 cluster for Kodiaq.
- 5C family, Ethernet: later Passat B8, and the Audi units where the virtual cockpit is a node on the Ethernet ring, such as the 8W5920790E cluster for A4/Q5 B9 and the 4M0920790B cluster for Q7 4M.
Component protection: what it blocks and what it does not
Component protection is a theft-deterrent layer that ties a module to the vehicle identity stored on the manufacturer’s server. It does not stop the module from powering up. It stops specific functions from working, and it does so selectively: audio, navigation, sometimes the cluster’s ability to accept coding. That selective behaviour is what confuses people, because the module looks alive and answers diagnostics while refusing to do its job.
Removing component protection requires an online session with ODIS and a valid entitlement to the manufacturer backend. A VCDS cable cannot do it, no matter which adaptation channel you find, because the authorisation is not local. Many independent shops already have this through a subscription or a specialist partner; if yours does not, the honest answer to the customer is that the job needs a bench session or a dealer visit, not a longer coding attempt.
The realistic workflow for a used cluster
- Identify before buying. Read the label, note the full part number including the revision letter, and confirm the immobilizer variant. Two clusters that look identical on the bench can be different architectures.
- Check the donor’s equipment. If the donor had ACC, direct TPMS, a towbar module or a different gearbox, expect to recode the equipment map. This is normal and reversible; a wrong architecture is not.
- Plan the immobilizer step. On MQB the cluster must be matched to the vehicle and the keys matched to the cluster. This is the step that determines whether the car starts. Do not schedule it last.
- Clear component protection if present, online, before you attempt adaptation. Adapting a module that is still in protection state produces failures that look like coding errors.
- Code the equipment map, then run basic settings for service interval and, if fitted, the leveling and assistance systems that report through the cluster.
If the job is only an activation or a coding change rather than a hardware swap — adding a menu, enabling a display function on a cluster that is already matched — the MQB BCM and gateway coding and retrofit activation service covers that path without shipping hardware.
Diagnostics: reading the failure correctly
A U0155 for lost communication with the instrument cluster is a bus problem, not a cluster problem, until proven otherwise. Check the CAN or Ethernet pins and the gateway installation list before condemning the unit. A cluster that communicates but shows dashes in place of values is usually a dataset or equipment-map mismatch. A cluster that shows SAFE is an immobilizer problem, full stop, and no amount of coding will move it.
One more thing worth saying plainly: odometer correction on a swapped cluster is regulated in most markets and is outright illegal in several. Plan the job around a legitimately matched cluster rather than around adjusting the mileage afterwards.
Browse the full range in our parts catalogue before you order — fitment by engine code beats fitment by model name.
FAQ
Can I code a used cluster to my car with VCDS?
You can code it, but coding is not matching. The immobilizer and any component protection step need online authorisation, so a used cluster is never a cable-only job on MQB.
Do I need the donor car’s VIN?
It helps for identifying the original equipment map and the architecture, and some specialists will ask for it. It does not replace the label on the cluster itself.
Why does the cluster work but the radio stays silent?
Classic component protection behaviour. The radio is powered and answers diagnostics but has its audio function locked until the online step is completed.