Forscan wheel change not working

[Mumblemouth]

Heyall..so I have a 24 BD non sas. But I’ve since added sas take offs and wheels. I was initially off by 4mph. I’ve since returned w Forscan and bumped up to 2800 (tire calculator said the actual tire size is 2741) I’m still off by 3mph. Am I missing something? I appreciate any advice.

Sponsored

 

[Mumblemouth]

Heyall..so I have a 24 BD non sas. But I’ve since added sas take offs and wheels. I was initially off by 4mph. I’ve since returned w Forscan and bumped up to 2800 (tire calculator said the actual tire size is 2741) I’m still off by 3mph. Am I missing something? I appreciate any advice.

Correction, I’ve bumped up to 2750 not 2800

 

[Beach_Bum]

The actual rolling radius is smaller than the stated spec from the manufacturer. If you read through a number of threads on tire size/speedo calibration in the ForScan sub-forum, you will find that many who have swapped to a Sasquatch wheel/tire have found 2600 to be accurate.

 

[Mumblemouth]

The actual rolling radius is smaller than the stated spec from the manufacturer. If you read through a number of threads on tire size/speedo calibration in the ForScan sub-forum, you will find that many who have swapped to a Sasquatch wheel/tire have found 2600 to be accurate.

Yeah that’s what I’ve read. I guess I’m a little confused..for example, my speedo says I’m going 65 but gps says I’m going 62. So I need to dial it back not forward?

I apologize if that’s a dumb question..it’s just getting mixed up in my brain.

 

[Beach_Bum]

Yeah that’s what I’ve read. I guess I’m a little confused..for example, my speedo says I’m going 65 but gps says I’m going 62. So I need to dial it back not forward?

I apologize if that’s a dumb question..it’s just getting mixed up in my brain.

One thing is to check against different GPS apps. I assumed they were all the same. Just downloaded the first from the Play Store. It was wildly off. I tested it a few times with the same inaccuracy. Downloaded 2 other apps and they were both accurate with respect to each other.

At the moment my speedo is accurate up to 70, then I'm going about 1mph faster over 70. I figure the heat with my mud terrains actually change the rolling radius at speed causing the discrepancy.

Here is @EvilJim1971 response to another in a different thread. The OP actually had to adjust his to 2580. There are a number of factors that can cause a discrepancy between one Bronco to another such as inflation PSI and the trim (2 vs. 4 dr; mass of the vehicle).

 

[Mumblemouth]

One thing is to check against different GPS apps. I assumed they were all the same. Just downloaded the first from the Play Store. It was wildly off. I tested it a few times with the same inaccuracy. Downloaded 2 other apps and they were both accurate with respect to each other.

At the moment my speedo is accurate up to 70, then I'm going about 1mph faster over 70. I figure the heat with my mud terrains actually change the rolling radius at speed causing the discrepancy.

Here is @EvilJim1971 response to another in a different thread. The OP actually had to adjust his to 2580. There are a number of factors that can cause a discrepancy between one Bronco to another such as inflation PSI and the trim (2 vs. 4 dr; mass of the vehicle).

Ah..mine is a 2dr. And I downloaded 3 different gps apps just to be sure. They all read the same except one which is pretty far off. So if my speedo is reading over my gps, I need to bring the number down not up, correct?

 

[Ducati1098]

Ah..mine is a 2dr. And I downloaded 3 different gps apps just to be sure. They all read the same except one which is pretty far off. So if my speedo is reading over my gps, I need to bring the number down not up, correct?

Whatever you calculate as far as circumference, the forscan value will always need to be typically ~5% lower

 

[Beach_Bum]

Ah..mine is a 2dr. And I downloaded 3 different gps apps just to be sure. They all read the same except one which is pretty far off. So if my speedo is reading over my gps, I need to bring the number down not up, correct?

Sounds right.

Not sure why the different GPS apps aren't reading the same. The premise behind them is fairly straightforward. But I experienced the same as the one app wasn't even close. Really messed with my thinking trying to understand how it could be.

For reference, there was a thread that compiled the OEM BdyCM Dimensions.

 

[Mumblemouth]

Sounds right.

Not sure why the different GPS apps aren't reading the same. The premise behind them is fairly straightforward. But I experienced the same as the one app wasn't even close. Really messed with my thinking trying to understand how it could be.

For reference, there was a thread that compiled the OEM BdyCM Dimensions.

Thank you so so much. I had it entirely backwards hahah!

Sponsored