brednog
New Member
- Joined
- Nov 7, 2024
- Threads
- 0
- Messages
- 3
- Reaction score
- 7
- Location
- Sydney, Australia
- First Name
- Bren
- Vehicle(s)
- 2019 Bullitt Mustang
Old thread I know - but just thought I would update based on my experience following this procedure with a 2019 Bullitt RHD (Australian delivered), which had about a 5% speedo error (speedo reading faster than GPS speed) - which was bugging me.
Summary: worked a treat!
* Bought FORScan recommended OBD2 to USB adapter / cable (OBDLink EX)
* Installed latest FORScan (v2.3.64) and enabled trial extended license
* Adjusted tire rolling circumference as per spreadsheet using GPS method (reduced as-built configured number)
* Went for a drive - got P160A DTC (no CEL) when I returned, but speedo was much more accurate
* Ran FORScan PCM relearn function and cleared DTC
* Went for another drive, all good, speedo accurate, no DTC on return!
One thing I noticed that has not been mentioned though - you don't have to modify the HEX value in the as-built BCM config anymore, as the latest FORScan versions have the tire rolling circumference as an editable parameter in the human friendly BCM editing section. So you can update the value there using a metric value in millimeters. When you do that you still check the as-built HEX values and see that they have updated as expected (which they did).
Hope this info is of use to someone! :-)
Summary: worked a treat!
* Bought FORScan recommended OBD2 to USB adapter / cable (OBDLink EX)
* Installed latest FORScan (v2.3.64) and enabled trial extended license
* Adjusted tire rolling circumference as per spreadsheet using GPS method (reduced as-built configured number)
* Went for a drive - got P160A DTC (no CEL) when I returned, but speedo was much more accurate
* Ran FORScan PCM relearn function and cleared DTC
* Went for another drive, all good, speedo accurate, no DTC on return!
One thing I noticed that has not been mentioned though - you don't have to modify the HEX value in the as-built BCM config anymore, as the latest FORScan versions have the tire rolling circumference as an editable parameter in the human friendly BCM editing section. So you can update the value there using a metric value in millimeters. When you do that you still check the as-built HEX values and see that they have updated as expected (which they did).
Hope this info is of use to someone! :-)
Sponsored
Last edited:
