Jump to content

Recommended Posts

Posted

Hi ya'll i am looking at buying a 2020 3500 HD, and the dealer has a off the lot truck I really like but it has the heavy duty front spring package on it, without the snow plow prep package. Does anyone have experience with this option? and will it make the front end ride like a stone boat? I cant take it for a test drive cause it is not at the dealership and I would like some feed back to exactly what this option does for the truck. Even the GM website has very little insight on this option.

Posted

Never seem it without the snow plow prep package.

 

Maybe go find one that has it and drive it...its gotta be a bit firmer but im sure its palatable.   My 3500HD doesnt have it and drives like a dream.  

Posted (edited)

F60 - heavy duty front suspension raises the torsion bar and front GAWR to the next size up.  On the majority of 4wd diesels, heavy front and snow plow prep (VYU) are the same front suspension with raising front GAWR from 5600 to 6000 lbs.  On majority of 4wd gas, heavy front goes up one torsion bar whereas snow plow prep goes up two or three sizes.  On gas trucks, you do get a different front shock with more force in it.  Most 4wd gas with go from 4800 Front GAWR to 5200 with heavy front.

 

The ride hit is relatively small on both gas and diesel trucks with heavy front.  Most of the change is in your rolling isolation where the higher spring rate reads the road more.  

 

#iworkforGM 

Edited by MTU Alum
  • Like 1
  • Thanks 2
Posted

I drove a loaded 2500 HD diesel without the heavy duty spring and then with it. It feels just slightly stiffer with it. The one without was a Denali. The one with was an AT4. Both fully loaded. Not sure if there are any other differences to suspension elsewise.


Sent from my iPhone using Tapatalk

  • 7 months later...
Posted

I just need the part number so the dealer can order and install the upgraded torsion bar to raise the FGAWR from 5600 to 6000.

The F60 was supposed to be ordered on the truck but they missed it and have promised to fix it. I am not concerned with whether I can tell the difference in the ride, it is the roll factor with a camper in the bed that is of concern.

Thanks

Posted

Note, just changing parts doesn't change the number on the sticker in your door jam, which is what your truck can legally manage.

  • Like 1
Posted

I am well aware of the sticker issue. The camper weight is under the weight indicated on the sticker. I want the truck to be as I ordered it and for the money I spent on it, the dealer owe’s me that. Not to mention it took six months to get it. 
Again, just looking for the correct part number. Thanks 
 

Posted

Thank you MTU for the part numbers and thanks to the rest of y'all for additional comments. Now to get to work.

Posted

how about part numbers for the standard 3500 torsion bars?

I am looking at a 3500 and it has the camper package on it. don't necessarily need or want the increase capacity or stiffer ride

thanks

  • 1 month later...
Posted (edited)

Does the hd spring package make it sit higher in the front on a gas 2500? I may have made a mistake ordering them thinking it was for towing a camper and I’ve already got the dealer going to install a gm 2” level as well before I pickup the truck. 

Edited by west_dt

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
  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...