SIST EN 61158-5-10:2008
Industrial communication networks - Fieldbus specifications - Part 5-10: Application layer service definition - Type 10 elements
Industrial communication networks - Fieldbus specifications - Part 5-10: Application layer service definition - Type 10 elements
The fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs." This standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to type 10 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This standard defines in an abstract way the externally visible service provided by the type 10 fieldbus Application Layer in terms of a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this standard is to define the services provided to 1) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and 2) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This standard specifies the structure and services of the type 10 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation.
Industrielle Kommunikationsnetze - Feldbusse - Teil 5-10: Dienstfestlegungen des Application Layer (Anwendungsschicht) - Typ 10-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-10: Définition des services des couches d'application - Eléments de type 10
Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 5-10. del: Definicija opravil na aplikacijskem nivoju - Elementi tipa 10 (IEC 61158-5-10:2007)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 61158-5-10:2008
01-julij-2008
1DGRPHãþD
SIST EN 61158-5:2004
Industrijska komunikacijska omrežja - Specifikacije za procesno vodilo - 5-10. del:
Definicija opravil na aplikacijskem nivoju - Elementi tipa 10 (IEC 61158-5-10:2007)
Industrial communication networks - Fieldbus specifications - Part 5-10: Application layer
service definition - Type 10 elements
Industrielle Kommunikationsnetze - Feldbusse - Teil 5-10: Dienstfestlegungen des
Application Layer (Anwendungsschicht) - Typ 10-Elemente
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-10:
Définition des services des couches d'application - Eléments de type 10
Ta slovenski standard je istoveten z: EN 61158-5-10:2008
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
SIST EN 61158-5-10:2008 en,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
EUROPEAN STANDARD
EN 61158-5-10
NORME EUROPÉENNE
March 2008
EUROPÄISCHE NORM
ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-5:2004
English version
Industrial communication networks -
Fieldbus specifications -
Part 5-10: Application layer service definition -
Type 10 elements
(IEC 61158-5-10:2007)
Réseaux de communication industriels - Industrielle Kommunikationsnetze -
Spécifications des bus de terrain - Feldbusse -
Partie 5-10: Définition des services Teil 5-10: Dienstfestlegungen
des couches d'application - des Application Layer
(Anwendungsschicht) -
Eléments de type 10
(CEI 61158-5-10:2007) Typ 10-Elemente
(IEC 61158-5-10:2007)
This European Standard was approved by CENELEC on 2008-02-01. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the Central Secretariat or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the Central Secretariat has the same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
Central Secretariat: rue de Stassart 35, B - 1050 Brussels
© 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61158-5-10:2008 E
---------------------- Page: 2 ----------------------
EN 61158-5-10:2008 - 2 -
Foreword
The text of document 65C/475/FDIS, future edition 1 of IEC 61158-5-10, prepared by SC 65C, Industrial
networks, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the
IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-5-10 on 2008-02-01.
This and the other parts of the EN 61158-5 series supersede EN 61158-5:2004.
With respect to EN 61158-5:2004 the following changes were made:
– deletion of Type 6 fieldbus and Type 1 fieldbus application layer, for lack of market relevance;
– addition of new fieldbus types;
– partition into multiple parts numbered 5-2, 5-3, …, 5-20.
The following dates were fixed:
– latest date by which the EN has to be implemented
at national level by publication of an identical
(dop) 2008-11-01
national standard or by endorsement
– latest date by which the national standards conflicting
(dow) 2011-02-01
with the EN have to be withdrawn
NOTE Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the
commitment to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer
protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the
EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective
intellectual-property-right holders.
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the International Standard IEC 61158-5-10:2007 was approved by CENELEC as a European
Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:
IEC 61784-1 NOTE Harmonized as EN 61784-1:2008 (not modified).
IEC 61784-2 NOTE Harmonized as EN 61784-2:2008 (not modified).
ISO/IEC 8877 NOTE Harmonized as EN 28877:1993 (not modified).
ISO 8601 NOTE Harmonized as EN 28601:1992 (not modified).
__________
---------------------- Page: 3 ----------------------
- 3 - EN 61158-5-10:2008
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year
1) 2)
IEC 60559 - Binary floating-point arithmetic for HD 592 S1 1991
microprocessor systems
1) 2)
IEC 61131-1 - Programmable controllers - EN 61131-1 2003
Part 1: General information
1) 2)
IEC 61131-3 - Programmable controllers - EN 61131-3 2003
Part 3: Programming languages
1) 2)
IEC 61158-6-3 - Industrial communication networks - EN 61158-6-3 2008
Fieldbus specifications -
Part 6-3: Application layer protocol
specification - Type 3 elements
1) 2)
IEC 61158-6-10 - Industrial communication networks - EN 61158-6-10 2008
Fieldbus specifications -
Part 6-10: Application layer protocol
specification - Type 10 elements
1)
ISO/IEC 646 - Information technology - ISO 7-bit coded - -
character set for information interchange
1) 2)
ISO/IEC 7498-1 - Information technology - Open Systems EN ISO/IEC 7498-1 1995
Interconnection - Basic Reference Model:
The Basic Model
1)
ISO/IEC 8802-1 - Information technology - - -
Telecommunications and information
exchange between systems - Local and
metropolitan area networks - Specific
requirements -
Part 1: Overview of Local Area Network
Standards
1)
ISO/IEC 8802-3 - Information technology - - -
Telecommunications and information
exchange between systems - Local and
metropolitan area networks - Specific
requirements -
Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access
method and physical layer specifications
1)
Undated reference.
2)
Valid edition at date of issue.
---------------------- Page: 4 ----------------------
EN 61158-5-10:2008 - 4 -
Publication Year Title EN/HD Year
1)
ISO/IEC 8822 - Information technology - Open Systems - -
Interconnection - Presentation service
definition
1)
ISO/IEC 8824-1 - Information technology - Abstract Syntax - -
Notation One (ASN.1): Specification of basic
notation
1)
ISO/IEC 8859-1 - Information technology - 8-bit single-byte - -
coded graphic character sets -
Part 1: Latin alphabet No.1
1)
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application Layer structure
1)
ISO/IEC 10646-1 - Information technology - Universal - -
Multiple-Octet Coded Character Set (UCS) -
Part 1: Architecture and Basic Multilingual
Plane
1)
ISO/IEC 10731 - Information technology - Open Systems - -
Interconnection - Basic reference model -
Conventions for the definition of OSI services
IEEE 802 2001 IEEE standard for local and metropolitan - -
area networks: overview and architecture
IEEE 802.1AB 2005 IEEE Standard for Local and metropolitan - -
area networks Station and Media Access
Control Connectivity Discovery
IEEE 802.1D 2004 IEEE standard for local and metropoitan - -
area networks - Media access control (MAC)
Bridges
IEEE 802.1Q 2005 IEEE Standard for Local and Metropolitan - -
Area Networks - Virtual Bridged Local Area
Networks
IEEE 802.3 2005 IEEE Standard for Information technology - - -
Telecommunications and information
exchange between systems - Local and
metropolitan area networks - Specific
requirements -
Part 3: Carrier Sense Multiple Access with
Collision Detection
IEEE 802.15.1 2005 IEEE Standard for Information technology - - -
Telecommunications and information
exchange between systems - Local and
metropolitan area networks - Specific
requirement -
Part 15.1: Wireless medium access control
(MAC) and physical layer (PHY)
specifications for wireless personal area
networks (WPANs)
1)
IETF RFC 768 - User Datagram Protocol - -
1)
IETF RFC 791 - Internet Protocol - -
1)
IETF RFC 792 - Internet Control Message Protocol - -
---------------------- Page: 5 ----------------------
- 5 - EN 61158-5-10:2008
Publication Year Title EN/HD Year
1)
IETF RFC 826 - Ethernet Address Resolution Protocol - -
1)
IETF RFC 1034 - Domain names - concepts and facilities - -
1)
IETF RFC 1112 - Host Extensions for IP Multicasting - -
1)
IETF RFC 2131 - Dynamic Host Configuration Protocol - -
1)
IETF RFC 2674 - Definitions of Managed Objects for Bridges - -
with Traffic Classes, Multicast Filtering and
Virtual LAN Extensions
1)
IETF RFC 2737 - Entity MIB (Version 2) - -
1)
IETF RFC 2863 - The Interfaces Group MIB - -
1)
IETF RFC 3418 - Management Information Base (MIB) for the - -
Simple Network Management Protocol
(SNMP)
1)
IETF RFC 3490 - Internationalizing Domain Names in - -
Applications (IDNA)
1)
IETF RFC 3621 - Power Ethernet MIB - -
1)
IETF RFC 3636 - Definitions of Managed Objects for IEEE - -
802.3 Medium Attachment Units (MAUs)
1)
The Open Group - CAE Specification DCE11: Remote - -
C706 Procedure Call
---------------------- Page: 6 ----------------------
IEC 61158-5-10
Edition 1.0 2007-12
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 5-10: Application layer service definition – Type 10 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XU
ICS 35.100.70; 25.040.40 ISBN 2-8318-9459-X
---------------------- Page: 7 ----------------------
– 2 – 61158-5-10 © IEC:2007(E)
CONTENTS
FOREWORD.16H16
INTRODUCTION.17H18
1 Scope.18H19
1.1 Overview .19H19
1.2 Specifications .20H20
1.3 Conformance .21H20
2 Normative references .22H20
3 Terms, definitions, abbreviations, symbols and conventions .23H22
3.1 Referenced terms and definitions .24H22
3.2 Additional terms and definitions for distributed automation .25H23
3.3 Additional terms and definitions for decentralized periphery .26H25
3.4 Additional terms and definitions for media redundancy .27H33
3.5 Abbreviations and symbols .28H34
3.6 Additional abbreviations and symbols for distributed automation .29H35
3.7 Additional abbreviations and symbols for decentralized periphery.30H35
3.8 Additional abbreviations and symbols for media redundancy .31H36
3.9 Conventions .32H36
4 Concepts .33H39
5 Data type ASE.34H39
5.1 General .35H39
5.2 Formal definition of data type objects .36H42
5.3 FAL defined data types.37H43
5.4 Data type ASE service specification .38H86
6 Communication model for common services .39H86
6.1 Concepts .40H86
6.2 ASE data types.41H86
6.3 ASEs .42H87
7 Communication model for distributed automation.43H184
7.1 Concepts .44H184
7.2 ASE data types.45H191
7.3 ASEs .46H195
7.4 ARs .47H412
7.5 Summary of FAL classes .48H416
7.6 Summary of FAL services .49H417
8 Communication model for decentralized periphery.50H420
8.1 Concepts .51H420
8.2 ASE data types.52H436
8.3 ASEs .53H436
8.4 Behavior of an IO device .54H671
8.5 Behavior of an IO controller .55H737
8.6 Application characteristics .56H744
---------------------- Page: 8 ----------------------
61158-5-10 © IEC:2007(E) – 3 –
Annex A (informative) Device instances .57H746
Annex B (informative) Components of an Ethernet interface .58H748
Annex C (informative) Scheme of MAC address assignment .59H752
Annex D (informative) Collection of objects.60H753
Annex E (informative) Measurement of the fast startup time.61H754
Bibliography.62H755
Figure 1 – Data type class hierarchy example .63H40
Figure 2 – NetworkTime date relation.64H63
Figure 3 – UTF-8 coding of four different characters .65H67
Figure 4 – PTCP applications.66H100
Figure 5 – Clock drift measurement .67H110
Figure 6 – Multiple synchronization.68H110
Figure 7 –MRP stack.69H112
Figure 8 – Ring topology with one manager and clients.70H123
Figure 9 – MRM in an open ring .71H123
Figure 10 – More than one MRM in the ring .72H125
Figure 11 – Media redundancy diagnosis dependencies.73H126
Figure 12 – Locating the destination for redundant RT frames .74H165
Figure 13 – Example of periods at a local port .75H172
Figure 14 – FAL ASEs communication architecture .76H187
Figure 15 – Runtime object model.77H188
Figure 16 – Relationship between engineering and runtime.78H189
Figure 17 – Navigation in the runtime object model.79H190
Figure 18 – Operating state block diagram.80H229
Figure 19 – Device status model for the common diagnosis .81H230
Figure 20 – ACCO ASE structure .82H261
Figure 21 – Productive operation of data connections .83H262
Figure 22 – Quality code transfer – standard behavior .84H274
Figure 23 – Startup of a connection .85H275
Figure 24 – Quality code with communication fault.86H275
Figure 25 – Quality code when an connection is cleared .87H276
Figure 26 – Quality code when an connection is deactivated.88H276
Figure 27 – Quality code during the transfer of "incorrect" connection data .89H277
Figure 28 – Quality code for provider in "CBAReady" state .90H278
Figure 29 – Quality code when clearing an object from the provider .91H278
Figure 30 – Quality code when a connection is forced.92H279
Figure 31 – Quality code at QoS violation .93H279
Figure 32 – Push mode .94H286
Figure 33 – Pull mode overview .95H287
---------------------- Page: 9 ----------------------
– 4 – 61158-5-10 © IEC:2007(E)
Figure 34 – Detailed sequence chart of the pull mode.96H288
Figure 35 – QoS and ORPC communication channel.97H289
Figure 36 – QoS Violation within Pull Mode.98H290
Figure 37 – Monitoring the providers heartbeat .99H291
Figure 38 – State machine RemoteAcco .100H293
Figure 39 – State machine RemoteAccoProvider.101H293
Figure 40 – State machine RemoteAccoProvider .102H294
ORPC
Figure 41 – State machine AR – Provider .103H294
ORPC
Figure 42 – State machine GetConnectionData – Provider.104H295
Figure 43 – State machine ProviderConnection.105H295
Figure 44 – State machine ProvConnActivation.106H296
Figure 45 – State machine WorkerORPC .107H296
Figure 46 – Communication stack of distributed automation devices .108H297
Figure 47 – Application relations between devices .109H298
Figure 48 – Communication relations .110H298
Figure 49 – RT communication channel .111H300
Figure 50 – Interaction between provider and consumer .112H302
Figure 51 – State machine AR – Consumer .113H304
SRT
Figure 52 – State machine AR – Provider .114H304
SRT
Figure 53 – State machine AccoDataCR – Consumer.115H305
Figure 54 – State machine AccoDataCR – Provider .116H306
Figure 55 – RT frame layout.117H307
Figure 56 – Establishing an AccoDataCR.118H308
Figure 57 – Flowchart of the copy cycle for local connections .119H309
Figure 58 – State machine connect attempt .120H313
Figure 59 – Productive operation of data connections (ORPC channel).121H320
Figure 60 – Productive operation of data connections (RT channel) .122H321
Figure 61 – Productive operation of data connections (Local channel) .123H321
Figure 62 – Data flow for cyclic RT .124H322
Figure 63 – Failure of the provider in productive operation (ORPC push mode).125H324
Figure 64 – Failure of the provider in productive operation (ORPC pull mode) .126H325
Figure 65 – Scenario 1: Provider failure in productive operation (RT).127H326
Figure 66 – Scenario 2: Recovery from provider failure in productive operation (RT).128H327
Figure 67 – Failure of the consumer (push mode) .129H327
Figure 68 – Failure of the consumer (pull mode) .130H328
Figure 69 – Failure of the consumer.131H329
Figure 70 – Failure of the provider when setting up connections .132H331
Figure 71 – Information levels.133H332
Figure 72 – ACCO ASE status model for the common diagnosis .134H332
Figure 73 – ACCO ASE status model for the detailed diagnosis .135H333
Figure 74 – Structure of the transmitted connection data .136H375
---------------------- Page: 10 ----------------------
61158-5-10 © IEC:2007(E) – 5 –
Figure 75 – Example of communication between controlling devices and field devices.137H421
Figure 76 – Example of communication between an engineering station and several
controlling and field devices .138H421
Figure 77 – Example of communication between field devices and a server station.139H422
Figure 78 – Example of communication between field devices .140H422
Figure 79 – Structural units of one arbitrary API of an IO device (general) .141H424
Figure 80 – Example 1 structural units for interfaces and ports within API 0.142H425
Figure 81 – Example 2 structural units for interfaces and ports within API 0.143H426
Figure 82 – Overview of application processes .144H428
Figure 83 – IO device with APs, slots and subslots .145H429
Figure 84 – Application Process with application objects (APOs) .146H432
Figure 85 – Access to a remote APO .147H433
Figure 86 – Access to a remote APO for provider/consumer association .148H434
Figure 87 – Example of one AR with two AREPs.149H435
Figure 88 – Relation of a record data object to one real object.150H437
Figure 89 – Relation of a record data object to two real objects .151H438
Figure 90 – Overview IO ASE service interactions .152H448
Figure 91 – Example of a resource model at the alarm source .153H525
Figure 92 – General isochronous application model (example).154H560
Figure 93 – ASE relations in an IO device operating in isochronous mode .155H566
Figure 94 – State machine relations in an IO device operating in isochronous mode .156H566
Figure 95 – SyncCtl state diagram .157H570
Figure 96 – Output state diagram.158H572
Figure 97 – Input state diagram .159H577
Figure 98 – Assignment of communication relationship to application relationship .160H650
Figure 99 – Implicit application relationship.161H653
Figure 100 – Example IO application relationship (one-to-one) .162H655
Figure 101 – Example IO application relationship one-to-many .163H656
Figure 102 – Overview ASE state machines for IO device .164H672
Figure 103 – State diagram application startup IO device.165H673
Figure 104 – State diagram startup manager IO device.166H681
Figure 105 – State diagram IRT port state IO device (standard) .167H684
Figure 106 – State diagram IRT port
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.