Jump to content

Please help, 04 GMC Sierra 1500

Tyler Porter
 Share

Recommended Posts

Tyler Porter New Member

Tyler Porter

Posted
Posted

Hello Everyone,

 

I'm helping a friend with his truck, 2004 GMC Sierra 1500 SLE 5.3L. Removed and replaced forgive me if the name is incorrect the I/P Harness that runs from the Fuse Block under the hood ,through the firewall, and  runs along the dash. Got it out with a struggle, install went smooth until the reason I'm asking for help. I have a connector that I can not figure out where it belongs???  It's a grey with  8 cavities with 1 Black with White stripe (Ground), 1 Brown, and 2 Brown with White Stripe wires. It exits the harness where the headlight dimming switch connector does. If anyone can help me or if you need more information please let me know. Thank you in advance for your time.

20210427_192508.jpg

20210427_182808.jpg

Sharpz Enthusiast

Sharpz

Posted
Posted

So I did look to see if I could locate that harness connection and just cant seem to find it on my 04 gmc sierra. I do know, that black w/ white tracer can be linked to the multifunction switch, brakes, Hvac, and RAF.  I am assuming you removed the old harness because the truck caught fire, or had serious damage.  How sure are you that you got the exact same harness from a sierra 04?  I can give you a link to every wiring diagram for your truck, but there is a lot of information, and it will take time to work through.  There is a limited amount of spots this connection can go, have you put juice to the truck yet to see if it would crank/code?  

  • 1 month later...
Coupe4888 New Member

Coupe4888

Posted
Posted
On 4/28/2021 at 12:43 AM, Tyler Porter said:

Hello Everyone,

 

I'm helping a friend with his truck, 2004 GMC Sierra 1500 SLE 5.3L. Removed and replaced forgive me if the name is incorrect the I/P Harness that runs from the Fuse Block under the hood ,through the firewall, and  runs along the dash. Got it out with a struggle, install went smooth until the reason I'm asking for help. I have a connector that I can not figure out where it belongs???  It's a grey with  8 cavities with 1 Black with White stripe (Ground), 1 Brown, and 2 Brown with White Stripe wires. It exits the harness where the headlight dimming switch connector does. If anyone can help me or if you need more information please let me know. Thank you in advance for your time.

20210427_192508.jpg

20210427_182808.jpg

Does it go to a rear cargo lamp button I have an 04 chevy and there is a plug with the headlight switch that goes to a push button right next to the head light switch that runs the cargo lamp and I do rember the plug looked the same as that one I would have to pop the button back out to see If the colors are the same but If I rember correctly they are

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

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