Jump to content

  

824 members have voted

You do not have permission to vote in this poll, or see the poll results. Please sign in or register to vote in this poll.

Recommended Posts

Posted

Thank you for this. My 16 just started doing this. Early mornings and after sitting in the parking got for a few hours.

 

I'll shift reverse, back out of my spot, and shift into drive and it'll take a couple seconds to engage drive.

 

As always, it doesn't do it all the time and so the dealer will tell me it can't be replicated.

 

Do you have any of the other pages to the TSD?

 

Mine does the same thing. 2015 with 35K and several trips to the dealer and absolutely no results. Often when it does engage a very audible clunk can be heard.

Posted

As the title states.... My 2015 GMC Sierra with the 6.2L and 8 Speed is at the dealership again with a field service engineer hoping to fix the transmission for the 5th try.

 

I will trade it in on another GMC Sierra.. and I want the 6.2L again. As you know, this sticks you with the 8 Speed transmission.

 

So.... Who has a trouble free 8 speed transmission? I have read many threads of problems, but hope to find those without problems to make the final decision: Do I get the 8 speed again in the 2016 model or do I downgrade to the 5.3L and the 6 Speed.

 

 

Please put in miles and year of your vehicle with any explanation you want in the thread.

 

I have 9,600 miles on my 2015 Denali CC 6.2 and I love the 8 speed.

To be fair, I had to bring it in at about 1,500 miles because of a hard 2-1 downshift when coming to a stop.

The dealer did some updates and it has been great since that time.

When you step into it, I love the shift point increase and the nice crisp shifts.

Posted

Love mine, 2016 5.3 w/ 8-spd, 7300 miles. The only issue I have is, most of the time, the first shift in the morning is late and firm. It not objectionable but its different and noticeable. It can be minimized with just the right amount of throttle. After that, it's fine

 

Sent from my SM-T817V using Tapatalk

Posted

So nobody has hard downshifts that emanate through the entire drivetrain? Mine happen about once a week or once a tank of gas... There must have been something wrong with mine from the factory.

Posted (edited)

What problems did it do before the tune, what did the tune fix, and what problems does it still have?

Edited by JacobC1983
Posted

Some is a preference, for instance during aggressive throttle it used to shift so smooth you didnt feel it, now it hits on each shift. Normal driving is still smooth. On some of the shifts it would have an odd delay like it was slipping, now each shift is purposeful. It does downshift with less throttle now. Things that still anoy me are when it goes through the gears on steady throttle it doesn't shift at the same rpm, like 1-2 @ 4500, 2-3@ 4400, then 3-4. @ 3800, etc. It feels like it shortshifts sometimes. Also it still clunks on decel, which anoys me.

  • Like 1
Posted

Ah dang.... the clunk on decel was one of the things I hoped a tune might fix.

Posted

Ah dang.... the clunk on decel was one of the things I hoped a tune might fix.

It still might, but I dunno. I'm still on the first iteration tune with Justin. It will be several back and fourths so it may be better. Right now he's working on tuning the blower, I'll focusbon the transmission after the engine is set.

Posted

I drove all the way home with grade braking off today, wow what a difference on the down shifts. Mines is never horrible but that cleaned up some little weirdness. Dang thing will coast forever now lol.

 

Sent From My Galaxy S6 Edge+

  • Like 1
Posted

 

I have 9,600 miles on my 2015 Denali CC 6.2 and I love the 8 speed.

To be fair, I had to bring it in at about 1,500 miles because of a hard 2-1 downshift when coming to a stop.

The dealer did some updates and it has been great since that time.

When you step into it, I love the shift point increase and the nice crisp shifts.

This was one thing I always liked about my truck too. When my foot was in it, the thing was a delight... Nice smooth and quick shifts ... It's when my foot wasn't in it that caused the problems.

Posted (edited)

Love it with grade braking off and think it's "decent, but really confused" with it on. Very smooth shifting.

Edited by Dunc
Posted

Mine's in the shop since yesterday afternoon for rough shifting and the 'Chevy Shake' at 70mph. Not sure what's happening but I have a loaner 2016 Silverado LT 5.3 with the 6 speed and it seems to shift great!

Posted

Mine's in the shop since yesterday afternoon for rough shifting and the 'Chevy Shake' at 70mph. Not sure what's happening but I have a loaner 2016 Silverado LT 5.3 with the 6 speed and it seems to shift great!

 

 

I just drove my loaner 2016 GMC Sierra SLT with the 5.3 and 6 speed for about 1000 miles and I think it shifts very good. With grade braking off it is perfect, but with it on is is substantially better than my 8 speed ever was.

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

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...