Read field inputs
Pressure, temperature, flow, level, position, and digital state from sensors and switches wired directly to its input modules.
PROGRAMMABLE LOGIC CONTROLLERS
A Programmable Logic Controller is a hardened industrial computer that runs deterministic control loops at the edge — switching pumps, throttling valves, interlocking safety — and reporting its state up to SCADA. This page walks through what they are, how they think, and where they fit.
Read inputs → solve logic → write outputs. Repeats every few milliseconds.
Visual programming descended from relay diagrams — electricians can read it.
Same inputs, same outputs, in bounded time. Safety-critical guarantee.
01 / FUNDAMENTALS
A Programmable Logic Controller is a single-purpose computer designed to survive a control cabinet — heat, vibration, voltage spikes — and execute a control program with millisecond-level reliability. It runs the same four-step cycle, forever.
Scan cycleRead inputs → execute logic → update outputs → housekeeping & comms. Repeat every 1–50 ms depending on the program. Deterministic by design.
Pressure, temperature, flow, level, position, and digital state from sensors and switches wired directly to its input modules.
Solve the control program — ladder, function block, or structured text — against current inputs. Same logic, same outcome, every cycle.
Energize relays, modulate analog signals, command variable-frequency drives — close the loop on the physical process.
Publish state, counters, and faults to SCADA over DNP3, Modbus, EtherNet/IP, or OPC UA — the supervisory layer’s eyes.
02 / PROGRAMMING
Ladder logic descends from physical relay wiring diagrams — two vertical power rails with horizontal “rungs” between them. Each rung is a logical condition. If power can flow from the left rail to the right rail through that rung’s contacts, the rung’s output coil energizes.
That visual metaphor is why ladder is the lingua franca of industrial control: electricians can read it without learning a programming language. The example on the right is a textbook seal-in motor starter — try the inputs.
Read it like this—| |— is a normally-open contact (closes when input is on). —|/|— is normally-closed (closes when input is off). —( )— is an output coil. Power flows left to right; if a coil gets power, its output turns on.
Press START — the M1 coil energizes and seals itself in. Press STOP or trip the overload to drop it.
03 / INTEGRATION
The PLC owns the loop. SCADA owns the picture. Between them flows a steady two-way stream — telemetry rising every poll, operator commands descending on demand — over industrial protocols designed for noisy, lossy plants.
04 / USE CASES
Three industries, same control philosophy. The hardware brands differ; the scan cycle does not. Pick a vertical to see what the PLC is doing on the ground.
PLCs sit at every wellhead, compressor station, and tank battery — controlling artificial-lift cycles, isolating leaks, and rolling telemetry up to the operator.
Plunger lift, gas lift cycle, ESP speed control
Stage discharge interlocks, vibration trip logic
Level transfer pumps, hatch detection, vapor recovery
Leak detection trip, ROW pressure containment
05 / DECISION
They look similar from the outside — both are ruggedized controllers with I/O and comms. The difference is what they were optimized for. Here’s the practical breakdown.
What's inside a Remote Terminal Unit and where you find them.
Function codes, data tables, and the float packing gotcha.
Architecture, layers, and the signal path from sensor to control room.
Ready to see how this applies to your operation? Start a pilot conversation — no commitment, no field changes.