Jump to content

6 speed slip?

Kyle1971
 Share

Recommended Posts

Kyle1971 Enthusiast

Kyle1971

Posted
Posted

My 2021 Silverado Custom with the L82 and 6 speed has almost 14,000 miles on it. Had fluid and filter changed at 10,000 miles….trans always acts like it slips when shifting into 3rd gear under light to moderate throttle. More noticeable when cold in morning. Not an issue under wide open throttle. Are the torque converters bad in these??32D196F9-D550-4091-9F26-109C0C8CC74E.thumb.jpeg.0ed9baa2797831e2af0db4b9f9a455a1.jpeg

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
1 hour ago, Kyle1971 said:

My 2021 Silverado Custom with the L82 and 6 speed has almost 14,000 miles on it. Had fluid and filter changed at 10,000 miles….trans always acts like it slips when shifting into 3rd gear under light to moderate throttle. More noticeable when cold in morning. Not an issue under wide open throttle. Are the torque converters bad in these??32D196F9-D550-4091-9F26-109C0C8CC74E.thumb.jpeg.0ed9baa2797831e2af0db4b9f9a455a1.jpeg

This is certainly not what we like to hear, Kyle1971.  Please know, customer satisfaction is extremely important to us. Our team would be more than happy to take a closer look into the concerns with your 2021 Chevrolet Silverado. To do so, please send an email to [email protected] with ATTN: Kyle1971/GM Trucks in the subject line.

Please include your contact information, VIN, a brief description of your concern, and the name of your preferred dealership. We look forward to hearing from you. To learn more about GM’s Privacy Policy, please visit https://www.gm.com/privacy-statement.html. The information you provide may be monitored and recorded and is subject to the GM Privacy Statement.
 
Privacy Statement | General Motors
Your privacy is important to General Motors. This Privacy Statement addresses the personal information GM collects and how GM handles that personal information.
www.gm.com
 

Bikerjon Enthusiast

Bikerjon

Posted
Posted

Kyle please post about what the fix is/was for your transmission. I have almost the same truck Trailboss Custom,5.3, and 6 speed trans. I would like to know how this issue gets resolved. I am not aware of any torque converter issues on these trucks but that should affect all transmission gears.

Kyle1971 Enthusiast

Kyle1971

Posted
  • Author
Posted

Will do Bikerjon. GM Canada has already been made aware of my concern.

Kyle1971 Enthusiast

Kyle1971

Posted
  • Author
Posted

GM forwarded my concerns to GM Canada, and as they have done with our GMC Terrain, they don’t care. Wish I was still back in Florida because GM CANADA doesn’t care about it’s customers.

  • Sad 1
Bikerjon Enthusiast

Bikerjon

Posted
Posted

I would take your truck to your local dealer, see the Service Manager, give him a detailed description of your situation and have him follow up with GM or GM Canada. This truck is still under the powertrain warranty and they need to get it fixed.

 

I still want to know what the resolution was/is.

Kyle1971 Enthusiast

Kyle1971

Posted
  • Author
Posted

I’ll keep you posted for sure, just real disappointed in GM CANADA; got a new GMC Terrain on same day as Silverado, and the customer service up here has been bad. I’m use to Florida and Tennessee. My local dealer is good but they seem to blow off my concerns. I’ve been a drag racer and performance enthusiast for over 35 years, so I know a “slip” when I feel it.  I’ll keep you posted. 👍🏻

Bikerjon Enthusiast

Bikerjon

Posted
Posted

Kyle don't give up and don't let them off the hook.

 

If you don't get satisfaction from your dealer P.M me and I will give you another method to solve your problem.  

Kyle1971 Enthusiast

Kyle1971

Posted
  • Author
Posted

I will stay on it for sure. It’s an awesome truck! Just want it right so it lasts me. It’s not easy to keep it looking good up here, but I make sure it’s good! Anything you could suggest would be appreciated. Thank you!!13973409-3D02-48C5-A5B8-FC4FAFDAF112.thumb.jpeg.ac3665f2ae7917d8382539de0c7024c4.jpeg

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