Jump to content

Recommended Posts

Posted (edited)
On 3/7/2021 at 5:06 PM, Alpha7 said:

Don’t bother with leaving kit. 
 

every shop I went to said that everyone that put a leveling kit on there 2500 hates it to either leave it as is and just put bigger tires if you want that can fit or put an actual suspension lift kit. One of the shops straight up just said they wouldn’t even do leveling kit on 2500s that it was just a waste of time and money.  
 

 

This is 100% false!  The shops that say " oh i'd never run a leveling kit" most likely only deal with people that want to spend $300-$500 on a kit and then expect it to ride the same or better. I was that guy a few years ago. I had a 2" leveling kit on my last truck that cost like $150 bucks and it rode like garbage.

 

But, I can tell you that my Cognito set up rides like a freakin dream and i'd put the ride quality of this kit up against any "proper" lift kit on the market. After my leveling kit nightmare, I spent 5k on my last truck suspension and it had Fox coilovers with the external resi's and that kit rode way better than the leveling kit, but it rode like a log wagon compared to the leveling kit on my 2500.

 

There's a reason why a Cognito leveling kit runs north of 2k with the Fox upgrade vs all the other's, and its because of the amount of R&D they put into their kits. You get what you pay for. If someone is cheap enough to skimp on the suspension of their 60-80k truck, then they will get exactly what they deserve when it comes to the ride quality.

Edited by gSwift
Posted
On 3/8/2021 at 7:22 AM, CobraEatr said:

Swift, your truck is the reason why I want the Cognito premier kit. I saw it on this board last week while searching leveling kits. It looks awesome. That’s the exact look I’m going for. 

Will you be running your stock wheels as well? And 37's or 35's? I had 37x12.50's but keep in mind that I had to run a 1" hubcentric spacer in order for the inside of my tires to clear my Cognito UCA's when at full lock. If you plan on aftermarket wheels then you'll want to do your research on an offset that will clear everything.

 

Good luck and post pics when its done.

Posted
25 minutes ago, gSwift said:

Will you be running your stock wheels as well? And 37's or 35's? I had 37x12.50's but keep in mind that I had to run a 1" hubcentric spacer in order for the inside of my tires to clear my Cognito UCA's when at full lock. If you plan on aftermarket wheels then you'll want to do your research on an offset that will clear everything.

 

Good luck and post pics when its done.

I’m going to run stock wheels. I saw today in the “how have you modded your truck” thread that you used spacers. I was disappointed when I read that because I would prefer not to use spacers. I like the tires tucked in as much as possible. I wanted to go with 37x12.50x20 Nitto Trail or Ridge Grapplers. 
 

If you have any more pics of your truck I would love to see them. Any and all angles. I may end up just using the spacers. How bad was the tire/UCA rub at full lock before you added the spacers? 

Posted
On 3/9/2021 at 9:02 PM, CobraEatr said:

I’m going to run stock wheels. I saw today in the “how have you modded your truck” thread that you used spacers. I was disappointed when I read that because I would prefer not to use spacers. I like the tires tucked in as much as possible. I wanted to go with 37x12.50x20 Nitto Trail or Ridge Grapplers. 
 

If you have any more pics of your truck I would love to see them. Any and all angles. I may end up just using the spacers. How bad was the tire/UCA rub at full lock before you added the spacers? 

It still stayed pretty tucked. Honestly I think it made the stock wheel and 37" tire combo look even better. I've always been anti spacer too, but with this one being hubcentric I didn't have a single vibration or anything. There was another user here that tried to use a cheaper spacer and it vibrated, he then swapped to the one I use and his vibrations stopped.  I did have to trim about a 1/4" off my factory wheel stud, but the last 1/4" isn't threaded anyways so you're not losing any useable thread.

 

 

CE6535DF-20F4-436B-A3D2-2AFCD5F880F1.jpeg

Posted
4 hours ago, gSwift said:

It still stayed pretty tucked. Honestly I think it made the stock wheel and 37" tire combo look even better. I've always been anti spacer too, but with this one being hubcentric I didn't have a single vibration or anything. There was another user here that tried to use a cheaper spacer and it vibrated, he then swapped to the one I use and his vibrations stopped.  I did have to trim about a 1/4" off my factory wheel stud, but the last 1/4" isn't threaded anyways so you're not losing any useable thread.

 

 

CE6535DF-20F4-436B-A3D2-2AFCD5F880F1.jpeg

Wow, that looks really good. Before you added the spacer, how bad was the rubbing? Was it something you could have lived with? 

Posted
16 hours ago, CobraEatr said:

Wow, that looks really good. Before you added the spacer, how bad was the rubbing? Was it something you could have lived with? 

The inside of the tire rubs the Cognito control arm at full lock real bad, the rubbing on the liner was minor and easily fixed with very little trimming. But the tire/control arm rub was so bad that the inside of the Ridgegrappler would grab the metal control arm and almost bring you to a full stop. Theres no way around running 37x12.50's on the factory offset wheels and the Cognito UCA's unless you run the spacer. 

 

Cognito told me from the beginning that it wouldn't work but I figured i'd risk it and find a solution. If i had it all to do over again I wouldn't change a single thing. The ride quality is truly unbelievable and everyone that rode in it couldn't believe how well it rode. 

Posted

Actually, Nitto makes a 37x11.50 which actually may give you all the room you may need. I didn't know they had a 11.50 until I had already bought my 12.50's. But I still think the spacer bringing the wheel out some completed the look

Posted
On 3/12/2021 at 7:11 PM, gSwift said:

Actually, Nitto makes a 37x11.50 which actually may give you all the room you may need. I didn't know they had a 11.50 until I had already bought my 12.50's. But I still think the spacer bringing the wheel out some completed the look

That’s a great idea. Thanks swift! Maybe the 1” difference in width will keep the tires from touching the UCA. 

  • 3 years later...
Posted

Hi, thanks for all the detail in this thread. I wanted to ask your opinion on shocks. I’m pulling the trigger on a congnito level kit for a 2024 2500. My question is do you think the ride is as good as factory with the Fox 2.0s or are the Elka or Fox 2.5s worth the upgrade? This is only for aesthetics. Very limited off roading. I do tow often. Thanks! 

Posted (edited)

My 2 cents on levelling kits/reindexed keys...

 

On my 2004 2500HD I had installed them, only to realize when I bought & towed a travel trailer (5000#) that it made the rear squat. Even though the tongue weight was 500#, I got a WD hitch to level that truck & my 2011 truck. When I got my 2017, It appeared that the WD hitch wasn't req'd. The truck didn't squat w/ the load (I still use a sway control).

Edited by revrnd
Posted (edited)

Never understood why people level trucks that tow or actually use their truck as a truck. There is a rake for a reason.

 

I use a WDH with my 6500# trailer that has 800# of tongue weight.

Edited by bruceb58
  • Like 3
Posted

Shocks will do nothing to soften the ride of such a heavily sprung truck unless you are fully loaded or towing heavy. Those monster springs need to compress before the shock can dampen the compression and rebound. These trucks have payloads of 3,000+lbs. Those springs aren't easily compressed by potholes and speed bumps.

 

As far as a factory driving level kit, the king of kings is the ZR2 suspension swap. Pros are factory suspension geometry, fit 37s, and low cost parts. Cons are it's not for wrench novices and consists of the same amount of work as doing a full 4"+ lift kit for a mere 1.5".

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
  • 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   3 Members, 0 Anonymous, 1,554 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...