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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   6 Members, 1 Anonymous, 1,658 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...