Ranger Mods

305/55r20
Will give it another try! Thanks!

I have a px3 biturbo with 270/65/18. So I should be able to set mine to 0997 without getting a dtc? I am very new so if I would just like to confirm that i update my 7E0G1G1000009240016 to 7E0G1G1000009970016 and write? I have made a backup to the pcm abt.

Main reason I am updating it is because the auto parrallel parking doesn't work properly with the bigger tyres I end up hitting the kerb. But will be nice to get accurate fuel consumption again.

jesmon84 wrote: ↑Mon Oct 14, 2019 10:17 pm I have a px3 biturbo with 270/65/18. So I should be able to set mine to 0997 without getting a dtc? I am very new so if I would just like to confirm that i update my 7E0G1G1000009240016 to 7E0G1G1000009970016 and write? I have made a backup to the pcm abt.

Main reason I am updating it is because the auto parrallel parking doesn't work properly with the bigger tyres I end up hitting the kerb. But will be nice to get accurate fuel consumption again.

Yes use 0997 in YOUR case. Note for others, if this is not your tyre size then do not enter this. Also this will only work for a 10 speed or manual.

Do NOT change it in the PCM, change it in the BCM only.

Then where you are currently pressing the BCM asbuilt from look up the top and do a PCM and a TCM relearn and then clear you DTCs. It will be fixed and back to factory DTE and speedo.

Hey Stewart, thanks for all the hard work and effort you put in to this. I have a US Spec 2019 Ford Ranger, with the 10-speed, I saw you mention that on the 10-speed you can use any size you want. I installed BFG KO2 285/70/17 Tyres, and adjusted 726-12-01 in the BCM to xxx 09DC xxx (previously was 0938) and am now getting a "U0422 - Invalid Data Received From Body Control Module" DTC in the PCM. I've tried the PCM relearn procedure and clearing the code but it keeps coming back immediately. I don't see a TCM Relearn listed in FORScan, and I'm not entirely sure if the US Ranger even has a TCM. Do you think this is a case of max Tyre sizes being hardcoded somewhere? I also checked for the "TIRESIZE" PID and it doesn't exist on this PCM. Any recommendations are welcome! Also, if you need logs or anything, just let me know I'm happy to send stuff over. Thanks!

j0shm1lls wrote: ↑Fri Oct 25, 2019 4:23 am Hey Stewart, thanks for all the hard work and effort you put in to this. I have a US Spec 2019 Ford Ranger, with the 10-speed, I saw you mention that on the 10-speed you can use any size you want. I installed BFG KO2 285/70/17 Tyres, and adjusted 726-12-01 in the BCM to xxx 09DC xxx (previously was 0938) and am now getting a "U0422 - Invalid Data Received From Body Control Module" DTC in the PCM. I've tried the PCM relearn procedure and clearing the code but it keeps coming back immediately. I don't see a TCM Relearn listed in FORScan, and I'm not entirely sure if the US Ranger even has a TCM. Do you think this is a case of max Tyre sizes being hardcoded somewhere? I also checked for the "TIRESIZE" PID and it doesn't exist on this PCM. Any recommendations are welcome! Also, if you need logs or anything, just let me know I'm happy to send stuff over. Thanks!

Send me logs from Forscan as below.

TCM relearn is your option so we need to add it.

FORScan for Windows

Note: FORScan for Windows has Debug Mode setting enabled by default so debug information is recorded always. So all what user needs is to send the information from the laptop. The instruction below explains how to do it. However, if the Debug Mode setting was previously disabled for some reason, you have to enable it, remove vehicle profile (Vehicles->Profiles, delete vehicle from the list), connect and reproduce the problem before move forward with the steps below.

1. Make sure FORScan is closed.
2. Open FORScan Log folder.
2.1.Windows 7 and older: press Windows Start button->All programms->FORScan->FORScan Log folder.
2.2. Windows 8 and newer: click on the Windows icon at the bottom left corner. Find FORScan group in the list (under letter 'F'). Expand the group. Find FORScan Log folder item in the expanded group and click on it.
3. Folder with logs will be opened, you should see 2 files there: dump.bin and FORScan.log (may be more). Please zip them (if possible)

saeb wrote: ↑Wed Oct 30, 2019 8:35 pm

j0shm1lls wrote: ↑Fri Oct 25, 2019 4:23 am Hey Stewart, thanks for all the hard work and effort you put in to this. I have a US Spec 2019 Ford Ranger, with the 10-speed, I saw you mention that on the 10-speed you can use any size you want. I installed BFG KO2 285/70/17 Tyres, and adjusted 726-12-01 in the BCM to xxx 09DC xxx (previously was 0938) and am now getting a "U0422 - Invalid Data Received From Body Control Module" DTC in the PCM. I've tried the PCM relearn procedure and clearing the code but it keeps coming back immediately. I don't see a TCM Relearn listed in FORScan, and I'm not entirely sure if the US Ranger even has a TCM. Do you think this is a case of max Tyre sizes being hardcoded somewhere? I also checked for the "TIRESIZE" PID and it doesn't exist on this PCM. Any recommendations are welcome! Also, if you need logs or anything, just let me know I'm happy to send stuff over. Thanks!

Send me logs from Forscan as below.

TCM relearn is your option so we need to add it.

FORScan for Windows

Note: FORScan for Windows has Debug Mode setting enabled by default so debug information is recorded always. So all what user needs is to send the information from the laptop. The instruction below explains how to do it. However, if the Debug Mode setting was previously disabled for some reason, you have to enable it, remove vehicle profile (Vehicles->Profiles, delete vehicle from the list), connect and reproduce the problem before move forward with the steps below.

1. Make sure FORScan is closed.
2. Open FORScan Log folder.
2.1.Windows 7 and older: press Windows Start button->All programms->FORScan->FORScan Log folder.
2.2. Windows 8 and newer: click on the Windows icon at the bottom left corner. Find FORScan group in the list (under letter 'F'). Expand the group. Find FORScan Log folder item in the expanded group and click on it.
3. Folder with logs will be opened, you should see 2 files there: dump.bin and FORScan.log (may be more). Please zip them (if possible)

Hi Stewart,

Attached are the logs as requested. Please let me know if there is anything else you need!

Thanks,
Josh

Hi Stewart, thanks for sorting this thing out.
Just wondering if the 977 amendment in the BCM line is all that I'd need to get the speedo to be reasonably accurate after having 33's put on?

I understand that Barry at BPT would be my best guess for full integration, but until I can make the call would this be sufficient or would I need to do something else in the mean time?

And yes, I did read every page of this post and boy is there a heap of information that goes over your head!

AS82XLT wrote: ↑Thu Dec 19, 2019 8:47 pm Hi Stewart, thanks for sorting this thing out.
Just wondering if the 977 amendment in the BCM line is all that I'd need to get the speedo to be reasonably accurate after having 33's put on?

I understand that Barry at BPT would be my best guess for full integration, but until I can make the call would this be sufficient or would I need to do something else in the mean time?

And yes, I did read every page of this post and boy is there a heap of information that goes over your head!

Did we speak on the book of face last night?

For anyone else. You want a transmission tune with anysize tyre fix then go direct to Barry, you want a firmware change to allow any size tyre but no transmission tune then PM me.

Yeah we did Stewart. Thanks again. I tried to delete the post but obviously it didn't work

I've got standard size tyres that are 265 60 18 and my speedo is giving me the craps being 4 ks out. How can I change it with Forscan to correct speedo reading without upsetting all the other things like Dte etc? BCM circumference is set at 2355mm

Unfortunately you can't. The "correction" is built in to the firmware. You can use forscan to change tyre size, which can align your speedo but your odometer and dte will be out.

The only way is a separate speedo display using either an obd dongle and something like a scangauge or ultragauge, or using a separate gps device.

saeb wrote: ↑Tue Aug 28, 2018 5:55 pm
PX1 can be changed with the 3 preset sizes although every hi rider or 4x4 PX1 I have checked has already been set at the highest.

See PX1 programming here https://www.saeb.net/viewtopic.php?f=12&t=1213

Ah, I never knew this. I have a PX1 - 2014 XLT Auto running 285/75/16's (Manufacturer states is 2589mm circumference).

On looking at the BCM Central Configuration, Tyre Circumference was initially set at "Not Configured". I went ahead and chose the maximum size from the list (which had approx 30 options). This was "57 - Rolling Circumference 2260mm" but on saving, I have a DTC, but no CEL in the IPC. It shows a code of U2300:55-2A & U2300:56-2A.

Aside from the fault code, my speedo is worse than before and is currently showing 102 on the Dash and 110 on GPS. On looking at the Revs/Mile PID, I am getting 712 revs/mi. 616 revs/mile would be most optimal. Changing back to "Not Configured" doesn't help.

My question is, can I get closer to optimal given that I have no larger options within the Tyre Circumference list? Am I able to clear the faults somehow?

Any assistance would be greatly appreciated.

As per my post that you quoted, the vehicle would have already been using the highest available tyre size so no point in changing.

Assume you backed up before you started so restore the backup and clear the DTCs then it should be back to normal.

saeb wrote: ↑Sun Feb 24, 2019 7:12 pm I usually just do the BCM, I only ever changed the PCM on occasion and the only reason I mentioned it originally was after reading some service material.

0977 to dec is 2423 x 10 = 24230 to hex is 5EA6

Try the standard value in the PCM and do a run to check ODO then change it to 5EA6 and see if there is any difference.

If you feel there was a difference with the odometer then give me your true tyre size and I will give you a different value.

Hi Stewart,

I got slightly larger tyres fitted to my PX2 manual so went ahead and changed the BCM and PCM values along with relearn on PCM.
I know you say here you normally only do BCM but is there any harm in just doing both?
I should now have correct odo and factory offset speedo?

FYI my new BCM is 0939 from 0910 and new PCM is 5C3A from 5AA0 for a scaled value of 2442mm circumference resulting in 2361mm.
PCM change threw DTC's in two modules which cleared with no issues.

What you have done is fine. I'm surprised you got a DTC with such a small change though. Either way you resolved it and it works, well done.

saeb wrote: ↑Sat Feb 15, 2020 6:51 pm What you have done is fine. I'm surprised you got a DTC with such a small change though. Either way you resolved it and it works, well done.

Great, thanks!
The DTC was in the ABS module and the PAM.

Gday, I recently purchased a MyCalibrator tuner from BPT Motorsport for my 3.2L Everest. One of the TCM tunes provided was specifically for 285/65/18 tyre size. After flashing this TCM Tune, I was able to change the BCM circumference value to '09CD' without any DTC (2509mm = 2598mm * 97%).

I dont understand the relationship between the TCM and the BCM in this regard, so is this still the correct adjustment to make when Tyre changes have been made in TCM also?
I was just confused whether if changes have already been made in TCM to account for bigger tyres, these changes still required in BCM, or am I throwing everything off?
What does the PCM value do in all of this, is it also required to be changed?

Eitherway, my speedo is now at 105kmh with GPS at 100kmh. And fuel Economy reading seems to have come down ~0.5l.

sd88me wrote: ↑Mon Mar 30, 2020 9:06 am Gday, I recently purchased a MyCalibrator tuner from BPT Motorsport for my 3.2L Everest. One of the TCM tunes provided was specifically for 285/65/18 tyre size. After flashing this TCM Tune, I was able to change the BCM circumference value to '09CD' without any DTC (2509mm = 2598mm * 97%).

I dont understand the relationship between the TCM and the BCM in this regard, so is this still the correct adjustment to make when Tyre changes have been made in TCM also?
I was just confused whether if changes have already been made in TCM to account for bigger tyres, these changes still required in BCM, or am I throwing everything off?
What does the PCM value do in all of this, is it also required to be changed?

Eitherway, my speedo is now at 105kmh with GPS at 100kmh. And fuel Economy reading seems to have come down ~0.5l.

BCM change will be fine, I just tend to do all because it must be in the PCM for a reason.

Just like Barry's custom TCM file or my TCM custom file, although both will remove tyre size limitations you still need to make at a minimum BCM change.

Also BCM "09D2" would be the correct change although not a huge difference.
Depending on PCM firmware version, for old style "6234" or new "09D2". You will know which one because the current one will either start with a 5 or a 0.

Make sure to do a PCM relearn afterwards.

Let me know if any custom PIDs/Gauges are not working as expected on the Tuner, they and the future firmware changes are still is the works. Once some more changes are made then I can start playing with PIDs again.

Hi All

I recently put on 285/70/17 tyres on my Ford Everest.
Prior to this I had 265/65/18 and had changed the values in forscan to the maximum of 977. which meant my speedo was back to reading 104km/h at a true 100km/h my ODE and DTE etc was bang on (after upgrading from the factory size of 265/60/18)

Now with the new tyres I am back out to a 4% error where the speedo is bang on (which would indicate everything is 4% out) due to them being larger and wider. My scangauge is showing the car as reading 96km/h at an indicated 100km/h (which also matches the GPS reading of 100km/h) so to me this confirms the car is still 4% out due to the larger tyres.

I have the BPT tune and just got the tcm tune updated for the larger tyre size (and dropped my $160 large) however it made zero difference to the 4% error. I raised this with Barry, and he seems to think it is right as the speedo reads correctly, where I think it is wrong? On my way home, my calculations seem to confirm this.
I travelled 34.2kms according to my GPS, however the car only indicated I had travelled 32.8kms indicating it was 1.4kms out (ironically close to 4%)
The speedo was identical with the new BPT tune as my old BPT tune (indicating seemingly nothing had changed)

So my questions are;
- Do I need to do a PCM relearn and this will fix the issue itself? If so, how do I do this?
- Will the BPT tcm tune have unlocked my PCM so I can now go higher than 977 without a fault code and I need to make changes in there using Forscan for the car to recognise the changes? (Barry didn't seem to think so) If so, what should the change be made to?
- Assuming I need to action point 2, if I then load my standard factory tcm tune back in, will it throw a fault code due to the increase from 977 or once it is unlocked, its unlocked for good?

Thanks in advance.

Ok, so bit the bullet and gave it a crack.
So I changed the BCM to 09DC
I tried to change the PCM to 6298 but it come up with an error message while it was trying to write.

Went for a quick drive and noticed the following
- No fault codes (yet?)
- Drove 11.7kms according to the GPS and the car said I travelled 11.6kms (so it appears to be far more accurate over a small snapshot)
- Speed was back to normal (104km/h speedo = 100km/h actual)
- Interestingly the scangauge was still out showing 96km/h. so it hasn't changed even though the speedo has and the ODO has. My assumption is the PCM change probably fixes this and I assume I can't do this due to the error?)

So.… a little bit more of an update.

On the MAX trans tune with the new tyre profile, I noticed the following;
- speedo and GPS appeared back to factory standard, meaning a 4% variance between indicated and actual speeds (104km/h on the speedo (100km/h on the GPS)
- the ODO seems relatively accurate with 1%
- My scangauge is interesting. with cruise set on one speed, it constantly jumps between accurate to 4% out approx. every 10 seconds.
EG. at 100km/h actual speed (GPS) the dash speedo reads 104km/h and my scangauge flicks between 96km/h and 100km/h. Its almost like it is picking up conflicting information from somewhere and doesn't know which one to display.

On the MILD trans tune with the new tyre profile, I noticed the following;
- It throws a fault code that wont clear P1635 and the engine light stays on.
- Everything else is PERFECT.
That is;
- speedo and GPS appeared back to factory standard, meaning a 4% variance between indicated and actual speeds (104km/h on the speedo (100km/h on the GPS)
- The ODO seems relatively accurate with 1%
- The fault with my scangauge seems to fix itself and it reads perfectly (same reading as the GPS)

It seems to me like the algorithms are slightly different from BPT between the two tcm tunes and something is going a miss with the tune or the way my car is displaying the information. I would love to be able to run the mild tcm tune (my preferred tune) but not sure how to get rid of the fault code.....?

Anyone got any thoughts?

P.S - I loaded both tcm tunes in a couple of times just to rule out a loading issue and came up with the same results each time....

I would do a PCM relearn either way.

I'm not sure what Barry is changing in the PCM and TCM.

I do know that I can run whatever tune I want and whatever tyre size I want with my own TCM modified firmware and everything is within .05% with the cluster having the normal 4% as expected.

You will not get the Mild to run without the DTC as the P code is TCM related and that file has not been modified to allow the change.

If you or Barry can make sense of it he is free to talk to me about the issue.

To clarify, I got two new TCM tunes loaded. One called “Mild 285/70/17” and one called “Max 285/70/17”
My understanding is they were both supposed to bring it back to factory original with bigger tyres.
Is there anything else I need to do to get the PCM change working (different input) or just do the relearn and see what happens?

If you are getting a P1635 and cannot clear it then the change has not been made in that TCM cal.
If I use an unmodified TCM cal I get the P code, if I mofidy the cal then write it the P code goes away without me needing to clear it.

Either way make the change in the BCM to "09DC"
And the PCM to 6298. Write the line and not the write button down the bottom and see if that helps. Sometimes writing the whole module will fail in the PCM.

Then do PCM relearn.

Asbuilt still needs to be changed either way as far as I'm concerned and is what I do even when I write a modified calibration.

So I made the change in the PCM and wrote the line with success. I also successfully did a PCM relearn.

None of this made any difference though (that I can see)
The scangauge speed still flicks between spot on and 4% out every 10sec (approx) and the mild tcm tune still throws a fault code.

Might talk to Barry to see if he can look into the mild tcm cal. Should I mention anything specific, or just P code 1635?