Jump to content

Rear blocks and Timbrens

johnhankel

By johnhankel
in Towing, Hauling & Hitches

Recommended Posts

johnhankel Enthusiast

johnhankel

Posted
Posted

I am putting the ReadyLift front leveling kit and the 2.25" rear blocks on my truck soon. I will still have a slight rake to the truck. I know some of you here have Timbren rear load levelers on your trucks.

 

Does anyone have these with added height in the rear? I assume I would have to add some kind of spacer to the Timbren to get it to the recommended 1" space between it and the axle.

 

I want to try and minimize the sag I get when hauling a car trailer. However, I do not want the factory rake put back in the truck that would be present if I went with a 3" block.

 

Can anyone help answer the questions? Thanks....

  • 2 years later...
Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

I am putting the ReadyLift front leveling kit and the 2.25" rear blocks on my truck soon. I will still have a slight rake to the truck. I know some of you here have Timbren rear load levelers on your trucks.

 

Does anyone have these with added height in the rear? I assume I would have to add some kind of spacer to the Timbren to get it to the recommended 1" space between it and the axle.

 

I want to try and minimize the sag I get when hauling a car trailer. However, I do not want the factory rake put back in the truck that would be present if I went with a 3" block.

 

Can anyone help answer the questions? Thanks....

I know this is an old post, but I have the same question, so I'm bumping it up to the top. Any input?

johnhankel Enthusiast

johnhankel

Posted
  • Author
Posted

I ended up solving the problem by making a spacer to fit in between the Timbren and the mounting area. I will try to get a picture this evening of the spacer.

 

I took them off of the truck last fall since I don't normally pull my trailer around during the winter. But I will putting them back on here soon.

 

I did buy longer bolts also since I added in the 1" spacer. I will try to find those bolt lengths tonight as well.

Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

Awesome. Thanks for the reply. So, do you think it would have squatted too much before they starting working, if you hadn't made the spacer? Why did you take them off? Was the ride different than stock?

  • 2 weeks later...
johnhankel Enthusiast

johnhankel

Posted
  • Author
Posted

It definitely would have been much lower in back, since it would have to drop 2" until it hit the Timbren.. I take them off in the winter since it does make the ride some what harsher. With the poor city roads we have, the axle would hit the Timbren while bouncing around on the street. It does not take too much of a bump to make these truck move an 1" up or down..

 

The instructions that come with the Timbren says there should be an inch of space when sitting, which is what I have.. But it just seems the rough road moves the axle up and down more than normal or something...

 

Here are a couple of pics of the spacers...

Timbren Spacer 2

Timbren Spacer

 

Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

It definitely would have been much lower in back, since it would have to drop 2" until it hit the Timbren.. I take them off in the winter since it does make the ride some what harsher. With the poor city roads we have, the axle would hit the Timbren while bouncing around on the street. It does not take too much of a bump to make these truck move an 1" up or down..

 

The instructions that come with the Timbren says there should be an inch of space when sitting, which is what I have.. But it just seems the rough road moves the axle up and down more than normal or something...

 

Here are a couple of pics of the spacers...

 

Cool man. Thanks for the pics and the reply. :cheers:

 

So just a 1" spacer and a 1" longer block should do the trick then....if I decide to go the timbren route...

johnhankel Enthusiast

johnhankel

Posted
  • Author
Posted

Just thinking about this some more.. If you have a waterjet or plasma cutter, just make a solid 1" thick round out of aluminum... no rust...

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

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