PLC programming languages overview (IEC 61131-3) - Time & Space Complexity
When working with PLC programming languages, it is important to understand how the time to run a program grows as the program or input size increases.
We want to know how the execution time changes when the program uses different language features or structures.
Analyze the time complexity of this simple PLC program using Structured Text.
PROGRAM Example
VAR
i : INT;
sum : INT := 0;
END_VAR
FOR i := 1 TO 100 DO
sum := sum + i;
END_FOR
END_PROGRAM
This program sums numbers from 1 to 100 using a loop.
Look for loops or repeated steps.
- Primary operation: The FOR loop that adds numbers.
- How many times: Exactly 100 times in this example.
The number of additions grows as the loop count grows.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 additions |
| 100 | 100 additions |
| 1000 | 1000 additions |
As the input number increases, the operations increase in a straight line.
Time Complexity: O(n)
This means the time to run grows directly with the size of the input loop count.
[X] Wrong: "The program runs in constant time because the loop count is fixed at 100."
[OK] Correct: If the loop count changes with input size, the time grows with it, so it is not constant time.
Understanding how loops and program structure affect execution time helps you write efficient PLC code and explain your reasoning clearly in discussions.
What if the loop was nested inside another loop of the same size? How would the time complexity change?
Practice
Solution
Step 1: Recall IEC 61131-3 languages
IEC 61131-3 defines Ladder Diagram, Function Block Diagram, Structured Text, Instruction List, and Sequential Function Chart.Step 2: Identify the language not listed
Python is a general-purpose programming language, not part of IEC 61131-3.Final Answer:
Python -> Option BQuick Check:
IEC 61131-3 excludes Python [OK]
- Confusing general programming languages with PLC languages
- Assuming all text-based languages are included
- Mixing up graphical and text-based languages
Solution
Step 1: Understand Structured Text assignment
In ST, the assignment operator is ':=' and statements end with a semicolon.Step 2: Check each option
Output := Input + 5;uses ':=' and ends with ';' correctly. Others use wrong operators or miss semicolons.Final Answer:
Output := Input + 5; -> Option AQuick Check:
ST assignment uses ':=' and ';' [OK]
- Using '=' instead of ':=' for assignment
- Omitting semicolon at statement end
- Confusing equality '==' with assignment
--[ ]--( )--where the input contact is normally open and connected to output coil, what is the output when the input is OFF?
Solution
Step 1: Understand Ladder Diagram symbols
The normally open contact [ ] closes when input is ON, allowing current to flow to the coil ( ).Step 2: Analyze input OFF condition
When input is OFF, the contact remains open, so no current flows to the coil, output stays OFF.Final Answer:
Output is OFF -> Option DQuick Check:
Open contact means no output current [OK]
- Assuming output is ON when input is OFF
- Confusing normally open with normally closed contacts
- Thinking output toggles without input change
IF Input = TRUE THEN Output := TRUE END_IF
Solution
Step 1: Check Structured Text syntax rules
Each statement must end with a semicolon ';' in ST.Step 2: Inspect the code snippet
The line 'Output := TRUE' lacks a semicolon at the end, causing a syntax error.Final Answer:
Missing semicolon after Output assignment -> Option AQuick Check:
Statements end with ';' in ST [OK]
- Forgetting semicolons after assignments
- Misusing '=' for assignment
- Assuming IF needs parentheses
Solution
Step 1: Understand AND logic in FBD
AND block outputs TRUE only if all inputs are TRUE simultaneously.Step 2: Choose correct block setup
One AND block with both inputs connected directly checks if both inputs are ON together.Final Answer:
One AND block with both inputs connected to it -> Option CQuick Check:
AND block with multiple inputs = simultaneous ON check [OK]
- Using OR blocks instead of AND
- Connecting AND blocks in series unnecessarily
- Using NOT block incorrectly for AND logic
Ready to prove it?
Pass the test and this pattern moves unknown
