What Is a Field Controller
Lesson 1.1
A field controller is a small dedicated computer. It reads inputs (temperature sensors, pressure sensors, switches), makes decisions based on a program loaded into it, and drives outputs: damper actuators, valve actuators, relays. That's the entire job. Read, decide, act. Over and over, usually several times per second, 24 hours a day.
It lives wherever it needs to be. In a metal panel bolted to a mechanical room wall. Strapped to the side of an air handler. Mounted above a ceiling tile next to a VAV box. Sometimes it's in a clean, well-lit electrical room. Sometimes it's in a place you need a headlamp and contortion skills to reach.
Without a controller, you have dumb mechanical equipment. A damper that doesn't know what position to be in. A valve that doesn't know when to open. A fan that runs constantly or not at all. The controller is the brain; it takes raw information from the field, applies logic, and makes the equipment behave intelligently.
Here's the thing nobody tells you early enough: garbage in, garbage out. A controller with a bad temperature sensor will make bad decisions about heating and cooling. A controller with a sloppy program will do exactly what it was told, which might not be what anyone actually wanted.
Controller Terminal Groups
Power (24VAC HOT / COM): Every controller needs power. Most field controllers run on 24VAC provided by a transformer in the panel. HOT and COM are your two power conductors. No power, no controller.
Analog Inputs (AI1-AI4): Read variable signals: things that exist on a range. Temperature sensors, pressure sensors, humidity sensors, CO2 sensors. These are your eyes. The controller reads a voltage or resistance value and converts it to an engineering unit.
Binary Inputs (BI1-BI2): Read on/off signals. A flow switch, a proof of operation, an occupancy contact, a high limit switch. Either the circuit is closed or it isn't. No middle ground.
Universal Inputs (UI1-UI2): Flexible; can be configured as analog or binary depending on what you connect. You configure them in software to match your field device.
Analog Outputs (AO1-AO2): Send variable signals to actuators and drives. A 0-10VDC signal to a damper actuator, a 4-20mA signal to a valve. The controller decides how open or closed something should be and sends the corresponding signal.
Binary Outputs (BO1-BO2): Switch things on or off. A relay that starts a fan, energizes a valve, or triggers an alarm. The controller closes the circuit to turn something on and opens it to turn it off.
Communications (RJ45, NET+, NET-): How the controller talks to the rest of the world. The RJ45 might be BACnet/IP or a proprietary protocol. The NET+ and NET- might be BACnet MS/TP or RS-485.
The Big Picture
A controller by itself does nothing useful. What brings it to life is a program: a sequence of operations written by an engineer or a technician that tells it exactly what to do with what it reads. The inputs and outputs are the hardware layer: the physical connection between the controller and the real world. The program is the logic layer: the rules that turn raw data into intelligent behavior.
Understanding both is what separates a technician who can troubleshoot from one who can only swap boards. When something goes wrong, you need to know whether the problem is in the field wiring, the sensor, the program, or the controller itself.