Jump to content

Recommended Posts

Posted (edited)
2 hours ago, Lfod1836 said:

I believe I read or saw in a video somewhere that the HD's starts out in second gear when not under load. This prevents tire spin and excessive wear.

It starts in 2nd (per my iDash gauge) unless the tow haul mode is engaged or M1 is selected. Starting in 2nd doesnt bother me from a stop. I do feel it is a bit slugglish from a rolling stop, like a slow yield or trying to cross traffic in a hurry.

 

Edited by sdelam
  • 7 months later...
Posted (edited)

I'm new to this forum and am respectfully requesting some help.  For a 2020 Chevrolet Silverado 3500HD with the 6.6 liter Duramax diesel engine and the Allison branded 10 speed transmission 10L1000, does anyone have a factory torque spec for the 16 bolts that fasten the transmission oil pan to the transmission case?

Edited by Montana Skies
  • 3 weeks later...
Posted
I called the dealer about the hard shift from highway speed to a stop, and the service rep told me this was completely normal for this transmission.  He said there was nothing they could do, and it will probably go away after a few thousand miles.
 
Not sure if I believe him, but maybe I'll give this truck another couple of months before I start looking at other dealers.

Doesn’t sound right. Have 12k miles on my truck. Probably 3/4 of that towing. Never experienced what you’re describing.


Sent from my iPhone using Tapatalk
Posted

Have a 2020 GM duramax, 2351 kms and my transmission is shot, has to be replaced. Dealer advised GM will not let them diagnose the problem and a new transmission is being shipped. After doing a bit of research it appears these new 10 speeds have lots of issues, GM needs to step up. After spending almost $100k CAD ($74/ 75k USD) this is BS,  GM not only should offer to replace the tranny but should actually provide a new vehicle in my humble opinion. Most other industries provide replacement of their product with such major issues. Am really pissed off at at the moment. No wonder people buy Japanese/ Korean for their overall quality.

Posted
2 hours ago, CarlJ said:

Have a 2020 GM duramax, 2351 kms and my transmission is shot, has to be replaced. Dealer advised GM will not let them diagnose the problem and a new transmission is being shipped. After doing a bit of research it appears these new 10 speeds have lots of issues, GM needs to step up. After spending almost $100k CAD ($74/ 75k USD) this is BS,  GM not only should offer to replace the tranny but should actually provide a new vehicle in my humble opinion. Most other industries provide replacement of their product with such major issues. Am really pissed off at at the moment. No wonder people buy Japanese/ Korean for their overall quality.

Where are you hearing that they have a lot of problems with the new HD transmission? 

 

 

  • 2 weeks later...
Posted

I'm on my second 2020 Silverado 2500. This first had a steering issue that I think was actually a faulty electronic power steering unit. It was bought Sept of 19. but it shifted like butter. My current '20 2500 drives like a dream.... except every 800mi or so, it will also lunge when shifting down to fist right before complete stop. I took it to dealer and they said there were no codes reported.  It seems like both issues I have had with both trucks started at about 1500mi

  • 1 year later...
Posted

The 10 speed is not an Allison. Zed F gear box the same that’s in Fords. Allison doesn’t have a 10 speed. 

Posted (edited)

Ford developed the 10 speed that is used in the 1/2 tons

As I understand it each uses there own transmission control. 

(as published in the media, they also share a gm developed 9 speed fwd trans)

 

Each has their own HD transmission. 

GM builds theirs.

In media video introduction they discussed in interaction with allison during development  

 

Pics of the HD pickup transmissions:

 

 

cq5dam.web.881.495.jpeg

Ford HD 10 speed

 

 

 

F15-trans-2.jpg

GM HD 10 speed

 

 

GM/Ford 10 speed 

 

Edited by redwngr
  • 1 month later...
Posted

10 speed wasn’t designed by GM and Allison. Joint effort with Ford, GM and Zed F. Zed F gearbox. Ford designed theirs for their trucks an GM designed theirs. Allison did do testing on them, but it already was a done deal. 

Posted
On 12/5/2021 at 10:43 PM, KennyL said:

10 speed wasn’t designed by GM and Allison. Joint effort with Ford, GM and Zed F. Zed F gearbox. Ford designed theirs for their trucks an GM designed theirs. Allison did do testing on them, but it already was a done deal. 

This is not true.  Ford and GM initially worked together on HD trans.  They decided not to continue the relationship and GM worked with Allison to complete the project.  I'm not sure where ZF part is coming from.  ZF has never been involved with GM.

 

#iworkforGM

Posted
On 12/5/2021 at 10:43 PM, KennyL said:

10 speed wasn’t designed by GM and Allison. Joint effort with Ford, GM and Zed F. Zed F gearbox. Ford designed theirs for their trucks an GM designed theirs. Allison did do testing on them, but it already was a done deal. 

 

 

Yea no, ZF was not involved.  

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   3 Members, 0 Anonymous, 1,615 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...