Learning TPMS sensors 2026: Complete guide & tips

What is TPMS Sensor Programming? Basics

Programming a TPMS sensor describes the process in which the unique sensor ID is registered in the vehicle's control unit. Without this process, the tyre pressure monitoring system does not recognise the new sensors – the TPMS warning light flashes and the system remains inactive. Every direct TPMS sensor transmits its ID and pressure and temperature values to the receiving module at 433.92 MHz (Europe) or 315 MHz (USA/Asia).

Sensor ID and radio communication

Every wheel sensor has a hexadecimal ID-32-bit identifier that is permanently programmed at the factory. When new sensors are fitted, the control unit must learn these IDs. Modern sensors use protocols such as Schrader, Siemens VDO, Pacific or Huf/Beru – each with specific telegram structures and CRC checksums. Transmission uses FSK or ASK modulation with a transmission power of maximum 10 mW to avoid interference with other radio services.

Auto-Learn vs. Stationary-Learn

With Auto-Learn, the vehicle registers new sensors automatically while driving. The control unit detects unknown IDs, compares the signal strength of the four wheel positions and assigns them automatically. This method is used mainly by Opel, Ford and older Toyota models. With Stationary-Learn, an OBD tool must write the IDs manually into the control unit. VAG, BMW and Mercedes predominantly use this method, in which the vehicle is put into a learning mode.

Trigger procedure in detail

Stationary-Learn requires triggering each sensor with a low-frequency signal (125 kHz) that wakes the sensor and forces it to transmit data immediately. Without a trigger, the sensor waits up to 60 seconds while stationary for the next transmission interval. Professional tools such as the Autel TS508 or ATEQ VT56 combine OBD communication with integrated trigger functions and thus cover over 98% of all direct TPMS. According to ECE Regulation 64, all passenger cars newly type-approved from 1 November 2014 must have a functioning TPMS – programming is therefore not an option but a requirement.

Why do you need to program TPMS sensors?

TPMS sensors must always be reprogrammed when the stored sensor IDs in the control unit change. This happens with every wheel change with new sensors, when switching from summer to winter tyres with their own set of wheels, or when a sensor fails due to a dead battery. A non-programmed TPMS leads to a permanent warning light in the instrument cluster and can lead to a significant defect during the main inspection according to §29 StVZO.

Scenario 1: Defective sensor and battery life

The lithium-ion button cell of a TPMS sensor lasts 5 to 10 years depending on the driving profile. For high-mileage drivers with a high transmission frequency, it is often only 5 years, while low-mileage drivers can get up to 10 years. The battery is permanently sealed and not replaceable – a voltage drop below 2.1 V leads to failure. After replacing the sensor, the new ID must be learned, otherwise the control unit will continue to search for the old ID that is no longer transmitting and set the error code "Sensor not found".

Scenario 2: Complete wheel change with own TPMS set

Many vehicle owners use two sets of wheels – one for summer, one for winter. If both sets are equipped with sensors, the current wheel set must be learned at each seasonal change. Some manufacturers such as BMW (from model year 2014) store two wheel sets in parallel, but most vehicles can only manage one set of IDs at a time. Manual learning via the instrument cluster only works on a few models (e.g. Toyota RAV4); for most, an OBD tool is required.

Error codes and their meaning

If a sensor is not learned, manufacturer-specific error codes appear in the TPMS control unit. Common codes are C1100–C119F (sensor ID missing), U0126 (communication loss) or B2872 (pressure too low). Reading via OBD tool shows exactly which sensor at which position is not recognised. ADAC tests prove: a functioning TPMS reduces the risk of tyre blowouts due to underinflation by up to 75 percent. Especially when loaded or on long motorway journeys at speeds above 160 km/h, a calibrated system is vital.

Differences between direct and indirect TPMS

The fundamental distinction in tyre pressure monitoring systems concerns the measurement method. Direct TPMS physically measures pressure and temperature inside the tyre, while indirect TPMS calculates pressure losses from the wheel speed signals of the ABS. Only direct TPMS requires sensors to be learned – and this is exactly the system installed in most European vehicles from model year 2014 onwards.

Direct TPMS: structure and function

Each wheel sensor contains a piezoresistive pressure sensor, a temperature sensor, a microcontroller with 32-bit ID, a transmitting antenna and a lithium battery with 3.0 V nominal voltage. The sensor measures tyre pressure in the range from 1.8 bar to 3.5 bar with an accuracy of ±0.07 bar and sends a data packet every 30 to 120 seconds. When stationary, the sensor goes into sleep mode to save battery. Vehicles with direct TPMS display the pressure per wheel in the instrument cluster – often with specific bar values.

Indirect TPMS: ABS-based pressure monitoring

Indirect systems require no sensors in the tyre at all. They use the ABS wheel speed sensors and detect pressure losses via the changed rolling geometry: a tyre with lower pressure has a smaller rolling circumference and rotates faster. The software detects differences from 0.3 bar pressure loss, but cannot detect gradual losses on all four tyres. Indirect TPMS must be initialised via the instrument cluster – a five-second button press on the TPMS button starts the calibration process, which requires about 20 km of driving. Learning with an OBD tool is completely unnecessary.

Which system requires learning?

Learning sensors is only necessary with direct TPMS. Owners of vehicles with indirect TPMS can ignore this point entirely – after a wheel change, they only need to perform initialisation via the vehicle menu or the reset button. Since November 2014, ECE Regulation 64 has required a functioning TPMS for all new passenger car type approvals, but permits both system variants. In practice, European manufacturers use direct systems over 90% of the time, because only these can display pressure precisely and per wheel.

Requirements for learning: tool and compatibility

Successfully learning a TPMS sensor requires three things: a compatible diagnostic tool, knowledge of the manufacturer-specific learning procedure and the correct sensor IDs. Without an OBD tool, learning is not possible on most vehicles from model year 2014 onwards. We show the most important professional tools and explain the differences between the manufacturer protocols.

Professional OBD tools compared

The market is dominated by two devices: the Autel TS508 and the ATEQ VT56. The Autel TS508 (approx. €180) supports over 98% of all direct TPMS with OBD connection, and can read out, program and learn sensor IDs. Its 3.5-inch colour display shows pressure and temperature live. The ATEQ VT56 (approx. €250) additionally offers an even more extensive vehicle database and a faster trigger function. Both devices are regularly updated via USB and cover the protocols of all European, Asian and American manufacturers. For the workshop they are indispensable; for the ambitious hobby mechanic, the Autel TS508 pays for itself by the second wheel set change.

Manufacturer-specific learning procedures and protocols

Each manufacturer uses its own protocols and learning strategies, which makes learning without a suitable tool more difficult:

• VAG (Audi/VW/Skoda/Seat): Stationary learn via OBD. The sensors (mostly Huf/Beru) must be triggered at 125 kHz. The system expects a fixed sequence: front left, front right, rear right, rear left.
• BMW: From the F series, storage of two wheel sets is possible. Learning via OBD with triggering in the same sequence as VAG. Sensors mostly from Schrader or Continental at 433 MHz.
• Mercedes: Stationary learn with OBD. Typical sensors from Schrader. The TPMS control unit is usually located in the boot, and OBD communication runs via the central gateway.

• Opel: Auto learn while driving. New sensors are detected automatically after 10–20 km of driving. No OBD tool required, provided original sensors or compatible types with the correct Schrader protocol are used.
• Ford: Mostly auto learn, on newer models (from 2018) also stationary learn with OBD. Frequency 433 MHz with Motorcraft protocol.
• Peugeot/Citroen: Mixed system. Some models auto learn, others require OBD. Sensors from Siemens VDO with a specific PSA protocol.

• Renault: Predominantly OBD learning with 433 MHz Schrader sensors. Trigger sequence as with VAG.
• Toyota: Depending on the model 315 MHz (e.g. US import) or 433 MHz. Many models with auto learn, some require OBD. Manual learning via the instrument cluster is possible on the RAV4 and Camry.

Compatibility check before purchase

Not every universal sensor works in every vehicle. Before purchase, the frequency (315 or 433 MHz), protocol and valve type (aluminium/rubber) must be matched. The KBA database lists the approved sensor types for each vehicle – this information is relevant for the MOT. An ATEQ VT56 or Autel TS508 indicates before programming whether the selected sensor is compatible and performs the plausibility check automatically.

Step by step: learning TPMS with an OBD tool

Learning with an OBD tool is the safest way to register new TPMS sensors. The process follows a standardised sequence, but varies depending on the tool and vehicle. We show the complete workflow for the Autel TS508 and ATEQ VT56 – two devices that together cover over 95% of all vehicles.

Basic preparation

Before the OBD tool is connected, all four tyres must be fitted with the new sensors and inflated to the specified pressure (usually 2.2 to 2.8 bar). The vehicle is on a level surface, the ignition is switched on, the engine remains off. On most models the OBD port is located on the left under the steering wheel. Important: during the learning procedure all radio sources nearby (Bluetooth, Wi-Fi, garage door openers) must be deactivated, as they can interfere with the 125 kHz trigger frequency.

Learning with the Autel TS508

The Autel TS508 guides you through a menu-driven process. In the main menu the vehicle is selected by make, model and year of manufacture. Then the menu item “Sensor learn” → “OBD learn”. The device briefly communicates with the TPMS control unit and then prompts you to trigger the sensors. The sequence is strict: front left → front right → rear right → rear left. The integrated trigger is held directly against the tyre sidewall near the valve. A successful trigger is confirmed by a beep and the display of the sensor ID. Once all four IDs have been captured, the TS508 writes the data to the control unit via OBD. After a brief plausibility check the tool displays “Learning successful”. A subsequent test drive of 5 kilometres ensures that all sensors are recognised correctly.

Learning with the ATEQ VT56

The VT56 works on the same principle but offers even faster trigger detection and a larger vehicle database. After selecting the vehicle, the VT56 starts the learning mode. Here too, triggering is carried out in the sequence starting with front left. The VT56 stores the IDs and compares them with the internal database for protocol compliance. The OBD write command is then executed. A notable advantage of the ATEQ VT56: on BMW vehicles from model year 2014 it can select the second wheel set directly and store it separately – without overwriting the first. After a successful write, ATEQ recommends restarting the ignition and a 10-minute test drive at speeds above 25 km/h so that the control unit can clearly assign the sensor positions.

Plausibility check and validation

After the learning procedure a plausibility drive is absolutely essential. The TPMS control unit compares the signal strengths of the individual IDs and definitively assigns them to the wheel positions. Most vehicles require 10–20 minutes of driving for this. During this time the system cannot display pressure warnings – the lamp only goes out after successful position assignment. A final check with the OBD tool shows whether all four IDs are assigned to the correct positions and whether the pressure values are plausible (±0.1 bar tolerance). Only then is the TPMS fully functional and complies with the legal requirements of ECE R64.

6. Learning TPMS without tools: is that possible?

6.1 Auto-learn vs. stationary learn

The question of whether TPMS learning is possible without a special diagnostic tool depends on the vehicle system used and the sensor protocol. In principle, two methods are distinguished: with auto-learn, after a wheel or sensor change the vehicle is driven a certain distance and the control unit detects the new sensor IDs itself via the radio signals. This method is common, for example, on some Asian manufacturers or older US models with 315 MHz systems. The prerequisite is a defined driving cycle: at least 15 minutes of uninterrupted driving at over 25 km/h so that the sensors wake from sleep mode and transmit their IDs.

In contrast, stationary learn requires the manual or tool-assisted entry of the sensor IDs while the vehicle is stationary. European manufacturers such as VAG, BMW and Mercedes almost consistently rely on this method, as it prevents theft and incorrect assignment with multiple wheel sets. A pure auto-learn mode is the exception here.

6.2 Limits of manual learning without an OBD tool

Without tools, a stationary learn is only feasible on a few vehicles via the on-board menu, and even then the control unit often first has to be enabled for learn mode using a diagnostic device. Since 2014, ECE Regulation 64 has required a direct TPMS for new cars in the EU, which as a rule uses coded sensors with a 433 MHz frequency (315 MHz usually remains reserved for export markets). In addition to pressure and temperature values, these sensors also transmit the individual, permanently assigned 8-digit ID, which must be stored in the TPMS control unit.

Typical fault codes such as C1102 (sensor ID not recognised) or 01325 (no signal from the tyre pressure monitoring module) show that without write access via the OBD interface a complete learn procedure is not possible. Nevertheless, there are vehicles, such as the third-generation Ford Focus, on which a manual training mode via the hazard warning button and a magnet can reactivate old sensors – for new sensors, however, OBD access remains essential.

Auto-learn

The vehicle independently recognises new TPMS sensor IDs after a defined driving cycle (>15 min, >25 km/h) without manual intervention. Mainly on 315 MHz systems without ID coding.

Stationary learn

Learn procedure while stationary, in which sensor IDs must be programmed via OBD tool, trigger device or on-board menu. Standard on European 433 MHz systems.

Conclusion: A genuine learn completely without tools fails on 9 out of 10 European vehicles due to the obligatory ID programming. To be on the safe side, you need at least a TPMS trigger device in conjunction with the vehicle's own learn routine – and for coded systems, an OBD diagnostic tool such as the Autel MaxiTPMS TS508 or the ATEQ VT56 is essential.

7. Specific guide for VW (Golf, Passat, Tiguan)

7.1 Platform overview and system variants

All Volkswagen Group vehicles on the modular transverse matrix platform (MQB) – including the Golf VII/VIII, Passat B8, Tiguan II, Skoda Octavia, Seat Leon – use a direct TPMS with a 433 MHz frequency and coded sensors. The sensor IDs are stored in control unit J502 (address 65). In contrast to earlier indirect systems via ABS sensors, an electronic identification match is mandatory here. The system distinguishes up to 4 wheel sets (summer, winter, spare), which makes the ID change necessary when swapping wheels.

7.2 Step-by-step learn routine with diagnostic tool

1. Ignition on, engine OFF. Connect the OBD diagnostic device (e.g. Autel TS508) and select the vehicle type.
2. Select menu item Tyre pressure monitoring → Program sensor.
3. Read out existing sensor IDs and overwrite them with new IDs, or start “relearn all sensors”.
4. Activate each wheel one after the other with the trigger device (LF trigger 125 kHz) until the control unit acknowledges the ID. Sequence: front left → front right → rear right → rear left.
5. After successful programming, clear the fault memory and carry out a short test drive (> 5 minutes above 25 km/h) so that the sensors transmit continuously and no new fault code is generated.

Practical example: An Audi A3 8V with start-stop automatic and AGM battery shows the message “Check tyre pressure – system fault” after a tyre change. Here the only remedy is to read in the four new sensor IDs using the TS508, as the TPMS control unit reacts particularly sensitively to implausible pressure values after a voltage drop caused by the start-stop automatic and sets fault code 02433.

7.3 Recommended sensors and frequencies

Important: VW sensors must be programmed to the correct protocol (VW Unified 433 MHz) in their delivery state. Autel MX sensors make this possible directly via the TS508 without preloading via PC.

8. Learning TPMS on BMW (3 Series, 5 Series, X3)

8.1 System architecture and RDC function

BMW has relied on a proprietary 433 MHz protocol since the introduction of tyre pressure control (RDC), which communicates via the RDC antenna (usually in the wheel arch or underbody). In vehicles from model year 2010 (E90 LCI, F30, G20, G30, F25 X3), coded sensors with a fixed 8-digit ID are installed. The control unit RDC (function code 2VB) continuously compares pressure, temperature and acceleration values. A special feature is the sleep-wake mechanism: BMW sensors switch to a sleep mode after standstill with a current consumption of only 0.1 µA and are reactivated by centrifugal force (from approx. 25 km/h) and an LF signal.

8.2 Manual learning via iDrive and workshop tool

In a limited number of BMW vehicles (e.g. F30 3 Series before facelift 2015), a wheel change can be acknowledged via the iDrive menu Vehicle → Tyre pressure → RDC reset – the control unit then searches for new IDs in auto-learn mode. However, this only works if the sensors are already known to the system. After a sensor change, the new IDs must be written in via OBD tool. Diagnosis is performed via the CAN bus (K-CAN2) and address B7.

With the Autel TS508, after vehicle selection (BMW → 3 Series → F30), the existing ID list is read out and overwritten with the newly activated IDs. The programming process typically takes 5–10 minutes. Error codes such as 481B02 (sensor timeout) or 481B01 (no reception) indicate that the old ID is still stored or the sensor is not transmitting.

8.3 Table: BMW vs. competitors learning procedures

BMW owners should note that the RDC sensors have a typical battery life of 7–10 years. After a voltage drop below 2.1 V (with a nominal 3.0 V lithium cell), the sensor stops transmitting and is registered as defective.

9. Learning Mercedes TPMS (A-Class, C-Class, E-Class)

9.1 RDK systems and protocol variants

Mercedes-Benz installs direct tyre pressure monitoring systems in the compact A-Class (W176, W177), the C-Class (W205, W206) and the E-Class (W213), which transmit either on 433 MHz (Europe) or 315 MHz (USA, Korea) depending on the market. The control unit is integrated into the NTG infotainment (e.g. NTG5.2, NTG6) and communicates with the wheel sensors via CAN-C. Each sensor transmits a 6-byte ID as well as pressure (accuracy ±0.07 bar) and temperature values. The sensors are coded at the factory and must comply with the KBA database (ECE Regulation 64-02).

9.2 Stationary learn with ATEQ VT56 and steering wheel menu

A manual ID matching is prepared on many Mercedes models via the on-board menu in the instrument cluster (Service → Tyre pressure → Learn sensors) – but communication usually fails without activation by a diagnostic device. The procedure with an ATEQ VT56:

1. Connect ATEQ VT56 to the OBD port and have the vehicle identification read automatically (VIN parsing).
2. Select TPMS → ID programming → Mercedes-Benz.
3. Trigger each wheel one after the other with the integrated LF trigger device (125 kHz) within 30 seconds per position – the order is FL, FR, RR, RL.
4. Write new IDs via OBD into the RDK control unit, confirm memory, ignition OFF and ON.
5. Delete error codes such as C110200 (signal from a tyre pressure sensor missing) or C110100 (pressure loss warning) after a successful test drive.

The A-Class W177 in particular reacts sensitively to missing sensor acknowledgements and after 20 minutes without ID reception no longer deactivates the RDK warning light automatically – so using a tool is essential here.

9.3 Retrofit options and sensor service life

For winter wheel sets, universal sensors such as the VDO REDI-Sensor are available, which is filled with a data sheet for MERC-RDK-433 and covers the OEM numbers A0009050700/A0009053800. The button cell of type CR2032HR with 3.0 V enables a mileage of 160,000 km or 7 years – after that, the transmission power drops below the threshold of -40 dBm and the sensor is stored as “not reachable” in the error memory.

10. Learning Ford TPMS (Focus, Mondeo, Kuga)

10.1 Training mode without diagnostic device? Possibilities and limits

Ford offers a manual training mode on many models – in particular on the Focus (MK3/MK4), Mondeo (MK5) and Kuga (MK2/MK3) – which at first glance allows new sensors to be learned without an OBD tool. The procedure: ignition ON, press the hazard warning button 3 times, the horn sounds once. The sensors must then be activated one after another with a TPMS trigger tool (125 kHz LF signal) or – in the case of older sensors – with a strong permanent magnet (field strength > 50 mT) in the order FL, FR, RR, RL. Successful reception is acknowledged by a short horn signal.

However, this method only works with original sensor IDs already stored in the system. If new aftermarket sensors have been fitted whose IDs are not stored in the control unit, the learning process is aborted with the flash code 4 flashes of the warning light. In this case an OBD diagnostic tool must be connected.

10.2 OBD programming with Autel TS508

The procedure with an Autel MaxiTPMS TS508 is particularly efficient on Ford vehicles, as via the OBD interface the device not only programs the IDs but also automatically detects the sensor positions and re-parameterises the Body Control Module (BCM):

1. Connect the Autel TS508 to the OBD port (often under the steering wheel on the left), have the vehicle identified via VIN.
2. Programming → Learn new sensors → Ford → Focus 2019. Display the existing ID table.
3. Activate the sensors one after another with the LF trigger. The TS508 immediately shows pressure, temperature and ID.
4. After all four positions have been acknowledged, the new IDs are written to the BCM via the CAN protocol (11-bit identifier, 500 kbit/s). The process takes approx. 3–4 minutes.
5. Test drive for at least 15 minutes above 30 km/h – the system checks the plausibility range (pressure 1.5–3.5 bar, temperature -20 °C to +60 °C) and clears the warning light.

10.3 Differences between 433 MHz and 315 MHz

European Ford models consistently use 433 MHz, while US imports and early Mexican production sometimes use 315 MHz. The frequency difference is critical: a 315 MHz sensor is not detected by a 433 MHz receiver. Before buying a sensor, a look at the old valve or the control unit label is necessary. The Kuga MK3 (from 2020) already uses an extended protocol version with +10 dBm higher transmission power and cyclic data intervals of 30 seconds (normally 60 seconds), which enables the tyre position to be located after just less than 2 minutes of driving.

TPMS learning on Opel, Audi, Skoda (VAG Group)

VAG platform: Audi, VW, Seat, Škoda – direct system with VCDS/OBDII

All Volkswagen Group (VW AG) vehicles from model year 2014 onwards use a direct TPMS with wheel sensors transmitting on 433 MHz (Europe). The control unit (usually address 65) expects the programmed sensor IDs in a fixed order: front left – front right – rear right – rear left. On Audi A3 8V, A4 B9, Q5 FY or VW Golf VII/VIII the write process is carried out via OBD-II. With the VW software VCDS (from HEX-V2) or ODIS you write the 7- or 8-digit HEX IDs (e.g. 0x7A3F1C2) directly into the memory of the comfort control unit. Alternatively, universal tools such as Autel TS508 or ATEQ VT56 instruct the control unit via OBD command to read in the newly detected sensor IDs ("OBD Relearn"). Important: on MQB Evo platforms (Golf VIII, Leon IV) from 2021, access to address 65 is SFD-protected – without online activation (GeKo/SVM) only the workshop route remains.

Opel: from auto-learn to EL-50448

Depending on the model generation, Opel uses different procedures. Vehicles of the GM era (Insignia A, Astra J, Corsa D, Mokka A) often work with a self-learning procedure (auto-learn). After the tyres have been correctly inflated and a drive above 25 km/h, the control unit automatically detects the new sensor IDs and assigns them to the positions. All that is needed is the correct reference pressure. Newer models from 2018 (Insignia B, Corsa F, Mokka B) on the PSA platform require a stationary learn – the sensor must be activated individually while stationary with an LF trigger (125 kHz). Here the low-cost programming trigger EL-50448 proves its worth; it costs between 12 and 25 euros on Amazon and is compatible with GM and Ford systems. After triggering, an OBD tool writes the detected IDs into the control unit. Important: some Opel models use 315 MHz systems – always check the OE reference on the old sensor before buying replacement sensors.

Frequencies and protocols in the VAG/Opel world

European VAG vehicles transmit exclusively on 433.05–434.79 MHz in accordance with ETSI EN 300 220. Opel models from the GM era for the US market, on the other hand, may use 315 MHz – an import from the USA therefore often has to be converted. Sensor communication follows the UHF protocol with FSK or ASK modulation. During OBD programming, the tool sends the so-called Mode $28 (FF FF) to trigger relearn mode, followed by the four sensor IDs in HEX order. Modern tools such as the ATEQ VT56 support automatic protocol matching and thus avoid collisions with the immobiliser.

Asian manufacturers: Toyota, Honda, Hyundai

Toyota: auto-learn and manual triggering

For its direct TPMS systems (e.g. RAV4, Corolla from 2017), Toyota almost consistently relies on an auto-learn function. After fitting new sensors, an initialisation drive of about 10–15 minutes at a constant 40 km/h is sufficient. The control unit identifies the four strongest 315 MHz signals (US models 315 MHz, EU models 433 MHz) and assigns them to the wheel positions via the RSSI value. A separate OBD write process is not required. It only becomes critical if you change complete wheels with sensors that were already programmed with a different ID on another Toyota – in that case, briefly pressing the TPMS reset button under the steering wheel (often near the glovebox) for 3 seconds until the warning light flashes three times helps.

Honda: sensor ID via OBD or self-learning

For most models built from 2016 onwards, Honda (Civic X, CR-V, HR-V) requires an OBD relearn. The control unit (body control module) requires the hexadecimal ID of each sensor in the order of the installation position. With the Autel TS508, the IDs can be read out and transferred directly to the vehicle in “OBD Write” mode – typically for Honda without manual LF triggering, as the tool prompts for the position input when connected to the OBD socket and the sensor in the wheel remains in “sleep” mode – only after successful writing does the control unit wake it with a 125 kHz wake-up call. Older Honda models (Civic IX) had an indirect system without sensors – in that case, of course, no relearn is necessary, only the reset button.

Hyundai/Kia: stationary learn with pressure change

Hyundai and Kia (i30, Tucson, Sportage) from 2018 onwards use a stationary learn via LF trigger. The sensor must be woken from its storage state with the OBD tool or a universal trigger (125 kHz). The decisive difference: some models require a pressure change during the relearn process. You must release at least 0.3 bar of tyre pressure from the fitted wheel within 30 seconds so that the control unit recognises the new ID as “active”. If the pressure remains constant, the system refuses to accept it. The use of the ATEQ VT56 with a guided Hyundai protocol, which prompts step by step to release air, is therefore recommended.

Relearning a TPMS sensor ID: technical background

What is the sensor ID and why is it unique?

Every direct TPMS sensor carries a globally unique 32-bit identification number from the factory (in short: sensor ID), represented as a 7- or 8-digit hexadecimal number (e.g. 3F A7 2C 1D) – that corresponds to over 4.2 billion possible combinations. This ID is permanently stored in the sensor's EEPROM and is transmitted with every data transmission (together with pressure, temperature and battery status) in the 433 MHz or 315 MHz telegram. The control unit maintains a whitelist of the four expected IDs. Only if the received ID matches the learned one is the pressure displayed on the instrument cluster – an essential safety mechanism that prevents interference from other vehicles in dense city traffic.

Protocols: FS code, HEX, decimal – communication with the control unit

In the world of diagnostics there are three common formats: the FS code (Factory Serial) is the raw value assigned by the sensor manufacturer (e.g. Schrader, Huf, Continental). The HEX format is the direct representation for OBD transmission (8 characters, hexadecimal). Some Asian manufacturers expect a decimal ID (ten digits). Modern tools such as the ATEQ VT56 translate automatically between the three formats. At the VAG group, the Mode $28 command is sent in hexadecimal: 28 FF FF for "relearn all sensors". The control unit responds with a positive acknowledgement (ACK) when the IDs have been received in the correct order.

How data transmission works via LF trigger (125 kHz) and UHF (433/315 MHz)

A sensor in its storage state transmits only sporadically in order to conserve the 3 V lithium battery. Only an LF wake-up call at exactly 125 kHz (trigger device close to the valve) activates the sensor immediately, after which it emits a UHF telegram every 0.3 seconds for around 30 seconds. The diagnostic tool picks up this telegram, extracts the ID, the measured pressure (accurate to 0.1 bar) and the temperature, and then offers this data record to the OBD write process. High-quality sensors of the latest generation (Huf IntelliSens 5, Schrader EZ-sensor 2.0) also support Bluetooth Low Energy as a programming interface, so that the smartphone acts as the trigger – LF hardware is not required.

Sensor ID

32-bit globally unique identifier of the TPMS sensor (HEX: e.g. 0x3FA72C1D)

OBD-II

On-board diagnostics interface (ISO 15765-4) for writing the sensor IDs to the control unit

LF trigger (125 kHz)

Low-frequency wake-up signal that brings the sensor out of sleep mode (range approx. 10 cm)

UHF telegram

433 or 315 MHz radio telegram with pressure, temperature, ID and battery voltage

FS code

Factory Serial Number – manufacturer-specific raw ID (often longer than the HEX ID)

Mode $28

OBD command according to ISO 14229 that starts the relearn mode in the TPMS control unit

RSSI

Signal strength indicator used by auto-learn systems to determine the wheel position roughly

CWA value

Cyclic Word Check – protection against corruption of the UHF telegram

EEPROM

Non-volatile memory in the sensor, retains ID and configuration even without a battery

ACK/NAK

Positive (acknowledgement) or negative acknowledgement from the control unit after an OBD write command

ETSI EN 300 220

European standard for short range devices, defines transmission power and channel spacing 433.05–434.79 MHz

SFD

Schutz Fahrzeug-Diagnose – VAG security mechanism from MQB-Evo onwards (GeKo activation)

Common errors and problems when learning in

Wrong sensor ID programmed – causes and remedies

The classic case: you have programmed a universal sensor with the wrong OE reference, and although the ID is recognised by the diagnostic tool, the control unit rejects it. Example: a Huf IntelliSens coded for BMW transmits a telegram in the wrong protocol format. Remedy: reprogram the sensor with the correct FS code for your vehicle make (using Autel TS508 or ATEQ VT56) or – if the sensor is already mounted on the rim – replace it completely. Always check the valid OE number on the old sensor (e.g. Schrader 29148 for VAG MQB).

Sensor not recognised: LF signal too weak or frequency incompatible

If the LF trigger is held at the wrong angle or too far from the valve (> 10 cm), the sensor remains silent. Particularly tricky are 315 MHz sensors in a 433 MHz vehicle – the trigger does wake it, but the UHF receiver is on the wrong frequency. Solution: use a sensor with the exact frequency that the vehicle had fitted at the factory (check the sticker in the door pillar). With steel rims or armoured valves, the trigger distance can even be less than 5 cm – an extension piece for inductive triggers helps here.

Interpreting fault codes: C1073, C1074, C1075 and their meaning

The manufacturer-independent fault codes according to ISO 14229 give precise indications. A list of the most common:

• C1073 – TPMS sensor battery voltage low (below 2.1 V). The sensor must be replaced. Battery life is 5–10 years (approx. 1,500 charge cycles of the lithium CFx cell).
• C1074 – Sensor ID not stored in the control unit. Carry out a new learn-in after a tyre change.
• C1075 – Signal loss / timeout. Sensor no longer transmits. The cause is often mechanical breakage after fitting.
• C1076 – Wrong wheel position detected. Force a relearn after rotation.

TPMS after a tyre change: do I always have to learn in?

Complete winter wheel sets with their own sensors

If you use a second set of wheels with sensors that have already been programmed and fitted, you must relearn them every time – unless the vehicle supports auto-learn (e.g. Toyota, older Opel models). On VAG and BMW models, the OBD write process is unavoidable because the control unit uniquely identifies each sensor by its ID. Invest in a personal tool such as the Autel TS508 (approx. €150), and the twice-yearly workshop visit pays for itself within two seasons.

Only the tyres changed, wheel rim and sensor stay – no relearning needed?

Yes, correct. If only the tyre is replaced and the sensor stays on the same rim in the same position, the relearn process is not required. The control unit stores the ID-to-position assignment permanently. Note: However, some fitting shops inadvertently damage the sensor when breaking the bead of the old tyre, so that fault C1075 suddenly appears after fitting. Have the tyre service confirm in writing that all sensors are intact.

Sensor position after wheel change (rotation) – reassignment via relearn

If the wheels are swapped diagonally (front left to rear right), the TPMS control unit must learn the new positions. Without a relearn, the instrument cluster displays the pressure from the front left at the rear right wheel – dangerous when a pressure loss warning occurs! Systems with auto-localisation (e.g. BMW via three LF antennas, VAG MQB evo) detect the new position automatically within 2–5 km of driving. Older systems, on the other hand, require the manual OBD relearn, in which the sensors must be learned in the correct order.

Cost of TPMS relearning: workshop vs. doing it yourself

Workshop prices by vehicle brand

The range extends from a friendly €20 at a tyre specialist ("5 minutes, have a coffee") to €120 at a franchised workshop with SFD activation. Typical costs apply depending on the brand:

• VAG (Audi, VW): €45–85 incl. OBD programming. SFD models +€20 surcharge (GeKo).
• BMW: €50–100, as ISTA diagnostics and connection to the BMW server (ICOM Next) are often required.
• Mercedes-Benz: €55–90, Xentry programming via DTS Monaco.
• Opel, Ford, PSA: €20–40 at an independent garage if no OBD write process is required.
• Asian brands (Toyota, Hyundai): €25–50, often only triggering and reset.

Investment in OBD tools: Autel TS508, ATEQ VT56 – payback

The Autel MaxiTPMS TS508 costs around €150 as a set (incl. LF trigger and USB cable) (06/2026). The ATEQ VT56 with subscription model (€60/year) costs €300 to purchase plus a €60 annual update fee – but with vehicle coverage of 99% of all brands and automatic protocol detection. With two wheel changes per year, you save €170 compared with an Audi franchised workshop (2 × €85) – after the second season the Autel has paid for itself.

Hidden costs: wrong sensors, adapters, subscription models

Factor in: a set of high-quality universal sensors (e.g. Huf IntelliSens 5, Schrader EZ-sensor 2.0) costs between €100 and €160. Cheap no-name sensors from €40 per set often have a failure rate of 15% on first relearning – here you pay twice. If you do not renew your ATEQ subscription, you lose access to new vehicle protocols and are left stranded with the next model year. SFD activation at VAG (GeKo) can also be rented as a one-off subscription for 24 hours – a worthwhile option for DIY mechanics.

FAQ: Common questions about TPMS sensor relearning