Jump to content

Anyone know if a H2 rear sway-bar will fit an HD?


Recommended Posts

Posted

I've seen them mounted behind the axle and have heard they share the chassis with the HD's so could it be a salvage yard bolt on for my 01 2500 HD 4x4?

 

Vernon

Posted
I've seen them mounted behind the axle and have heard they share the chassis with the HD's so could it be a salvage yard bolt on for my 01 2500 HD 4x4?

 

Vernon

 

 

 

 

Well, The H2 uses a 14 Bolt SF rear axle and the HD uses either a 14 Bolt FF(10.5" Ring gear) or the AAM 1150(11.5" Ring Gear) depending on the engine, transmission combo. If the sway bar on the H2 bolts to the axle shaft tubes then I would say that it may not fit because the axle shaft tubes on the FF are larger than the SF. The H2 is also built on the SUV type chassis and not the HD which is a little different. The only thing the H1 and H2 have in common is the name. Take some measurements of the sway bar on the H2 and see if it will fit on your HD, you may be able to modify it. :jester:

Posted
hey vernon. i don't think the chassis is the same. i thought the h2 chassis is the same as a tahoe. you can get a rear swaybar through hellwig suspension but if you have an oversized exhaust (ie 4") it will hit. thats what happened to me.

Heathen

 

Thanks for your replys and you guys are very good at guesstimating. This board has got to be one of the best there is.

 

I had just spotted a set on Ebay and was hoping to get a quick answer before the auction ended. Well that didn't happen so I bought them before I knew, dang it, :jester: .

 

It so happened that the very next day on of my customers at the auto garage showed up to check on his Vette in his new H2. So I slid under neath with a pad and tape measure and took some notes.

 

First off, it's not a bolt on but the bar will fit around the rear end nicely. The main problem will be attaching the sway bar brackets to the axle tubes. The H2 uses the SUV style control arm set up with coil springs while the truck uses the leaf springs. The H2 sway-bar brackets are about 36" center to center and they bolt straight up in a conventional sway bar saddle bracket slightly to the rear of the axle tubes, against the bottom of the control arm brackets. On the truck rear end the shock brackets are 36" center to center. The P/S is in front of the axle and out of the way but the D/S is behind the axle and therefore it's bottom bracket is a factor in mounting this bar. The way this would be fitted is with some pre-fabbed leaf spring to axle tube mounting brackets. I've seen some that will fit the HD axle tubes on a Jeep DIY suspension parts web-site before. By welding or bolting leaf spring brackets flat side down in the spots where the sway bar saddles need to be you could use them as mounts, bolting them directly to the new brackets.

 

The end links are close (I don't have my notes here right now) to 9-10 wider. They bolt to the frame in standard ear brackets with a through bolt in the link. The frame widths are similar. This would be easy to adapt to the truck with some simple fabricated brackets either bolted or welded to the frame. It looks as if it would clear my spare at 265/75 and the custom 3" dual tail pipes.

 

This is all speculation at the moment, if I get to it I'll post the results.

 

Vernon

Archived

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

  • 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, 2,066 Guests (See full list)

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...