← back

CODE.01 / F · FB · OOP

Functions, Function Blocks & OOP

How to build a PLC program that survives its own change orders.

From "why does copy-paste hurt?" to interfaces, inheritance and polymorphism. Every construct is shown in both ladder and Structured Text, the examples run live on the in-browser engine so you can watch them scan by scan, and the track ends in a workshop of real plant tasks: pump gangs, batch sequencers, recipe files and production logs.

15 lessons≈6 hours16 workshop exercisesLD + ST throughout
▸ ONE TYPE · MANY MACHINESIEC 61131-3FUNCTION_BLOCK FB_DeviceWRITTEN ONCE · ONE PLACE TO CHANGEConveyorinstance #1Fill Valveinstance #24-20Transmitterinstance #3

▸ READING AS A GUEST

All 15 lessons are open to read without an account. Signing up saves your place, keeps your XP and streak, and opens the whole workshop instead of the first few exercises.

CH.04 · ARCHITECT IT YOURSELF

Build

Take a real line from I/O list to block architecture, then prove it in the workshop.

▸ HANDS-ON · THE OOP WORKSHOP

16 exercises from real projects

Scaling a transmitter, a motor block used twice, a three-pump duty gang, an array of conveyor zones, a batch state machine, a device manager, plus the jobs every commissioning engineer meets sooner or later: writing a production log to the controller's memory card and reading a recipe back out of a text file. You write the ST, the engine grades it.

▸ open the workshop

▸ FEEL THE PROBLEM · PATCH DAY

Before (or after) the lessons: take a maintenance shift on a plant written with zero function blocks. A change order lands, you hunt every pasted copy it touches, and the engine shows you exactly what the one you missed costs. Then the same shift, one FUNCTION_BLOCK, one edit.

▸ take a shift

Work through the chapters in order, because each one assumes the last.

0 / 15 complete