2011 F150 XLT Scab 5L 4x4; FORScan v2.3.70 paid extended license; OBDLINK-EX USB adaptor with firmware updated on 02/01/2026
I can see the four last installed sensors' ID numbers, TPM_RFR_(nn) HEX values, using the oscilloscope - (monitor) icon. These IDs were from a set of used 2014 wheels.
I read the sensor's ID numbers from a set of used 2018 Ford wheels (315 MHz), which are on the truck now, using my Launch CRT5011E TPMS tool.
I don't see any way to edit these HEX values using the Chip (Configuration) icon to the new HEX value ID numbers, which should enable the truck to relearn the sensors using the Ford training/relearn procedure.
History
I've used the Ford Owner Manual training/relearn procedure to train a set of new MoreSensor Compact PRO (preprogrammed) sensors with my Launch TPMS tool.
I've also trained a set of used stock Ford 2014 (315 MHz) sensors to my truck.
The Ford training/relearn procedure fails with the 2018 (315 MHz) set of sensors, which then displays the annoying TPMS Fault Message on each start up.
I've disabled TPMS warning and fault for now...
Any insight would be appreciated.
Changing / Editing TPMS sensor ID Numbers in BdyCM and IPC
Re: Changing / Editing TPMS sensor ID Numbers in BdyCM and IPC
The CRT5011E is the tool designed to do what you want. If it doesn't work there is probably something wrong with the sensors.
Re: Changing / Editing TPMS sensor ID Numbers in BdyCM and IPC
You shouldn't need FORScan to do this - put the vehicle in TPMS relearn and using a tool to "wake" the sensors, go around and program them starting at the front driver side tire in a counter clockwise motion. If they aren't registering, the sensors are used, the sensors are defective, you are not in the correct programming mode (my vehicle has 2 modes so research yours) or the tool you are using to "wake" the sensors isn't working correctly.
-
DBMoehl
- Posts: 18
- Joined: Mon Jan 03, 2022 11:39 pm
- Vehicle: F150 gas 5.0L 2011
- Location: Pacific Northwest of USA
Re: Changing / Editing TPMS sensor ID Numbers in BdyCM and IPC
Thanks for your responses.
I think the problem may be that the connection protocol for the 2011-2017 TPMS, and the 2018 up sensor's protocol are different, even though both my truck and sensors operate on 315 MHz.
The change to 433 MHz TPMS and sensors that started in 2017 was not abrupt but seems to have been done sporadically.
If I could write the HEX ID numbers to the BdyCM module, then the truck's TPMS might recognize the sensors when doing a relearn using Ford's Training/Relearn procedure and using my Launch CRT 5011E to activate the sensors.
At present, there are only four sensor IDs in the BdyCM (from the last set of wheels) even though I've successfully trained and relearned 3 different sets of sensors to the truck.
It appears that earlier versions of FORScan were capable of writing the TPM_RFR_(nn) values to the BdyCM module.
Thoughts?
Thanks!
Dennis
I think the problem may be that the connection protocol for the 2011-2017 TPMS, and the 2018 up sensor's protocol are different, even though both my truck and sensors operate on 315 MHz.
The change to 433 MHz TPMS and sensors that started in 2017 was not abrupt but seems to have been done sporadically.
If I could write the HEX ID numbers to the BdyCM module, then the truck's TPMS might recognize the sensors when doing a relearn using Ford's Training/Relearn procedure and using my Launch CRT 5011E to activate the sensors.
At present, there are only four sensor IDs in the BdyCM (from the last set of wheels) even though I've successfully trained and relearned 3 different sets of sensors to the truck.
It appears that earlier versions of FORScan were capable of writing the TPM_RFR_(nn) values to the BdyCM module.
Thoughts?
Thanks!
Dennis