Jump to content

Recommended Posts

Posted

No because the rubber peice is pushing against the transmission. It's really right causing a vibration

Posted

After some reading I realize now why it wouldnt be so easy as to cut off the end of the yoke. It's possible that the tailshaft of the trans is bottoming out in the inside of the yoke. Not like what I was thinking was happening, which is the end of the yoke bottoming out into the transmission. If this is the case, then cutting down the yoke length would not help.

Posted

I would never cut a slip yoke. I would shorten the driveshaft itself.

 

My Maxtrac flip kit has an off center pin hole in the hanger bracket that shifts the axle back slightly to give the driveshaft room.

 

You could drill another hole in your hanger to do the same thing, but if you're finicky about the axle being perfectly centered in the wheel well I would not suggest it; it moves it back an inch.

Posted

I'll just have the shaft shortened by a shop. I got ahead of myself. Riding to work in the pouring rain on the Harley wasn't fun this morning. Was trying to avoid more days of that. Plus I am anxious to get the truck on the ground and driving. Especially because I am expecting vibrations/shake/noise from incorrect driveline angles, and the day or two extra that will be to sort out.

Posted

Ok so I have 4' pointing down at the tailshaft of the trans. And the pinion is setting pretty much dead level, not even .5' down.

 

What degree pinion shims would be recommended?

 

Driveshaft goes to repair shop tomorrow. I'm at their mercy for when that gets done.

Posted (edited)

Ok so I have 4' pointing down at the tailshaft of the trans. And the pinion is setting pretty much dead level, not even .5' down.

 

What degree pinion shims would be recommended?

 

Driveshaft goes to repair shop tomorrow. I'm at their mercy for when that gets done.

As I understand it...

 

On single u-joint slip yoke driveshafts your adjust so that operating angles match. If driveshaft is 8deg. and tail shaft is down 2deg. then it has 6deg. operating angle. You need to shim the axle to 2deg. up so that its operating angle is also 6deg. (using arbitrary #'s for this example)

 

See link: https://www.drivelinesnw.com/part-trouble-shooting/vibration-analysis/angle-analysis/measuring-and-correcting-angle-problems/

Edited by JRoyPDX
Posted

f0q0c8.jpg

 

4/6 drop

 

1.5" of driveshaft cut down

 

4 degrees of shims to bring rear pinion back up

2qwzw9v.jpg

  • Like 5
Posted

Put 10 miles on it and no shimmy or shakes. Did a light launch and it felt great. Need to get it aligned Monday after work. But it's not that far out at all. Maybe a slight negative camber

Posted

Can you take a picture of the front of the driveshaft where it goes into your trans and also a picture of he driveline angle and distance between the axle and frame

Posted

 

 

4/6 drop

 

1.5" of driveshaft cut down

 

4 degrees of shims to bring rear pinion back up

Looks good, makes me want to go 1" more to 4/7 all the way around on mine.

  • Like 1
Posted

You should. I might raise the rear of mine up to 6. For some reason my leafs are really.soft

Posted

My lift hangers show soon. Did you get hit with the Chevy lean ?

Posted

Just checked mine out, I am about 1/2" higher on the front right. Still about a 1" rake in the back overall.

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