Jump to content

Recommended Posts

Posted

Rough Country 3.5 inch suspension lift. Tires are 305/70r17 BF Goodrich Mud-terrains. Wheels are Dick Cepek 17x9 with -12 offset. Minimal rubbing under full lock.

post-132849-0-62270900-1407196812_thumb.jpg

post-132849-0-47260600-1407196820_thumb.jpg

post-132849-0-77457100-1407196834_thumb.jpg

post-132849-0-62270900-1407196812_thumb.jpg

post-132849-0-47260600-1407196820_thumb.jpg

post-132849-0-77457100-1407196834_thumb.jpg

post-132849-0-62270900-1407196812_thumb.jpg

post-132849-0-47260600-1407196820_thumb.jpg

post-132849-0-77457100-1407196834_thumb.jpg

post-132849-0-62270900-1407196812_thumb.jpg

post-132849-0-47260600-1407196820_thumb.jpg

post-132849-0-77457100-1407196834_thumb.jpg

  • Like 1
Posted

Just got a question for all you lifted guys do you still have the problems that are described in the "Shake or vibration" thread in the problem section?

 

My Trail Grapplers hum like hell and vibrate the wheel around 40-50mph and sometimes while braking after i did the Zone 6.5" kit. It isn't as bad when the tires are cold and the psi is down. When they heat up on a hot day the issue kicks in. I am going to have them check my alignment again, but I already decided to move to the Open County ATs and have them on order.

Posted

 

My Trail Grapplers hum like hell and vibrate the wheel around 40-50mph and sometimes while braking after i did the Zone 6.5" kit. It isn't as bad when the tires are cold and the psi is down. When they heat up on a hot day the issue kicks in. I am going to have them check my alignment again, but I already decided to move to the Open County ATs and have them on order.

 

That's weird youre having those issues with the trail grapplers because mine hum very little out of all the mud tires I've owed and no vibration what so ever and ride just like my stock tires did except at coming to a stop and going from a dead stop you can feel the knobs in the tires

Posted

 

That's weird youre having those issues with the trail grapplers because mine hum very little out of all the mud tires I've owed and no vibration what so ever and ride just like my stock tires did except at coming to a stop and going from a dead stop you can feel the knobs in the tires

 

It's got to be the alignment then unless there is something not right with the lift install. I didn't experience anything with them before the lift other than what you mentioned.

Posted

Ya nitto terra grapplers 950, 9000 miles on them.

Posted

Wish they made a 4" kit for the 2 wheel drives!

CST Suspension FTW. They have a 3.5-5" kit for the 14's

  • Like 1
Posted

CST Suspension FTW. They have a 3.5-5" kit for the 14's

 

LOL @ $1,200 for a 4" lift with no shocks. For that kind of money, there's a shop here locally that will do a 6" lift WITH shocks for $1,299 INSTALLED. Or if one wanted to go with a less expensive alternative, just do a 2.5" level and a 1.5" body lift like I did and total cost is around $250.

Posted (edited)

 

LOL @ $1,200 for a 4" lift with no shocks. For that kind of money, there's a shop here locally that will do a 6" lift WITH shocks for $1,299 INSTALLED. Or if one wanted to go with a less expensive alternative, just do a 2.5" level and a 1.5" body lift like I did and total cost is around $250.

They are high but not extreme. I paid more for a Camburg 2.5" level kit on my 2013. Also you don't need shocks with that kit since it relocates the hub; the other suspension components stay the same. It all depends on what you want, if you aren't looking for performance you can do the same with a level and body lift for 350$. He was mentioning BDS, this is cheaper than BDS. You buy the coilovers then you can get the 5" and have the best of both wprlds. You get what you pay for. Edited by CAtaylor
Posted

They are high but not extreme. I paid more for a Camburg 2.5" level kit on my 2013. Also you don't need shocks with that kit since it relocates the hub; the other suspension components stay the same. It all depends on what you want, if you aren't looking for performance you can do the same with a level and body lift for 350$. He was mentioning BDS, this is cheaper than BDS. You buy the coilovers then you can get the 5" and have the best of both wprlds. You get what you pay for.

I was referring to rear shocks which the CTS kit does not include.

Posted

I was referring to rear shocks which the CTS kit does not include.

Yep, I completely jumped over that. You are correct on that one.

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   5 Members, 1 Anonymous, 1,741 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...