Jump to content

Recommended Posts

Posted

I am looking to lower my 08 Sierra Denali AWD, and I was just wondering if anyone has any experience with this. I've heard changing the right height of an AWD truck may cause vibrations. I am thinking of doing a 2/4 inch drop. Anybody had any or know of any problems with this? Side note: My plans are to use lowering springs up front and drop shackles and block removal in the rear. Probably just going to run stock shocks if they will still fit.

Posted (edited)

Not sure about AWD, but there are a few 4x4 guys with 4/6 drops. Our body style of trucks sit up so darn high a 2 inch drop is almost unnoticeable.

 

I would recommend drop spindles vs. springs.

 

 

08GMC007_zpsa2a49b0e.jpg
08GMC006_zps92099294.jpg
08GMC008_zpsa9e8448c.jpg

Edited by DoMDrty
Posted (edited)

PM NORCAL SS. He does a lot of drops. He does a lot of AWD Silverado SS's. Here is a link to his profile

http://www.gm-trucks.com/forums/user/110073-norcal-ss/

 

I see you have one post. You need to have I think 5 or 10 posts to PM someone. I sent him a PM on another site to look at this thread.

Edited by chawkins6789
Posted

The 4wd guys wouldn't have a problem with vibration because on the highway your front drive section is not engaged. On my AWD it is always engaged, so I am worried about what the change in pinion angles up front will do. I agree with you on the springs, also. I might even just go with the belltech adjustable struts up front, since i need new shocks and struts anyway, and keep the stock springs.

Posted

I edited my post. I hope he replies here. He has experience in lowering AWD trucks and Trailblazer SS's

Posted

ive done many of them

 

Front i would do belltech spindles and rear belltech sp shocks

then djm 4-5 inch flip kit

 

Any quetsions just holler i deal with both djm and belltech daily

Posted

Thanks, I don't know if you came because my message on silveradoss.com but Thanks for the help over here

Posted
no prob

 

You are the expert

 

Sent from my DROID RAZR MAXX using Xparent Red Tapatalk 2

 

 

Posted

Would the belltech lowering struts work ok for the 2" drop in the front, or do I need to go with drop spindles to keep a good ride?

Posted

I want to do 2/4, but I already have 2" belltech drop schackles in the rear to level the truck. Just checking prices, my cheapest route is belltech lowing struts up front to lower it 2", just the leaf spring flip brackets to drop the rear 2 more inches (if I can get those by themselves), and then belltech sp shocks in the back. Then I will end up with a 2/4 drop and new belltech shocks front and rear. But I don't want to scrifice the ride if the lowering struts set to -2" are going to make the front to stiff.

Posted

Spindles wont screw your ride. The suspension remains the same. He knows what he is doing with AWD trucks. He does Silverado SS's and Trailblazer SS's all day long. I would go along with his suggestions and being a forum member he may cut you a little deal on it. A lot of guys on another forum I'm on buy their stuff from him

Posted

ok heres the issue with the trucks different ones used different front springs. Some of the trucks 07 up ive seen sit 3/4 inch higher than others due to the springs they used at the plant.

 

Heres what i do on all the kits i install before anything

 

1) measure from ground to fenderlip in rear

2) make sure you still have the lifting block in rear still in

 

Tell me that and I can dial in the exact kit you should go with. For 2 inches in front id roll the belltech spindles

 

Here is my new escalade 2.75 drop front (spindles and my custom strut mod) and rear cromoly control arms and beltech kit with djm swaybar no issues at all

20120916_125433.jpg

Posted

ok, here's what I got. 36.5" in the front, 37.75" in the rear. I already have Belltech 2" drop shackles in the rear to level the truck (As you can see it really didnt level it). Ultimately, I want to end up with about a 2/4 drop with new struts and shocks front and rear (I still have the stock shocks and I have 115,000 on the truck). I am going to upsize my wheels to 22" with 285/45 tires, and I want to add a sway bar kit to the rear (belltech or DJM, whatever i can find a better deal on). I appreciate your help, Norcal. You seem like you know your stuff, and your trucks look Great!

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   6 Members, 0 Anonymous, 1,450 Guests (See full list)

  • Latest Articles

  • Posts

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
    • $2.20 E-85 down from $2.59 Around $3.80 for regular and about $5 on average for Premium.  Propane $3.99 a gallon. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...