Jump to content

Recommended Posts

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.

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.

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

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

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!

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.

Posted

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

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.

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

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

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...