Jump to content

Recommended Posts

Posted
On 8/24/2020 at 6:47 PM, Trwtow said:

what did you find out i got same exact prob 6.2 hi country 100 miles thanks

I had the same thing on my 2021 6.2 RST. 

I got word back from the dealership. Bad lifters a bent pushrods.

 

  • 1 month later...
Posted

Just started having this same issue in my 2021 RST (5.3l V8) bought in March of this year. Started running rough and misfiring yesterday on the way home. Could hear the knocking in the engine (thinking it was a stuck lifter or valve issue). The knock/tick increases in speed as the RPMs go up (and coasting with no gas pedal input stops the ticking). Parked it in front of the garage and checked the oil. It's due for a change (14% oil life left at about 6,500 miles, so first change). Oil is dirty and dark, as expected, but nothing that should be super sludgy. Turned it on today and engine is still running rough. After idling for about a minute, I got the Service Parking Brake and Service ESC messages with the traction control light. Calling dealer tomorrow.

  • 2 months later...
Posted
On 8/24/2020 at 8:55 PM, Velocity12 said:

Mine has done this several times. Service ESC, Parking brake, and traction control I think. Then the transmission shifts funny. If I turn the truck off and on again it will go away. Don’t have much faith in my local dealer so I haven’t brought it in yet. 

This is exactly what just happened to my truck (2020 trail boss) took it to dealership they said they will look at it on Monday, hope the problem can be found and fixed. Downshifts horribly 12000 miles

Posted

Following. Just had to tow my 2021 Sierra 1500 SLT with the 6.2 into the dealer as well. Stopped and filled up with fuel and on the way to work it started to misfire and shifting hard. Stopped at another gas station along the way and parked it and had a buddy that I work with come pick me up. Returned after work to haul it into the dealer and went to start it to put it on my buddy's trailer, it started running real rough with the check engine light, service parking brake light, and check ECS light all on. Started second guessing the fuel and everything but had my receipt that said I had got premium fuel and not diesel. Truck has 10k miles on it and looks terrible being pulled into a dealer by a Ford.....LMAO

Posted
7 hours ago, luke adams said:

Following. Just had to tow my 2021 Sierra 1500 SLT with the 6.2 into the dealer as well. Stopped and filled up with fuel and on the way to work it started to misfire and shifting hard. Stopped at another gas station along the way and parked it and had a buddy that I work with come pick me up. Returned after work to haul it into the dealer and went to start it to put it on my buddy's trailer, it started running real rough with the check engine light, service parking brake light, and check ECS light all on. Started second guessing the fuel and everything but had my receipt that said I had got premium fuel and not diesel. Truck has 10k miles on it and looks terrible being pulled into a dealer by a Ford.....LMAO

Welcome to the site.

 

By your description of how the engine is running, my guess would be an internal failure, lifters, bent/broken push rod as possibilities. 

Posted
On 10/16/2021 at 2:43 PM, JimCost2014 said:

Welcome to the site.

 

By your description of how the engine is running, my guess would be an internal failure, lifters, bent/broken push rod as possibilities. 

245018549_269718358386251_7083531551069240791_n.jpg.a7580753eb16453dbbf926fb5f88d815.jpg

Posted

Really don't even want to read all of these different threads on the same lifter issue anymore at all.  So disappointed in this truck now.  Should have stayed in my old one.

Posted

I got one of these. and it works great. It turns off the cylinder deactivation. https://www.edgeproducts.com/products/in-line_chips_and_modules/pulsar/pulsar_lt/parts/22451                                                                                                                               The truck runs better, no more auto shut off and I think I picked up some mileage.

  • 1 month later...
Posted

my 2021 silverado 1500LT 5.3L has the same symptoms, this started about a week ago, service parking brake, rough idle, engine light and anti-traction disabled. i find if i turn it off and then restart it goes away but yesterday i got a message from onstar diagnostics that it detected a emissions problem and i need to take it in for service within 7 days.

 

 

Posted (edited)
On 11/23/2021 at 6:10 AM, Dominic58 said:

my 2021 silverado 1500LT 5.3L has the same symptoms, this started about a week ago, service parking brake, rough idle, engine light and anti-traction disabled. i find if i turn it off and then restart it goes away but yesterday i got a message from onstar diagnostics that it detected a emissions problem and i need to take it in for service within 7 days.

 

 

This is exactly what just happened to me today. I have already had injector #4 replaced because of this 3 weeks ago. 

Edited by Mark Crocker
add more info
Posted

This sounds like a common problem and doesn’t sound like they have a fix for it. Im starting to get worried.

  • 3 months later...
Posted

My 2021 Sierra 1500 AT4 with 24000 miles, today the service ESC and parking brake screen came on. Cab started shaking if I drove above 45 mph. Steering screen on truck said to be careful.  I was pulling a trailer at the time. Was wondering if the light hook up from trailer to truck might have messed with trucks computer system. 

  • 4 weeks later...
Posted
On 8/10/2020 at 3:06 PM, xeyedjohn said:

I have a 2020 Silverado LTZ 6.2L with 4500 miles and after slowing down and accelerating again I noticed it was running very rough and seemed to be missing.  The Service ESC first came up and then the check engine light came on.  Shorty after the wrench and parking brake light came on, and I also noticed the whole time the traction control ight was illuminated.  Then the error message went to service parking brake.  This is some BS.  Will update when and if I get a resolution.

Service Praking Brake.JPG

Service ESC.jpg

Steering Assist.JPG

So, I having the same issue today(3/29/22). When going to doctor appointment!  Tried to get help from GMC service department, which was very little other than getting a appointment to get it checked & they would have to have it for 2-days & no loaner!

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

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