Jump to content

2016 Sierra 6.2 8speed aftermarket 4.10 gears?

WhiteLMM

By WhiteLMM
in Modifications & Accessories

 Share

Recommended Posts

WhiteLMM Enthusiast

WhiteLMM

Posted
Posted

Hey guys. Like the topic says Ive got a 2016 Sierra 6.2 and 8speed auto. Im modding the truck for a buddy. I installed a 5" rough country lift and 20x10 wheels and 305/55r20 tires. Actual diameter is 33.5" I'm wondering if 4.10 gears would be beneficial for performance or if it would just be too much quick shifting? I used a ratio calculator and with the 33s and 4.10 gears the trucks would be spinning 300rpm more at 60mph than when the truck was 100% stock.

robvas Enthusiast

robvas

Posted
Posted (edited)

IMO that's too much gear for just 33" tires

 

Is there an official list of what gears are available for the the rear end that comes with the 6.2? They had 3.23, 3.42, and 3.73 available in 2014 from the OEM. There's at least one guy out there with 4.10's isn't there? What aftermarket support is out there?

Edited by robvas
WhiteLMM Enthusiast

WhiteLMM

Posted
  • Author
Posted

I'm thinking we might wait unless I get some more input here. Truck has intake and cat back exhaust at the moment.. But kooks long tube headers/catted y-pipe and black bear tune are next.

Truck currently has 3.23 gears

WhiteLMM Enthusiast

WhiteLMM

Posted
  • Author
Posted

I found a better gear ratio calculator. Yes 4.10 would be way too much gear. 3.42 with 33s would put it back to stock 3.23 ratio and oem gears are made up to 3.73 so that would the way to go but probably not worth the $$

Txjose Senior Enthusiast

Txjose

Posted
Posted

RPM's would be 1604 at 60MPH that's not bad at all with 4.10's

 

RT

Where do u find this stuff at... I wanna know what mine will be lol

 

Sent from my Note 4 on Tapashit

Txjose Senior Enthusiast

Txjose

Posted
Posted

I have a calculator! LOL

 

RT

How do you calculate dat shiznett hommiii lol

 

Sent from my Note 4 on Tapashit

Badass69 Senior Enthusiast

Badass69

Posted
Posted

4.10s and gm's 8 speed with stock tire diameter basically gives you what Ram offers with their deeper geared zf 8 speed and 3.92's... it would be awesome actually... well but the lack of traction won't be lol.

 

Good luck with finding 4.10's though.... 6.2 trucks and max tow 5.3 trucks have the 9.76" ring gear and not the 9.5"... so 3.73 is as deep as these go using 6 speed max tow parts.

 

Sent from my SM-G900W8 using Tapatalk

redwngr Senior Enthusiast

redwngr

Posted
Posted
8L90 Gear ratios

First: 4.560

Second: 2.970

Third: 2.080

Fourth: 1.690

Fifth: 1.270

Sixth: 1.000

Seventh: 0.850

Eighth: 0.650

davidncurtis Enthusiast

davidncurtis

Posted
Posted

I'm not sure that you need to change out the gears with 33s. I'm running 35" BFGs with a 6.2L and 3.23 gears and my truck hasn't lost a bit of performance. It does have a tune on it but it does not lack anything. I pull a 7500 lb boat and its almost as if its not even there.

 

I would say let your buddy drive the truck and see if there are any issues. I doubt he will notice anything.

txmuder Enthusiast

txmuder

Posted
Posted (edited)

I went with 3.73 on mine, had 4.10 on my '12 silverado with 6 spd and yes it made it quite fast but the MPG's dropped a lot, 3.73's with the 8spd is still averaging 16-17 mpg on my daily driving and on a 300+ mile trip I averaged 21.7 mpg and that was loaded down with camping gear (fire wood) and 3 people in truck doing 70 to 80+ mph

Edited by txmuder
  • Like 1

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
 Share
Go to topic listing

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

  • Latest Articles

  • Posts

    • 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?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

      Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...