Jump to content

Recommended Posts

Posted (edited)

Hi all,

 

This is a friendly warning regarding Eibach's PRO-TRUCK Sport Shock for the 2019+ Silverado 1500's (Part #: E60-23-032-01-10). In short, it increases suspension travel by ~3" which binds the upper ball joint.

 

I had previously used Eibach's PRO-TRUCK line of shocks on a 2016 Colorado as a Bilstein 5100 alternative when looking to get rid of the stock rake. Eibach's product gains lift the same way as Bilstein by using an adjustable c-clip to increasing pre-load with the benefit of firmer valving. While Eibach's installation instructions are lacking compared to Bilstein, the Eibach struts performed well and I didn't have any issues .

 

Today, I finished installing the Eibach onto my 2024, Silverado LT, Z71 which was straight forward. However, I've come to conclude the product could be dangerous by increasing travel by ~3", exceeding the safe angle of the upper ball joint at full extension. My findings were:

  • The maximum extension of the stock Rancho strut was 19 5/8". This was measured from the lower mounting bracket to the bottom of the threads on the strut shaft as this is where the upper mount sits - first photo/ #9669
  • The maximum extension of the Eibach strut was 22 5/8" when measured in the same manner - second photo/ 9675.
  • For a comparison between the stock Rancho and Eibach strut, look at third photo/ 9669.

 

I've gathered from posts such as this one and this one, increasing the travel length more that 2" puts the upper ball joint past it's maximum angle. Eibach's design of increasing travel by 3" is the equivalent of installing a 3" spacer onto of the stock Rancho strut, stressing the stock upper ball joint at full extension. Nowhere on Eibach's product page or instructions does it indicate this product needs aftermarket upper control arms to be safe or that the travel length was increased by 3" over stock.

 

In light of this, I've ordered the Bilstein 5100 to replace the Eibach's (PN: 24-293297). The data sheet shows the strut has a full extension length of 21.65". Since I do not have the strut yet, I do not know if this measurement includes the threads on the shaft or if this is to base where the upper mount sits. Regardless, this means Bilstein's strut is either the same length as the stock Ranch strut or, introduces 2" of suspension travel which falls within the ability of the stock UCA's.

 

By no means do I claim to be an expert as I am new to the T1XX platform, but these principles were well documented when I owned a GMT360 and GMT 31XX. 'In strut' lifts are considered safe since you do not increase the maximum extension of the strut, meaning you do not increase the maximum angle of the upper ball joint. 'In strut' lifts increase the preload to gain lift. 'Outside strut' lifts are easier to install but become dangerous at a point since it will increase the maximum extension to a point where the upper ball joint becomes the downward limiting factor. After repeated instances of this, the upper ball joint can fail by sheering or popping out of the socket.

 

I welcome any and all questions, comments, or feedback as I learn the T1XX platform.

 

Kind regards,

Ac3 (Ace)

 

 

 

IMG_9672.JPG

IMG_9675.JPG

IMG_9669.JPG

Edited by Ac3
  • Ac3 changed the title to Warning: Eibach PRO-TRUCK Sport Strut
Posted

Why not just get aftermarket upper control arms? They are a known weak point. Apparently enough so that with the introduction of the ZR2 they changed the upper control arms on them and the same part number is used on the Trail Bosses. Any lift beyond the 2" stock height should include new upper arms with corrected ball joint angles.

Posted

Great point.

 

In my personal experience, I find aftermarket bushing don't last as long in comparison to the sealed OEM's. My use case is mild - my vehicle is 80% pavement with the other 20% being my father's farm or forest service roads. Rarely am I doing serious off-roading and when so, rarely at speed.

 

The Bilstein 5100's came in today and the travel is only a 2" longer compared to the stock Ranchos, 1" shorter than the Eibachs. Based on the historical OEM Trail Boss UCA PN and the general online concessions, I should be okay with this setup.

 

Cheers,

Ac3 (Ace)

Posted (edited)
On 7/7/2024 at 8:27 PM, Ac3 said:

...Eibach's product gains lift the same way as Bilstein by using an adjustable c-clip to increasing pre-load...

...'In strut' lifts are considered safe since you do not increase the maximum extension of the strut, meaning you do not increase the maximum angle of the upper ball joint. 'In strut' lifts increase the preload to gain lift. 'Outside strut' lifts are easier to install but become dangerous at a point since it will increase the maximum extension to a point where the upper ball joint becomes the downward limiting factor. After repeated instances of this, the upper ball joint can fail by sheering or popping out of the socket.

None of these lift styles increase or change the amount of "pre-load" on the springs. You can verify this by measuring the height of the spring with and without the lift installed, assuming you reuse the same spring.

 

There are only two ways with these lifts to increase spring pre-load:

One, you put so much "lift" into the system that the strut assembly and/or spacers pushes the upper control arm so far down that it is forced against the droop limit stop at all times. 

 

Two, a poorly engineered strut, where the strut piston is not long enough or able to extend out enough to make up for the higher spring perch location via the c-clips. 

 

These styles of lift work by moving the two strut mounting points further away from each other, via spacers at the top of the assembly or bottom, what you seem to refer to as 'outside strut' lifts. The 'inside strut' lifts are doing the exact same thing by moving the bottom spring perch up and down on the lower strut shaft.

 

Regardless, your warning about upper control arms and ball joints is well merited.

Edited by asilverblazer

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,858 Guests (See full list)

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...