Programming vs. Relearn: Two Different Jobs
People mix these up constantly, and it causes a lot of wasted time.
Programming writes an ID and pressure-calibration data onto the sensor itself. That happens on the bench, before the tire ever goes on the wheel. A pre-programmed sensor already has this done at the factory.
Relearn (or registration) writes that sensor ID into the vehicle’s TPMS receiver — usually the BCM or a dedicated module. The receiver only listens for IDs it already knows. A brand-new sensor can be transmitting perfectly at 433MHz and still show nothing but dashes on the dash, because the module has no idea that ID exists.
So if you bought pre-programmed sensors, you skip programming entirely and go straight to relearn. That’s the whole job.
Tools and Information You Need Before You Start
| Item | Why you need it | Notes |
|---|---|---|
| Bidirectional scan tool with TPMS function | Performs OBD relearn, reads and clears TPMS codes | A basic code reader won’t do this |
| TPMS activation/trigger tool | Wakes sensors, reads IDs, fires the stationary learn sequence | ATEQ, Autel, Bartec-class tools |
| Correct-frequency sensors | A 315MHz sensor will never be seen by a 433MHz car | Confirm on the old sensor body or by VIN |
| Accurate tire inflator/gauge | Relearn procedures won’t complete at wrong pressures | Set to the door-jamb placard |
| Battery charger or support | Voltage sag mid-write aborts the relearn | Keep the battery up during the procedure |
| The old sensor IDs | Useful for verification and for ID-cloning tools | Photograph the old sensor labels first |
Do the prep in the right order: confirm frequency, confirm valve type (clamp-in vs. snap-in), then confirm pressures, then