IIOT - Module 3
IIOT - Module 3
Protocols Industrial
Automation
By
Kshama Shukla
AP MME
Contents (Iot protocols and security)
• Protocol Standardization for IoT
• M2M and WSN Protocols
• SCADA and RFID Protocols
• Unified Data Standards
• Protocol – Modbus
• KNX, Zigbee
• Network layer
• API key
• Different IIOT Cloud platforms
Protocol Standardization for IoT
• IoT protocols are a crucial part of the IoT technology stack — without them, hardware would be
rendered useless as the IoT protocols enable it to exchange data in a structured and meaningful
way.
• Out of these transferred pieces of data, useful information can be extracted for the end user and
thanks to it, the whole deployment becomes economically profitable, especially in terms of IoT
device management.
• When talking about the Internet of Things, we always think about communication.
• Interaction between sensors, devices, gateways, servers, and user applications is the essential
characteristic that makes the Internet of Things what it is.
• But what enables all this smart stuff to talk and interact are the IoT protocols which can be seen
as languages that the IoT gear uses in order to communicate.
M2M
• SCADA supervisory computers. These control all SCADA processes and are
used to gather data from field devices and to send commands to those
devices to control industrial processes.
• HMI software. This provides a system that consolidates and presents data
from SCADA field devices and enables operators to understand and, if
needed, modify the status of SCADA-controlled processes.
• Communication infrastructure. This enables SCADA supervisory systems to
communicate with field devices and field controllers. This infrastructure
enables SCADA systems to collect data from field devices and to control
those devices.
Features of SCADA Systems
• Data acquisition is a foundation of SCADA systems; sensors collect data and
deliver it to field controllers, which, in turn, feed data to the SCADA
computers.
• Remote control is achieved through the control of field actuators, based on
the data acquired from field sensors.
• Networked data communication enables all SCADA functions. Data
collected from sensors must be transmitted to SCADA field controllers,
which, in turn, communicate with the SCADA supervisory computers; remote
control commands are transmitted back to actuators from the SCADA
supervisory computers.
• Data presentation is achieved through HMIs, which represent current and
historical data to the operators running the SCADA system.
Features of SCADA Systems
• Real-time and historical data are both important parts of the SCADA
system, as they enable users to track current performance against historical
trends.
• Alarms alert SCADA operators to potentially significant conditions in the
system. Alerts can be configured to notify operators when processes are
blocked, when systems are failing, or when other aspects of SCADA
processes need to be stopped, started or adjusted.
• Reporting on SCADA system operations can include reports on system
status, process performance and reports customized to specific uses.
SCADA architecture
• Level 0. The field level includes field devices, such as sensors, used to
forward data relating to field processes and actuators used to control
processes.
• Level 1. The direct control level includes local controllers, such as PLCs and
RTUs, that interface directly with field devices, including accepting data
inputs from sensors and sending commands to field device actuators.
• Level 2. The plant supervisory level includes local supervisory systems that
aggregate data from level controllers and issue commands for those
controllers to carry out.
• Level 3. The production control level includes systemwide supervisory
systems that aggregate data from Level 2 systems to produce ongoing
reporting to the production scheduling level, as well as other site or
regionwide functions, like alerts and reporting.
• Level 4. The production scheduling level includes business systems used to
manage ongoing processes.
What Is the Modbus Protocol?
• Modbus is a request-response protocol implemented using a master-slave
relationship.
• In a master-slave relationship, communication always occurs in pairs—one
device must initiate a request and then wait for a response—and the
initiating device (the master) is responsible for initiating every interaction.
• Typically, the master is a human machine interface (HMI) or Supervisory
Control and Data Acquisition (SCADA) system and the slave is a sensor,
programmable logic controller (PLC), or programmable automation
controller (PAC).
• The content of these requests and responses, and the network layers across
which these messages are sent, are defined by the different layers of the
protocol.
MODBUS
• The most commonly used form of Modbus protocol is RTU over RS-485.
• Modbus RTU is a relatively simple serial protocol that can be transmitted via
traditional UART technology.
• Data is transmitted in 8-bit bytes, one bit at a time, at baud rates ranging
from 1200 bits per second (baud) to 115200 bits per second.
• The majority of Modbus RTU devices only support speeds up to 38400 bits
per second.
MODBUS
• A Modbus RTU network has one Master and one or more Slaves.
• Each slave has a unique 8-bit device address or unit number.
• Packets sent by the master include the address of the slave the message is
intended for.
• The slave must respond only if its address is recognized, and must respond
within a certain time period or the master will call it a "no response" error.
• Each exchange of data consists of a request from the master, followed by a
response from the slave.
• Each data packet, whether request or response, begins with the device
address or slave address, followed by function code, followed by parameters
defining what is being asked for or provided.
• The exact formats of the request and response are documented in detail in
the Modbus protocol specification.
• The general outline of each request and response is illustrated below.
• https://www.renkeer.com/modbus-protocol-and-its-types/
WSN Protocols