Jump to content

Reduced engine power right after oil change

Interleukin6
 Share

Recommended Posts

Interleukin6 Enthusiast

Interleukin6

Posted
Posted (edited)

2022 LTD LT 2.7T. I just changed oil by myself today. Right after I cranked up the engine after putting new oil, my truck rumbled a little bit then threw the “reduced engine power” on the DIC. I thought it just takes a little time for new engine oil to circulate (yes, I prefilled the filter all the time). I turned off and started the engine a couple of times and drove my truck but never noticed any actual reduced engine power but the check engine light is still on the DIC whenever I started the engine. I had changed oil and filter by myself for a long time and this had never happened before. Will the check engine light be eventually cleared, or once it is on, do I need a scan tool to turn it off even though it is not an actual problem? Or I need to take mine to the dealer for possible serious issues? Thank you.

Edited by Interleukin6
Silverado4x4 Senior Enthusiast

Silverado4x4

Posted
Posted (edited)
2 hours ago, Interleukin6 said:

2022 LTD LT 2.7T. I just changed oil by myself today. Right after I cranked up the engine after putting new oil, my truck rumbled a little bit then threw the “reduced engine power” on the DIC. I thought it just takes a little time for new engine oil to circulate (yes, I prefilled the filter all the time). I turned off and started the engine a couple of times and drove my truck but never noticed any actual reduced engine power but the check engine light is still on the DIC whenever I started the engine. I had changed oil and filter by myself for a long time and this had never happened before. Will the check engine light be eventually cleared, or once it is on, do I need a scan tool to turn it off even though it is not an actual problem? Or I need to take mine to the dealer for possible serious issues? Thank you.

It probably saw a low oil pressure after the oil change and threw a code, I can't remember but I think it's 5 ignition engine start cycles to reset the code if it doesn't see the issue again or you can get a scan tool to reset it.

Edited by Silverado4x4
  • Like 1
Interleukin6 Enthusiast

Interleukin6

Posted
  • Author
Posted

Ya~ I think so. I don’t think there are serious engine issues throwing the check engine light after the “reduced engine power” message right after oil change because my truck has been perfectly fine and oil change went through as it was supposed to be….  Has anyone had the same issue before? Thank you.

newdude Senior Enthusiast

newdude

Posted
Posted

If it was the P06DD for low or no pressure after startup, that really should only set if the filter wasn't pre-filled as the PI states.  Also, the PI doesn't mention anything about it stumbling or rumbling though.

 

Do you have a code reader to scan the code?

  • Like 1
Interleukin6 Enthusiast

Interleukin6

Posted
  • Author
Posted

No I don’t have a code reader but like Silverado4x4 said the check engine light disappeared by itself and everything looks ok. Can I use a code reader later when it is available to know what happened or once cleared, I can’t? 

The Raven Enthusiast

The Raven

Posted
Posted

It's the 0W-20!!! It's a conspiracy by GM to make your engine implode right after the warranty!!

 

I'm kidding...I just know this is going to turn into one of those oil weight threads.  As long as the engine is running fine and you aren't hearing any out-of-the-ordinary noises, run it for a bit and see if the CEL goes away.  Or make an appointment at the dealer - that'll always make that CEL go away, right before you take it in.

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted
26 minutes ago, The Raven said:

It's the 0W-20!!! It's a conspiracy by GM to make your engine implode right after the warranty!!

 

I'm kidding...I just know this is going to turn into one of those oil weight threads.

 

image.jpeg.13c03883c6c3ce9fdaed45e17416d61b.jpeg

 

Not a conspiracy Kevin, it's a business model. Not driven by Warranty. Driven by C.A.F.E. and EPA. The reduced warranty miles over time the result of this reality. SAE20 has a wear rate about 30% higher than SAE30. A FACT that most will never notice given their buying habits. They never own one long enough to matter to them. 

 

OP's oil pressure problems based only on weight.... Not likely. But nice try 😉 

  • Like 1
  • Haha 1
The Raven Enthusiast

The Raven

Posted
Posted (edited)
14 minutes ago, Grumpy Bear said:

 

 

 

Not a conspiracy Kevin, it's a business model. Not driven by Warranty. Driven by C.A.F.E. and EPA. The reduced warranty miles over time the result of this reality. SAE20 has a wear rate about 30% higher than SAE30. A FACT that most will never notice given their buying habits. They never own one long enough to matter to them. 

 

download.png.c2021126517b7f33c4e0ac86981491e6.png

Edited by The Raven
newdude Senior Enthusiast

newdude

Posted
Posted
15 hours ago, Interleukin6 said:

No I don’t have a code reader but like Silverado4x4 said the check engine light disappeared by itself and everything looks ok. Can I use a code reader later when it is available to know what happened or once cleared, I can’t? 

 

 

Yea, as long as its still stored.  It might wipe it out of the history after enough cycles.  

  • Like 1
newdude Senior Enthusiast

newdude

Posted
Posted
3 hours ago, The Raven said:

It's the 0W-20!!! It's a conspiracy by GM to make your engine implode right after the warranty!!

 

I'm kidding...I just know this is going to turn into one of those oil weight threads.  As long as the engine is running fine and you aren't hearing any out-of-the-ordinary noises, run it for a bit and see if the CEL goes away.  Or make an appointment at the dealer - that'll always make that CEL go away, right before you take it in.

 

 

2.7 takes 5w30 😉

  • Thanks 1

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...