Jump to content

Recommended Posts

Posted

I'm in the process of swapping a ff 14 bolt axle out of a 2004 2500hd. My truck currently has the weak 10 bolt axle with drum brakes. My question is, will I have a problem with my brakes because the 14 bolt has disk brakes? There are aftermarket kits for the 10 bolt axle to convert it to disk and in these kits it doesn't say anything about needing a special master cylinder or proportioning valve. I'm also unsure how the brakes are praportioned on my truck. I haven't found any prop valves on it.

  • Like 1
Posted

So do you think I would be safe running the disk brakes with no other modifications? I looked at some abs pumps on ebay and it looks like the 1500 and 2500HD in 2005 are the same part number. But that's just based on the sellers info.

Posted

What sre you doing for the front since front and rear are different bolt patterns if you swap. And honestly i would either swap just your brakes or upgrade. ABS is not your only task to overcome with the swap. Different pinion yoke and length so a custom driveshaft is needed.

Posted

Chris is right, that swap is a lot more in depth because of the 8 bolt rear vs the front 6 lug, as well as drive shaft length and pinion angle issues. Your rig will definitely be capable of using the discs because the abs module will adjust to the new "resistance" of the discs. There was a thread on here that someone only upgraded brakes not the whole diff assembly and everything worked fine, well actually improved over drums. One thing i am not sure of is that you may need to get a computer hooked up to bleed the abs module if you don't prevent the air getting to it.

Posted

I'm having custom 6 lug hubs made for it and I measured the pinion length and it's about a quarter inch longer than the 10 bolt so im hoping ill have enough room in the slipyoke. And i also bought a 1350 to 1410 u joint to connect the drive shaft to the diff. If the abs will auto adjust that would be bitchin. I will post detailed pics when I do the swap

Posted

Custom wheels needed too. Stock wheels wont clear the hub on a full float

Posted

The custom hubs will have a smaller center section. So I will have to have the axle shafts turned down at the mating surface to match the new hubs. Then any 6 lug wheel will work

  • 4 weeks later...
  • 1 month later...
  • 1 year later...
Posted

Your swap looks killer. What brake rotors did you use? Anything 6 lug that's disc?

 

How much and where did you have your hubs made?

 

I have a 75 k10 and I have an 04 2500hd 14 bolt I want to put in, but I want to retain 6 lug.

 

Thanks in advance

  • 3 years later...
Posted

Hi I'm Steve or scoob new to the forum but have been looking at converting my 2005 gmc sierra 4x4 1500 to a full floating rear axle just like chevelle212 but wanted to know what brake rotors u ordered or what vehicles style those rotors come from?

Posted

Also if u could tell me was this rear axle out of a gas 6.0 2500hd?excellent job on the conversion. Any other parts needed for the conversion would be a big help. Did u have any problems after w vibrations or braking issues ?

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