Jump to content

Recommended Posts

Posted

Just bought my first Denali 😀 it is a 2021 Sierra Denali with safety package 1 and 2 . At first I thought it had came with heads up display , because I had seen the components For the heads up display on the dashboard . After searching though the DIC I could not find a option for HUD.
Can anyone confirm that my truck didn’t come with HUD? I am wondering why I have all the components for HUD on the dash but I can’t find anyway to turn it on. 
thank you !! BTW first post !! 😁

Posted (edited)

The switch on the dash left of steering wheel, 3 control buttons, not thru the DIC. 

 

Note, it can be adjusted for brightness and position so you may need to adjust it to your line of sight etc...It could be dimmed (like dash lights) to off so you can't see it.............lift up on the dimer switch (right) until you can see it.

DSC01174.JPG

Edited by elcamino
Posted
2 hours ago, elcamino said:

The switch on the dash left of steering wheel, 3 control buttons, not thru the DIC. 

 

Note, it can be adjusted for brightness and position so you may need to adjust it to your line of sight etc...It could be dimmed (like dash lights) to off so you can't see it.............lift up on the dimer switch (right) until you can see it.

DSC01174.JPG


damn ! I guess my truck didn’t come with HUD! Do you know What parts do I need to add it  on to my truck ??

 

Posted

It's in the tech package.  Do you have the 360 camera?  Rearview mirror camera?  If not, no HUD.

Posted
2 hours ago, elcamino said:

The switch on the dash left of steering wheel, 3 control buttons, not thru the DIC. 

 

Note, it can be adjusted for brightness and position so you may need to adjust it to your line of sight etc...It could be dimmed (like dash lights) to off so you can't see it.............lift up on the dimer switch (right) until you can see it.

DSC01174.JPG


damn ! I guess my truck didn’t come with HUD! Do you know What parts do I need to add it  on to my truck ??

 

Posted

If you don't have the 360 camera, all you will get is the red dots for collision avoidance.  

Posted (edited)

Looks like you need rpo PDJ Driver Alert Pkg II and rpo CWM Technology Package which includes (UVS) HD Surround Vision, (DRZ) Rear Camera Mirror, (UVN) Bed View Camera and (UV6) Multicolor 15" Diagonal Head-Up Display. Available on SLT, AT4 and Denali.

 

Cannot be added, its part of a bigger puzzle which your truck does not appear to have.

 

Edited by elcamino
  • Like 1
Posted
7 hours ago, elcamino said:

Looks like you need rpo PDJ Driver Alert Pkg II and rpo CWM Technology Package which includes (UVS) HD Surround Vision, (DRZ) Rear Camera Mirror, (UVN) Bed View Camera and (UV6) Multicolor 15" Diagonal Head-Up Display. Available on SLT, AT4 and Denali.

 

Cannot be added, its part of a bigger puzzle which your truck does not appear to have.

 

I have the driver alert package 2 still can’t add on ? 

Posted
2 hours ago, Steeldenali said:

I have the driver alert package 2 still can’t add on ? 

 

Nope.  On the other hand if you have a boat load of cash it can be done with a whole lot of work!

There is a member on here that has done it and listed parts & prices for all the additional hardware.

Do a search on here and check it out.  (If I come across it I'll post it for you.)

  • Thanks 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
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...