第1页 / 共741页
第2页 / 共741页
第3页 / 共741页
第4页 / 共741页
第5页 / 共741页
第6页 / 共741页
第7页 / 共741页
第8页 / 共741页
profinet协议开发文件.pdf
1 Scope
1.1 Overview
1.2 Specifications
1.3 Conformance
2 Normative references
3 Terms, definitions, abbreviations, symbols and conventions
3.1 Referenced terms and definitions
3.1.1 ISO/IEC 7498-1 terms
3.1.2 ISO/IEC 8822 terms
3.1.3 ISO/IEC 9545 terms
3.1.4 ISO/IEC 8824-1 terms
3.2 Additional terms and definitions for distributed automation
3.3 Additional terms and definitions for decentralized periphery
3.4 Additional terms and definitions for media redundancy
3.5 Abbreviations and symbols
3.6 Additional abbreviations and symbols for distributed automation
3.7 Additional abbreviations and symbols for decentralized periphery
3.8 Additional abbreviations and symbols for media redundancy
3.9 Conventions
3.9.1 Overview
3.9.2 General conventions
3.9.3 Conventions for class definitions
3.9.4 Conventions for service definitions
3.9.4.1 General
3.9.4.2 Service parameters
3.9.4.3 Service procedures
4 Concepts
5 Data type ASE
5.1 General
5.1.1 Overview
5.1.2 Basic type overview
5.1.3 Fixed length type overview
5.1.4 Constructed type overview
5.1.4.1 Strings
5.1.4.2 Arrays
5.1.4.3 Structures
5.1.4.4 Nesting level
5.1.5 Specification of user defined data types
5.1.6 Transfer of user data
5.2 Formal definition of data type objects
5.2.1 Data type class
5.2.1.1 Template
5.2.1.2 Attributes
5.3 FAL defined data types
5.3.1 Fixed length types
5.3.1.1 Boolean types
5.3.1.1.1 Boolean
5.3.1.1.2 VARIANT_BOOL
5.3.1.2 Bitstring types
5.3.1.3 Currency types
5.3.1.4 Date types
5.3.1.4.1 date
5.3.1.4.2 Date
5.3.1.4.3 TimeOfDay
5.3.1.4.4 TimeOfDay with date indication
5.3.1.4.5 TimeOfDay without date indication
5.3.1.4.6 TimeDifference
5.3.1.4.7 TimeDifference with date indication
5.3.1.4.8 TimeDifference without date indication
5.3.1.5 Enumerated types
5.3.1.5.1 PERSISTDEF
5.3.1.5.2 VARTYPE
5.3.1.5.3 ITEMQUALITYDEF
5.3.1.5.4 STATEDEF
5.3.1.5.5 GROUPERRORDEF
5.3.1.5.6 ACCESSRIGHTSDEF
5.3.1.6 Handle types
5.3.1.6.1 HRESULT
5.3.1.7 Numeric types
5.3.1.7.1 Floating point types
5.3.1.7.1.1 float
5.3.1.7.1.2 Float32
5.3.1.7.1.3 double
5.3.1.7.1.4 Float64
5.3.1.7.2 Integer types
5.3.1.7.2.1 char
5.3.1.7.2.2 Integer8
5.3.1.7.2.3 short
5.3.1.7.2.4 Integer16
5.3.1.7.2.5 long
5.3.1.7.2.6 Integer32
5.3.1.7.2.7 Integer64
5.3.1.7.3 Unsigned types
5.3.1.7.3.1 unsigned char
5.3.1.7.3.2 Unsigned8
5.3.1.7.3.3 unsigned short
5.3.1.7.3.4 Unsigned16
5.3.1.7.3.5 unsigned long
5.3.1.7.3.6 Unsigned32
5.3.1.7.3.7 Unsigned64
5.3.1.7.3.8 Normalised value N2
5.3.1.7.3.9 Normalised value N4
5.3.1.7.3.10 Variable normalised X2
5.3.1.7.3.11 Variable normalised X4
5.3.1.7.3.12 Unipolar2.16
5.3.1.7.3.13 Fixed point value E2
5.3.1.7.3.14 Fixed point value C4
5.3.1.7.3.15 Bit sequence V2
5.3.1.7.3.16 Nibble L2
5.3.1.8 OctetString character types
5.3.1.8.1 UUID
5.3.1.9 Pointer types
5.3.1.9.1 Interface Pointer
5.3.1.9.2 LPWSTR
5.3.1.10 Time types
5.3.1.10.1 NetworkTime
5.3.1.10.2 NetworkTimeDifference
5.3.1.10.3 Time constant T2
5.3.1.10.4 Time constant T4
5.3.1.10.5 Time constant D2
5.3.1.10.6 Time constant R2
5.3.1.11 VisibleString character types
5.3.2 String types
5.3.2.1 OctetString
5.3.2.2 VisibleString
5.3.2.3 UNICODEString
5.3.3 Structure types
5.3.3.1 ADDCONNECTIONIN
5.3.3.2 ADDCONNECTIONOUT
5.3.3.3 BSTR
5.3.3.4 CONNECTIN
5.3.3.5 CONNECTIN2
5.3.3.6 CONNECTINCR
5.3.3.7 CONNECTINSRT
5.3.3.8 CONNECTOUT
5.3.3.9 CONNECTOUTCR
5.3.3.10 DIAGCONSCONNOUT
5.3.3.11 DISPPARAMS
5.3.3.12 EXCEPINFO
5.3.3.13 FILETIME
5.3.3.14 GETIDOUT
5.3.3.15 GETCONNECTIONOUT
5.3.3.16 GETCONSCONNOUT
5.3.3.17 GETPROVCONNOUT
5.3.3.18 MACAddr
5.3.3.19 OctetString2+Unsigned8
5.3.3.20 Float32+Unsigned8
5.3.3.21 Unsigned8+Unsigned8
5.3.3.22 READITEMOUT
5.3.3.23 SAFEARRAY
5.3.3.24 VARIANT
5.3.3.25 WRITEITEMIN
5.3.3.26 WRITEITEMQCDIN
5.3.3.27 Unsigned16_S
5.3.3.28 Integer16_S
5.3.3.29 Unsigned8_S
5.3.3.30 OctetString_S
5.3.3.31 F message trailer with 4 octets
5.3.3.32 F message trailer with 5 octets
5.4 Data type ASE service specification
6 Communication model for common services
6.1 Concepts
6.2 ASE data types
6.3 ASEs
6.3.1 Discovery and basic configuration ASE
6.3.1.1 Overview
6.3.1.2 DCP class specification
6.3.1.2.1 General
6.3.1.2.2 Template
6.3.1.2.3 Attributes
6.3.1.3 DCP service specification
6.3.1.3.1 Get
6.3.1.3.2 Set
6.3.1.3.3 Identify
6.3.1.3.4 Hello
6.3.2 Precision time control ASE
6.3.2.1 Concepts
6.3.2.2 PTCP class specification
6.3.2.2.1 Template
6.3.2.2.2 Attributes
6.3.2.3 PTCP service specification
6.3.2.3.1 Start bridge
6.3.2.3.2 Start slave
6.3.2.3.3 Start master
6.3.2.3.4 Stop bridge
6.3.2.3.5 Stop slave
6.3.2.3.6 Stop master
6.3.2.3.7 Sync state change
6.3.2.3.8 PTCP behavior
6.3.2.3.8.1 Synchronization
6.3.2.3.8.2 Rate control compensation
6.3.2.3.8.3 Multiple synchronization
6.3.2.3.8.4 Best master algorithm (BMA)
6.3.2.4 Media Redundancy support for synchronization with PTCP
6.3.2.5 Invocation of the PTCP object
6.3.3 Media redundancy ASE
6.3.3.1 Overview
6.3.3.2 Media redundancy class specification
6.3.3.2.1 General
6.3.3.2.2 Template
6.3.3.2.3 Attributes
6.3.3.3 Media redundancy service specification
6.3.3.3.1 Start MRM
6.3.3.3.2 Stop MRM
6.3.3.3.3 Redundancy State Change
6.3.3.3.4 Start MRC
6.3.3.3.5 Stop MRC
6.3.3.3.6 Neighborhood changed
6.3.3.4 Media redundancy behavior
6.3.3.4.1 Ring ports
6.3.3.4.2 Media redundancy manager (MRM)
6.3.3.4.3 Media redundancy client (MRC)
6.3.3.4.4 Redundancy domain
6.3.3.4.5 Multiple MRM in a single ring (option)
6.3.3.4.6 RT media redundancy (option)
6.3.3.5 Usage with diagnosis and alarms
6.3.3.5.1 Media redundancy diagnosis dependencies
6.3.3.6 MRP parameters
6.3.3.6.1 Ring port parameters
6.3.3.6.2 Ring Topology parameters
6.3.3.6.3 MRM and MRC parameters
6.3.4 Real-time cyclic ASE
6.3.4.1 Overview
6.3.4.2 RTC class specification
6.3.4.2.1 General
6.3.4.2.2 Template
6.3.4.2.3 Attributes
6.3.4.3 RTC service specification
6.3.4.3.1 Set Prov Data
6.3.4.3.2 Set Prov Status
6.3.4.3.3 PPM Activate
6.3.4.3.4 Close
6.3.4.3.5 Start
6.3.4.3.6 Error
6.3.4.3.7 Get Cons Data
6.3.4.3.8 Get cons status
6.3.4.3.9 Set RedRole
6.3.4.3.10 CPM activate
6.3.5 Real-time acyclic ASE
6.3.5.1 Overview
6.3.5.2 RTA class specification
6.3.5.2.1 General
6.3.5.2.2 Template
6.3.5.2.3 Attributes
6.3.5.3 RTA service specification
6.3.5.3.1 APMS Activate
6.3.5.3.2 APMR Activate
6.3.5.3.3 APMS A Data
6.3.5.3.4 APMR A Data
6.3.5.3.5 APMR Ack
6.3.5.3.6 APMS error
6.3.5.3.7 APMR Error
6.3.5.3.8 APMS_Close
6.3.5.3.9 APMR_Close
6.3.6 Remote procedure call ASE
6.3.6.1 Overview
6.3.6.2 RPC class specification
6.3.6.2.1 Template
6.3.6.2.2 Attributes
6.3.6.3 RPC service specification
6.3.6.3.1 Connect
6.3.6.3.2 Release
6.3.6.3.3 Read
6.3.6.3.4 Write
6.3.6.3.5 Control
6.3.7 Link layer discovery ASE
6.3.7.1 Overview
6.3.7.2 IEEE 802.1AB class specification
6.3.7.2.1 Template
6.3.7.2.2 Attributes
6.3.7.2.3 Invocation of the IEEE 802.1AB object
6.3.7.3 IEEE 802.1AB service specification
6.3.7.3.1 Remote systems data change
6.3.7.3.2 Placeholder
6.3.8 MAC bridges ASE
6.3.8.1 Overview
6.3.8.2 IEEE 802.1D class specification
6.3.8.2.1 General
6.3.8.2.2 Template
6.3.8.2.3 Attributes
6.3.8.3 IEEE 802.1D service specification
6.3.8.3.1 Port state change
6.3.8.3.2 Set port state
6.3.8.3.3 Flush filtering data base
6.3.8.3.4 IFW IRT Schedule Add
6.3.8.3.5 IFW IRT Schedule Remove
6.3.8.3.6 IFW Schedule
6.3.8.4 Invocation of the IEEE 802.1D object
6.3.9 Virtual bridged LAN ASE
6.3.9.1 Overview
6.3.9.2 IEEE 802.1Q class specification
6.3.9.2.1 Template
6.3.9.2.2 Attributes
6.3.9.2.3 Invocation of the IEEE 802.1Q object
6.3.9.3 IEEE 802.1Q service specification
6.3.10 Medium access ASE
6.3.10.1 Overview
6.3.10.2 IEEE 802.3 class specification
6.3.10.2.1 General
6.3.10.2.2 Template
6.3.10.2.3 Attributes
6.3.10.3 IEEE 802.3 service specification
6.3.10.3.1 MAU type Change
6.3.10.3.2 Set MAU type
6.3.10.4 Invocation of the IEEE 802.3 object
6.3.11 IP suite ASE
6.3.11.1 Overview
6.3.11.2 IP suite class specification
6.3.11.2.1 General
6.3.11.2.2 Template
6.3.11.2.3 Attributes
6.3.11.3 IP suite service specification
6.3.11.3.1 Set ARP Cache
6.3.12 Domain name system ASE
6.3.12.1 Overview
6.3.12.2 DNS class specification
6.3.12.2.1 General
6.3.12.2.2 Template
6.3.12.2.3 Attributes
6.3.12.3 DNS service specification
6.3.13 Dynamic host configuration ASE
6.3.13.1 Overview
6.3.13.2 DHCP class specification
6.3.13.2.1 General
6.3.13.2.2 Template
6.3.13.2.3 Attributes
6.3.13.3 DHCP service specification
6.3.14 Simple network management ASE
6.3.14.1 Overview
6.3.14.2 SNMP class specification
6.3.14.2.1 General
6.3.14.2.2 Template
6.3.14.2.3 Attributes
6.3.14.3 SNMP service specification
6.3.15 Common DL mapping ASE
6.3.15.1 Overview
6.3.15.2 DL Mapping class specification
6.3.15.2.1 General
6.3.15.2.2 Template
6.3.15.2.3 Attributes
6.3.15.3 DL Mapping service specification
6.3.15.3.1 IRT Schedule Add
6.3.15.3.2 IRT Schedule Remove
6.3.15.3.3 Schedule
6.3.15.3.4 N Data
6.3.15.3.5 A Data
6.3.15.3.6 C Data
7 Communication model for distributed automation
7.1 Concepts
7.1.1 Overview
7.1.2 Objectives of the FAL AE
7.1.3 Devices types
7.1.4 FAL ASEs
7.1.5 Runtime object model
7.1.6 Navigation in the object model
7.1.7 Online/offline comparison
7.2 ASE data types
7.2.1 Supported data types
7.2.2 Connectable data types
7.2.3 Extended type description
7.2.4 Definitions for identifiers
7.2.4.1 Character set type 1
7.2.4.2 Character set type 2
7.2.4.3 Common definitions
7.2.4.4 Usage of character sets
7.3 ASEs
7.3.1 Object Management ASE
7.3.1.1 Overview
7.3.1.2 Class specification
7.3.1.2.1 Template
7.3.1.2.2 Attributes
7.3.1.3 Service specification
7.3.1.3.1 Interface Unknown
7.3.1.3.1.1 QueryInterface
7.3.1.3.1.2 AddRef
7.3.1.3.1.3 Release
7.3.1.3.2 Interface Dispatch
7.3.1.3.2.1 GetTypeInfoCount
7.3.1.3.2.2 GetTypeInfo
7.3.1.3.2.3 GetIDsOfNames
7.3.1.3.2.4 Invoke
7.3.2 AP ASE
7.3.2.1 Physical device
7.3.2.1.1 Overview
7.3.2.1.2 Physical Device class specification
7.3.2.1.2.1 Template
7.3.2.1.2.2 Attributes
7.3.2.1.3 Physical device behavior
7.3.2.1.3.1 Overview
7.3.2.1.3.2 Online/offline comparison of the LDev objects
7.3.2.1.4 Physical device service specification
7.3.2.1.4.1 Interface physical device
7.3.2.1.4.1.1 get_Producer
7.3.2.1.4.1.2 get_Product
7.3.2.1.4.1.3 get_SerialNo
7.3.2.1.4.1.4 get_ProductionDate
7.3.2.1.4.1.5 Revision
7.3.2.1.4.1.6 get_LogicalDevice
7.3.2.1.4.1.7 Type
7.3.2.1.4.1.8 PROFInetRevision
7.3.2.1.4.1.9 get_PDevStamp
7.3.2.1.4.2 Interface Browse
7.3.2.1.4.2.1 get_Count
7.3.2.1.4.2.2 BrowseItems
7.3.2.1.4.2.3 get_Count2
7.3.2.1.4.2.4 BrowseItems2
7.3.2.1.4.3 Interface Persist
7.3.2.1.4.3.1 Save
7.3.2.1.4.3.2 Save2
7.3.2.2 Logical Device
7.3.2.2.1 Overview
7.3.2.2.2 Logical Device class specification
7.3.2.2.2.1 Template
7.3.2.2.2.2 Attributes
7.3.2.2.3 Logical Device behavior
7.3.2.2.3.1 Operating state
7.3.2.2.3.2 Diagnosis
7.3.2.2.4 Logical Device service specification
7.3.2.2.4.1 Interface logical device
7.3.2.2.4.1.1 get_Name
7.3.2.2.4.1.2 get_Producer
7.3.2.2.4.1.3 get_Product
7.3.2.2.4.1.4 get_SerialNo
7.3.2.2.4.1.5 get_ProductionDate
7.3.2.2.4.1.6 Revision
7.3.2.2.4.1.7 get_ACCO
7.3.2.2.4.1.8 get_RTAuto
7.3.2.2.4.1.9 PROFInetRevision
7.3.2.2.4.1.10 ComponentInfo
7.3.2.2.4.2 Interface State
7.3.2.2.4.2.1 get_State
7.3.2.2.4.2.2 Activate
7.3.2.2.4.2.3 Deactivate
7.3.2.2.4.2.4 Reset
7.3.2.2.4.2.5 AdviseState
7.3.2.2.4.2.6 UnadviseState
7.3.2.2.4.3 Interface Time
7.3.2.2.4.3.1 get_Time
7.3.2.2.4.3.2 put_Time
7.3.2.2.4.4 Interface Browse
7.3.2.2.4.4.1 get_Count
7.3.2.2.4.4.2 BrowseItems
7.3.2.2.4.4.3 get_Count2
7.3.2.2.4.4.4 BrowseItems2
7.3.2.2.4.5 Interface group error
7.3.2.2.4.5.1 GroupError
7.3.2.2.4.5.2 AdviseGroupError
7.3.2.2.4.5.3 UnadviseGroupError
7.3.3 ACCO ASE
7.3.3.1 Overview
7.3.3.2 ACCO class specification
7.3.3.2.1 Template
7.3.3.2.2 Attributes
7.3.3.3 ACCO Behavior
7.3.3.3.1 Interconnecting RT-Auto objects – ACCO
7.3.3.3.2 Architecture
7.3.3.3.3 Short overview
7.3.3.3.3.1 Establishing connections
7.3.3.3.3.2 Productive operation of data connections
7.3.3.3.4 Definitions
7.3.3.3.4.1 Configuration Data Base
7.3.3.3.4.2 Rules for connections
7.3.3.3.4.3 Definition of the identifiers
7.3.3.3.4.3.1 Identifier for an LDev object
7.3.3.3.4.3.2 Identifier for an RT-Auto menber
7.3.3.3.4.3.3 Identifier for a System Member
7.3.3.3.4.3.4 Identifiers for accessing sub elements
7.3.3.3.4.4 Quality of Service (QoS)
7.3.3.3.4.5 Dead band and epsilon value
7.3.3.3.4.6 Version of a connection
7.3.3.3.4.7 Substitute values
7.3.3.3.4.8 Quality code
7.3.3.3.4.8.1 Overview
7.3.3.3.4.8.2 Using quality codes
7.3.3.3.4.8.3 Standard behavior for quality codes
7.3.3.3.4.8.4 Startup of a connection
7.3.3.3.4.8.5 Behavior in case of a communication fault
7.3.3.3.4.8.6 Behavior in case of connection is cleared
7.3.3.3.4.8.7 Behavior in case of connection is deactivated
7.3.3.3.4.8.8 Behavior in case of "incorrect" connection data
7.3.3.3.4.8.9 Behavior in case of the provider in "CBAReady" state
7.3.3.3.4.8.10 Behavior in case of clearing an object from the provider
7.3.3.3.4.8.11 Behavior in case of connection is forced
7.3.3.3.4.8.12 Behavior in case of QoS violation
7.3.3.3.4.8.13 Write access to values via put-services or WriteItem services
7.3.3.3.4.8.14 Component-overlapping quality code
7.3.3.3.4.8.15 Property access and quality code
7.3.3.3.4.9 Operating state
7.3.3.3.4.10 Power-On
7.3.3.3.4.11 Persistence
7.3.3.3.4.12 Online/offline comparison of the connections
7.3.3.3.5 Communication channels
7.3.3.3.5.1 Configuration
7.3.3.3.5.2 ORPC communication channel
7.3.3.3.5.2.1 General
7.3.3.3.5.2.2 Context management
7.3.3.3.5.2.2.1 Overview
7.3.3.3.5.2.2.2 Push mode
7.3.3.3.5.2.2.3 Pull mode
7.3.3.3.5.2.3 QoS
7.3.3.3.5.2.4 QoS violation
7.3.3.3.5.2.5 Connection monitoring
7.3.3.3.5.2.5.1 Connection monitoring by the consumer – Push mode
7.3.3.3.5.2.5.2 Connection monitoring by the consumer – Pull mode
7.3.3.3.5.2.5.3 Connection monitoring by the provider – Push mode
7.3.3.3.5.2.5.4 Connection monitoring by the provider – Pull mode
7.3.3.3.5.2.6 State machines
7.3.3.3.5.2.6.1 State machine RemoteACCO
7.3.3.3.5.2.6.2 State machine RemoteACCOProvider
7.3.3.3.5.2.6.3 State machine RemoteACCOProviderORPC
7.3.3.3.5.2.6.4 State machine ARORPC
7.3.3.3.5.2.6.5 State machine GetConnectionData – Provider
7.3.3.3.5.2.6.6 State machine ProviderConnection
7.3.3.3.5.2.6.7 State machine ProvConnActivation
7.3.3.3.5.2.6.8 State machine WorkerORPC
7.3.3.3.5.3 RT communication channel
7.3.3.3.5.3.1 General
7.3.3.3.5.3.2 Application relations and communication relations
7.3.3.3.5.3.3 Using RT
7.3.3.3.5.3.3.1 RT variants
7.3.3.3.5.3.3.2 Frame ID
7.3.3.3.5.3.3.3 Segmentation
7.3.3.3.5.3.3.4 RT cycle time and QoS value
7.3.3.3.5.3.3.5 QoS violation
7.3.3.3.5.3.3.6 Connection monitoring
7.3.3.3.5.3.3.6.1 Connection monitoring by the consumer
7.3.3.3.5.3.3.6.2 Connection monitoring by the provider
7.3.3.3.5.3.4 State machines
7.3.3.3.5.3.4.1 Remote interactions
7.3.3.3.5.3.4.2 State machine for application relations
7.3.3.3.5.3.4.3 State machine for AccoDataCR
7.3.3.3.5.4 Local communication channel
7.3.3.3.5.4.1 Overview
7.3.3.3.5.4.2 QoS
7.3.3.3.5.4.3 QoS violation
7.3.3.3.5.5 Constant communication channel
7.3.3.3.6 ACCO Management operation
7.3.3.3.6.1 Overview
7.3.3.3.6.1.1 Tasks of the consumer
7.3.3.3.6.1.2 Tasks of the provider
7.3.3.3.6.2 Establishing connections
7.3.3.3.6.2.1 Overview
7.3.3.3.6.2.2 Connections with a constant
7.3.3.3.6.2.3 Negotiating with the provider – common definitions
7.3.3.3.6.2.3.1 General
7.3.3.3.6.2.3.2 Connect attempt
7.3.3.3.6.2.3.3 Signature identity check
7.3.3.3.6.2.3.3.1 Overview
7.3.3.3.6.2.3.3.2 Signature identity check for data connections (Base object version 1)
7.3.3.3.6.2.3.3.3 Signature identity check for data connections (Base object version 2)
7.3.3.3.6.2.4 Negotiating with the provider – ORPC
7.3.3.3.6.2.5 Negotiating with the provider – RT
7.3.3.3.6.2.5.1 General
7.3.3.3.6.2.5.2 Reconfiguration
7.3.3.3.6.2.6 Negotiating with the provider – Local
7.3.3.3.6.2.7 Negotiating with the provider – Constant
7.3.3.3.6.3 Changing connections
7.3.3.3.6.4 Clearing connections
7.3.3.3.6.4.1 General
7.3.3.3.6.4.2 Negotiating with the provider – ORPC
7.3.3.3.6.4.3 Negotiating with the provider – RT
7.3.3.3.6.4.4 Negotiating with the provider – Local
7.3.3.3.6.4.5 Negotiating with the provider – Constant
7.3.3.3.6.5 Activating and deactivating connections
7.3.3.3.6.5.1 General
7.3.3.3.6.5.2 Negotiating with the provider – ORPC
7.3.3.3.6.5.3 Negotiating with the provider – RT
7.3.3.3.6.5.4 Negotiating with the provider – Local
7.3.3.3.6.5.5 Negotiating with the provider – Constant
7.3.3.3.7 Productive operations of connections
7.3.3.3.7.1 Overview
7.3.3.3.7.2 Productive operation for data connections
7.3.3.3.7.2.1 ORPC channel
7.3.3.3.7.2.2 RT channel
7.3.3.3.7.2.3 Local channel
7.3.3.3.7.3 Productive operation for the RT communication channel
7.3.3.3.7.4 Fault scenarios
7.3.3.3.7.4.1 Overview
7.3.3.3.7.4.2 Time intervals
7.3.3.3.7.4.3 Packet duplication
7.3.3.3.7.4.4 Packet loss
7.3.3.3.7.4.5 Garbled data
7.3.3.3.7.4.6 Sequence switching
7.3.3.3.7.4.7 Recycling frames
7.3.3.3.7.4.8 Failure of the provider in productive operation
7.3.3.3.7.4.8.1 ORPC communication channel
7.3.3.3.7.4.8.2 RT communication channel
7.3.3.3.7.4.9 Failure of the consumer in productive operation
7.3.3.3.7.4.9.1 ORPC communication channel
7.3.3.3.7.4.9.2 RT communication channel
7.3.3.3.7.4.10 Unilateral communication failure recognition during productive operation
7.3.3.3.7.4.10.1 ORPC communication channel
7.3.3.3.7.4.10.2 RT communication channel
7.3.3.3.7.4.11 Failure of the provider during negotiation
7.3.3.3.7.4.12 Transmission of garbled data
7.3.3.3.8 Connection diagnosis
7.3.3.3.9 Synchronous Read / Write
7.3.3.3.9.1 Overview
7.3.3.3.9.2 Synchronous access
7.3.3.4 ACCO Service specification
7.3.3.4.1 Interface ACCO Management
7.3.3.4.1.1 AddConnections
7.3.3.4.1.2 RemoveConnections
7.3.3.4.1.3 ClearConnections
7.3.3.4.1.4 SetActivationState
7.3.3.4.1.5 GetInfo
7.3.3.4.1.6 GetIDs
7.3.3.4.1.7 GetConnections
7.3.3.4.1.8 ReviseQoS
7.3.3.4.1.9 get_PingFactor
7.3.3.4.1.10 put_PingFactor
7.3.3.4.1.11 get_CDBCookie
7.3.3.4.1.12 GetConsIDs
7.3.3.4.1.13 GetConsConnections
7.3.3.4.1.14 DiagConsConnections
7.3.3.4.1.15 GetProvIDs
7.3.3.4.1.16 GetProvConnections
7.3.3.4.1.17 GetDiagnosis
7.3.3.4.2 Interface ACCO Server
7.3.3.4.2.1 Connect
7.3.3.4.2.2 Disconnect
7.3.3.4.2.3 DisconnectMe
7.3.3.4.2.4 SetActivation
7.3.3.4.2.5 Ping
7.3.3.4.2.6 Connect2
7.3.3.4.2.7 GetConnectionData
7.3.3.4.3 Interface ACCO Callback
7.3.3.4.3.1 OnDataChanged
7.3.3.4.3.2 Gnip
7.3.3.4.4 Interface ACCO Sync
7.3.3.4.4.1 ReadItems
7.3.3.4.4.2 WriteItems
7.3.3.4.4.3 WriteItemsQCD
7.3.3.4.5 Interface Group Error
7.3.3.4.5.1 GroupError
7.3.3.4.5.2 AdviseGroupError
7.3.3.4.5.3 UnadviseGroupError
7.3.3.4.6 Interface ACCO Server SRT
7.3.3.4.6.1 ConnectCR
7.3.3.4.6.2 DisconnectCR
7.3.3.4.6.3 Connect
7.3.3.4.6.4 Disconnect
7.3.3.4.6.5 DisconnectMe
7.3.3.4.6.6 SetActivation
7.3.4 RT-Auto ASE
7.3.4.1 Overview
7.3.4.2 RT-Auto class specification
7.3.4.2.1 Template
7.3.4.2.2 Attributes
7.3.4.3 RT-Auto behavior
7.3.4.3.1 General
7.3.4.3.2 Interconnecting RT-Auto objects
7.3.4.3.3 Property access
7.3.4.4 RT-Auto service specification
7.3.4.4.1 Interface RT-Auto
7.3.4.4.1.1 get_Name
7.3.4.4.1.2 Revision
7.3.4.4.1.3 ComponentInfo
7.3.4.4.2 Interface Browse
7.3.4.4.2.1 get_Count
7.3.4.4.2.2 BrowseItems
7.3.4.4.2.3 get_Count2
7.3.4.4.2.4 BrowseItems2
7.3.4.4.3 Interface system properties
7.3.4.4.3.1 get_StateCollection
7.3.4.4.3.2 get_StampCollection
7.4 ARs
7.4.1 Overview
7.4.2 ORPC AR class specification
7.4.2.1 Formal definition
7.4.2.2 Attributes
7.4.3 ORPC AR service specification
7.4.3.1 CoCreateInstance
7.4.3.2 CoDisconnectObject
7.4.3.3 Call
7.5 Summary of FAL classes
7.6 Summary of FAL services
8 Communication model for decentralized periphery
8.1 Concepts
8.1.1 User requirements
8.1.2 Features
8.1.3 Associations
8.1.4 Device types
8.1.4.1 General
8.1.4.2 IO controller
8.1.4.3 IO supervisor
8.1.4.4 IO parameter server
8.1.4.5 IO device
8.1.4.5.1 General
8.1.4.5.2 Slot
8.1.4.5.3 Subslot
8.1.4.5.4 Channel
8.1.5 Instance model and device addresses
8.1.6 Application process
8.1.6.1 Overview
8.1.6.2 Application service element
8.1.6.3 Application objects
8.1.7 Application relationship
8.1.7.1 General
8.1.7.2 Application relationship endpoint
8.1.7.3 Overview of application relationships
8.2 ASE data types
8.3 ASEs
8.3.1 Record data ASE
8.3.1.1 Overview
8.3.1.2 Record data class specification
8.3.1.2.1 Template
8.3.1.2.2 Attributes
8.3.1.2.3 Invocation of the Record Data object
8.3.1.3 Record data service specification
8.3.1.3.1 Read
8.3.1.3.2 Read Query
8.3.1.3.3 Write
8.3.2 IO Data ASE
8.3.2.1 Overview
8.3.2.2 IO Data class specification
8.3.2.2.1 Input Data class specification
8.3.2.2.1.1 Template
8.3.2.2.1.2 Attributes
8.3.2.2.1.3 Invocation of the Input Data object
8.3.2.2.2 Output data class specification
8.3.2.2.2.1 Template
8.3.2.2.2.2 Attributes
8.3.2.2.2.3 Invocation of the Output Data object
8.3.2.3 IO Data service specification
8.3.2.3.1 Set input
8.3.2.3.2 Set input IOCS
8.3.2.3.3 Get Input
8.3.2.3.4 Get Input IOCS
8.3.2.3.5 New Input
8.3.2.3.6 Set Input APDU Data Status
8.3.2.3.7 New Input APDU Data Status
8.3.2.3.8 Read input data
8.3.2.3.9 Set Output
8.3.2.3.10 Set Output IOCS
8.3.2.3.11 Get Output
8.3.2.3.12 Get Output IOCS
8.3.2.3.13 New Output
8.3.2.3.14 Set Output APDU Data Status
8.3.2.3.15 New Output APDU Data Status
8.3.2.3.16 Read Output Data
8.3.2.3.17 Read Output Substitute Data
8.3.2.3.18 Write Output Substitute Data
8.3.2.4 Behavior of IO Data objects
8.3.2.4.1 General behavior of the Input Data object
8.3.2.4.2 General behavior of the Output Data object
8.3.3 Logbook Data ASE
8.3.3.1 Overview
8.3.3.2 Logbook Data class specification
8.3.3.2.1 Template
8.3.3.2.2 Attributes
8.3.3.3 Logbook Data service specification
8.3.3.3.1 Read logbook
8.3.3.3.2 Logbook Event
8.3.4 Diagnosis ASE
8.3.4.1 Overview
8.3.4.2 Diagnosis class specification
8.3.4.2.1 Template
8.3.4.2.2 Attributes
8.3.4.2.3 Invocation of the Diagnosis object
8.3.4.3 Diagnosis service specification
8.3.4.3.1 Read Device Diagnosis
8.3.4.3.2 Diagnosis Item
8.3.4.3.3 Diagnosis Event
8.3.4.3.4 Behavior of Diagnosis objects
8.3.4.3.5 General behavior of the Diagnosis object
8.3.4.3.6 Behavior Diagnosis entry
8.3.4.3.7 Behavior maintenance required entry
8.3.4.3.8 Behavior maintenance demanded entry
8.3.4.3.9 Behavior qualified entry
8.3.4.3.10 Optimization for Diagnosis objects
8.3.4.3.10.1 Subslot Number level
8.3.4.3.10.2 Channel Error type level
8.3.5 Alarm ASE
8.3.5.1 Overview
8.3.5.2 Alarm class specification
8.3.5.2.1 Template
8.3.5.2.2 Attributes
8.3.5.2.3 Invocation of the Alarm object
8.3.5.3 Alarm service specification
8.3.5.3.1 Alarm Notification
8.3.5.3.2 Alarm Ack
8.3.5.4 Behavior of Alarm objects
8.3.5.4.1 General behavior of the alarm sink
8.3.5.4.2 General behavior of the alarm source
8.3.5.4.3 Behavior for diagnosis changes
8.3.6 Context ASE
8.3.6.1 Overview
8.3.6.2 Context class specification
8.3.6.2.1 Template
8.3.6.2.2 Attributes
8.3.6.2.3 Invocation of the Context object
8.3.6.3 Context service specification
8.3.6.3.1 Connect
8.3.6.3.2 Connect Device Access
8.3.6.3.3 Release
8.3.6.3.4 Abort
8.3.6.3.5 End Of Parameter
8.3.6.3.6 Application Ready
8.3.6.3.7 Ready For Companion
8.3.6.3.8 Read Expected Identification
8.3.6.3.9 Read Real Identification
8.3.6.3.10 Read Identification Difference
8.3.6.4 Behavior of the Context object
8.3.6.5 Behavior of the attribute Submodule State
8.3.7 Isochronous Mode Application ASE
8.3.7.1 Overview
8.3.7.2 Isochronous Mode Application class specification
8.3.7.2.1 Template
8.3.7.2.2 Attributes
8.3.7.3 Isochronous Mode Application service specification
8.3.7.3.1 Write IsoM Data
8.3.7.3.2 Read IsoM Data
8.3.7.3.3 SYNCH Event
8.3.7.4 Behavior of Isochronous Mode Application objects
8.3.7.4.1 Overview of relations to other ASE objects
8.3.7.4.2 Basic behavior of input and output data in the isochronous mode
8.3.7.4.3 State machine description for isochronous mode
8.3.7.4.3.1 General
8.3.7.4.3.2 Primitive definitions
8.3.7.4.3.2.1 Primitives exchanged between the AL and the SyncCtl state machine
8.3.7.4.3.2.2 Primitive exchanged between the SyncCtl state machine and the user
8.3.7.4.3.2.3 Primitive exchanged between the Input state machine and the user
8.3.7.4.3.2.4 Primitive exchanged between the output state machine and the user
8.3.7.4.3.2.5 Primitives exchanged between the Output state machine and the SyncCtl state machine
8.3.7.4.3.2.6 Primitives exchanged between the Input state machine and the SyncCtl state machine
8.3.7.4.3.2.7 Primitives exchanged between the AL and the Output state machine
8.3.7.4.3.2.8 Primitives exchanged between the Input state machine and the AL
8.3.7.4.3.3 SyncCtl state diagram
8.3.7.4.3.4 SyncCtl state table
8.3.7.4.3.5 Output state diagram
8.3.7.4.3.6 Output state table
8.3.7.4.3.7 Input state diagram
8.3.7.4.3.8 Input state table
8.3.8 Physical Device Management ASE
8.3.8.1 Overview
8.3.8.2 Physical Device Management class specification
8.3.8.2.1 General
8.3.8.2.2 Physical Device Management class specification
8.3.8.2.2.1 Template
8.3.8.2.2.2 Attributes
8.3.8.3 Physical Device Management service specification
8.3.8.3.1 Write Expected Port Data
8.3.8.3.2 Write Adjusted Port Data
8.3.8.3.3 Read Real Port Data
8.3.8.3.4 Read Expected Port Data
8.3.8.3.5 Read Adjusted Port Data
8.3.8.3.6 Write IR Data
8.3.8.3.7 Read IR Data
8.3.8.3.8 Write Sync Data
8.3.8.3.9 Read Real Sync Data
8.3.8.3.10 Read Expected Sync Data
8.3.8.3.11 Read PDev Data
8.3.8.3.12 Sync State Info
8.3.8.3.13 Write Adjusted Fiber Optic Data
8.3.8.3.14 Read real fiber optic data
8.3.8.3.15 Write MRP Interface Data
8.3.8.3.16 Read MRP Interface Data
8.3.8.3.17 Write MRP Port Data
8.3.8.3.18 Read MRP Port Data
8.3.8.3.19 Write FSU Data
8.3.8.3.20 Read FSU Data
8.3.9 Network Continuous Time ASE
8.3.9.1 Overview
8.3.9.2 Network Continuous Time class specification
8.3.9.2.1 Template
8.3.9.2.2 Attributes
8.3.9.2.3 Invocation of the Network Continuous Time object
8.3.9.3 Network Continuous Time service specification
8.3.9.3.1 Set time
8.3.9.3.2 Placeholder
8.3.10 AR ASE
8.3.10.1 Overview
8.3.10.1.1 General
8.3.10.1.2 Communication relationship
8.3.10.1.2.1 General
8.3.10.1.2.2 Communication relationship endpoint
8.3.10.1.2.3 Buffer and queues
8.3.10.1.2.4 Communication relationship endpoint roles
8.3.10.1.2.5 Overview of communication relationships
8.3.10.2 Application relationships
8.3.10.2.1 Implicit application relationship
8.3.10.2.2 IO application relationship
8.3.10.2.3 Supervisor application relationship
8.3.10.3 ARL class specification
8.3.10.3.1 Template
8.3.10.3.2 Attributes
8.3.10.4 CRL class specification
8.3.10.4.1 Template
8.3.10.4.2 Attributes
8.3.10.4.3 Invocation of CRL object
8.3.10.5 AR service specification
8.3.10.5.1 Read AR Data
8.3.10.5.2 Placeholder
8.4 Behavior of an IO device
8.4.1 Overview
8.4.2 Startup of an IO device
8.4.3 Physical Device parameter check
8.4.3.1 Remote system data
8.4.3.2 Local system data
8.4.3.3 Optical system data
8.4.4 Diagnosis and problem indicator
8.4.5 User alarms
8.4.6 Behavior in case of configuration change
8.4.6.1 General
8.4.6.2 State behavior of submodules
8.4.7 Behavior for PTCP within IO devices
8.4.7.1 Diagnosis and Alarms
8.4.7.2 Sync error dependencies
8.4.7.3 State machine description
8.4.7.4 State table
8.4.7.5 Functions
8.5 Behavior of an IO controller
8.5.1 Overview
8.5.2 Behavior of an IO controller during startup
8.6 Application characteristics
8.6.1 Device ident number
8.6.2 Network topology
Bibliography
Application Layer services for
decentralized periphery and distributed
automation
Specification
for
PROFINET
Version 2.2
October 2007
Order No: 2.712
Document Identification: TC2-06-0006a
File name: PN-AL-services_2712_V22_Oct07
Prepared by the PROFIBUS Working Group 11 “PROFINET IO” in the Technical Committee 2
“Communication Profiles”.
The attention of adopters is directed to the possibility that compliance with or adoption of PI (PROFIBUS&PROFINET
International) specifications may require use of an invention covered by patent rights. PI shall not be
responsible for identifying patents for which a license may be required by any PI specification, or for conducting
legal inquiries into the legal validity or scope of those patents that are brought to its attention. PI specifications
are prospective and advisory only. Prospective users are responsible for protecting themselves against liability
for infringement of patents.
NOTICE:
The information contained in this document is subject to change without notice. The material in this document
details a PI specification in accordance with the license and notices set forth on this page. This document does
not represent a commitment to implement any portion of this specification in any company's products.
WHILE THE INFORMATION IN THIS PUBLICATION IS BELIEVED TO BE ACCURATE, PI MAKES NO
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL INCLUDING, BUT
NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF
MERCHANTABILITY OR WARRANTY OF FITNESS FOR PARTICULAR PURPOSE OR USE.
In no event shall PI be liable for errors contained herein or for indirect, incidental, special, consequential,
reliance or cover damages, including loss of profits, revenue, data or use, incurred by any user or any third
party. Compliance with this specification does not absolve manufacturers of PROFIBUS or PROFINET
equipment, from the requirements of safety and regulatory agencies (TÜV, BIA, UL, CSA, FCC, IEC, etc.).
PROFIBUS® and PROFINET® logos are registered trade marks. The use is restricted for
members of PROFIBUS&PROFINET International. More detailed terms for the use can be
found on the web page www.profibus.com/libraries.html. Please select button
"Presentations & logos".
The verbal forms MAY and NEED NOT shall be used to indicate a course of
In this specification the following key words (in bold text) will be used:
may:
action permissible within the limits of the document.
should:
The verbal forms SHOULD and SHOULD NOT are used in this document to
indicate that among several possibilities one is recommended as particularly
suitable, without mentioning or excluding others, or that a certain course of
action is preferred but not necessarily required, or that (in the negative form) a
certain possibility or course of action is deprecated but not prohibited.
The verbal forms SHALL and SHALL NOT are used in this document to
shall:
indicate requirements strictly to be followed in order to conform to the
document and .from which no deviation is permitted.
The verbal forms CAN and CAN NOT shall be used for statements of
Can:
possibility and capability, whether ,material, physical or causal.
For details see ISO/IEC Directives, Part 2; “Rules for the structure and drafting of
international standards”. www.iec.ch
Publisher:
PROFIBUS Nutzerorganisation e.V.
Haid-und-Neu-Str. 7
76131 Karlsruhe
Germany
Phone: +49 (0) 721 / 96 58 590
Fax:
+49 (0) 721 / 96 58 589
E-mail: info@profibus.com
Web site: www.profibus.com
© No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
Management summary – Scope of this document
See clause 1.
List of affected patents
See FOREWORD
No patent search, neither external nor internal, has been done by the members of the
Working Group up to now. PROFIBUS International does not guarantee the completeness of
this list.
Related documents and references
See clause 2.
Requirements for certification tests
PI has established the certification process. The related test specification exists.
This standard is concerned, in particular, with the communication and interworking of
sensors, effectors and other automation devices. By using this standard together with
other standards positioned within the OSI or fieldbus reference models, otherwise
incompatible systems may work together in any combination.
The profiles within this document use references to IEC 61158 documents, which are
equivalent to the following PI documents:
IEC doc#
IEC 61158-1
IEC 61158-5-10
IEC 61158-6-10
IEC 61784-1
IEC 61784-2
IEC doc title
PI doc title
PI Order#
Type
layer service
–
10
Overview and guidance for
the IEC 61158 series
Application
definition
elements
Application
layer protocol
specification – Type 10
elements
Profile sets for continuous
and discrete manufacturing
Additional
for
ISO/IEC 8802 3 based
communication networks in
real-time applications
profiles
and
layer
layer
for
the
services
guidance
Overview
PROFIBUS & PROFINET specifications
Application
for
decentralized periphery and distributed
automation
Application
for
decentralized periphery and distributed
automation
Profiles for distributed automation
protocol
Profiles for decentralized periphery
2.702
2.712
2.722
2.732
2.742
61158-5-10/FDIS © IEC
– 10003 –
CONTENTS
1 Scope..................................................................................................................... 10024
1.1 Overview ...................................................................................................... 10024
1.2 Specifications ............................................................................................... 10025
1.3 Conformance ................................................................................................ 10025
2 Normative references ............................................................................................. 10025
3 Terms, definitions, abbreviations, symbols and conventions .................................... 10027
3.1 Referenced terms and definitions .................................................................. 10027
3.2 Additional terms and definitions for distributed automation............................. 10028
3.3 Additional terms and definitions for decentralized periphery ........................... 10030
3.4 Additional terms and definitions for media redundancy................................... 10038
3.5 Abbreviations and symbols............................................................................ 10039
3.6 Additional abbreviations and symbols for distributed automation .................... 10040
3.7 Additional abbreviations and symbols for decentralized periphery .................. 10040
3.8 Additional abbreviations and symbols for media redundancy .......................... 10041
3.9 Conventions ................................................................................................. 10042
4 Concepts................................................................................................................ 10044
5 Data type ASE ........................................................................................................ 10044
5.1 General ........................................................................................................ 10044
5.2
Formal definition of data type objects ............................................................ 10047
5.3
FAL defined data types ................................................................................. 10048
5.4 Data type ASE service specification .............................................................. 10090
6 Communication model for common services ............................................................ 10090
6.1 Concepts ...................................................................................................... 10090
6.2 ASE data types ............................................................................................. 10090
6.3 ASEs ............................................................................................................ 10091
7 Communication model for distributed automation..................................................... 10191
7.1 Concepts ...................................................................................................... 10191
7.2 ASE data types ............................................................................................. 10197
7.3 ASEs ............................................................................................................ 10201
7.4 ARs .............................................................................................................. 10419
7.5 Summary of FAL classes............................................................................... 10423
7.6 Summary of FAL services ............................................................................. 10424
8 Communication model for decentralized periphery................................................... 10428
8.1 Concepts ...................................................................................................... 10428
8.2 ASE data types ............................................................................................. 10444
8.3 ASEs ............................................................................................................ 10444
8.4 Behavior of an IO device............................................................................... 10680
8.5 Behavior of an IO controller .......................................................................... 10724
8.6 Application characteristics............................................................................. 10728
Annex A (informative) Device instances....................................................................... 10730
Annex B (informative) Components of an Ethernet interface......................................... 10732
Annex C (informative) Scheme of MAC address assignment ........................................ 10736
– 10004 –
61158-5-10/FDIS © IEC
Annex D (informative) Collection of objects ................................................................. 10737
Annex E (informative) Measurement of the fast startup time......................................... 10738
Bibliography.................................................................................................................. 10739
FIGURES
Figure 1 – Data type class hierarchy example................................................................ 10045
Figure 2 – NetworkTime date relation ............................................................................ 10068
Figure 3 – PTCP applications ........................................................................................ 10104
Figure 4 – Clock drift measurement ............................................................................... 10115
Figure 5 – Multiple synchronization ............................................................................... 10115
Figure 6 – MRP stack.................................................................................................... 10118
Figure 7 – Ring topology with one manager and clients.................................................. 10129
Figure 8 – MRM in an open ring .................................................................................... 10129
Figure 9 – More than one MRM in the ring ..................................................................... 10130
Figure 10 – Media redundancy diagnosis dependencies................................................. 10131
Figure 11 – Locating the destination for redundant RT frames........................................ 10171
Figure 12 – Example of periods at a local port ............................................................... 10178
Figure 13 – FAL ASEs communication architecture........................................................ 10193
Figure 14 – Runtime object model ................................................................................. 10194
Figure 15 – Relationship between engineering and runtime............................................ 10195
Figure 16 – Navigation in the runtime object model........................................................ 10196
Figure 17 – Operating state block diagram .................................................................... 10235
Figure 18 – Device status model for the common diagnosis ........................................... 10236
Figure 19 – ACCO ASE structure .................................................................................. 10267
Figure 20 – Productive operation of data connections .................................................... 10268
Figure 21 – Quality code transfer – standard behavior ................................................... 10280
Figure 22 – Startup of a connection............................................................................... 10281
Figure 23 – Quality code with communication fault......................................................... 10281
Figure 24 – Quality code when a connection is cleared .................................................. 10282
Figure 25 – Quality code when a connection is deactivated............................................ 10282
Figure 26 – Quality code during the transfer of "incorrect" connection data..................... 10283
Figure 27 – Quality code for provider in "CBAReady" state ............................................ 10284
Figure 28 – Quality code when clearing an object from the provider ............................... 10284
61158-5-10/FDIS © IEC
– 10005 –
Figure 29 – Quality code when a connection is forced.................................................... 10285
Figure 30 – Quality code at QoS violation ...................................................................... 10285
Figure 31 – Push mode ................................................................................................. 10292
Figure 32 – Pull mode overview..................................................................................... 10293
Figure 33 – Detailed sequence chart of the pull mode .................................................... 10294
Figure 34 – QoS and ORPC communication channel ..................................................... 10295
Figure 35 – QoS Violation within Pull Mode ................................................................... 10296
Figure 36 – Monitoring the providers heartbeat .............................................................. 10297
Figure 37 – State machine RemoteACCO ...................................................................... 10299
Figure 38 – State machine RemoteACCOProvider ......................................................... 10299
Figure 39 – State machine RemoteACCOProviderORPC ................................................... 10300
Figure 40 – State machine ARORPC – Provider................................................................ 10300
Figure 41 – State machine GetConnectionData – Provider ............................................. 10301
Figure 42 – State machine ProviderConnection ............................................................. 10301
Figure 43 – State machine ProvConnActivation ............................................................. 10302
Figure 44 – State machine WorkerORPC ....................................................................... 10302
Figure 45 – Communication stack of distributed automation devices .............................. 10303
Figure 46 – Application relations between devices ......................................................... 10304
Figure 47 – Communication relations............................................................................. 10304
Figure 48 – RT communication channel ......................................................................... 10306
Figure 49 – Interaction between provider and consumer ................................................ 10308
Figure 50 – State machine ARSRT – Consumer ............................................................... 10310
Figure 51 – State machine ARSRT – Provider.................................................................. 10311
Figure 52 – State machine AccoDataCR – Consumer..................................................... 10312
Figure 53 – State machine AccoDataCR – Provider ....................................................... 10312
Figure 54 – RT frame layout.......................................................................................... 10313
Figure 55 – Establishing an AccoDataCR ...................................................................... 10314
Figure 56 – Flowchart of the copy cycle for local connections ........................................ 10315
Figure 57 – State machine connect attempt ................................................................... 10319
Figure 58 – Productive operation of data connections (ORPC channel) .......................... 10326
Figure 59 – Productive operation of data connections (RT channel) ............................... 10327
Figure 60 – Productive operation of data connections (Local channel)............................ 10327
Figure 61 – Data flow for cyclic RT ................................................................................ 10328
– 10006 –
61158-5-10/FDIS © IEC
Figure 62 – Failure of the provider in productive operation (ORPC push mode) .............. 10330
Figure 63 – Failure of the provider in productive operation (ORPC pull mode) ................ 10331
Figure 64 – Scenario 1: Provider failure in productive operation (RT) ............................. 10332
Figure 65 – Scenario 2: Recovery from provider failure in productive operation (RT) ...... 10333
Figure 66 – Failure of the consumer (push mode) .......................................................... 10333
Figure 67 – Failure of the consumer (pull mode) ............................................................ 10334
Figure 68 – Failure of the consumer .............................................................................. 10335
Figure 69 – Failure of the provider when setting up connections .................................... 10337
Figure 70 – Information levels ....................................................................................... 10338
Figure 71 – ACCO ASE status model for the common diagnosis .................................... 10338
Figure 72 – ACCO ASE status model for the detailed diagnosis ..................................... 10339
Figure 73 – Structure of the transmitted connection data ............................................... 10382
Figure 74 – Example of communication between controlling devices and field devices.... 10429
Figure 75 – Example of communication between an engineering station and several
controlling and field devices ........................................................................... 10429
Figure 76 – Example of communication between field devices and a server station ........ 10430
Figure 77 – Example of communication between field devices........................................ 10430
Figure 78 – Structural units of one arbitrary API of an IO device (general)...................... 10432
Figure 79 – Example 1 structural units for interfaces and ports within API 0 ................... 10433
Figure 80 – Example 2 structural units for interfaces and ports within API 0 ................... 10434
Figure 81 – Overview of application processes .............................................................. 10436
Figure 82 – IO device with APs, slots and subslots ........................................................ 10437
Figure 83 – Application Process with application objects (APOs).................................... 10440
Figure 84 – Access to a remote APO ............................................................................. 10441
Figure 85 – Access to a remote APO for provider/consumer association ........................ 10442
Figure 86 – Example of one AR with two AREPs............................................................ 10443
Figure 87 – Relation of a record data object to one real object ....................................... 10445
Figure 88 – Relation of a record data object to two real objects...................................... 10446
Figure 89 – Overview IO ASE service interactions ......................................................... 10456
Figure 90 – Example of a resource model at the alarm source ....................................... 10533
Figure 91 – General isochronous application model (example) ....................................... 10568
Figure 92 – ASE relations in an IO device operating in isochronous mode ...................... 10574
Figure 93 – State machine relations in an IO device operating in isochronous mode....... 10574
Figure 94 – SyncCtl state diagram................................................................................. 10578
61158-5-10/FDIS © IEC
– 10007 –
Figure 95 – Output state diagram .................................................................................. 10580
Figure 96 – Input state diagram..................................................................................... 10585
Figure 97 – Assignment of communication relationship to application relationship .......... 10659
Figure 98 – Implicit application relationship ................................................................... 10663
Figure 99 – Example IO application relationship (one-to-one)......................................... 10664
Figure 100 – Example IO application relationship one-to-many ...................................... 10665
Figure 101 – Overview ASE state machines for IO device .............................................. 10681
Figure 102 – State diagram application startup IO device............................................... 10682
Figure 103 – State diagram neighborhood check ........................................................... 10690
Figure 104 – State diagram PD parameter check IO device............................................ 10699
Figure 105 – State diagram for a submodule.................................................................. 10709
Figure 106 – State diagram IO controller during startup ................................................. 10725
Figure 107 – Example of network topology including slower wireless segments .............. 10728
Figure 108 – Example of media redundancy including wireless segments....................... 10729
Figure A.1 – Instance model.......................................................................................... 10730
Figure B.1 – Scheme of an Ethernet interface................................................................ 10732
Figure B.2 – Scheme of an Ethernet interface with bridging ability ................................. 10733
Figure B.3 – Scheme of an Ethernet interface with optical ports ..................................... 10734
Figure B.4 – Scheme of an Ethernet interface with bridging ability using radio
communication .............................................................................................. 10735
Figure B.5 – Scheme of an Ethernet interface with radio communication ........................ 10735
Figure C.1 – Scheme of MAC address assignment......................................................... 10736
Figure D.1 – Example for an intersection of IO device, slot, and AR ............................... 10737
Figure E.1 – Measurement of the fast startup time ......................................................... 10738
TABLES
Table 1 – PERSISTDEF ................................................................................................ 10051
Table 2 – VARTYPE...................................................................................................... 10052
Table 3 – ITEMQUALITYDEF ........................................................................................ 10053
Table 4 – STATEDEF.................................................................................................... 10056
Table 5 – GROUPERRORDEF ...................................................................................... 10056
Table 6 – ACCESSRIGHTSDEF .................................................................................... 10057
Table 7 – HRESULT...................................................................................................... 10057
Table 8 – N2 value range .............................................................................................. 10062
相关推荐
2023年江西萍乡中考道德与法治真题及答案.doc
2012年重庆南川中考生物真题及答案.doc
2013年江西师范大学地理学综合及文艺理论基础考研真题.doc
2020年四川甘孜小升初语文真题及答案I卷.doc
2020年注册岩土工程师专业基础考试真题及答案.doc
2023-2024学年福建省厦门市九年级上学期数学月考试题及答案.doc
2021-2022学年辽宁省沈阳市大东区九年级上学期语文期末试题及答案.doc
2022-2023学年北京东城区初三第一学期物理期末试卷及答案.doc
2018上半年江西教师资格初中地理学科知识与教学能力真题及答案.doc
2012年河北国家公务员申论考试真题及答案-省级.doc
2020-2021学年江苏省扬州市江都区邵樊片九年级上学期数学第一次质量检测试题及答案.doc
2022下半年黑龙江教师资格证中学综合素质真题及答案.doc
