Reusable code patterns in PLC Programming - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a reusable function block named 'Counter'.

PLC Programming

FUNCTION_BLOCK [1]
VAR
    Count: INT;
END_VAR
END_FUNCTION_BLOCK

Drag options to blanks, or click blank then click option'

ATimer

BMotorControl

CCounter

DSensorInput

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic or unrelated name like 'Timer' or 'MotorControl'.

The function block is named 'Counter' to create a reusable counting block.

2fill in blank

medium

Complete the code to call the reusable function block 'Counter' and increment its count.

PLC Programming

VAR
    MyCounter: [1];
END_VAR
MyCounter.Count := MyCounter.Count + 1;

Drag options to blanks, or click blank then click option'

ACounter

BTimer

CSensor

DActuator

Attempts:

3 left

💡 Hint

Common Mistakes

Declaring the variable with an unrelated type like 'Timer' or 'Sensor'.

The variable 'MyCounter' is declared as type 'Counter' to use the reusable block.

3fill in blank

hard

Fix the error in the function block call to correctly reset the counter.

PLC Programming

IF ResetSignal THEN
    MyCounter.[1] := 0;
END_IF

Drag options to blanks, or click blank then click option'

AStart

BEnable

CReset

DCount

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to reset a non-existent 'Reset' or 'Start' variable.

The 'Count' variable inside the 'MyCounter' block is reset to zero.

4fill in blank

hard

Fill both blanks to create a reusable function block that toggles a boolean output.

PLC Programming

FUNCTION_BLOCK [1]
VAR
    Output: BOOL := [2];
END_VAR
END_FUNCTION_BLOCK

Drag options to blanks, or click blank then click option'

AToggleBlock

BTRUE

CFALSE

DCounterBlock

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated block names or initializing the output to TRUE.

The function block is named 'ToggleBlock' and the boolean output is initialized to FALSE.

5fill in blank

hard

Fill all three blanks to define a reusable function block with an integer input, output, and a method to double the input.

PLC Programming

FUNCTION_BLOCK [1]
VAR_INPUT
    InputValue: INT;
END_VAR
VAR_OUTPUT
    OutputValue: INT;
END_VAR
METHOD DoubleInput : VOID
BEGIN
    OutputValue := InputValue [2] [3];
END_METHOD
END_FUNCTION_BLOCK

Drag options to blanks, or click blank then click option'

ADoubleBlock

B*

C2

D+

Attempts:

3 left

💡 Hint

Common Mistakes

Using addition instead of multiplication.

Incorrect block names.

The block is named 'DoubleBlock'. The method doubles the input by multiplying by 2.

Practice

1. What is the main benefit of using FUNCTION_BLOCK in PLC programming?

easy

A. It creates a graphical interface for the PLC.

B. It makes the program run faster by using less memory.

C. It automatically fixes errors in the code.

D. It allows you to reuse code and simplify program management.

Solution

1. Step 1: Understand the purpose of FUNCTION_BLOCK

   FUNCTION_BLOCK is designed to package code that can be reused multiple times in a PLC program.

2. Step 2: Identify the main benefit

   Reusing code saves time and makes the program easier to manage and maintain.

3. Final Answer:

   It allows you to reuse code and simplify program management. -> Option D

4. Quick Check:

   Reusable code = Simplify management [OK]

Hint: FUNCTION_BLOCK means reusable code blocks [OK]

Common Mistakes:

• Thinking FUNCTION_BLOCK speeds up execution
• Believing it fixes errors automatically
• Confusing it with user interface creation

2. Which of the following is the correct way to declare a FUNCTION_BLOCK named Counter in PLC programming?

easy

A. FUNCTION Counter
VAR_INPUT
Count: INT;
END_VAR
END_FUNCTION

B. FUNCTION_BLOCK Counter
VAR_INPUT
Count: INT;
END_VAR
END_FUNCTION_BLOCK

C. FUNCTION_BLOCK Counter()
VAR_INPUT
Count: INT;
END_VAR
END_FUNCTION_BLOCK

D. FUNCTION_BLOCK Counter
VAR_OUTPUT
Count: INT;
END_VAR
END_FUNCTION_BLOCK

Solution

1. Step 1: Identify correct FUNCTION_BLOCK syntax

   FUNCTION_BLOCK declaration starts with 'FUNCTION_BLOCK Name' and ends with 'END_FUNCTION_BLOCK'. Inputs are declared inside VAR_INPUT.

2. Step 2: Check each option

   FUNCTION_BLOCK Counter VAR_INPUT Count: INT; END_VAR END_FUNCTION_BLOCK correctly declares FUNCTION_BLOCK Counter with VAR_INPUT and ends properly. FUNCTION Counter VAR_INPUT Count: INT; END_VAR END_FUNCTION uses FUNCTION instead of FUNCTION_BLOCK. FUNCTION_BLOCK Counter() VAR_INPUT Count: INT; END_VAR END_FUNCTION_BLOCK adds parentheses which are not used. FUNCTION_BLOCK Counter VAR_OUTPUT Count: INT; END_VAR END_FUNCTION_BLOCK uses VAR_OUTPUT instead of VAR_INPUT for input variable.

3. Final Answer:

   FUNCTION_BLOCK Counter VAR_INPUT Count: INT; END_VAR END_FUNCTION_BLOCK -> Option B

4. Quick Check:

   Correct FUNCTION_BLOCK syntax = FUNCTION_BLOCK Counter VAR_INPUT Count: INT; END_VAR END_FUNCTION_BLOCK [OK]

Hint: FUNCTION_BLOCK uses VAR_INPUT for inputs, no parentheses [OK]

Common Mistakes:

• Using FUNCTION instead of FUNCTION_BLOCK
• Adding parentheses after FUNCTION_BLOCK name
• Declaring inputs under VAR_OUTPUT

3. Given this FUNCTION_BLOCK code snippet, what will be the output value of Result after execution?

FUNCTION_BLOCK AddTwo
VAR_INPUT
A: INT;
B: INT;
END_VAR
VAR_OUTPUT
Result: INT;
END_VAR
Result := A + B;
END_FUNCTION_BLOCK

// Usage
AddTwoInstance: AddTwo;
AddTwoInstance.A := 3;
AddTwoInstance.B := 5;
// Execute block
// What is AddTwoInstance.Result?

medium

A. 8

B. 35

C. 0

D. Error: Result not assigned

Solution

1. Step 1: Understand the FUNCTION_BLOCK logic

   The block adds inputs A and B and stores the sum in Result.

2. Step 2: Substitute input values and calculate

   A = 3, B = 5, so Result = 3 + 5 = 8.

3. Final Answer:

   8 -> Option A

4. Quick Check:

   3 + 5 = 8 [OK]

Hint: Add inputs to get output Result [OK]

Common Mistakes:

• Concatenating numbers as strings
• Assuming Result is zero by default
• Thinking Result is not assigned automatically

4. Identify the error in this FUNCTION_BLOCK code snippet:

FUNCTION_BLOCK Multiply
VAR_INPUT
X: INT;
Y: INT;
END_VAR
VAR_OUTPUT
Product: INT;
END_VAR
Product = X * Y;
END_FUNCTION_BLOCK

medium

A. Incorrect use of '=' instead of ':=' for assignment.

B. VAR_OUTPUT should be declared before VAR_INPUT.

C. Missing semicolon at the end of the assignment line.

D. FUNCTION_BLOCK name must be lowercase.

Solution

1. Step 1: Check assignment syntax in FUNCTION_BLOCK

   In PLC programming, assignment uses ':=' not '='.

2. Step 2: Verify other syntax elements

   Semicolon is present. VAR_INPUT before VAR_OUTPUT is correct. FUNCTION_BLOCK names are case-sensitive but uppercase is allowed.

3. Final Answer:

   Incorrect use of '=' instead of ':=' for assignment. -> Option A

4. Quick Check:

   Use ':=' for assignment [OK]

Hint: Use ':=' for assignments in PLC code [OK]

Common Mistakes:

• Using '=' instead of ':='
• Thinking semicolon is optional
• Believing VAR_OUTPUT must come first

5. You want to create a reusable FUNCTION_BLOCK that counts how many times an input boolean Trigger changes from FALSE to TRUE. Which approach correctly implements this behavior?

hard

A. Reset the counter to zero every time Trigger is TRUE.

B. Increment the counter every time the FUNCTION_BLOCK runs regardless of Trigger state.

C. Use a VAR to store previous Trigger state and increment a counter only when Trigger changes from FALSE to TRUE.

D. Use VAR_INPUT to store the counter and increment it inside the block.

Solution

1. Step 1: Understand the counting condition

   The counter should increase only when Trigger changes from FALSE to TRUE (rising edge).

2. Step 2: Implement edge detection logic

   Store previous Trigger state in a VAR variable. Compare current and previous states. Increment counter only if previous was FALSE and current is TRUE.

3. Final Answer:

   Use a VAR to store previous Trigger state and increment a counter only when Trigger changes from FALSE to TRUE. -> Option C

4. Quick Check:

   Edge detection needs previous state storage [OK]

Hint: Store previous input to detect rising edge [OK]

Common Mistakes:

• Incrementing counter every cycle
• Resetting counter incorrectly
• Using VAR_INPUT for internal state