FORScan tire size issues
I need help with FORScan. I'm trying to change the tire size from a 275/65r18 to 275/70r18. I thought I was supposed to change 726-12-01 to like 09ff but it didn't allow that. I do not have access to the laptop used until tomorrow.
|
I don’t believe anyone has gotten forscan to actually change the tire size. I think the only way anyone has gotten it to work on a sub 2015 model is by using a programmer.
|
The sticky at the top should have the info you seek.
|
Worked on my 2014, but 2011-2013 haven't had success.
|
Originally Posted by jdunk54nl
(Post 6228099)
Worked on my 2014, but 2011-2013 haven't had success.
i successfully stopped hyperflash with forscan. Maybe I’ll give the tires a shot to see if I’m lucky. I know some 2012 and 2013 guys were unsuccessful with hyperflash removal. I know the most recent update added a lot of plain English settings compared to previous versions. Maybe that’s why I was successful removing hyperflash. |
Originally Posted by LexPD
(Post 6228105)
Interesting. I didn’t know it would work on a 2014. Do you know what the difference is between 13 and 14 that would make it work?
i successfully stopped hyperflash with forscan. Maybe I’ll give the tires a shot to see if I’m lucky. I know some 2012 and 2013 guys were unsuccessful with hyperflash removal. I know the most recent update added a lot of plain English settings compared to previous versions. Maybe that’s why I was successful removing hyperflash. |
Originally Posted by jdunk54nl
(Post 6228111)
No clue, it might also be late model 14's compared to early models. My truck production date was July 2014 so it might have been close enough to the 2015's production that it got some of the different circuitry.
|
The "plain english" settings in Forscan have nothing to do with it. That just means the programmer is confident enough in a particular value change to make it a menu item. It is still doing the same work, changing a hex value in the Ford module, you just don't see it directly. It's all based on the Ford hardware, whatever the differences are.
|
Originally Posted by Spiky
(Post 6228171)
The "plain english" settings in Forscan have nothing to do with it. That just means the programmer is confident enough in a particular value change to make it a menu item. It is still doing the same work, changing a hex value in the Ford module, you just don't see it directly. It's all based on the Ford hardware, whatever the differences are.
|
Rnlcomp has posted that IDS also does not work. It's a Ford problem with how the PCM responds to the different kinds of access.
|
Originally Posted by Spiky
(Post 6228368)
Rnlcomp has posted that IDS also does not work. It's a Ford problem with how the PCM responds to the different kinds of access.
I have no need to try it as I have a tuner but if someone does and reports it works I can update the spreadsheet. |
I reprogrammed the tire size on my 2012 Lariat with Forscan about a week ago, using one of the options in the plain language menu, and it seems to have done the job. Torque was reading about a 3-4 mph variation between GPS speed and OBD speed before the change, now reads about .5 mph off. Actual speedometer is still about half a needle width off when I'm running Waze.
I initially got the P160A code, did the BCM/PCM relearn, and it went away. |
Originally Posted by jdunk54nl
(Post 6228111)
No clue, it might also be late model 14's compared to early models. My truck production date (or at least in service date) was July 2014 so it might have been close enough to the 2015's production that it got some of the different circuitry.
|
All times are GMT -4. The time now is 10:12 AM. |
© 2024 MH Sub I, LLC dba Internet Brands