Abstract:
An apparatus for the diagnosis of a cooling system which receives inputs in the form of data about a cooling system, and measurements made from the cooling system, and which then calculates the amount of refrigerant to be removed or added to the cooling system for optimal performance. In addition, methods for ensuring correct setup of a cooling system are disclosed. The methods may apply to FXV (fixed expansion valve) systems and may include making and displaying a prediction of a refrigerant adjustment based upon measurements such as return air wetbulb temperature, condenser air entering temperature, refrigerant superheat vapor line temperature, and refrigerant superheat vapor line pressure. A method for ensuring correct setup of a cooling system is disclosed. The method may apply to TXV (thermostatic expansion valve) systems and may include making and displaying a prediction of a refrigerant adjustment based upon measurements such as refrigerant subcooling liquid line temperature and refrigerant subcooling liquid line pressure. A method for ensuring correct setup of a cooling system is disclosed. The method may include making and displaying a prediction of a refrigerant adjustment or of an airflow adjustment based upon measurements such as return air wetbulb temperature, return air drybulb temperature and supply air drybulb temperature. Recommendations may also be based upon evaporator coil temperature splits. Methods for visual identification, archiving of associated measurement and verification data, and viewing of data for a correct setup of a cooling system are disclosed. Methods of maintaining correct setup of a cooling system through use of labels and locking, double-sealing, color-coded, and laser etched Schrader caps are disclosed.

Description:
RELATED APPLICATIONS 
   The application claims the benefit of copending U.S. Provisional Patent Application No. 60/611,054 filed Sep. 17, 2004 having the same inventor applicant. 

   FIELD OF THE INVENTION 
   The invention generally relates to air-conditioning systems and heat pump systems, especially in cooling mode. The invention more particularly comprises methods and systems for verifying proper refrigerant charge and airflow for split-system and packaged air-conditioning systems and heat pump systems in cooling mode. 
   BACKGROUND 
   The present application references U.S. Pat. No. 6,612,455 to inventor Byrne entitled Cap Lock for Assembly and System. 
   Byrne&#39;s cap lock for assembly and system can be used to assist maintenance of proper refrigerant charge and airflow for the life of air conditioners. 
   Some studies show approximately 50 to 67 percent of air conditioners suffer from improper refrigerant charge and airflow, and this reduces efficiency by approximately 10 to 50 percent (“National Energy Savings Potential from Addressing HVAC Installation Problems,” US Environmental Protection Agency, 1998; “Assessment of HVAC Installations in New Air Conditioners in the Southern California Edison Service Territory,” Electric Power Research Institute, 1995; “Enhancing the Performance of HVAC and Distribution Systems in Residential New Construction,” Hammarlund, J., et al. 1992 ACEEE Summer Study on Energy Efficiency in Buildings. “Field Measurements of Air Conditioners with and without TXVs,” Mowris, R., Blankenship, A., Jones, E., 2004 ACEEE Summer Study on Energy Efficiency in Buildings, August 2004). 
   Potential savings in the United States from proper refrigerant charge and airflow are approximately 19.6 Billion kilowatt-hours per year and electricity demand savings are approximately 10.3 Million kilowatts. Most air conditioning technicians do not have proper training, equipment, or verification methods to ensure proper refrigerant charge and airflow. Instead, technicians rely on rules of thumb such as “add refrigerant until suction line is 6-pack cold or suction pressure is 70 psig or liquid pressure is less than 250 psig.” Air conditioners either do not receive regular service or they are serviced periodically and overcharged due to organizational practices of adding refrigerant charge until the suction line is “6-pack cold.” This practice causes air conditioners to be overcharged and operate inefficiently. 
   Some prior art methods involve taking measurements of certain temperatures and pressures of a cooling system and determining if the system either needs refrigerant added or removed. A significant drawback to these methods is that no measure of the amount of refrigerant to be added or removed is known. Instead, the technician must add or remove incremental amounts of refrigerant. With each incremental iteration, the system must be operated and stabilized, typically for fifteen minutes or more, before another set of readings can be taken to determine if the system is now running in an efficient manner. The time involved with this haphazard iterative method results in an unnecessary cost to the consumer. What is called for is a system and method for the diagnosis of air conditioning systems that determines an amount of refrigerant to be added or removed without iteration. 
   Correcting overcharged systems with improper airflow saves electricity by reducing refrigerant pressure and proportionally reducing electric power usage. It also eliminates problems of liquid refrigerant returning to the compressor causing premature failure. Correcting undercharged air conditioners with improper airflow saves electricity by increasing capacity allowing them to run less which extends the life of the compressor. It also prevents overheating of the compressor and premature failure. 
   The present invention relates, in part, to a method for verifying proper refrigerant charge and airflow for split-system and packaged air-conditioning systems and heat pump systems in cooling mode to improve performance and efficiency and maintain these attributes over the effective useful life of the air conditioning system. 
   In particular, the method may be suitable for determining proper R22 and R410a refrigerant level and airflow across the evaporator coil in air-conditioning systems, which are used to cool residential and commercial buildings. The method includes in-operation diagnostic measurements with the compressor and indoor fan switched on. The diagnostic system records site information, air conditioner information, measurement equipment calibration information, measurements used in the algorithms to make predictive recommendations, refrigerant charge and airflow adjustments, and verification data using: 1) personal digital assistant Expert-system Software (PDAES) software; 2) Telephony Expert-system Software (TES), deploying Interactive Voice Response (IVR) technologies; 3) personal computer (PC) software; and 4) internet database software, accessed via a web-based browser interface. 
   SUMMARY 
   An apparatus for the diagnosis of a cooling system which receives inputs in the form of data about a cooling system, and measurements made from the cooling system, and which then calculates the amount of refrigerant to be removed or added to the cooling system for optimal performance. 
   In addition, methods for ensuring correct setup of a cooling system are disclosed. The methods may apply to FXV (fixed expansion valve) systems and may include making and displaying a prediction of a refrigerant adjustment based upon measurements such as return air wetbulb temperature, condenser air entering temperature, refrigerant superheat vapor line temperature, and refrigerant superheat vapor line pressure. 
   A method for ensuring correct setup of a cooling system is disclosed. The method may apply to TXV (thermostatic expansion valve) systems and may include making and displaying a prediction of a refrigerant adjustment based upon measurements such as refrigerant subcooling liquid line temperature and refrigerant subcooling liquid line pressure. 
   A method for ensuring correct setup of a cooling system is disclosed. The method may include making and displaying a prediction of a refrigerant adjustment or of an airflow adjustment based upon measurements such as return air wetbulb temperature, return air drybulb temperature and supply air drybulb temperature. Recommendations may also be based upon evaporator coil temperature splits. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
     The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention, and, together with the description, serve to explain the principles of the invention: 
       FIG. 1  is a schematic diagram showing an air-conditioning system with provision for refrigerant charge and airflow measurements according to an embodiment of the invention. 
       FIG. 2  is a photograph of an air-conditioning system with verified refrigerant charge, airflow and verified thermostatic expansion valve labels and locking, double-sealing, color-coded, and laser-etched Schrader caps to properly identify the air conditioning refrigerant R22 or R410a according to an embodiment of the invention (see U.S. Pat. No. 6,612,455 for reference). 
       FIG. 3  shows a refrigerant charge and airflow (RCA) verification system process flowchart using PDAES or TES (telephony expert-system software) to diagnose and recommend steps according to an embodiment of the invention. 
       FIG. 4  is an airflow (temperature split method) algorithm flowchart diagram. 
       FIG. 5  is a superheat algorithm flowchart diagram. 
       FIG. 6  is a subcooling algorithm flowchart diagram. 
       FIG. 7  provides a summary flowchart of RCA Verification automated PDAES and TES such as may be used with embodiments of the invention. 
       FIGS. 8A-C  are PDA displays of the calibration portion according to some embodiments of the present invention. 
       FIGS. 9A-C  are PDA displays of the airflow portion according to some embodiments of the present invention. 
       FIGS. 10A-C  are PDA displays of the superheat portion according to some embodiments of the present invention. 
       FIGS. 11A-C  are PDA displays of the subcooling portion according to some embodiments of the present invention. 
       FIGS. 12A-D  are illustrative of a test case addressed using an embodiment of the present invention. 
       FIG. 13  is an illustrative schematic of a computer according to some embodiments of the present invention. 
       FIG. 14  is an illustrative example of a temperature split look-up table. 
       FIGS. 15A-15B  are an illustrative example of superheat look-up table. 
       FIGS. 16A-16P  are an illustrative example of a temperature and pressure look-up table for refrigerants R22 and R410a. 
   

   DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
   In the following description, for purposes of clarity and conciseness of the description, not all of the numerous components shown in the schematics and/or drawings are described. The numerous components are shown in the drawings to provide a person of ordinary skill in the art a thorough, enabling disclosure of the present invention. The operation of many of the components would be understood and apparent to one skilled in the art. 
     FIG. 1  is a schematic diagram showing an exemplary R22 or R410a air-conditioning system with provision for refrigerant charge and airflow measurements according to an embodiment of the invention. Typically, the compressor  1  compresses refrigerant into high-pressure vapor. Refrigerant vapor thus enters condenser coil  2 . Outdoor fan  3  blows air across the exterior of condenser coil  2 . This cools refrigerant by removing heat  4  and condenses refrigerant to a liquid. Liquid refrigerant  5  moves along a refrigerant pipeline to inside evaporator coil via an FXV metering device  6  or, in alternative embodiments, via a TXV metering device. 
   Metering device  6  may control the rate at which refrigerant enters the evaporator coil and may also create a pressure drop. This allows refrigerant to expand from a small diameter tube to a larger one. Fan  7  blows air across inside coil and refrigerant absorbs heat from air  8  and refrigerant evaporates back to vapor. Refrigerant vapor returns to compressor to start cycle over again. 
   For air conditioners equipped with fixed expansion valve (FXV) devices, factory refrigerant charge and the following measurements may be entered into a subsystem, for example a Personal Digital Assistant Expert-system Software (PDAES) or an automated Telephony Expert-system Software (TES): * Return wetbulb temperature measured at the evaporator coil (near  7 ,  FIG. 1 ); * Condenser air entering temperature measured at the condenser coil (near  3 ,  FIG. 1 ); * Vapor temperature and * Vapor pressure, both measured at compressor return (near  9 ,  FIG. 1 ). 
   Software algorithms in a PDAES or TES can use these values to diagnose proper refrigerant charge and recommend a weight of refrigerant to add or remove from the air conditioning system so as to achieve a balance of saturated refrigerant vapor in the evaporator coil and condenser coil so as to provide optimal cooling capacity and/or energy efficiency. 
   For air conditioners equipped with TXV devices, factory refrigerant charge and the following measurements may entered into a subsystem, for example a Personal Digital Assistant Expert-system software (PDAES) or an automated Telephony Expert-system Software (TES): Liquid temperature and pressure are measured at output side of compressor  1  ( FIG. 1 ). Software algorithms such as in a PDAES or automated TES may use these values to diagnose proper refrigerant charge and recommend the weight of refrigerant to add or remove from the air conditioning system to achieve a balance of saturated refrigerant vapor in the evaporator coil and condenser coil, for example to provide optimal cooling capacity and/or energy efficiency. 
   For either FXV or TXV systems the following measurements are entered into the PDA or automated telephony system: return (entering) wetbulb and drybulb temperatures are measured at ( 7 ) at the inside coil (left) and supply drybulb is measured at ( 8 ). Software algorithms in the PDAES or automated TES software use these values to diagnose proper airflow across the evaporator coil and recommend corrective steps to improve airflow or to check and correct refrigerant charge to provide optimal cooling capacity and energy efficiency. The airflow methodology is based on standard methods known to persons of ordinary skill in the arts. 
     FIG. 2  is a photograph of an air-conditioning system  201  with verified refrigerant charge and airflow label and verified thermostatic expansion valve label maintained with locking, double-sealing, color-coded (green for R22 and red for R410a), laser-etched Schrader caps (see U.S. Pat. No. 6,612,455 for reference). 
   In some embodiments of the present invention, as seen in  FIG. 3 , the refrigerant charge and airflow verification process involves interaction between a technician at the site of the air conditioning system and a computer system at a remote location.  FIG. 3  shows a refrigerant charge and airflow (RCA) verification system process flowchart showing how jobs may be performed using PDAES or automated TES to diagnose proper RCA and recommend corrective steps to improve airflow and/or to check and correct refrigerant charge and airflow as outlined supra to provide optimal cooling capacity and/or energy efficiency for an operative air-conditioning system such as that of  FIG. 1 . 
   Referring again to  FIG. 3 , in box  1 . 0 , the air conditioner dealer subscribes to use the RCA verification system and provides the following information for each technician: * technician name; * cellular telephone number; and * Environmental Protection Agency refrigerant certification number (as required by Section 608 of the Federal Clean Air Act and Federal Law 40CFR part 82 subpart F). The subscription validation may use this information to register a technician for the Automatic Number Identification (ANI) or Dialed Number Identification Service (DNIS) when using the RCA Verification automated Telephone Expert-system Software (TES) (box  1 . 2 ) or Personal Digital Assistant Expert-system Software (PDAES) (box  1 . 3 ). 
   Still referring to  FIG. 3 , in box  1 . 1  the dealer uploads air conditioner job data to the Secure Internet Database (box  1 . 5 ). Data are uploaded for new jobs (box  2 . 1 ) or existing jobs (box  2 . 2 ). Job data are specified as indicated in boxes  2 . 2  through  2 . 1 . 17  and as follows: * date (box  2 . 1 . 1 );
     * customer name (box  2 . 1 . 2 );   * customer address (box  2 . 1 . 3 );   * customer city (box  2 . 1 . 4 );   * customer ZIP code (box  2 . 1 . 5 );   * customer phone number (box  2 . 1 . 6 );   * air conditioner capacity in thousand British Thermal Units per hour, (kBtuh) (box  2 . 1 . 7 );   * air conditioner manufacturer (box  2 . 1 . 8 );   * air conditioner model (box  2 . 1 . 9 );   * air conditioner serial number (box  2 . 1 . 10 );   * air conditioner refrigerant type R22 or R410a (box  2 . 1 . 11 );   * air conditioner factory charge in ounces, (lb. and oz.) (box  2 . 1 . 12 );   * air conditioner Seasonal Energy Efficiency Ratio (SEER) (box  2 . 1 . 13 );   * air conditioner airflow, in cubic feet per minute, (cfm) (box  2 . 1 . 14 );   * air conditioner fixed expansion valve, (FXV), or   thermostatic expansion valve, (TXV), (box  2 . 1 . 15 );   * air conditioner installation date (box  2 . 1 . 16 ); and   * refrigerant charge added or removed (box  2 . 1 . 17 ).   

   Referring now to  FIG. 3  and box  1 . 2 , the TES checks for correct ANI or DNIS automatically (box  1 . 2 . 1 ) and may provide for alternative manual entry (box  1 . 2 . 2 ). If the technician is not validated (box  1 . 7 ) then a call may be initiated to the system administrator (box  1 . 7 ), and the technician can register for training (box  1 . 8 ). The PDAES or TES check the temperature and pressure measurement equipment calibration date (box  1 . 4 ). If the equipment has not been calibrated within (typically) 30 days of the current date, then PDAES or TES require calibration (box  1 . 4 . 1 ). With properly calibrated equipment the technician is ready to use the RCA verification system with new or existing job information or use the RCA calculator if the technician is not going to track customer job information (box  2 . 0 ). The required information for new or existing jobs is checked (box  2 . 0 . 1 ). The technician may enter information for a new job (boxes  2 . 1  through  2 . 1 . 17 ) or enter and validate information at the customer site (boxes  2 . 2  and  2 . 2 . 1 ). 
     FIG. 8A  illustrates a first job display page  801  and a second job display page  804  of a PDA according to some embodiments of the present invention. The information box  803  is displayed when the temperature and pressure measurement equipment calibration date is not valid. 
   In some embodiments of the present invention, the technician is only using the RCA calculator (box  2 . 3 ) and is not planning on linking to a computer system at a remote location. In such a case, the technician may enter air conditioner AC refrigerant type, i.e., R22 or R410a (box  2 . 3 . 1 ), air conditioner expansion device, FXV or TXV, and air conditioner factory charge (box  2 . 3 . 2 ). After entering all required job and air conditioner information, the technician is then ready to use the PDAES or TES to verify RCA at the customer site (box  3 . 0 ). 
   Airflow temperature split measurements are entered next (box  3 . 1 ). The airflow procedure is described in detail with reference to  FIG. 4  infra. After the airflow temperature split measurements are entered and recommendations are followed, the PDAES or TES may check for FXV or TXV devices (box  3 . 1 . 10 ). The technician enters data to verify proper refrigerant charge using either the SH (superheat) procedure (box  3 . 2 ) or SC (subcooling) procedure (box  3 . 3 ). These procedures are described in detail in  FIGS. 5 and 6  respectively. 
   The appropriate refrigerant charge verification procedure diagnoses proper refrigerant charge or, alternatively, recommends the weight of refrigerant to add or remove from the air conditioning system to achieve a balance of saturated refrigerant vapor in the evaporator coil and condenser coil to provide optimal cooling capacity and/or energy efficiency (boxes  3 . 2 . 14  etc.). 
   The RCA verification system checks to see if air conditioner RCA are verified (box  4 . 0 ). If RCA is not verified, the system recommends further diagnostic measurements of superheat and airflow (box  3 . 2 . 15 ) or further diagnostic measurements of subcooling and airflow (box  3 . 3 . 13 ). The PDAES and TES may save all information entered by technicians regarding measurements and actions taken to verify proper RCA (box  4 . 1 ). These data are uploaded to the secure internet database server where data are archived (box  1 . 5 ). RCA verification quality control inspections may typically be performed on a statistical random sample of jobs completed by each technician for quality assurance purposes (box  5 . 0 ). Customers, dealers, and manufacturers view RCA verification data stored on the secure internet database server using an internet browser by logging on with a user name and password (boxes  5 . 1 ,  5 . 2  and  5 . 3 ).  FIG. 3  items  3 . 2 . 14 ,  3 . 3 . 15 ,  3 . 2 . 17 ,  3 . 3 . 12 ,  3 . 2 . 12  and  3 . 3 . 10  are discussed infra in connection with other figures. 
     FIG. 4  provides an airflow (temperature split method) algorithm flowchart diagram illustrating measurements entered into the PDAES, computer, or TES system—and used by software algorithms to diagnose proper airflow and recommend corrective steps such as to improve airflow to provide optimal cooling capacity and/or energy efficiency for desired operation of an air-conditioning system such as that of  FIG. 1 . Referring to  FIG. 4 , in box  3 . 1 . 1 , a PDAES or TES system may prompt the technician to enter the air conditioner rated or the measured airflow, for example in cfm (cubic feet per minute) 
     FIG. 9A  illustrates the airflow display  901  of a PDA running software according to some embodiments of the present invention. To begin the airflow temperature split procedure, the technician enters indoor entering air wet bulb temperature, typically in degrees Fahrenheit ° F. (box  3 . 1 . 2 ); indoor entering air dry bulb temperature (box  3 . 1 . 3 ), and indoor leaving supply air dry bulb temperature (box  3 . 1 . 4 ). As seen in  FIG. 9A , the indoor entering (return) air wet-bulb temperature  902 , the indoor entering (return) dry-bulb temperature  903 , and the leaving (supply) air dry-bulb temperature  904  are displayed after having been entered. The PDAES or TES may use these data to calculate and report actual temperature split (box  3 . 1 . 5 ), required temperature split (box  3 . 1 . 6 ), and the delta temperature split. The actual temperature split is calculated by subtracting the leaving supply air dry bulb temperature from the entering air dry bulb temperature. In some embodiments, the computer system (PDA or other device) has stored data including a required temperature split lookup table. An example of such a table is seen in  FIG. 14 . Based upon the indoor entering air wet bulb temperature, and the indoor entering wet bulb temperature, the stored data provides the required temperature split. Delta temperature split may be calculated as equal to the actual minus required temperature split (box  3 . 1 . 7 ). Also seen on the display  901  are the actual temperature split, the required temperature split, and the delta temperature split. The TES and PDAES may check to see whether the delta temperature split is within a margin such as ±3° F. (box  3 . 1 . 8 ). If the delta temperature split is within ±3° F., then the system may save temperature split measurements and report the “verified airflow” condition (box  3 . 1 . 9 ). The display  901  shows that the air flow is verified  905  in the example illustrated in  FIG. 9A . 
   Still referring to  FIG. 4 , when airflow has been verified the technician may be prompted to check superheat or subcooling, or if those are OK, then all measurements may be saved and the system may report a “verified refrigerant charge and airflow” condition (box  3 . 1 . 10 ). Alternatively, if the delta temperature split is NOT within about ±3° F., then the system checks whether delta temperature split is less than about −3° F. (box  3 . 1 . 11 ). If YES, the system may report a “low capacity check refrigerant charge” condition (box  3 . 1 . 12 ). The system may then prompt the technician to check superheat or subcooling (box  3 . 1 . 13 ).  FIG. 9C  illustrates the display of a PDAES using yet another leaving (supply) air dry-bulb temperature  909 . In this example, the delta temperature split is not within the prescribed limits (at −7.2) and the PDAES displays the following information to advise the technician. “Low Capacity. Check Charge.” See  909 . 
   Conversely, if a delta temperature split is greater than +3° F. (box  3 . 1 . 14 ), the system may report a “increase airflow” condition (box  3 . 1 . 15 ). The system then prompts the technician with a checklist of actions intended to improve airflow, such as: clean/replace filter; open airflow vents; clear airflow obstructions; increase fan speed; and repair/replace duct system (box  3 . 1 . 16 , items  3 . 1 . 16 . 1  et seq). After completing these repair procedures, the technician may be prompted to return to the start of the airflow temperature split procedure and continue, for example box  3 . 1 . 2 .  FIG. 9B  illustrates the display of a PDA using a different leaving (supply) air dry-bulb temperature  906 . In this example, the delta temperature split is not within the prescribed limits (at +6.8) and the PDA displays the following information to advise the technician. “Increase airflow. Clean filter. Open vents.” See  907 . 
   Still referring to  FIG. 4 , when airflow is verified the technician may be prompted to check superheat or subcooling, or if these are OK, then all measurements may be saved and the system may report a “verified refrigerant charge and airflow” condition (box  3 . 1 . 10 ). 
     FIG. 5  provides a superheat algorithm flowchart diagram illustrating the measurements entered into a PDAES or TES and used by software algorithms to diagnose proper refrigerant charge for air conditioning systems with FXV (fixed expansion valve) devices. The flow chart shows the procedural steps to diagnose and correct refrigerant charge as described supra to provide optimal cooling capacity and energy efficiency for operational air-conditioning systems such as that of  FIG. 1 . 
   Referring to  FIG. 5 , in box  3 . 2 . 1 , the PDAES or TES system prompts the technician to enter factory charge, for example in pounds or ounces (if not already entered, for example, along with the job data). To begin the superheat procedure, the technician enters indoor entering air wet bulb temperature, for example in ° F. (degrees Fahrenheit) (box  3 . 2 . 2 ), outdoor condenser entering air dry bulb temperature also ° F. (box  3 . 2 . 3 ), vapor line pressure in psig (pounds per square inch gauge) (box  3 . 2 . 4 ), and vapor line temperature, ° F. (box  3 . 2 . 5 ). The TES and PDAES may use these data to calculate and report evaporator saturation temperature (box  3 . 2 . 6 ), actual superheat ° F. (box  3 . 2 . 7 ), required superheat ° F. (box  3 . 2 . 8 ), and delta superheat ° F., equal to the actual minus required superheat temperature ° F. (box  3 . 2 . 9 ). The evaporator saturation temperature may be calculated using the vapor line temperature as the independent variable and a temperature and pressure look-up table for refrigerants R22 and R410a. An example of such a table is seen in  16 A- 16 P. 
   The PDAES or TES checks to see if the delta superheat temperature is within a wider range, typically ±5° F. (box  3 . 2 . 10 ). If the delta superheat temperature is within (for example) ±5° F., then the system may save superheat temperature measurements and report a “verified refrigerant charged” condition (box  3 . 2 . 11 ). When refrigerant charge has been verified the technician may be prompted to continue with airflow temperature split procedures (described supra), or if already verified then all measurements may be saved and the system may report a “verified refrigerant charge and airflow” condition (box  3 . 2 . 12 ). 
     FIG. 10A  illustrates the superheat display  901  of a PDA running software according to some embodiments of the present invention. The entered indoor entering air wet bulb temperature  1002 , the outdoor condenser entering air dry bulb temperature  1003 , vapor line pressure  1004 , and the vapor line temperature  1014  are seen on the display. Also seen on the display are the actual superheat, the required superheat, and the delta superheat. The factory charge  1105 , and the refrigerant type  1013  are also seen on the display. In the illustrative example of  FIG. 10A , the delta superheat is within bounds and the display indicates that the refrigerant level is verified  1006 . 
   Still referring to  FIG. 5 , if the delta superheat temperature is NOT within ±5° F., then the system checks whether delta superheat temperature is greater than +5° F. (box  3 . 2 . 13 ). If YES, the system uses algorithms to recommend “add refrigerant” (box  3 . 2 . 14 ), and states the amount of refrigerant to add. The system then prompts the technician to continue and check superheat again after a period such as 15 minutes to allow for the air conditioner to reach equilibrium with the refrigerant charge adjustment (box  3 . 2 . 15 ). 
   Alternatively, if delta superheat temperature is less than −5° F. (box  3 . 2 . 16 ), the system uses algorithms to recommend “remove refrigerant charge”, for example in an amount equal to delta superheat times “coefficient-SH2 times factory charge (box  3 . 2 . 17 ). The system then prompts the technician to continue and check superheat again after say 15 minutes to allow for the air conditioner to reach equilibrium with the refrigerant charge adjustment (box  3 . 2 . 15 ). When refrigerant charge has been verified the technician may be prompted to continue with airflow temperature split procedures (described supra), or if already verified then all measurements may be saved and the system may report a “verified refrigerant charge and airflow” condition (box  3 . 2 . 12 ). 
   In some embodiments, the system calculates the amount of refrigerant to add based on the inputs listed above using a computer program in conjunction with stored data. The evaporator saturation temperature may be calculated using the vapor line temperature as the independent variable and a temperature and pressure look-up table for refrigerants R22 and R410a. An example of such a table is seen in  FIGS. 16A-16P . In some embodiments, the computer program interpolates the evaporator temperature based upon the vapor line pressure for values in between values in the table. Once the evaporator saturation temperature is determined, the actual superheat temperature is determined by subtracting the evaporator saturation temperature from the vapor line temperature. 
   The required superheat temperature is determined from a data table stored in the computer system in some embodiments. An example of such a table is seen in  FIGS. 15A-15B . Using the indoor entering air wet-bulb temperature and the outdoor condenser entering air dry-bulb temperature, the required superheat is derived. The delta superheat is derived by subtracting the required superheat from the delta superheat. 
   If the delta superheat is within plus or minus 5 degrees (typical), or the pre-determined range, the system is operating with the appropriate amount of refrigerant. If the delta superheat is greater than 5 degrees, the system calculates the amount of refrigerant to be added. An example of a PDA display in such a circumstance is seen in  FIG. 10C . If the delta superheat is less than −5 degrees, the system calculates the amount of refrigerant to be removed. An example of a PDA display in such a case is seen in  FIG. 10B . 
   For cases where the delta superheat is greater than 5 degrees, the superheat factory charge coefficient used is 0.5 if the amount of factory charge is not known. The amount of refrigerant to be added is the delta superheat multiplied by the superheat factory charge coefficient. If the factory charge is known and is between 40 and 1200, then the superheat factory charge coefficient is the factor charge divided by (ø times 109). If the factory charge is less than 40, then the superheat charge coefficient is 0.5. If the factory charge is greater than 1200, then the factory charge coefficient is 1200 divided by (ø times 109). In these examples, ø=1.61803398874989. The amount of refrigerant determined to be added using this method and system allows the proper amount of additional refrigerant to be determined without the need for time consuming iterations. 
   For cases where the delta superheat is less than −5 degrees, the superheat factory charge coefficient used is 1 if the amount of factory charge is not known. The amount of refrigerant to be removed is the absolute value of the delta superheat multiplied by the superheat factory charge coefficient. If the factory charge is known and is between 40 and 1200, then the superheat factory charge coefficient is the factory charge divided by (ø times 55). If the factory charge is less than 40, then the superheat charge coefficient is 0.5. If the factory charge is greater than 1200, then the factory charge coefficient is 1200 divided by (ø times 55). In these examples, ø=1.61803398874989. ø is a constant determined in part from empirical study. The amount of refrigerant determined to be removed using this method and system allows the proper amount of additional refrigerant to be determined without the need for time consuming iterations. 
     FIG. 6  is a subcooling algorithm flowchart diagram illustrating the measurements entered into a PDAES or automated TES and used by the software algorithms to diagnose proper refrigerant charge for air conditioning systems with TXV (thermostatic expansion valve) devices. The flowchart shows procedural steps to diagnose and correct refrigerant charge as described supra to provide optimal cooling capacity and/or energy efficiency for operational air-conditioning systems such as the system of  FIG. 1 . Modern condensing units are designed to obtain their capacities and efficiencies at a given subcooling value. Any variance from design subcooling will reduce capacity and efficiency. 
   Still referring to  FIG. 6  and box  3 . 3 . 1 , the PDAES or TES prompts the technician to enter factory charge, typically in ounces (unless already entered with the job data). To begin the subcooling procedure, the technician enters required subcooling temperature, typically in ° F. (degrees Fahrenheit) (box  3 . 3 . 2 ), liquid line temperature, ° F. (box  3 . 3 . 3 ), and liquid line pressure, in psig (box  3 . 3 . 4 ). The required subcooling temperature value is typically found on an information plate on newer cooling devices. The cooling device&#39;s service manual may also list the required subcooling temperature. If the required subcooling temperature is unavailable, a default value of 10 F may be used for standard efficiency and 15 F for 12 SEER or above. 
     FIG. 11A  illustrates a PDA screen  1101  seen while diagnosing a TXV device using the subcooling portion of the present invention. The required subcooling temperature  1102 , the liquid line temperature  1103 , and the liquid line pressure  1104  have all been entered and can be seen on the display. The PDAES or TES use these data to calculate and report condenser saturation temperature (box  3 . 3 . 5 ), actual subcooling, ° F. (box  3 . 3 . 6 ), and delta subcooling ° F. 
   In some embodiments, the system calculates the amount of refrigerant to add based on the inputs listed above using a computer program in conjunction with stored data. The condenser saturation temperature may be calculated using the liquid line temperature as the independent variable and a temperature and pressure look-up table for refrigerants R22 and R410a. An example of such a table is seen in  FIGS. 16A-16P . In some embodiments, the computer program interpolates the condenser saturation temperature based upon the liquid line pressure for values in between values in the table. Once the condenser saturation temperature is determined, the actual subcooling temperature is determined by subtracting the liquid line temperature from the condenser saturation temperature. The delta subcooling may be calculated as equal to the actual subcooling temperature minus required subcooling temperature ° F. (box  3 . 3 . 7 ). 
   Next, the PDAES or TES may check to see if the delta subcooling temperature is within a range of, typically, ±3° F. (box  3 . 3 . 8 ). If the delta subcooling temperature is within ±3° F., then the system may save subcooling temperature measurements and may report a “verified refrigerant charged” condition (box  3 . 3 . 9 ). An example of such a case  1106  is seen in  FIG. 11A . When refrigerant charge is verified the technician is prompted to go to airflow temperature split, or if that is already verified, then all measurements may be saved and the may system report a “verified refrigerant charge and airflow” condition (box  3 . 3 . 10 ). 
   Alternatively, if the delta subcooling temperature is NOT within ±3° F., then the system may check whether delta subcooling temperature is greater than +3° F. (box  3 . 3 . 11 ). If YES, the system may use algorithms to recommend “remove refrigerant” (box  3 . 3 . 12 ). An example of the liquid line temperature  1110  and the liquid line pressure  1111  in such a case is illustrated in  FIG. 11C . For cases where the delta subcooling is greater than +3° F., the amount of refrigerant to be removed is the value of the delta subcooling multiplied by the subcooling factory charge coefficient. The subcooling factory charge coefficient used is 1 if the amount of factory charge is not known. If the factory charge is known and is between 40 and 1200, then the subcooling factory charge coefficient is the factory charge divided by (ø times 55). If the factory charge is less than 40, then the subcooling factory charge coefficient is 0.5. If the factory charge is greater than 1200, then the subcooling factory charge coefficient is 1200 divided by (ø times 55). In these examples, ø=1.61803398874989. ø is a constant determined in part from empirical study. The amount of refrigerant determined to be removed using this method and system allows the proper amount of additional refrigerant to be determined without the need for time consuming iterations. 
   The amount of refrigerant to be removed  1112  is displayed on the PDA screen. The system then prompts the technician to continue and check subcooling again after perhaps 15 minutes to allow for the air conditioner to reach equilibrium with the refrigerant charge adjustment (box  3 . 3 . 13 ). 
   If delta subcooling temperature is less than −3° F. (box  3 . 3 . 14 ), the system may use algorithms to recommend “add refrigerant charge” (box  3 . 3 . 15 ). An example of the liquid line temperature  1107  and the liquid line pressure  1108  in such a case is illustrated in  FIG. 11B . For cases where the delta subcooling is less than −3° F., the amount of refrigerant to be added is the absolute value of the delta subcooling multiplied by the subcooling factory charge coefficient. The subcooling factory charge coefficient used is 1 if the amount of factory charge is not known. If the factory charge is known and is between 40 and 1200, then the subcooling factory charge coefficient is the factory charge divided by (ø times 55). If the factory charge is less than 40, then the subcooling factory charge coefficient is 0.5. If the factory charge is greater than 1200, then the subcooling factory charge coefficient is 1200 divided by (ø times 55). In these examples, ø=1.61803398874989. ø is a constant determined in part from empirical study. The amount of refrigerant determined to be removed using this method and system allows the proper amount of additional refrigerant to be determined without the need for time consuming iterations. 
   The amount of refrigerant to be added  1109  is displayed on the PDA screen. The system then prompts the technician to continue and check subcooling again after about 15 minutes to allow for the air conditioner to reach equilibrium with the refrigerant charge adjustment (box  3 . 2 . 13 ). When refrigerant charge is verified the technician is prompted to go to airflow temperature split, or if this is okay, then all measurements are saved and the system reports “verified refrigerant charge and airflow (box  3 . 3 . 10 ). 
     FIG. 7  provides a summary flowchart of RCA Verification automated PDAES (Personal Digital Assistant Expert-system Software) and automated TES (Telephony Expert-system Software) such as may be used with embodiments of the invention.  FIG. 7  shows a method used to gather air conditioner refrigerant charge and airflow verification information and report data on the internet database available for viewing by customers, dealers, distributors, and manufacturers. 
   Still referring to  FIG. 7 , in box  1 . 0 , the air conditioner dealer subscribes to use the RCA verification system and provides technician and job information. The subscription validation system uses this information to validate technicians using the ANI (Automatic Number Identification) or DNIS (Dialed Number Identification Service) when using the TES (reference  1 . 2 ) or PDAES (reference  1 . 3 ). 
   Still referring to  FIG. 7  and box  1 . 1 , the dealer uploads air conditioner job data to the Secure Internet Database (box  1 . 5 ). Data are uploaded for new or existing jobs (box  2 . 1 ). Job data are described in boxes  2 . 2  through  2 . 1 . 17  of  FIG. 3 . Still referring to  FIG. 7  and box  1 . 2 , technicians use the TES or PDAES to verify RCA at the customer site (box  3 . 0 ). Airflow temperature split measurements may be entered and diagnosed first. The airflow procedure is described in detail supra in connection with  FIG. 4 . After the airflow measurements are entered and diagnosed and recommendations are followed, the PDAES or TES are used to verify refrigerant charge (box  3 . 0 ). The technician enters data to verify proper refrigerant charge using the superheat or subcooling procedures. These procedures are described in detail in  FIGS. 5 and 6 . 
   The refrigerant charge verification procedure diagnoses proper refrigerant charge or recommends the weight of refrigerant to add or remove from the air conditioning system to achieve a balance of saturated refrigerant vapor in the evaporator coil and condenser coil to provide optimal cooling capacity and energy efficiency. Still referring to  FIG. 7  and box  4 . 0 , if refrigerant charge and airflow are not verified, the technician continues further diagnostic measurements of superheat and airflow or further diagnostic measurements of subcooling and airflow. 
   The PDAES and TES save all information entered by technicians regarding measurements and actions taken to verify proper RCA. These data are uploaded to the secure internet database server where data are archived (box  1 . 5 ). RCA verification quality control inspections are performed on a statistical random sample of jobs completed by each technician such as for quality assurance purposes (box  5 . 0 ). Customers, dealers, and manufacturers view RCA verification data stored on the secure internet database server using an internet browser by logging on with a user name and password (boxes  5 . 1  through  5 . 3 ). 
     FIGS. 12A-D  illustrate an example of a cooling system that has been diagnosed and changed to proper working order using a system and method according to some embodiments of the present invention. The cooling system was a 4-ton TXV equipped split-system air conditioner overcharged with 139 ounces of refrigerant, or 35% over the recommended factory charge. The air conditioner used 5.8 kW when overcharged and 4.8 kW when properly charged. The EER increase from 7.1 to 9.7. 
     FIGS. 12B-D  illustrate the PDA displays of the original readings and again after the recommended refrigerant removal had taken place. The system was operating properly after the recommended removal, without any need for iteration and the extra time associated with iteration. 
   In some embodiments of the present invention, as seen in  FIG. 13 , an computer  1301  receives input and gives output via an I/O portion  1302 . In some embodiments, the I/O portion  1302  is the screen of a personal digital assistant. In some embodiments, the computer  1301  is a personal digital assistant or other computing device. The computer  1301  contains a computer program  1303  and stored data  1304 . In some embodiments, the data is contained within the computer program. 
   The embodiments described above are exemplary rather than limiting and the bounds of the invention should be determined from the claims. Although preferred embodiments of the present invention have been described in detail hereinabove, it should be clearly understood that many variations and/or modifications of the basic inventive concepts herein taught which may appear to those skilled in the present art will still fall within the spirit and scope of the present invention, as defined in the appended claims.