Jump to content

Recommended Posts

Posted (edited)

New here as well. After reading this I decided to to 285/55/22 Nittos from 285/45/22 oem Bridgestone Dueler A/T's

 

 

97B51FD3-8F80-4902-9157-19B7A65C3708.jpeg

Edited by jwtero
  • Like 2
Posted
On 7/15/2019 at 12:01 PM, jwtero said:

New here as well. After reading this I decided to to 285/55/22 Nittos from 285/45/22 oem Bridgestone Dueler A/T's

 

 

97B51FD3-8F80-4902-9157-19B7A65C3708.jpeg

Looking sweet!  Are those the Ridge Grapplers or the Terra Grapplers? Lift/level?

Posted

I installed power steps and with this wheel/tire combo, it make the truck look even better 

2FC81BE1-3EDE-49CC-B060-AEC2C90F168D.jpeg

  • Like 1
Posted
14 hours ago, jfuerte said:

Looking sweet!  Are those the Ridge Grapplers or the Terra Grapplers? Lift/level?

Ridge Grapplers. I had OEM Rancho shocks, I upgraded to the Bilstein 5100s all around. Set the front at its highest setting. It had a level previously from different owner. I pulled the lower level piece, and kept the top one in as I seen a few others have done. Ride is extremely smooth, and planted firmly.

7 hours ago, Dkn1997 said:

I installed power steps and with this wheel/tire combo, it make the truck look even better 

2FC81BE1-3EDE-49CC-B060-AEC2C90F168D.jpeg

This is definitely next on my list of things to do. I need them for my wife and kids, and my son is disabled so steps are needed to put him into the truck. Im 6'7" so I don't use them.

Posted
This is definitely next on my list of things to do. I need them for my wife and kids, and my son is disabled so steps are needed to put him into the truck. Im 6'7" so I don't use them.
Any rub with that set up?

Sent from my SM-G950U using Tapatalk

Posted

Yes some rubbing.  I only put a 2” level on it.  A 2.5” level would alleviate a lot of it.  It’s not bad. Full lock in reverse and if you come into a parking lot apron like maverick and goose buzzing the tower it will make a noise that’s not cool at all 

  • Like 1
  • 2 weeks later...
Posted
On 7/19/2019 at 1:28 PM, jwtero said:

Ridge Grapplers. I had OEM Rancho shocks, I upgraded to the Bilstein 5100s all around. Set the front at its highest setting. It had a level previously from different owner. I pulled the lower level piece, and kept the top one in as I seen a few others have done. Ride is extremely smooth, and planted firmly.

This is definitely next on my list of things to do. I need them for my wife and kids, and my son is disabled so steps are needed to put him into the truck. Im 6'7" so I don't use them.

When switching to the Bilsteins do you have to swap/change anything else or could I just do a straight up swap with the Ranchos and be good to go?

  • 2 weeks later...
Posted
On ‎7‎/‎19‎/‎2019 at 1:59 PM, acinquegrana said:

Any rub with that set up?

Sent from my SM-G950U using Tapatalk
 

No sir.

On ‎7‎/‎29‎/‎2019 at 10:12 PM, jfuerte said:

When switching to the Bilsteins do you have to swap/change anything else or could I just do a straight up swap with the Ranchos and be good to go?

Direct Swap, of course you have to disassemble the strut assembly to swap them. But im going a different route, and will be selling my 285/55/22 Nitto Ridge Grapplers with under 100 miles on them, and selling my Bilstein B* 5100 shocks with same less than 100 miles, and OEM steps off of the truck.

Posted
11 hours ago, jwtero said:

No sir.

Direct Swap, of course you have to disassemble the strut assembly to swap them. But im going a different route, and will be selling my 285/55/22 Nitto Ridge Grapplers with under 100 miles on them, and selling my Bilstein B* 5100 shocks with same less than 100 miles, and OEM steps off of the truck.

Where are you located?

  • 2 weeks later...
Posted

I am still waiting to pull the trigger on a set of 285 55 22 G2's.... but before I do.. Have any of you experienced a slight thump under your feet when cornering at slow speeds? I am wondering if it is steering rack related. I am posting here since you all have larger tires. Looking to see if it has affected anyone else. I'm on a ready lift 2.25 front level with UCA, and zone add a leaf. Stock tires. Loving the ride. Perfect height all around with slight rake.25cd3c2b60a79d71555cea7823a5e05d.jpg

Sent from my SM-G950U using Tapatalk

  • 1 month later...
Posted
On 7/20/2017 at 1:42 PM, pdosescu said:

I added the spacer for the look mostly. It's the same front and rear and it looks pretty solid. I ran a SuspensionMaxx 2.5" level. I loved it and the bracket for the relocation of the level sensor was good. It was actually accidentally transferred to the Fabtech control arms and it ended up making my whole lift ride better because it put the sensor at a better angle. Here's the truck with the level.

a9d3a27e92e1930da0cff1da4bb34ff0.jpg

The ride was pretty much same as stock. The only time I could feel a difference was at 75+mph and I think the aerodynamic change was the biggest difference.

 

I would highly recommend a true lift for such a size tire. Yes, it could technically fit on just a level, but it really doesn't make a lot of sense to limit the movement of the suspension that way. But I built this truck to be able to drive through a ditch if I feel like it... haha you know what I mean though.

 

Here's the truck with the Fabtech 4". I'd highly recommend this set up. I'll take pics of the upper ball joint if you want. It's solid.

0d1397f4b8cd7e60a47b13f54f02d9b9.jpgc6172030c12927cb05a027c201fc1494.jpg70e43d415075285f94124f57dd6a4fba.jpg

 

 

 

Sent from my iPhone using Tapatalk

What size spacers do you have on your truck???

Posted

Could someone with a 2.5" lift and the 285/55/22 setup take a height measurement from the ground to the top of the XM antenna please?  I'm ready to switch to the bigger tires and lift but am not sure If I will fit in my garage.  I don't really want to give up parking inside especially with winter coming soon.  Or if you have a 2.5" level and the 285/55/22, are you able to fit in a standard 7ft garage opening?

 

 

 

 

Posted

I don’t have a measurement, but my 15 Denali with the same setup cleared without any problem. My current 18 Denali with a 3 inch and 35/12.50/22’s also clear without any issues. 

0DC9474D-C5C4-4697-A61E-3CCF7DBF9B46.jpeg

  • 1 month later...
Posted

For everyone that has had some time with LT285 55 22s (specifically terra grappler G2)... How do you like the ride quality? Is the 10 ply tire that drastic? How is the "seat of pants feel" for power loss from the heavier tire? Is the ABS sensitive over bumps? What tire pressures are you running?

Also on a side note... Has anyone experienced rubber cracking with their nitto G2s? Only ask because I had a set of "G1s" from 2012 and the cracking was unreal.

Sorry for the rant.

Thanks!

Sent from my SM-G950U using Tapatalk

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