Jump to content

1500 6.2L not running right

Logroller

By Logroller
in Troubleshooting & Recalls

 Share

Recommended Posts

Logroller Enthusiast

Logroller

Posted
Posted (edited)

The ‘17 Sierra 1500 6.2L idle is a little weak and its knocking or ticking some. This is the first time I changed the oil, other times by dealer. Oil pressure looks normal.

 

I put in the required 8qts 0w/20 dexos 1 Gen 2, dipstick is fine, put on the a new oul filter (same as others), and all Acdelco as it has been. Do these motors take a little bit to run correctly after an engine oil change? Never had a motor do this.

Edited by Logroller
BigBadSierra Senior Enthusiast

BigBadSierra

Posted
Posted

Try some CRC GDI  I put a can into the intake just before every oil change and all of my stumbling goes away. 

Hillwood Enthusiast

Hillwood

Posted
Posted
The ‘17 Sierra 1500 6.2L idle is a little weak and its knocking or ticking some. This is the first time I changed the oil, other times by dealer. Oil pressure looks normal.
 
I put in the required 8qts 0w/20 dexos 1 Gen 2, dipstick is fine, put on the a new oul filter (same as others), and all Acdelco as it has been. Do these motors take a little bit to run correctly after an engine oil change? Never had a motor do this.
Was it doing anything differently before you changed oil?

Sent from my SM-G965U using Tapatalk

Logroller Enthusiast

Logroller

Posted
  • Author
Posted

Nope.

this freaking dipstick. It’s reading above hatch mark now and below the dot by the tip on the other side. That’s a huge difference.

And was after I took 16+oz out, basically a little over a quart. I gotta imagine there’s quite a bit left in there even after draining for 30 to 45 minutes, becuase the new oil is dark when I drained that amount. 

 

So I have 7quarts new in there, plus whatever was left in the system from the drain, puts it over hatch and under tip dot. Freaking baffling dipstick and changing oil is not something new to me.

diyer2 Senior Enthusiast

diyer2

Posted
Posted

Lets keep this simple to start with.

8 quarts with a filter change is normal right?

Owners manual info.

Oil change will not cause motor problems.

It just decided to have a problem at that time IMO.

I would start here.

Put some Sea Foam in the gas tank and clean the throttle body.

Drive it and see what happens.

 

:)

Logroller Enthusiast

Logroller

Posted
  • Author
Posted (edited)
52 minutes ago, diyer2 said:

Lets keep this simple to start with.

8 quarts with a filter change is normal right?

Owners manual info.

Oil change will not cause motor problems.

It just decided to have a problem at that time IMO.

I would start here.

Put some Sea Foam in the gas tank and clean the throttle body.

Drive it and see what happens.

 

:)

My guess is putting 8qts in with the stuff left in the system was causing a lifter or something issue. I took a qt out and the noise went away. I hate how the dipstick reads. 

After sitting over night, the hatch mark side, inserted facing the firewall, showed plenty over top hatch. I took out a qt and its still over hatch and the opposite side of the stick reads at below the dot by tip. Say what? 

I think this stick reads weird.

Edited by Logroller
Logroller Enthusiast

Logroller

Posted
  • Author
Posted (edited)
47 minutes ago, Hillwood said:

SES light on? If so check for codes.

Sent from my SM-G965U using Tapatalk
 

No lights or DIC oil warning.

Edited by Logroller
Hillwood Enthusiast

Hillwood

Posted
Posted

It's making unusual noises though?
How many miles on her?

Sent from my SM-G965U using Tapatalk

Logroller Enthusiast

Logroller

Posted
  • Author
Posted (edited)

6.2L = 8qt

and diyer2, an oil change can cause motor issues e.g., too little, too much will cause issues.

 

771095F2-7CBE-4415-BA49-C89F9FDD69E7.jpeg

2DBDD710-F138-4552-B4F4-E391FC09BBFE.jpeg

1C256F5E-E93F-491C-B810-1B56328F3DD4.jpeg

Edited by Logroller
Logroller Enthusiast

Logroller

Posted
  • Author
Posted (edited)
12 minutes ago, Hillwood said:

It's making unusual noises though?
How many miles on her?

Sent from my SM-G965U using Tapatalk
 

Just shy of 19K. Noise went away with taking 1qt out. Have no idea whats really in it now, but my guess is even after draining for 45mins, there’s at least half to 3/4 qt, maybe more, old oil in there given how dark the new oil was when I took out the qt. There has to be a lot of places for the oil to sit in these motors. I drained the pan and then took the filter off and oil just gushed out from the filter tube. So I can just imagine areas where it sits and cannot flow down on its own.

Edited by Logroller
  • Like 1
James Elliott Enthusiast

James Elliott

Posted
Posted
Just shy of 19K. Noise went away with taking 1qt out. Have no idea whats really in it now, but my guess is even after draining for 45mins, there’s at least half to 3/4 qt, maybe more, old oil in there given how dark the new oil was when I took out the qt. There has to be a lot of places for the oil to sit in these motors. I drained the pan and then took the filter off and oil just gushed out from the filter tube. So I can just imagine areas where it sits and cannot flow down on its own.
I'd just leave it how it is now and just put some sea foam or additive in the oil like Lucas oil additive

Sent from my moto e5 cruise using Tapatalk

Logroller Enthusiast

Logroller

Posted
  • Author
Posted

No need for fuel addivtives or fuel cleaners. I’m 99% sure the noise was due to oil being over full. It’s incredibly stupid how different the dipstick will read from 30mins after running the motor to a few hours later. Just need to figure out this freaking dipstick so I can get real oil readings. Annoying shit.

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