Jump to content

Loss of interior audio in cold weather

Mathew Kirsch

By Mathew Kirsch
in Troubleshooting & Recalls

 Share

Recommended Posts

Mathew Kirsch Enthusiast

Mathew Kirsch

Posted
Posted

2015 Silverado 1500, 120,000 miles.

 

When the temperature gets below 25F, and the headlights are on, and the heater fan is on, and the radio is on, when I pulse the windshield wipers, I lose all interior audio.

 

No radio. No blinkers. No warning chimes. Nothing.

 

Turning the radio off and on, even REALLY turning it off and on, does nothing. The only way to get audio back is to park the truck, shut it off, get out, walk away for 10 minutes, and come back. After that everything is fine again until the next time it happens.

 

It has done this since the truck was new.

 

Dealers want nothing to do with it. Couldn't reproduce it, no fault found. Talked to a service manager here recently about it. He put his hands in his pockets, looked at the ground, poked at an imaginary rock with his toe, and said, "Welll uh, I've never heard of such a thing, and uh, it sounds electrical, wiring... You could spend thousands hunting down a wiring problem like that..."

Don Spedaliere New Member

Don Spedaliere

Posted
Posted

I have a 2015 Sierra and just recently I’ve had a similar experience. I get in the truck and put the key in and no bells. Start the truck no radio, no blinker noise. Saw another thread that mentioned a low battery voltage issue. Can’t figure it, shut the truck off for ten minutes and everything comes back.

JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
9 hours ago, Don Spedaliere said:

I have a 2015 Sierra and just recently I’ve had a similar experience. I get in the truck and put the key in and no bells. Start the truck no radio, no blinker noise. Saw another thread that mentioned a low battery voltage issue. Can’t figure it, shut the truck off for ten minutes and everything comes back.

Welcome to the site.

 

If you still have the original battery. replace it, they do not last very long with the draw that is put on them by the truck.

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