Jump to content

HMI or radio issue?

Dustin10
 Share

Recommended Posts

Dustin10 New Member

Dustin10

Posted
Posted

I have a 2018 GMC Sierra. My radio would not work when the temperature was really cold (negative temperatures) but as the truck would warm up the radio would start working again. As time went on warmer temperatures like 10, 15 and even 30 degrees would start to impact the radio. Same issue it wouldn’t work for 10-20 minutes until the truck was warmed up. Eventually the radio stopped working all together. When it quit working all together my front bumper sensors stopped working and so did the speed limit display in my dash. The back up camera worked and displayed on the screen the whole time. I brought it to the dealership today and they reset the radio with their computer but said I will eventually need a new radio. If it’s just the radio why would it impact the front bumper sensors and the speed limit display? They said one system going down can cause others to go down too.  Anything else it could be and could the dealership be wrong thinking it’s just the radio? When I research online I’m seeing the HMI could be a more likely culprit. Both are expensive so I’d rather have more information before buying parts. 
 

new battery, replaced the main ground from the battery and to the frame. 

davester Senior Enthusiast

davester

Posted
Posted

it depends on what's wrong. 

 

bad/failing solder joins can make or break connections based on changing temps, and if this happens on the computer data bus the truck uses, that can impact the ability for other computers to communicate.  But, it could also just be a coincidence that the front sensors are having problems around when the radio is.

  • Like 1
Dustin10 New Member

Dustin10

Posted
  • Author
Posted
1 hour ago, davester said:

it depends on what's wrong. 

 

bad/failing solder joins can make or break connections based on changing temps, and if this happens on the computer data bus the truck uses, that can impact the ability for other computers to communicate.  But, it could also just be a coincidence that the front sensors are having problems around when the radio is.

When they reset the radio module the front sensors started working again.. my friend works for the dealer and with their discount the radio is still $500+ without labor. I’d hate to pay for that then find out it is the HMI or something else. To me it just doesn’t seem like it’s a radio unit alone causing this. 

MikeBMW Senior Enthusiast

MikeBMW

Posted
Posted

For what it's worth, Ive never experienced a bad HMI module.
I've installed many of these as I upgraded to a navigation HMI.
I still have two sitting on the shelf but they would have to programmed to your VIN which is what WAMS does.
If you find that to be the issue, I can send you one but, again, @GTPprix would need to program it.
 

  • Like 1
newdude Senior Enthusiast

newdude

Posted
Posted
11 hours ago, Dustin10 said:

I have a 2018 GMC Sierra. My radio would not work when the temperature was really cold (negative temperatures) but as the truck would warm up the radio would start working again. As time went on warmer temperatures like 10, 15 and even 30 degrees would start to impact the radio. Same issue it wouldn’t work for 10-20 minutes until the truck was warmed up. Eventually the radio stopped working all together. When it quit working all together my front bumper sensors stopped working and so did the speed limit display in my dash. The back up camera worked and displayed on the screen the whole time. I brought it to the dealership today and they reset the radio with their computer but said I will eventually need a new radio. If it’s just the radio why would it impact the front bumper sensors and the speed limit display? They said one system going down can cause others to go down too.  Anything else it could be and could the dealership be wrong thinking it’s just the radio? When I research online I’m seeing the HMI could be a more likely culprit. Both are expensive so I’d rather have more information before buying parts. 
 

new battery, replaced the main ground from the battery and to the frame. 

 

 

Speed limit works off the navigation system.  Which is...in the radio.  

 

Park assist.  The alert tones are handled via the radio.  The tone not working won't disable the system though.  The only things that will disable the park sensors is things related to those like a bad sensor or multiple sensors, wiring, bad module, etc.  

 

Sounds to me like the radio is the issue. 

 

A failed or failing HMI most commonly would have the radio changing screen pages on its own, radio source switching on its own, etc.  You'd have a working screen but it will have a mind of its own.  But everything would work still as far as the radio and what it does.  

  • Like 2
carkhz316 Enthusiast

carkhz316

Posted
Posted (edited)

The HMI also handles switching of the rear camera input/ output, so the fact that the backup camera works on demand generally rules out the HMI as well. If the HMI fails, you'll still have sound coming from the radio, but the infotainment will be blank or unresponsive. Typically, stations and volume can be controlled from the instrument cluster if that happens.

 

The radio, amp, HMI, CD player, and instrument cluster are on their own dedicated communication bus known as the Media Oriented Systems Transport, or MOST bus. It is fairly easy to diagnose with the proper tooling. GDS2 and some aftermarket scan tools will outline which 'node' or module (of the aforementioned components) are not working properly and help to isolate the defective module or circuit portion. The dealer should have been able to find this out without too much effort.

Edited by carkhz316
  • Like 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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...