Jump to content

2014 Seirra Denali Poor Night Driving Lighting


Recommended Posts

Posted

I'm certain there must be some in agreement with me. What kind of line are GM/dealers feeding it's customers? Headlights are so poor we drive my wife's Honda at night. Plus it keeps the mileage down on the Seirra. I'm about to start some crap over the crap they gave us for headlights.

  • Replies 90
  • Created
  • Last Reply
Posted

There's at least 1 post about this on the 2500 forum.

 

Gringo

Posted

I just drove my Sierra for the first time in the dark tonight.

I agree, piss poor, and high beams don't help much either!

sam :-)

Posted

Projectors are a joke in these trucks. :/ My wife's 2012 Acadia is better

Posted

Jesh, I have yet to see what the issue is with the lights. The ones in my 2014 AT are not that bad, once I leveled the truck I took some time to get them adjusted correctly. My main issue with them is only in regards to the color of the bulb, not really the output.

Posted

Yes, the lights suck.....You can do some things to help..

 

1. Turn down that bright ass screen in the center stack at night. It does help.

 

2. Do the high beam with fog light hack - will definitely help when you can use hi beams. http://www.gm-trucks.com/forums/topic/162734-foglights-on-with-high-beams/

 

3. Switch over the HID. Or if you dont want to do that HID stuff.. try switching to 9011 bulbs like I did. That helped.

Posted

DSC_7808Large_zpsa6d306d6.jpg

 

[/url]

 

DSC_7813Large_zps36a8a222.jpg

 

That's why bulb changes, aftermarket lights and HID conversions are the number 1 modification on this forum for the 2014 SLT and Denali.

Posted

DSC_7808Large_zpsa6d306d6.jpg

 

[/url]

 

DSC_7813Large_zps36a8a222.jpg

 

That's why bulb changes, aftermarket lights and HID conversions are the number 1 modification on this forum for the 2014 SLT and Denali.

wow!

Posted

That's about 15,000 lumens, 4300 in wide flat beams, 4300 in tight spots, and about 7000 in the headlights converted to HID. I think it's plenty for my needs on long trips across the country on the backroads.

Posted

Hi GTD,

 

We always appreciate both the positive and constructive feedback, and can assure you that we do take this feedback quite seriously. With your permission, I'd like to feed it back to our engineers and design team, but prior to doing that, we'd appreciate any additional info you'd be willing to share. If you're comfortable, please private message us with your VIN, your name, and any additional thoughts related to your Sierra. Down the road, it may be helpful for us to set you up with a truck engineer to share your feedback and suggestions. Again, thank you for taking the time to share some additional thoughts with us.

 

Sincerely,

 

Jennifer T.

GM Customer Care

Posted

Jennifer,

As I'm sure you have noticed, there is a lot of discontent about headlights on the 2014 SLT and Denali Sierra on these forums and other forums.

Posted

Love my truck but too scarred too drive at night. Waiting for hids too get the problems worked out then the stock bulbs are history.

Archived

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

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