There is a maximum circumference that can be used. Not sure why. I played around just to see what would happen and had the same errors pop up. Set it back to the max of...whatever it is...and used forscan to clear the codes. (That maximum value is in this thread somewhere) No issues after that. Speedo is about 8% under gps.
Lmao. I take it you didn’t see my reply?
Yeah it doesn't make sense to me why there is a limit. They must have their reasons.I did - but at the time I was still trying to figure out what that ABS code was all about and how to clear it. My brain just was not thinking that exceeding the max size would cause it. So I filed in the back of my mind under "shit to remember if I get a "tire size too big" sounding error (ha ha)
BTW - I just scanned that thread you linked to and still didn't see the actual number. But, I guess, I now know it's somewhere between 2775 and 2921
Dealer was able to correct the error, they said they had to change/update a couple of modules. I believe they used whatever specs the Sasquatch package has. Drives and handles much better now, but my speedo is now about 5mph above gps. I will reach out to them again on Monday.
THANK YOU for posting and updating this info! Worked like a charm. I wanted to share my experience for others who might be in the same boat.Use the PCM service function instead of the PCM relearn. The PCM relearn doesn't work.
UPDATE: on new Forscan versions (2.3.52+), " PCM Module initialization/relearn vehicle data" is reported to work.
Detail:
1- I used FORScanSetup2.3.47.test20220221 (version that supports MY2022 goat modes) with OBDLink EX. You will also need a FORScan demo license.
FORScanSetup2.3.47.test20220221.exe
2- Set front/rear TPMS and tire size in BdyCM. For KM3 37x12.50R17D on sasquatch wheels, use 35psi and 2760mm. For sasquatch stock tires and wheels, use 39psi and 2653mm. Tire circumference cannot exceed 2800mm. DTC's will be set in 2-3 modules that will need to be fixed.
3 - To fix the non-PCM DTC's, run the AWD relearn. Don't run the PCM relearn (it doesn't work).
4 - Clear the DTC's. All should be cleared except PCM.
5 - Run the PCM reset-all-adaptations service function. This will fix the size mismatch and also clear the PCM DTC. It will relearn the engine/trans/fuel adaptations over time while driving. UPDATE: on new Forscan versions (2.3.52+), " PCM Module initialization/relearn vehicle data" is reported to work.
6 - Confirm all DTCs are cleared.
7 - Install a free speedometer app with tenth-mph readout on your phone and testdrive to confirm speed is within 0.5mph at 60mph cruise control. For new tires, the actual speed should be a little higher than speedo. For worn tires the actual speed will be a little less.
2770mm for my 37” is right on.I did - but at the time I was still trying to figure out what that ABS code was all about and how to clear it. My brain just was not thinking that exceeding the max size would cause it. So I filed in the back of my mind under "shit to remember if I get a "tire size too big" sounding error (ha ha)
BTW - I just scanned that thread you linked to and still didn't see the actual number. But, I guess, I now know it's somewhere between 2775 and 2921
It seems the digital speedometer will always read 1 mph low when calibrated correctly as it persists across the whole range of speeds.
Yes it’s very much a trial and error it seems. Went to the 285/75/17 for my winter tire package and seems like 2567 got me bang on. Always found the 2653 was off by a mph showing higher than actual right from stock so this fixed change and I’ll wait to see how it is once I put the Sasquatch tires back on in spring.
