Jump to content

2003 Silverado 2500 HD All kinds of the electical issues

billd76

Recommended Posts

billd76 Enthusiast

billd76

Posted
Posted

HI all,

Truck has 105k miles. stock radio with keyless entry FOB. Instrument cluster is going bonkers, had cluster rebuilt by guy in Kentucky. Got it back from rebuild, and having the same issues: This is the list of what it's doing:

Gauges work sometimes and sometimes not

Tach and speedo seem to always work.

When gauges drop out, radio shuts off

When gauges go out, drivers door lock and window not work.

HIgh beam indicator light will not illuminate

2 and 4 wheel driver selector panel sometimes shows neutral or not lights at all. sometimes read correctly. When it reads correctly, service 4 wheel drive meassage appears.

occasionally it will take 4 attempts to start, it will start then die immediately

The Theft light sometimes illuminates

The ABS light sometimes will come on while driving

The parking brake lamp will come on while driving

 

Things I have done:

I have cleaned all ground points I can get to. (two near front bumper on drivers side and two below cab mount on drivers side. How do you get the ground points between the engine block and fire wall? lower the trans?

checked battery voltage.

I have pull both kicker panels off and checked wires

I pulled the under hood fuse panel off and inspected connectors and wires

I checked connectors and wiring on the inside fuse panel

I pulled the lower dash panel off and inspected BCM wiring

I pulled the protective cover off the ECM and inspected wires and connectors.

 

I have attempted to scan for codes from two different tech 2s. keep getting data link error.

I have not checked the two ground point up under the top section of the dash, as I can't figure out how to get the top right side of the dash off.

Everyone I've talked to says it sounds like a ground issue. I am at a total lose!!! all fuses appear to be good!! HELP!!!!!!

billd76 Enthusiast

billd76

Posted
  • Author
Posted

A friend has a 06. I took his cluster and put in my truck, didn't work. I put my cluster in his and it worked. back to checking grounds!!!

billd76 Enthusiast

billd76

Posted
  • Author
Posted

got home last night and spliced into the small black and white ground wire that is between the engine block and firewall, soldered a wire at the splice and ran it over to the large ground wire connection point on the fire wall. All gauges are now working, but still have a theft light. theft light. When the theft light comes on, the gauges drop out for a split second then come right back, theft light stays one. Guess I need to check more grounds. At least now I think I could get a code, if there is any, with a tech 2.

billd76 Enthusiast

billd76

Posted
  • Author
Posted

Yeah close. I added some dielectric grease to the connector near the ignition switch. I think it actually made it worse, I have some contact cleaner that I got at guitar center called get the funk out. Going to remove the dielectric grease with it tonight. It's purple nyogel dielectric grease, not supposed to cross talk between pins, but it might be.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • 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.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...