Jump to content

Recommended Posts

Posted

I have a 1999 Chevy Silverado 1500 Z71 and am having issues with my ABS. When coming to a stop, the ABS will kick in when under 10ish mph. I started to happen after I changed my driver front wheel bearing. It was a cheap Ebay bearing, so, now, about 3-4 months later, I bought a new wheel bearing and installed it today to see if it changed. Nope. When I changed it a couple months ago, the ABS & Brake light would come on but reset when I would shut the truck off. The ABS pump is not having the typical issue where it runs non-stop, but it kicks in for no reason.

Posted

I'm experiencing the exact same problem. Almost caused me to rear end someone yesterday as I was almost stopped when it kicked in and then I couldnt stop anymore and almost rolled right into the back of him.

 

Theres a TSB out there 03-05-25-007d that says its caused by an increased air gap between the wheel speed sensor and hub reluctor ring due to rust and debris build up on the sensor mounting surface.

 

Hopefully someone can post the TSB, for some reason I cant copy paste it.

Posted

I have been having a similar problem. I have been noticing that if I hit a bump while on the brakes, the ABS will kick in almost like I lose my brakes for a second, but I can feel the pulsation in the pedal. Then the brakes will "catch" and it's like I hit the brakes too hard all of a sudden. I also get the ABS and brake light from time to time, but it always resets once you turn the key off like the OP described.

Posted

On my '98 Silverado the mounting surface below the sensor began to corrode, causing the sensor to lift. It only lifted like a millimeter, but enough that the sensors would have issues reading. I never had an ABS light go on, but I had issues at stopping speed where my ABS would go off (pulsating pedal). This was because my front sensors could not get a good reading, didn't match with the rear wheel speed, thus a time ABS should engage. I used a wire brush to clean up the mounting surfaces, worked like a charm! Before doing this I put in a paper towel to the hole to plug it up so debris wouldn't go inside it.

Posted

Swhitney is right. The problem is called "unintended low speed ABS activation". There was a recall for trucks in the "rust belt". Undo the torx screw that holds the ABS "reader" to the hub and pull it out. Put a piece of paper towel in the hole and use some emery cloth to remove the corrosion on the mounting pad. Just a millimeter of corrosion will hold the reader far enough away from the sensor to cause low speed activation. Put some grease on the mounting pad and tighten the reader back to the hub. Problem solved.

  • Like 1
Posted
On my '98 Silverado the mounting surface below the sensor began to corrode, causing the sensor to lift. It only lifted like a millimeter, but enough that the sensors would have issues reading. I never had an ABS light go on, but I had issues at stopping speed where my ABS would go off (pulsating pedal). This was because my front sensors could not get a good reading, didn't match with the rear wheel speed, thus a time ABS should engage. I used a wire brush to clean up the mounting surfaces, worked like a charm! Before doing this I put in a paper towel to the hole to plug it up so debris wouldn't go inside it.

 

My 97 would get like this too, did as swhitey did above and cured it, for a while then had to re-do it about every year year and a half.

Posted

i had this same problem with my truck... ended up being my abs speed sensor... When my mechanic went to take them out and clean off the rust on hub they both broke... $230 each side later :lol: it drives like new again... :banghead: but was a costly repair... I could have go the sensors cheaper online but my truck was in shop with both wheels off / calipers.. and i needed it next day so the stealership was only option :thumbs:

Posted

I had the same issue, my Passenger side was already pooched, and I probably helped the issue along when I pulled the sensor out and part of it stayed in the hub assembly. Luckily, my shop had a used sensor for $30 bucks, plus an hour of shop time.

 

If you feel like it, CAREFULLY pull the sensors out, and go from there.

Posted

If and when you pull the sensors out, be prepared to buy new ones... I trust my shop , good friend of our family, and both sensors broke when they tried removing them.. Then the problem was the plastic piece stayed inside so it took them even longer to remove it.. Just prepare for the worse... :crazy:

Posted
I have a 1999 Chevy Silverado 1500 Z71 and am having issues with my ABS. When coming to a stop, the ABS will kick in when under 10ish mph. I started to happen after I changed my driver front wheel bearing. It was a cheap Ebay bearing, so, now, about 3-4 months later, I bought a new wheel bearing and installed it today to see if it changed. Nope. When I changed it a couple months ago, the ABS & Brake light would come on but reset when I would shut the truck off. The ABS pump is not having the typical issue where it runs non-stop, but it kicks in for no reason.

 

Any chance you have the ABS codes?????? Cxxxx.................. Could be the control module

 

Jbo

Posted

I pulled the sensor on the passenger side and cleaned it up, came out ok, and wasn't all that dirty. It had 3 shims on it, in which i left all 3 on, but cleaned them all up. Before I even left the driveway, abs kicked in again. I pulled the fuse until I can get it to the dealer because I have had many close calls and it's getting annoying. Last night when I came home from work, just perfect, no issues....Today, I drove 1 mile over to my grandparents and it did it about 2 or 3 times that I had to slow down to stop.

Posted

those are the same symptoms i had... Did you clean rust off hub? if so then you need new sensors... If you can , avoid going to dealer for them and get them online... i needed my truck right away and only option i had was dealer and paid dearly for it

Posted

The driver sensor is brand new because it was with the bearing. Even the passenger side bearing/sensor is just over a year old and looked just fine. Unless it's my rear abs sensor, which is in the rear axle or transfer case, I'm not sure. I'm getting tired of screwing with it. The dealer can tell me what's wrong with it, because I give up

Posted

When I owned my 2001 I got a recall notice for this problem. I didn't have the problem so I never took my truck in, but I am pretty sure that GM was going to cover it. I might be worth while for you guys to look into it by calling the dealer.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   2 Members, 0 Anonymous, 2,875 Guests (See full list)


  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...