Jump to content

07 Nbs Guage Cluster Hard To See


suprdav2

Recommended Posts

Posted

I've got a 2007 NBS Silverado W/T, and in the mid-afternoon, if the Texas sun is out in full force, it's really hard to see the guages.....especially if I have sunglasses on. A relative of mine has an 08 Silverado LS, and his guage cluster lights up automatically when you start the truck. Was this something new for 08, and if so........can this be retrofitted to my 07?

 

TIA,

 

Dave

Posted

Yes,It was new for '08 that the cluster was backlit.

There is a solution for you,BUT if your out of warranty it will cost you.....

 

 

#07-08-49-029A: Instrument Panel (IP) Gauges/Gages Difficult to Read or See, Poor Backlighting (Replace IP and Program) - (Jan 25, 2008)

 

 

Subject: Instrument Panel (IP) Gauges>/Gauges Difficult to Read or See, Poor Backlighting (Replace IP and Program)

 

 

Models: 2007 Chevrolet Avalanche, Silverado, Suburban, Tahoe

 

2007 GMC Sierra, Sierra Denali, Yukon, Yukon Denali, Yukon XL, Yukon Denali XL

 

Condition:

Some customers may comment that the instrument panel (IP) gauges are difficult to read due to poor backlighting. This condition does not affect the IP cluster operation.

 

Correction:

Important:

 

• DO NOT program the service software into existing 2007 clusters. The service software is designed to work only with the 2008 cluster hardware, which includes a new microprocessor.

 

• For IP clusters replaced/programmed due to a customer concern of poor backlighting, warranty claims must be submitted using the labor operation listed in this bulletin. Refer to the Warranty Section for more information.

 

• Program the replacement IPC using TIS2WEB Pass-Thru Programming. Select "I/PC" from the Supported Controllers table in TIS2WEB to complete the programming. DO NOT select I/PC Set-up. Mileage and/or Engine Hours must be set by the ESC's prior to installing the IP in the vehicle.

 

• DENALI CUSTOMER'S ONLY - Please advise the customer that 2008 Denali clusters are not available. In order to correct this condition, a 2008 Yukon or Sierra cluster will have to be installed in the vehicle. The customer must advise the dealer whether they wish to keep the current 2007 Denali cluster or replace it with a 2008 Yukon or Sierra cluster (which will correct the condition).

 

 

Notice: Programming a 2007 cluster with the 2008 service software can drain the battery and potentially cause a "no start" condition.

 

If the customer is dissatisfied with the IP cluster visibility, the current (2007) cluster should be replaced with the 2008 hardware/software. Refer to the charts listed in the Parts Information section of this bulletin to determine the new IP cluster and software part numbers.

Posted
Does this apply to both dashes?

 

Should,Your dealer can check by looking at the service part number on your current cluster and seeing if theres a replacement cluster listed.

Posted

Ok so it says that you may have to swap in the 08 hardware...does this include swapping the 6 gauge in place of the 4 gauge...I've heard both answers of yes and no whether or not this will work

Posted

No luck here. I've called 3 dealers nearby, and keep getting a run around by all of them, really sounding like they don't even want to touch it if it's going to be under warranty.

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