Field note
A no-fault-found call is not wasted if you leave behind a complete operating baseline and a plan for what to capture when the fault returns.
Capture the baseline
- Record thermostat/controller status, supply/return temperatures, pressures/temperatures as appropriate, voltage, current, active/history alarms, sensor values, fan operation, and environmental/load conditions.
- Compare nameplate/reference values without treating one number as a universal pass/fail target.
Challenge the equipment safely
- Cycle or stage the equipment only within reasonable operating limits.
- Watch for delayed fan starts, relay chatter, sensor dropout, pressure spikes, communication loss, and other transient clues.
Leave a useful next step
Tell the next technician exactly what was normal, what transient condition was seen, what the customer observed, and what data should be captured if it happens again.
Safety / model checks
- Do not create unsafe rapid cycling while trying to force an intermittent problem.
- Do not add refrigerant or replace parts only because the symptom cannot be reproduced.
IntermittentBaselineDiagnostics
Safety note
HVAC work can involve high voltage, rotating equipment, pressurized refrigerants, and combustion systems. Use this site as a reference only. Follow the equipment manual, applicable codes, PPE, lockout/tagout, and current refrigerant rules. Field cases and troubleshooting paths are case-specific and are not OEM procedures or universal targets.
Related field cases
Rooftop Unit · Field archiveIntermittent cooling complaint cannot be duplicated during a complete rooftop checkRooftop Unit · Field archiveElevated compressor current does not automatically mean the compressor is failingPackaged AC / RTU · Field archiveGood cooling performance prevents unnecessary refrigerant adjustment during intermittent sensor complaint