Jump to content

Who likes their new 10 Speed Transmission


Recommended Posts

Posted

So who has the new 10 speed in their 2018 Yukon Denali or 2018 Escalade.

 

How do you like it?

 

Does it downshift better than my 8 speed and 6 speed?

 

let us know what you think!

 

 

Posted

It takes a while to get used to that's for sure. But its wild how its ALWAYS right there for power and your not waiting for that downshift to accelerate

Posted

This is interesting.  Maybe there aren't enough 10 speeds out there to complain about, or GM actually built a good transmission!!  

Posted

I had a 2015 with the 8 speed and it had many issues, so I understand the complaints. But I bought a 2017 Denali 8 speed and it is flawless and greatly improved. Not one issue 10,000 miles so far. I figure the 10 speed will be awesome 2-3 years in. GM never hits it out of the park on year one....never. 

Posted

just returned from 3200 mile trip to Moab! I give the 10 speed a great review overall. It handled Vail pass and everything else easily. It downshifts almost instantly and you can control it with the throttle through 4 downshifts once you get the hang of it.. that is you can push more and get another gear then another then another.. I still use manual more than I should in the mountains and kept the rpm at about 3200-3500. No trailer, but full of stuff.

 

Only downside I can tell to date at 6K into it is it is a bit stiff when really cold and just starting out (as is the electric PS). But I really don't mind if this is a "characteristic" and not a sign of something bad. Cold mechanicals shouldn't work like warm ones and remind me to go easy. Seems to be a bit more fussy when cold of late. But I am really quite sensitive of this stuff. Seems like the 1-2 shift seems to throw it off some but it is almost imperceptible. 

 

The transmission has been completely perfect when warm. Really impressive.

 

Overall, I never had a 8sp, but the 10 is really impressive so far. I had a 6 sp Jeep GC prior, and a 4sp tahoe before that, not to mention the K5 with OD!

 

Run temps for trans are up to 180F to date in the mountains going about 80MPH up in cold rain / snow in 4WD H, no trailer. Run below 150 otherwise.

 

I drive really fast on the hwy, I am not bragging, I am admitting. With 4 bikes on the back.

Totals for the entire trip were 3200miles, 65mph ave, 18.9mpg ave. Temps were probably ave 40F. This includes mountains, even some 4WD low in moab where it did OK considering...

 

18.9mpg seems amazing to me considering these parameters. I mean in Utah, I was going 93mph on I80! (16mpg ave then).

 

This trip was the first of many and clearly confirmed to me that I made the right call buying this thing. Not to be political, but I read about the new Ford and Lincoln ecotechs with the same trans, and everyone writing that there is no competition for them...  I just cannot imagine wanting that setup... My GMC Yukon Denali is simply made for (western) road trips as I see it.

Posted

I'm glad to hear the 10 speed works well.  I'm NOT happy with my 8 speed.  Often after slowing down to make a sharp turn I've experienced very hard downshift when reapplying the throttle.  It bangs into a lower gear like an old 50's/60's era Hydro trans.  Dealer says it's normal due to CAFE standards.  Thank you EPA for giving me a 70+k car with a lousy trans.

Posted

I have had a 2015 8 speed, and 2016 6 speed and a 2017 6 speed.  All have had clunky gear changes, banging into lower gears at least a few times each time I drive them.  Several relearns etc. 

 

I am glad to hear some good reports of the 10 speeds.

 

 

  • 1 month later...
Posted

I just traded my 2016 6 speed Tahoe LT for an RST with the 10-speed.

 

LOVE it. Was experiencing the same HARD downshift with tip-in as Havasubum on the 6-speed LT.

 

Was concerned that it was getting worse, so with 50K miles, I bit the bullet and got the 10-speed in the RST. 

 

Yes, it shifts a lot. Yes, there's a TINY bit of clunk on downshifting into the lower gears when tipping back in with the throttle, but I love it.

 

And the truck JUMPS!

  • 11 months later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,066 Guests (See full list)

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