Sponsored

U0422 After Tire Size Change

Stangman570

Well-Known Member
Joined
May 31, 2019
Threads
21
Messages
404
Reaction score
1,030
Location
Florida Panhandle
Vehicle(s)
2019 Ford Ranger 4x4 XLT Sport
Got my new BDX SCT tuner in. Has anyone been successful with clearing the U0422 after changing the tire size?

It's not throwing a MIL and I have confirmed it's only occurring with the tire size change. I flashed it back to stock and read zero active codes. I can flash it to the 93 tune and scan for codes with zero hits.

I set the tire size to my 295/70/17's that are around 33.46 to 33's and flash it. Clear the code followed by an immediate read and I get the U0422. No biggie, just wondering if someone figured out how to get rid of it?
Sponsored

 
Last edited:

ControlNode

Well-Known Member
First Name
John
Joined
Nov 29, 2021
Threads
16
Messages
1,709
Reaction score
3,641
Location
Eastern NC
Vehicle(s)
84 Civic "2000S"/16 Focus RS/21 Ranger XLT
Occupation
Computers
I'm not sure but try seeing if 265/70R17 throws the same error.

I reason for suggesting this is that I know with the Ford ProCal kit they say you can configure up to that size. Perhaps the limitation is not the programmer but instead the BCM? If this is the case when using a programmer that does not have a soft limit in it the BCM bulks at the value and throws the code.
 
Last edited:

RedlandRanger

Moderator
First Name
Rob
Joined
Nov 14, 2018
Threads
42
Messages
5,111
Reaction score
11,105
Location
Oregon
Vehicle(s)
2019 Ford Ranger Lariat FX4, 1973 Mercury Capri
Vehicle Showcase
1
I've not seen anyone who has had success getting rid of that code. It doesn't throw the CEL, so it doesn't seem like it is a big deal.
 
OP
OP
Stangman570

Stangman570

Well-Known Member
Joined
May 31, 2019
Threads
21
Messages
404
Reaction score
1,030
Location
Florida Panhandle
Vehicle(s)
2019 Ford Ranger 4x4 XLT Sport
I'm not sure but try seeing if 265/70R17 throws the same error.

I reason for suggesting this is that I know with the Ford ProCal kit they say you can configure up to that size. Perhaps the limitation is not the programmer but instead the BCM? If this is the case when using a programmer that does not have a soft limit in it the BCM bulks at the value and throws the code.
It seems that I read that somewhere that there was a limitation. I'll have to try and see if that is the limit.
 
OP
OP
Stangman570

Stangman570

Well-Known Member
Joined
May 31, 2019
Threads
21
Messages
404
Reaction score
1,030
Location
Florida Panhandle
Vehicle(s)
2019 Ford Ranger 4x4 XLT Sport
I've not seen anyone who has had success getting rid of that code. It doesn't throw the CEL, so it doesn't seem like it is a big deal.
Agreed, I just hate to see it when scanning for codes. Came across this while troubleshooting a blis issue I had this weekend. But your right, as long as it never throws a CEL and I'm spot on with the speedometer correction then I'm all good.
 

ControlNode

Well-Known Member
First Name
John
Joined
Nov 29, 2021
Threads
16
Messages
1,709
Reaction score
3,641
Location
Eastern NC
Vehicle(s)
84 Civic "2000S"/16 Focus RS/21 Ranger XLT
Occupation
Computers
I've not seen anyone who has had success getting rid of that code. It doesn't throw the CEL, so it doesn't seem like it is a big deal.
While it does not trigger CEL, it could still be a warranty voiding code, if it is only thrown for over size wheel and your rear diff explodes, no warranty. And that makes sense to me due to the extra load a taller tire puts on the 3.73 diff. Going up enough in tire size and should look to 4.11:1, or even 4.70:1, ratio options for the final drive gear set(s).
Sponsored

 
 








Top