- Replies 3
- Views 1.4k
- Created
- Last Reply
Top Posters In This Topic
-
jathanmentzer 2 posts
-
Mopar1973Man 1 post
Popular Days
Most Popular Posts
-
Me personally, I would have avoided the Powerstop kit. The ceramic brake pads will eat the rotors before eating the pads. When I look at the pad life on my own truck at 180k miles for my first set. My
I know, old topic. It's just that no one seems to be in the same situation I am. I just finished replacing front rotors, calipers, and pads (Powerstop Z36 kit) and discovered the passenger side hub was shot, spun like a fidget spinner. Also replaced the driver side axle shaft assembly since the threads got screwed up taking the nut off. Anyway, I also threw a new ABS sensor on the driver side hub from a brand new bearing my friend messed up and gave to me, since I had access to it. I get everything back together, bleed the brakes, and as soon as I cross the 20-25 mph mark, the ABS/Brake Christmas tree lights up. Does not come on with brake pedal action, comes on when I hit that speed range and then doesn't go off until I turn the truck off. Pedal feels mushy compared to before, but I think that's an unrelated bleeding issue. Of course 2 minutes into the bed-in procedure and Bambi wants to say hi, knocked my front license plate off but that was it (lights came on before running over deer btw). Not sure what would be causing this, I read the other threads and I doubt that it's a tone ring issue since one hub is new (Timken) and the other was just fine beforehand. Front ABS doesn't do much of anything (Don't feel anything in the pedal either), but it didn't do much before the job either. I forgot to disconnect the batteries when changing the sensors, but disconnecting them later did not change anything. Also, the parking brake light works as designed before I hit 20-25 mph and it stays on, so I doubt it's anything with that system specifically. 4wd light does not come on unless I put it on 4wd, so nothing unusual there. The only area I touched was the front hub/brake assembly, so that must be where some change is causing an error, just not sure what. Any help is appreciated, thanks.