• Welcome Visitor! Please take a few seconds and Register for our forum. Even if you don't want to post, you can still 'Like' and react to posts.

INFO FORScan As Build data spread sheet, 2011 and earlier


So I was playing around with it today mainly because I was wondering if I could enable an electric fan controlled by the PCM. After connecting a wire to pin 45 on the PCM and checking resistance to ground and voltage to hot while using output test mode when I turn on low speed fan the resistance changes slightly but it's still predominantly grounded all the time... I didn't take any pictures or screenshots while I was playing with it though.
 
so some ECM use a PWM network and some communicate on HSCAN network. PCM in 07 ranger switched to a PCM with 3 separate plugs. Somewhere around 03 Ford started using HSCAN instead of PWM in various models. Near as I can see researching wiring diagram the ranger made the switch in 05. From my understanding if the obd2 port has a pin populating pin 6 it has CAN communication. With a paid license you can download the current forscan beta, and with a vLinker FS adapter you should be able to program PCMs in that window. If the beta and vlinker let you download asbuilt date from PWM PCMs than you could potentially download the asbuilt data from one and write to the newer one that can be altered, however this also has potential to brick the new PCM and I'm not 100% to sure if restoring a backup will fix it. I'm also not sure what other modifications would be needed beyond wiring pin 6 in the obd2 port.
 
Last edited:
@Broosedamoose

sorry I didn’t answer you sooner. It seems like you done everything as I would have done it to be honest.
I’m not sure why your having issues, I’ve done the same thing on my ‘11 ranger ‘08 expedition, and ‘11 F250.

you may be any to look at the spread sheet and re check that I gave you the correct hexadecimal code.

Convert your hexadecimal code for that line to binary, change the correct 1 to a 0, then back to hexadecimal.
 
2007 Ford Ranger Sport RWD, wish to change the tire size, can it be done?

1750527638111.png
 

Attachments

  • 1750527620813.png
    1750527620813.png
    41.2 KB · Views: 11
solraven's link where a FORScan expert says tire size settings on an older truck are "likely in the PCM VIN ID block", coupled with comparing Broosedamoose and t3chno1d's AS-BUILT data, seem to indicate tire size isn't adjustable in the GEM.

Broosedamoose's truck is already larger-tire-size-corrected, so we should see the difference if that's where it lives. Only the -04- and -05- blocks are notably different, only the first two fields in Broosedamoose's -04- show relatively larger numbers, and the values in those bytes don't look like they have anything to do with tire size, circumference, revs/mile, etc.

Although, maybe I'm just not interpreting it right.

On writing changes, does FORScan automate checksum correction now? It's been a few years, but last time I checked, you had to recalculate the checksum manually.
 
I'm taking my truck in for a recall and also to get the speedo calibrated, it reads 108 when travelling at 100 km/h. My mistake, I should have said tire size adjusted. They said they couldn't calibrate the speedo. I'll resate it when I visit. Is there any way to back up my PCM programming to see what they change?
 
I'm taking my truck in for a recall and also to get the speedo calibrated, it reads 108 when travelling at 100 km/h. My mistake, I should have said tire size adjusted. They said they couldn't calibrate the speedo. I'll resate it when I visit. Is there any way to back up my PCM programming to see what they change?

There is a way to backup the data. It is recommended that one do that before they change things, just incase they change the wrong thing or fat finger a setting.
 
I've read that dealers will (can?) only adjust calibration between stock options, so if you have tires larger than were ever offered, they won't help.

Tractmec made it seem like editing the PCM calibration in Forscan beta on '04+ is translated, so you wouldn't need to mess with AS-BUILT at all. The vLinkerFS is $32, which isn't bad to try it out and still end up with an OBDII-USB cable regardless.
 

Sponsored Ad


Sponsored Ad

TRS Events

Member & Vendor Upgrades

For a small yearly donation, you can support this forum and receive a 'Supporting Member' banner, or become a 'Supporting Vendor' and promote your products here. Click the banner to find out how.

Recently Featured

Want to see your truck here? Share your photos and details in the forum.

Ranger Adventure Video

TRS Merchandise

Follow TRS On Instagram

TRS Sponsors


Sponsored Ad


Sponsored Ad


Amazon Deals

Sponsored Ad

Back
Top