Jump to content

Recommended Posts

Posted

Hey, just got a 2014 2500HD 6.0L with the 6L90 tranny (truck still looks like a 2013 series)
I see lots of youtube videos on the 1500's where you pry the exhaust down slightly to get enough room to drop the pan, but I couldn't find any info on 2500's.
But my 2500 the pan looks slightly different (maybe longer cause it’s a 6L90 not a 6L80)
The exhaust also looks different, doesn’t have the flat spot like the 1500’s. Also doesn’t have the flex part that I see in the videos of the 1500s where guys pry on the exhaust or rachet strip pull on it.

Is the 2500 the same just pry on the exhaust? Anyone drop the tranny pan on these before?

Posted

Probably not.

 

You will have to look under the truck but I think the exhaust has a bracket that bolts to the transmission on the passenger side. Using a pry bar will not push anything down if that is connected.

Posted

My 2011 I was able to remove the pan with exhaust intact. I didn’t have to pry anything the pan was able to slide out with a little wiggling. Prepare for the mess. I wish these things had drain plugs like the Allison’s.


Sent from my iPhone using Tapatalk

  • 3 weeks later...
Posted

Thanks everyone

 

Ended up being super easy. Lots of room to get the pan out. Don't need to remove anything extra. I grabbed a 12v pump off Amazon with a 4ft hose for like 20 bucks, sucked the tranny fluid out via the dipstick. Made dropping the pan pretty much mess free. Got about 6 quarts out like this. Maybe 7. Ya sure the pump was slow, maybe 1.5 to 2 beers slow. But mess free!!!

 

For the filter seal, used a flat blade and a hammer and cave one part in, then grabbed it with vice grips and pulled it out. Used a socket to drive the new one in evenly. Compared to the 6l80 videos, the 6l90 seal seems allot higher up, harder to get a hammer at it. Deep socket helped.

The plastic tranny filter had the round circle that shows the year and month it was manufactured. Looks like it was more than likely the original still after 115k miles, glad I changed it. Pan seal is a metal/rubber style, so reusable.

 

For anyone that stumbles on this, i also replaced the tranny cooler lines and engine cooler lines (4wd model). I'm not a fan of cutting the old lines to make remaval easier, if you can't remove the old lines you can't get the new lines in.

 

For the engine oil lines, between the diff and motor mount is pretty tight. I ended up lowering the front diff. Pop off the 1 electrical cable, and the diff vent. Undo the front drive shaft u joint straps. From underneath 2 nuts on passenger side, 2 bolts on driver side, and 1 from up top on drivers side (a bunch of extentions and a impact made this quick and easy). Let the diff down slowly with a jack. Don't need to undo the CV joints, but let it sit on some blocks so its weight isn't hanging from the CV's. Lines came out and in from the back.

 

For the tranny lines, I couldn't get them to come out the back. The long bend of the line going into the aux cooler was a struggle. Ended up removing the plastic that hangs below the front bumper and fished them out the front.

Diff was already lowered from doing the engine lines, not sure if it woukd have been needed or not for the tranny lines.

Used a jack and a bottle jack to slowly get the front diff back up and lined up.

 

I remember it being much easier on my 93. But the supply and return lines were completely separate back then. On my new 14 the lines go to a common block that mounts on the engine, or tranny, making it harder as you have to fish both lines together instead of separate.

  • Like 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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   2 Members, 0 Anonymous, 2,046 Guests (See full list)

  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...