that would explain the 540km to a tank issue, i changed the asbuilt speedo to 0977 but was thinking it did the odometer also.. will input the other Tyre size figure in the PCM and see if fuel changes, on a side note the OBDLink app was telling me 10l/p100 but dash was around 12l/p100 so Obd must be getting readings from different area.
Information: Following the announcement on October 23, 2023, this site has been archived as of July 1, 2024. For further details, visit this page.
Tyre sizes - Including asbuilt Calculator
-
- Junior Member
- Posts: 97
- Joined: Mon Jun 26, 2017 9:33 pm
- Location: Gold Coast QLD
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2016
- Has thanked: 1 time
- Been thanked: 4 times
Greg
2016 PX2 XLT Dual cab 4x4
Sync 3 Auto
2016 PX2 XLT Dual cab 4x4
Sync 3 Auto
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
Soon as you increase to 285 you will never get DTE or odometer 100% correct. No amount of changes without modifying firmware will allow it.
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
-
- Junior Member
- Posts: 97
- Joined: Mon Jun 26, 2017 9:33 pm
- Location: Gold Coast QLD
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2016
- Has thanked: 1 time
- Been thanked: 4 times
ok will the above change make it better or do nothing for dte?
Greg
2016 PX2 XLT Dual cab 4x4
Sync 3 Auto
2016 PX2 XLT Dual cab 4x4
Sync 3 Auto
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
Try it and let us know.
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
Now that I have my Win10 dongle from Stewart, I'm trying to work my way through fixing the odometer, DTE, and fuel consumption reporting problem. I keep track of my fuel consumption using an iPhone app, and there has always been a difference between the app and the truck. My average on the app is 10.1L/100km, and on the truck it is 12.5L/100km.
Also, the odometer and trip meters don't match the kilometer markers on the Autobahn. Yesterday, I used my Ultragauge to check the accuracy over a 14km stretch of the nearby Autobahn, and the UG tells me the calibration factor is 1.023. Once calibrated, the UG seems to be nearly spot on with the Autobahn markers. After a trip today, I logged 168.2km on the UG, while the trip meter showed 165km. Only half of the driving was on the Autobahn, so I couldn't verify the measured distance for the entire trip. One of my upcoming trips will include a 85km stretch on one Autobahn, so I'll log that section on the UG and the truck.
While I don't care about the relation of the speedometer to the actual speed, I do care that the odometer matches the actual distance driven. I didn't check the UG or speedometer speed values against the GPS yet.
My 2018 PX2 Auto 3.2L has Continental M+S 265/60R-18 110T Tyres inflated to 2.6 Bar (37.7 PSI). I assume these were factory installed Tyres, since I didn't change them and they were on the truck when I first saw it on the dealer's lot before signing the contract.
Here are the relevant values from FORscan:
BCM 726-12-01 0175 0934 5144
PCM 7E0-01-01 0000 5C08 004D
The 0934 equates to a 2356mm Tyre circumference, and I assume this should be changed to 0977 to max out the value for the automatic transmission. However, I don't know if the 5C08 is correct for my Tyres, or if not, what it needs to be. I appreciate any help in this.
Mike
Also, the odometer and trip meters don't match the kilometer markers on the Autobahn. Yesterday, I used my Ultragauge to check the accuracy over a 14km stretch of the nearby Autobahn, and the UG tells me the calibration factor is 1.023. Once calibrated, the UG seems to be nearly spot on with the Autobahn markers. After a trip today, I logged 168.2km on the UG, while the trip meter showed 165km. Only half of the driving was on the Autobahn, so I couldn't verify the measured distance for the entire trip. One of my upcoming trips will include a 85km stretch on one Autobahn, so I'll log that section on the UG and the truck.
While I don't care about the relation of the speedometer to the actual speed, I do care that the odometer matches the actual distance driven. I didn't check the UG or speedometer speed values against the GPS yet.
My 2018 PX2 Auto 3.2L has Continental M+S 265/60R-18 110T Tyres inflated to 2.6 Bar (37.7 PSI). I assume these were factory installed Tyres, since I didn't change them and they were on the truck when I first saw it on the dealer's lot before signing the contract.
Here are the relevant values from FORscan:
BCM 726-12-01 0175 0934 5144
PCM 7E0-01-01 0000 5C08 004D
The 0934 equates to a 2356mm Tyre circumference, and I assume this should be changed to 0977 to max out the value for the automatic transmission. However, I don't know if the 5C08 is correct for my Tyres, or if not, what it needs to be. I appreciate any help in this.
Mike
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
Seems a bit odd Mike, standard tyres should not need the BCM changed.
Can you email me about this one please, it will be easier in this case.
Can you email me about this one please, it will be easier in this case.
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
Email sent, and thank you very much for the extra work!
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
This evening I experimented with a few changes to the BCM value, starting with 0977 (2423mm). This turned out to be too much, and the test run on a 14km section of the Autobahn showed the odometer reaching one kilometer before the first marker. I changed the value to 0960 (2400mm), and this was not enough. On the same stretch of road, the odometer reached one kilometer after the first marker.
Now that I knew two extreme limits, it was just a process of divide and conquer to find the correct value. Fortunately, traffic was light and there was a place to pull over at each end of the run to change the values. I halved the values before I settled on 096E (2414mm), and this was nearly spot on for the 14km run in both directions. Once I was satisfied with this, I calibrated the Ultragauge and the calibration factor was 0.999.
The next test was the GPS comparison. Unfortunately, it was getting late and I was running out of fuel, so I decided to call it a night and head home. During the drive home, the GPS and Ultragauge were nearly identical, but the speed was at or below 70km. The truck speedometer was about two or three kilometers below the GPS value. I'll test the GPS again tomorrow since I'll be on the Autobahn for over 45 minutes.
I reset both the truck trip meter and the Ultragauge trip meter at the gas station. On the drive home, about six kilometers, I drove the last half kilometer in my neighborhood at a walking pace so I could see when each was changing, since they appeared to be happening simultaneously at faster speeds. The Ultragauge was less than one meter ahead of the truck trip meter. I think I can live with this.
I learned after the first BCM change it is important to run the "PCM Module initialization/relearn vehicle data" option after changing the BCM value. I don't know what values in the PCM are being changed, but if I didn't do this after changing the BCM value, the change had no affect on the road. After I ran the relearn option, a few DTC errors popped up in FORScan, but I cleared them and they didn't pop up again. There was no check engine light (spanner) on the dash.
Now that I knew two extreme limits, it was just a process of divide and conquer to find the correct value. Fortunately, traffic was light and there was a place to pull over at each end of the run to change the values. I halved the values before I settled on 096E (2414mm), and this was nearly spot on for the 14km run in both directions. Once I was satisfied with this, I calibrated the Ultragauge and the calibration factor was 0.999.
The next test was the GPS comparison. Unfortunately, it was getting late and I was running out of fuel, so I decided to call it a night and head home. During the drive home, the GPS and Ultragauge were nearly identical, but the speed was at or below 70km. The truck speedometer was about two or three kilometers below the GPS value. I'll test the GPS again tomorrow since I'll be on the Autobahn for over 45 minutes.
I reset both the truck trip meter and the Ultragauge trip meter at the gas station. On the drive home, about six kilometers, I drove the last half kilometer in my neighborhood at a walking pace so I could see when each was changing, since they appeared to be happening simultaneously at faster speeds. The Ultragauge was less than one meter ahead of the truck trip meter. I think I can live with this.
I learned after the first BCM change it is important to run the "PCM Module initialization/relearn vehicle data" option after changing the BCM value. I don't know what values in the PCM are being changed, but if I didn't do this after changing the BCM value, the change had no affect on the road. After I ran the relearn option, a few DTC errors popped up in FORScan, but I cleared them and they didn't pop up again. There was no check engine light (spanner) on the dash.
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
I made some test runs this evening to compare the speedometer with the GPS and Ultragauge. I missed some of the speeds, but the Ultragauge and GPS were identical. All speeds are in KPH. I started at 31 KPH because the cruise control would not engage at 30 KPH. I waited for the speed to stabilize before capturing the values.
Is there another adjustment to change the speedometer output to match the GPS?
Code: Select all
Speedo GPS/UG Percentage
31 29 6.45%
50 47 6.00%
60 56 6.67%
90 86 4.44%
100 96 4.00%
110 105 4.55%
120 115 4.17%
140 134 4.29%
150 144 4.00%
160 153 4.38%
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
- GerryP
- Moderator
- Posts: 514
- Joined: Sun May 21, 2017 8:17 pm
- Location: Karoonda SA
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2017
- Forscan Dongle Type: OBDlink MX+ Black Bluetooth
- Has thanked: 58 times
- Been thanked: 82 times
Great work Mike. I believe the speedo 'adjustment' is in the firmware and cannot be changed using forscan. Stewart may have more info, but I have the same predicament as you... odometer correct, as is my fuel DTE, internal speed reading is spot on, but speedo dial is 6% out. It's a pain...
Gerry
'17 Ford Ranger PX2 XLT Supercab
Manual, Canopy, Flares, ROH Assassins, Smartbar Stealth, Solar & Dual Battery
'17 Ford Ranger PX2 XLT Supercab
Manual, Canopy, Flares, ROH Assassins, Smartbar Stealth, Solar & Dual Battery
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
Well done Mike. Sorry I was getting to you but......well you sorted it. Its close to the end of year and work needs to be completed and posts generally responded to while I'm walking around at the moment.
4% is a good number at 100kph. I would be happy with those figures.
What type of driving do you normally do and at what speeds as this may well influence the fuel figures up to 2.5% according to those numbers. Doing 60kph for a majority of the run would definitely throw some figures out.
There still should not have been a reason adjust it with standard tyres though. Is the cluster kph or mph?
4% is a good number at 100kph. I would be happy with those figures.
What type of driving do you normally do and at what speeds as this may well influence the fuel figures up to 2.5% according to those numbers. Doing 60kph for a majority of the run would definitely throw some figures out.
There still should not have been a reason adjust it with standard tyres though. Is the cluster kph or mph?
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
No worries on the delay, as from your previous posts it appears you are quite busy!
The cluster is KPH. Over half of my driving is on the Autobahn at 140+ KPH. One of the guys who lives on my street is a traffic cop, and the next time they are running stationary LASER speed checks in the area, I'll make a few passes at different speeds to compare the gauges and GPS.
The cluster is KPH. Over half of my driving is on the Autobahn at 140+ KPH. One of the guys who lives on my street is a traffic cop, and the next time they are running stationary LASER speed checks in the area, I'll make a few passes at different speeds to compare the gauges and GPS.
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
-
- New Member
- Posts: 3
- Joined: Sat Aug 19, 2017 7:58 pm
- Location: Hobart
- Model Of Vehicle: RANGER XL PX2
- Year Of Vehicle: 2018
Hi Stewart,
Similar issue to those posted above, running 255/85R16 on a PX2 auto so I've maxed the BCM out at 0977 however my DTE is out significantly. At the moment I've got a stock tank and I'm getting around 65L before 0km DTE. How are you calculating the corrected PCM value and/or can you please advise the hex for 255/85R16 (~2638mm circumference)? I note you've mentioned it's impossible to get the speedo & odo/DTE back to parity but this is well beyond any internal correction factor.
Thanks,
Josh
Similar issue to those posted above, running 255/85R16 on a PX2 auto so I've maxed the BCM out at 0977 however my DTE is out significantly. At the moment I've got a stock tank and I'm getting around 65L before 0km DTE. How are you calculating the corrected PCM value and/or can you please advise the hex for 255/85R16 (~2638mm circumference)? I note you've mentioned it's impossible to get the speedo & odo/DTE back to parity but this is well beyond any internal correction factor.
Thanks,
Josh
Coiled PX2 XL dual cab
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
095D should suit your vehicle and give you approx 100km cluster, 96 GPS. You may have to go lower though and it will be trail and error.Kometes wrote: ↑Mon Dec 17, 2018 10:07 pm Hi Stewart,
Similar issue to those posted above, running 255/85R16 on a PX2 auto so I've maxed the BCM out at 0977 however my DTE is out significantly. At the moment I've got a stock tank and I'm getting around 65L before 0km DTE. How are you calculating the corrected PCM value and/or can you please advise the hex for 255/85R16 (~2638mm circumference)? I note you've mentioned it's impossible to get the speedo & odo/DTE back to parity but this is well beyond any internal correction factor.
Thanks,
Josh
Try these first then we will do the PCM.
XL, XLS etc use the same window of allowable change, between eg. XT 0950 and 0980 where an xl may be between 0900 and 0930. Figures are reference and not the min or max figures.
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
-
- Junior Member
- Posts: 10
- Joined: Tue Nov 20, 2018 12:17 pm
- Location: Hastings, Victoria
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 1 time
- Been thanked: 3 times
Hi everyone,
I'm hoping someone can help me out, I have received my USB cable and downloaded FORScan and got it working and i have successfully changed economy screen and a few other things. However, I have changed the BCM 726-12-01 to the max of 0977 from 0934 for my tyre size of 285/65/18 and it doesn't seem to be changing anything. At 100kph on Speedo and gps my ultra gauge is reading 95 and the odo is also the 5% low. Am I missing something? Stewart has been helping and I am very grateful for his time, just wanting to see if anyone else has had problems or can see if I am doing something wrong. Cheers
Sent from my SM-G950F using Tapatalk
I'm hoping someone can help me out, I have received my USB cable and downloaded FORScan and got it working and i have successfully changed economy screen and a few other things. However, I have changed the BCM 726-12-01 to the max of 0977 from 0934 for my tyre size of 285/65/18 and it doesn't seem to be changing anything. At 100kph on Speedo and gps my ultra gauge is reading 95 and the odo is also the 5% low. Am I missing something? Stewart has been helping and I am very grateful for his time, just wanting to see if anyone else has had problems or can see if I am doing something wrong. Cheers
Sent from my SM-G950F using Tapatalk
2018 Wildtrak 3.2 Auto - Provent 200, Ultragauge, Safari Armax snorkel, 3" DPF back exhaust and 285/65/18 Falken Wildpeak AT3W
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
Did you run the "PCM Module initialization/relearn vehicle data" option after changing the BCM value? I discovered that changes to the BCM don't appear to do anything until I run this routine.
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
-
- Junior Member
- Posts: 10
- Joined: Tue Nov 20, 2018 12:17 pm
- Location: Hastings, Victoria
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 1 time
- Been thanked: 3 times
So after doing some testing today, it appears the change has been successful. 0977 has the odo 3% low, the UG reads 96 and the GPS reads 100 and the dash reads 101 give or take a little for fluctuations of course. I knew it wasn't gonna be perfect but I thought it would be a little closer than that. 0934 has it at about 6% low and the UG reads 93 at 100 on the GPS and 98 on the dash. Do these figures sound about right for a 285/65/18? I thought there were people with that size getting their readings almost back to factory. Cheers for the help.
Sent from my SM-G950F using Tapatalk
Sent from my SM-G950F using Tapatalk
2018 Wildtrak 3.2 Auto - Provent 200, Ultragauge, Safari Armax snorkel, 3" DPF back exhaust and 285/65/18 Falken Wildpeak AT3W
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
That is pretty much perfect. Maybe 1kph high.
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
- Trail-Seeker
- Donator
- Posts: 15
- Joined: Tue Oct 02, 2018 2:24 am
- Location: Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: ELM327
- Has thanked: 2 times
- Been thanked: 1 time
My Ranger is running on 265/70/17 from the first day on. Speedo and GPS are max 1KPH appart from each other, doesn't matter if I drive 30 or 160KPH!? Accordig to my dealer they just put the other wheels on, but didn't modify anything. Is that coincidence?
Just got my USB Forscan dongle a few days ago, didn't have time so far to have a look into the BCM yet. Will have to wait until 2019, family has other plans for me in the moment.
Just got my USB Forscan dongle a few days ago, didn't have time so far to have a look into the BCM yet. Will have to wait until 2019, family has other plans for me in the moment.
2018 PXII Wildtrak in frost white, 3.2 Auto, 17x8 TUFF T01, 265/70 BFG A/T, Gobi-X Rock Sliders, Lazer Lamps RRR 750 Elite 3, OBDLinkMX, Rhino Rack
- MikeK
- Donator
- Posts: 83
- Joined: Fri Oct 26, 2018 10:00 am
- Location: Gernsheim, Germany
- Model Of Vehicle: RANGER WILDTRAK PX2
- Year Of Vehicle: 2018
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
- Has thanked: 5 times
- Been thanked: 9 times
@Trail-Seeker, this is great! How does the odometer compare to the Autobahn markers? If the odometer matches the markers, I wouldn't change anything.
Mike
Mike
2018 Wildtrak 3.2L Auto Supercab 4x4 in Pride Orange
-
- New Member
- Posts: 3
- Joined: Sat Aug 19, 2017 7:58 pm
- Location: Hobart
- Model Of Vehicle: RANGER XL PX2
- Year Of Vehicle: 2018
Hi Stewart,saeb wrote: ↑Tue Dec 18, 2018 8:03 pm095D should suit your vehicle and give you approx 100km cluster, 96 GPS. You may have to go lower though and it will be trail and error.Kometes wrote: ↑Mon Dec 17, 2018 10:07 pm Hi Stewart,
Similar issue to those posted above, running 255/85R16 on a PX2 auto so I've maxed the BCM out at 0977 however my DTE is out significantly. At the moment I've got a stock tank and I'm getting around 65L before 0km DTE. How are you calculating the corrected PCM value and/or can you please advise the hex for 255/85R16 (~2638mm circumference)? I note you've mentioned it's impossible to get the speedo & odo/DTE back to parity but this is well beyond any internal correction factor.
Thanks,
Josh
Try these first then we will do the PCM.
XL, XLS etc use the same window of allowable change, between eg. XT 0950 and 0980 where an xl may be between 0900 and 0930. Figures are reference and not the min or max figures.
Just to confirm, I should be trying 095D in the BCM?
Coiled PX2 XL dual cab
- saeb
- Site Admin
- Posts: 4169
- Joined: Wed May 17, 2017 8:50 pm
- Location: Seaford VIC
- Model Of Vehicle: RANGER XLT PX2
- Year Of Vehicle: 2015
- Forscan Dongle Type: Ford VCM
- Has thanked: 295 times
- Been thanked: 1063 times
Correct
Stewart
Ford PX2 Supercab 2015 Automatic
Ford PX2 Supercab 2015 Automatic
-
- Donator
- Posts: 4
- Joined: Mon Dec 31, 2018 11:25 am
- Location: Newcastle, NSW
- Model Of Vehicle: EVEREST TREND UA
- Year Of Vehicle: 2019
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
Hi Stewart,
My dongle arrived today thanks - install went smoothly.
My primary driver for getting the dongle was to try and correct my new MY19 Ford Everest for the larger tyres that I had fitted before pickup.
I have read through this thread and understand the 4% factory underestimate etc...
Factory tyres 265/60/R18 (2433mm)
New tyres 275/65/R18 (2558mm)
Interestingly I just checked the BCM and PCM fields in forscan and they are both set to 0933 / 2355mm, which is 3.3% smaller than the factory tyre
Anyway, in the interests of getting as close as possible to my current 2558mm circumference tyres:
Do I set the BCM field to 0977 as it is the max for my vehicle, or is it possible to set the MY19 higher (I guess ideally to 09FE? Should I experiment if this has not been tested on a MY19 2.0L Everest?)
Re PCM Odometer field - Can you advise what value to set for my tyres if it is not 09FE?
Finally - I have done a "save all" for the BCM and PCM modules as a backup - do I need to do anything else? Is there a tutorial on the steps to update / write new values or do I just hit the write button and disconnect and its done?
Oh - I saw the post about testing non asbuilt options for the MY19 - happy to have a go / look if you let me know what I'm looking for exactly (having not seen it before)
Thanks for your help
Waz
My dongle arrived today thanks - install went smoothly.
My primary driver for getting the dongle was to try and correct my new MY19 Ford Everest for the larger tyres that I had fitted before pickup.
I have read through this thread and understand the 4% factory underestimate etc...
Factory tyres 265/60/R18 (2433mm)
New tyres 275/65/R18 (2558mm)
Interestingly I just checked the BCM and PCM fields in forscan and they are both set to 0933 / 2355mm, which is 3.3% smaller than the factory tyre
Anyway, in the interests of getting as close as possible to my current 2558mm circumference tyres:
Do I set the BCM field to 0977 as it is the max for my vehicle, or is it possible to set the MY19 higher (I guess ideally to 09FE? Should I experiment if this has not been tested on a MY19 2.0L Everest?)
Re PCM Odometer field - Can you advise what value to set for my tyres if it is not 09FE?
Finally - I have done a "save all" for the BCM and PCM modules as a backup - do I need to do anything else? Is there a tutorial on the steps to update / write new values or do I just hit the write button and disconnect and its done?
Oh - I saw the post about testing non asbuilt options for the MY19 - happy to have a go / look if you let me know what I'm looking for exactly (having not seen it before)
Thanks for your help
Waz
MY19 Ford Everest BI-Turbo Trend - Stock + 275/65/18
-
- Donator
- Posts: 4
- Joined: Mon Dec 31, 2018 11:25 am
- Location: Newcastle, NSW
- Model Of Vehicle: EVEREST TREND UA
- Year Of Vehicle: 2019
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
Further to my previous post, a GPS test puts the speedo within 1% of actual - so if I increase to the max figure of "0977" the speedo should read about 3% over which is great.
The same GPS test puts the odometer reading approx 5% lower than actual, based on that intel, any suggestion as to what I should change to current PCM 0933 value to?
Cheers
Waz
The same GPS test puts the odometer reading approx 5% lower than actual, based on that intel, any suggestion as to what I should change to current PCM 0933 value to?
Cheers
Waz
MY19 Ford Everest BI-Turbo Trend - Stock + 275/65/18
-
- Donator
- Posts: 4
- Joined: Mon Dec 31, 2018 11:25 am
- Location: Newcastle, NSW
- Model Of Vehicle: EVEREST TREND UA
- Year Of Vehicle: 2019
- Forscan Dongle Type: SAEB Forscan Dongle WIN10
My apologies for the repeated messages.
Ive just had my first attempt at making edits to MY19 Everest Trend, and it was a fail unfortunately
Changed
BCM 726-12-01 = 0977
After an ignition restart the car threw DTC P160A (indicator)
Clearing it did not resolve the DTC
A relearn PCM option that I have seen mentioned in other threads does not appear for me in forscan
Then tried to change
PCM 7E0-01-01 = 60AE (which I convinced myself was the correct value for 275/65/18)
When attempting to write this I got the following error "Writing blocks failed - incompatible configuration"
I then changed the BCM back to factory, cleared the codes and gave up for the day
Any feedback appreciated.
Cheers
Waz
Ive just had my first attempt at making edits to MY19 Everest Trend, and it was a fail unfortunately
Changed
BCM 726-12-01 = 0977
After an ignition restart the car threw DTC P160A (indicator)
Clearing it did not resolve the DTC
A relearn PCM option that I have seen mentioned in other threads does not appear for me in forscan
Then tried to change
PCM 7E0-01-01 = 60AE (which I convinced myself was the correct value for 275/65/18)
When attempting to write this I got the following error "Writing blocks failed - incompatible configuration"
I then changed the BCM back to factory, cleared the codes and gave up for the day
Any feedback appreciated.
Cheers
Waz
MY19 Ford Everest BI-Turbo Trend - Stock + 275/65/18