English:Programmable Logic Controllers
Programmable Logic Controllers
Introduction
A programmable logic controller or PLC is an industrial computer used to control machines and processes. It receives information from field devices such as pushbuttons, limit switches, proximity sensors, temperature transmitters, and pressure transmitters. It evaluates that information according to a stored program and then controls outputs such as indicator lamps, contactors, solenoid valves, variable-frequency drives, and other actuators.
PLCs are used throughout industrial automation, including manufacturing, packaging, material handling, water treatment, building services, process plants, energy systems, and training equipment. For apprentices, trainees, and vocational students, PLC knowledge connects electrical engineering, electronics, programming, measurement, machine technology, troubleshooting, and workplace safety.
The photograph above shows examples of PLC hardware. Although different manufacturers use different shapes, terminals, software packages, and naming systems, the main ideas remain similar: field signals enter through inputs, a processor executes control logic, and outputs influence the process.
As you work through this aiMOOC, think like a technician: What is the process supposed to do? What signal tells the PLC what is happening? What logic makes the decision? What output causes the physical action?
Learning Goals
After completing this aiMOOC, you should be able to explain the purpose of a PLC, identify major hardware components, distinguish digital and analog I/O, describe the scan cycle, read basic ladder logic, compare major IEC 61131-3 programming approaches, create simple control sequences, document an automation task, and troubleshoot a PLC-controlled system systematically.
You should also be able to work more safely by recognizing the limits of software diagnostics, following authorized energy-control procedures, avoiding unsafe bypasses, and knowing when a task requires a qualified specialist.
From Relay Panels to PLCs
Before PLCs became common, many industrial control systems were built with large numbers of electromechanical relays, timers, and hard-wired connections. Changing the sequence of a machine could require substantial rewiring.
In the late 1960s, the automotive industry sought a more flexible electronic replacement for relay-based machine control. General Motors Hydramatic issued requirements for a programmable controller, and Bedford Associates developed the Modicon 084. This early work helped establish the modern PLC concept. A major advantage was that control behavior could be changed by modifying a program instead of rebuilding an entire relay panel.
PLCs were designed for industrial conditions and for maintainability by plant technicians. Ladder logic became especially important because its symbols and left-to-right logic resembled relay-control diagrams that electricians already knew.
The modern PLC has grown far beyond simple relay replacement. Current systems can process digital and analog signals, communicate over industrial networks, execute mathematical functions, control motion, exchange data with HMI and SCADA systems, and coordinate complex sequences.
PLC Hardware and Signal Flow
A useful way to understand a PLC is to follow information from the physical process into the controller and back out to the process.
The block diagram illustrates the basic relationship between input devices, the controller, and output devices. A real installation may also include power supplies, safety devices, network switches, remote I/O, motor drives, operator panels, and supervisory computers.
Core PLC Hardware
Power supply: The power supply provides the electrical energy required by the controller and, depending on the design, may also support connected modules. Always use the voltage range and wiring arrangement specified by the manufacturer.
CPU: The central processing unit executes the control program, manages memory, performs diagnostics, and handles communication tasks. Many PLCs have status indicators that help you identify operating modes and faults.
Memory: PLC memory stores the user program, variables, configuration data, and system information. Some data may be retained through a power cycle while other data is cleared, depending on the controller and project settings.
Input modules: Inputs receive signals from field devices. An input does not automatically mean that a condition is safe or correct; it only reports the electrical or data state that reaches the module.
Output modules: Outputs send control signals toward field equipment. A PLC output often controls an interface device such as a relay, contactor, valve coil, or drive command rather than powering a large load directly.
Communication interfaces: Modern PLCs exchange data with remote I/O, drives, HMIs, other controllers, engineering computers, and higher-level systems.
Programming device: A computer running engineering software is commonly used to configure hardware, create programs, download projects, monitor variables, and diagnose faults.
In a real control cabinet, the PLC is only one part of the automation system. Good technicians learn to relate the software view to terminals, wiring diagrams, sensors, actuators, protection devices, and the mechanical process.
Inputs and Outputs
The abbreviation I/O means input/output. I/O creates the bridge between software decisions and the physical world.
Digital Inputs and Outputs
A digital signal is interpreted as one of two logical states, commonly represented as FALSE and TRUE or 0 and 1. The exact voltage and electrical behavior depend on the hardware.
Typical digital inputs include pushbuttons, selector switches, limit switches, photoelectric sensors, proximity sensors, overload contacts, and status contacts.
Typical digital outputs include pilot lamps, relay coils, contactor commands, solenoid-valve commands, alarms, and enable signals.
A common industrial control voltage is 24 V DC, but you must never assume the required voltage from appearance alone. Check the module data sheet and electrical drawings.
Some DC I/O systems use sourcing and sinking arrangements. These terms describe current direction and transistor configuration. Incorrect combinations can prevent a signal from working or damage equipment, so always follow the specific wiring documentation.
Analog Inputs and Outputs
An analog signal represents a changing process value rather than only ON or OFF. Common industrial examples include 4 to 20 mA current loops and 0 to 10 V voltage signals, but many other signal ranges also exist.
An analog input might represent temperature, pressure, level, flow, position, weight, or speed. The PLC normally reads a raw numerical value and the program or hardware configuration converts it into engineering units.
An analog output might provide a speed reference to a drive, a position command, or a control signal to an actuator.
When wiring or troubleshooting analog signals, you must consider signal type, polarity, reference potential, shielding, grounding practice, and the exact module configuration. Use the manufacturer documentation for the installed equipment.
I/O Addressing and Tags
The program needs a way to identify each signal. Older systems often emphasize absolute addresses such as input and output memory locations. Modern systems frequently use symbolic tags such as Conveyor_Start_PB, Tank_Level, or Motor_Run_Command.
Useful tag names make the program easier to understand. Good documentation also links each tag to a terminal number, device identifier, drawing reference, normal state, signal type, and description.
A technician should be able to trace one signal across several representations: field device, wiring diagram, terminal strip, I/O channel, PLC tag, program condition, and HMI indication.
The PLC Scan Cycle
Most PLCs operate by repeatedly executing a control cycle. The exact internal order depends on the controller, but the general idea includes updating input information, executing program logic, handling system and communication work, and updating outputs.
A simplified learning model is:
- Read inputs: The controller obtains the current state or value of field inputs.
- Execute logic: The CPU evaluates the user program using the available data.
- Update outputs: Program results are transferred to output channels according to the controller architecture.
- Handle system tasks: Communication, diagnostics, and other controller services are performed as required.
The time required for repeated processing is often called scan time or cycle time. For many machine-control tasks, this time is very short, but it is still important. A rapidly changing input may require special hardware, interrupts, high-speed counters, or another control strategy.
Do not assume that every PLC updates I/O in exactly the same order. Some controllers use process-image memory, immediate I/O instructions, cyclic tasks, event tasks, or priority interrupts. When timing matters, consult the documentation for the specific platform.
Programming According to IEC 61131-3
IEC 61131-3 is an international standard for programmable-controller programming languages. The 2025 edition specifies the textual language Structured Text and the graphical languages Ladder Diagram and Function Block Diagram. It also defines Sequential Function Chart elements for structuring programs and function blocks.
Older training material may show additional historical language classifications. When you work with a current controller, use the language support and standard edition documented for that platform.
Ladder Diagram
Ladder Diagram or LD is a graphical language inspired by relay-control schematics. A ladder program is organized into rungs. Conditions are commonly shown as contacts and results as coils or instructions.
A normally open contact instruction is logically true when its referenced Boolean value is true. A normally closed contact instruction is logically true when its referenced Boolean value is false. These software symbols do not automatically tell you the physical construction of a field contact, so always distinguish the program instruction from the real device.
A coil instruction typically writes a Boolean result. Depending on the program, that result may represent a physical output or an internal memory bit.
For example, a simple motor-run condition might require a start request, a healthy overload signal, an enabled operating mode, and no active stop condition. In professional work, you should express these requirements clearly before writing code.
Function Block Diagram
Function Block Diagram or FBD represents logic and processing functions as connected blocks. It is useful when a control problem can be understood as signals flowing through logical, mathematical, timer, comparison, or control functions.
FBD is often effective for process logic, signal conditioning, calculations, reusable functions, and systems where connected functional relationships are easier to read than long sequences of contacts.
Structured Text
Structured Text or ST is a textual programming language. It is useful for calculations, data processing, loops, conditions, arrays, state logic, and algorithms that would be cumbersome to express graphically.
A conceptual Structured Text example is:
IF Start_Request AND System_Ready THEN
Motor_Command := TRUE;
END_IF;
This example is only a learning illustration. A real machine program normally needs stop handling, fault handling, mode control, restart behavior, safety design, and equipment-specific requirements.
Sequential Function Chart
Sequential Function Chart or SFC organizes behavior into steps and transitions. It is useful when a process follows recognizable stages such as waiting, clamping, processing, releasing, and returning to the initial state.
A good sequence design states what must be true before a transition occurs, what actions belong to each step, what happens on faults, and how the system returns to a defined condition.
SFC thinking is valuable even when the final implementation uses Ladder Diagram or Structured Text because it helps you describe the process before you write detailed code.
Common Program Elements
Boolean Logic
PLC programs use Boolean relationships such as AND, OR, and NOT.
AND means all required conditions must be true.
OR means at least one permitted condition is true.
NOT means a condition is logically inverted.
These relationships appear in ladder branches, function blocks, expressions, interlocks, permissives, alarm logic, and sequence conditions.
Timers
Timers are used when an action depends on elapsed time. Examples include delaying a fan start, checking that a sensor changes state within an expected interval, or keeping an indicator active for a defined period.
Timer behavior differs between instruction types and platforms. You should understand the timer input, preset time, elapsed time, output status, reset behavior, and retentive behavior before using it.
Counters
Counters accumulate events, such as products passing a sensor, machine cycles, rejected parts, or completed operations. A useful counter design defines what counts as one event, how repeated signals are prevented from causing false counts, when the counter resets, and what happens after a power cycle.
Interlocks and Permissives
An interlock prevents an action when an incompatible or unsafe process condition exists. A permissive is a condition that must be satisfied before an action is allowed.
For example, a pump may require sufficient tank level, the correct operating mode, no active fault, and an available downstream path before a run command is issued.
Process interlocks are not automatically equivalent to certified machine-safety functions. Safety-related control requires an appropriate risk assessment, architecture, hardware, validation, and compliance with applicable standards and regulations.
Data Handling and Scaling
Analog and numerical data frequently require conversion. A raw input value may need to be scaled into engineering units such as degrees Celsius, bar, litres per minute, millimetres, or revolutions per minute.
Good programs make units clear, check for invalid ranges, handle sensor faults, and avoid unexplained numeric constants. When possible, use named constants and documented function blocks so another technician can understand the calculation.
From Specification to Commissioning
Good PLC programming begins before the first rung or line of code.
Design Workflow
- Define the process: Describe what the machine or system must do in normal, manual, fault, startup, and shutdown conditions.
- Create an I/O list: Record every signal, device, type, address or tag, normal state, and purpose.
- Describe the sequence: Use a flowchart, state diagram, SFC, cause-and-effect table, or written sequence.
- Define interlocks: State which conditions permit or block each action.
- Plan tests: Decide how each requirement and fault case will be verified.
- Document the result: Keep drawings, code comments, variable names, backups, version information, and test records consistent.
Simulation and Offline Testing
A simulator or training PLC lets you test logic without operating a production machine. This is especially useful for apprentices and students.
You can create virtual input signals, observe program states, confirm sequence transitions, test timer behavior, and deliberately introduce non-hazardous simulated faults. Simulation does not prove that the real wiring, mechanics, safety system, or process will behave correctly, but it can remove many software errors before commissioning.
Commissioning
Commissioning connects the tested program with the real installation. A structured commissioning plan normally verifies hardware configuration, I/O mapping, device operation, communication, operating modes, sequences, alarms, interlocks, restart behavior, documentation, and acceptance criteria.
Only authorized personnel should energize equipment or perform work that could expose people to electrical, mechanical, pneumatic, hydraulic, thermal, or other hazardous energy.
Safety and Responsible Work
A PLC can command powerful machinery, so software work can have physical consequences.
Never rely on a stopped PLC program, an HMI stop command, or a de-energized output indication as proof that hazardous energy is isolated. Servicing and maintenance require the applicable energy-control procedure and verification defined by your workplace and legal jurisdiction.
For example, OSHA guidance for general industry in the United States addresses lockout/tagout for servicing and maintenance where unexpected energization, startup, or release of stored energy could cause injury. Other countries use their own legal and technical requirements. Follow the rules that apply at your workplace.
Do not bypass guards, emergency-stop functions, safety interlocks, or protective devices to make a test easier. Safety functions must be designed and validated for their intended purpose.
Online PLC tools can force variables or outputs on some platforms. Forcing is powerful and potentially dangerous because it can override normal program behavior. Use it only under an approved procedure, with the process in a controlled state, and with clear responsibility for removing every force.
Before changing a production program, make a verified backup, understand the current version, identify the reason for the change, assess effects on related equipment, obtain required authorization, and document the result.
Systematic Troubleshooting
Troubleshooting is more effective when you trace the signal path instead of changing several things at once.
A practical method is:
- Confirm the symptom: Ask what should happen, what actually happens, and under which operating conditions.
- Establish a safe working state: Follow the required procedure before physical inspection or intervention.
- Check basic status: Verify permitted power, controller mode, diagnostic indicators, and active faults.
- Trace the input: Check the field device, wiring, terminal, input-channel status, and PLC tag.
- Trace the program: Identify which logic condition prevents or enables the command.
- Trace the output: Check the program command, output-channel status, interface device, field wiring, and actuator.
- Record the finding: Document the actual root cause and the corrective action.
A useful technician asks, Where does the expected state first become different from the actual state? That point often narrows the fault quickly.
Do not replace parts merely because they are easy to reach. Evidence-based troubleshooting reduces downtime and prevents new faults.
Communication and Integration
PLCs rarely operate alone. They may exchange information with HMIs, SCADA systems, variable-frequency drives, servo drives, robots, remote I/O, barcode readers, vision systems, databases, and other controllers.
Industrial networks may use Ethernet-based or fieldbus technologies. Examples include PROFINET, EtherNet/IP, Modbus TCP, PROFIBUS, and other platform-specific or open protocols.
When diagnosing communication, separate the layers of the problem. Check physical connectivity, device power, addressing, configuration, protocol settings, connection status, tag mapping, and application logic.
Automation networks are part of operational technology. Good practice includes controlled user access, secure backups, documented changes, network segmentation where appropriate, disabling unnecessary services, and following the organization’s cybersecurity policy.
Industrial Applications and Careers
PLC skills are useful in many vocational roles, including industrial electrician, mechatronics technician, automation technician, maintenance technician, machine builder, commissioning technician, controls engineer, process technician, and system integrator.
Typical PLC-controlled applications include conveyor systems, packaging machines, filling systems, assembly equipment, pumping stations, HVAC systems, material-handling equipment, batch processes, test rigs, and production cells.
The most valuable workplace skill is not memorizing one software package. It is learning how to connect process knowledge, electrical drawings, I/O behavior, program logic, safety requirements, diagnostic evidence, and clear documentation.
Interactive Tasks
Quiz: Test Your Knowledge
What is the main purpose of a PLC? (Control industrial machines and processes) (!Display office documents) (!Store entertainment media) (!Replace every field device)
Which device normally provides information to a PLC input? (Sensor) (!Actuator) (!Contactor coil) (!Indicator lamp)
Which PLC component executes the user program? (CPU) (!Terminal strip) (!Fuse holder) (!Pilot lamp)
Which signal type represents two logical states? (Digital signal) (!Analog signal) (!Mechanical drawing) (!Network cabinet)
Which PLC language resembles relay control diagrams? (Ladder Diagram) (!Structured Text) (!Machine code) (!Spreadsheet formula)
Which current IEC language is primarily textual? (Structured Text) (!Ladder Diagram) (!Function Block Diagram) (!Wiring diagram)
What does a ladder coil usually represent? (Boolean result) (!Cable shield) (!Power supply voltage) (!Mechanical bearing)
Which device commonly provides an analog process value? (Pressure transmitter) (!Emergency label) (!Fuse carrier) (!Terminal marker)
What should you do before hazardous maintenance work? (Follow the authorized energy isolation procedure) (!Trust the HMI stop button) (!Force the output off) (!Assume the machine cannot move)
Which troubleshooting approach is most systematic? (Trace the signal from field input through logic to output) (!Replace several parts at once) (!Rewrite the entire program) (!Ignore diagnostic information)
Memory Game
| Scan cycle | Repeated controller processing sequence |
| Ladder Diagram | Graphical relay style programming language |
| Structured Text | Textual PLC programming language |
| Input module | Interface that receives field signals |
| Output module | Interface that sends control signals |
| Interlock | Condition that blocks an incompatible action |
| HMI | Operator interface for monitoring and commands |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Pushbutton state | Digital input |
| Pressure measurement | Analog input |
| Contactor command | Digital output |
| Speed reference | Analog output |
| Executes control logic | CPU |
Crossword Puzzle
| Ladder | Which PLC language resembles relay control diagrams? |
| Sensor | Which device detects a physical condition for the controller? |
| Actuator | Which device produces a physical action from a control command? |
| Processor | Which computing element executes controller instructions? |
| Interlock | What condition can block an incompatible machine action? |
| Ethernet | Which common network technology is widely used in modern automation? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- PLC Vocabulary Poster: Create a one-page illustrated poster that explains PLC, CPU, input, output, sensor, actuator, scan cycle, and HMI in your own words.
- I/O Classification Hunt: Examine a training rig, simulator, or instructor-provided machine diagram and classify at least ten devices as digital input, analog input, digital output, or analog output.
- Ladder Logic Sketch: Draw a simple ladder rung for an indicator that turns on when two permitted conditions are true, then explain the meaning of every contact and coil.
- Scan Cycle Explainer: Produce a short animation or video showing how input information, program logic, and output updates relate during a simplified PLC scan.
Standard
- Start Stop Simulator: Build and test a start-stop control in a PLC simulator, add a fault condition, and record test cases that prove the intended behavior.
- Conveyor I/O List: Create a professional I/O list for a small conveyor with pushbuttons, sensors, a motor starter, status lamps, and one analog measurement.
- Technician Interview: Interview an automation or maintenance professional about PLC troubleshooting, documentation, safety, and the skills expected from new trainees, then summarize the main lessons.
- Automation Site Visit: With instructor and workplace approval, visit a training laboratory, machine builder, production facility, or technical exhibition and create a photo-free observation report about the control system architecture.
Advanced
- Sorting Sequence Design: Design a multi-step sequence for a simulated sorting station using an SFC, state diagram, or flowchart, then implement the logic in an available PLC language.
- Fault Injection Experiment: In a safe simulator or de-energized training environment, introduce several documented signal faults and measure how quickly a structured troubleshooting method identifies each cause.
- PLC Network Integration Plan: Design a small automation network connecting a PLC, HMI, drive, and remote I/O, including addressing, data exchange, documentation, and basic cybersecurity controls.
- Commissioning Portfolio: Produce a complete mini-project containing requirements, I/O list, sequence description, PLC program, test plan, fault tests, version record, and commissioning checklist for a simulated machine.
Learning Assessment
- Signal Path Analysis: Given a machine fault where a sensor is physically active but the actuator does not move, explain how you would trace the fault from field device to PLC input, program logic, output channel, interface device, and actuator.
- Logic Transfer: Convert a written requirement containing two permissives, one stop condition, and one fault condition into a clear ladder-logic concept and justify each element.
- Analog Scaling: Design a scaling strategy for a transmitter and explain how you would detect values that indicate an open circuit, overrange, or configuration error without assuming that every platform uses the same raw counts.
- Sequence Test Design: Create normal, boundary, restart, and fault test cases for a three-step automated sequence and explain what evidence would demonstrate correct behavior.
- Safety Reasoning: Explain why a PLC output shown as OFF is not sufficient proof that a machine is safe for maintenance, and identify the type of workplace procedure that must control hazardous energy.
- Root Cause Evaluation: Compare random part replacement with evidence-based signal tracing and explain which method better supports reliable maintenance, documentation, and future fault prevention.
Evidence of Learning
Evidence of learning should show that you can connect theory with practical automation work.
| Area | Evidence |
|---|---|
| Knowledge | You can explain PLC purpose, architecture, I/O types, scan-cycle concepts, programming approaches, interlocks, communication, and safety limitations. |
| Skills | You can read basic PLC logic, trace signals, create tags and I/O lists, design simple sequences, test programs, and diagnose faults methodically. |
| Products | You can produce a documented PLC mini-project containing requirements, diagrams, program logic, test cases, troubleshooting records, and version information. |
| Professional practice | You can communicate findings clearly, follow authorization and energy-control procedures, avoid unsafe bypasses, and keep changes traceable. |
| Transfer | You can apply the same signal-flow and troubleshooting principles to unfamiliar PLC brands, machines, sensors, actuators, and industrial networks. |
OERs on the Topic
The Wikimedia Commons collection on programmable logic controllers provides additional openly licensed photographs and diagrams that you can use for study projects: Wikimedia Commons: Programmable logic controller
The current IEC reference for PLC programming languages is: IEC 61131-3:2025 Programmable controllers – Part 3: Programming languages
For general information about hazardous-energy control in United States general industry, see: OSHA Lockout/Tagout Tutorial
Linked Learning Areas
aiMOOC Projects
.jpg){kind=link}
MOOCwiki · Deutsch
Nach dem Lernen ist vor dem Lernen
Entdecke direkt den nächsten Lernkurs. Weitere Inhalte erscheinen, wenn Du weiter nach unten scrollst.
Zur MOOCwiki-HauptseiteMediathek
Mediathek
Mediathek wird aus dem Wiki geladen ...
Keine passenden Inhalte gefunden. Bitte ändere Suche oder Filter.