Jump to content

Recommended Posts

Posted

I had a horrible dealer experience dealing with this issue. If any of you are under warranty you need to demand the dealership replace the HMI at the very least. A new head unit demand next if even a single issue arises after HMI. This an incredibly common problem amongst GM owners across all platforms. The dealers know the problem and they know the fix, they just put you off as long as possible because I’m guessing the parts are expensive even for the them.
The problem will not fix itself, it will not just stop happening. Have you ever heard of a electronic device that has issues and just makes itself better. They can do the updates, they can reprogram but it’s a equipment issue. The equipment is faulty and will not self-correct. Pulling the fuse, disconnecting the battery, etc will be temporary fixes, not long term.

if you are out of warranty you can try buying a HMI interface off EBay or elsewhere on the web. If you can’t get it preprogrammed you will need to take it in and have dealership or other service place do it. Probably gonna cost $150 for just the programming at dealership, stereo shop may be able to do it cheaper. Unfortunately if this doesn’t fix the issue you need a new head unit. I would absolutely not buy a used one, chances of it develop it he same issue is very high. New ones are like $800.

Your final option is to go through a company like Cruthcfield. I love that place. I priced out a new head unit, face-plate, all wires and harnesses to use the trucks existing controls, steering wheel, menu’s, etc. I think the total was like $850.

Don’t back down if your under warranty. Do some cursory searches and you will find a ton of vehicles with this problem. Print out 3-4 and take em with you.

Hope this helps.

  • 3 weeks later...
Posted

2017 Silverado 1500 LTZ - problem started about 1 month ago - blank screen - seems to be related to cold - when starting truck first thing in morning when below 30 degrees - screen comes back when passenger compartment warms up. Out of warranty period so I havent taken it back yet

  • 1 month later...
Posted

It has a very simple fix. Just as anything else some computers freeze and need to be rebooted. To easily fix this problem disconnect your battery completely from your vehicle for at least 30 mins. Once you have done this you can then reconnect the battery thus resetting your vehicles Ecu (computer). This is safe, cheap, effective with little side effects other than having to change the time and date back to your standard time zone.

Posted

It has a very simple fix. Just as anything else some computers freeze and need to be rebooted. To easily fix this problem disconnect your battery completely from your vehicle for at least 30 mins. Once you have done this you can then reconnect the battery thus resetting your vehicles Ecu (computer). This is safe, cheap, effective with little side effects other than having to change the time and date back to your standard time zone.

  • 7 months later...
Posted

My truck has been doing this for almost a year. Dealer could get no code and when I shutoff the truck it would work again, for awhile. I drive it to the dealer the next time it did it and they saw it and still no code. Many months later they have replace the navigation module and antenna. It did it on the way home. Still waiting for fix. 

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

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