SIST EN IEC 61158-6-27:2023
(Main)Industrial communication networks - Fieldbus Specifications Part 6-27: Application layer protocol specification - Type 27 elements (IEC 61158-6-27:2023)
Industrial communication networks - Fieldbus Specifications Part 6-27: Application layer protocol specification - Type 27 elements (IEC 61158-6-27:2023)
1.1 General
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 part of IEC 61158 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 27 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 International Standard defines in an abstract way the externally visible service provided by the different Types of 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 International Standard is to define the services provided to
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.
This International Standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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 289 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this International Standard to provide access to the FAL to control certain aspects of its operation.
1.2 Specifications
[...]
1.3 Conformance
[...]
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-27: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 27-Elemente (IEC 61158-6-27:2023)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-27 : Spécification du protocole de la couche application - Éléments de type 27 (IEC 61158-6-27:2023)
L’IEC 61158-6-27:2023 donne les éléments communs visant à assurer les communications de messagerie de base à temps critique et à temps non critique entre les programmes d’application d’un environnement d’automatisation et d’un matériel spécifique au bus de terrain de type 27. Le terme "à temps critique" est utilisé pour indiquer la présence d’une fenêtre temporelle, dans laquelle il est exigé de réaliser une ou plusieurs actions spécifiées selon un niveau défini de certitude. Tout manquement à réaliser ces actions dans la fenêtre de temps prévue risque de provoquer la défaillance des applications qui les demandent, avec le risque de mettre en danger l’équipement, l’usine, voire les personnes.
Le présent document définit de manière abstraite les caractéristiques visibles de l’extérieur fournies par la couche application de bus de terrain de type 27 en ce qui concerne:
la syntaxe abstraite définissant les unités de données du protocole de la couche application transmises entre les entités d’application de communication;
la syntaxe de transfert définissant les unités de données du protocole de la couche application transmises entre les entités d’application de communication;
les diagrammes d’états de contexte d’application définissant le comportement de service d’application observable entre les entités d’application en communication; et
les diagrammes d’états de relations entre applications définissant le comportement de communication visible entre les entités d’application en communication.
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-27. del: Specifikacija protokola na aplikacijski ravni - Elementi tipa 27 (IEC 61158-6-27:2023)
Aplikacijska raven procesnih vodil (FAL) uporabniškim programom omogoča dostop do komunikacijskega okolja procesnih vodil. Glede na to je mogoče aplikacijsko raven procesnih vodil šteti za »okno med ustreznimi aplikacijami«.
Ta del standarda IEC 61158 določa skupne elemente za osnovne časovno kritične in časovno nekritične sporočilne komunikacije med aplikacijami v avtomatizacijskem okolju ter material, specifičen za procesna vodila tipa 27. Izraz »časovno kritičen« se uporablja za predstavitev prisotnosti časovnega okna, v okviru katerega se zahteva dokončanje enega ali več opredeljenih dejanj z določeno stopnjo gotovosti. Zaradi neuspešnega dokončanja opredeljenih dejanj v časovnem oknu je možna odpoved aplikacij, ki zahtevajo dejanja, pri čemer so ogroženi oprema, obrat in morda človeška življenja.
Ta mednarodni standard na abstrakten način določa na zunaj vidno opravilo, ki ga zagotavlja aplikacijska raven procesnih vodil različnih tipov v smislu:
a) abstraktnega modela za določanje aplikacijskih virov (objektov), ki ga lahko upravljajo uporabniki prek opravila aplikacijske ravni procesnih vodil,
b) primitivnih dejanj in dogodkov opravila;
c) parametrov, povezanih z vsakim primitivnim dejanjem in dogodkom, ter obliko, ki jo prevzamejo, in
d) medsebojne povezave med temi dejanji in dogodki ter njihovimi veljavnimi zaporedji.
Namen tega mednarodnega standarda je določiti opravila, ki se zagotavljajo za:
a) uporabnika aplikacijske ravni procesnih vodil na meji med uporabniško in aplikacijsko ravnjo referenčnega modela procesnega vodila, in
b) upravljanje sistemov na meji med aplikacijsko ravnjo in upravljanjem sistemov za referenčni model procesnega vodila.
Ta mednarodni standard določa strukturo in opravila aplikacijske ravni procesnih vodil IEC v skladu z osnovnim referenčnim modelom OSI (ISO/IEC 7498-1) in strukturo aplikacijske ravni OSI (ISO/IEC 9545).
Opravila in protokole aplikacijske ravni procesnih vodil zagotavljajo aplikacijski osebki (AE) aplikacijske ravni procesnih vodil znotraj aplikacijskih procesov. Aplikacijski osebek aplikacijske ravni procesnih vodil sestavljata sklop objektno usmerjenih aplikacijskih opravilnih elementov (ASE) in osebek za upravljanje ravni (LME), ki upravlja aplikacijski osebek. Aplikacijski opravilni elementi zagotavljajo komunikacijska opravila, ki delujejo na sklopu povezanih razredov objektov aplikacijskega procesa (APO). Med aplikacijske opravilne elemente aplikacijske ravni procesnih vodil spada aplikacijski opravilni element za upravljanje, ki zagotavlja skupen sklop opravil za upravljanje primerkov razredov aplikacijske ravni procesnih vodil.
Čeprav ta opravila določajo način izdajanja ter dostavljanja zahtev in odzivov z vidika aplikacij, ne zajemajo specifikacije v zvezi s tem, kako naj se nanje odzovejo aplikacije, ki te zahteve in odzive oddajajo. To pomeni, da vedenjski vidiki aplikacij niso opredeljeni; opredeljena je le definicija zahtev in odzivov, ki jih lahko pošiljajo/prejemajo. Tako se 289 uporabnikom aplikacijske ravni procesnih vodil omogoči večja prilagodljivost pri standardizaciji takega vedenja objektov. Poleg teh opravil so v tem mednarodnem standardu opredeljena tudi nekatera podporna opravila, da se omogoči dostop do aplikacijske ravni procesnih vodil za nadzorovanje nekaterih vidikov njenega delovanja.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2023
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-27. del:
Specifikacija protokola na aplikacijski ravni - Elementi tipa 27 (IEC 61158-6-
27:2023)
Industrial communication networks - Fieldbus Specifications Part 6-27: Application layer
protocol specification - Type 27 elements
(IEC 61158-6-27:2023)
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-27: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 27-Elemente (IEC 61158-6-27:2023)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-27 :
Spécification du protocole de la couche application - Éléments de type 27 (IEC 61158-6-
27:2023)
Ta slovenski standard je istoveten z: EN IEC 61158-6-27:2023
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD EN IEC 61158-6-27
NORME EUROPÉENNE
EUROPÄISCHE NORM April 2023
ICS 25.040
English Version
Industrial communication networks - Fieldbus Specifications Part
6-27: Application layer protocol specification - Type 27 elements
(IEC 61158-6-27:2023)
Réseaux de communication industriels - Spécifications des Industrielle Kommunikationsnetze - Feldbusse - Teil 6-27:
bus de terrain - Partie 6-27 : Spécification du protocole de Protokollspezifikation des Application Layer
la couche application - Éléments de type 27 (Anwendungsschicht) - Typ 27-Elemente
(IEC 61158-6-27:2023) (IEC 61158-6-27:2023)
This European Standard was approved by CENELEC on 2023-04-20. 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 CEN-CENELEC
Management Centre 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 CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2023 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 61158-6-27:2023 E
European foreword
The text of document 65C/1205/FDIS, future edition 1 of IEC 61158-6-27, 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 approved by CENELEC as EN IEC 61158-6-
27:2023.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2024-01-20
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2026-04-20
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 61158-6-27:2023 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 standard indicated:
IEC 61158-1:2023 NOTE Approved as EN IEC 61158-1:2023 (not modified)
IEC 61158-2 NOTE Approved as EN 61158-2
IEC 61158-6 (series) NOTE Approved as EN 61158-6 (series)
IEC 61784-1 (series) NOTE Approved as EN IEC 61784-1 (series)
IEC 61784-2 (series) NOTE Approved as EN IEC 61784-2 (series)
To be published. Stage at the time of publication: FprEN IEC 61784-1-X:2023.
To be published. Stage at the time of publication: FprEN IEC 61784-2-X:2023.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 1 Where an International Publication has been modified by common modifications, indicated by (mod), the
relevant EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available
here: www.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 61158-5-27 2023 Industrial communication networks - EN IEC 61158-5-27 2023
Fieldbus specifications - Part 5-27:
Application layer service definition - Type
27 elements
ISO/IEC 646 - Information technology; ISO 7-bit coded - -
character set for information interchange
ISO/IEC 7498-1 - Information technology - Open Systems - -
Interconnection - Basic reference model:
The basic model
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application layer
structure
ISO/IEC 9899 - Information technology - Programming - -
languages - C
ISO/IEC 10731 - Information technology - Open Systems - -
Interconnection - Basic Reference Model -
Conventions for the definition of OSI
services
ISO/IEC 19501 2005 Information technology - Open Distributed - -
Processing - Unified Modeling Language
(UML) Version 1.4.2
ISO/IEC/IEEE 60559 2020 Information technology - Microprocessor - -
Systems - Floating-Point arithmetic
ISO/IEC/IEEE 8802-3 - Telecommunications and exchange - -
between information technology systems –
Requirements for local and metropolitan
area networks – Part 3: Standard for
Ethernet
IEEE Std 802.1D - IEEE Standard for Local and metropolitan - -
area networks: Media Access Control
(MAC) Bridges
IEEE Std 802.1Q - IEEE Standard for Local and metropolitan - -
area networks - Bridges and Bridged
Networks
IEEE Std 802.1AB - IEEE Standard for Local and metropolitan - -
area networks: Station and Media Access
Control Connectivity Discovery
IEEE Std 802.1AS - IEEE standard for Local and metropolitan - -
area networks - Timing and
Synchronization for Time-Sensitive
Applications in Bridged Local Area
Networks
IETF RFC 768 1980 User Datagram Protocol - -
IETF RFC 791 1981 Internet Protocol - -
IETF RFC 826 1982 Ethernet Address Resolution Protocol: Or - -
Converting Network Protocol Addresses to
48.bit Ethernet Address for Transmission
on Ethernet Hardware
IETF RFC 1112 1989 Host Extensions for IP multicasting - -
IETF RFC 2460 1998 Internet Protocol - Version 6 (IPv6) - - -
Specification
IEC 61158-6-27 ®
Edition 1.0 2023-03
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –
Part 6-27: Application layer protocol specification – Type 27 elements
Réseaux de communication industriels – Spécifications des bus de terrain –
Partie 6-27: Spécification du protocole de la couche application – Éléments de
type 27
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040 ISBN 978-2-8322-6620-5
– 2 – IEC 61158-6-27:2023 © IEC 2023
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 10
1.1 General . 10
1.2 Specifications . 10
1.3 Conformance . 11
2 Normative references . 11
3 Terms, definitions, abbreviated terms, symbols and conventions . 12
3.1 Referenced terms and definitions . 12
3.1.1 Terms and definitions from ISO/IEC 7498-1 . 12
3.1.2 Terms and definitions from ISO/IEC 9545 . 12
3.1.3 Terms and definitions from ISO/IEC 8824-1 . 13
3.1.4 Terms and definitions from ISO/IEC 10731 . 13
3.1.5 Terms and definitions from ISO/IEC 19501 . 13
3.2 Additional terms and definitions . 13
3.3 Abbreviations and symbols . 22
3.4 Conventions . 24
3.4.1 General conventions . 24
3.4.2 PDU data type conventions . 24
3.4.3 State machine conventions . 24
4 Abstract syntax . 26
4.1 General . 26
4.2 Basic Data types . 27
4.3 FAL PDU types . 28
4.3.1 General . 28
4.3.2 Top of APDU types: _APDU . 31
4.3.3 PDUs for field system management service . 31
4.3.4 Detailed definitions of _FID-PDUs . 34
4.3.5 PDUs for field device control service . 48
4.3.6 PDUs for message service . 57
4.4 Detailed definitions of _FDCService-PDUs . 58
4.4.1 Enhanced PDU type . 58
4.5 Device profile . 72
5 Transfer syntax . 72
5.1 Concepts . 72
5.2 Encode rules . 73
5.2.1 INTEGER and its subtypes . 73
5.2.2 REAL type and its subtypes . 74
5.2.3 BIT STRING type . 76
5.2.4 OCTET STRING type and IA5String type . 77
5.2.5 NULL type . 77
5.2.6 Structure type and Array type . 77
6 Structure of FAL protocol state machine . 78
7 AP-context state machine (APC SM) . 80
7.1 Overview. 80
7.2 State descriptions . 81
IEC 61158-6-27:2023 © IEC 2023 – 3 –
7.3 Triggering events . 81
7.4 Action descriptions at state transitions . 82
8 FAL service protocol machines (FSPM) . 84
8.1 Overview. 84
8.2 RT Protocol Machine (RT PM). 84
8.2.1 Link layer discovery . 84
8.2.2 MAC bridges . 84
8.2.3 Virtual bridges . 105
8.2.4 IP suite . 105
8.2.5 DLL mapping protocol machine (DMPM) . 105
8.3 Field System Management Protocol Machine (FSM PM) . 110
8.3.1 Overview . 110
8.3.2 Discovery and basic configuration . 112
8.3.3 Starting up of system . 115
8.3.4 Sync methods . 144
8.3.5 Plug-and-play entry . 153
8.4 Field Deice Control Protocol Machine (FDC PM) . 154
8.4.1 Protocol overview . 154
8.4.2 Cyclic communication mode . 156
8.4.3 Event driven communication mode . 160
8.4.4 Master Protocol Machine (FDCPM-M) . 161
8.4.5 Slave Protocol Machine (FDCPM-S) . 169
8.4.6 Error procedure summary . 179
8.5 Message Protocol Machine (MSG PM) . 181
8.5.1 Protocol overview . 181
8.5.2 Requester Protocol Machine (MSGPM-RQ) . 183
8.5.3 Responder Protocol Machine (MSGPM-RS) . 186
9 Application relationship protocol machine (ARPM) . 188
9.1 General . 188
9.2 ARPM for FDC ASE . 188
9.2.1 Overview . 188
9.2.2 ARPM for FDC Master (ARPM-FDCM) . 189
9.2.3 ARPM for FDC Slave (ARPM-FDCS) . 196
9.3 ARPM for MSG ASE (ARPM-MSG) . 203
9.3.1 State descriptions . 203
9.3.2 Triggering events . 203
9.3.3 Action descriptions at state transitions . 204
10 DLL mapping protocol machines (DMPMs) . 204
Annex A (informative) Device profile and FDC command sets . 205
Annex B (normative) Virtual memory space and Device Information . 207
B.1 Overview. 207
B.2 Communication Data Object . 207
B.3 Device Information . 208
B.3.1 Device identifier area structure . 208
B.3.2 Detail specifications of device IDs . 209
Annex C (informative) Basic message function . 217
Bibliography . 218
– 4 – IEC 61158-6-27:2023 © IEC 2023
Figure 1 – Encode of Integer subtypes . 73
Figure 2 – Example of transfer of INTEGER value . 74
Figure 3 – Encode of Unsigned subtypes . 74
Figure 4 – Float32 type encode . 75
Figure 5 – Float64 type encode . 75
Figure 6 – Bit field definition example with named bits . 76
Figure 7 – Bit field definition example with field size . 77
Figure 8 – SEQUENCE type encode . 78
Figure 9 – Structure of FAL protocol state machines . 80
Figure 10 – State chart diagram of APC SM . 81
Figure 11 – Master CTC state transition chart . 86
Figure 12 – Slave CTC state transition chart . 96
Figure 13 – Structuring of the protocol machines within the DMPM (bridge) . 106
Figure 14 – SRC state transition chart . 106
Figure 15 – Example of network configuration . 111
Figure 16 – Network initialization procedures . 112
Figure 17 – Neighboring node notification sequence . 113
Figure 18 – Connected node detection sequence . 114
Figure 19 – Example of neighboring node information . 115
Figure 20 – FSMUL state transition chart for the master with SM function . 116
Figure 21 – FSMUL state transition chart for the master without SM function . 129
Figure 22 – FSMUL state transition chart for a slave . 138
Figure 23 – Sequence of SM delay time notification by CDO writing. 145
Figure 24 – Delay measurement sequence (SM: BM) . 147
Figure 25 – Master delay measurement sequence for the BM (SM: master with band
master function (BM)) . 148
Figure 26 – Delay measurement sequence for the master other than the BM (SM: BM). 149
Figure 27 – Delay measurement sequence (SM: S#1) . 151
Figure 28 – Master delay measurement sequence for the BM (SM: S#1) . 152
Figure 29 – Plug-and-play entry sequence . 154
Figure 30 – Example communication cycle of FDC master AP . 156
Figure 31 – Example communication cycle of FDC slave AP . 157
Figure 32 – Synchronous command communication in sync state . 158
Figure 33 – Asynchronous command communication in sync state . 159
Figure 34 – Asynchronous command communication in async state . 160
Figure 35 – Event-driven communication . 161
Figure 36 – State chart diagram of FDCPM-M . 162
Figure 37 – State chart diagram of FDCPM-S . 170
Figure 38 – PDU transmission flow for user message . 182
Figure 39 – PDU transmission flow for one-way message . 183
Figure 40 – State chart diagram of MSGPM-RQ . 184
Figure 41 – State chart diagram of MSGPM-RS . 186
Figure 42 – Example of single transfer process . 188
IEC 61158-6-27:2023 © IEC 2023 – 5 –
Figure 43 – Example of dual transfer process . 189
Figure 44 – State chart diagram of ARPM-FDCM . 190
Figure 45 – Statechart diagram of ARPM-FDCS . 196
Figure 46 – Statechart diagram of ARPM-MSG . 203
Figure B.1 – Memory map of virtual memory space . 207
Figure B.2 – Memory map of device ID area . 208
Table 1 – State transition descriptions . 25
Table 2 – Description of state machine elements . 25
Table 3 – Conventions used in state machines . 26
Table 4 – Multicast address . 29
Table 5 – Length_or_type . 29
Table 6 – IPv4 Header . 30
Table 7 – IPv6 Header . 30
Table 8 – UDP Header . 30
Table 9 – Node address . 33
Table 10 – Mapping for Protocol State Machines . 79
Table 11 – State descriptions of APC SM . 81
Table 12 – Trigger event descriptions of APC SM . 82
Table 13 – Transitions of APC SM . 83
Table 14 – Master CTC state transition table . 87
Table 15 – Slave CTC state transition table . 96
Table 16 – List of CTC macros . 101
Table 17 – The primitives and parameters for FDC interface issued by FDC . 103
Table 18 – The primitives and parameters for FSM interface issued by CTC . 104
Table 19 – The list of primitives and parameters (FSM source) . 104
Table 20 – The list of primitives and parameters (FSMUL source) . 105
Table 21 – SRC state transition table . 107
Table 22 – List of SRC macros . 108
Table 23 – List of SRC functions . 109
Table 24 – Primitives and parameters for SRC-CTC interface . 110
Table 25 – Send frame primitive and parameters . 110
Table 26 – Receive frame primitives and parameters . 110
Table 27 – Primitives and parameters of repeat select service . 110
Table 28 – FSMUL state transition table for the master with SM function . 117
Table 29 – FSMUL state transition table for the master without SM function . 129
Table 30 – FSMUL state transition table for a slave . 138
Table 31 – List of FSMUL macros . 142
Table 32 – FDC protocol mode . 155
Table 33 – State descriptions of FDCPM-M . 162
Table 34 – Trigger event descriptions of FDCPM-M . 163
Table 35 – Transitions of main SM of FDCPM-M . 164
Table 36 – Transitions of submachine of FDCPM-M . 166
– 6 – IEC 61158-6-27:2023 © IEC 2023
Table 37 – State descriptions of FDCPM-S . 170
Table 38 – Trigger event descriptions of FDCPM-S . 171
Table 39 – Transitions of main SM of FDCPM-S . 172
Table 40 – Transitions of submachine of FDCPM-S . 174
Table 41 – State descriptions of MSGPM-RQ . 184
Table 42 – Trigger event descriptions of MSGPM-RQ . 185
Table 43 – Transitions of MSGPM-RQ . 185
Table 44 – State descriptions of MSGPM-RS . 186
Table 45 – Trigger event descriptions of MSGPM-RS . 187
Table 46 – Transitions of MSGPM-RS . 187
Table 47 – State descriptions of ARPM-FDCM . 191
Table 48 – Trigger event descriptions of ARPM-FDCM . 193
Table 49 – Transitions of main SM of ARPM-FDCM . 193
Table 50 – Transitions of submachine of ARPM-FDCM . 195
Table 51 – State descriptions of ARPM-FDCS . 197
Table 52 – Trigger event descriptions of ARPM-FDCS . 199
Table 53 – Transitions of main SM of ARPM-FDCS . 200
Table 54 – Transitions of submachine of ARPM-FDCS . 201
Table 55 – State descriptions of ARPM-MSG . 203
Table 56 – Trigger event descriptions of ARPM-MSG . 203
Table 57 – Transitions of ARPM-MSG . 204
Table A.1 – Example of registered device profiles . 205
Table A.2 – Example command list of the profile '00'H . 206
Table B.1 – Memory map of CDO area . 207
Table B.2 – Specifications of device IDs . 209
Table C.1 – Example of message command set . 217
IEC 61158-6-27:2023 © IEC 2023 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-27: Application layer protocol specification –
Type 27 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent
rights. IEC shall not be held responsible for identifying any or all such patent rights.
Attention is drawn to the fact that the use of the associated protocol type is restricted by its
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 layer protocol type to be used with
other layer protocols of the same type, or in other type combinations explicitly authorized by its
intellectual-property-right holders.
NOTE Combinations of protocol types are specified in the IEC 61784 1 series and the IEC 61784 2 series.
IEC 61158‑6‑27 has been prepared by subcommittee 65C: Industrial networks, of IEC technical
committee 65: Industrial-process measurement, control and automation. It is an International
Standard.
– 8 – IEC 61158-6-27:2023 © IEC 2023
The text of this International Standard is based on the following documents:
Draft Report on voting
65C/1205/FDIS 65C/1234/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts of the IEC 61158 series, under the general title Industrial communication
networks – Fieldbus specifications, can be found on the IEC web site.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IEC 61158-6-27:2023 © IEC 2023 – 9 –
INTRODUCTION
This document is one of a series produced to facilitate the interconnection of automation system
components. It is related to other standards in the set as defined by the "three-layer" fieldbus
reference model described in IEC 61158-1.
The application protocol provides the application service by making use of the services
available from the data-link or other immediately lower layer. The primary aim of this document
is to provide a set of rules for communication expressed in terms of the procedures to be carried
out by peer application entities (AEs) at the time of communication. These rules for
communication are intended to provide a sound basis for development in order to serve a variety
of purposes:
• as a guide for implementers and designers;
• for use in the testing and procurement of equipment;
• as part of an agreement for the admittance of systems into the open systems environment;
• as a refinement to the understanding of time-critical communications within OSI.
This document is concerned, in particular, with the communication and interworking of sensors,
effectors and other automation devices. By using this document together with other documents
positioned within the OSI or fieldbus reference models, otherwise incompatible systems can
work together in any combination.
The International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed
that compliance with this document may involve the use of a patent. IEC takes no position
concerning the evidence, validity, and scope of this patent right.
The holder of this patent right has assured IEC that s/he is willing to negotiate licences under
reasonable and non-discriminatory terms and conditions with applicants throughout the world.
In this respect, the statement of the holder of this patent right is registered with IEC. Information
may be obtained from the patent database available at patents.iec.ch.
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights other than those in the patent database. IEC shall not be held
responsible for identifying any or all such patent rights.
– 10 – IEC 61158-6-27:2023 © IEC 2023
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 6-27: Application layer protocol specification –
Type 27 elements
1 Scope
1.1 General
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 part of IEC 61158 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 27 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 document defines in an abstract way the externally visible behavior provided by the
Type 27 fieldbus application layer in terms of
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machines defining the application service behavior visibly
between communicating application entities, and
• the application relationship state machines defining the communication behavior visibly
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the representation-on-wire of the service primitives defined in IEC 61158-5-27, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 27 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure
(ISO/IEC 9545).
1.2 Specifications
The principal objective of this document is to specify the syntax and behavior of the application
layer protocol that conveys the application layer services defined in IEC 61158-5-27.
A secondary objective is to provide migration paths from previously existing industrial
communications protocols. It is this latter objective which gives rise to the diversity of protocols
standardized in IEC 61158-6 series.
IEC 61158-6-27:2023 © IEC 2023 – 11 –
1.3 Conformance
This document does not specify individual implementations or products, nor does it constrain
the implementations of application layer entities within industrial automation systems.
Conformance is achieved through implementation of this application layer protocol specification.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...