- First Name
- Austin
- Joined
- Jan 3, 2025
- Threads
- 1
- Messages
- 7
- Reaction score
- 9
- Location
- Portland, OR
- Vehicle(s)
- Bronco
- Your Bronco Model
- Wildtrak
- Thread starter
- #16
This is exactly what I am experiencing. You think it is all working because the dash and GOAT switch both indicate that the drivetrain is in either 4H or 4L. Until you're stuck and the front wheels are just sitting idle. Then when the vehicle realizes there is no front wheel speed while the rears are turning it disables the 4x4... which obviously wasn't working in the first place.What I found out with the FAD was that it wouldn't throw a code until you got into a condition where it expected all 4 wheels to be turning, but the front's weren't.
So if you were just tooling down the road with decent traction in 4H/4L, and the fronts were rolling along, the Bronco (and I) thinks everything is just ok. It wasn't until the rear wheels lost traction and you were hoping the fronts would pull you out that it would throw a code (and I would start throwing things).
Now, I'm not sure if the Tcase has a feedback signal that checks engagement, or even if it does if the failure mode couldn't work around that anyway in the case of what may be the cause of this.
Not sure how I could test the 4A. I tried to a bit this morning on some dirt roads but the tires still had too much grip to tell me anything definitive.
Sponsored