Jump to content

2015 Silverado 2500HD LCD Center Console Display "Dimming"

Trailbreaker77
 Share

Recommended Posts

Hillbilly10 Enthusiast

Hillbilly10

Posted
Posted

It's getting to be a real issue, I use a fleet fuel card, and I have to enter the mileage, with the display so dim, the odometer is unreadable. Don't know why they changed it for the 2016 model. Never had an issue with it on the 2015, and it appears they are not going to fix it saying it's operating as designed!

SouthernSilveradoGuy85 Senior Enthusiast

SouthernSilveradoGuy85

Posted
Posted (edited)

On my '14 the DIC in the gauge cluster and the dash screen in the middle will dim whenever the lights are turned on. Not the DRLs, but when ti goes from DRLs to regular headlights for when it gets dark or if you have the windshield wipers on long enough. Never had a problem reading mine in the day or night since day 1.

Edited by SouthernSilveradoGuy85
Hillbilly10 Enthusiast

Hillbilly10

Posted
Posted

On my '14 the DIC in the gauge cluster and the dash screen in the middle will dim whenever the lights are turned on. Not the DRLs, but when ti goes from DRLs to regular headlights for when it gets dark or if you have the windshield wipers on long enough. Never had a problem reading mine in the day or night since day 1.

 

Apparently it's something new GM is doing, never had this problem with my previous two trucks. My 2016 is exactly the same model and options as my 2015, but only the 2016 is doing it. We have around a hundred and twenty five 2015 models, and don't have this issue with any of them, so I don't know why GM thought it was a problem and changed it into a problem for 2016.

GS340 Enthusiast

GS340

Posted
Posted

I'm going to ask about it when I take it in for the first oil change. It's so bad in the afternoon you cant read the screen

Hillbilly10 Enthusiast

Hillbilly10

Posted
Posted

I'm going to ask about it when I take it in for the first oil change. It's so bad in the afternoon you cant read the screen

Mine is that way too, and it's a real problem because the odometer is part of that display, and I have to enter the mileage for my corporate fuel card on almost a daily basis. If I don't do it in the morning, I have to guess, and that upsets the bean counters if I'm off a lot.

  • 2 months later...
GS340 Enthusiast

GS340

Posted
Posted (edited)

I wanted to let you know the dealer contacted the GM tech line and they sent an update for the cluster. After applying the update the dash is much brighter, doesn't appear to fade out, and is noticeably adjusting as the sun sets. As you drive in areas with lots of trees... Hard to explain but as the trees cast a shadow on the dash sensor you can see the dash dim or brighten. I was sitting in traffic, inching forward, in and out of tree shadows watching it work. Which it never did before. It was always one setting and depending on the amount of sunlight it could wash out the dash.

 

I have the update ID number on the invoice/work order and will post it later

 

You should be happy after the update is applied.

Edited by GS340
GS340 Enthusiast

GS340

Posted
Posted (edited)

Same here mine did it about a year ago and I did the same thing with the dimer wheel, never done it since.

The issue I was experiencing was not related to the dimmer wheel/adjuster. With the head lights off that adjuster doesn't do anything with regards to adjusting the dash brightness. The problem I was having is in the afternoon getting into the truck the dash LCD would be readable. While driving the dash would slowly dim out to the point you couldn't read anything. Slllloooooooooowwwwwlllllyyyyy fade out over 30 to 45 minutes. The adjuster wheel has nothing to do with it. Turning the headlights on and using the wheel would change the brightness on everything BUT the center LCD. If I turn off the truck and let it sit for while. It would be readable on the next startup and slowly fade again only in the afternoon sunlight. Never at night or early morning. There must have been and issue in the software and the single from the sensor on the dash. It appears the update fixed the issue.

Edited by GS340
  • 4 years later...
Richard allen New Member

Richard allen

Posted
Posted

I have a 2015 2500 HD and my DIC lights go out all the time in cold weather or warm weather it has 125000. Miles on it the rotator dial has no effect and I use my dimmer switch low and bright no effect what can I do I depend on the DIC for information 

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

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

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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