Jump to content

What are GM specs for oil psi range on 6.2

Payton34

By Payton34
in Troubleshooting & Recalls

 Share

Recommended Posts

Payton34 Enthusiast

Payton34

Posted
Posted

I have looked around and find so many answers.  What is the actual spec GM says is normal oil psi range on a 2014 6.2.  I never noticed before but sitting in a drive thru after driving an hour the oil psi was at 22-24psi.  It goes up to 40 when driving and sometimes to 60 when accelerating hard.  When it is a cold star It is always at 40psi then drops to 32-35 after 5-10 minutes of warm up.  I must have never seen it go to 22psi before cause the inst cluster screen has been in technology page which doesn’t show oil psi. I have been looking at oil psi gauge more ofter since I had lifter fail a year ago. Before the lifter failure I am pretty sure I never saw my oil psi change from 40 no matter what

  • Like 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

I don't know if you will find some exact specs because these trucks use a variable oil pump that is controlled by the PCM.

 

I think the minimum oil pressure is 7-10psi though at idle. The oil pressure you are seeing is completely normal and I can assure you that it's been like that for the entire life of the engine. I've owned several LS engines and had my 2016 Silverado for 4+ years now and the oil pressure has been like your the entire time.

  • Like 2
Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted (edited)

Hot oil pressure minimums.

22 psi @ 1,000 rpm

30 psi @ 2,000 rpm

33 psi @ 3,000 rpm

LV1, LV3, L83, L86 and L96. 

 

These are test gauge numbers. Don't trust that dash gauge. 

 

 

Edited by Grumpy Bear
  • Like 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

Isn't it dumb that they say 1,000rpm. These engines idle at 525rpm from the factory, so basically cut the 22psi in half for that in my opinion.

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted

I didn't want to say anything until I checked on some things. 

 

22 psig is the minimum oil pressure these AFM lifters will work properly. 

1,000 rpm is just under the lowest rpm the AFM will stay engaged on decel. 

Spec is then set for safe operation. So...no, not so dumb. IMHO of course. 

 

I'm down the road at 55 mph roughly 1200 rpm and 38 psi dash gauge.

1,000 rpm still 38 psi

Just under 600 rpm idle 33/34 psi. Drops about the breadth of the needle. 

 

Yes, it's a six and yes, it has the same oiling system and same specs.

0W30 oil. 165K mile stock motor. FYI. But I've run 0W20 in this and 10W30. Not one psi difference in hot oil pressures. 

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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...