Lesson Air conditioning (cooling) · Comfort and psychrometrics
Psychrometric chart in the field
The psychrometric chart plots dry-bulb against moisture so you can see relative humidity, wet-bulb, dew point, and enthalpy at a glance. In the field you may use a chart, an app, or a meter that calculates RH—but the ideas stay the same: plot return air, plot supply air, and understand what the coil did.
Finding a state point
Measure DB and either WB or RH. That intersection is the air’s state. From there read dew point and approximate enthalpy if the chart/app provides them.
Coil process (cooling)
Return air moves toward colder, drier supply air (ideally). Horizontal-ish movement relates to sensible; downward moisture reduction is latent. Real coils do both.
Why techs should care
- Predict condensate and sweaty duct risk
- See if supply is cold but still moist
- Talk to customers with evidence (“indoor dew point is high”)
- Support charge and airflow diagnosis with WB/DB pairs
Practical field kit
Digital psychrometer or quality DB/WB; do not need a poster chart daily if the meter computes RH/dew point—but know what the numbers mean.
Mixed air and economizers
Outdoor air mixed with return creates a new state point. Economizer faults show up as unexpected mixed-air conditions.
Limits of the tool
Garbage sensors → garbage points. Probe in supply before the first takeoff; avoid radiant sun on outdoor sensors.
Enthalpy economizer idea
When outdoor enthalpy is lower than indoor, free cooling may help. When outdoor air is hot and humid, dumping OA on “percent open” worsens latent load. Chart thinking stops bad economizer habits.
Apparatus dew point concept
The coil’s effective surface temperature drives how dry supply air can get. If the coil is not cold enough (low airflow issues aside), latent removal suffers. Relating supply dew point to comfort complaints is practical chart use.
Plotting mixed air
Return and outdoor points connect along a straight mixture line by mass fraction. A stuck OA damper shows up as a mixed-air state that does not match the intended fraction.
Tools vs understanding
Apps spit RH instantly; you still need to know that RH alone without DB is incomplete for coil process talk. Carry both the tool and the concept.
Practice on the job
Before you leave the topic in your head, force a slow walkthrough on the next real call:
- Name the component or condition you are standing in front of without looking at the ticket.
- Say out loud what “good” looks like for airflow, temperatures, and safety.
- Write one measurement you will take even if the customer wants a parts swap now.
- Tie the symptom to a cause you can prove—not a habit charge or a jumper.
- Recheck after the fix under the same ambient and load conditions you logged at the start.
That five-step habit turns book knowledge into field judgment. If you cannot explain the “why” to a helper on their first month, you do not own the lesson yet.
Tie-backs that prevent callbacks
Callbacks usually come from skipping the boring proofs: clean air paths, correct control sequence, solid liquid or safe vapor where the design expects it, and safeties that still work. When pressures look confusing, return to the physical story—heat in, heat out, metering, and compression—then re-measure. When a heating or IAQ complaint shows up, return to air, fuel/electric safety, and moisture before you upsell gadgets.
Keep OEM charts and nameplates above folklore. Typical numbers in training are compasses; the plate and the chart for today’s indoor/outdoor conditions are the map. Photograph settings you change so the next visit does not undo a careful repair.
Field notebook prompts
- What ambient and load state did I record?
- What did I prove before I adjusted charge, fuel, or setpoints?
- What safety device did I verify still protects the system?
- What should the owner do between visits (filters, doors, PM)?
Field case
Situation. “A/C not dehumidifying.” Return 76°F DB / 64°F WB; supply 58°F DB but RH still high in space. Short cycles.
How to think it.
- Chart/meter shows some latent removal per pass, but little runtime.
- Focus on cycle length and fan mode (ON vs AUTO).
- Comfort improves with longer cycles / corrected control.
Takeaway: state points explain process, runtime explains result.
In the field
Symptom
Humidity complaints, sweating ducts
Where to look
DB/WB or RH at return and supply
Likely causes
- Short run, poor coil process, infiltration
What to measure
- Paired psych readings + runtime
What not to do
- Memorize chart trivia without measuring
Checklist
- I can locate a state point from DB + WB/RH
- I interpret supply vs return as a coil process
- I use dew point language with customers when helpful
- I verify sensor placement
- I combine psych data with runtime observation