SIST EN IEC 61158-6-26:2019
(Main)Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer protocol specification - Type 26 elements (IEC 61158-6-26:2019)
Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer protocol specification - Type 26 elements (IEC 61158-6-26:2019)
IEC 61158-6-26:2019 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. The purpose of this document is to define the protocol provided to
a) define the wire-representation of the service primitives defined in this document, 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).
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-26: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 26-Elemente (IEC 61158-6-26:2019)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-26: Spécification du protocole de la couche application - Eléments de type 26 (IEC 61158-6-26:2019)
L'IEC 61158-6-26:2019 fournit des éléments communs pour les communications de messagerie prioritaires et non prioritaires élémentaires entre les programmes d’application des environnements d’automatisation et le matériel spécifique au bus de terrain de type 26. On utilise le terme "prioritaire" pour traduire la présence d’une fenêtre temporelle, à l’intérieur de laquelle une ou plusieurs actions spécifiées doivent être terminées avec un niveau de certitude défini. Si les actions spécifiées ne sont pas réalisées dans la fenêtre temporelle, les applications demandant les actions risquent de connaître une défaillance, avec les risques que cela comporte pour les équipements, les installations et éventuellement la vie humaine.
La présente norme définit de manière abstraite le comportement, visible par un observateur externe, assuré par les différents Types de la couche Application de bus de terrain, en termes
a) de syntaxe abstraite définissant les unités de données de protocole de la couche Application, transmises entre les entités d'application en communication,
b) de syntaxe de transfert définissant les unités de données de protocole de la couche Application, transmises entre les entités d'application en communication;
c) de diagramme d'états de contexte d'application définissant le comportement de service d'application observable entre les entités d'application en communication; et
d) de diagrammes d'états de relations d'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-26. del: Specifikacija protokola na aplikacijski ravni - Elementi tipa 26 (IEC 61158-6-26:2019)
Ta dokument določa skupne elemente za osnovne časovno kritične in časovno nekritične sporočilne komunikacije med aplikacijami v avtomatizacijskem okolju ter materialu, specifičnem za procesna vodila tipa 26. 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 zunanje vidno vedenje, ki ga zagotavlja aplikacijski nivo procesnih vodil tipa 26 v zvezi s/z: a) abstraktno sintakso, ki opredeljuje podatkovne enote protokola aplikacijskega nivoja, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo, b) prenosno sintakso, ki opredeljuje podatkovne enote protokola aplikacijskega nivoja, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo, c) strojem stanj aplikacijskega konteksta, ki opredeljuje vedenje aplikacijskega opravila, vidnega med aplikacijskimi osebki, ki komunicirajo, in d) stroji stanj aplikacijskega razmerja, ki opredeljujejo komunikacijsko vedenje med aplikacijskimi osebki, ki komunicirajo. Namen tega standarda je opredeliti protokol za: a) določitev žične predstavitve primitivov opravil iz standarda IEC 61158-5-26 in b) določitev zunanje vidnega vedenja, povezanega z njihovim prenosom. Ta dokument določa protokol aplikacijskega nivoja procesnih vodil tipa 26 v skladu z osnovnim referenčnim modelom OSI (glej ISO/IEC 7498-1) in strukturo aplikacijskega nivoja OSI (glej ISO/IEC 9545). Opravila in protokole aplikacijskega nivoja procesnih vodil zagotavljajo aplikacijski osebki (AE) aplikacijskega nivoja procesnih vodil znotraj aplikacijskih procesov. Aplikacijski osebek aplikacijskega nivoja procesnih vodil sestavljata sklop objektno usmerjenih aplikacijskih opravilnih elementov (ASE) in osebek za upravljanje nivojev (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 aplikacijskega nivoja procesnih vodil spada aplikacijski opravilni element za upravljanje, ki zagotavlja skupen sklop opravil za upravljanje primerkov razredov aplikacijskega nivoja 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 uporabnikom aplikacijskega nivoja procesnih vodil omogoči večja prilagodljivost pri standardizaciji takega vedenja objektov. Poleg teh opravil so v tem dokumentu opredeljena tudi nekatera podporna opravila, da se omogoči dostop do aplikacijskega nivoja procesnih vodil za nadzorovanje nekaterih vidikov njegovega delovanja.
General Information
Relations
Overview
EN IEC 61158-6-26:2019 (also published as IEC 61158-6-26:2019) is the application-layer protocol specification for Type 26 fieldbus elements within industrial communication networks. It defines the wire representation of service primitives and the externally visible behavior of the Type 2 fieldbus application layer. The standard supports both time-critical and non-time-critical messaging between application programs in automation systems and is specified in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).
Key Topics and Requirements
- Application layer protocol definition: Detailed FAL (Fieldbus Application Layer) syntax and FAL PDU abstract syntax for Type 26.
- Transfer and encoding rules: ASN.1-style transfer syntax and encoding rules for PDUs (Basic, OctetString, SEQUENCE, bit- and fixed-length encodings).
- PDU types: Token, Transparent-msg, Participation-req, Byte/Word block read/write, Network-parameter read/write, Stop/Operation commands, Trigger, Log-data read/clear, Message-return, Vendor-specific messages, and timing/measurement PDUs.
- Protocol behavior: Externally visible interactions between remote applications including logical ring maintenance, node addition and drop-out procedures, data transmission frames and cyclic-data handling.
- Real-time requirements: Explicit support for operations with defined time-windows where failure to meet timing constraints can risk equipment, plant operation, or human safety.
- Conformance and interoperability: Specifies how to represent service primitives on the wire and the expected externally visible behavior to ensure interoperability of Type 2 fieldbus devices.
Applications and Who Uses This Standard
EN IEC 61158-6-26:2019 is intended for:
- Fieldbus device manufacturers (PLCs, I/O modules, sensors, actuators) implementing Type 26 application-layer protocols.
- System integrators and automation engineers designing real-time industrial networks where deterministic messaging and safety timing windows are required.
- Software developers of protocol stacks and diagnostics tools for industrial communication.
- Standards and compliance teams ensuring devices meet IEC/EN fieldbus specifications for Type 2 fieldbus application layers.
Practical applications include deterministic control loops, safety-critical messaging in process and factory automation, remote node management, configuration, and event/logging services in distributed control systems.
Related Standards
- IEC 61158-5-26 - Application layer service definition (Type 26)
- IEC 61158-1 - Overview and guidance for IEC 61158 series
- IEC 61784-2 - Fieldbus profiles for real-time networks
- OSI references: ISO/IEC 7498-1, ISO/IEC 9545
- ASN.1 & encoding rules: ISO/IEC 8824-1, ISO/IEC 8825-1
- Relevant IETF RFCs for transport/network referencing (UDP/TCP/IP) used in normative references
Keywords: EN IEC 61158-6-26:2019, Type 26, fieldbus, application layer, industrial communication networks, time-critical messaging, Type 2 fieldbus, real-time automation.
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2019
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 6-26. del:
Specifikacija protokola na aplikacijski ravni - Elementi tipa 26 (IEC 61158-6-
26:2019)
Industrial communication networks - Fieldbus specifications - Part 6-26: Application layer
protocol specification - Type 26 elements (IEC 61158-6-26:2019)
Industrielle Kommunikationsnetze - Feldbusse - Teil 6-26: Protokollspezifikation des
Application Layer (Anwendungsschicht) - Typ 26-Elemente (IEC 61158-6-26:2019)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-26:
Spécification du protocole de la couche application - Eléments de type 26 (IEC 61158-6-
26:2019)
Ta slovenski standard je istoveten z: EN IEC 61158-6-26:2019
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
August 2019
ICS 25.040.40; 35.100.70; 35.110
English Version
Industrial communication networks - Fieldbus specifications -
Part 6-26: Application layer protocol specification - Type 26
elements
(IEC 61158-6-26:2019)
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 application - Eléments de type 26 (Anwendungsschicht) - Typ 26-Elemente
(IEC 61158-6-26:2019) (IEC 61158-6-26:2019)
This European Standard was approved by CENELEC on 2019-07-25. 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,
Turkey 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
© 2019 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 61158-6-26:2019 E
European foreword
The text of document 65C/948/FDIS, future edition 1 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) 2020-04-25
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2022-07-25
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.
Endorsement notice
The text of the International Standard IEC 61158-6-26:2019 was approved by CENELEC as a
European Standard without any modification.
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.cenelec.eu.
Publication Year Title EN/HD Year
IEC 61158-1 2019 Industrial communication networks - Fieldbus EN IEC 61158-1 2019
specifications - Part 1: Overview and guidance
for the IEC 61158 and IEC 61784 series
IEC 61158-5-26 2019 Industrial communication networks - Fieldbus EN IEC 61158-5-26 2019
specifications - Part 5-26: Application layer
service definition - Type 26 elements
IEC 61784-2 2019 Industrial communication networks - Profiles - EN IEC 61784-2 2019
Part 2: Additional fieldbus profiles for real-time
networks based on ISO/IEC/IEEE 8802-3
ISO/IEC 7498-1 - Information technology - Open Systems - -
Interconnection - Basic Reference Model: The
Basic Model
ISO/IEC/IEEE - Information technology - Telecommunications - -
8802-3 and information exchange between systems -
Local and metropolitan area networks - Specific
requirements - 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): 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 - -
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 1.0 2019-06
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-7016-5
– 2 – IEC 61158-6-26:2019 © IEC 2019
CONTENTS
FOREWORD . 10
INTRODUCTION . 12
1 Scope . 13
1.1 General . 13
1.2 Specifications . 14
1.3 Conformance . 14
2 Normative references . 14
3 Terms, definitions, symbols, abbreviations and conventions . 15
3.1 Terms and definitions from other ISO/IEC standards . 15
3.1.1 Terms and definitions from ISO/IEC 7498-1 . 15
3.1.2 Terms and definitions from ISO/IEC 8822 . 16
3.1.3 Terms and definitions from ISO/IEC 9545 . 16
3.1.4 Terms and definitions from ISO/IEC 8824-1 . 16
3.1.5 Terms and definitions from ISO/IEC 8825-1 . 17
3.2 Type 26 specific terms and definitions . 17
3.3 Abbreviations and symbols . 21
3.4 Conventions . 23
3.4.1 Conventions used in state machines . 23
3.4.2 Convention for abstract syntax description . 24
3.4.3 Convention for reserved bits and octets . 24
3.4.4 Conventions for bit description in octets . 24
4 FAL syntax description . 25
4.1 General . 25
4.2 Overview of Type 26 fieldbus . 26
4.2.1 Application field and Common-memory . 26
4.2.2 Structure of Type 26 protocol . 27
4.2.3 Structure of Type 26 FAL . 28
4.2.4 Data link layer . 29
4.3 Operating principle . 29
4.3.1 Overview . 29
4.3.2 Logical ring maintenance . 30
4.3.3 Node addition . 33
4.3.4 Node in a logical ring . 36
4.3.5 Node drop-out . 36
4.3.6 Data transmission . 37
4.3.7 Data transmission frames . 46
4.4 FAL PDU abstract syntax . 49
4.4.1 Basic abstract syntax . 49
4.4.2 Transparent-msg- PDU . 51
4.4.3 Token-PDU . 51
4.4.4 Participation-req-PDU . 51
4.4.5 Byte-block-read PDUs . 51
4.4.6 Byte-block-write PDUs . 52
4.4.7 Word-block-read PDUs . 52
4.4.8 Word-block-write PDUs . 52
4.4.9 Network-parameter-read PDUs . 52
4.4.10 Network-parameter-write PDUs. 53
IEC 61158-6-26:2019 © IEC 2019 – 3 –
4.4.11 Stop-command PDUs . 53
4.4.12 Operation-command PDUs . 53
4.4.13 Profile-read PDUs . 53
4.4.14 Trigger-PDU . 54
4.4.15 Log-data-read PDUs . 54
4.4.16 Log-data-clear PDUs . 54
4.4.17 Message-return PDUs . 54
4.4.18 Vendor-specific-msg PDUs . 55
4.4.19 Start-TK-hld-time-mrmt PDUs . 55
4.4.20 Terminate-TK-hld-time-mrmt PDUs . 55
4.4.21 Start-GP_Comm-sndr-log PDUs . 56
4.4.22 Terminate-GP_Comm-sndr-log PDUs . 56
4.4.23 Set-remote-node-config-para PDUs . 56
4.4.24 Read-rmt-partici-node-mgt-info-para PDUs . 56
4.4.25 Read-rmt- node-mgt-info-para PDUs . 57
4.4.26 Read-rmt-node-set-info-para PDUs . 57
4.4.27 Reset-node PDUs . 57
4.4.28 Cyclic-data PDUs . 57
4.5 Data type assignments . 57
5 Transfer syntax . 59
5.1 Encoding rules . 59
5.1.1 Basic encoding . 59
5.1.2 Fixed length Unsigned encoding . 59
5.1.3 Fixed length BitString encoding . 59
5.1.4 OctetString encoding . 59
5.1.5 SEQUENCE encoding . 60
5.2 PDU elements encoding . 60
5.2.1 FALARHeader . 60
5.2.2 Transparent-msg PDU . 63
5.2.3 Token-PDU . 64
5.2.4 Participation-req-PDU . 65
5.2.5 Byte-block-read PDUs . 66
5.2.6 Byte-block-write PDUs . 67
5.2.7 Word-block-read PDUs . 69
5.2.8 Word-block-write PDUs . 71
5.2.9 Network-parameter-read PDUs . 73
5.2.10 Network-parameter-write PDUs. 76
5.2.11 Stop-command PDUs . 79
5.2.12 Operation-command PDUs . 81
5.2.13 Profile-read PDUs . 83
5.2.14 Trigger-PDU . 85
5.2.15 Log-data-read PDUs . 86
5.2.16 Log-data-clear PDUs . 92
5.2.17 Message-return PDUs . 94
5.2.18 Vendor-specific-msg PDUs . 96
5.2.19 Start-TK-hld-time-mrmt PDUs . 98
5.2.20 Terminate-TK-hld-time-mrmt PDUs . 100
5.2.21 Start-GP_Comm-sndr-log PDUs . 103
5.2.22 Terminate-GP_Comm-sndr-log PDUs . 104
– 4 – IEC 61158-6-26:2019 © IEC 2019
5.2.23 Set-remote-node-config-para PDUs . 107
5.2.24 Read-rmt-partici-node-mgt-info-para PDUs . 110
5.2.25 Read-rmt- node-mgt-info-para PDUs . 112
5.2.26 Read-rmt-node-set-info-para PDUs . 115
5.2.27 Reset-node PDUs . 117
5.2.28 Cyclic-data PDUs . 118
6 FAL protocol state machines structure . 120
6.1 Overview. 120
6.2 Common variables, parameters, timers, counters, lists and queues . 121
6.2.1 V(3CWT), P(3CWT), T(3CWT): Three-lap-time-period-of-the-token-
circulation . 121
6.2.2 V(ACK): ACK received . 121
6.2.3 V(ACK_TN): ACK to this node . 121
6.2.4 V(AWT), P(AWT), T(AWT): Waiting-time-period-for-receiving-message-
acknowledge. 122
6.2.5 V(CBN): Current fragment number for fragmented cyclic-data
transmission . 122
6.2.6 V(CTFG): Cyclic-data fragment transfer . 122
6.2.7 V(CTRen), P (CTRen): Cyclic-data receive enable . 122
6.2.8 V(CTRQ): Cyclic-data transfer request . 122
6.2.9 C(MCNT): Cumulative count of message transmission carried over . 122
6.2.10 V(MCV): Message transmission carried over. 122
6.2.11 V(NMTP): No message transmission in previous cycle . 123
6.2.12 V(MFT), P(MFT), T(MFT): Allowable-minimum-frame-Interval-Time . 123
6.2.13 V(MmtCntType): Measurement control type . 123
6.2.14 V(MRVRQ): Message receive request . 123
6.2.15 V(MSRQ): Message transfer request . 123
6.2.16 Q(MSRXQ): Message-RX-Queue . 123
6.2.17 Q(MTXQ):Message-TX-Queue . 124
6.2.18 V(PAT), P(PAT), T(PAT): Participation-request-frame-acceptance-time . 124
6.2.19 V(PnMgtIF): Participation-node-management-information List . 124
6.2.20 V(PWT), T(PWT): Participation-request-frame-transmission-waiting-time . 124
6.2.21 V(RCT): Allowable-refresh-cycle-time . 124
6.2.22 V(RMT), T(RMT): Refresh-cycle-measurement-time. 124
6.2.23 C(RTX): Retransmission count . 125
6.2.24 V(SEQ): Sequence number value List . 125
6.2.25 V(SN): Successor node . 125
6.2.26 V(SrtMmt): Measurement started . 125
6.2.27 Q(SVRXQ): Server-RX Queue . 125
6.2.28 Q(SVTXQ): Server-TX Queue . 125
6.2.29 V(TBN), P(TBN): Total fragment number of Cyclic-data . 125
6.2.30 V(TDT), P(TDT), T(TDT): Joining-token-detection-time . 125
6.2.31 V(THT), P(THT), T(THT): Token-holding-time . 126
6.2.32 V(TK): Token holding . 126
6.2.33 V(TKH): Token holding node . 126
6.2.34 V(TN): Node identifier number . 126
6.2.35 V(TrWT), T(TrWT): Trigger-frame-transmission-waiting-time . 126
6.2.36 V(TSZ), P(TSZ): Total cyclic-data size . 126
6.2.37 V(TW), P(TW ), T(TW)( ): Token-watchdog-time . 126
IEC 61158-6-26:2019 © IEC 2019 – 5 –
6.2.38 V(VSEQ): Version of sequence number value List . 126
6.3 Functions used in state tables . 127
7 FAL service protocol machine (FSPM) . 129
7.1 Overview. 129
7.2 Cyclic-data protocol machine . 130
7.2.1 Overview . 130
7.2.2 Cyclic-data primitives between FAL user and FSPM . 130
7.2.3 State table . 131
7.3 Message data protocol machine . 132
7.3.1 Overview . 132
7.3.2 Message-data primitive between FAL user and FSPM . 132
7.3.3 State table . 136
7.4 Load measurement protocol machine . 144
7.4.1 Overview . 144
7.4.2 Load measurement primitives between FAL user and FSPM . 144
7.4.3 State table . 146
7.5 General purpose communication server protocol machine . 149
7.5.1 Overview . 149
7.5.2 GP command server primitives between FAL user and FSPM . 149
7.5.3 State table . 150
7.6 Network management protocol machine . 152
7.6.1 Overview . 152
7.6.2 Network management primitives . 152
7.6.3 State table . 153
8 Application relationship protocol machine (ARPM) . 155
8.1 Overview. 155
8.2 Cyclic-TX/RX control . 156
8.2.1 Overview . 156
8.2.2 Cyclic-TX/RX control primitives between FSPM and ARPM . 156
8.2.3 State table . 157
8.3 Message-TX/RX control . 157
8.3.1 Overview . 157
8.3.2 Message-TX/RX control primitives between FSPM and ARPM . 158
8.3.3 State table . 158
8.4 Command server TX/RX control . 158
8.4.1 Overview . 158
8.4.2 Command server TX/RX primitives between FSPM and ARPM . 159
8.4.3 State table . 159
8.5 AR control . 160
8.5.1 Overview . 160
8.5.2 AR control primitives between FSPM and ARPM . 160
8.5.3 State table . 160
9 DLL mapping protocol machine (DMPM) . 179
9.1 Overview. 179
9.2 Mapping of DMPM service primitives and DLL service primitives . 179
9.3 Mapping DMPM service port to DL-SAP . 181
9.4 Mapping of Network address to each node . 182
Bibliography . 183
– 6 – IEC 61158-6-26:2019 © IEC 2019
Figure 1 – Bit identification in an octet . 25
Figure 2 – Bit identification in multiple octets (four-octet case) . 25
Figure 3 – Data sharing with the CM . 27
Figure 4 – Protocol stack for Type 26 fieldbus . 28
Figure 5 – The structure of ASEs for Type 26 FAL . 29
Figure 6 – A token circulation on a logical ring . 30
Figure 7 – Logical ring recovery . 32
Figure 8 – An example in case of start simultaneously with another node . 34
Figure 9 – Start alone case . 35
Figure 10 – Node addition: in-ring start-up state . 36
Figure 11 – Data sharing with the CM . 38
Figure 12 – Configuration of the Common-memory . 39
Figure 13 – APDUs of cyclic-data frames containing fragmented data . 40
Figure 14 – Example of sequential diagram of ACK over UDP channel . 43
Figure 15 – Delivery confirmation checked by TCP protocol . 44
Figure 16 – Train of data frames and a token frame . 46
Figure 17 – Frame structure . 47
Figure 18 – Structure of Trans-msgData . 64
Figure 19 – Structure of B_Blk_Rd_rspData with M_RLT = 0 . 67
Figure 20 – Structure of B_Blk_Rd_rspData in case of M_RLT = 1 . 67
Figure 21 – Structure of B_Blk_Wt_reqDat . 69
Figure 22 – Structure of B_Blk_Wt_rspData in case of M_RLT = 1 . 69
Figure 23 – Structure of W_Blk_Rd_rspData with M_RLT = 0 . 71
Figure 24 – Structure of W_Blk_Rd_rspData in case of M_RLT = 1 . 71
Figure 25 – Structure of W_Blk_Wt_reqDat . 73
Figure 26 – Structure of W_Blk_Wt_rspData in case of M_RLT = 1 . 73
Figure 27 – Structure of Net-para-Rd-rspData . 75
Figure 28 – Structure of Net-para-Rd-rspData with M_RLT = 1 . 76
Figure 29 – Structure of Net-para-Wrt-reqData. 78
Figure 30 – Structure of Net-para-Wrt-rspData with M_RLT = 1 . 79
Figure 31 – Structure of Stop-cmdData with M_RLT = 1 . 81
Figure 32 – Structure of Op-cmdData with M_RLT = 1 . 82
Figure 33 – Structure of Profile-readData with M_RLT = 0 . 84
Figure 34 – Structure of Profile-readData with M_RLT = 1 . 85
Figure 35 – Structure of Log-readData with M_RLT = 0 . 88
Figure 36 – Structure of Log-readData with M_RLT = 1 . 92
Figure 37 – Structure of Log-clearData . 93
Figure 38 – Structure of Msg-return-reqData . 95
Figure 39 – Structure of Msg-return-rspData . 95
Figure 40 – Structure of V_msg_reqData . 97
Figure 41 – Structure of V_msg_rspData in case of M_RLT = 0 . 98
Figure 42 – Structure of V_msg_rspData in case of M_RLT = 1 . 98
IEC 61158-6-26:2019 © IEC 2019 – 7 –
Figure 43 – Token-holding-time measurement result . 102
Figure 44 – Structure of Sndr-logData . 106
Figure 45 – Structure of Set-remote-node-config-para-ReqData . 108
Figure 46 – Structure of Set-remote-node-config-para-RspData . 109
Figure 47 – Structure of Read-rmt-partici-node-mgt-info-ReqData . 111
Figure 48 – Structure of Read-rmt-partici-node-mgt-info-RspData . 111
Figure 49 – Structure of Rmt-node-mgt-info-paraData . 114
Figure 50 – Structure of Set-info-para-read-data . 116
Figure 51 – Structure of ACKdata . 119
Figure 52 – Relationship between FAL protocol machines . 121
Figure 53 – Overall structure of FSPM . 130
Figure 54 – State transition diagram of Cyclic-data protocol machine. 131
Figure 55 – State transition diagram of Message-data protocol machine . 136
Figure 56 – State transition diagram of Load measurement protocol machine . 146
Figure 57 – State transition diagram of GP-command-server protocol machine . 150
Figure 58 – State transition diagram of Network management protocol machine . 153
Figure 59 – Overall structure of ARPM . 156
Figure 60 – State transition diagram of Cyclic-TX/RX control . 157
Figure 61 – State transition diagram of Message-TX/RX control . 158
Figure 62 – State transition diagram of Command server TX/RX protocol machine . 159
Figure 63 – Overall state transition diagram of AR control protocol machine . 161
Figure 64 – State transition diagram for message-data transmission . 173
Figure 65 – State transition diagram for ACK creation and message-data reception . 176
Figure 66 – Overall structure of DMPM . 179
Figure 67 – DL-SAP mapping . 181
Figure 68 – Structure of IP address . 182
Table 1 – Conventions used for state machines . 23
Table 2 – Conventions used in state machine . 23
Table 3 – Available functions to message-data transfer on UDP channel . 42
Table 4 – Data transmission frame and the TCD value . 47
Table 5 – Upper layer operating condition matrix . 61
Table 6 – Transparent-msg-PDU specific values . 64
Table 7 – Token-PDU specific values . 65
Table 8 – Participation-req -PDU specific values . 65
Table 9 – Byte-block-read-req-PDU specific values . 66
Table 10 – Byte-block-read-rsp-PDU specific values . 66
Table 11 – Byte-block-write-req-PDU specific values . 68
Table 12 – Byte-block-write-rsp-PDU specific values . 68
Table 13 – Word-block-read-req-PDU specific values . 70
Table 14 – Word-block-read-rsp-PDU specific values . 70
Table 15 – Word-block-write-req-PDU specific values . 72
Table 16 – Word-block-write-rsp-PDU specific values . 72
– 8 – IEC 61158-6-26:2019 © IEC 2019
Table 17 – Network-parameter-read-req-PDU specific values . 74
Table 18 – Network-parameter-read-rsp-PDU specific values . 74
Table 19 – Values of data elements of Net-para-Rd-rspData . 76
Table 20 – Network-parameter-write-req-PDU specific values . 77
Table 21 – Network-parameter-write-rsp-PDU specific values . 77
Table 22 – Values of the data elements of Net-para-Wrt-reqData . 78
Table 23 – Stop-command-req-PDU specific values . 79
Table 24 – Stop-command-rsp-PDU specific values . 80
Table 25 – Operation-command-req-PDU specific values . 81
Table 26 – Operation-command-rsp-PDU specific values . 82
Table 27 – Profile-read-req-PDU specific values . 83
Table 28 – Profile-read-rsp-PDU specific values . 83
Table 29 – Trigger-PDU specific values . 86
Table 30 – Log-data-read-req-PDU U specific values . 87
Table 31 – Log-data-read-rsp-PDU specific values . 87
Table 32 – Contents of Log-readData . 88
Table 33 – Log-data-clear-req-PDU specific values . 92
Table 34 – Log-data-clear-rsp-PDU specific values . 93
Table 35 – Message-return-req-PDU specific values . 94
Table 36 – Message-return-rsp-PDU specific values . 94
Table 37 – Vendor-specific-msg-req-PDU specific values . 96
Table 38 – Vendor-specific-msg-rsp-PDU specific values . 96
Table 39 – Start-TK-hld-time-mrmt-req-PDU specific values . 99
Table 40 – Start-TK-hld-time-mrmt-rsp-PDU specific values . 99
Table 41 – Terminate-TK-hld-time-mrmt-req-PDU specific values . 100
Table 42 – Terminate-TK-hld-time-mrmt-rsp-PDU specific values . 101
Table 43 – Value of the data element of TK-hld-timeData . 102
Table 44 – Start-GP_Comm-sndr-log-req-PDU specific values . 103
Table 45 – Start-GP_Comm-sndr-log-rsp-PDU specific values . 104
Table 46 – Terminate-GP_Comm-sndr-log-req-PDU specific values . 104
Table 47 – Terminate-GP_Comm-sndr-log-req-PDU specific values . 105
Table 48 – Value of the data element of Sndr-logData . 106
Table 49 – Set-remote-node-config-para-req-PDU specific values . 107
Table 50 – Set-remote-node-config-para-rsp-PDU specific values . 107
Table 51 – Value of the data element of Set-remote-node-config-para-ReqData . 108
Table 52 – Bit definition of Update flag . 109
Table 53 – Value of the data element of Set-remote-node-config-para-RspData .
...
Frequently Asked Questions
SIST EN IEC 61158-6-26:2019 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:2019)". This standard covers: IEC 61158-6-26:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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).
IEC 61158-6-26:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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).
SIST EN IEC 61158-6-26:2019 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:2019 has the following relationships with other standards: It is inter standard links to SIST EN IEC 61158-6-26:2023. 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:2019 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.
기사 제목: SIST EN IEC 61158-6-26:2019 - 산업 통신 네트워크 - 필드버스 사양 - 파트 6-26: 응용 계층 프로토콜 사양 - 유형 26 요소들 (IEC 61158-6-26:2019) 기사 내용: 이 문서는 자동화 환경에서 응용 프로그램 간의 기본 시간 비프리엄 및 비 시간 비프리 엄 통신에 대한 공통 요소를 제공하며, 유형 26 필드버스에 대한 자료를 포함합니다. "시간 비프리엄"이란, 특정 동작을 수행하기 위해 일정 시간 안에 하나 이상의 지정된 동작이 완료되어야 함을 나타냅니다. 시간 창 안에서 지정된 동작이 완료되지 않으면, 요청한 동작에 실패할 수 있으며, 장비, 공장 및 인명에 위험이 따릅니다. 이 국제표준은 유형 26 필드버스 응용 계층의 외부적으로 나타나는 동작을 추상적으로 정의합니다. 이는 다음과 같은 사항을 포함합니다: a) 응용 계층 프로토콜 데이터 단위를 전달하는 통사 문법의 정의; b) 응용 계층 프로토콜 데이터 단위를 전달하는 전송 문법의 정의; c) 응용 서비스 동작을 정의하는 응용 컨텍스트 상태 머신; 및 d) 통신 동작을 정의하는 응용 관계 상태 머신. 이 문서의 목적은 다음과 같은 프로토콜을 정의하는 것입니다: a) IEC 61158-5-26에서 정의된 서비스 원시의 전선 표현을 정의하고, b) 전송과 연관된 외부적으로 나타나는 동작을 정의합니다. 이 문서는 유형 26 필드버스 응용 계층의 프로토콜을 OSI 기본 참조 모델 (ISO/IEC 7498-1 참조) 및 OSI 응용 계층 구조 (ISO/IEC 9545 참조)에 따라 명시합니다. FAL 서비스 및 프로토콜은 응용 프로세스 내에 포함된 FAL 응용 엔터티(AE)에 의해 제공됩니다. FAL AE는 일련의 객체 지향 응용 서비스 요소(ASE)와 AE를 관리하는 계층 관리 엔티티(LME)로 구성됩니다. ASE는 관련 응용 프로세스 객체(APO) 클래스에서 작동하는 통신 서비스를 제공합니다. FAL ASE 중 하나는 FAL 클래스의 인스턴스 관리를 위한 공통 서비스를 제공하는 관리 ASE입니다. 이 서비스는 요청 및 응답이 어떻게 발행되고 전달되는지, 응용 프로그램이 이들과 어떻게 처리해야 하는지를 응용 프로그램의 관점에서 지정하지만, 응용 프로그램의 동작 측면은 지정되지 않습니다. 즉, 응용 프로그램의 동작 측면은 지정되지 않으며, 요청 및 응답이 어떻게 발송 및 수신되는지만 정의됩니다. 이는 FAL 사용자가 객체 동작을 표준화하는 데 더 큰 유연성을 제공합니다. 이 문서에서는 FAL의 작동의 특정 측면을 제어하기 위해 지원 서비스도 정의됩니다.
The article discusses the SIST EN IEC 61158-6-26:2019 standard, which specifies the application layer protocol for Type 26 fieldbus. The protocol provides a way for communication between application programs in an automation environment. It distinguishes between time-critical and non-time-critical messaging, with time-critical actions needing to be completed within a specified timeframe. The document defines the behavior of the fieldbus application layer, including the syntax of data units, the application service behavior, and the communication behavior between application entities. The protocol is in accordance with the OSI Basic Reference Model and the OSI Application Layer Structure. The article also mentions the FAL services and protocols provided by FAL application-entities, which include a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME). The ASEs provide communication services for application process objects, and a management ASE is also included to manage the instances of FAL classes. The article notes that while the services specify how requests and responses are issued and delivered, they do not specify the behavior of the applications themselves, allowing for greater flexibility in standardizing object behavior. Additionally, the document defines supporting services that control certain aspects of the FAL's operation.
記事のタイトル：SIST EN IEC 61158-6-26:2019 - インダストリアルコミュニケーションネットワーク - フィールドバス仕様 - 第6-26部：アプリケーションレイヤープロトコル仕様 - タイプ26の要素 (IEC 61158-6-26:2019) 記事の内容：この文書は、自動化環境でのアプリケーションプログラム間の基本的な時間制約と非時間制約のメッセージング通信に共通の要素を提供し、タイプ26のフィールドバスに関連するマテリアルを提供します。 "時間制約"という用語は、1つ以上の指定されたアクションが一定の確実性で完了する必要がある時間ウィンドウが存在することを表します。時間ウィンドウ内で指定されたアクションが完了しない場合、アクションを要求するアプリケーションの失敗があり、設備、プラント、および可能性としての人命に危険が伴います。この国際標準は、フィールドバスのアプリケーションレイヤーのタイプ26によって提供される外部に表示される振る舞いを抽象的に定義します。これには以下が含まれます：a) コミュニケーションするアプリケーションエンティティ間で伝達されるアプリケーションレイヤープロトコルデータユニットを定義する抽象構文、b) コミュニケーションするアプリケーションエンティティ間で伝達されるアプリケーションレイヤープロトコルデータユニットを定義する転送構文、c) コミュニケーションするアプリケーションエンティティ間で表示されるアプリケーションコンテキストステートマシン、d) コミュニケーションするアプリケーションエンティティ間で表示されるアプリケーションリレーションシップステートマシン。この文書の目的は、a) IEC 61158-5-26で定義されたサービスプリミティブのワイヤ表現を定義し、b) その転送に関連する外部に表示される振る舞いを定義するためのプロトコルを定義することです。この文書では、OSI基本参照モデル（ISO/IEC 7498-1を参照）とOSIアプリケーションレイヤー構造（ISO/IEC 9545を参照）に準拠したタイプ26フィールドバスのアプリケーションレイヤープロトコルが指定されています。FALサービスとプロトコルはアプリケーションプロセス内のFALアプリケーションエンティティ(AE)によって提供されます。FAL AEは、一連のオブジェクト指向のアプリケーションサービスエレメント(ASE)と、AEを管理するレイヤーマネジメントエンティティ(LME)から構成されます。ASEは、関連するアプリケーションプロセスオブジェクト(APO)クラスで動作する通信サービスを提供します。FAL ASEの1つは、FALクラスのインスタンスの管理を行うマネジメントASEです。これらのサービスは、アプリケーションの視点から要求と応答がどのように発行され、配信されるかを指定しますが、要求と応答の取り扱いについては指定しません。つまり、アプリケーションの振る舞いは指定されず、送受信できる要求と応答の定義のみが指定されます。これにより、FALユーザーはオブジェクトの振る舞いの標準化においてより柔軟性を持つことができます。また、この文書では、FALの動作の一部を制御するためのサポートサービスも定義されています。
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...