Jump to content

Recommended Posts

Posted

Hi folks.

 

Just bought a 2017 GMC Sierra SLT with 66k on it Saturday. Today I noticed (this evening when it was dark) that the A/C button light flickers... sometimes it stays on for a few seconds and sometimes dark for a few seconds, and sometimes flickering back and forth constantly. The air conditioner isn’t on, btw.

 

Just curious if this is the start of electrical issue, or is it simply a small bulb or something burning out. Everything around it is lit up and fine.

 

thanks

  • 5 months later...
  • 3 months later...
Posted
On 2/5/2020 at 4:36 AM, B1Sousa said:

Update: now the defrost button close by is doing the same thing 

Maybe this?

 

  • Symptoms of a failed headlight switch include:
  • Headlights and taillights failing to turn on or off
  • Interior lights flicker, or fail to turn on or off
  • Gauge cluster lighting off or flickering with headlights on
  • Parking light malfunctions
  • 3 weeks later...
Posted

My 2018 Sierra's AC light is also flickering at night. The AC is not on. The light becomes dim and then it stays on and then gives off. I noticed this a few weeks ago.

  • Like 1
Posted

yah - my truck is still under the 3 year 36,000 mile warranty.  I bought a new control unit for 95.00 shipped from ebay.  I don't trust the shoddy techs ripping my aluminum trim off and the center screen to get the controls out; I'd rather do it myself!  From what I've read it's pretty common, so I'm sure my new part will only do it again.  I plan on shipping my old part out to a guy I know that can solder in new replacement led lights. 

Posted

replaced control with a new GM one from ebay $100.00 shipped.  Although my truck is still under warranty, I'm sure the dealer would have broken a few of the clips that hold the aluminum bezel around the center stack.  They "love" warranty work.  That trim was a ****** to take off with out breaking/bending!  My old part was 84258726 the new part is the same with the last digit being a  9.  As I'm sure, that in two years, this will happen again, I'm sending my old part to 1mr.repairman so he can replace all the led lights with quality parts and i will swap it back in when the new GM one goes on the blink.  Kind of sucks for a $50+ truck!

Posted
1 minute ago, Miguel Olea said:

replaced control with a new GM one from ebay $100.00 shipped.  Although my truck is still under warranty, I'm sure the dealer would have broken a few of the clips that hold the aluminum bezel around the center stack.  They "love" warranty work.  That trim was a ****** to take off with out breaking/bending!  My old part was 84258726 the new part is the same with the last digit being a  9.  As I'm sure, that in two years, this will happen again, I'm sending my old part to 1mr.repairman so he can replace all the led lights with quality parts and i will swap it back in when the new GM one goes on the blink.  Kind of sucks for a $50+ truck!

Did all of the functions still work on the old HVAC control? I thought that when something went out, like a light, or a switch function, they were garbage.

Posted

everything worked - just the back lights would flicker or stay off.  Such a chintzy design.  All the lights still work on my 06 Yukon with 160,000 miles.

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

    • 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?
    • 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...