Jump to content

Recommended Posts

Posted

They're working great, for a direct replacement using stock springs they are light years better than Ranchos. The 6112 should be awesome. The Toyota guys love them and say they're comparable to KINGS/ICONS

Sent from my SM-G950U1 using Tapatalk

Do we have any idea when they will release those?

Posted

Do we have any idea when they will release those?

They expected to date has come and gone. Who knows ?

 

Sent from my SM-G950U1 using Tapatalk

  • 2 weeks later...
Posted

Quick question..

2014 sierra crew cab

I got 275/60/20 Discoverer AT/3 and doing the Billstein level on top notch.

Can i get the tires mounted first before the shock install? Just wondering if it will rub hard untill i can get the shocks installed the next day or so.

Posted

According to the "Technical CSR" I've been emailing about these for the last few months, the current status is "They are due in anytime now, waiting on spring coating."

  • Like 1
Posted
Just now, RHStansbury said:

According to the "Technical CSR" I've been emailing about these for the last few months, the current status is "They are due in anytime now, waiting on spring coating."

 

They always have one reason or another, but hopefully that is the truth. They have been due since last year. I will believe them when they arrive to our loading dock!!!

Posted
On 10/23/2017 at 5:24 AM, Ozer said:

Quick question..

2014 sierra crew cab

I got 275/60/20 Discoverer AT/3 and doing the Billstein level on top notch.

Can i get the tires mounted first before the shock install? Just wondering if it will rub hard untill i can get the shocks installed the next day or so.

 

U-Turns will be hard. But if its just for a day I think you will survive.

  • Like 1
Posted

I just read a thread on the Bilsein bump that occurs after installation of the shocks. It seems the top plate does not get tightened down all the way unless you use a washer or spacer under the shock top nut. I have been having some noise in the front end since the swap over washboard sections in the road. I checked this afternoon when I got home from work and found my top plate loose enough to move. So I did some searching and found the thread mentioned above. The bad part about trying to correct tbis is you gotta almost stand on your head to correct it. Maybe not tomorrow night but by the weekend I will have done something about it anyway. I'll link the thread here tomorrow.

Posted
I just read a thread on the Bilsein bump that occurs after installation of the shocks. It seems the top plate does not get tightened down all the way unless you use a washer or spacer under the shock top nut. I have been having some noise in the front end since the swap over washboard sections in the road. I checked this afternoon when I got home from work and found my top plate loose enough to move. So I did some searching and found the thread mentioned above. The bad part about trying to correct tbis is you gotta almost stand on your head to correct it. Maybe not tomorrow night but by the weekend I will have done something about it anyway. I'll link the thread here tomorrow.
My Bilsteins set on the max lift were installed earlier this year so (living in the Midwest) this is first they've seen cooler temps.
On the expressway today the truck was really riding funny. Kinda like very small whoops so it felt like it was bouncing up and down really fast. ( I was going between 70 and 80 mph)Not like with out shocks.. It was very stiff feeling. I wrote it off as just being that section of highway combined with the trucks wheelbase.
Later I was on a totally different expressway and felt the same.
Anyone experience this? Would a spacer lift work better for ride quality with the shocks set at stock height?
Also Eddie 70, mine makes a light knocking/ rattle noise when going slow over terrain that makes the truck flex side to side. Nothing big.. Just driving across the yard will do it and I can't find anything lose.

Sent from my SM-N950U using Tapatalk

Posted

I went out to the garage tonight when I got home and checked everything really closely. The top plate was VERY loose. The best way I found to tighten the bolt was through the fender well. Hold the wheel well liner back, rotate the shock shaft so you can hold it with a small crescent wrench. Tighten the 16MM nut on the top of the shock until it is tight against the top plate and no more movement is noticed.

 

Read this thread for pics.

  • Thanks 1
Posted

I have driven approximately 175 miles since I did this the other day. This was the fix for mine. It may loosen up, but I can't imagine it would using the supplied nuts that came with the shocks. They are just a tad undersized and you have to use a wrench to run them down. However, if it does loosen, I will double nut it.

SO much better with them tightened down. The truck is almost quiet again and it has 92k miles. I am excited again!

  • Like 1

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

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