Redes de Comunicación

Industrial
How are they grouped?
AS-Interface
 AS-Interface

• Milestones

First Systems in First products

USE Safety at Work

1990 1994 1998 2001

AS-Interface New functionality

The Idea Analogue data transfer,
62 Slaves, Diagnosis

AS-International Association 4
 AS-Interface

• AS-Interface worldwide

AS-Interface AS-Interface
 Belgium  Japan
 China  Netherlands
 France 2003
Worldwide
 Sweden
1991 more than
 Germany 11 members founding
270 members  Switzerland
 Great Britain  USA
 Italy

AS-International Association
 AS-Interface

• Performance characteristics
• Response time
• Message length
• Message live
time
• Message rate
• Device diversity

AS-International Association
 AS-Interface

• Performance characteristics

response time message message

length live time

>s 1/h MByte 1 Years

Control level

Field / device level

Actuator-/Sensor level
ms 100/s Bit >100 ms

message rate device diversity

AS-International Association
 AS-Interface
• Data and energy on one 2-wire cable
• Supply up to 8A
• Inductive Sensors
• Optical Sensors
• Capacitive Sensors
• Magnetic valves
• .....
• Connection technology
• Penetration technology
• High protection class
available (IP 67, IP 68,
IP 69K)

Electro mechanic

Penetration connectors
Reverse polarity protection
AS-International Association
 AS-Interface
• Decentralized Elements
• Modular mounting
• Master Slave system

AS-International Association
 AS-Interface

• Network topology
Line Star Tree
Control unit Control unit Control unit
Master Master Master

Slave

Slave Slave
Slave
Slave
Slave Slave Slave
Slave
Slave
Slave
Slave
Slave Slave
Slave
Slave
Slave

Slave
Slave Slave Slave Slave
Slave

Slave Slave Slave Slave Slave Slave Slave Slave Slave

AS-International Association
 AS-Interface

AS-International Association
 AS-Interface

• AS-Interface communication
• Cyclical polling
• Profiles
• Manufacturer independent exchangeability
• Simple access to the control unit

AS-International Association
 AS-Interface

AS-International Association
 AS-Interface
AS-Interface communication
 Master call  Slave response
- Start bit, control bit, - Start bit,
address 5 bit, Information 4 bit,
Information 5 bit, Parity bit, End bit
Parity Bit, End bit

AS-International Association
 AS-Interface: Protocol Version History

As-I has continued to improve over the years and has resulted in
several versions of the communication protocol. AS-Interface has
been careful to revise the standards to allow for improvements
without adversely affecting current users or products/systems that
are of older versions. They have made these versions both forward
and backward compatible. Here are some of the key differences:
• 2.0-This is the first version of AS-i that had significant usage in the
process industries. It featured 31 device and only discrete device
profiles were possible (4 bits per device)
• 2.1-This version added the capability for up to 8bits of discrete I/O
and also analog I/O profiles. This version also allowed for optional
extended addressing feature (A/B slaves) so that up to 62 devices
could be on a single AS-interface network
• 3.0-This version allows for many new device profiles for greater
flexibility

AS-International Association
 AS-Interface: Protocol Version History
The new ASi-5 standard links the commonly available actuators and
sensors of the lower fieldbus level to the upper Ethernet based level
even more efficiently, flexibly, and reliably. The facts prove this:
• Cycle times are four times shorter with 1.2 ms for 24 connected
devices
• Data width of 16 bit to 32 byte per device
• Twice the network length with 200 m per segment
• Up to 96 connected devices
• Additional diagnostics channel concurrent to the process data
Furthermore, ASi-5 is a strictly deterministic system: Inputs and
outputs can be prioritized up to 1.2 ms.

https://www.as-interface.net
Source:
Modbus Organization
 Modbus
Modbus is an industrial protocol standard that was created by
Modicon, now Schneider Electric, in the late 1970’s for
communication among programmable logic controllers (PLCs).
Modbus protocol is defined as a master/slave protocol, meaning a
device operating as a master will poll one or more devices operating
as a slave. This means a slave device cannot volunteer information;
it must wait to be asked for it. The master will write data to a slave
device’s registers, and read data from a slave device’s registers. A
register address or register reference is always in the context of the
slave’s registers.

Source:
Modbus Organization
Modbus OSI Model
Modbus Topology
Bus Topology is the most used in Modbus RTU, Modbus TCP can
implement all topologies as Ethernet networks.
Modbus Features
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

Typical Transmision rates are: 9600 bps and 19.2 Kbps.

Logically you can address over 250 devices; however, the RS-485
transceivers are not capable of physically driving that many devices.
Modbus protocol states that the limit is 32 devices, and most RS-
485 transceivers will agree with this. Only if all devices on the
network have low load transceivers can you have more than 32
devices.
Serial Transmission modes
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.
Modbus ASCII is an older implementation that contains all of the
elements of an RTU packet, but expressed entirely in printable
ASCII characters. Modbus ASCII is considered deprecated, is rarely
used any more, and is not included in the formal Modbus protocol
specification.
Modbus TCP
Modbus TCP encapsulates Modbus RTU request and response data
packets in a TCP packet transmitted over standard Ethernet
networks. The unit number is still included and its interpretation
varies by application – the unit or slave address is not the primary
means of addressing in TCP. The address of most importance here
is the IP address, e.g. 192.168.1.100. The standard port for Modbus
TCP is 502, but port number can often be reassigned if desired.
Review of Modbus Register Types
The types of registers referenced in Modbus devices include
the following:
• Coil (Discrete Output)
• Discrete Input (or Status Input)
• Input Register
• Holding Register
Review of Modbus Function Codes
Modbus protocol defines several function codes for accessing
Modbus registers. There are four different data blocks defined by
Modbus, and the addresses or register numbers in each of those
overlap. Therefore, a complete definition of where to find a piece of
data requires both the address (or register number) and function
code (or register type).
PROFIBUS
International

Ð More than 900 members - 23 regional user associations

Product Variety

Drives Controllers
AC Drives PLC/NC/RC Software Drivers
DC Drives DOS/Windows/NT/95
VME, PC Tools
RT-OS/OS9/VRTX
Workstation Configuration
VxWorks/PSOS+
Bus Monitor
OS2, QNX
Decentralized I/O Engineering
UNIX/VMS
Binary I/O Network components
Analog I/O Repeaters
Services
Fiber optics
Host Interfaces
Regulators Development Support
VAX computers
Timer Cables Implementation Support
VME computers
Counter Training
MMI
Ident-Systems
Operator Panels Instruments
Level Gateways
Text Displays
Valves
Flow AS-Interface
Pneumatic Valves
Pressure Proprietary networks
Magnetic Valves
Temperature
Profibus Versions
EN 50170 - 2
The PROFIBUS Protocol is in Accordance with the ISO/OSI
Reference Model for Open Systems
• The PROFIBUS Bus Access Method combines
Multi-Master and Master-Slave communications
Bus Access

• The PROFIBUS Bus Access Protocol (Layer 2) is

identical for all three PROFIBUS variations
• This enables transparent communication and easy
combinations of FMS/DP/PA Network sections
• Because FMS/DP use the same Physical Media (RS-
485/FO), they can be combined on the same cable
Bus Access

Hybrid Bus Access Protocol

✓ Token-Passing between Masters
Master - Slave Protocol between Master and Slaves

Master
✓ active stations with the right to control the bus for a
limited amount of time (Token - Hold - Time)

Slave
✓ Slaves only respond on request of a Master - they
have no rights to control the bus
FMS, DP, PA

FMS stands for Fieldbus Messaging System

✓ peer to peer communication

DP stands for Decentralized Periphery

✓ fast data exchange

PA stands for Process Automation

✓ intrinsically safe environment
FMS/DP In Common

• DP and FMS are based on same Layer 1 and 2:

✓ DP and FMS can be operated on the same bus
✓ Message header and data length are identical
✓ The bus physics are identical

• One master can service several slaves

• Several masters can participate on the bus
• Baudrates from 9.6 kBd up to 12 MBd are
possible
FMS/DP In Common

• Data transmission can be between 1 and 244 bytes

• 126 stations can be connected
• System can consist of several segments
• 32 stations (RS 485 drivers) per segment
• Common components
✓ Cabling, connectors, repeater, fibre optic

• Savings in maintenance and spare parts inventory

PA/DP In Common

• DP and PA are based on the same protocol

definition - DP/V1 (extended DP)
✓ DP and PA can use the same master systems
✓ Message header and data length are identical
✓ Configuration tools are the same
✓ Data transmission can be between 1 and 244 bytes
PA/DP In Common
FMS Features

• FMS is optimized for universal, object oriented

communication of intelligent master devices at the
cell level
• FMS permits a subset of the MMS-Functions
(Manufacturing Message Specification, ISO 9506)
• A slave can be assigned to several masters
✓ Several masters can write to the same slave

• Communication connections can be temporary or

permanent
• Communication is defined in a communication
relation list
FMS Features

• FMS access procedure

Slave 1 Slave 2 Slave 3 Slave x

PA Features

• Based on the extended PROFIBUS-DP Protocol

and IEC 1158-2 Transmission
✓ Suitable to replace today's 4...20 mA Technology
✓ Only two wires for data and power
✓ Connects Instruments to the control system via a serial
bus
✓ Functional improvements plus reliable serial digital
transmission
✓ Control, regulation and monitoring via a simple twisted pair
cable
✓ A single engineering tool for all devices
PA Features

Typical System Configuration with PROFIBUS-PA

DP Features

• DP communication is permanent and cyclic

• The transmitted data is specified during the
configuration (optimized data exchange)
• Only one master can write outputs (safety aspect)
• Data can be read by controlling and Class 2 master
• Acyclic data via DPV1 functions
• Alarm acknowledgment
• Fastest fieldbus system (up to 12 MBaud)
• Up to 244 byte input AND 244 byte output data per
station
DP Features

• DP- Access Procedure

Reliability-DP/FMS

• Hamming Distance HD = 4
• HD 4 means, that up to 3 transmission failures at a
time can be detected (done by the ASICs)
✓ By detecting a faulty telegram, it will be resent
automatically without affecting other existing stations
• HD 4 is a term used to describe the reliability of the
data transmission on the Profibus network.
✓ Special Start and End Sentinels
✓ Parity Bit for Each Byte
✓ Slip Free
✓ According to IEC 870-5-1
✓ Delimiter Synchronization
PROFIBUS Wiring

• PROFIBUS DP/FMS wiring can be done with:

✓ twisted shielded pair copper cable
✓ fiber optic components
✓ infrared components

• Detailed installation guideline is available

PROFIBUS Wiring

• Twisted shielded pair cable

✓ line parameters are defined in EN 50170
✓ standard cable available from Belden and Siemens
✓ standard connectors available
Baudrate Max. Segment length Max. Expansion
9.6 1000m / 3278feet 10,000m / 32786feet
19.2 1000m / 3278feet 10,000m / 32786feet
93.75 1000m / 3278feet 10,000m / 32786feet
187.5 1000m / 3278feet 10,000m / 32786feet
500.0 400m / 1311feet 4,000m / 13114feet
1,500.0 200m / 655feet 2,000m / 6557feet
3,000.0 100m / 327feet 1,000m / 3270feet
6,000.0 100m / 327feet 1,000m / 3270feet
12,000.0 100m / 327feet 1,000m / 3270feet
max. expansion is done with 9 repeaters in a row
PROFIBUS Wiring

Fiber optic components

✓ plastic and glass fiber optic is available
✓ optical plugs and modules are available

Noise immune potential difference independent longer

distances (up to 20 miles) redundant operating is posible line,
ring and star configuration
PROFIBUS Wiring

Redundancy Improves System Reliability

DP Details

• Class 1 master -
✓ central controller which exchanges data with the
connected I/O devices (slaves)
✓ determines the baudrate
✓ handles the Token
✓ several class1 masters are permitted, typical devices are
PLC, PC
• Class 2 master -
✓ diagnostic and startup tool, typically a configuration tool
✓ can control one slave at a time
• Slave station -
✓ passive station which acknowledges messages or answers
per request
DP Details

Master- master, master- slave communication

a device can consist of multiple functions, e.g.... class1 and class2, class1 and slave
Interoperability

• Open Configuration permits Plug and Play

Device Description

GSD: General Station Data

• GSD file
✓ each slave or master class 1 device on PROFIBUS DP
needs to have a device description file, the characteristic
of each PROFIBUS-DP device is described in the GSD-File
✓ the GSD-file contains all device specific parameters e.g.:
³ Supported Baudrate
³ Supported Message Length
³ Number of input / output data
³ Meaning of diagnostic messages
³ Options for modular devices e.g. which are available

✓ text file (ASCII-format)

✓ each configuration tool relates to the GSD information
Device Description

✓GSD-Files are created by the device vendors

✓the PROFIBUS Trade Organization provides an GSD-Editor
which makes it very easy to create GSD-Files
✓the GSD-Editor contains a GSD-Checker which guarantees
the conformance of the GSD-Files to the PROFIBUS standard
✓a library of GSD-Files is provided at the PROFIBUS web
page: http://www.profibus.com
Source:
https://realpars.com/devicenet/
 DeviceNet
DeviceNet was originally developed by Allen-Bradley which is a
Rockwell Automation brand, and they decided to share this new
technology with others and make it an open network.

Source:
https://realpars.com/devicenet/
 DeviceNet and OSI Model
DeviceNet is based on the Common Industrial Protocol (CIP) and
uses the three upper layers of CIP starting at Session, while the
bottom 4 layers have been adapted to the DeviceNet application.

Source:
https://realpars.com/devicenet/
ODVA
 DeviceNet Cables
The genius behind DeviceNet is that it joined the power and the
signal into one cable, saving money and reducing the need for
multiple cables which utilize more space.

Source:
https://realpars.com/devicenet/
 DeviceNet Data Rates
DeviceNet data rates are 125, 250, or 500 Kilobits per second. The
longer the length needed will result in a slower data rate and vice
versa.

Source:
https://realpars.com/devicenet/
 DeviceNet Topology and Terminating resistors
The topology in Devicenet is Bus (Trunkline with droplines)
The DeviceNet trunkline requires a 121 Ohms, 1 percent, 0.25 Watts
or larger terminating resistor at each end of the trunk and directly
connected across the signal wires (blue and white).
The terminating resistors reduce electrical noise and without them,
in their correct place, the DeviceNet will not work properly.

Source:
https://realpars.com/devicenet/
 RSNetWorx for DeviceNet
Allen Bradley developed “RSNetWorx” for DeviceNet to be able to
“map” and “assign addresses” to all the devices in the network.
DeviceNet uses Electronic Data Sheets (EDS) that are simple text
files that contain all the information to identify a device and assist in
commissioning them onto the network.

Source:
https://realpars.com/devicenet/
Source:
www.fieldbus.org
What is Fieldbus?
 A fieldbus is an all-digital, serial two-way, multi-drop
communication System.
 H1 (31.25kbps) interconnects field equipment (Sensors,
Actuators & I/O).
 HSE (High Speed Ethernet, 100mbps) provides
integration of high speed controllers, subsystems (via
Linking Device) and data servers and workstation.
Integrated Architecture

 Management Information Systems (MIS),

Enterprise Resource Planning (ERP), and
Human Machine Interface (HMI) access the H1
Fieldbus information via the Data Servers.

MIS Business Enterprise

ERP and
HMI Plant Application
Packages

HSE Network
H1 and HSE
Factory/Plant
Instrumentation and
H1-Fieldbus Control devices
H1 Overview
Multiple Variables
 Fieldbus allows “multiple variables” from each device to be brought
into the control system for archiving, trend analysis, process
optimization, reporting, predictive maintenance and for asset
management.
 Fieldbus distortion-free characteristics digital communication enables
improved control capability which can improve product yields.
Diagnostics

 Self Diagnostics and communication capabilities of

microprocessor based fieldbus devices helps reduce
downtime and improve plant safety.
 Plant operation and Maintenance personnel can be
notified and corrective actions taken quickly and safely.

Control System Network HSE

Analog Controller Fieldbus Controller

PV
PV , Mode , Variables , Alarm
Diagnostics , Etc
4-20mA I/O Subsystem
H1

Traditional 4-20mA View stops at I/O Subsystem Fieldbus Extends View to Field Instrument
Control Strategy
 Standard Function Blocks is used to implement the Control Strategy.
 Many control system functions such as AI, PID and AO can be
performed by the field device through the use of these Standard
Function Blocks.
 Distribution of control into field devices can reduced the amount of
hardware and cabinet footprint needed.

Control System Network HSE

PID

Analog Controller Fieldbus Controller

PV
PV , Mode , Variables , Alarm
I/O Subsystem
Diagnostics , Etc
4-20mA AI AO H1

AI AO PID

Traditional Control and I/O requires extra hardware Fieldbus Extends Control and I/O to Field Instrument
H1 Technology
H1 Physics
 Multi-Drop wire pair with Power and Signal on same cable.
 Support Intrinsic Safety.
 Function Blocks built into Field Devices.
 Control on the Wire – single loop integrity
 Distance up to 1900 meters
 Add Repeaters to extend > 1900 meters
 Max. of 4 repeaters can be used to a maximum distance of 9500
meters

Fieldbus Signal
HSE

H1Digital Signal H1 Digital Signal

R

Freedom to Ch19o0o0sme.etPeroswerto Integrate. Distance > 1900 meters

Intrinsic Safety

Control room Field

Field device

I.S certified devices

Trunk

Power
supply
Conditioner T T

Wiring block

I.S Interface
Host
Control
System

I.S certified devices

EDDL and CFF Files

 Field Devices will consists of:

– Actual Physical Device. DD & CFF
– Device Description (DD). Configuration
System
– Common File Format (CFF).
 DDs and CFFs made by the
Device Supplier www.fieldbus.org
 Parameters and Capabilities
are defined in device files –
DD and CFF
– Defines how device shall be
displayed in the system H1 Network

 Instruments
described with
Device Description
Language
DD and CFF Files

 Device Descriptor (DD) File allow operation of

devices from different suppliers on the same
fieldbus with single host system.
 Common File Format (CFF) is a file which
describes the functions and capabilities of a field
device.
 The CFF file is used in conjunction with the
Device Descriptor file to enable a host system to
configure the system off-line.
 CFF files are standard ASCII text file.
 Fieldbus Components
Power Supply Workstation HMI

Fieldbus Interface Module

Conditioner Fieldbus Controller

Safe Area (Host)

H1 Bus (Trunk) Hazardous Area (Field)

Terminator
Terminator
Junction Box

H1 Bus Wire (Spurs)

Freedom to Choose. Power to Integrate. 73
Transmitters
Transmitters Analyzer
Analyzer
Actuator
Actuator Valve
Resource Block
 The Resource Block describes characteristics of the fieldbus device
such as device name, manufacturer and serial number, etc.
 There is only one Resource Block in a device.

FIM H1 link interfaces

Device
Transducer block

Resource block
Device

Control Builder Project tab

Freedom to Choose. Power to Integrate.
Transducer Block
 Transducer Blocks are used to configure devices.
 Transducer Blocks are required to Read sensors value
and command output value.

FIM H1 link interfaces

Device
Transducer block

Resource block
Device

Control Builder Project tab

Freedom to Choose. Power to Integrate.
Function Blocks
 The Control System Strategy is built using Function Blocks.
 Input and output parameters of Function Blocks can be linked over
the fieldbus.
 The execution of each Function Blocks is precisely scheduled and
there can be many function blocks in a single user application.

AI Block PID Block

AO Block

FreedomFreedom tooChoose.Choose.
PowerPowertoto Integrate.Integrate.
Standard Function Blocks

Function Blocks Function Blocks Function Blocks

Analog Input Device Control Multiple Analog Input
Analog Output Output Splitter Multiple Analog Output
Bias/Gain Signal Characterizer
Multiple Discrete Input
Control Selector Lead Lag
Multiple Discrete Output
Discrete Input Deadtime

Discrete Output Integrator (Totalizer)

Setpoint
Manual Loader
Ramp
Proportional/Derivative Generator
Proportional/Integral Input Selector
/Derivative Arithmetic
Ratio Timer
Analog Alarm
Thanks for coming