Jump to content

Recommended Posts

Posted

I wish I had seen this a few months ago. Had this very same issue while driving home to DE from NYC. Oil pressure took a nose dive and I was still 60+ miles from home on the NJ turnpike. Very high pucker factor!

 

Question, is this something that happens frequently? How often should the screen be replaced?

Posted

Seems to still be confusion here on issues with these trucks regarding the oil pressure sending unit screen. 

 

First and foremost let's clarify which engines have the screen below the oil pressure sending unit.  In short it's only on engines equipped with active fuel management.  In the full size trucks that equates to any 5.3 in a GMT900 bodied truck from 2007 through 2013(LY5, LH6, LC9 etc).  Otherwise it would also be present in the L76 6 liter trucks as well as the L94 equipped 6.2 powered SUV's and the oddball hybrids 6 liter (LFA or LZ1).

 

  Regular L92 or L9H 6.2's, the LY2 or L20 4.8 or the LY6 and L96 in the HD trucks do NOT have the screen under the sensor.

 

Furthermore no GMT800 truck (1999 through 2007 classic) has the screen as those are Gen 3 engines and this pressure sender screen is a Gen IV thing only as outlined above.

 

 

  • Like 1
Posted

I have the same issues but I pulled my sending unit and the screen was fine. It looks like I have leaky valve seals. I burn quite a bit of oil. Especially in colder weather when the metals seem to shrink a bit. 

Posted
On 3/5/2019 at 9:42 AM, jfath14 said:

I have the same issues but I pulled my sending unit and the screen was fine. It looks like I have leaky valve seals. I burn quite a bit of oil. Especially in colder weather when the metals seem to shrink a bit. 

Just because the screen looks fine doesn't mean the trash didn't sink back down. Check out my video and see how to fix it for good.

 

 

  • Like 1
  • 1 month later...
Posted (edited)

Can anyone tell me if there is some kind of fail safe for low oil pressure on a 1999. GMC Sierra 5.3?? I was driving on the interstate when it cut off on me and I couldn’t get it started back up. Wouldn’t even attempt to turn over. I know there was plenty of oil in it(just added and checked before I got on the road). Right before it died my oil pressure dropped to 0 and my DID said low oil pressure. TIA

Edited by 99GMCZ
Misspelled
  • 2 months later...
Posted

Seems like most relavent place to ask this.

I have an 07 classic that the oil pressure gauge is always pegged at 80 psi until you floor it, then it goes to 0 and get a warning chime. Let off the gas, pressure goes back to 80 psi.  I replaced the stepper motor in the cluster and it had no effect.

I also have an 05 yukon denali that does the exact same thing , low oil pressure warning chimes all the time when driving. Oil sending unit on this one was changed about a year ago, but not the stepper.

 

Any ideas? Thanks

 

Posted
On 6/26/2019 at 7:02 PM, Jim1977 said:

Seems like most relavent place to ask this.

I have an 07 classic that the oil pressure gauge is always pegged at 80 psi until you floor it, then it goes to 0 and get a warning chime. Let off the gas, pressure goes back to 80 psi.  I replaced the stepper motor in the cluster and it had no effect.

I also have an 05 yukon denali that does the exact same thing , low oil pressure warning chimes all the time when driving. Oil sending unit on this one was changed about a year ago, but not the stepper.

 

Any ideas? Thanks

 

More than likely it is just the oil pressure sensor. You don't have the filter under the sensor on the old body style but the sensor is in the same place and the replacement is the same minus the filter. Look at the video above. Still blow the passage out to make sure nothing is clogging it. 

 

On 3/6/2019 at 5:59 PM, carnau said:

 

 

 

 

Posted

Seems like most relavent place to ask this.

I have an 07 classic that the oil pressure gauge is always pegged at 80 psi until you floor it, then it goes to 0 and get a warning chime. Let off the gas, pressure goes back to 80 psi.  I replaced the stepper motor in the cluster and it had no effect.

I also have an 05 yukon denali that does the exact same thing , low oil pressure warning chimes all the time when driving. Oil sending unit on this one was changed about a year ago, but not the stepper.

 

Any ideas? Thanks

 

Posted

I guess maybe the denali could have gotten a faulty new sensor. Or wasn't cleaned out enough.

Going to follow video advice, and blow out the tube .

 

  • 1 month later...
Posted

Soooo, the oil pressure isn’t low, the sending unit is just not seeing full pressure because of the screen? Can you just remove it with a pick or something and pop in the new screen or is it more involved then that? If so I’m gonna order a screen and swap it out in like 15 min. 

Posted
On 8/9/2019 at 12:52 AM, Farley_shawz said:

Soooo, the oil pressure isn’t low, the sending unit is just not seeing full pressure because of the screen? Can you just remove it with a pick or something and pop in the new screen or is it more involved then that? If so I’m gonna order a screen and swap it out in like 15 min. 

Watch my video above.

  • 1 month later...
  • 4 weeks later...
Posted (edited)

Carnau, watched the video you posted, thank, might come in handy in the future.  Just kinda crappy you have to keep this whole thing in the back of your mind in case this problem pops up when you're on the road somewhere.

Have you done the job?  Someone earlier in this thread mentioned using a regular deep socket but the guy in the video says you need a special one?   I'd think a regular 6 point socket would work..?

Edited by Fisherguy58
Posted (edited)
On 3/6/2019 at 5:59 PM, carnau said:

Just because the screen looks fine doesn't mean the trash didn't sink back down. Check out my video and see how to fix it for good.

 

 

much thanks for that video !! had 20psi hot idle now 38

Edited by nqabigt
spelling
  • 1 month 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

  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...