Jump to content

Recommended Posts

Posted (edited)

As everyone here already knows…”it shouldn’t take more than a few minutes” turned into me pondering how many fist sized dents I needed in my door panel for aerodynamic efficiency or the “golf ball” look.

 

Anywho.

 

I delved into the underside of my custom trail boss in an attempt to install a dipstick in my 6L80. Of course, I must mention that the 6L80 was present in the 4.3 models until at least the 2020 model year (RPO code MYC), this dipstick fits all 6L80/90 transmissions as far as I’m aware, in the 6/8 cylinder engines alike.

 

Here is the order of operations.

 

NOTE: TRANSMISSION CROSSMEMBER REMOVAL OR DROPPING THE REAR OF THE TRANSMISSION WAS NOT REQUIRED. FOR MY APPLICATION.


Remove dipstick from tube to make installation easier. The dipstick gets in the way otherwise. Also, lube the seal and tube with white lithium grease to ease insertion.

 

In order to access the hole where the plug is (that must be removed prior to installation), there is a heat shield that needs removal on the passenger side of the transmission. It is held on by two 10 mm bolts. Beware of the front one, it’s blocked by the bend in the shield, and too close to the catalytic converter to get a regular 3/8” ratchet and shallow well socket in there.

 

After removing the heat shield, you can use a trim tool, your fingers, or a screwdriver to remove the plug where the dipstick enters the transmission (there is only one location it will go).

 

Then, find the studs on the backside of the bellhousing, and locate the one below the starter hump. Using a 15 mm deep well, swivel, and breaker bar or 1/2” ratchet, remove the stud. 
 

Test fit and place it in its approximate location, but beware the ground strap on the back of the block, right next to the path of the tube, there is a chance it gets in the way like mine, and you’ll need to loosen it in order to route the tube unabated. 15mm bolt.

 

Install your dipstick seal first, you can use a thin layer of white lithium grease for ease of insertion. Follow up by seating the tube in the grommet, and then reinstall your bell housing stud. Be mindful that torquing that stud could cause the dipstick to raise out of the hole, so it’s wise to keep light pressure downwards on the tube to ensure it stays in the transmission until you snug and tighten the stud.

 

Once the tube is seated and the stud installed, make sure your O2 sensor wire holder/zip tie is still in its pocket on the transmission, and reinstall the heat shield. 
 

If you had to loosen or remove the ground strap on the block, reinstall/tighten the bolt.

 

Use the procedure sent with the dipstick to check level and add fluid as needed. Mine needed 1 quart (this is typical, mine didn’t leak and hasn’t lost fluid.).

 

This dipstick does work with aftermarket and deep pans. Lubelocker also makes a reusable gasket for the 6L80 and one for the 6L90 if anyone is interested.

Edited by s10dragracer888
  • Thanks 1
Posted

Thank you! I wish they made the 6, 8, and 10 speed transmissions to come with a dipstick and drain plug in the pan. It’d be too much to ask to be able to change the filter like we could on the Allison 1000/2000s.

  • Like 1
  • Thanks 1

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

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