Jump to content

Refrigerant in trans oil

Brian Hains
 Share

Recommended Posts

Brian Hains Enthusiast

Brian Hains

Posted
Posted

I had a transmission flush on my 2018 6L80 at the dealer. Had convertor shudder and random shifting problems. After a while could only use manual shift. Back to dealer, they said refrigerant from the condenser is in the fluid. Could the flush have caused the condenser cooler to rupture internally, causing this?

rav3 Senior Enthusiast

rav3

Posted
Posted

I guess it's always possible but I have not heard of this in the past. In either case, I don't think the dealer would admit it.

Brian Hains Enthusiast

Brian Hains

Posted
  • Author
Posted
1 hour ago, txab said:

Yo sure the word used wasn't coolant?

 

1 hour ago, Snowcamo said:

Smh

Im not big on initials. What do you mean?

rav3 Senior Enthusiast

rav3

Posted
Posted

On our 2017 Silverado, the transmission cooler lines go to the AC condenser, which serves as the primary heat exchanger for the transmission fluid, with the lines running to the top portion of the condenser to cool the fluid. While some radiators have an integrated cooler, GM vehicles from this era are designed with the transmission cooler built into the A/C condenser.

  • Like 1
Snowcamo Senior Enthusiast

Snowcamo

Posted
Posted
1 hour ago, Brian Hains said:

 

Im not big on initials. What do you mean?

Shaking my head

 

Like man thats messed up- while shaking my head in sorrow...

  • Like 1
kickass audio Enthusiast

kickass audio

Posted
Posted (edited)

i'm calling BS on this. It's only possible to have engine coolant contaminate the trans fluid since the first part of the passage in that era truck will have the trans line run through a warming tube on the side cap of the radiator that cools the engine coolant before it then passes onto the secondary radiator that has 100% isolated chambers for the air conditioner condenser and aux trans cooler.

 

I know 100% this is the design as I had a leak in the AC condenser and had to replace the condenser and aux trans cooler. On my 2014 the upper portion of the setup, maybe like the first 4 inches from the top, are a bit thicker for the passageways that connect to the fins on the radiator to dissipate heat and it had a totally separate connection that was tack welded to try and make it one assembly for removal/installation. At no time does the trans fluid come into contact with the HVAC lines.

 

The newer refresh trucks like my new one have totally separate coolers where the condenser is on it's own and the same for the secondary transmission cooler. The only shared cooling is with the heat tube that runs through one side of the radiator for the engine oil cooler and the transmission cooler before the trans line passes to the secondary radiator for additional cooling.

Edited by kickass audio
  • Like 1
  • Thanks 1
JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted

Soooo, does the dealer have a fix? Did they admit guilt, or are they saying it is a common problem?

  • Like 1
rav3 Senior Enthusiast

rav3

Posted
Posted

I'm not an A/C guy but doesn't the refrigerant become a gas when not compressed? I don't think it's possible. It would evaporate. You might have a little A/C oil mixed and I would also think that the A/C system could be contaminated with ATF. Not good. I would have a new condenser & filter installed, flush & recharge A/C.  Then flush the transmission, install new transmission filter & see what happens. 

Good luck getting the dealer to eat that one.

  • Like 3
  • 4 weeks later...
JC702 New Member

JC702

Posted
Posted

Having replaced the ac condenser in the 2014 Sierra I used to drive I know the condenser is also the trans cooler so there could be some validity to this BUT I would have to ask how they came to this conclusion since refrigerant is a gas which would leave no evidence of intermixing with a liquid like trans fluid that i know of.

 

My old condenser had a small pin hole leak that would cause the AC to blow warm air about a week after recharging it. 


If this diagnosis were accurate, I would think you would have experienced warm AC before any trans symptoms became evident. . 

 

  • 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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...