Jump to content

Looking for a Mid Travel system that fits my needs


JasonAVGuy

Recommended Posts

Posted

Hey everyone I could really use some help with my suspension. I was playing around on a millings pile the other day and I am really unhappy with the travel of my front suspension. I have looked at a ton of kits and feel I need some help and opinions of others. I use my truck every day on and off road. I tow a good bit and it is my daily driver. I would like to keep my 17in gm rims with 285/70r17 and also be able to put my stock 18in rims on the truck. I'm looking for a kit that gives me more suspension travel and 2-4 inches of front lift. I also want to maintain the rear rake because with my decked system and tools in the bed my truck sits level. Being able to still tow without issues is a must for me and maintaining drivability is important. I do not want to add front spacers or just level the truck my goal is for more travel and more front bumper ground clearance.

 

Truck On rocks

Suspension Flex 3

 

Posted

What I'd recommend is what I'm doing to my truck, I'm getting the Icon suspension kit, it's a longer than stock travel suspension and since it's a coil over in the front it's adjustable from 0-3" of lift, from everywhere I've looked it's going to give you the best daily able set up and is going to fit all my needs which are much like yours, the only difference being mine has 20's, if you want to maintain a bit of rake to be able to put stuff in the back and tow I'd recommend adding a leaf in the back, it's what I did and it added the right amount of rake. These trucks look nose high when they are perfectly level so that inch or so of lift the leaf adds makes it look level

 

 

Sent from my iPhone using Tapatalk

Posted

What I'd recommend is what I'm doing to my truck, I'm getting the Icon suspension kit, it's a longer than stock travel suspension and since it's a coil over in the front it's adjustable from 0-3" of lift, from everywhere I've looked it's going to give you the best daily able set up and is going to fit all my needs which are much like yours, the only difference being mine has 20's, if you want to maintain a bit of rake to be able to put stuff in the back and tow I'd recommend adding a leaf in the back, it's what I did and it added the right amount of rake. These trucks look nose high when they are perfectly level so that inch or so of lift the leaf adds makes it look level

Sent from my iPhone using Tapatalk

Thank you! I will take a look at the Icon kit. I am planing on adding helper springs in the back as is so I may end up adding a set of rear blocks to help. My decked system adds about 500 pounds of constant weight.

Posted

You could go with the bajakits chase kit, it includes king shocks and UCAs, deaver springs with bajakits shackles are awsome.

 

Im not sure on the amount of travel for the front with the chase kit but i get 12" on my bajakits prerunner kit with 4x4. I think its 14" on 2wd

 

The chase kit allows you keep the swaybar and stock fenders for stock width

 

The prerunner adds like 3" per side so you will need fiberglass fenders.

Posted

You could go with the bajakits chase kit, it includes king shocks and UCAs, deaver springs with bajakits shackles are awsome.

Im not sure on the amount of travel for the front with the chase kit but i get 12" on my bajakits prerunner kit with 4x4. I think its 14" on 2wd

The chase kit allows you keep the swaybar and stock fenders for stock width

The prerunner adds like 3" per side so you will need fiberglass fenders.

Do you know if the chase kit adds any front lift? Also I can't seem to find out if you can keep the stock rims. Any thoughts on the chase kit vs the camburg kit?

 

https://camburg.com/shop/suspension/fox-chevy-1500-2wd-4wd-07-14-factory-2-5-kit/

Posted

It will lift the truck since youre bolting a longer coilover

 

Honestly i would go with bajakits over camburg, i feel camburg is more commercial and uses round tubing for the UCA

 

Bajakits is a sidebranch for brenthel industries, they race and build their own trophy trucks and all sorts of buggies.

 

It seems like camburg works with fox and bajakits works with kings, i guess its a matter of taste

 

Theres a guy here selling brand new bajakits UCAs

As for the wheels, i dont know on bajakits chase kit but on my prerunner kit i needed 4.75" backspacing, idk what stock wheels are

 

Camburg also requires 4.75"

Posted

It will lift the truck since youre bolting a longer coilover

 

Honestly i would go with bajakits over camburg, i feel camburg is more commercial and uses round tubing for the UCA

 

Bajakits is a sidebranch for brenthel industries, they race and build their own trophy trucks and all sorts of buggies.

 

It seems like camburg works with fox and bajakits works with kings, i guess its a matter of taste

 

Theres a guy here selling brand new bajakits UCAs

As for the wheels, i dont know on bajakits chase kit but on my prerunner kit i needed 4.75" backspacing, idk what stock wheels are

 

Camburg also requires 4.75"

 

Thanks! You bring up some good points. I never thought about the round uca's. I liked the idea of the camburgs because of the lift but I would rather have known quality. I guess I need to figure out if my wheels will work.

Posted

Both Baja Kits and Camburg have racing backgrounds. As far as Upper control arm build materials, it really comes down to preference weather you want to see tube or boxed. In this application there is no advantage/disadvantage between the two.

 

Both are going to give some form of lift, up to about 3"- The lift comes from the Coilover, the upper control arm eliminates ball joint issues from the added lift height and the uniball helps smooth out ride transition bump/full extension.

 

Stock wheels will work on both, but you will run into rubbing issues with an aftermarket size tire.

Archived

This topic is now archived and is closed to further replies.

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