I posted this over on the HD site. Even though this is for my 2500 which uses a different refrigerant, may be it is applicable here too.
After having the AC TSB done early this year, I was still not happy with the AC performance. While better than pre-TSB, I am still seeing a low of 50* driver's center vent and 46* passenger's center vent. On a 90*+ day, the truck meets specs, but on a 70-80* day it does not, as I see the same vent temps. Specs are 45* on a 70-80* day and 55* on a 90*+ day, with all temps taken from the Driver's side center panel vent.
I recently took the truck to a different dealer for a second opinion, and the tech ran through all the checks and it passed everything except the vent temps on cooler days. They did provide me a bit more information than I had previously gotten, such as the lowest recorded temp of the evap temp sensor of 38*. In the next few days, I decided to look on my own some more, mainly to see if I could verify if the evap temp sensor was really reading 38*. I borrowed a DVM with a quick reading temp probe and attached it to the low side line coming out of the evaporator (as close as possible) on the engine side of the firewall. What I saw has me very confident in a theory...
- These observations are after the initial cooldown of the system, when the compressor starts cycling. This was also done with MAX AC on. This is very repeatable, at least on my truck.
- The lowest recorded temp I see on the line is right at 38*, this corresponds directly to the 38* referenced by the tech.
- Every time I saw 38*, the compressor cycled off.
- The line temp quickly rose to 44*.
- Every time I saw 44*, the compressor cycled on.
- This ON-ON cycle happened between 10-15 seconds. I could easily hear the ON click of the compressor.
- When the temperature was dropping, at 39* it seemed to drop slower than at other temperatures. It seemed to take longer to drop from 39* to 38*, than from 41* to 40*.
- I think this is where the H-Block\TXV was beginning to meter refrigerant...
This leads me to my theory. I believe the evap temp sensor is cycling the compressor based on a software setpoint of 38*. I believe this value is set artificially high, thus not allowing the H-Block\TXV time to properly adjust and meter the refrigerant. In everything I know and have researched about this, I believe the H-Block\TXV should be able to sufficiently meter refrigerant flow under a high cooling load without freezing up the evaporator. Therefore the evap temp sensor cutting the compressor out at 38* is greatly reducing the cooling ability of the system. The evap temp sensor should only be cutting the compressor out under lower cooling loads, when the evaporator is actually at risk of freezing up.
My belief is that if the evap temp sensor cutout was set lower, say to 34*, the H-Block\TXV may now have enough time to properly meter the refrigerant before the compressor is forced to cycle. The other possibility is the H-Block\TXV was not properly spec'ed, or had a defect in manufacturing, for the 38* evap temp sensor cutout and does not function at the proper setpoint.
If the evap temp sensor cutout temp was dropped to 34* and the H-Block\TXV did regulate the evap temperature at 36-38*, the compressor would no longer cycle and greatly increase the cooling ability of the system. By having the compressor run continuously under a high cooling load, I could see this reducing vent temps by at least 6*. This would put both of my vent temps under spec at all outside temps with nothing more than a slight software change.
If anyone wants to replicate this experiment, I would be happy to hear the results. See if others are experiencing the same compressor cycling as I am and see if this is part of the poor cooling performance puzzle too many of us are struggling with.