Direct TPMS is one of the few MQB retrofits where the hardware is genuinely simple and the coding is where the job lives or dies. The module is small, the sensors are in the wheels, and yet cars come back with a permanent warning because address 65 was never added, or because nobody wrote the sensor IDs. This is the sequence that actually clears the dash.
Direct and Indirect TPMS Are Not the Same System
Most MQB cars left the factory with indirect TPMS: the ABS module compares wheel speeds and flags a pressure loss through the ESC software. There is no sensor in the wheel and no control unit to code. Direct TPMS adds a dedicated receiver, four wheel sensors with their own radio IDs, and a display in the instrument cluster or the infotainment screen.
That difference explains a common misconception. Fitting the second-generation direct TPMS kit for VW MQB to a car with indirect TPMS does not “upgrade” the existing system — it installs a second, parallel one and then tells the ABS module to stop doing the indirect calculation. If the ABS side is not recoded, both systems run and the car reports pressure faults from two directions at once.
Where the Module Sits and Why the CAN Run Matters
On MQB the TPMS control unit lives behind the lower dash on the driver’s side in most bodies, on the extended CAN. The kit ships with the module and the sensor set; the harness run is short but it has to reach the correct CAN pair. Two failure modes come from this: tapping comfort CAN instead of extended CAN, which leaves the module invisible to the gateway, and tapping the wrong twisted pair, which produces intermittent communication faults that only appear when the car is warm.
Before you power anything, confirm which gateway the car has. A 3Q0907530AC highline gateway exposes the extended CAN channels you need; a mid-line gateway may not carry the module in its installation list at all.
Step One: Get Address 65 Into the Installation List
This is the step that gets skipped, and it is the reason a correctly wired module appears dead. The gateway holds a list of control modules the car expects to talk to. Adding physical hardware does not add it to that list.
- Open the gateway installation list in VCDS or ODIS.
- Enable address 65 — Tire Pressure Monitoring.
- Save, then cycle the ignition and rescan.
- Confirm the module answers and reports a part number.
If address 65 will not stay enabled, the gateway is rejecting it — usually a firmware or variant limit rather than a wiring fault. That is the point to stop and check the gateway part number instead of pulling the dash apart again.
Step Two: Recode the ABS Side
The ABS module has to be told that tyre pressure monitoring is now handled by a direct system, otherwise it keeps calculating and keeps setting its own warning. The relevant coding byte differs between ABS part numbers and software versions, so read the long coding helper for your specific module rather than copying a value from a forum post. Write down the original coding before you change anything — a mis-coded ABS module on an MQB car disables more than TPMS.
After coding, clear faults in the ABS module and cycle the ignition. A residual “tyre pressure monitoring not available” message at this stage is normal until the sensors are addressed.
Step Three: Address the Wheel Sensors
The sensors transmit a fixed ID. The module has to learn four of them, and until it has, it reports the system as incomplete. There are two routes: an inductive write-in tool held against each valve stem, or a drive cycle long enough for the module to pick up all four transmissions.
- Write-in tool: fastest and deterministic, but the tool has to support the 433 MHz MQB sensor generation.
- Drive cycle: works, but only if all four sensors are alive and the car exceeds the speed threshold the module expects.
- Mixed approach: write in three, drive for the fourth — a sign that one sensor is weak rather than that the procedure failed.
A sensor that will not learn is usually a dead battery rather than a coding problem. Sensors have a service life measured in years, and a set pulled from a donor car may already be at the end of it. Fit new sensors when the kit is new; diagnosing a five-year-old sensor costs more than replacing it.
Step Four: Adaptations and the Cluster Menu
With four IDs stored, the remaining work is presentation. The pressure thresholds and the warning strategy are adaptation channels in the TPMS module, and the menu entry has to exist in the instrument cluster. On a 5G1920791B virtual cockpit for Golf 7 and 7.5 the TPMS page appears once the cluster coding knows the function is present; on a 5NA920791B cluster for Tiguan MK2 the same applies with a different menu layout.
If the values are displayed but the units or the recommended pressures look wrong, that is an adaptation issue, not a sensor issue. Recommended pressures are per-vehicle data and have to match the tyre placard, not a default from another body style.
When a Sensor Will Not Learn: Reading the Right Blocks
The measuring blocks in address 65 tell you more than the fault memory does. Look for per-wheel status, received ID, signal quality and last reception time. A wheel showing a plausible ID with poor signal quality is a sensor mounted incorrectly or a receiver with an antenna problem. A wheel showing no ID at all is either a dead sensor or a sensor that has never been triggered — some units stay asleep until they see rotation or an inductive wake-up.
Do not chase a wheel-specific fault through the body harness until you have swapped that sensor to another corner. Ten minutes of substitution beats an afternoon of continuity testing.
Common Failure Modes
- Module invisible: address 65 not enabled in the gateway installation list.
- Two warnings at once: ABS still coded for indirect TPMS.
- Three wheels learned, one missing: dead sensor battery or blocked reception.
- Warning returns after a week: adaptation thresholds left at defaults, or a sensor slowly failing.
- Works cold, fails warm: CAN pair tapped incorrectly or a poor crimp in the harness run.
TPMS also interacts with the body electronics more than people expect. If the car has a 5Q0937084DH BCM that was replaced or reflashed during other retrofit work, re-check the gateway installation list afterwards — some workshop coding routines reset optional addresses.
FAQ
Can direct TPMS be retrofitted without changing the ABS coding?
No. The ABS module continues to run its indirect calculation and will keep setting its own pressure warning. Direct TPMS requires the ABS side to be recoded so the two systems do not run in parallel.
Do I have to buy new wheel sensors?
Strongly recommended. Sensors have a finite battery life and a used set of unknown age is the most common reason a retrofit appears to fail at the learning stage.
Why does the cluster show dashes instead of pressures?
Because fewer than four sensor IDs are stored, or the cluster coding does not include the TPMS menu. Check the stored IDs in address 65 before touching cluster coding.