Activate indirect TPMS on VW T6.1 using OBDeleven or VCDS

The Problem

The factory indirect TPMS was not enabled on some T6.1 Transporters that left the factory without it activated. Owners attempting to code it in encountered conflicts with the existing direct (sensor-in-wheel) TPMS hardware, causing dash faults, infotainment screen flip-flopping, and a persistent "SET function currently unavailable" error.

Before touching any module coding, confirm the procedure applies to your van. This applies to T6.1 Transporters that left the factory without indirect TPMS activated; some of these also have leftover direct TPMS hardware (a module 65 receiver) that conflicts with the coding. Run a full auto-scan first and check whether module 65 (TPMS) is present and whether direct sensors are still fitted in the wheels. There is no single confirmed build-date cut-off or PR/option code published for the affected vans — check your vehicle data sticker and Gateway (module 19) installation list against your dealer's records, and verify the correct TPMS option/PR code for your specific VIN with a VW dealer or via ODIS/ETKA before coding (verify before proceeding).

Solution

1. Perform a full vehicle auto-scan and save all adaptation maps (admaps) before changing any coding.

   • This gives a complete baseline to revert to, which is especially important on T6.1s that rely heavily on adaptation channels alongside basic coding.

2. In module 03 (ABS), enable the indirect TPMS / wheel speed monitoring parameter using OBDeleven Pro or VCDS.

   • If standard byte 0 coding is inaccessible, you need to unlock and edit the higher coding bytes. In OBDeleven this is done via the L2 (long coding / extended) coder; in VCDS the same bytes are edited through the Long Coding Helper. Either way, confirm byte 17, bit 1 = 1, which shifts the byte value from 21 to 23, or from 31 to 33 if TPMS is already partially applied.

3. In module 17 (Instruments), apply the required TPMS coding change so the instrument cluster recognises and displays indirect TPMS warnings correctly.

4. In module 5F (Infotainment), apply the indirect TPMS coding so the infotainment screen shows the indirect view — a single "SET" button — rather than four individual tyre pressure readouts.

5. Check the infotainment tyre pressure screen now shows a single "SET" button instead of four individual tyre pressure values.

   • If the screen flip-flops between both views, the direct TPMS receiver (module 65) is still active and conflicting — proceed to the next step.

6. If the van originally had direct TPMS sensors that are no longer present, physically remove fuse 52 to disable the direct TPMS receiver and stop it overriding the indirect coding.

   • Coding out module 65 via the Gateway (module 19, Installation List) can cause additional faults including a gateway fault and a damper fault, and is not the recommended approach unless you have deep VCDS expertise across all interfacing modules.

7. Once the infotainment shows the indirect SET screen, drive the vehicle and press SET to store the current tyre pressures as the baseline reference for the ABS wheel-speed comparison.

   • The "SET function currently unavailable" message may persist until the ABS sensors have gathered sufficient calibration data over a drive cycle; if it remains after a reasonable drive, recheck that all three module codings have been correctly saved.

8. After the test drive, run a fresh full auto-scan and clear any faults, then drive again and rescan.

   • Faults in modules 01, 03, 13, or 17 that reappear after a drive indicate a coding conflict — recheck byte 17, bit 1 in module 03 and re-apply all TPMS codings in sequence.

9. Be aware that a dealer connecting the vehicle to ODIS can overwrite TPMS coding and rear speaker fader settings — check and recode after any dealer visit if necessary.

   • A VW-initiated SOS network update applied via the infotainment does not appear to affect TPMS or other custom codings in module 5F.