Jump to content

2015 Truck 6.2 L Engine, 8L90E Transmission troubles, problems, fixes

NiceDay

By NiceDay
in Troubleshooting & Recalls

Recommended Posts

pm26 Senior Enthusiast

pm26

Posted
Posted

Hello

 

Thinking about purchasing a new GM truck. I am wondering if anyone is having any problems with their new 1/2 ton trucks. Is GM having any problems with the 6.2 Liter Eco Tec 3 engine or still having some troubles with the new 8L90E Transmission. Other troubles and their solutions would be intresting too.

 

It would be nice to learn in advance what to expect, will it be a wonderful smooth ride. Should I expect a few fixable bumps along the way or am I entering a nightmare ride.

 

Thanks in advance for your input.

Success stories are certainly welcomed for a well rounded view.

Chances are, it will be "a wonderful smooth ride" for about 3000 miles, by which time the sloppy tolerances and shoddy assembly of various moving parts will rear their ugly head. Then it is time to trade the truck in for a new one.

  • Replies 76
  • Created
  • Last Reply
SierraMyst Enthusiast

SierraMyst

Posted
Posted

UPDATE:

 

Got my truck back yesterday with the new transmission they promised, It has performed without a flaw...no hard shifting or any clunking...I'm keeping my fingers crossed that all stays that way.....I guess I will see if it holds up after a couple hundred miles...wish me luck!

Please keep us updated.

Jtodd Enthusiast

Jtodd

Posted
Posted

UPDATE:

 

 

After recieving my truck back on Monday, with the new transmission as of yesterday afternoon it began to hard shift and make a banging noise when I accelerate and decelerate. Seems like the more I drive it the worse it's getting! I have a case with GMC just called and left numerous messages...TELLING THEM I WANT OUT OF THIS TRUCK!!!it has cost me nothing but time and money

pm26 Senior Enthusiast

pm26

Posted
Posted

UPDATE:

 

 

After recieving my truck back on Monday, with the new transmission as of yesterday afternoon it began to hard shift and make a banging noise when I accelerate and decelerate. Seems like the more I drive it the worse it's getting! I have a case with GMC just called and left numerous messages...TELLING THEM I WANT OUT OF THIS TRUCK!!!it has cost me nothing but time and money

That's really frustrating. Especially for a truck with a nice engine like the 6.2, and nice interior trim on top of that.

CounterMeasure Enthusiast

CounterMeasure

Posted
Posted

UPDATE:

 

 

After recieving my truck back on Monday, with the new transmission as of yesterday afternoon it began to hard shift and make a banging noise when I accelerate and decelerate. Seems like the more I drive it the worse it's getting! I have a case with GMC just called and left numerous messages...TELLING THEM I WANT OUT OF THIS TRUCK!!!it has cost me nothing but time and money

 

I've had two transmissions in my 6.2, along with many "relearn procedures", so I really feel for you. In case it helps, what I noticed for each of those cases is for the first few miles, the transmission was really nice and smooth. Then after that it got really bangy and clunky with lots of harsh shifting. Especially when cold. Then a few hundred miles later it settled in a bit, but it never gets back to that original smoothness.

 

What I've been told by those "in the know" is that's part of the programming to figure out the shift pressures. The transmission data tables have specific shift times, depending on RPM, torque, temp and so forth. So the transmission has to figure out the shift pressures needed to hit those times. And the only way it can figure them out is to try different pressures and record if it hits those times. Recently, I've personally seen the data tables in question, and what sucks is there are A LOT of values in the tables for the various factors. So it can take a while for the transmission figure out the pressures, because you have to take it through the various driving conditions for each of those points.

 

Long story short, I'd bet that if you give it more miles, it will settle down. But I am totally with you that it really sucks in the mean time. There was a period of time in all that mess that I also wanted out of my truck and back into my Tundra. Sometimes I still do, but not worth the trade loss and hassle at this point. So I've decided it will be the last GM product I will own, or at least for a very long time, and I try to dissuade friends and family away from a GM product by telling them all the issues I've had and how they've treated me.

Jtodd Enthusiast

Jtodd

Posted
Posted

 

I've had two transmissions in my 6.2, along with many "relearn procedures", so I really feel for you. In case it helps, what I noticed for each of those cases is for the first few miles, the transmission was really nice and smooth. Then after that it got really bangy and clunky with lots of harsh shifting. Especially when cold. Then a few hundred miles later it settled in a bit, but it never gets back to that original smoothness.

 

What I've been told by those "in the know" is that's part of the programming to figure out the shift pressures. The transmission data tables have specific shift times, depending on RPM, torque, temp and so forth. So the transmission has to figure out the shift pressures needed to hit those times. And the only way it can figure them out is to try different pressures and record if it hits those times. Recently, I've personally seen the data tables in question, and what sucks is there are A LOT of values in the tables for the various factors. So it can take a while for the transmission figure out the pressures, because you have to take it through the various driving conditions for each of those points.

 

Long story short, I'd bet that if you give it more miles, it will settle down. But I am totally with you that it really sucks in the mean time. There was a period of time in all that mess that I also wanted out of my truck and back into my Tundra. Sometimes I still do, but not worth the trade loss and hassle at this point. So I've decided it will be the last GM product I will own, or at least for a very long time, and I try to dissuade friends and family away from a GM product by telling them all the issues I've had and how they've treated me.

Jtodd Enthusiast

Jtodd

Posted
Posted

Thanks for the info!! This has been the most depressing vehicle I have ever owned, "What a nightmare"! I too will never have anything good to say about owning a GMC!

txmuder Enthusiast

txmuder

Posted
Posted

Jim,

Did the updates correct the shift from park to drive and did you have a delay or clunking before the updates?

 

If you could post the procedure numbers that would help a lot of folks on here.

Yes JB it did but now after 4 weeks almost its still very smooth and no more issues as of today that is.

 

Not sure of the procedure number but I will dig up the warranty ticket to see if it has one, I remember the service manager/Adviser told me that it required 3 different upgrades to the TCM (transmission control module)

  • 2 weeks later...
Jtodd Enthusiast

Jtodd

Posted
Posted

Back at the dealership after a new transmission..took it in 2 days ago...haven't heard anything yet....this will be the 4th time since November....??

Wnc66 Enthusiast

Wnc66

Posted
Posted

I'm also dealing with this matter! What a crock! Love the motor but the transmissions are junk! Dealer and Chevrolet giving me the Bs stories! Last Chevrolet ever! I work for a major supplier for GM, and all I can say to my coworkers is how disappointed I am with this truck! They listen!

Jtodd Enthusiast

Jtodd

Posted
Posted

I know what you mean!!its all a crock..just received my truck back 3 days ago and as of yesterday it's back to hard shifts and clunking.Been trying to get ahold of the GMC REP handling my case but she is out on Easter Vacation.

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted

I know what you mean!!its all a crock..just received my truck back 3 days ago and as of yesterday it's back to hard shifts and clunking.Been trying to get ahold of the GMC REP handling my case but she is out on Easter Vacation.

 

Good Afternoon Jtodd,

 

I would certainly like to look into your case further and assist with any questions you have regarding your truck. Please feel free to send us a private message with any questions you have. Thank you and we look forward to hearing from you.

 

Anisha T.

GM Customer Service

bmc350 Enthusiast

bmc350

Posted
Posted

Thank you all for documenting your issues with your trucks. My truck is a 2015 Sierra w/6.2. Has been having minor shift issues for a while and they started getting progressively worse. At the point now that I have to take it in, as the service 4WD recently started showing. Beside the very hard shifts, I'm also having transfer case issues and recently found out my truck has been stuck in 4WD Hi and will not come out of it. This thread and a few others gave me some information for when I take it into service. Good luck with all your trucks...

Jtodd Enthusiast

Jtodd

Posted
Posted

 

Good Afternoon Jtodd,

 

I would certainly like to look into your case further and assist with any questions you have regarding your truck. Please feel free to send us a private message with any questions you have. Thank you and we look forward to hearing from you.

 

Anisha T.

GM Customer Service

Archived

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

Go to topic listing

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