I recently posted about the lights showing up on my dash, and people suggested I replace the wheel sensors. So, I went ahead and replaced them all, but the lights are still there.
I used a professional OBD reader, and it’s not detecting any codes.
The hill hold feature works for a second, then the lights come on. What else could be causing this?
How far have you driven since changing the sensors?
Kai said:
How far have you driven since changing the sensors?
Not even 60 feet. I cleared the codes, but the lights came back on almost immediately.
Kai said:
How far have you driven since changing the sensors?
Not even 60 feet. I cleared the codes, but the lights came back on almost immediately.
You might need to drive it a bit more. Sometimes, the sensors need data after a reset. Like when you clear codes and take it for an emissions check, they’ll often say to drive it for around a hundred miles first so it has enough data to run on.
@Kai
So if the hill hold triggers a code just by backing out of my driveway, do I need to clear it again before driving those 100 miles?
Gregory said:
@Kai
So if the hill hold triggers a code just by backing out of my driveway, do I need to clear it again before driving those 100 miles?
I’d just drive it for a while and see if it sorts itself out now that the new sensors are in.
The issue might be in the parking brake control module. It usually stores codes for things like this. If not, check the anti-lock brake module. A full professional scan tool should be able to tell you which module has the code. Basic scanners often can’t read all the modules.
@Troy
I’m using an Autel AL619, which isn’t cheap. It shows ‘Control Module’ but doesn’t specify which one. The code is U3000:48-68 Control Module CMDTCs.
Gregory said:
@Troy
I’m using an Autel AL619, which isn’t cheap. It shows ‘Control Module’ but doesn’t specify which one. The code is U3000:48-68 Control Module CMDTCs.
That code is pretty generic. You’ll probably need more specific details.
@Troy
Any idea how to get more details with this scanner?
That code could mean there’s an internal error in the ABS module.
You might want to use an OEM-level scan tool like IDS or Forscan. Check those codes with a proper diagnostic tool, fix what needs fixing, and then clear the codes.
Clayton said:
You might want to use an OEM-level scan tool like IDS or Forscan. Check those codes with a proper diagnostic tool, fix what needs fixing, and then clear the codes.
Alright, I’ll look into getting Forscan.
Quick update… I found another function on my OBD reader and the code is:
U3000:48-68.
Gregory said:
Quick update… I found another function on my OBD reader and the code is:
U3000:48-68.
Here’s a link that might help: https://www.fordescape.org/threads/at-a-loss-with-abs-brake-tcs-lights-coming-on-hill-start-unavailable-u3000-48-error.120581/
@Dallas
I read through that thread. Aside from checking the battery terminals, I’m not sure what else to try. Tomorrow, I’ll check the maxi fuses, but I’m feeling a bit lost here.
Gregory said:
@Dallas
I read through that thread. Aside from checking the battery terminals, I’m not sure what else to try. Tomorrow, I’ll check the maxi fuses, but I’m feeling a bit lost here.
Maybe consider taking it to a shop that specialises in ABS systems. Dealerships can be pricey, but it might save some headaches since ABS isn’t really a DIY fix most of the time.
@Dallas
I just drove it around a bit, and as long as the hill assist doesn’t activate, the ABS and traction control work fine. But if I stop on a hill and let the hill assist engage, everything shuts off. Wondering if this could point to an issue with the parking brake control module?
Every time I clear the code, it only comes back when I stop on a hill.
I had some errors showing up too, but they’d disappear if I restarted the engine. Ended up changing the battery, and since then, no issues. Not sure if that fully solved it, but it’s working so far.