roadPilot

726-45-01 for speedo correction on a 2011 XLT 5.0 4x4 SCrew was a no-go.

As built 0988 (275/70R17) to 09D4 (275/70R18).

Remains ~3.5% off. 70 mph actual (two different mobile phone using GPS apps) vs. 68.5 mph on speedo (and digital readout from OBDlink MX & OBDWiz app.

Spart

Good to hear. Sounds like for whatever reason, the 2011-2014 trucks have the value stored in the as-built but don't rely on it for the speedometer.

Incorrigible

Hi folks - any idea how to get the original values to line 726-12-01?

I'm showing the codes below after correcting the speedo. Livinitup in the FORScan thread suggested I "load" my original saved as-built data but I didnt save it. Big mistake I thought the original FORScan run saved the info. I have to go back to dealer and don't want the "wrench" light encouraging the dealer to look around and find reasons to charge me more money.

After running a DTC scan two faults show up:

P 160 A Control Module Vehicle Options Reconfiguration Error
Status: DTC present at time of request
Malfunction Indicator Lamp is ON for this DTC
Module: Transmission Control Module

and

P160 A control module Vehicle Reconfiguratio Error
DTC Present at time of request
Malfunction indicator lamp is OFF for this DTC
Module: Powertrain control module

If I try and clear the faults w FORScan they come right back

Firerunner

iTrader: (3)

Have you been to https://www.motorcraftservice.com/AsBuilt and pulled for asbuilt data from there?

(If its your first time there you will need to pick a language, then go to free resources --> quick guides --> Module Build Data (AsBuilt)

Incorrigible

Thanks Firerunner!

Max91

Here ya go.

Incorrigible

Thanks Max and Firerunner - I entered the as-built into 726 12-01 middle string #### 099E #### and the DTC went away but my speedo is now running low due to 35"'s. I then entered back the modified figures to compensate for the 35's the string 0A32 in the middle field and now the speedo was right ...and the DTC was back. Perhaps these 10 speed tranny's are not liking us peeps messing with the body control modules. In any case thanks for the assist!

Max91

Yeah, I think you have to stay within the factory sizes (17,19,20..etc). Even that throws a DTC but not a lamp indicator.

Glad I could help

MNSportsman

iTrader: (1)

Glad you got things squared away Incorrigible. If you get a chance, you might ask Livnitup to updtae the Forscan spreadsheet to note that 2017s may receive the wrench in addition to the DTC which I belive he already has noted.

Livnitup

I need someone with a '17 who wants to change their tire size in BCM as a volunteer. I have a new test beta version of FORScan that includes a procedure called "PCM Module initialization/relearn vehicle data" that should allow anyone to change their tire size in BCM and then force PCM to relearn this new size so that no PCM DTC will be present. This should also work on 2017's where guys get the wrench icon on the cluster display. So if you have a '17 and want to test this out, pm me and if this procedure works I'll post the new version of FORScan publicly for everyone.

Note: This new function should not be run on any truck with a custom tune as it will screw up the Vehicle Identification Block so any custom tune would need to be removed first and then the tune could be put back on after this procedure is ran.