Jump to content

Recommended Posts

Posted

I noticed my transmission temperature getting quite high when driving on trails or towing through traffic so I decided to add a secondary Derale 13900 transmission cooler in addition to the stock front mounted cooler. My truck is a 2020 Custom TB with the 5.3 and 6 speed 6l80e. This kit came with everything I needed except for a couple fittings, and the fan is wired to an ignition power source so it won't drain the battery. You can see that it is mounted to a winch mount that I had made, but without the winch there that would be a great spot to fit the cooler. Essentially I followed the return cooler line from the transmission forward until the hard lines split off into two rubber lines with the return going to the driver side of the truck. NOTE: The hard lines are 3/8" but the rubber line is 1/2" (learned that the hard way). I first held the cooler in place and measured what angle it needed to sit at and tacked together some mounts, then after a couple of iterations got it to where it fit and the skid plate did not interfere. I then finish welded, drilled, tapped, and painted the mounts. On the cooler itself, I mounted the 180 deg thermostat to the lower connection. With the cooler location determined, I then measured and cut the 3/8" rubber hose in the kit. I then clamped the return rubber line on the truck, cut the rubber hose, and connected the 3/8" cooler hoses to the pre-existing 1/2" hose on the truck. I used one 3/8-1/2 straight barbed connector and one 3/8-1/2 90 deg barbed connector. Some zip ties to tidy up the lines too. Wiring was simple as well, easiest way to get a for sure ignition power source was to get a fuse tap from autozone for a micro2 fuse and then you have a fused ignition source. Ran the power to the thermostat and then positive from motor to the other side of thermostat and the ground to the frame. The hole in the skid plate has an aluminum mesh behind it to keep small rocks out, and it's pretty high up so shouldn't see much abuse. Haven't given it a full test for cooling capability yet but the fan is nice and strong so I have no doubt it'll help. For about $200 total I'd say its a great upgrade for anyone who tows in the city or hits the trails on any steeper terrain.

Cooler Final.jpg

Posted

Forgot to add, but also had to refill the transmission obviously. Make sure it's nice and level and get a fluid pump but it was quite an easy process that is published readily for the 6l80e.

Skid Final.jpg

  • 10 months later...
Posted

Wanted to post an update to this thread, have had the thermostat out and secondary cooler installed for a whole year and here are some observations: transmission temp on the highway sits around 135 in winter (not super cold here only gets into high 20’s) and 150 in summer (even up to 100°+ outside). City driving gets to around 165°. Have done some off-roading on long, steep service roads and got the secondary cooler to kick on. I’d say I was averaging about 5mph on some really steep grades and the cooler kept the temps down below 200° even with about 1000 lbs of people and equipment in the truck. Likewise with towing I have a 8.5x24 foot car hauler and have had no issues with transmission temps even in traffic. 
A note for installation: the Derale kit comes with a thermostat that has a tiny thread that is not tapered. You NEED to use a liberal amount of LIQUID TEFLON to get it to seal, or else you will have a drip. Also, injection fuel line style hose clamps are the way to go for these lines as they aren’t under much pressure but these give you peace of mind to prevent a line blowing off from a cracked clamp. DO NOT use the clamps that come with the Derale kit (ask me how I know…). 
Overall I would highly recommend the upgrade if you do any kind of off-roading or towing as it was cost effective and works great!

  • Thanks 2
Posted

Thanks for the writeup, this could work for 8 and 10 speed transmissions as well.  Well Done!!!

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

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