Jump to content

Recommended Posts

Posted

While changing oil tonight I noticed that there appears to be a light leak coming from one of the hoses between the radiator and the engine. I'm 99% sure it's an engine oil cooler line (not transmission cooler). There was a drop forming on the line and it definitely looked and smelled like engine oil. I need to remove the plastic cover under the engine to get a better look but in the mean time I was trying to find a diagram showing the hose. I'm not having much success. Any one ever had one of these lines replaced or know where to find a part diagram?

 

Thanks

  • 2 weeks later...
Posted

Yes, at 17000 miles I noticed a leak under the line on the liner. Took it to the dealer. They replaced under warranty stating the o ring inside the line from where the line goes from metal to rubber was leaking oil out slowly. Caused by the pressure that builds in the line. Currently have 38000 no other issues with the truck. Not even the shaking issue.

  • 9 months later...
Posted

Well, the trans cooler lines will not get hot until the trans is at 185+ degrees

 

so you can drive around for 15 minutes and feel whats hot and whats not, then wait another 15 minutes when the trans gets to operating temp and it will be super hot if its the trans line

Posted

yes, quite common for the lines to develop a leak where the rubber meets the fitting.

Had to do my '11 at 60k

  • 2 months later...
Posted

Just found this thread and I just found the hose leaking on my 2014. I am at 97k miles. For those that have replaced the line, I can see the block just above the oil filter, where is the cooler end located? I believe mine is also leaking at that end because there is oil at the radiator/condenser support also on mine. 

oil leak 5.jpg

Posted

I did both the trans cooler lines on my 2010, and it was a pain and I wouldnt DIY it again, I'd just pay someone with a lift. I bought the oil cooler lines too but never got around to doing them before I sold the truck. You have to pull the axle to do the oil cooler lines (at least on the NNBS), which is why I never did it. I still have the lines sitting in my garage taking up space. These lines are prone to leaking, and my oil cooler lines started weeping at about 50k on my 2010 and I sold it with 90k with no worse leaking, so I wouldn't worry about it totally failing on you anytime soon. 

  • Like 2
Posted
1 hour ago, rastasquid said:

I did both the trans cooler lines on my 2010, and it was a pain and I wouldnt DIY it again, I'd just pay someone with a lift. I bought the oil cooler lines too but never got around to doing them before I sold the truck. You have to pull the axle to do the oil cooler lines (at least on the NNBS), which is why I never did it. I still have the lines sitting in my garage taking up space. These lines are prone to leaking, and my oil cooler lines started weeping at about 50k on my 2010 and I sold it with 90k with no worse leaking, so I wouldn't worry about it totally failing on you anytime soon. 

 

I am 2wd so it may not be as bad if I do have to replace the lines. I just had the radiator replaced under warranty about 1000 miles ago. I believe the majority of my leak is from one of the fittings at the radiator and the fix should be on them. Most of the leak I see is under the radiator and condenser. The leak from the oil line is minimal at this point. 

oil leak 5.jpg

Posted (edited)
2 hours ago, rastasquid said:

If you decide to do them, see if 20828695 is still compatable... I'll give you a great deal haha

 

Thanks for the offer Rasta! I'll keep that in mind. I keep thinking I am finding the correct part number but so far no luck.

 

 

Edited by Eddie 70
  • 11 months later...
Posted

My 2018 Sierra SLT Z71 started leaking oil with less than 800 miles.   I took to the dealer today and they have to replace the engine oil cooler lines.  This is not a simple task but it is covered under warranty.

  • 6 months later...
Posted
On 2/10/2018 at 3:39 PM, Eddie 70 said:

Oil cooler line leak.

oil leak 3.jpg

I have this same problem on my 2014 Silverado 1500 but the route to replace this seems impossible. Any input or video on how to do it?

  • 4 months later...
Posted (edited)

I did this today. I had to remove bolts holding the axle to drop it a little. After that the hoses just took some gentle coaxing to remove and slip the other back in. They were 21mm. I don’t think it would have been possible without dropping the axle, but that part was a piece of cake. 2009 Yukon Denali 6.2L

Edited by Dadf8

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,803 Guests (See full list)

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...