Jump to content
diesel 3.0

diesel 3.0


Open Club  ·  279 members

diesel 3.0

Level/lift kit suggestions??

jeeper2000

By jeeper2000
in Topics

 Share

Recommended Posts

jeeper2000 New Member

jeeper2000

Posted
Posted

I have a 2020 Chevy 1500 babymax and looking for a level/lift kit. Would preferably like to take it to around 2 or 3 inches and hopefully keep the factor 20 inch wheels. Got stock 275/60/20 at the moment and would like to go bigger as well. I've done done research and it seems like many of the coilover or snap ring lift shocks offer less lift to the diesel engine variants. What are y'all running lift wise and what size tires are you running? 

  • 1 month later...
MattsNuked New Member

MattsNuked

Posted
Posted

I'm in the process of getting a 4" Ready Lift and some 34" tires. In Phoenix I've had some issues with shops figuring out what will work for the 3.0 since a lot of manf's don't list them and don't want to put on something that they can't confirm fitment. The Lift Shop and Midway Chevy seem to be the most knowledgeable. 

  • 2 weeks later...
paxamus Enthusiast

paxamus

Posted
Posted

I went with the Cognito 3" coilover kit and I am super happy with it! I mean, I would love to lift it 5-6 inches and run 37's but I cant do that as I drive almost 55 miles daily.  The Cognito coilover's (Fox shocks) ride great and I kept my stock wheels and went with 35x11.50- I did need a 1/4" spacer on the front and did some minor trimming, but the ride and droop on those coilovers is ridiculous!  When I went to rotate my tires my big floor jack just barely got the fronts off the ground because of all of the travel on the suspension

  • 2 weeks later...
RST from TN Enthusiast

RST from TN

Posted
Posted

I did the rough country 3.5, I had to change my wheels to do the 35X12.50 however I did have to manipulate my fender liners to eliminate the rubbing. 1886995932_Lift.thumb.jpg.334aabf382ad1671a6bd4b371422fd1e.jpg1.jpg.c964c11ab31028ecb7513c18cb5f9252.jpg

 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Chuck FB
      Joke Thread

      By Chuck FB · Posted

      This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...