Jump to content

Recommended Posts

Posted

I have a 97 K1500 and the brake pedal would go to the floor when I pressed it. I did a full brake job on the front (calipers, pads, rotors). The rear shoes and drums were in good shape so I put them back on without changing. The brake fluid was black so I bled the reservoir and all four brake lines in correct sequence using a Mityvac 6835 brake bleeder. I bled all the lines two times just to make sure I got all the old black fluid out.

 

Once I got it back together the pedal would only hold pressure briefly and then go to the floor again, and now the red check brake light will go on and off once the pedal drops.

 

Any ideas?

 

 

Thank you

Posted

Did you adjust the shoes on the rear out as far as possible? If not, the pedal can go to the floor.

Posted

Yes, I adjusted them all the way up to where they had a decent amount of drag when I put the drums back on. They can't be adjusted from the back while the drum is on so I got them up as high as possible before I reinstalled the drums. I briefly get pressure in the pedal but then it drops and the check brake light comes on.

Posted (edited)

I had the soft pedal problem before the bleed too. I don't think there is a lot of air in the system since I was pulling it through the lines using vaccum. I let each line bleed for about one minute and I sealed each bleeder screw while the machine was still pulling fluid through the line. I guess the master cylinder is the only thing left.

Edited by tommy99
Posted

So I bench bled and swapped out the master cylinder. Vacuum bled all of the lines again with about 45 secs of vacuum on each line. I'm still getting the red check brake light and the pedal is soft and going to the floor. I'm not getting any leaks in the lines or bleeders. Has anyone had a similar experience? Is it possible there is some air trapped in the ABS? Would the yellow ABS light come on if there was air in it, because I'm not getting the ABS light.

 

Any ideas?

Posted

It was two bad wheel cylinders. I was re-bleeding the brakes and one of them finally popped. Both wheel cylinders were slightly leaking but the dust boot was catching the brake fluid before it could pour out.

  • 3 weeks later...
Posted

Brake fluid absorbs water and should be replaced every couple of years. Water is heavier than brake fluid, so the water collects in the wheel cylinder. The water causes the cylinder to pit, and eventually leak.

Posted (edited)

Brake fluid absorbs water and should be replaced every couple of years. Water is heavier than brake fluid, so the water collects in the wheel cylinder. The water causes the cylinder to pit, and eventually leak.

 

I bleed my brakes every year, but this is a friend's truck, and it was heavily neglected. I doubt that fluid had ever been changed. I disassembled both wheel cylinders and they were pitted and scarred.

 

To add to this topic.. The ABS system was also damaged. I'm guessing the damage was caused by the dirty brake fluid since it seemed to ruin everything else it came in contact with. The replacement ABS unit will be here in a couple of days. Once I get it swapped out, and everything is working, I will disassemble the old ABS valve body to see how bad it looks. I can post pics if anyone is interested.

Edited by tommy99
  • 2 weeks later...
Posted

Wow, so this brake job saga is finally over. I replaced the master cylinder, ABS unit, rotors, pads, calipers, drums, shoes, springs, and wheel cylinders. I would get a solid pedal when it was up on jacks but as soon as I started driving the pedal would drop down and start pulsating. I wasn't getting any check lights, and I bled the entire system and bench bled the master cylinder multiple times, but every time I would get on the road the pedal would pulsate up and down as soon as I pressed it.

 

Well I finally figured out what was wrong after weeks of working on this thing. The dirty brake fluid didn't just destroy the rubber in the wheel cylinders, it also started eating up the rubber flex lines from the inside. They got so weak that as soon as I would apply the brake and build pressure in the lines they would start expanding and collapsing. The fluctuation of pressure in the lines would make the pedal pulsate up and down. After changing all of the flex lines I got a solid braking system.

Posted

Good to see all the knowledge here on brakes.i have the same truck but mine is a diesel.Brakes are okay but should be much better.They will not skid the front wheels on hard braking,only back will skid if hard braking.New front pads,calipers and rotors.Rear has new drums,shoes and wheel cylinders. To me you have to push peddle with to much effort to make truck stop.All that is left is Hydrabooster on a diesel and the Master cylinder.No visible leaks on either unit.What you all think?I think there is not enough braking pressure to front wheels.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...