Jump to content

1996 Chevrolet pickup 105,000 miles started it up yesterday and as I w

Chevy2014

Recommended Posts

Chevy2014 Enthusiast

Chevy2014

Posted
Posted

I started my 96 Chevrolet pickup with 105,000 miles and as I was driving around the block I noticed my check Gage's light was on and then seen I had zero pressure in oil so came back home and parked the truck.. I was in process of going to store for gasoline to now my grass. As I was mowing grass I could see some oil puddles below truck. So I check the dipstick. Still has all the oil in truck. Now I am just wondering how to troubleshoot the truck? Can I start it and see if the oil pressure is true and if it is zero would the truck knock from not getting any oil circulation? Also not sure if its coincidence the oil leaking but seems to be around the distributercap area because I can see it running down the outside of tranny dipstick.. Anyway. Any ideas? Oil sensor switch or oil pump? Anyway to test switch or cheap enough to just replace?

  • 2 weeks later...
ifixedit Enthusiast

ifixedit

Posted
Posted

The oil you see by the distributor and running down the side of the transmission is likely from the oil pressure sending unit as they are located very close to that area at the back of the block near the distributor. The sending unit may not be screwed in tightly and is allowing some oil to leak, but this shouldn't cause zero oil pressure unless it's completely fallen out or is ready to do so.

 

It's highly unusual that it would have oil pressure one day and not the next. If it does not have oil pressure you don't want to allow it to run very long as yes, things will start knocking and ticking in a hurry and engine damage will ensue shortly thereafter. While you're testing a few things I will outline here, I wouldn't allow it to run much longer than about 10 seconds until you can determine whether it's circulating oil or not. I'd start out by checking the wire going to the oil pressure sending unit and see if it has just perhaps lost it's connection and is giving a false reading at the dash. I'd also ensure the sending unit it screwed in tightly. If you don't find anything unusual with the wire or sending unit, and a short restart (again maybe 10 seconds total running time) results in the same, the next thing I'd probably try just to verify whether or not the oil pump is working and is circulating oil would be to remove one of the valve covers, whichever is easiest to remove. Then briefly start the truck and run it again for maybe 10 seconds tops. If it has oil pressure you should have oil squirting all over the place with the valve cover removed and at a minimum a considerable amount oil running down the exhaust side of the head, it's pretty easy to determine just by observing for a few seconds. If you have oil flowing it would indicate a faulty oil pressure sending unit or a bad connection to it. If you don't see any oil squirting out of the pushrod cup holes on the top part of the rocker arms, shut it down ASAP as you've definitely got problems. At that point which indicates no oil pressure I'd suspect maybe the shaft driving the oil pump has either sheared off or maybe the pick-up tube going to the oil pump has fallen off and is laying in the bottom of the oil pan which is pretty much going to require the engine has to come out to repair properly as on small block Chevys you can't just drop the oil pan in the vehicle without removing the timing chain cover as well. At a minimum if you attempt to do it in the vehicle it's a royal pain unless someone else here knows of a trick.

 

Good luck

Archived

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

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

  • Who's Online   5 Members, 0 Anonymous, 596 Guests (See full list)

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...