PLC Programming Languages: Ladder, FBD, SFC, ST and IL Compared

1. Ladder Diagram (LD)

Ladder Diagram represents the program as horizontal rungs between two vertical power rails.

Contacts on the left represent input conditions. A coil on the right represents the output action. If all contacts on a rung are true, the coil energises.

It maps directly to relay panel logic, which is why electricians adopt it quickly. Every PLC manufacturer supports it.

It is the default choice for simple machine logic, motor starters, and conveyor control. See the Ladder Logic for Beginners guide for a full introduction.

Use when: the team has an electrical background, the logic is mostly discrete on/off, and the program must be maintained by field electricians who are not software engineers.

Avoid when: the program needs complex arithmetic, loops, or data array processing. These require many rungs of Ladder that are hard to read and harder to debug.

2. Function Block Diagram (FBD)

Function Block Diagram represents the program as a network of interconnected blocks. Each block is a function: a PID controller, a timer, a comparator, a filter. Data flows from left to right through the connections between blocks.

FBD maps naturally to instrument loop thinking. A PID block has a setpoint input, a process variable input, and an output signal -- connect them the same way you would draw a loop diagram.

The DCS function block programming guide covers FBD in DCS systems where it is the dominant choice.

Use when: the program is primarily continuous control (PID, cascade, ratio control), the team comes from an instrumentation background, or the program is running in a DCS style environment.

Avoid when: the program has complex sequential logic. FBD is excellent for continuous loops but becomes a tangled mess of connections when used for step-by-step sequences.

3. Sequential Function Chart (SFC)

Sequential Function Chart models a process as a series of rectangular steps joined by horizontal transition bars. The program sits in exactly one active step at a time. When the transition condition below the active step becomes true, the program moves to the next step.

SFC is the clearest way to represent a batch sequence or machine cycle. A filling machine: Step 1 open inlet valve, Step 2 wait for level, Step 3 close valve, Step 4 open discharge.

Each step has an action list and each transition has a condition expression. The sequence is visible without reading code. See the sequential circuits article.

Use when: the program is a sequence of distinct steps with clear entry and exit conditions: batch reactors, filling machines, CIP/SIP cycles, robot programs.

Avoid when: the control is purely continuous (use FBD) or purely parallel discrete logic (use LD). SFC is a sequencer, not a general purpose language.

4. Structured Text (ST)

Structured Text is a high level text language with IF THEN ELSE, CASE, FOR, WHILE, and REPEAT constructs. Variables, data types, and function calls work similarly to Pascal or modern C. It is the most expressive of the five PLC programming languages for algorithmic work.

Use when: the program needs mathematical formulas, array manipulation, string processing, or algorithm implementation. Also excellent for reusable function blocks where readability matters more than graphical representation.

Avoid when: the maintenance team is electricians with no programming background. ST code is not readable to someone who learned PLCs through relay logic. Combine ST with LD by writing complex calculations in ST function blocks called from a Ladder main program.

5. Instruction List (IL)

Instruction List is a low level assembly like language. Each line is one instruction operating on an accumulator register. It was included in the original IEC 61131-3 standard as a bridge for engineers coming from relay instruction sets and early PLC programming.

Important: the 2013 edition of IEC 61131-3 deprecated Instruction List. Most modern PLC platforms are removing IL support. For new projects, Structured Text performs the same role with far better readability. Do not start new programs in IL. Use another PLC programming language instead.