Jump to content

Vortec Max 6.0 Oil Pressure?

07VMax

By 07VMax
in Ask A GM Technician

 Share

Recommended Posts

07VMax Enthusiast

07VMax

Posted
Posted

on my 07 nnbs Vortec Max when the engine is at normal operating temp and at idle the oil pressure Gauge is just above 20 and cruising at 60mph it is just under 40. is this normal for a 33k mile truck?? every one of my other silverados have had just over 40 at idle and around 50 cruising

  • 1 month later...
  • 5 years later...
Kingpj New Member

Kingpj

Posted
Posted

New to this group. I jus bought an 07 vmaxx with l76 engine. Was wondering if the low oil pressure with bad pump or a stock pump going out could cause a lifter collapse

  • 2 years later...
Chuck Henry New Member

Chuck Henry

Posted
Posted (edited)

I have a 07 silverado 1500.vortec max.on cold start oil pressure is 40.gets hot drops to bout 12psi at idle.is this normal.6.0 engine

Edited by Chuck Henry
  • 2 weeks later...
Jeffery Porter Enthusiast

Jeffery Porter

Posted
Posted

I have a 04 that does the same thing. Idle hot 500 rpm and gage drops to about 10 psi, touch the gas and goes to 20. Only thing left to replace is rod bearing.. No noises, Hot or Cold, I'm stumped. Any ideas out there..??

  • 1 month later...
swathdiver Senior Enthusiast

swathdiver

Posted
Posted
46 minutes ago, Jeffery Porter said:

Same issue on my 04 5.3. I was told rod bearing won't help the low pressure @ 500 rpm. I'm thinking rod and main bearings, I don't have any more ideas.

What about your pickup tube o-ring?  They usually fail around 160K miles.  Quick way to check is to overfill motor with an additional 2-3 quarts of oil to submerge o-ring.  If pressure rises, you have identified culprit.

 

The OP in this nine year old post, that's normal for an aluminum engine.

swathdiver Senior Enthusiast

swathdiver

Posted
Posted
On 12/31/2019 at 10:54 AM, Jeffery Porter said:

New o ring, new oil pump, new sender unit. No noise, just low pressure at idle.

Driving I have 20/30 1500 to 1800 rpm.

Well, you are above minimums, you can check the pump spring, maybe run a slightly thicker oil or just drive it until you schedule an engine overhaul/replacement.

Jeffery Porter Enthusiast

Jeffery Porter

Posted
Posted

I just switched to Rotalla 15w40. Helped a little on pressure. My only problem is sitting at a red light and my pressue is about 2/4. 195k on engine. Thinking of meling 296 hv oil pump, seems to help the idle issue. I have a new meling 295 pump now, didn’t help much over stock pump.

  • Like 2
  • 1 month later...
highmileslowsmiles New Member

highmileslowsmiles

Posted
Posted

Jeffery Porter, 
Did you come up with anything else?

Same issue -276k mile L76 - haven't replaced pump yet. (Already did relief valve in pan, valley cover without dod/afm, new pressure switch)

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...