Jump to content

intermittent electric issues (Gauges and radio cut out) 2006 Silverado

Solas
 Share

Recommended Posts

Solas Enthusiast

Solas

Posted
Posted

I have a 2006 Silverado 1500 with the following problem

Intermittently - All dash gauges cut out and charging light, security warning light- light up. radio also cuts out ... I think electric door locks and windows also don't work....once I depress the brake pedal all comes back until it happens again 10 sec to several minutes later. Dash lights, headlights, tach, speedometer, heater fans stay on - engine never skips a beat...happens moving and idling...brake pedal always fixes it ... can happen 10 times per minutes or can go 5-10 minutes w/o it happening... very frustrating -any suggestions?

 

txab Senior Enthusiast

txab

Posted
Posted

Always check the battery condition. Battery cables/connections including body grounds

Solas Enthusiast

Solas

Posted
  • Author
Posted

Is the megafuse the 125 amp one that is not visable unless you remove the plastic surrounding the the fuse box under the hood? I've seen reference to a 175 amp one on the firewall in 2008...but doesn't appear to be there on the 2006?

06pirate Enthusiast

06pirate

Posted
Posted (edited)

My truck in a 2006 GMC Sierra. A couple of years ago I had a bunch of unusual and seemingly unrelated electrical problems. Check engine light illuminated dimly, cruise control worked but would not shut off with switch, only by pushing brake pedal, interior lights flickering sometimes, etc. It turned out that mice had chewed the hell out of the wiring under the main fuse panel mounted in the engine bay, left front fender. I spent an entire weekend splicing and re-insulating to fix it all. It isn't real easy to get at the wires under the fuses, you have to pull the fuse panel section off of the rest of the big plastic box, but if you don't find anything else wrong, you might look under there. I now put mothballs in plastic holders under the hood to keep the mice out.

 

Oh, and neither my OBDII scanner nor the dealer's superdooper scanner showed any fault codes.

Edited by 06pirate
Solas Enthusiast

Solas

Posted
  • Author
Posted

My truck in a 2006 GMC Sierra. A couple of years ago I had a bunch of unusual and seemingly unrelated electrical problems. Check engine light illuminated dimly, cruise control worked but would not shut off with switch, only by pushing brake pedal, interior lights flickering sometimes, etc. It turned out that mice had chewed the hell out of the wiring under the main fuse panel mounted in the engine bay, left front fender. I spent an entire weekend splicing and re-insulating to fix it all. It isn't real easy to get at the wires under the fuses, you have to pull the fuse panel section off of the rest of the big plastic box, but if you don't find anything else wrong, you might look under there. I now put mothballs in plastic holders under the hood to keep the mice out.

 

Oh, and neither my OBDII scanner nor the dealer's superdooper scanner showed any fault codes.

 

This is where I suspect the problem is (main fuse panel)...if it were in the dash circuitry - I don't think the radio would be involved and if it was the ignition switch..I don't see why some accessories but not others...the brake pedal correcting it 100% of the time has me perplexed....I will head under the fuse panel under the hood megufuse and all...it was sitting for a bit - so mice a possibility

  • 1 month later...
Solas Enthusiast

Solas

Posted
  • Author
Posted

I have a 2006 Silverado 1500 with the following problem

Intermittently - Dash gauges (voltage, oil pressure, etc) cut out and charging light, security warning light- light up. radio also cuts out ... I think electric door locks also don't work....once I depress the brake pedal all comes back until it happens again 10 sec to several minutes to hours later. Dash lights, headlights, tach, speedometer, heater fans all unaffected - engine never skips a beat...happens moving and idling...brake pedal always fixes it ... can happen a couple times per minutes or can go 5-10 minutes w/o it happening even hours... very frustrating -any suggestions? Ignition wiring? Could brake circuit be backfeeding power?

  • 6 years later...
Carl Lutz New Member

Carl Lutz

Posted
Posted

Aluminum oxide is the demon.    Aluminum stud, aluminum nut & aluminum braided cable, engine body ground. removed from firewall cleaned put back no gremlin.  If the problem is at the block (hard to get at) just run a 14 - 16 gauge copper wire from stud to block, alternator bracket has a 8 mm bolt holding a wire clip (that was first thing I did), stopped in the middle of no where after gremlin attack dash gauges door locks headlights warning lights radio clock reset.  Went to start turning key nothing at all.  Key in the on position with a coat hanger touched body ground bolt and block the key in ignition alarm started dinging.  used a lamp cord that was in the bed stripped it rigged it up and no problems rest of 30 miles home.  once home pulled ground strap from firewall cleaned with wire brush reinstalled not a flicker from headlights when brakes are applied nothing demon/gremlin completely gone.

  • 11 months later...
DeeboSC78 Enthusiast

DeeboSC78

Posted
Posted

I realize this is an old post but Solas, did you figure it out?

 

I have an 06 Z71 and its doing the exact same thing. Warning lights pop up on dash, all gauges drop to zero, radio turns off, windows/doors wont work, etc but truck still runs. If I have AC on , fan will continue blowing but compressor not sending cold air. If i turn the truck off and restart, its usually fine.

 

Fairly new Interstate battery, will check ground and connections but this is driving me crazy

  • 6 months later...
Youngblood25 New Member

Youngblood25

Posted
Posted
On 8/21/2021 at 9:14 AM, DeeboSC78 said:

I realize this is an old post but Solas, did you figure it out?

 

I have an 06 Z71 and its doing the exact same thing. Warning lights pop up on dash, all gauges drop to zero, radio turns off, windows/doors wont work, etc but truck still runs. If I have AC on , fan will continue blowing but compressor not sending cold air. If i turn the truck off and restart, its usually fine.

 

Fairly new Interstate battery, will check ground and connections but this is driving me crazy

Did you ever get this issue resolved? I cannot find out why my truck is doing this and shops are charging ridiculous amounts to go through my system.

  • 1 year later...
  • 1 year later...
LTcolorado22 New Member

LTcolorado22

Posted
Posted

I’m currently having similar issues on my 2006 Chevrolet Silverado. 
 

My doors won’t power unlock or lock , windows won’t go up and down, radio doesn’t turn on, my four gauges are not working( battery, oil, pressure, temperature, gas) and interior lighting only turns on when I manually pushed the buttons. 
 

My battery light is on so I replaced the battery because it had gone out but didn’t fix the problem. 
 

My ABS light is on. 
 

No check engine light.

 

I checked my fuses and relays and they all look good. 

 

not sure the problem. 

  • 4 weeks later...
Preat New Member

Preat

Posted
Posted

2007 Chevy Silverado having trouble with the cluster, radio and climate control coming and going plus the blower motor runs with not key in truck

  • 2 months later...

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

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