Jump to content

Where is this ground wire supposed to go?


Recommended Posts

Posted

Hi guys and gals.  Had a motor change done recently as old motor blew up due to low oil pressure (ended being a really clogged pickup tube screen ) anyhow ,

 

there is is this black wire off the harness on the drivers side.   The buddy who I got motor from got it on the firewall bolt.   I didn’t see it there before the swap.  So I’m wondering if it’s in the wrong spot.  I tried moving it and removing it and I get reduced power with it disconnected and the truck doesn’t turn off with the key.  
 

can anyone kindly help me ?

 

also I do see a ground he spliced into on the passenger rear that he also put on the firewall bolt.  
 

it is a 2004 Silverado 5.3
 

im curious about this all as the oil pressure sometimes fluctuates bad.  Can max at 550 or goto zero (no lifter tap at zero).   

EC5DFC2C-3954-4A39-91F3-B32340B8CBC1.jpeg

Posted

I would suggest getting a subscription to the full-service manual for your truck to sort out your problems.  It'll have wiring diagrams, ground locations, wire colors, harness routing, plug pinouts, and diagnostic procedures for the problems you are having.

 

alldatadiy.com, or other sites for ti, or the paper version at helminc.com/amazon/ebay.

Posted

Not sure about that wire.  My 03 Suburban doesn't have a ground shooting out of the harness right there.  It does have 2 grounds on the block behind the intake and one from the driver's side rear of the block (same bolt) up to that stud on the firewall that your buddy probably used.  Here's a picture of both grounds at the back of the engine.

20191113_110727.jpg

Posted

I think that bolts onto the drivers side pulley/alternator/ power steering pump housing. As noted in the photo below. Photo is an 08, but you may still have the ground location.

 

 

IMG_20190906_201722988_MP.jpg

Posted

Thanks for everyone’s reply.  I haven’t had chance.  But I’m gonna assume there’s no ground on back block or on the opposite side of the oil sensor.  
 

I know there is a firewall to transmission bolt ground.   
 

it’s a weird thing to try to diagnose as the oil gauage works sometimes.  Other times it will sit zero and say low oil pressure (yet motor sounds fine).  And then either come back or fluctuate.   It can even say 550 (80 psi) at idle 600 ish rpm.  

Posted

Gauge operating oil pressure sensors have a common issue with failing and doing just what you have described. Check oil pressure with a manual gauge and replace sensor if needed.

Posted
3 hours ago, Mikebtte said:

Gauge operating oil pressure sensors have a common issue with failing and doing just what you have described. Check oil pressure with a manual gauge and replace sensor if needed.

Thanks for reply,  it’sa new sensor I got from Napa last spring.    Really wanting to go the mechanical gauge route.   Gonna have to see what is needed for that

Posted

Well, brand new parts can fail as well.  Or, it could be something else, like a wiring problem or even an actual oil pressure problem.  And was the sensor changed after you swapped engines?

 

Mechanical gauges also have their problems, as they require a physical line from the engine block to the gauge, and if that line isn't routed and protected just right, it'll rub through or break.

Posted
15 minutes ago, davester said:

Well, brand new parts can fail as well.  Or, it could be something else, like a wiring problem or even an actual oil pressure problem.  And was the sensor changed after you swapped engines?

 

Mechanical gauges also have their problems, as they require a physical line from the engine block to the gauge, and if that line isn't routed and protected just right, it'll rub through or break.

I know this wire off the harness that goes to the firewall never use been there before. He also had the battery to block ground on the firewall.  Which I moved to the block.  
 

todays trip from work to home (10 min drive) gauage mostly stuck on zero with the occasional fluctuations.   Motor sounded fine.  
 

yes the sensor was changed with this motor that’s in it now as I had this issue short after this motor was put in.  
 

I know the coolant level sensor isn’t plugged in anymore.       What also makes me curious is the ground wire he got off the harness on the passenger wire which I think goes to firewall as well.  
 

I took it to a garage before and they weren’t no help.   And it sucks how I can’t even pop my hood where I live anymore lol.  
 

edit: should note , sometimes when it says zero pressure it doesn’t say low oil pressure.  When some other times it can

Posted

Have you looked at the pins in the plug that goes to the sensor? One could have pushed out on install and is making contact erratically and giving a faulty signal.

As for the ground wire, just ground it some place, as long as it is grounded you are good.

Posted
43 minutes ago, Mikebtte said:

Have you looked at the pins in the plug that goes to the sensor? One could have pushed out on install and is making contact erratically and giving a faulty signal.

As for the ground wire, just ground it some place, as long as it is grounded you are good.

I’ll have find a friend that’ll let me work on my truck and take the intake off to have a look.   (Can no longer to car work at my apartment , it’s where the motor swap was done lol)                
 

I know the battery to bottom block ground is there.   Just not the back of the block by the oil sensor.  

Posted

Merry Christmas everyone!  
 

just took my new tablet out with the torque pro app.  The oil pressure on there is erratic too.  So must rule out the cluster.  
 

I quickly checked under the hood.  That ground on passenger back that’s supposed to goto the back block.  It seems a little hack job and does goto the firewall bolt that wire end seems kinda brittle too.   
 

I’ll have take it somewhere I can take a better look.   
 

does that have to go on the back block or can I cut it and route it anywhere on the motor ?     Just trying see if I can avoid pulling intake off again lol.  
 

thanks again for everyone’s help.  

Archived

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

  • 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   5 Members, 0 Anonymous, 1,769 Guests (See full list)

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...