Basic Knowledge of PLC: A 2026 Must-Read for Getting Started

What a PLC actually is in 2026 — and why this starter guide still matters

A Programmable Logic Controller is still the rugged industrial computer that reads sensor inputs, runs a user program on a deterministic scan cycle, and writes outputs to motors, valves, and HMIs. That sentence has not changed in forty years. Everything around it has: the IEC 61131-3 programming standard, the dominance of Ethernet-based fieldbuses, the arrival of cloud engineering portals, and the slow retirement of ladder-only teaching kits. If you are getting started with PLCs in 2026, the fundamentals in this guide will carry you for the next decade — but you should learn them on current hardware, not the legacy units a 2024 tutorial would point you at.

This Engineering Note rewrites our March 2024 post for the current state of the market. It keeps the original structure (what a PLC is, components, programming languages, memory types, I/O, programming process) but updates every recommendation to 2026 SKUs, software versions, and standards.

What changed in PLC fundamentals since 2024

The basic PLC block diagram has been stable for decades, but the layers above it moved in the last two years. Before we go through the building blocks, here is the deltas you need to know:

• IEC 61131-3 is now table stakes. The third edition (published in 2013) was still being adopted by mid-tier vendors in 2024. By 2026 every major PLC vendor exposes Ladder Diagram (LD), Function Block Diagram (FBD), Structured Text (ST), and Sequential Function Chart (SFC) in the same project. Instruction List (IL) has been formally deprecated in the 2024 amendment and is no longer taught as a primary language.
• EtherNet/IP and PROFINET own the fieldbus. PROFIBUS, DeviceNet, and CC-Link are still installed in tens of millions of nodes, but new designs in 2026 start on industrial Ethernet. Modbus TCP sits in the OT/IT convergence layer and shows up on almost every gateway.
• OPC UA over TSN replaced most vendor-proprietary pub/sub. Siemens, Rockwell, Mitsubishi, Omron, and Schneider all shipped OPC UA server capability in their default firmware by 2025. Beginners writing PLC code today will at least see OPC UA node names in the project tree.
• Cloud engineering portals are mainstream. TIA Portal Cloud, Studio 5000 Logix Designer as a Service, GX Works3 with MELSOFT MaiLab, and Sysmac Studio with NX-Cloud are all in beta or general release in 2026. You can now write and simulate a starter program on a Chromebook without installing vendor IDEs locally.
• Cybersecurity is no longer optional. IEC 62443-4-2 is referenced in most 2026 procurement specs. Beginners should learn to set a user password, segment the engineering port from the fieldbus, and avoid the default credentials still printed on old demo kits.

The PLC block diagram still holds

Strip away the standards, the fieldbuses, and the cloud connectors, and a 2026 PLC is still four physical blocks on a DIN rail or in a chassis: the power supply, the CPU, the input modules, and the output modules. Add a programming port (Ethernet or USB), a real-time clock, and increasingly a built-in web server, and you have a complete controller. Whether the unit is a 24-point micro-PLC like the Allen-Bradley Micro820 (2080-LC30-48QWB), a mid-frame S7-1200 (6ES7214-1AG40-0XB0), or a ControlLogix 1756-L73 chassis, the scan cycle is identical:

1. Read inputs. The CPU latches the state of every discrete and analog input module into a process image.
2. Execute the user program. Rungs, function blocks, or structured-text routines run in deterministic order. On a 1756-L73 the typical scan is sub-millisecond per thousand rungs; on a LOGO! 8.4 it is around 0.1 ms per block.
3. Write outputs. The output process image is sent to the output modules, energising relays, driving transistors, or pushing analog values to a valve.
4. Housekeeping. Communication tasks, web server, OPC UA publish, and diagnostics run between scans or on dedicated time slices.

Internal to the CPU you will find: a firmware flash (the operating system), user memory (the program and retain tags), data memory (current values), and increasingly a secure-element or TPM for signed firmware. None of this changes the beginner mental model — it does change which starter kit you pick, because some units now ship with onboard secure boot.

The five PLC programming languages under IEC 61131-3

The five languages described in IEC 61131-3 are still the canonical set, with the practical change that Instruction List has been deprecated and Structured Text has grown from "optional" to "first class" in most vendor studios:

Language	IEC 61131-3 name	Best for	2026 vendor example
Ladder Diagram	LD	Discrete logic, interlocks, motor starters	Studio 5000 routine type Ladder; TIA Portal LAD
Function Block Diagram	FBD	PID loops, drives, signal conditioning	TIA Portal FBD; EcoStruxure FBD
Structured Text	ST	Math, recipes, batch logic, parsing	Codesys ST; GX Works3 ST; Sysmac Studio ST
Sequential Function Chart	SFC	State machines, batch / process steps	TIA Portal SFC; SoMachine SFC
Instruction List (deprecated)	IL	Legacy reading only — do not write new code in IL	Removed from default IDEs by 2026

For a beginner, ladder logic is still the right place to start because it maps cleanly to the electrical schematics most maintenance technicians already read. But pair ladder with structured text from week three: in 2026 nearly every real-world program combines the two, with ladder handling the safety I/O and structured text handling data conversion and recipe management.

PLC memory types you need to know

The memory model has changed very little in twenty years, but the storage media underneath have. A modern PLC keeps four classes of memory:

Memory class	2026 backing technology	Lifetime	Beginner note
System firmware	NOR flash, signed image	20+ years; vendor-managed updates	Never overwrite manually
User program	MRAM or battery-backed SRAM	Non-volatile; 10 years typical for battery	Back up after every change
Retain / persistent tags	MRAM or NV RAM	Non-volatile across power cycles	Use for setpoints, counters, production totals
Working memory	DRAM	Volatile; resets on power loss	Use for transient flags and timers

The traditional "RAM / ROM / EEPROM" mental model from 2024 tutorials still works as a teaching device, but every PLC shipped in 2026 uses some form of MRAM or NV RAM for retain tags instead of a coin-cell-backed SRAM. This means no more battery-replacement schedules on most modern controllers — a small but real change in the maintenance routine.

The PLC I/O system: digital, analog, and motion

Every I/O module still falls into one of three buckets. What is new is the resolution, the channel density, and the IO-Link integration on the analog side:

• Digital I/O. 24 V DC sinking / sourcing is still the default for sensors. 110 / 230 V AC modules are reserved for motor contactors and valve coils. Channel counts per module have crept up: 32-point digital modules are now standard on mid-range racks (1756-IB32IF, 6ES7 321-1BL00).
• Analog I/O. 4–20 mA and 0–10 V are still the workhorses. New in 2026: 16-bit and even 24-bit resolution is standard on most analog input modules, and IO-Link master modules (1756-IB16IF with IO-Link, Siemens SM 1278 6ES7 278-4BD60) bring single-cable intelligent sensors onto the rack.
• Motion and specialty. A standalone PLC still needs a motion module or a servo drive with EtherCAT / EtherNet/IP motion to do multi-axis control. Beginners usually learn motion on a single-axis stepper (KOEED stocks the Mitsubishi MR-J4 and Yaskawa Sigma-7 lines for student labs) before they tackle multi-axis coordination.

Two standards are worth knowing. The IEC 61131-3 data types are still used everywhere — BOOL, INT, DINT, REAL, STRING, TIME, DATE — and every vendor adds a few proprietary types on top. The second is the IO-Link standard (IEC 61131-9), which is the default single-cable sensor interface on a 2026 line. You do not need to master IO-Link on day one, but you should know it exists when you see an "IOL" port on a sensor.

From wiring diagram to working program: the 2026 workflow

The five-step programming process from the original 2024 post still maps cleanly to a current project. Each step has new tools, but the order is unchanged:

Step 1 — Map the process

Write down every sensor and actuator on the machine, group them by I/O card, and assign a tag name. In 2026 most teams do this in a spreadsheet and import the tag list directly into Studio 5000 / TIA Portal as a CSV. KOEED's PLC Error Code Database and PLC Hex to Float Converter speed up the next two steps.

Step 2 — Configure the hardware

Open the device tree in TIA Portal / Studio 5000 / GX Works3 and add the CPU, I/O modules, and any networked drives or HMIs. Assign IP addresses (or let the tool assign them via DHCP). Verify the firmware version of each module against your project — mismatched firmware is the most common reason a 2026 beginner program will not download.

Step 3 — Write the code

Build the safety logic first in ladder (E-Stops, guards, permissives), then the sequence logic in SFC or a state machine in ST, then the HMI tags. Use named tags rather than absolute addresses; this is the single biggest habit that separates 2026 beginners from the engineers still maintaining 2000s-era file-based programs.

Step 4 — Simulate

Every modern IDE ships a simulator. S7-PLCSIM V19, Studio 5000 Logix Emulate, GX Works3 Simulator, and Sysmac Studio NJ/NX Simulator all run the actual compiled code against a virtual rack. Run your first three programs entirely in simulation before you touch real hardware.

Step 5 — Commission and test

Walk through every I/O point on the bench with a multimeter and a hand on the E-Stop. Verify each safety function independently, then together. Document the as-built tag list, export the project to a versioned archive, and store a copy offsite. This last habit is the one that saves you during the next firmware update or board swap.

What to learn first: a 2026 reading order

Condensed, the order that maps to current vendor documentation and current KOEED stock:

1. Boolean logic on a micro-PLC. LOGO! 8.4, Micro820, or Arduino Opta. AND / OR / NOT / latches / timers / counters, all in ladder.
2. Analog scaling. Read a 4–20 mA pressure transmitter, convert it with the PLC Analog Calculator, drive a control valve. Practice on FX5U or S7-1200.
3. Structured Text basics. IF / CASE / FOR loops, array handling, recipe management. Same hardware, different routine.
4. Industrial Ethernet. PROFINET between an S7-1500 and a Sinamics drive, or EtherNet/IP between a CompactLogix 5380 and a PowerFlex 525.
5. HMI and SCADA. WinCC Unified, FactoryTalk View, or GT Designer3. Build a screen with two buttons, a numeric input, and an alarm banner.
6. Safety and motion (optional, semester two). Safety I/O on a GuardLogix or a Siemens F-CPU; single-axis motion on an MR-J4 or Sigma-7.

Frequently asked questions

Do I still need to learn ladder logic in 2026?

Yes. Even though every modern studio supports structured text and function block diagram, ladder remains the dominant language for safety logic and for the troubleshooting screens every maintenance technician will read. A 2026 engineer who cannot read ladder is functionally illiterate on the plant floor.

Which PLC should a complete beginner buy first?

Siemens LOGO! 8.4 (6ED1052-1HB08-0BA1) for a low-cost starter, Allen-Bradley Micro820 (2080-LC30-48QWB) if your local job market is North American, Mitsubishi FX5U (FX5U-32MR/ES) if you are in Asia or working on export machinery, or Arduino Opta (AFX00003) if you want a $200 Codesys-compatible kit. All four are in active stock at KOEED.

Is PROFIBUS still worth learning in 2026?

For maintaining installed machines, absolutely. For new designs, no — start on PROFINET or EtherNet/IP. The IEC standard (IEC 61158) still lists PROFIBUS as a valid fieldbus, but no major OEM is shipping new PROFIBUS-only controllers in 2026.

What is the difference between a PLC and an industrial PC in 2026?

Functionally, very little — both can run deterministic code, drive I/O, and host an HMI. A traditional PLC still wins on ruggedness, deterministic scan, and decades of installed-base training. An industrial PC (IPC) or edge controller wins on compute, vision integration, and AI inference at the edge. Most modern lines mix both: a PLC for fast I/O and safety, an IPC for analytics and vision.

Related on KOEED Blog

• How-to guides — step-by-step tutorials on specific PLC families and tools
• Engineering Notes — long-form technical write-ups on cross-reference, fault codes, and fieldbus debugging
• Migration Guides — move from MicroLogix / S7-300 / FX3U to current platforms without rewriting from scratch
• Allen-Bradley collection — Micro820, CompactLogix 5380, ControlLogix stock
• Siemens collection — LOGO! 8.4, S7-1200, S7-1500, ET 200 stock