Jump to content

Intermittent Intellitrak & ABS warning lights

Evan Sanders
 Share

Recommended Posts

Evan Sanders New Member

Evan Sanders

Posted
Posted (edited)

Hi all, first post here so please excuse any FNG stupidity (I tried searching for this but not a ton of luck finding actual solutions).  I have a 2009 Suburban that the cruise stopped working on a few years ago.  I don't use it much so I never did anything about it.  Recently I'm starting to get warning lights that Intellitrak and ABS need service, usually this happens only on colder mornings (California cold, so like 50 degrees or so).  Also recently I've started having an issue with the park interlock not letting the truck shift out of park, again usually on cold starts and very rarely when the truck is warm.  I have a feeling that there's a common sensor that these systems use that is causing all or most of these failures, and am hoping that someone can help me narrow down where to look without having to jiggle every electrical connection at every wheel to try to figure out which one might be the culprit.  Can anyone loan me a clue? 

 

I've had this truck since 2010 and have done all the maintenance and repairs on it myself.  It's in great shape for having been through 5 kids and I'm starting the process to get it more suited towards light four wheeling for the purpose of getting my wife and I to remote trailheads so we can backpack deeper in the wilderness.  Step one is to take care of these things that effect safety and drivability, step two will be to fix random things that never bothered me enough to fix until now just to get the truck to 100% before I start in on the fun stuff.

Edited by Evan Sanders
MaverickZ71 Senior Enthusiast

MaverickZ71

Posted
Posted (edited)

Too many possibilities.  Almost any trouble code can throw a Stabilitrak/ABS warning, even it the problem has nothing directly to do with Stabilitrak/ABS.  You need to get the codes read.  It could very well be the shifter safety interlock.  Some auto parts places will scan codes for you for free (because they want to sell you the subsequent parts).  Or if you subscribe to OnStar, press the blue button and tell them you want a remote diagnostic run and for them to tell you the code number(s).  Then you can look the code number up on the internet to see what the common fix is.  Last resort is to bite the bullet and pay the GM dealer $100+ per hour for an initial diagnosis.  

Edited by MaverickZ71
Evan Sanders New Member

Evan Sanders

Posted
  • Author
Posted

Yeah I was a little premature posting this, I have a code reader and just haven't hooked it up yet.  Hoping for the easy answer I suppose.

ecard_926 Enthusiast

ecard_926

Posted
Posted

I had this same thing happen to me. Didn't notice the shifting into gear problem, but everything else is what I had. Mine was the switch on the brake pedal. Solved everything. I can see that being the problem with the shifting out of park issue as well. Hope this helps.

Sent from my SM-G930T using Tapatalk

MaverickZ71 Senior Enthusiast

MaverickZ71

Posted
Posted

I had to replace the brake light switch on our '09 Silverado because the cruise control quit working.  Crazy thing is, the brake lights still worked and it shifted in and out of park perfectly.  

 

I've also seen the Stabilitrak/ABS lights and chime accompany bad throttle body codes, AFM misfire codes, low brake fluid codes, etc.

 

The problem is, it seems like the cheaper code readers will read most of the powertrain error codes, but when you get into some deeper electrical issues or body control module codes, etc, you have to have an expensive GM scantool to read those.    

newdude Senior Enthusiast

newdude

Posted
Posted

I'd have the codes read to really see what is going on, but cruise not working and not coming out of park could be caused by the brake pedal position sensor.  The sensor is related to cruise control as that is one of a couple options that cancels the cruise control.  As for the coming out of park, that sensor is used by the Body Control Module and Engine Control Module to see if the pedal has been applied or not in order for the BCM to then power the shift interlock solenoid and let you shift out of park.  

newdude Senior Enthusiast

newdude

Posted
Posted (edited)
42 minutes ago, MaverickZ71 said:

I had to replace the brake light switch on our '09 Silverado because the cruise control quit working.  Crazy thing is, the brake lights still worked and it shifted in and out of park perfectly.  

 

I've also seen the Stabilitrak/ABS lights and chime accompany bad throttle body codes, AFM misfire codes, low brake fluid codes, etc.

 

The problem is, it seems like the cheaper code readers will read most of the powertrain error codes, but when you get into some deeper electrical issues or body control module codes, etc, you have to have an expensive GM scantool to read those.    

 

Blue Driver.  https://www.bluedriver.com/products/bluedriver-scan-tool

 

They have what they call "enhanced diagnostics" that can read ALL the OBDII codes in ALL the modules it can find for many brands, including GM.  I have two of these and they will read all modules, from ECM and TCM to BCM and HMI and more.   

Edited by newdude
  • Thanks 1

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...