Decentral Field Devices PROFINET IO

PROFINET IO
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
1
Decentral Field Devices
© PNCC Burgdorf
PROFINET IO System
PROFINET - a modular technology
1
Process
Automation
MES
Functional scope
Device
Designations
Device Model
Data Exchange
Interbus
Integration
Motion
Control
WLAN
Safety
Communication
Diagnosis
Fieldbus
Integration
PROFIBUS
Integration
Decentralized
Periphery
Test +
Certification
WEB
Integration
Train
Application
2
Distributed
Automation
Network
Installation
Network
Management
© PNCC Burgdorf
Real-time
Communication
Security
PROFINET IO System
2
1
PROFINET and ISO/OSI-Model
ISO/OSI
Functional scope
Device
Designations
7b
PROFINET IO Services
PROFINET IO Protocol
7a
Connectionless
RPC
DCOM
Connection
oriented
RPC
empty
empty
4
UDP(RFC
768)
TCP(RFC
793)
3
IP (RFC 791)
Device Model
Data Exchange
Communication
6
Diagnosis
Fieldbus
Integration
PROFINET CBA acc.
to IEC 61158 Type 10
5
2
Real-Time Enhancements acc. To IEC 61784-2
IEEE802.3,Full-Duplex,IEEE802.1Q,Priority Tagging
1
IEEE 802.3 100 Base TX , 100 Base FX
3
© PNCC Burgdorf
PROFINET IO System
3
Functional Scope
PROFINET CBA
Functional scope
PROFINET IO
Device
Designations
Device Model
WEB-Services
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
KomponentenBasierte
Kommunikation
Fill
Fill
4
IRT
Real-Time
© PNCC Burgdorf
PROFINET IO System
4
2
What is PROFINET IO ?
PROFINET
PROFINET IO
IO is
is
Decentral
Decentral Periphery
Periphery with
with
Ethernet
Ethernet connection
connection and
and
PROFINET
PROFINET communication.
communication.
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
PROFINET IO uses
Ethernet
z
Communication via Real-Time and
Non Real-Time
z
Device description based on
XML-standard
5
© PNCC Burgdorf
PROFINET IO System
5
How is PROFINET IO implemented?
z
Modular Periphery:
only the bus interface changes
z
Periphery boards can be used
universal
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
Ethernet
z
z
Device Configuration
in well known way
Ethernet
PROFIBUS
6
PLC-User program
in well known way
Flexible integration of decentral field devices on PROFIBUS
and Industrial Ethernet possibleÆ Investment Protection
© PNCC Burgdorf
PROFINET IO System
6
3
Device Designation and their Rolls
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
• PROFINET IO-Controller:
● Data exchange of IO signals to assigned field devices
● Device containing the control program
Diagnosis
Fieldbus
Integration
• PROFINET IO-Device:
● Field Device attached to the IO-Controller
7
• PROFINET IO-Supervisor:
● HMI and Diagnosis Station
© PNCC Burgdorf
PROFINET IO System
7
Device Designation and their Rolls
Functional scope
Device
Designations
e.g. PLC
IO-Controller
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
Programming
Device/PC
PROFINET Supervisor
ƒƒ Diagnosis
Diagnosis
ƒƒ Up/Download
Up/Download
Commissioning,
Commissioning,
Plant
Plant diagnosis
diagnosis
Application
Application program
program
with
with access
access to
to
process
process signals
signals
via
PLC
process
via PLC process
image
image
ƒƒ
ƒƒ
ƒƒ
Configuration
Configuration
Production
Production data
data
Alarms
Alarms
Ethernet
ƒƒ
ƒƒ
ƒƒ
Field Device
IO-Device
Diagnosis
Diagnosis
Status/Control
Status/Control
Parameterization
Parameterization
8
Read
Read and
and write
write
IO
IO data
data
© PNCC Burgdorf
PROFINET IO System
8
4
Device Model according to proven Scheme
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
• The PROFINET device model is comparable to
PROFIBUS
● Modules in slots and subslots
● Channel located in modules
• The use of existing IO modules guarantees investment
protection for device manufactures and plant operators
• Modules and submodules are defined in the device
description. They can be assigned to slots and subslots
within the real device
• Every Subslot may have IO-data, Diagnosis-data,
Data
9
blocks, Alarms
© PNCC Burgdorf
PROFINET IO System
9
The PROFINET IO Device Model
Bus Interface can easily be exchanged
Functional scope
Device
Designations
Device Model
BusInterface
Subslot 1
Subslot 2
Subslot 3
Subslot 4
Subslot 1
Subslot 4
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
Slot 0
Slot 1
Subslot 6
Slot 2
Slot 3
10
The subslots are representing the real process
© PNCC Burgdorf
PROFINET IO System
10
5
IO-Controller
Functional scope
Device
Designations
IO-Controller
userprogram
Device Model
Data Exchange
L EW 100
PAE
IO-Device
inputs
Communication
Diagnosis
Fieldbus
Integration
outputs
T AW 200
PAA
11
ƒ The IO-data is stored in the process image
© PNCC Burgdorf
PROFINET IO System
11
Data Exchange between Devices
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
• Every communication is assigned to an Application
Relation
• There is an Application Relation (AR) defined between
IO-Controller/and/or supervisor and IO-Device
• An AR may contain several Communication Relations
(CR´s) for
● acyclic services (i.e. record data CR)
Æconfiguration,read,write
● cyclic services (IO-data CR) Æ process data and
● Alarms (Alarm CR)
12
Every IO-devices shall support 3 AR´s (controller,
supervisor, redundancy)
© PNCC Burgdorf
PROFINET IO System
12
6
Data Exchange between Devices
Functional scope
Device
Designations
Device Model
Data Exchange
Real-Time
Real-Time channel
channel Real-Time channel
Standard
Real-Time channel
Standard channel
channel ƒ Process data
ƒ Process data
ƒƒ Configuration
Configuration
ƒƒ Alarms
Alarms
Communication
Diagnosis
Fieldbus
Integration
Record data CR
IO data CR
Alarm CR
IO-Controller
13
IO-Device
AR
© PNCC Burgdorf
PROFINET IO System
13
The Start-up Phase
Functional scope
Device
Designations
• The Application Relation (IO-AR) between the devices is
set-up by the so called Context Management (CM) via
UDP/IP and RPC (Remote Procedure Call).
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
• This step establishes the communication relation for the
process data (IO data CR) automatically.
● IO-data and update rate and
● Alarms are specified here
IO-Controller
CM
IO-Device
Set-up of the
Communication Relation
© PNCC Burgdorf
14
CM
PROFINET IO System
14
7
The Cyclic Communication of Process Data
Functional scope
Device
Designations
Device Model
Data Exchange
• Subsequently, the process data is transmitted cyclically
between the devices via the real-time channel
• Diagnosis data and alarms are transferred in the acyclic
real-time channel
Communication
Diagnosis
Fieldbus
Integration
IO-Controller
IO-Device
Set-up of the
CM
CM
Communication Relation
15
Process
Data
RT
Driver
RT
Driver
Cyclical process data in Real-time
© PNCC Burgdorf
Process
Data
PROFINET IO System
15
Cyclic Data Exchange
Functional scope
Device
Designations
IO- Data Objects Æ Real Time Data
ƒ Exchange of the cyclic process-data
ƒ Update time is configurable
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
ƒ Characteristics:
ƒ cyclic
ƒ Provider-Consumer-Model
ƒ Unconfirmed
ƒ Configurable update time
ƒ Buffer to buffer
ƒ The user data is accompanied by status informationen
ƒ Data exchange is time controlled
16
Cyclic data exchange already starts after Connect-Frame
© PNCC Burgdorf
PROFINET IO System
16
8
Acyclic Data Exchange (Read and Write Services)
Functional scope
Device
Designations
Record Data Objects Æ Non Real Time Data
ƒ Acyclic data exchange
ƒ Parameterization of IO-Devices,
ƒ Configuration of IO-Devices
ƒ Read status informations
Device Model
Data Exchange
Communication
Diagnosis
ƒCharacteristics:
ƒ Acyclic data exchange
ƒ Bidirectional
ƒ One to one
ƒ Connection oriented
ƒ Queued
ƒ Confirmed
ƒ Monitoring of Repetition with „SequenceCounter“17
Fieldbus
Integration
© PNCC Burgdorf
PROFINET IO System
17
Use of Record Data (Read and Write Services)
Functional scope
ƒ
Diagnosis information can be read from the user from every
device at any time
ƒ
Logbook entries for alarms and error messages
ƒ
Identification informations acc. to PNO-Guideline „I&M
Functions“
ƒ
Information functions about real and logical Module
structures.
ƒ
IO-Data Objects (to read back the IO-data).18
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
© PNCC Burgdorf
PROFINET IO System
18
9
The Start Up Sequence
IO Device
Establish
Provider/ Consumer /
Alarm -State machine
Start Provider
IO Controller
Connect .req ()
Functional scope
Connect .rsp (+)
Device
Designations
IO Controller
Timeout
Write _ Record .req ()
Establish
Provider/ Consumer /
Alarm - State machine
Start Provider
Start Consumer with
Monitoring
Device Model
Data Exchange
Communication
-
Write _ Record .rsp (+)
Write_ Record .req ()
Start Consumer
with Monitoring
Write_ Record .rsp (+)
Diagnosis
Fieldbus
Integration
DControl .req ()
Start Alarm State machine
DControl .rsp (+)
CControl .req ()
CControlrsp ()
Start Alarm State machine
19
Outputs
Inputs
© PNCC Burgdorf
PROFINET IO System
19
Quick Error Localization through Structured Error Information
• The diagnostic information is structured hierarchically
Functional scope
Device
Designations
Device Model
Data Exchange
● Station name, slot, subslot, channel, channel type, error
information
• SNMP completes the diagnosis with network information
Communication
Layer
Layer 1:
1: Failure
Failure in
in Device
Device
Diagnosis
(e.g.
(e.g. Valve
Valve Station
Station 2)
2)
Fieldbus
Integration
Layer
Layer 2:
2: Failure
Failure in
in Module
Module
(e.g.
(e.g. Analog
Analog Input
Input Module
Module 3)
3)
subslot
SF
BF
ON
Channel
Kanal 0 0
Channel
Kanal
0 0 Kanal 0
Channel
Channel
Kanal 1 1 Kanal
1 1 Kanal 1
Channel
Kanal 2 2 Kanal
2 2 Kanal 2
Channel
...
...
...
Network
Network
Diagnosis
Channel
Kanal x xDiagnosis
Kanal
Channel
x x Kanal
Channel
x
x
Slot 1
Slot 2
Layer
Layer 3:
3: Failure
Failure in
in Sub
Sub
Module
Module
20
Layer
Layer 4:
4: Failure
Failure in
in Channel
Channel
(e.g.
(e.g. Cable
Cable Break
Break in
in Channel
Channel 2)
2)
Slot 3
© PNCC Burgdorf
PROFINET IO System
20
10
Diagnosis there, where it is needed
Functional scope
Device
Designations
Device Model
Data Exchange
• Diagnosis information is transmitted as alarm from
the IO-Device to the IO-Controller
● The alarm triggers a reaction in the PLC program
• IO-Supervisor gets the diagnosis information directly
from the IO-Device
Communication
● Display diagnosis information on service PG or HMI station
Diagnosis
Fieldbus
Integration
IO-Controller
Supervisor
Display
Display on
on
PG/HMI
PG/HMI
Error
Error Routine
Routine
in
in IO-Controller
IO-Controller
21
Ethernet
Read
Read diagnosis
diagnosis directly
directly
from
from IO-Device
IO-Device
Diagnosis
Diagnosis
information
information
IO-Device
© PNCC Burgdorf
PROFINET IO System
21
Network Diagnosis
IO-Controller
IO-Controller
Functional scope
Device
Designations
Device Model
2
1
Data Exchange
Communication
IO-Device3
Diagnosis
Fieldbus
Integration
IO-Device1
z
IO-Device2
The switch passes the
PROFINET-Diagnosis from the
IO-Devices to the Controller
IO-Device2
IO-Device1
22
Switch is configured as
IO-Device (GSDML)
Switch reports Network-failure as PROFINETDiagnosis to the IO-Controller(1)
Additional SNMP-channel for StandardInformation (2)
© PNCC Burgdorf
PROFINET IO System
22
11
Alarms Æ “All Inclusive”
Process-Alarms
Functional scope
Device
Designations
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
● shall be used if the event is process related
Diagnosis-Alarms
● shall be used if the error or event is coming up device internal
Pull and Plug-Alarm
Return of Submodule Alarm
Redundancy alarm
Control by Supervisor
Release by Supervisor
23
Process and Diagnosis can be prioritised differently
© PNCC Burgdorf
PROFINET IO System
23
Alarm Handling
Functional scope
Device
Designations
Device Model
Alarm Data Objects Æ Real Time Data
ƒ Report of operating states
ƒ system defined events (e.g. pull and plug of boards)
ƒ user defined events
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
ƒCharacteristics:
ƒ acyclic
ƒ queued,
ƒ confirmed,
ƒ directed and
ƒ secured
24
© PNCC Burgdorf
PROFINET IO System
24
12
Monitoring of Diagnosis and Alarms (Principle)
IO Device
IO Controller
Functional scope
Device
Designations
Invoke Alarm
RTA_Data(Alarm)
Device Model
Data Exchange
Acyclic ServiceTimeout
Alarm Processing
Communication
Diagnosis
RTA_ACK
Fieldbus
Integration
RTA_Data(Alarm_Ack)
Acyclic ServiceTimeout
RTA_ACK
© PNCC Burgdorf
25
PROFINET IO System
25
Proxy Concept
Functional scope
PROFINET
Device
Designations
Device Model
Proxy
Data Exchange
Communication
Diagnosis
Proxy
PROFIBUS
INTERBUS
Fieldbus
Integration
Field busses, like PROFIBUS or INTERBUS, can be
26
integrated in PROFINET systems via Proxies
Openness through integration of existing field buses is
Investment protection for device manufacturers and users
© PNCC Burgdorf
PROFINET IO System
26
13
PROFINET IO / PROFIBUS - System
IO-Controller
Functional scope
Device
Designations
PROFIBUS
Device Model
Data Exchange
Communication
Diagnosis
Fieldbus
Integration
PROFINET
Both devices need
27 same parameters
the
PROFIBUS
© PNCC Burgdorf
PROFINET IO System
27
PROFINET IO – Proxy
IO-Controller
5
ControllerConfiguration
Tool
Functional scope
Device
Designations
Device Model
4
Data Exchange
6
Communication
Diagnosis
Fieldbus
Integration
Connect:
I/O combination
Write:
User parameters
GSD
3
7
PROXY-Configuration
Tool
Data exchange with
any other bus system
28
2
1
Any Device
Description
© PNCC Burgdorf
PROFINET IO System
28
14