PLC Logic Operation Tables: Truth Tables for AND, OR, NOT in Ladder Logic

PLC Programming · Engineering Notes · 2026

By the KOEED Engineering Desk · 2026-06-30 · 8 min read · Engineering Notes

A logic operation table — the humble truth table — is still the fastest way to reason about AND, OR, and NOT before you touch a single rung of ladder logic. This 2026 field note shows how these tables map to modern PLC instruction sets and where they save you hours of debugging.

Key Takeaways

  • A logic operation table lists every input combination and its output for a Boolean function (AND, OR, NOT, XOR, NAND, NOR).
  • Truth tables translate directly into ladder-logic rungs: series contacts = AND, parallel contacts = OR, normally-closed = NOT.
  • They cut commissioning time and make fault diagnosis systematic instead of trial-and-error.
  • Since 2024, IEC 61131-3 structured text and vendor AOIs let you express the same table as reusable code, not just contacts.
  • KOEED stocks the CPUs and I/O modules that run this logic, from Allen-Bradley to Siemens.

A PLC logic operation table is a truth table that pairs every input state with its output, giving engineers a reliable blueprint for AND, OR, and NOT logic in ladder or structured-text programs.

What a logic operation table actually is

A logic operation table (truth table) is a chart that shows every possible combination of input states and the resulting output for a given Boolean operation. In PLC programming, inputs are field signals — a limit switch, a pushbutton, a level sensor — and the output is a coil, lamp, or internal bit. By laying out all combinations, the table removes guesswork: you read the output you need and build the rung to match.

AND, OR, NOT in one glance

The three core operations cover the vast majority of interlocks and permissives on a real machine. Here they are as a single ledger table (1 = TRUE/energized, 0 = FALSE/de-energized):

Input A Input B A AND B A OR B NOT A
0 0 0 0 1
0 1 0 1 1
1 0 0 1 0
1 1 1 1 0

Mapping the table onto ladder logic

Ladder logic is a graphical mirror of these tables. The translation rules are fixed across every vendor — Allen-Bradley Studio 5000, Siemens TIA Portal, Mitsubishi GX Works:

  • AND → contacts in series on one rung. Both must be closed for the coil to energize.
  • OR → contacts in parallel (a branch). Either path closes the rung.
  • NOT → a normally-closed (XIO) contact that passes power until its bit goes TRUE.
// Structured Text (IEC 61131-3) equivalent of the table above
Motor_Run  := Start_PB  AND  NOT E_Stop;      // AND + NOT
Alarm_Lamp := High_Level OR  Low_Level;       // OR
Permissive := Guard_Closed AND Pressure_OK AND NOT Fault;

> Tip

Build the truth table first, then verify each rung against it during commissioning. Use the PLC Analog Calculator when an analog threshold feeds a Boolean bit — scale the signal before it becomes a table input.

What changed since 2024

The truth table itself is timeless Boolean algebra, but how engineers apply it on the plant floor has shifted:

  • Structured Text over contacts. IEC 61131-3 ST is now the default for complex permissives on newer CPUs (S7-1500, ControlLogix 5580). A dense truth table becomes a few readable lines instead of a rung nest.
  • Reusable AOIs / function blocks. Vendors ship Add-On Instructions that encapsulate a validated logic table, so the same interlock is tested once and dropped in everywhere.
  • AI-assisted diagnostics. Tools like the KOEED AI Diagnostic Tool compare observed I/O against the expected truth table to flag the failing operation faster.
  • Legacy hardware still runs it. SLC 500 and S7-300 systems from the 2000s use the exact same AND/OR/NOT logic — only the editor changed. Sourcing those modules is where downtime risk lives.

Cross-Reference

Legacy discrete I/O running your logic tables → modern equivalents KOEED keeps in stock: Allen-Bradley 1756 ControlLogix and Siemens SIMATIC S7-1500.

Migration difficulty: low for pure Boolean logic. The table stays the same; only tag mapping changes.

Using tables to troubleshoot

When an output misbehaves, force the inputs to a known row and compare the coil state to the table. A mismatch isolates the fault to one operation — a stuck NC contact, a mis-wired parallel branch, or a scan-order issue. Pair this with the PLC Error Code Database and, for serial links, the Modbus CRC Calculator to rule out comms corruption before blaming the logic.

Sourcing the CPU or I/O that runs your logic?

Send your BOM to Moritta@KOEED.COM. Active stock, EOL stock, and cross-references — all in one quote within 24 hours.

Create a Quote →

Related on KOEED Blog

Frequently asked questions

What is a logic operation table in PLC programming?

It is a truth table that lists every input combination and the resulting output for a Boolean operation, giving programmers a reliable reference for building AND, OR, and NOT logic.

How does a truth table map to ladder logic?

Series contacts implement AND, parallel branches implement OR, and a normally-closed contact implements NOT. Read the required output from the table, then draw the matching rung.

Are logic operation tables still used in 2026?

Yes. The Boolean logic is unchanged, but engineers now often express the same table in IEC 61131-3 structured text or reusable AOIs alongside classic ladder contacts.

Can I use a truth table to troubleshoot a PLC?

Force the inputs to a known row and compare the actual output to the table. Any mismatch points to the specific failing operation, such as a stuck contact or mis-wired branch.

KOEED Engineering Desk

Industrial automation editors at KOEED. We write about PLC sourcing, cross-reference, and legacy system support. Reach the team at Moritta@KOEED.COM.

Related Articles

Вернуться к блогу