Jump to content
Message added by Zane,

Hey all — this question comes up regularly, so we've put together a full reference covering lug nut torque, bolt patterns, stud sizes, and socket sizes for every Silverado, Sierra, Tahoe, Yukon, Suburban, Escalade, Colorado, and Canyon from 1999 through 2026.

👉 GM Truck Lug Nut Torque Specs: 1500, HD, SUVs (1999–2026)

Recommended Posts

Posted

I use my impact gun and have for 20+ years. Shops tell you to re-torque after 50 miles and when I've checked them, they don't even budge using a johnson bar. So you tell me that they use a torque wrench when I can't budge them with a johnson bar?

Posted

f17b430129b63dd7ce9e204389c8bf27.jpg

 

Solves that battle lol

 

I torque down using my calibrated breaker bar and arm force. Never had an issue

 

 

Sent from my iPad using Tapatalk

  • Like 4
Posted (edited)

anybody ever use a torque wrench to figure out how tight the shops run them on with an impact gun? I'm willing to bet it's higher than required.

I've tried this, my wife's G6 came back from the dealer when they put new springs in the back. Torque was between 100 and 170, I undid them and re-torqued at 110

Edited by Coby7
Posted

anybody ever use a torque wrench to figure out how tight the shops run them on with an impact gun? I'm willing to bet it's higher than required.

Yeah, I check everytime and they are usually loose...at least my shop is, FWIW, they don't kill them, just run them snug and hit them once. A good shop will use torque sticks to prevent over torquing the lugs...a better shop will use a torque wrench.

 

Of course I had a Big O in Los Alamos, New Mexico cross thread a nut and rivet it tight (cross threaded), took a 1" impact to twist the stud off (not the nut, the stud) so I could get the wheel off again...that Big O told me that was normal stud wear! IDIOTS!

 

Sent from my SAMSUNG-SM-G900A using Tapatalk

Posted

anybody ever use a torque wrench to figure out how tight the shops run them on with an impact gun? I'm willing to bet it's higher than required.

 

 

I usually find one or two really tight and the others not even close to the right spec. So basically they are all tighened up wrong.

 

You can over tighten anything with torque limiting device if used improperly though.

Posted (edited)

When I worked at Firestone a few years ago, I ran the lugs down with the impact ( the shop's impact wasn't as good as the other mechanics) and then torqued the lugs to the factory specs for the vehicle. Some would be at 76 and others too 175 depending on the manufacturer. The lug always turned a bit, sometimes a half rotation then the torque wrench clicked.

 

Three years later, now when I rotate my tires, I just use a breaker bar to set the torque to what feels right without feeling that I am over tightening it. I do plan on buying a torque wrench for this exact purpose, just haven't picked one up yet.

Edited by MikeB52r
Posted (edited)

4 Hard pumps on my 18" ratchet, should be good for 120 ish pounds, gotta reevaluate the mental torque wrench every year as i get stronger.

 

of course it took years to figure it out, with my father "helping" of course when I overtorqued bolts in the shop

Edited by congden
  • Like 1
Posted

This is one of those things that most don't care much about...what could go wrong??

I had a tire pass me up on the interstate once. Jackass at one of these chain tire places tightened up the lugs too tight. Fun experience. Was towing a trailer with my motorcycle. Broke all the lugs.

Happened in some back woodsy place, had a tow truck driver arrive with a busted eye from a bar fight. He wasn't even the guy I called. He was angry when I refused to let his drunken ass tow my motorcycle to his house...lesson learned.

Posted

Screenshot%202016-12-29%2015.06.53_zpsqo

It has been many years since I have had to change a wheel. Step 1 on these instructions read "Align the locating mark of the tire and wheel to the hub". What does this mean?

  • Like 1
Posted

Yeah that did bug me a bit, don't know why it would have an alignment mark, everything should be symmetrical.

Posted

Torquing evenly prevents rotor warp also. I torque the alloy wheels at 100 and the steelies at 110. Never lost a wheel and never broke a stud.

The torque spec for our trucks lugs is 140, my Z06 is 100 ft/lbs

 

You definitely want to torque them correctly as others have mentioned helps w/ rotor wear, but more importantly if 3 are @ 150+ lbs, 2 @ 80 lbs & 1 @ 100 you may find next time you check one of the nuts may be loose enough to spin w/ your finger. I lost a stud on a '95 V@ jetta beater I used for a while in college & kept tightening the lugs as best I could on an 11 hr ride from MA to sw VA & I distinctly remember being alarmed because @ every fill up along the way the remaining 3 nuts on that wheel had to be re-tightened.

Stupid as hell to drive like that, and not apples to apples because I'm sure the studs were worn & we're talking about a tiny 4 lug vehicle, but there is ALWAYS a reason certain bolts have torque ratings & others don't. They wouldn't be there if it weren't necessary....Lord knows the car companies are always looking @ ways to shave incremental costs

Posted

Just wondering out loud here, but I wonder if some of the Chevy shake problems could be from the lugs since some have mentioned that they can cause vibrations?

  • Like 1
Posted

I put wheels/tires on cars/trucks/RV's/etc all throughout college as my job (discount tire). Torque your wheels if you have the tools to do it. It was policy for us to torque every wheel we took off and put on. We used compacts as well but we have special torque sockets we had to use.

Guest
This topic is now closed to further replies.
  • 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   4 Members, 0 Anonymous, 1,691 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...