Jump to content

Transmission hard shift

Phantom 4D
 Share

Recommended Posts

Phantom 4D Enthusiast

Phantom 4D

Posted
Posted

Have a 2019 Sierra SLT X31, yeah, that's a mouthful. Anyway, when coming to a stop, I've noticed the transmission wants to "jerk" in 1st gear creating a bit of a thump, if you will. I've tried several ways of braking. Light, medium and heavy pedal. It still wants to jerk to a stop. At one time, back last year, every stop caused very hard down shifting. Of course the dealer found nothing. 

Has anyone else had this or a similar issue? If so, what was the outcome?

driver1965 Enthusiast

driver1965

Posted
Posted

The 2019 / 2020 Silverado had issues with the transmission fluid being used. In colder climates the fluid would allow "water" to get into the gears. Many transmissions were replaced and dealerships were directed to replace the transmission fluid. One can look online for the correct transmission fluid. Yes, GMC screwed up with the wrong type of fluid.

 Not knowing where you live, and if you do not trust your dealership, I would flush/replace the fluid. 45K is the recommended fluid change. I have used BG products but after every 30K I flush/replace the fluid. Enjoy your day.

ejdziurka Enthusiast

ejdziurka

Posted
Posted

Sounds like typical 8 Speed behavior.   My solution was to trade it in on a 10 speed.

  • Like 1
11bravoZ71 Enthusiast

11bravoZ71

Posted
Posted

I had the EXACT same issue develop with my 19 LT Z71 around 20k miles I now have almost 50k miles and it never did it again. After I took it in and described what you said… they checked and said it was a “software anamoly” and updated the transmission I called it the the 2-1 transmission jerk only happened when coming to a stop.  After they fixed it I drained and filled my tranny with the new Mobil 1 blue label ATF and mew filter from the dealer. For good measure. Because of possibility that that is was filled with the old specd ATF fluid since mine was one of the first 19’s produced. This 8 speed has been great since then. 

Phantom 4D Enthusiast

Phantom 4D

Posted
  • Author
Posted

Thanks for the input. Taking it to the dealer for the fourth free oil change. Going to give them a heads up before I go. Tell the service writer I want a tech to ride with me. If they refuse, the owners office is just down the hall. 

Black02Silverado Senior Enthusiast

Black02Silverado

Posted
Posted

Just curious as to when you purchased your truck and how many miles on it.  I would push the issue and at least have them change out the fluid.

Adamace1 Enthusiast

Adamace1

Posted
Posted

I have same issue. Hard downshift into first. Dealer couldn't it to do it on test drive. It only does it one day out of 12 days. They said GM will not do fluid change because 21 have new fluid. Plus they say it has newest software installed. If it gets worse I'll bring it back. The 8 speed has complaints for over 5 years, so I knew what I was getting into.

Acpantera Enthusiast

Acpantera

Posted
Posted

I only have about 2,000 miles on my 2.7 w/8spd. I had a few late down shifts to 1st, making for a not so smooth slow stop. Hopefully this tranny has learned my habbits, hasn't done it in the last 1,000 mikes or so.

SpeedRacerHD New Member

SpeedRacerHD

Posted
Posted

I have 2017 sierra 1500 with about 30k on the clock. This thing shifts like its got 300k not 30k. Hard in and out of first. Bang thru the gears. Only shifts good if i hammer on it! So im comin in hot everywhere i go lol......why?

 

  • Like 1
  • Haha 1
  • 9 months later...
denny noname Enthusiast

denny noname

Posted
Posted
On 9/18/2021 at 8:14 AM, SpeedRacerHD said:

I have 2017 sierra 1500 with about 30k on the clock. This thing shifts like its got 300k not 30k. Hard in and out of first. Bang thru the gears. Only shifts good if i hammer on it! So im comin in hot everywhere i go lol......why?

 

LOL That's what I'm doing now . Coming in hot.

pokismoki Senior Enthusiast

pokismoki

Posted
Posted (edited)

 

 

if these aren't tuneable, then I would reflash the factory TCU software or updated GM software  into the transmission, or have GM tech do a relearn proceedure.  the clutch to clutch hand offs for gear swaps are getting hung up, and need to be dialed in 

Edited by pokismoki
Stevo 06 New Member

Stevo 06

Posted
Posted
On 9/12/2021 at 4:28 PM, Phantom 4D said:

Have a 2019 Sierra SLT X31, yeah, that's a mouthful. Anyway, when coming to a stop, I've noticed the transmission wants to "jerk" in 1st gear creating a bit of a thump, if you will. I've tried several ways of braking. Light, medium and heavy pedal. It still wants to jerk to a stop. At one time, back last year, every stop caused very hard down shifting. Of course the dealer found nothing. 

Has anyone else had this or a similar issue? If so, what was the outcome?

I have a 2017 Silverado with 67k miles on it and my transmission is the doing the same hard down shift into 1st when stopping.  It happened six months ago the first time first thing in the morning.  After I got to Lowe's and finished shopping and returned to my truck, it was fine (although the check engine light was still on).  I cleared the fault and it didn't happen again for six months.  This time it happened again first thing in the morning and normalized after my first stop when I returned to the vehicle.  The cruise control wouldn't set while the fault was going on but worked when the system normalized (after first stop of the day).  I have an appointment with the Chevy dealer but I have to leave it there for a few days.  This is baffling to me and I hope it doesn't cost a fortune.     

Stevo 06 New Member

Stevo 06

Posted
Posted

I have a 2017 Silverado with 67k miles on it and my transmission is the doing the same hard down shift into 1st when stopping.  It happened six months ago the first time first thing in the morning.  After I got to Lowe's and finished shopping and returned to my truck, it was fine (although the check engine light was still on).  I cleared the fault and it didn't happen again for six months.  This time it happened again first thing in the morning and normalized after my first stop when I returned to the vehicle.  The cruise control wouldn't set while the fault was going on but worked when the system normalized (after first stop of the day).  I have an appointment with the Chevy dealer but I have to leave it there for a few days.  This is baffling to me and I hope it doesn't cost a fortune.     

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