Jump to content

8 Speed Transmission Recall?

seniorjumper82
 Share

Recommended Posts

seamus2154 Enthusiast

seamus2154

Posted
Posted

Is there anyway we can confirm that we are eligible for this recall of the transmission?

 

 

 

I still have the delayed engagement when I start my vehicle and put from park to drive.

 

My TC was changed due to shuddering and they also reflashed the computer to match new converter. If you google that # I referenced it states the stator shaft must be changed w/ a new check ball. I don't know what that entails, but a dealer tech opening my trans is not what i want if it can be avoided.

  • Replies 87
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

seniorjumper82
seniorjumper82

Nothing in the mail. Checked for recall with my Chevrolet app and popped up. GM program #2044120 date issued Jun 21,2016. Program title: Cracked 2-3-4-6-8 Clutch Piston   Program description: Cert

FishinJ
FishinJ

I had my TC replaced at the end of June and all my shuttering, vibration and clunking is gone. Since then I have driven from FL to MI and all over. Put on a lot of miles and it drives smoother than

ram1067
ram1067

X2 and that's why i lease.....pos will be in the used pool in 1.5yrs

MojoTexas Enthusiast

MojoTexas

Posted
Posted

I'm new to the forum, but found this thread (and site) by searching for information on this recall.

 

I just purchased my 2016 Sierra last month, and it's at the dealership right now. Supposedly it's going to take several days for them to get a new transmission from GM. The service manager said that it's about a six-hour job, but there's only a couple of their technicians that are really qualified for a big job like completely swapping out the transmission. Needless to say I'm not very thrilled that I've only had the vehicle for five weeks, and I'm having to put it in the shop for roughly a week.

FishinJ Enthusiast

FishinJ

Posted
Posted

I had my TC replaced at the end of June and all my shuttering, vibration and clunking is gone. Since then I have driven from FL to MI and all over. Put on a lot of miles and it drives smoother than ever since the repairs were made.

  • Like 2
Dndodd Enthusiast

Dndodd

Posted
Posted

Thanks, Mine only has 1200 miles on it and the transmission has never seemed to be consistent. One minute it seems OK then it acts up as described in the threads. Jerky, Shudders, etc.

p7m89mm Enthusiast

p7m89mm

Posted
Posted

Is the slipping and flaring that's discussed the same that has been reported when slowly exiting a turn or hill starting?

 

 

Sent from my iPhone using Tapatalk

  • Like 1
camcamaro1991 Enthusiast

camcamaro1991

Posted
Posted (edited)

I'm new to the forum, but found this thread (and site) by searching for information on this recall.

 

I just purchased my 2016 Sierra last month, and it's at the dealership right now. Supposedly it's going to take several days for them to get a new transmission from GM. The service manager said that it's about a six-hour job, but there's only a couple of their technicians that are really qualified for a big job like completely swapping out the transmission. Needless to say I'm not very thrilled that I've only had the vehicle for five weeks, and I'm having to put it in the shop for roughly a week.

 

Mike who is your home dealership, I got my at Sewell Dallas GMC.

Edited by camcamaro1991
MojoTexas Enthusiast

MojoTexas

Posted
Posted

 

Mike who is your home dealership, I got my at Sewell Dallas GMC.

 

I bought my Sierra from the GMC dealership in McKinney. I wanted the "All Terrain X" package, and they were the only dealership around that I had exactly what I wanted on the lot.

 

I am curious if they will have to pull all the affected vehicles off the lot and repair them before they sell them. It's my understanding that they're not supposed to sell a vehicle with an outstanding recall in effect. With the 2017 models coming out soon, I think they would be highly motivated to start clearing out the 2016 inventory, and it's going to be tougher to do that if they have to replace the transmissions first.

 

When I dropped mine off yesterday, they said that the standard for replacing a transmission is about six hours. Multiply that by all of the affected vehicles that they still have in inventory...what a mess!

martinto Enthusiast

martinto

Posted
Posted

Very interesting situation. I've had my 2016 Sierra w/6.2 and NHT for a few months and have not experienced a problem thus far. Only 3000 miles so far. Did tow a travel trailer over 700 miles with no problem...HOWEVER, I'm heading out on a 6000+ miles cross country road trip towing the travel trailer. I'll be closely watching the 8 speed performance, and trust/hope I don't experience any issues. Rolling the dice!

George C Enthusiast

George C

Posted
Posted

I'm on my third transmissions n in my wife's Yukon Denali. None of the situations no were failures. Clunk for the first, and a stator replacement for the second.

Work was done, and no further issues.

seamus2154 Enthusiast

seamus2154

Posted
Posted

Are you saying they changed the whole transmission for each of those issues or repaired them??

seamus2154 Enthusiast

seamus2154

Posted
Posted

dont have them touch it unless its bad. IMHO

 

I can agree with that. I did have them replace the TC but that is just out and in, figured how could you screw that up? Had no choice as it was shuddering, and clunking. This delayed engagement is not just when cold, mine is doing it, even hot after sitting, just going in a store for a bit. Not eager to have a tech taking apart my trans, but a replacement I am open to, thats why i am asking.

Badass69 Senior Enthusiast

Badass69

Posted
Posted

It will be fine.... I had mine done as my delay was an all the time thing and this helped.

 

Sent from my PURE XL using Tapatalk

ChevyRoofer Senior Enthusiast

ChevyRoofer

Posted
Posted

It will be fine.... I had mine done as my delay was an all the time thing and this helped.

 

Sent from my PURE XL using Tapatalk

 

Did it occur in hot and cold weather? We're at 103 regularly here and I get the delayed engagement every time.

 

Was planning on bringing it into the dealer, just wanted to confirm there hasn't been countless horror stories from this fix.

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,640 Guests (See full list)

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