PLC-to-SCADA communication in PLC Programming - Mini Project: Build & Apply

PLC-to-SCADA Communication Setup

📖 Scenario: You are working in an industrial plant where a PLC (Programmable Logic Controller) controls a conveyor belt. The plant uses a SCADA (Supervisory Control and Data Acquisition) system to monitor and control the PLC remotely. Your task is to set up a simple communication program in the PLC that sends the conveyor belt status to the SCADA system.

🎯 Goal: Build a PLC program that creates a data structure to hold conveyor status, configures a communication address, updates the status based on a condition, and outputs the status for SCADA to read.

📋 What You'll Learn

Create a variable to hold conveyor belt status

Define a communication address variable

Use a conditional statement to update the conveyor status

Output the conveyor status for SCADA monitoring

💡 Why This Matters

🌍 Real World

This project simulates how PLCs communicate real-time status to SCADA systems in factories to enable remote monitoring and control.

💼 Career

Understanding PLC-to-SCADA communication is essential for automation engineers and technicians working in industrial control and monitoring.

1

Create Conveyor Status Variable

Create a BOOL variable called ConveyorRunning and set it to FALSE to represent the conveyor belt status.

PLC Programming

# Create a BOOL variable ConveyorRunning and set it to FALSE
# Your code here

Hint

Use the BOOL data type and initialize the variable to FALSE.

2

Define Communication Address

Create a STRING variable called SCADA_Address and set it to "192.168.1.100" to represent the SCADA system IP address.

PLC Programming

ConveyorRunning : BOOL := FALSE;
# Create a STRING variable SCADA_Address and set it to "192.168.1.100"
# Your code here

Hint

Use the STRING data type and assign the IP address as a string.

3

Update Conveyor Status Based on Condition

Write an IF statement that sets ConveyorRunning to TRUE if a BOOL input variable StartButton is TRUE, otherwise set it to FALSE.

PLC Programming

ConveyorRunning : BOOL := FALSE;
SCADA_Address : STRING := "192.168.1.100";
# Write an IF statement to update ConveyorRunning based on StartButton
# Your code here

Hint

Use the IF...THEN...ELSE...END_IF structure to check StartButton and set ConveyorRunning.

4

Output Conveyor Status for SCADA

Write a statement to assign ConveyorRunning to an output variable SCADA_ConveyorStatus so the SCADA system can read the conveyor status.

PLC Programming

ConveyorRunning : BOOL := FALSE;
SCADA_Address : STRING := "192.168.1.100";

IF StartButton THEN
    ConveyorRunning := TRUE;
ELSE
    ConveyorRunning := FALSE;
END_IF;

# Assign ConveyorRunning to SCADA_ConveyorStatus output variable
# Your code here

Hint

Assign the ConveyorRunning variable to SCADA_ConveyorStatus to share the status.

Practice

1. What is the main purpose of PLC-to-SCADA communication?

easy

A. To program the PLC hardware directly

B. To replace the PLC with a SCADA system

C. To allow remote control and monitoring of machines

D. To connect two PLCs without a SCADA system

Solution

1. Step 1: Understand the role of PLC and SCADA

   PLC controls machines locally, SCADA monitors and controls remotely.

2. Step 2: Identify communication purpose

   Communication enables SCADA to read data and send commands to PLC for remote control.

3. Final Answer:

   To allow remote control and monitoring of machines -> Option C

4. Quick Check:

   PLC-to-SCADA communication = remote control and monitoring [OK]

Hint: Think: Who controls and who monitors remotely? [OK]

Common Mistakes:

• Confusing PLC programming with communication
• Thinking SCADA replaces PLC
• Assuming PLCs communicate without SCADA

2. Which of the following is a common protocol used for PLC-to-SCADA communication?

easy

A. Modbus

B. FTP

C. HTTP

D. SMTP

Solution

1. Step 1: Recall common industrial communication protocols

   Modbus and OPC UA are widely used for PLC-to-SCADA data exchange.

2. Step 2: Identify correct protocol from options

   Modbus is a standard protocol for PLC communication; HTTP, FTP, SMTP are not typical for this use.

3. Final Answer:

   Modbus -> Option A

4. Quick Check:

   Industrial protocol for PLC-SCADA = Modbus [OK]

Hint: Industrial control uses Modbus, not web or email protocols [OK]

Common Mistakes:

• Choosing HTTP thinking it's for all network communication
• Confusing FTP or SMTP with control protocols
• Not knowing Modbus is designed for industrial use

3. Given this PLC script snippet reading a SCADA command:

IF SCADA_Command = 1 THEN
  Motor_Start := TRUE;
ELSE
  Motor_Start := FALSE;
END_IF;

What will be the value of Motor_Start if SCADA_Command is 0?

medium

A. Error

B. TRUE

C. 1

D. FALSE

Solution

1. Step 1: Analyze the IF condition

   The condition checks if SCADA_Command equals 1; if true, Motor_Start is TRUE.

2. Step 2: Evaluate with SCADA_Command = 0

   Since 0 is not equal to 1, ELSE branch runs, setting Motor_Start to FALSE.

3. Final Answer:

   FALSE -> Option D

4. Quick Check:

   SCADA_Command=0 means Motor_Start=FALSE [OK]

Hint: IF equals 1? No? Then FALSE [OK]

Common Mistakes:

• Assuming Motor_Start stays TRUE by default
• Confusing numeric 0 with TRUE
• Expecting error due to zero value

4. Identify the error in this PLC-to-SCADA communication snippet:

IF SCADA_Status = TRUE THEN
  Alarm := TRUE
ELSE
  Alarm := FALSE;
END_IF;

medium

A. Missing semicolon after Alarm := TRUE

B. Incorrect use of ELSE statement

C. SCADA_Status should be compared to 1, not TRUE

D. END_IF is not needed

Solution

1. Step 1: Check statement syntax

   Each assignment must end with a semicolon in PLC languages.

2. Step 2: Locate missing semicolon

   Alarm := TRUE line lacks a semicolon at the end, causing syntax error.

3. Final Answer:

   Missing semicolon after Alarm := TRUE -> Option A

4. Quick Check:

   Semicolon missing after assignment = syntax error [OK]

Hint: Every assignment needs a semicolon [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Thinking ELSE syntax is wrong
• Confusing boolean TRUE with numeric 1

5. You want to send a temperature value from PLC to SCADA every 5 seconds using Modbus. Which approach is best?

hard

A. Send temperature as a string message over HTTP every 5 seconds

B. Write temperature to a Modbus register and update it every 5 seconds

C. Use SCADA to poll the PLC once and never update

D. Send temperature only when it changes, ignoring timing

Solution

1. Step 1: Understand Modbus data exchange

   Modbus uses registers to hold data; PLC writes values, SCADA reads them.

2. Step 2: Choose update method for regular timing

   Writing temperature to a register and updating every 5 seconds ensures SCADA gets fresh data regularly.

3. Final Answer:

   Write temperature to a Modbus register and update it every 5 seconds -> Option B

4. Quick Check:

   Regular register update = reliable Modbus communication [OK]

Hint: Use Modbus registers for periodic data updates [OK]

Common Mistakes:

• Using HTTP which is not standard for PLC-Modbus
• Polling only once misses updates
• Ignoring timing causes stale data