Jump to content

Recommended Posts

Posted

Just Got my 2021 Silverado LT 2wd had it about a week when my wife and i took a trip a few hours away , 2 hours into it i heard a faint high pitch whine (2 seconds ) then radio went blank still heard music playing but had no control even the HVAC started blowing heat until i turned off auto and set manual temp i say it went blank but could tell there was some slight back light ,,, i pulled over shut the vehicle off and exited the truck for a few minutes the music still played and had 0 control over any selection Vol, station etc , i continued on my trip not going to let that ruin our get away figured i keep a jump box with me anyway ,, got to the hotel unloaded truck the about an hour later i went out and it had shut off the next morning was like it never happened and it hasnt happened since but i also havent driven longer than an hour or so since then either i checked for OTA updates says none a few days later i saw theres an update for the radio made an appt at the dealer i worked at for 20+ years as a shop foreman over 35yrs master tech for chevy but now i work for the Govt (still a mechanic tho) theyve told me i have the latest update but ordered a center stack because its a common fault, 1 all i want is for them to update the radio before someone tears my dash apart and replace a part with a guaranteed used referb part that may not be faulty

lt

Posted

I saw PI bulletin  PIC6425b that addressed many concerns across the GM line up and saw software v152 as the latest in the bulletin so I checked mine and even tho theyve told me i have the latest i'm at V135 with a date of 10/14/2019 the problem is since i left that dealership many of the techs that knew what they were doing have also left and from what i'm told the most of the techs are from KIA brought over with a new MGR

anyway my next option is to contact some old friends at another chevy dealership and see if i can get them to update the radio BTW the back up camera worked normal when the radio quit

 

my other concern is the truck has the 8" radio with XM no Nav , my window sticker says 8" radio with XM  but when i scan the QR code for the option label it comes back as the IOR radio which i think is the non XM 7" radio 

the truck was purchased new early feb 2021 no mods , i did how ever add a dash cam last week long after the radio concern because i was waiting to get my windows tinted 

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,891 Guests (See full list)

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...