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
  • 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   5 Members, 1 Anonymous, 1,741 Guests (See full list)


  • Latest Articles

  • Posts

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