Jump to content

3/4 ton to 1 ton axle swap

riverhawk

Recommended Posts

Ranger Senior Enthusiast

Ranger

Posted
Posted

I don't see why it wouldn't bolt up directly as the chassis the same otherwise. The only differences I could think of are the driveshafts and maybe brakes. the 11.5" is usually paired with a Duramax or big block 8.1

Doug_Scott Senior Enthusiast

Doug_Scott

Posted
Posted

More selections of lockers available.

 

 

Is there a particular locker you are looking at? I can understand there are more to choose from, but, you only need the one.

 

I have zero knowledge of what either rear axle comes with, but, my concerns would be with brakes (diameter and type, interaction of ABS), parking brake (compatible mounts and activation method), suspension mounts (size and location), and pinion flange (for both correct u-joint, pinion angle, and length of driveshaft).

 

Do both axles have same bolt circle and number of studs? Are both rear axles full floating? Is the diameter of the hole in the middle of the rim the same size on both axles (are the wheels interchangable between the two rear axles)?

 

Based on my experiences, those are the immediate concerns I would have if I were doing this. I don't have the answers, but, those are the questions.

ATMINF Enthusiast

ATMINF

Posted
Posted

the GMT 800 3/4 and 1 ton chassis are the same. the spring packs are the main difference. I am not sure if the srw 3500 with the 6.0L came with a 10.5 or 11.5 14 both FF rear? The only thing I remember reading that made the difference if you had the 10.5 vs 11.5 was the 8.1 or Dmax as stated earlier.

riverhawk Enthusiast

riverhawk

Posted
  • Author
Posted

To start I thank everyone for your replies.To answer Doug, I want to use a detroit truetrac. For some reason a 10.5 is the only 14 bolt version they don't make. And yes both size axles use the same wheel. Both are full floaters. I know the later model 11.5 have bigger u-joints. But there's a adapter pinon shaft kit for that. The angles should be the same or atleast close enough. The drive shaft length will be different on 2 wheel models but I've got 4 wheel drive so I think it will be same length if they use the same xfer case. The brakes are'nt a problem. would just use the ones that came with the axle it came with. The only problem may be the leaf spring eye to eye length as ATMINF stated. I'll have to measure one. Thanks again.

Riverjet502 Enthusiast

Riverjet502

Posted
Posted

My '04 3500 srw with 6.0L came with the 11.5 inch, 14 bolt rear. Interchangeability should be no problem. Especially if you can find the whole donor truck to get y our parts from.

Prokopchuk_9 Senior Enthusiast

Prokopchuk_9

Posted
Posted
I don't see why it wouldn't bolt up directly as the chassis the same otherwise. The only differences I could think of are the driveshafts and maybe brakes. the 11.5" is usually paired with a Duramax or big block 8.1

 

You are correct sir. IMO should bolt up I would say...

Prokopchuk_9 Senior Enthusiast

Prokopchuk_9

Posted
Posted
My '04 3500 srw with 6.0L came with the 11.5 inch, 14 bolt rear. Interchangeability should be no problem. Especially if you can find the whole donor truck to get y our parts from.

 

Are you shir?? I never seen that before..I've only seen duallies or duramax with them.

Diesail Enthusiast

Diesail

Posted
Posted

AAM makes a Torsen limited slip for the 10.5. Dodge uses them. I know the AAM unit for the 11.5 is a 2:1 torque bias and the True-trac is a 3:1, I would assume the 10.5 is also a 2:1 bias, so it it doesn't transfer as much torque as the the True-Trac, but it would save you an axle swap and they are cheaper than the True-Trac.

Ranger Senior Enthusiast

Ranger

Posted
Posted
My '04 3500 srw with 6.0L came with the 11.5 inch, 14 bolt rear. Interchangeability should be no problem. Especially if you can find the whole donor truck to get y our parts from.

 

Are you shir?? I never seen that before..I've only seen duallies or duramax with them.

 

 

3500s are still considered 1 ton trucks even with SRW I believe...

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • 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
    • davester
      Replacement Radiator

      By davester · Posted

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