Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!
ABS Brake bleed with Foxwell
- Martinthetinman
-
Topic Author
- Offline
- New Member
-
2 months 1 week ago #83006
by Martinthetinman
ABS Brake bleed with Foxwell was created by Martinthetinman
Hello, I have a 2002 Buick LeSabre that I am attempting to bleed the ABS module. I purchased the Foxwell NT650Elite to do the job. Unfortunately, I can not get the scanner to do the bleed.
I did a Quick Scan and read the codes....there were a couple....one referred to a bad wheel sensor. Not sure about the others but they didn't seem to be related to the module. I erased the codes . I then started bleed process, when I tried to proceed I got the message that DTC were present and they needed repaired before the test could continue. I am not understanding why ? Codes are cleared so how can it detect DTC? Irregardless, why would I have to repair unrelated dtc to do a bleed ? I assume I'm doing something wrong, please help. I have contacted Foxwell and they offer no assistance. Thanks
I did a Quick Scan and read the codes....there were a couple....one referred to a bad wheel sensor. Not sure about the others but they didn't seem to be related to the module. I erased the codes . I then started bleed process, when I tried to proceed I got the message that DTC were present and they needed repaired before the test could continue. I am not understanding why ? Codes are cleared so how can it detect DTC? Irregardless, why would I have to repair unrelated dtc to do a bleed ? I assume I'm doing something wrong, please help. I have contacted Foxwell and they offer no assistance. Thanks
Please Log in or Create an account to join the conversation.
2 months 6 days ago #83072
by Tyler
I've run into the same issue with GM products. All the wheel speed sensor circuits MUST be working correctly for the bleed function to work. Even if you clear the fault codes and immediately launch into the bleed function, the EBCM can still detect a wheel speed sensor circuit fault. The wheel speed circuits are monitored at all times with the ignition on.
Short answer is that the fault code is related because the GM engineer wanted it to be related.
If they didn't think it was related, they would have written the programming for the EBCM differently.
Why do they think it's related? I've always wondered the same. Liability, maybe? Never really got a satisfactory answer.
I really don't think you're doing anything wrong. You're just seeing the EBCM reacting to a fault the way it's programmed to. Even if Foxwell does answer, they won't be much help, as it's not really a scan tool problem.
Replied by Tyler on topic ABS Brake bleed with Foxwell
I then started bleed process, when I tried to proceed I got the message that DTC were present and they needed repaired before the test could continue. I am not understanding why ? Codes are cleared so how can it detect DTC?
I've run into the same issue with GM products. All the wheel speed sensor circuits MUST be working correctly for the bleed function to work. Even if you clear the fault codes and immediately launch into the bleed function, the EBCM can still detect a wheel speed sensor circuit fault. The wheel speed circuits are monitored at all times with the ignition on.
Irregardless, why would I have to repair unrelated dtc to do a bleed ?
Short answer is that the fault code is related because the GM engineer wanted it to be related.
Why do they think it's related? I've always wondered the same. Liability, maybe? Never really got a satisfactory answer.
I assume I'm doing something wrong, please help. I have contacted Foxwell and they offer no assistance.
I really don't think you're doing anything wrong. You're just seeing the EBCM reacting to a fault the way it's programmed to. Even if Foxwell does answer, they won't be much help, as it's not really a scan tool problem.
Please Log in or Create an account to join the conversation.
Time to create page: 0.387 seconds