SIST EN IEC 61158-6-26:2023
(Main)Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer protocol specification - Type 26 elements (IEC 61158-6-26:2023)
Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer protocol specification - Type 26 elements (IEC 61158-6-26: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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of
a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units;
c) the application context state machine defining the application service behavior visible between communicating application entities;
d) the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this document is to define the protocol provided to
a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and
b) define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 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-2.
A secondary objective is to provide migration paths from previously-existing industrial communications protocols.
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.
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-26: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 26-Elemente (IEC 61158-6-26:2023)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-26: Spécification du protocole de la couche liaison de données - Eléments de type 26 (IEC 61158-6-26:2023)
L'IEC 61158-6-26: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 26. 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.
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-26. del: Specifikacija protokola na aplikacijski ravni - Elementi tipa 26 (IEC 61158-6-26: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 2. 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 opredeljuje interakcije med oddaljenimi aplikacijami in določa na zunaj vidno vedenje, ki ga zagotavlja aplikacijska raven procesnih vodil tipa 2 v smislu:
a) formalne abstraktne sintakse, ki določa podatkovne enote protokola aplikacijske ravni, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo;
b) prenosne sintakse, ki opredeljuje pravila kodiranja, ki se uporabljajo za podatkovne enote protokola aplikacijske ravni;
c) stroja stanja aplikacijskega konteksta, ki opredeljuje vedenje aplikacijskega opravila, vidnega med aplikacijskimi osebki, ki komunicirajo;
d) strojev stanja aplikacijskega razmerja, ki opredeljujejo komunikacijsko vedenje med aplikacijskimi osebki, ki komunicirajo.
Namen tega dokumenta je opredeliti protokol, ki se zagotavlja za:
a) določitev žične predstavitve primitivov opravil iz standarda IEC 61158-5-2, in
b) določitev na zunaj vidnega vedenja, povezanega z njihovim prenosom.
Ta dokument določa protokol aplikacijske ravni procesnih vodil tipa 2 v skladu z osnovnim referenčnim modelom OSI (ISO/IEC 7498-1) in strukturo aplikacijske ravni OSI (ISO/IEC 9545).
General Information
Relations
Overview
EN IEC 61158-6-26:2023 defines the application layer protocol specification for Type 26 Fieldbus elements within industrial communication networks. It is part of the IEC 61158 family and describes the Fieldbus Application Layer (FAL) that provides application programs with a standardized “window” onto the fieldbus communication environment. The standard specifies the externally visible protocol behaviour (syntax, encoding and state machines) for time‑critical and non‑time‑critical messaging between automation applications, and it aligns with the OSI Basic Reference Model and OSI application layer structure.
Key topics and requirements
- FAL abstract syntax and PDUs: formal definitions of application layer protocol data units (PDUs) including common PDUs such as Token-PDU, Transparent-msg, Participation-req and a wide set of read/write, control and vendor-specific PDUs.
- Transfer syntax and encoding: rules that define the wire representation of PDUs; uses formal encoding approaches referenced in ISO/IEC ASN.1 and related encoding rules (e.g., BER/CER/DER).
- Application context and relationship state machines: state-machine descriptions that define application service behaviour and the communication relationships visible to remote application entities.
- Timing and time‑critical behaviour: specification of time-windows and required certainty levels for actions where missing deadlines risks equipment, plant or human safety.
- Network management and parameters: PDUs and structures for network parameter read/write, logical ring maintenance, node addition/drop-out, and diagnostics/logging.
- Conformance approach: defines protocol conformance criteria (not implementations or products); supports migration paths from earlier industrial communication protocols.
Applications and who uses it
- Device and fieldbus stack vendors: to implement Type 26 FAL protocol in firmware and software stacks.
- Automation and control system integrators: to ensure device interoperability and predictable time‑critical messaging in plants.
- Control engineers and system architects: when designing networks that require formal timing guarantees and standardized application-layer behaviour.
- Safety and functional‑safety assessors: for understanding timing constraints and protocol‑level behaviours relevant to risk assessments.
- Standards bodies and test laboratories: for conformance testing and certification of Type 26 Fieldbus implementations.
Related standards
- IEC 61158-5-26 (Application layer service definition - Type 26)
- ISO/IEC 7498-1 (OSI Basic Reference Model)
- ISO/IEC 9545 (OSI application layer structure)
- ISO/IEC 8824‑1 / 8825‑1 (ASN.1 and encoding rules)
- Relevant IETF RFCs and Ethernet/IP references used for lower-layer interoperability
This standard is essential for anyone implementing or integrating Fieldbus Type 26 application-layer protocols, providing the formal syntax, encoding and behavioural rules needed for interoperable, time‑sensitive industrial communication.
Frequently Asked Questions
SIST EN IEC 61158-6-26:2023 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer protocol specification - Type 26 elements (IEC 61158-6-26:2023)". This standard covers: 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 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-2. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. 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.
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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 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-2. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. 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.
SIST EN IEC 61158-6-26:2023 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 35.100.70 - Application layer; 35.110 - Networking. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN IEC 61158-6-26:2023 has the following relationships with other standards: It is inter standard links to SIST EN IEC 61158-6-26:2019, SIST EN IEC 61158-6-2:2019. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase SIST EN IEC 61158-6-26:2023 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of SIST standards.
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2023
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-26. del:
Specifikacija protokola na aplikacijski ravni - Elementi tipa 26 (IEC 61158-6-
26:2023)
Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer
protocol specification - Type 26 elements (IEC 61158-6-26:2023)
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-26: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 26-Elemente (IEC 61158-6-26:2023)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-26:
Spécification du protocole de la couche liaison de données - Eléments de type 26 (IEC
61158-6-26:2023)
Ta slovenski standard je istoveten z: EN IEC 61158-6-26: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-26
NORME EUROPÉENNE
EUROPÄISCHE NORM May 2023
ICS 25.040.40; 35.100.70; 35.110 Supersedes EN IEC 61158-6-26:2019
English Version
Industrial communication networks - Fieldbus specifications -
Part 6-26: Application layer protocol specification - Type 26
elements
(IEC 61158-6-26:2023)
Réseaux de communication industriels - Spécifications des Industrielle Kommunikationsnetze - Feldbusse - Teil 6-26:
bus de terrain - Partie 6-26: Spécification du protocole de la Protokollspezifikation des Application Layer
couche liaison de données - Eléments de type 26 (Anwendungsschicht) - Typ 26-Elemente
(IEC 61158-6-26:2023) (IEC 61158-6-26:2023)
This European Standard was approved by CENELEC on 2023-05-02. 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-26:2023 E
European foreword
The text of document 65C/1204/FDIS, future edition 2 of IEC 61158-6-26, 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
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2024-02-02
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2026-05-02
document have to be withdrawn
This document supersedes EN IEC 61158-6-26:2019 and all of its amendments and corrigenda (if
any).
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-26: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 NOTE Approved as EN IEC 61158-1
IEC 61784-1 (series) NOTE Approved as EN IEC 61784-1 (series)
IEC 61784-2 (series) NOTE Approved as EN IEC 61784-2 (series)
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-26 2023 Industrial communication networks - Fieldbus - -
specifications - Part 5-26: Application layer
service definition - Type 26 elements
IEC 61158-2-21 2023 Industrial networks - Profiles - Part 2-21: - -
Additional real-time fieldbus profiles based on
ISO/IEC/IEEE 8802-3 - CPF 21
ISO/IEC 7498-1 - Information technology - Open Systems - -
Interconnection - Basic reference model: The
basic model
ISO/IEC/IEEE 8802-3 - Telecommunications and exchange between - -
information technology systems -
Requirements for local and metropolitan area
networks - Part 3: Standard for Ethernet
ISO/IEC 8822 - Information technology - Open Systems - -
Interconnection - Presentation service
definition
ISO/IEC 8824-1 - Information technology - Abstract Syntax - -
Notation One (ASN.1) - Part 1: Specification
of basic notation
ISO/IEC 8825-1 - Information technology - ASN.1 encoding - -
rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)
ISO/IEC 9545 - Information technology - Open Systems - -
Interconnection - Application layer structure
ISO/IEC 9899 - Information technology - Programming - -
languages - C
IETF RFC 768 - User Datagram Protocol - -
IETF RFC 791 - Internet Protocol Darpa Internet Program - -
Protocol Specification
IETF RFC 792 - Internet Control Message Protocol - -
Publication Year Title EN/HD Year
IETF RFC 793 - Transmission Control Protocol Darpa Internet - -
Program Protocol Specification
IETF RFC 796 - Address mappings - -
IETF RFC 826 - Ethernet Address Resolution Protocol: Or - -
Converting Network Protocol Addresses to
48.bit Ethernet Address for Transmission on
Ethernet Hardware
IETF RFC 894 - Standard for the Transmission of IP - -
Datagrams over Ethernet Networks
IETF RFC 919 - Broadcasting Internet Datagrams - -
IETF RFC 922 - Broadcasting Internet datagrams in the - -
presence of subnets
IETF RFC 950 - Internet Standard Subnetting Procedure - -
IEC 61158-6-26 ®
Edition 2.0 2023-03
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-26: Application layer protocol specification – Type 26 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-6630-4
– 2 – IEC 61158-6-26:2023 © IEC 2023
CONTENTS
FOREWORD . 11
INTRODUCTION . 13
1 Scope . 14
1.1 General . 14
1.2 Specifications . 15
1.3 Conformance . 15
2 Normative references . 15
3 Terms, definitions, symbols, abbreviated terms and conventions . 16
3.1 Terms and definitions from other ISO/IEC standards . 17
3.1.1 Terms and definitions from ISO/IEC 7498-1 . 17
3.1.2 Terms and definitions from ISO/IEC 8822 . 17
3.1.3 Terms and definitions from ISO/IEC 9545 . 17
3.1.4 Terms and definitions from ISO/IEC 8824-1 . 17
3.1.5 Terms and definitions from ISO/IEC 8825-1 . 18
3.2 Type 26 specific terms and definitions . 18
3.3 Abbreviated terms and symbols . 22
3.4 Conventions . 24
3.4.1 Conventions used in state machines . 24
3.4.2 Convention for abstract syntax description . 26
3.4.3 Convention for reserved bits and octets . 26
3.4.4 Conventions for bit description in octets . 26
4 FAL syntax description . 27
4.1 General . 27
4.2 Overview of Type 26 fieldbus . 27
4.2.1 Application field and Common-memory . 27
4.2.2 Structure of Type 26 protocol . 28
4.2.3 Structure of Type 26 FAL . 29
4.2.4 Data link layer . 30
4.3 Operating principle . 31
4.3.1 Overview . 31
4.3.2 Logical ring maintenance . 31
4.3.3 Node addition . 34
4.3.4 Node in a logical ring . 38
4.3.5 Node drop-out . 39
4.3.6 Data transmission . 39
4.3.7 Data transmission frames . 49
4.4 FAL PDU abstract syntax . 52
4.4.1 Basic abstract syntax . 52
4.4.2 Transparent-msg- PDU . 55
4.4.3 Token-PDU . 55
4.4.4 Participation-req-PDU . 56
4.4.5 Byte-block-read PDUs . 56
4.4.6 Byte-block-write PDUs . 56
4.4.7 Word-block-read PDUs . 56
4.4.8 Word-block-write PDUs . 57
4.4.9 Network-parameter-read PDUs . 57
4.4.10 Network-parameter-write PDUs. 57
IEC 61158-6-26:2023 © IEC 2023 – 3 –
4.4.11 Stop-command PDUs . 57
4.4.12 Operation-command PDUs . 58
4.4.13 Profile-read PDUs . 58
4.4.14 Trigger-PDU . 58
4.4.15 Log-data-read PDUs . 58
4.4.16 Log-data-clear PDUs . 59
4.4.17 Message-return PDUs . 59
4.4.18 Vendor-specific-msg PDUs . 59
4.4.19 Start-TK-hld-time-mrmt PDUs . 60
4.4.20 Terminate-TK-hld-time-mrmt PDUs . 60
4.4.21 Start-GP_Comm-sndr-log PDUs . 60
4.4.22 Terminate-GP_Comm-sndr-log PDUs . 60
4.4.23 Set-remote-node-config-para PDUs . 61
4.4.24 Read-rmt-partici-node-mgt-info-para PDUs . 61
4.4.25 Read-rmt- node-mgt-info-para PDUs . 61
4.4.26 Read-rmt-node-set-info-para PDUs . 61
4.4.27 Reset-node PDUs . 62
4.4.28 Cyclic-data PDUs . 62
4.4.29 Extended-prticiption-req-PDU . 62
4.4.30 Extended-network-parameter-read PDUs . 63
4.4.31 Extended-network-parameter-write PDUs . 63
4.5 Data type assignments . 63
5 Transfer syntax . 65
5.1 Encoding rules . 65
5.1.1 Basic encoding . 65
5.1.2 Fixed length Unsigned encoding . 65
5.1.3 Fixed length BitString encoding . 65
5.1.4 OctetString encoding . 65
5.1.5 SEQUENCE encoding . 65
5.2 PDU elements encoding . 65
5.2.1 FALARHeader . 65
5.2.2 Transparent-msg PDU . 69
5.2.3 Token-PDU . 70
5.2.4 Participation-req-PDU . 71
5.2.5 Byte-block-read PDUs . 72
5.2.6 Byte-block-write PDUs . 74
5.2.7 Word-block-read PDUs . 75
5.2.8 Word-block-write PDUs . 77
5.2.9 Network-parameter-read PDUs . 79
5.2.10 Network-parameter-write PDUs. 83
5.2.11 Stop-command PDUs . 85
5.2.12 Operation-command PDUs . 87
5.2.13 Profile-read PDUs . 89
5.2.14 Trigger-PDU . 92
5.2.15 Log-data-read PDUs . 92
5.2.16 Log-data-clear PDUs . 98
5.2.17 Message-return PDUs . 100
5.2.18 Vendor-specific-msg PDUs . 102
5.2.19 Start-TK-hld-time-mrmt PDUs . 105
– 4 – IEC 61158-6-26:2023 © IEC 2023
5.2.20 Terminate-TK-hld-time-mrmt PDUs . 106
5.2.21 Start-GP_Comm-sndr-log PDUs . 110
5.2.22 Terminate-GP_Comm-sndr-log PDUs . 111
5.2.23 Set-remote-node-config-para PDUs . 114
5.2.24 Read-rmt-partici-node-mgt-info-para PDUs . 117
5.2.25 Read-rmt- node-mgt-info-para PDUs . 120
5.2.26 Read-rmt-node-set-info-para PDUs . 123
5.2.27 Reset-node PDUs . 125
5.2.28 Cyclic-data PDUs . 126
5.2.29 Extended-participation-request PDU . 129
5.2.30 Extended-network-parameter-read PDUs . 129
5.2.31 Extended-network-parameter-write PDUs . 132
6 FAL protocol state machines structure . 135
6.1 Overview. 135
6.2 Common variables, parameters, timers, counters, lists and queues . 136
6.2.1 V(3CWT), P(3CWT), T(3CWT): Three-lap-time-period-of-the-token-
circulation . 136
6.2.2 V(ACK): ACK received . 136
6.2.3 V(ACK_TN): ACK to this node . 137
6.2.4 V(AWT), P(AWT), T(AWT): Waiting-time-period-for-receiving-message-
acknowledge. 137
6.2.5 V(CBN): Current fragment number for fragmented cyclic-data
transmission . 137
6.2.6 V(CTFG): Cyclic-data fragment transfer . 137
6.2.7 V(CTRen), P (CTRen): Cyclic-data on CM1 and CM2 receive enable . 137
6.2.8 V(CTRQ): Cyclic-data transfer request . 137
6.2.9 V(ExCTRQ): Cyclic-data of CM3 transfer request . 138
6.2.10 C(ExCT): Cumulative count of extended-cyclic-data transmission . 138
6.2.11 V(ExCTRen), P(ExCTRen): Cyclic-data on CM3 receive enable . 138
6.2.12 V(ExTBN), P(ExTBN): Total fragment number of Cyclic-data on CM3 . 138
6.2.13 V(ExTSZ), P(ExTSZ): Total cyclic-data size on CM3 . 138
6.2.14 C(MCNT): Cumulative count of message transmission carried over . 138
6.2.15 V(MCV): Message transmission carried over. 138
6.2.16 V(MFT), P(MFT), T(MFT): Allowable-minimum-frame-interval-time. 138
6.2.17 V(MmtCntType): Measurement control type . 139
6.2.18 V(MRVRQ): Message receive request . 139
6.2.19 V(MSRQ): Message transfer request . 139
6.2.20 Q(MSRXQ): Message-RX-Queue . 139
6.2.21 Q(MTXQ): Message-TX-Queue . 139
6.2.22 V(NMTP): No message transmission in previous cycle . 139
6.2.23 V(PAT), P(PAT), T(PAT): Participation-request-frame-acceptance-time . 140
6.2.24 V(PnMgtIF): Participation-node-management-information List . 140
6.2.25 V(PWT), T(PWT): Participation-request-frame-transmission-waiting-time . 140
6.2.26 V(RCT): Allowable-refresh-cycle-time . 140
6.2.27 V(RMT), T(RMT): Refresh-cycle-measurement-time. 140
6.2.28 C(RTX): Retransmission count . 141
6.2.29 V(SEQ): Sequence number value List . 141
6.2.30 V(SN): Successor node . 141
6.2.31 V(SrtMmt): Measurement started . 141
IEC 61158-6-26:2023 © IEC 2023 – 5 –
6.2.32 Q(SVRXQ): Server-RX Queue . 141
6.2.33 Q(SVTXQ): Server-TX Queue . 141
6.2.34 V(TBN), P(TBN): Total fragment number of Cyclic-data on CM1 and
CM2 . 141
6.2.35 V(TDT), P(TDT), T(TDT): Joining-token-detection-time . 141
6.2.36 V(THT), P(THT), T(THT): Token-holding-time . 142
6.2.37 V(TK): Token holding . 142
6.2.38 V(TKH): Token holding node . 142
6.2.39 V(TN): Node identifier number . 142
6.2.40 V(TrWT), T(TrWT): Trigger-frame-transmission-waiting-time . 142
6.2.41 V(TSZ), P(TSZ): Total cyclic-data size on CM1 and CM2 . 142
6.2.42 V(TW), P(TW ), T(TW)( ): Token-watchdog-time . 142
6.2.43 V(VSEQ): Version of sequence number value List . 142
6.3 Functions used in state tables . 143
7 FAL service protocol machine (FSPM) . 146
7.1 Overview. 146
7.2 Cyclic-data protocol machine . 146
7.2.1 Overview . 146
7.2.2 Cyclic-data primitives between FAL user and FSPM . 146
7.2.3 State table . 147
7.3 Message data protocol machine . 149
7.3.1 Overview . 149
7.3.2 Message-data primitive between FAL user and FSPM . 149
7.3.3 State table . 153
7.4 Load measurement protocol machine . 163
7.4.1 Overview . 163
7.4.2 Load measurement primitives between FAL user and FSPM . 163
7.4.3 State table . 164
7.5 General purpose communication server protocol machine . 168
7.5.1 Overview . 168
7.5.2 GP command server primitives between FAL user and FSPM . 168
7.5.3 State table . 168
7.6 Network management protocol machine . 170
7.6.1 Overview . 170
7.6.2 Network management primitives . 170
7.6.3 State table . 171
8 Application relationship protocol machine (ARPM) . 174
8.1 Overview. 174
8.2 Cyclic-TX/RX control . 175
8.2.1 Overview . 175
8.2.2 Cyclic-TX/RX control primitives between FSPM and ARPM . 175
8.2.3 State table . 176
8.3 Message-TX/RX control . 176
8.3.1 Overview . 176
8.3.2 Message-TX/RX control primitives between FSPM and ARPM . 176
8.3.3 State table . 177
8.4 Command server TX/RX control . 177
8.4.1 Overview . 177
8.4.2 Command server TX/RX primitives between FSPM and ARPM . 178
– 6 – IEC 61158-6-26:2023 © IEC 2023
8.4.3 State table . 178
8.5 AR control . 178
8.5.1 Overview . 178
8.5.2 AR control primitives between FSPM and ARPM . 179
8.5.3 State table . 179
9 DLL mapping protocol machine (DMPM) . 202
9.1 Overview. 202
9.2 Mapping of DMPM service primitives and DLL service primitives . 202
9.3 Mapping DMPM service port to DLSAP . 204
9.4 Mapping of Network address to each node . 204
Bibliography . 206
Figure 1 – Bit identification in an octet . 26
Figure 2 – Bit identification in multiple octets (four-octet case) . 27
Figure 3 – Data sharing with the CM . 28
Figure 4 – Protocol stack for Type 26 fieldbus . 29
Figure 5 – The structure of ASEs for Type 26 FAL . 30
Figure 6 – A token circulation on a logical ring . 32
Figure 7 – Logical ring recovery . 34
Figure 8 – An example in case of start simultaneously with another node . 36
Figure 9 – Start alone case . 37
Figure 10 – Node addition: in-ring start-up state . 38
Figure 11 – Data sharing with the CM . 40
Figure 12 – Configuration of the Common-memory . 41
Figure 13 – Example of train of multiple extended-cyclic-data frames . 42
Figure 14 – APDUs of cyclic-data frames containing fragmented data . 43
Figure 15 – Example of sequential diagram of ACK over UDP channel . 46
Figure 16 – Delivery confirmation checked by TCP protocol . 47
Figure 17 – Train of data frames and a token frame . 49
Figure 18 – Frame structure . 50
Figure 19 – Structure of Trans-msgData . 70
Figure 20 – Structure of B_Blk_Rd_rspData with M_RLT = 0 . 73
Figure 21 – Structure of B_Blk_Rd_rspData in case of M_RLT = 1 . 73
Figure 22 – Structure of B_Blk_Wt_reqDat . 75
Figure 23 – Structure of B_Blk_Wt_rspData in case of M_RLT = 1 . 75
Figure 24 – Structure of W_Blk_Rd_rspData with M_RLT = 0 . 77
Figure 25 – Structure of W_Blk_Rd_rspData in case of M_RLT = 1 . 77
Figure 26 – Structure of W_Blk_Wt_reqDat . 79
Figure 27 – Structure of W_Blk_Wt_rspData in case of M_RLT = 1 . 79
Figure 28 – Structure of Net-para-Rd-rspData with M_RLT = 0 . 81
Figure 29 – Structure of Net-para-Rd-rspData with M_RLT = 1 . 82
Figure 30 – Structure of Net-para-Wrt-reqData. 84
Figure 31 – Structure of Net-para-Wrt-rspData with M_RLT = 1 . 85
Figure 32 – Structure of Stop-cmdData with M_RLT = 1 . 87
IEC 61158-6-26:2023 © IEC 2023 – 7 –
Figure 33 – Structure of Op-cmdData with M_RLT = 1 . 88
Figure 34 – Structure of Profile-readData with M_RLT = 0 . 90
Figure 35 – Structure of Profile-readData with M_RLT = 1 . 92
Figure 36 – Structure of Log-readData with M_RLT = 0 . 94
Figure 37 – Structure of Log-readData with M_RLT = 1 . 98
Figure 38 – Structure of Log-clearData . 99
Figure 39 – Structure of Msg-return-reqData . 101
Figure 40 – Structure of Msg-return-rspData . 102
Figure 41 – Structure of V_msg_reqData . 104
Figure 42 – Structure of V_msg_rspData in case of M_RLT = 0 . 104
Figure 43 – Structure of V_msg_rspData in case of M_RLT = 1 . 105
Figure 44 – Token-holding-time measurement result . 109
Figure 45 – Structure of Sndr-logData . 114
Figure 46 – Structure of Set-remote-node-config-para-ReqData . 116
Figure 47 – Structure of Set-remote-node-config-para-RspData . 117
Figure 48 – Structure of Read-rmt-partici-node-mgt-info-ReqData . 119
Figure 49 – Structure of Read-rmt-partici-node-mgt-info-RspData . 119
Figure 50 – Structure of Rmt-node-mgt-info-paraData . 122
Figure 51 – Structure of Set-info-para-read-data . 124
Figure 52 – Structure of ACKdata . 128
Figure 53 – Structure of Ex-Net-para-Rd-rspData with M_RLT = 0 . 131
Figure 54 – Structure of Ex-Net-para-Rd-rspData with M_RLT = 1 . 132
Figure 55 – Structure of Ex-Net-para-Wrt-reqData . 134
Figure 56 – Structure of Ex-Net-para-Wrt-rspData with M_RLT = 1 . 135
Figure 57 – Relationship between FAL protocol machines . 136
Figure 58 – Overall structure of FSPM . 146
Figure 59 – State transition diagram of Cyclic-data protocol machine. 147
Figure 60 – State transition diagram of Message-data protocol machine . 154
Figure 61 – State transition diagram of Load measurement protocol machine . 164
Figure 62 – State transition diagram of GP-command-server protocol machine . 169
Figure 63 – State transition diagram of Network management protocol machine . 172
Figure 64 – Overall structure of ARPM . 175
Figure 65 – State transition diagram of Cyclic-TX/RX control . 176
Figure 66 – State transition diagram of Message-TX/RX control . 177
Figure 67 – State transition diagram of Command server TX/RX protocol machine . 178
Figure 68 – Overall state transition diagram of AR control protocol machine . 180
Figure 69 – State transition diagram for message-data transmission . 196
Figure 70 – State transition diagram for ACK creation and message-data reception . 199
Figure 71 – Overall structure of DMPM . 202
Figure 72 – DLSAP mapping . 204
Figure 73 – Structure of IP address . 205
Table 1 – Conventions used for state machines . 25
– 8 – IEC 61158-6-26:2023 © IEC 2023
Table 2 – Conventions used in state machine . 25
Table 3 – Available functions to message-data transfer on UDP channel . 44
Table 4 – Data transmission frame and the TCD value . 50
Table 5 – Upper layer operating condition matrix . 67
Table 6 – Transparent-msg-PDU specific values . 70
Table 7 – Token-PDU specific values . 71
Table 8 – Participation-req -PDU specific values . 71
Table 9 – Byte-block-read-req-PDU specific values . 72
Table 10 – Byte-block-read-rsp-PDU specific values . 72
Table 11 – Byte-block-write-req-PDU specific values . 74
Table 12 – Byte-block-write-rsp-PDU specific values . 74
Table 13 – Word-block-read-req-PDU specific values . 76
Table 14 – Word-block-read-rsp-PDU specific values . 76
Table 15 – Word-block-write-req-PDU specific values . 78
Table 16 – Word-block-write-rsp-PDU specific values . 78
Table 17 – Network-parameter-read-req-PDU specific values . 80
Table 18 – Network-parameter-read-rsp-PDU specific values . 80
Table 19 – Values of data elements of Net-para-Rd-rspData . 82
Table 20 – Network-parameter-write-req-PDU specific values . 83
Table 21 – Network-parameter-write-rsp-PDU specific values . 83
Table 22 – Values of the data elements of Net-para-Wrt-reqData . 84
Table 23 – Stop-command-req-PDU specific values . 85
Table 24 – Stop-command-rsp-PDU specific values . 86
Table 25 – Operation-command-req-PDU specific values . 87
Table 26 – Operation-command-rsp-PDU specific values . 88
Table 27 – Profile-read-req-PDU specific values . 89
Table 28 – Profile-read-rsp-PDU specific values . 90
Table 29 – Trigger-PDU specific values . 92
Table 30 – Log-data-read-req-PDU U specific values . 93
Table 31 – Log-data-read-rsp-PDU specific values . 93
Table 32 – Contents of Log-readData . 94
Table 33 – Log-data-clear-req-PDU specific values . 98
Table 34 – Log-data-clear-rsp-PDU specific values . 99
Table 35 – Message-return-req-PDU specific values . 100
Table 36 – Message-return-rsp-PDU specific values . 100
Table 37 – Vendor-
...
SIST EN IEC 61158-6-26:2023 표준은 산업 통신 네트워크의 필드버스 응용 계층 프로토콜 사양을 다루고 있으며, 특히 Type 26 요소에 중점을 두고 있습니다. 이 표준의 주요 범위는 필드버스 응용 계층(FAL)이 사용자가 필드버스 통신 환경에 접근할 수 있는 방법을 제공한다는 것입니다. 이는 응용 프로그램 간의 메시지 통신이 시간적 중요성과 비시간적 중요성을 포함하여 기본적인 요소들을 정의하고 있습니다. 이 표준의 강점은 IEC 61158-5-2에서 정의된 서비스 기본 요소를 기반으로 하여 응용 계층 프로토콜 데이터 단위(PDU)의 형식적 추상 구문을 지정한다는 점입니다. 이는 통신되는 응용 프로그램 엔티티 간의 상호작용을 명확하게 정의하여 시간 제한 내에 특정 작업을 완료해야 하는 필요성을 강조하고 있습니다. 시간에 민감한 통신에서의 이러한 명확한 정의는 장비와 인간 생명에 대한 위험을 줄이는 데 기여합니다. 또한, 필드버스 응용 계층의 외부 가시적 행동을 정의함으로써 다양한 산업 자동화 시스템 내에서의 응용 계층 엔티티 구현에 대한 제약이 없도록 하였으며, 이는 기업들이 기존 산업 통신 프로토콜에서 새로운 프로토콜로 쉽게 전환할 수 있도록 합니다. 이 문서에서는 OSI 기본 참조 모델 및 OSI 응용 계층 구조와의 일치를 통해 필드버스 응용 계층 프로토콜을 정의하고 있습니다. 결론적으로, SIST EN IEC 61158-6-26:2023 표준은 필드버스 응용 계층의 명확한 프로토콜 사양을 제공하며, 이는 산업 자동화 환경에서 효율적이고 안전한 통신을 보장하는 데 필수적입니다. 이는 표준화된 응용 계층이 기업의 통신 환경에서 중요한 역할을 수행할 수 있도록 도와줍니다.
The SIST EN IEC 61158-6-26:2023 standard provides a critical framework for industrial communication networks, specifically focusing on the application layer protocol specification for Type 26 elements. Its scope is comprehensive, designed not only to facilitate communication between application programs in automation environments but also to address both time-critical and non-time-critical messaging needs. One of the standout strengths of this standard is its emphasis on time-critical operations. By defining the necessary time windows for action completion, it mitigates risks associated with equipment and human safety, reinforcing the importance of reliable communications in industrial automation. The specification delineates clear interactions between remote applications, ensuring that the protocol supports the formal abstract syntax for application layer protocol data units, as well as the essential transfer syntax and application context state machines. The standard’s relevance cannot be overstated in today’s increasingly interconnected industrial landscape. It conforms to the OSI Basic Reference Model and the OSI application layer structure, which not only promotes interoperability but ensures that implementations can be adapted and integrated into a variety of existing frameworks. The provision for migration paths from previously existing communication protocols further enhances its applicability, ensuring that organizations can transition smoothly to newer systems without substantial overhead. Moreover, the document outlines the protocol for the Type 2 fieldbus application layer, effectively bridging gaps that may arise in different industrial automation systems. While it outlines the expected behavior and syntax, it wisely refrains from constraining specific implementations or products, allowing for flexibility and adaptability within various industrial contexts. In summary, the SIST EN IEC 61158-6-26:2023 standard stands out due to its thorough approach to specifying application layer communication protocols. Its commitment to ensuring time-sensitive operations, interoperability with existing standards, and provision for future adoption make it an essential document for professionals in the field of industrial communication networks.
SIST EN IEC 61158-6-26:2023は、産業用通信ネットワークにおけるフィールドバス仕様の一部であり、アプリケーション層プロトコルの詳細を提供します。この標準は、産業オートメーション環境におけるアプリケーションプログラム間の基本的な時間重要及び非時間重要なメッセージ通信に関する共通要素を含んでおり、特にタイプ2フィールドバスに関連した内容に焦点を当てています。 この標準の強みは、"時間クリティカル"な通信の重要性を明確に定義している点にあります。定義された時間ウィンドウ内で行動を完了する必要があり、これが不可能な場合、アプリケーションや機器、そして人命に対するリスクが伴うことが強調されています。このような視点から、SIST EN IEC 61158-6-26:2023は、実装者にとって信頼性の高い通信環境を構築するための重要なガイドラインとなります。 また、この文書は、アプリケーションレイヤープロトコルデータユニット（PDU）の正式な抽象構文、エンコーディングルール、アプリケーションの状態遷移マシン、ならびに通信の振る舞いを定義するアプリケーション関係の状態遷移マシンを詳細に記述していることも、標準の重要なポイントです。これにより、異なるアプリケーションエンティティ間の通信が円滑に行えることを保証します。 さらに、SIST EN IEC 61158-6-26:2023は、OSI基本参照モデルやアプリケーション層構造に準拠し、これにより産業用オートメーションシステムにおけるアプリケーション層エンティティの実装に対する制約を設けず、柔軟な適用を可能にしています。既存の産業通信プロトコルとの移行パスも提供されており、これにより新規導入がスムーズに行える点が特に評価されます。 全体として、SIST EN IEC 61158-6-26:2023は、産業用フィールドバスのアプリケーション層の標準化において重要な役割を果たしており、ユーザーに対して安全で確実な通信環境を確保するための価値ある文書です。
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...