Jump to content

Recommended Posts

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?

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.

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?

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
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
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
Posted

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

  • Like 1
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...
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
  • 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,858 Guests (See full list)

  • Latest Articles

  • Posts

    • 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?
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...