Jump to content

Recommended Posts

Posted

I have a 2020 AT4 2500. At 375 miles, I pulled out onto a 3 lane road an went to give it the throttle and the truck jerked an bucked and wouldn't go. It limped home at about 35-40 mph because the transmission wouldn't shift. I got an email from OnStar to have it serviced immediately. I connected my  Diagnostic tool and it gave me 4 errors, all transmission related. 

 

I took it to the dealer and they said the transmission fluid was low. They also fixed the Wireless charging pad, (factory didn't plug it in) I drove the truck for another 2 weeks and at around 1100 miles on the odometer the same thing happened. I haven't even towed anything yet!

 

Took it in again. Dealership said GM is going to replace the transmission. Then called back and said they are not going to replace the transmission, but instead the "valve body". I asked for the part# of what they are replacing and he didn't know. I will get that information when I pick the truck up next week.

 

This is super frustrating to say the least. I got a text from the salesperson where got the truck, and he said ther rep told him that 4 out of 5 trucks are having this or similar transmission problems. 

 

Has anyone else had this problem?

Posted
2 hours ago, gpraceworks said:

 ther rep told him that 4 out of 5 trucks are having this or similar transmission problems. 

Has anyone else had this problem?

Welcome to this forum!   Sorry to hear about your issue and thank goodness for warranties.  I think the "4 out of 5"  trucks story was misheard/misunderstood.  Perhaps 4 out of 5 trucks that have a transmission problem, are having this or a similar issue.    Enjoy your new truck once this hiccup is history. The '20 2500/3500's are currently the nicest trucks on the road, imo!

Posted
3 hours ago, Donstar said:

Welcome to this forum!   Sorry to hear about your issue and thank goodness for warranties.  I think the "4 out of 5"  trucks story was misheard/misunderstood.  Perhaps 4 out of 5 trucks that have a transmission problem, are having this or a similar issue.    Enjoy your new truck once this hiccup is history. The '20 2500/3500's are currently the nicest trucks on the road, imo!

I'm sure he  Exaggerated a little bit...lol.

 

I'm looking forward to getting this behind me and just enjoying it. 

Posted

3200 on mine.  Not one hiccup out of my transmission.  Have pulled up to 15000 with mine.  

Posted

When I bought my 2015 brand new I had the transmission take a crap after 200 miles. It would only shift into reverse and park. I had a great picture of it on a flatbed the day after I brought it home. They ended up replacing a bad electronic part, and back in business. For the next 94k miles I replaced a def tank heater, and a seat buzzer for the parking sensors. I got a nice bedrug out of the transmission problem when GM customer care called me to apologize about the transmission issue, unprompted.

 

My point is, that was a true Allison. Things happen, that's what warranties are for. I really doubt the 4/5 statement. Mine is smooth as silk, very nice. They'll get it fixed.

 

I drove the first 10k on my 2015 with a mild bit of nausea over the transmission and eventually forgot about it.... I wish I hadn't tiptoed those first 10k, there was no need for it.

Posted

1200 miles on mine, can't tell when it shifts, unless I watch the tachometer.

Posted
11 hours ago, jpgcrna said:

When I bought my 2015 brand new I had the transmission take a crap after 200 miles. It would only shift into reverse and park. I had a great picture of it on a flatbed the day after I brought it home. They ended up replacing a bad electronic part, and back in business. For the next 94k miles I replaced a def tank heater, and a seat buzzer for the parking sensors. I got a nice bedrug out of the transmission problem when GM customer care called me to apologize about the transmission issue, unprompted.

 

My point is, that was a true Allison. Things happen, that's what warranties are for. I really doubt the 4/5 statement. Mine is smooth as silk, very nice. They'll get it fixed.

 

I drove the first 10k on my 2015 with a mild bit of nausea over the transmission and eventually forgot about it.... I wish I hadn't tiptoed those first 10k, there was no need for it.

 

My 2020 Gasser with the 6 speed has had a couple of weird feeling shifts, but overall very nice.

 

I did see a 2020 2500HD on a flatbed Saturday at a corner and saw that they followed me and pulled into the local dealership. Curious what the problem was with that truck... didn't see if it was a gas or diesel, but I'm guessing a diesel as they mainly sell diesels there.

Posted

Well, I spoke too soon.  Mine goes in after thanksgiving for a leak inside the bell housing.  Not a major one but leaking. Wiped off inspection plate 3 times and it keeps accumulating on it after a drive.  Probably pump or front seal in the bell housing.  We will see..I hate to have transmission dropped already.  Oh well!

Posted

Well I guess we’ll find out. I guess the good news here is that the regular Allison works with this motor if all else fails

Posted

Im in the dealership now with what sounds like the same situation (same symptoms except it only felt like i lost 1st gear, after a few days the check engine light turned off and it seemed like the symptoms went away).  Service Tech is saying they are going to replace the tranny.

 

I've got about 6000 miles on it.  Pulled my 5th wheel a few hundred miles.

  • 1 month later...
Posted

So I have what appears to be a transmission issue at just over 500 miles.  The first time I went up to 74MPH I heard a hollow howling type noise that seemed to come from the front right of the truck. My passenger stated he thought he felt the floor vibrating and it sounded like it was coming from the rear.  

 

What I have learned is if I put the transmission in manual shift, then do 74, I hear the noise in 10th gear.  If I downshift from 10th to 9th the noise goes away.  If while in 9th gear I slow down to 68, the noise comes back until I downshift into 8th.  When hearing this noise, both times the tach was exactly at 1500RPM.  

 

Also, at times of acceleration if I've heard the noise at lower speeds and when looking at the tach, it is at 1500RPM.  Anyone else having this issue?

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

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