Jump to content

Help! 07 Tahoe Message Center Went Blank

cweese
 Share

Recommended Posts

cweese Enthusiast

cweese

Posted
Posted

Please help. Started up the tahoe and everything was working fine. A few seconds passed by and then the message center went totally blank and the gear selector on the instrument panel (P, R, N, D, 3, 2, 1) is so dim that we can hardly see it. Everything else works normal in the instrument panel (spedo, pressure gauges, etc). The manual dimmer switch for the entire instrument panel is set as high as it will go before turning on the dome light. Any ideas are greatly appreciated!

Doug_Scott Senior Enthusiast

Doug_Scott

Posted
Posted
Please help. Started up the tahoe and everything was working fine. A few seconds passed by and then the message center went totally blank and the gear selector on the instrument panel (P, R, N, D, 3, 2, 1) is so dim that we can hardly see it. Everything else works normal in the instrument panel (spedo, pressure gauges, etc). The manual dimmer switch for the entire instrument panel is set as high as it will go before turning on the dome light. Any ideas are greatly appreciated!

 

Probably a stupid idea, but you sure the headlights aren't on? Have you looked that dash after it gets dark outside? With the sun out and headlights on, backlit things go very dim, analog gauges will still look the same, but digital outputs will be very dim with the sun out.

cweese Enthusiast

cweese

Posted
  • Author
Posted

Thanks for the suggestion, Doug. Yes i have tried it with the headlights on & off and nothing changes. The message center is still blank. I have had the drls disabled since ive owned it and we drive it both day and night. Everything else works just like it should. I really hope I can figure this out because I don't want to have to take it to the stealership. I just wonder if a connection somehow can loose somewhere but I don't have a clue of where to start looking. Any more ideas?

cweese Enthusiast

cweese

Posted
  • Author
Posted

I have checked all the fuses and everything is good. I'm totally baffeled at what's wrong here. Anymore ideas, anybody?

ujtruck Enthusiast

ujtruck

Posted
Posted

if you don't have all those fancy tools and service manual, then its time to visit your local dealer or someone who understand "- +"

 

if you have a good code scanner - hook it now and scan, see if you have:

DTC B3567

B3567 01: Driver Information Center (DIC) Select Switch Circuit Short To Battery

B3567 59: Driver Information Center (DIC) Select Switch Circuit/Component Protection Time-Out

 

 

Circuit/System Description

The driver information switches are normally open momentary switches. Power is provided to the

driver information center (DIC) switches via the instrument panel cluster (IPC). The IPC

interfaces with the DIC switches via 3 discreet circuits. The switch input to the cluster is pulled

low or grounded when a switch is activated. The IPC reads the voltage at the analog input to

determine which switches is pressed. The switch input to the cluster is set up in a resistor ladder

format for three of the four switches. The DIC switches include the PERSONALIZATION,

SET/RESET, TRIP/FUEL, AND VEHICLE INFO switches. A stuck switch or a short to battery

sets a DTC.

 

if you do have DTC B3567

 

 

1. Ignition OFF, disconnect the harness connector at the DIC switch assembly.

2. Ignition OFF, test for less than 1 ohm between the low reference terminal 2 and ground.

If greater than the specified range, test the low reference circuit for an open/high

resistance.

3. Ignition OFF, test for less than 1 ohm between the ground terminal 5 and ground.

If greater than the specified range, test the ground circuit for an open/high resistance.

4. Ignition ON, verify that all of the scan tool DIC Switch parameters are Inactive.

If any are not Inactive, test the appropriate signal circuit terminal 1 or terminal 3 for a

short to ground. If the circuit tests normal, replace the IPC.

5. Ignition ON, install a 3-amp fused jumper wire between the signal circuit terminal 1 and the

low reference circuit terminal 2. Verify the scan tool DIC Switch parameters, except the

DIC Fuel Info. parameter, are Active.

 

If any are not Active, test the signal circuit for a short to voltage or an open/high

resistance. If the circuit tests normal, replace the IPC.

6. Ignition ON, install a 3-amp fused jumper wire between the signal circuit terminal 3 and

ground. Verify the scan tool DIC Fuel Info. parameter is Active.

If not Active, test the signal circuit for a short to voltage or and open/high resistance. If

the circuit tests normal, replace the IPC.

7. If all the circuits test normal, test or replace the DIC switch assembly.

 

my .02 cent worth :)

  • 1 year later...
Gmcguy228 New Member

Gmcguy228

Posted
Posted

I had the same problem with mine, I took it to my mechanic and he referred me to a guy that did instrument cluster repairs. He got it fixed and gave me a warranty with it. It cost $125 but I didn't have to get taped at the dealer for a new instrument cluster. I'll post the link to his website... http://clustersurgeon.com/ hope that helps

  • 2 months later...
markemark513 Enthusiast

markemark513

Posted
Posted

im trying to build the DIC myself because the cheapest i could find was $90 on ebay. i found the diagram and all i need is 4 push buttons and three resistors. but in the diagram it wont tell me the value of the resisters. i have the pdf that i am attaching the link with here http://arrc.ebscohost.com/statics/p5/pdfs/vf_wiring/va277702.pdf#toolbar=1&navpanes=0&scrollbar=1

 

is anybody willing to open theirs up and take a look or even check the resistance from pin 1 and 3 from when each button is pressed besides the fuel/trip button?

  • 5 years later...
  • 1 year later...
Tujuan New Member

Tujuan

Posted
Posted

I have same exact problem. Can anyone post their final success story details? Seems like a very specific problem fix since the drive gear position indicator is dimmed to barely visible with all else blanked.

swathdiver Senior Enthusiast

swathdiver

Posted
Posted
2 hours ago, Tujuan said:

I have same exact problem. Can anyone post their final success story details? Seems like a very specific problem fix since the drive gear position indicator is dimmed to barely visible with all else blanked.

Get with this guy:

 

  • 5 years later...
dpasek New Member

dpasek

Posted
Posted

This problem is caused by a bad LL2705 mosfet in the instrument cluster. It is a 75 cent part and it's located near the lower right corner of the DIC vacuum fluorescent display module. The cluster needs to be disassembled to accomplish the remove/replace/resolder repair.

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, 1,858 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...