Jump to content

Recommended Posts

Posted

Hey Yall, I have Nitro Ridge Grappler 37x12.5x18s on the way. Will they fit on my 2020 2500HD without a lift. Have torsion bars cranked to level, with lots of room left.

Posted (edited)
On 11/16/2020 at 11:18 AM, mkeddie161 said:

https://r.tapatalk.com/shareLink/topic?url=https://www.gm-trucks.com/forums/topic/238565-my-upfitting/&share_tid=238565&share_fid=33003&share_type=t&link_source=app

I don't think so
Post 35 has my 35s
They barely caught when full lock....
But let me know if they do so I can go bigger

Sent from my Moto Z (2) using Tapatalk
 

I have 37's on my factory 20's but I had to crank the torsion bars to get them to fit and it still rubbed the liner and flaps. I did a 3" Cognito leveling kit 2 days later and it still rubbed the liner and the flaps but that was an easy fit. The bad part was the offset on the factory wheels and the wide 37's rubbed my new Cognito upper control arms, so I had to add a 1" spacer.

 

Long story short, you can fit 37's with a 2.5" to 3" lift/level and some cutting, but definitely NOT without a lift.

Edited by gSwift
Posted
19 hours ago, cooldude960 said:

What spacers did you run?

They were called Venum I think. They were hub centric and seemed like great quality. I knew I didn't need a really big spacer to clear everything and from what I saw, all the big name brand spacers started at 1.5" and went up. Venum was the only brand I saw that offered a 1" spacer.

  • 3 weeks later...
Posted
5 hours ago, Dhami79 said:

Just put on some 37s getting some rubbing, ill have to check out the venom spacers. No rubbing with 1"?

Mine was only rubbing the liners when I first put on the 37's, they didn't rub the stock control arms. I had to have the spacers to clear the Cognito upper control arms which pushed the wheels/tires outward and increases the rubbing issues on the liners and rub flaps. Assuming that you're running stock control arms, you can possibly trim or pull back the liners and secure them with zip ties but not 100% sure. 

Posted

I've since added 2" ECCP spacers, had to trim  liners and liner mounts. Truck looks awesome, went on a road trip and now I'm getting a deep vibration. Can't figure it out. No steering wheel shaking..had them balanced twice and alignment done. 

20201211_161704.jpg

  • Like 1
  • 2 weeks later...
Posted

Update. Just switched to 3 inch venom spacers. Truck looks sick, made the switch based on recommended hub centric spacers. Little less vibration otherwise rides great. Any ideas on what to look at next for the vibration.

Posted
2 hours ago, Dhami79 said:

Update. Just switched to 3 inch venom spacers. Truck looks sick, made the switch based on recommended hub centric spacers. Little less vibration otherwise rides great. Any ideas on what to look at next for the vibration.

Mine doesn't have a vibration at any speed that i've noticed, so i'm not sure what could be causing yours. Did it have any vibration before the lift and spacers? Your truck looks great

Posted
9 hours ago, gSwift said:

Mine doesn't have a vibration at any speed that i've noticed, so i'm not sure what could be causing yours. Did it have any vibration before the lift and spacers? Your truck looks great

No vibration before. Seems to start around 70 mph. Otherwise I love it. Throwing on some bilstein B8 5160s on the front today, hope that helps.

16078074586475761342655049401143.thumb.jpg.12fc306a86cc2fde972f9b3568913d98.jpg

Posted
7 hours ago, Dhami79 said:

No vibration before. Seems to start around 70 mph. Otherwise I love it. Throwing on some bilstein B8 5160s on the front today, hope that helps.

16078074586475761342655049401143.thumb.jpg.12fc306a86cc2fde972f9b3568913d98.jpg

I had a vibration around 65-70 mph but that was before the 37's and the dealer fixed it by road force balancing my stock tires, so unfortunately, I may not be of much help.

Posted
On 12/22/2020 at 9:04 AM, Dhami79 said:

No vibration before. Seems to start around 70 mph. Otherwise I love it. Throwing on some bilstein B8 5160s on the front today, hope that helps.

16078074586475761342655049401143.thumb.jpg.12fc306a86cc2fde972f9b3568913d98.jpg

 

 

Drive below 70 mph, that's like 75, unless you have the speedo flashed....  I 

Posted
18 hours ago, gearheadesw said:

 

 

Drive below 70 mph, that's like 75, unless you have the speedo flashed....  I 

Will the dealer flash the speedo? Thought I read some posts here that they refused to do it?

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