Jump to content

Questions about my 6.2l Denali


Recommended Posts

Posted

Bought the truck in January and have had it in storage (beyond my control but planned for) until now. I've only put about 800km on her in the 4-5 days i've owned it but a few, probably simple questions have come up.

 

1. Has there been any updates to the intellilink or any other settings since January that have been released? Wondering if I should take it into the dealer to update firmware or settings before I set out on a planned road trip.

 

2. Has anyone had any troubles with their iphone disconnecting from the intellilink randomly then reconnecting when paired with bluetooth? It seems to happen to me at random, it will disconnect then reconnect itself after about 5 seconds. Not ground breaking because I usually also have it plugged in by USB but still annoying.

 

3. Yesterday my steering wheel audio controls wouldn't work but the dash buttons and touch screen would. The driver info center said audio off and anything I tried couldn't change it. Nothing on the steering wheel would would audio wise. XM was on and I could work it no problem from the dash and the only way to fix it was turning the truck off and on again. Hasn't happened again so i'm wondering if I hit a magic combo of buttons to make it happen?

 

4. The window epoxy repair in cold temps, does it work? I live in Northern Canada and have a rock chip in the windshield after only owning it for about 43 minutes (lousy Alberta truckers jk), its not big at all, in fact i'm surprised I even noticed it so I was thinking of the epoxy repair but I've never had it done and with temps as low as -50 i'm wondering if it can hold up?

Posted

yes there is an update out for the HMI module to address Bluetooth issues with the phones and the infotainment screen locking up at times. Takes about 3 hours or so to update the module.

Posted

Hi mojo85,

 

I see that you are turning to the forum for feedback on a few questions related to the operation of your Sierra. I just wanted to let you know, that should you feel you need additional assistance with any of these questions you can always reach out to GM of Canada by phone at 800-263-3777 or by visiting http://www.gm.ca/gm/english/corporate/about/contactus/overview.

 

Have a great night,

 

Austin J.

GM Customer Care

Archived

This topic is now archived and is closed to further replies.

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