🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 61158-6-26:2019

BS EN IEC 61158-6-26:2019

$215.11

Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 26 elements

Published By Publication Date Number of Pages
BSI 2019 190
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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 26 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 behavior provided by the Type 26 of the fieldbus Application Layer in terms of:

  1. the abstract syntax defining the application layer protocol data units conveyed between communicating application entities;

  2. the transfer syntax defining the application layer protocol data units conveyed between communicating application entities;

  3. the application context state machine defining the application service behavior visible between communicating application entities; and

  4. 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:

  1. define the wire-representation of the service primitives defined in IEC 61158-5-26, and

  2. define the externally visible behavior associated with their transfer.

This document specifies the protocol of the Type 26 fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI Application Layer Structure (see ISO/IEC 9545).

FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.

Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
7 CONTENTS
15 FOREWORD
17 INTRODUCTION
18 1 Scope
1.1 General
19 1.2 Specifications
1.3 Conformance
2 Normative references
20 3 Terms, definitions, symbols, abbreviations and conventions
3.1 Terms and definitions from other ISO/IEC standards
3.1.1 Terms and definitions from ISO/IEC 74981
21 3.1.2 Terms and definitions from ISO/IEC 8822
3.1.3 Terms and definitions from ISO/IEC 9545
3.1.4 Terms and definitions from ISO/IEC 88241
22 3.1.5 Terms and definitions from ISO/IEC 88251
3.2 Type 26 specific terms and definitions
26 3.3 Abbreviations and symbols
28 3.4 Conventions
3.4.1 Conventions used in state machines
Tables
Table 1 – Conventions used for state machines
Table 2 – Conventions used in state machine
29 3.4.2 Convention for abstract syntax description
3.4.3 Convention for reserved bits and octets
3.4.4 Conventions for bit description in octets
30 4 FAL syntax description
4.1 General
Figures
Figure 1 – Bit identification in an octet
Figure 2 – Bit identification in multiple octets (four-octet case)
31 4.2 Overview of Type 26 fieldbus
4.2.1 Application field and Common-memory
32 4.2.2 Structure of Type 26 protocol
Figure 3 – Data sharing with the CM
33 4.2.3 Structure of Type 26 FAL
Figure 4 – Protocol stack for Type 26 fieldbus
34 4.2.4 Data link layer
4.3 Operating principle
4.3.1 Overview
Figure 5 – The structure of ASEs for Type 26 FAL
35 4.3.2 Logical ring maintenance
Figure 6 – A token circulation on a logical ring
37 Figure 7 – Logical ring recovery
38 4.3.3 Node addition
39 Figure 8 – An example in case of start simultaneously with another node
40 Figure 9 – Start alone case
41 4.3.4 Node in a logical ring
4.3.5 Node drop-out
Figure 10 – Node addition: in-ring start-up state
42 4.3.6 Data transmission
43 Figure 11 – Data sharing with the CM
44 Figure 12 – Configuration of the Common-memory
45 Figure 13 – APDUs of cyclic-data frames containing fragmented data
47 Table 3 – Available functions to message-data transfer on UDP channel
48 Figure 14 – Example of sequential diagram of ACK over UDP channel
49 Figure 15 – Delivery confirmation checked by TCP protocol
51 4.3.7 Data transmission frames
Figure 16 – Train of data frames and a token frame
52 Figure 17 – Frame structure
Table 4 – Data transmission frame and the TCD value
54 4.4 FAL PDU abstract syntax
4.4.1 Basic abstract syntax
56 4.4.2 Transparent-msg- PDU
4.4.3 Token-PDU
4.4.4 Participation-req-PDU
4.4.5 Byte-block-read PDUs
57 4.4.6 Byte-block-write PDUs
4.4.7 Word-block-read PDUs
4.4.8 Word-block-write PDUs
4.4.9 Network-parameter-read PDUs
58 4.4.10 Network-parameter-write PDUs
4.4.11 Stop-command PDUs
4.4.12 Operation-command PDUs
4.4.13 Profile-read PDUs
59 4.4.14 Trigger-PDU
4.4.15 Log-data-read PDUs
4.4.16 Log-data-clear PDUs
4.4.17 Message-return PDUs
60 4.4.18 Vendor-specific-msg PDUs
4.4.19 Start-TK-hld-time-mrmt PDUs
4.4.20 Terminate-TK-hld-time-mrmt PDUs
61 4.4.21 Start-GP_Comm-sndr-log PDUs
4.4.22 Terminate-GP_Comm-sndr-log PDUs
4.4.23 Set-remote-node-config-para PDUs
4.4.24 Read-rmt-partici-node-mgt-info-para PDUs
62 4.4.25 Read-rmt- node-mgt-info-para PDUs
4.4.26 Read-rmt-node-set-info-para PDUs
4.4.27 Reset-node PDUs
4.4.28 Cyclic-data PDUs
4.5 Data type assignments
64 5 Transfer syntax
5.1 Encoding rules
5.1.1 Basic encoding
5.1.2 Fixed length Unsigned encoding
5.1.3 Fixed length BitString encoding
5.1.4 OctetString encoding
65 5.1.5 SEQUENCE encoding
5.2 PDU elements encoding
5.2.1 FALARHeader
66 Table 5 – Upper layer operating condition matrix
68 5.2.2 Transparent-msg PDU
69 5.2.3 Token-PDU
Figure 18 – Structure of Trans-msgData
Table 6 – Transparent-msg-PDU specific values
70 5.2.4 Participation-req-PDU
Table 7 – Token-PDU specific values
Table 8 – Participation-req -PDU specific values
71 5.2.5 Byte-block-read PDUs
Table 9 – Byte-block-read-req-PDU specific values
Table 10 – Byte-block-read-rsp-PDU specific values
72 5.2.6 Byte-block-write PDUs
Figure 19 – Structure of B_Blk_Rd_rspData with M_RLT = 0
Figure 20 – Structure of B_Blk_Rd_rspData in case of M_RLT = 1
73 Table 11 – Byte-block-write-req-PDU specific values
Table 12 – Byte-block-write-rsp-PDU specific values
74 5.2.7 Word-block-read PDUs
Figure 21 – Structure of B_Blk_Wt_reqDat
Figure 22 – Structure of B_Blk_Wt_rspData in case of M_RLT = 1
75 Table 13 – Word-block-read-req-PDU specific values
Table 14 – Word-block-read-rsp-PDU specific values
76 5.2.8 Word-block-write PDUs
Figure 23 – Structure of W_Blk_Rd_rspData with M_RLT = 0
Figure 24 – Structure of W_Blk_Rd_rspData in case of M_RLT = 1
77 Table 15 – Word-block-write-req-PDU specific values
Table 16 – Word-block-write-rsp-PDU specific values
78 5.2.9 Network-parameter-read PDUs
Figure 25 – Structure of W_Blk_Wt_reqDat
Figure 26 – Structure of W_Blk_Wt_rspData in case of M_RLT = 1
79 Table 17 – Network-parameter-read-req-PDU specific values
Table 18 – Network-parameter-read-rsp-PDU specific values
80 Figure 27 – Structure of Net-para-Rd-rspData
81 5.2.10 Network-parameter-write PDUs
Figure 28 – Structure of Net-para-Rd-rspData with M_RLT = 1
Table 19 – Values of data elements of Net-para-Rd-rspData
82 Table 20 – Network-parameter-write-req-PDU specific values
Table 21 – Network-parameter-write-rsp-PDU specific values
83 Figure 29 – Structure of Net-para-Wrt-reqData
Table 22 – Values of the data elements of Net-para-Wrt-reqData
84 5.2.11 Stop-command PDUs
Figure 30 – Structure of Net-para-Wrt-rspData with M_RLT = 1
Table 23 – Stop-command-req-PDU specific values
85 Table 24 – Stop-command-rsp-PDU specific values
86 5.2.12 Operation-command PDUs
Figure 31 – Structure of Stop-cmdData with M_RLT = 1
Table 25 – Operation-command-req-PDU specific values
87 Figure 32 – Structure of Op-cmdData with M_RLT = 1
Table 26 – Operation-command-rsp-PDU specific values
88 5.2.13 Profile-read PDUs
Table 27 – Profile-read-req-PDU specific values
Table 28 – Profile-read-rsp-PDU specific values
89 Figure 33 – Structure of Profile-readData with M_RLT = 0
90 5.2.14 Trigger-PDU
Figure 34 – Structure of Profile-readData with M_RLT = 1
91 5.2.15 Log-data-read PDUs
Table 29 – Trigger-PDU specific values
92 Table 30 – Log-data-read-req-PDU U specific values
Table 31 – Log-data-read-rsp-PDU specific values
93 Figure 35 – Structure of Log-readData with M_RLT = 0
Table 32 – Contents of Log-readData
97 5.2.16 Log-data-clear PDUs
Figure 36 – Structure of Log-readData with M_RLT = 1
Table 33 – Log-data-clear-req-PDU specific values
98 Figure 37 – Structure of Log-clearData
Table 34 – Log-data-clear-rsp-PDU specific values
99 5.2.17 Message-return PDUs
Table 35 – Message-return-req-PDU specific values
Table 36 – Message-return-rsp-PDU specific values
100 Figure 38 – Structure of Msg-return-reqData
Figure 39 – Structure of Msg-return-rspData
101 5.2.18 Vendor-specific-msg PDUs
Table 37 – Vendor-specific-msg-req-PDU specific values
Table 38 – Vendor-specific-msg-rsp-PDU specific values
102 Figure 40 – Structure of V_msg_reqData
103 5.2.19 Start-TK-hld-time-mrmt PDUs
Figure 41 – Structure of V_msg_rspData in case of M_RLT = 0
Figure 42 – Structure of V_msg_rspData in case of M_RLT = 1
104 Table 39 – Start-TK-hld-time-mrmt-req-PDU specific values
Table 40 – Start-TK-hld-time-mrmt-rsp-PDU specific values
105 5.2.20 Terminate-TK-hld-time-mrmt PDUs
Table 41 – Terminate-TK-hld-time-mrmt-req-PDU specific values
106 Table 42 – Terminate-TK-hld-time-mrmt-rsp-PDU specific values
107 Figure 43 – Token-holding-time measurement result
Table 43 – Value of the data element of TK-hld-timeData
108 5.2.21 Start-GP_Comm-sndr-log PDUs
Table 44 – Start-GP_Comm-sndr-log-req-PDU specific values
109 5.2.22 Terminate-GP_Comm-sndr-log PDUs
Table 45 – Start-GP_Comm-sndr-log-rsp-PDU specific values
Table 46 – Terminate-GP_Comm-sndr-log-req-PDU specific values
110 Table 47 – Terminate-GP_Comm-sndr-log-req-PDU specific values
111 Figure 44 – Structure of Sndr-logData
Table 48 – Value of the data element of Sndr-logData
112 5.2.23 Set-remote-node-config-para PDUs
Table 49 – Set-remote-node-config-para-req-PDU specific values
Table 50 – Set-remote-node-config-para-rsp-PDU specific values
113 Figure 45 – Structure of Set-remote-node-config-para-ReqData
Table 51 – Value of the data element of Set-remote-node-config-para-ReqData
114 Figure 46 – Structure of Set-remote-node-config-para-RspData
Table 52 – Bit definition of Update flag
Table 53 – Value of the data element of Set-remote-node-config-para-RspData
115 5.2.24 Read-rmt-partici-node-mgt-info-para PDUs
Table 54 – Read-rmt-partici-node-mgt-info-para-req-PDU specific values
Table 55 – Read-rmt-partici-node-mgt-info-para-rsp-PDU specific values
116 Figure 47 – Structure of Read-rmt-partici-node-mgt-info-ReqData
Figure 48 – Structure of Read-rmt-partici-node-mgt-info-RspData
117 5.2.25 Read-rmt- node-mgt-info-para PDUs
Table 56 – Value of the data element of Read-rmt-partici-node-mgt-info-RspData
Table 57 – Read-rmt- node-mgt-info-para-req-PDU specific values
118 Table 58 – Read-rmt- node-mgt-info-para-rsp-PDU specific values
119 Figure 49 – Structure of Rmt-node-mgt-info-paraData
Table 59 – Value of the data element of Rmt-node-mgt-info-paraData
120 5.2.26 Read-rmt-node-set-info-para PDUs
Table 60 – Bit definition of Node status
Table 61 – Read-rmt-node-set-info-para-req-PDU specific values
121 Figure 50 – Structure of Set-info-para-read-data
Table 62 – Read-rmt-node-set-info-para-rsp-PDU specific values
122 5.2.27 Reset-node PDUs
Table 63 – Value of the data element of Set-info-para-read-data
Table 64 – Rest-node-req-PDU specific values
123 5.2.28 Cyclic-data PDUs
Table 65 – Rest-node-rsp-PDU specific values
Table 66 – Cyclic-data-PDU specific values
124 Figure 51 – Structure of ACKdata
125 6 FAL protocol state machines structure
6.1 Overview
Table 67 – Value of the element of ACKdata
Table 68 – Value of R_STSx field
126 6.2 Common variables, parameters, timers, counters, lists and queues
6.2.1 V(3CWT), P(3CWT), T(3CWT): Three-lap-time-period-of-the-token-circulation
6.2.2 V(ACK): ACK received
6.2.3 V(ACK_TN): ACK to this node
Figure 52 – Relationship between FAL protocol machines
127 6.2.4 V(AWT), P(AWT), T(AWT): Waiting-time-period-for-receiving-message-acknowledge
6.2.5 V(CBN): Current fragment number for fragmented cyclic-data transmission
6.2.6 V(CTFG): Cyclic-data fragment transfer
6.2.7 V(CTRen), P (CTRen): Cyclic-data receive enable
6.2.8 V(CTRQ): Cyclic-data transfer request
6.2.9 C(MCNT): Cumulative count of message transmission carried over
6.2.10 V(MCV): Message transmission carried over
Table 69 – Value of R_STSx field
128 6.2.11 V(NMTP): No message transmission in previous cycle
6.2.12 V(MFT), P(MFT), T(MFT): Allowable-minimum-frame-Interval-Time
6.2.13 V(MmtCntType): Measurement control type
6.2.14 V(MRVRQ): Message receive request
6.2.15 V(MSRQ): Message transfer request
6.2.16 Q(MSRXQ): Message-RX-Queue
129 6.2.17 Q(MTXQ):Message-TX-Queue
6.2.18 V(PAT), P(PAT), T(PAT): Participation-request-frame-acceptance-time
6.2.19 V(PnMgtIF): Participation-node-management-information List
6.2.20 V(PWT), T(PWT): Participation-request-frame-transmission-waiting-time
6.2.21 V(RCT): Allowable-refresh-cycle-time
6.2.22 V(RMT), T(RMT): Refresh-cycle-measurement-time
130 6.2.23 C(RTX): Retransmission count
6.2.24 V(SEQ): Sequence number value List
6.2.25 V(SN): Successor node
6.2.26 V(SrtMmt): Measurement started
6.2.27 Q(SVRXQ): Server-RX Queue
6.2.28 Q(SVTXQ): Server-TX Queue
6.2.29 V(TBN), P(TBN): Total fragment number of Cyclic-data
6.2.30 V(TDT), P(TDT), T(TDT): Joining-token-detection-time
131 6.2.31 V(THT), P(THT), T(THT): Token-holding-time
6.2.32 V(TK): Token holding
6.2.33 V(TKH): Token holding node
6.2.34 V(TN): Node identifier number
6.2.35 V(TrWT), T(TrWT): Trigger-frame-transmission-waiting-time
6.2.36 V(TSZ), P(TSZ): Total cyclic-data size
6.2.37 V(TW), P(TW ), T(TW)( ): Token-watchdog-time
6.2.38 V(VSEQ): Version of sequence number value List
132 6.3 Functions used in state tables
Table 70 – Functions used in state tables
134 7 FAL service protocol machine (FSPM)
7.1 Overview
135 7.2 Cyclic-data protocol machine
7.2.1 Overview
7.2.2 Cyclic-data primitives between FAL user and FSPM
Figure 53 – Overall structure of FSPM
Table 71 – Cyclic-data primitives between FAL user and FSPM
136 7.2.3 State table
Figure 54 – State transition diagram of Cyclic-data protocol machine
Table 72 – State table of Cyclic-data protocol machine
137 7.3 Message data protocol machine
7.3.1 Overview
7.3.2 Message-data primitive between FAL user and FSPM
Table 73 – Message-data primitives between FAL user and FSPM
141 7.3.3 State table
Figure 55 – State transition diagram of Message-data protocol machine
Table 74 – State table of Message-data protocol machine
149 7.4 Load measurement protocol machine
7.4.1 Overview
7.4.2 Load measurement primitives between FAL user and FSPM
150 Table 75 – Load measurement primitives between FAL user and FSPM
151 7.4.3 State table
Figure 56 – State transition diagram of Load measurement protocol machine
Table 76 – State table of Load measurement protocol machine
154 7.5 General purpose communication server protocol machine
7.5.1 Overview
7.5.2 GP command server primitives between FAL user and FSPM
155 7.5.3 State table
Figure 57 – State transition diagram of GP-command-server protocol machine
Table 77 – GP command server primitives between FAL user and FSPM
156 Table 78 – State table of General purpose command server protocol machine
157 7.6 Network management protocol machine
7.6.1 Overview
7.6.2 Network management primitives
Table 79 – Primitives used in network management protocol machine
158 7.6.3 State table
Figure 58 – State transition diagram of Network management protocol machine
159 Table 80 – State table of Network management protocol machine
160 8 Application relationship protocol machine (ARPM)
8.1 Overview
161 8.2 Cyclic-TX/RX control
8.2.1 Overview
8.2.2 Cyclic-TX/RX control primitives between FSPM and ARPM
Figure 59 – Overall structure of ARPM
162 8.2.3 State table
8.3 Message-TX/RX control
8.3.1 Overview
Figure 60 – State transition diagram of Cyclic-TX/RX control
Table 81 – Cyclic-TX/RX control primitives between FSPM and ARPM
Table 82 – State table of Cyclic-TX/RX control
163 8.3.2 Message-TX/RX control primitives between FSPM and ARPM
8.3.3 State table
8.4 Command server TX/RX control
8.4.1 Overview
Figure 61 – State transition diagram of Message-TX/RX control
Table 83 – Message-TX/RX control primitives between FSPM and ARPM
Table 84 – State table of Message-TX/RX control
164 8.4.2 Command server TX/RX primitives between FSPM and ARPM
8.4.3 State table
Figure 62 – State transition diagram of Command server TX/RX protocol machine
Table 85 – Command server TX/RX primitives between FSPM and ARPM
Table 86 – State table of Command server TX/RX protocol machine
165 8.5 AR control
8.5.1 Overview
8.5.2 AR control primitives between FSPM and ARPM
8.5.3 State table
Table 87 – AR control primitives between FSPM and ARPM
166 Figure 63 – Overall state transition diagram of AR control protocol machine
167 Table 88 – Overall AR control state table
178 Figure 64 – State transition diagram for message-data transmission
179 Table 89 – State table for message-data transmission
181 Figure 65 – State transition diagram for ACK creation and message-data reception
182 Table 90 – State table for ACK creation and message-data reception
184 9 DLL mapping protocol machine (DMPM)
9.1 Overview
9.2 Mapping of DMPM service primitives and DLL service primitives
Figure 66 – Overall structure of DMPM
185 Table 91 – Mapping of DMPM primitives and DLL service primitives
Table 92 – Supposed Transport service primitives
186 9.3 Mapping DMPM service port to DL-SAP
Figure 67 – DL-SAP mapping
Table 93 – Mapping of output and input ports to DL-SAP
187 9.4 Mapping of Network address to each node
Figure 68 – Structure of IP address
188 Bibliography

Related products

BS EN IEC 61158-6-26:2019
$215.11