BS EN IEC 61158-6-23:2019
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 23 elements
Published By | Publication Date | Number of Pages |
BSI | 2019 | 232 |
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 23 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 different Types of the fieldbus Application Layer in terms of:
-
the abstract syntax defining the application layer protocol data units conveyed between communicating application entities,
-
the transfer syntax defining the application layer protocol data units conveyed between communicating application entities,
-
the application context state machine defining the application service behavior visible between communicating application entities; and
-
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:
-
define the wire-representation of the service primitives defined in IEC 61158-5-23, and
-
define the externally visible behavior associated with their transfer.
This document specifies the protocol of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
7 | CONTENTS |
14 | FOREWORD |
16 | INTRODUCTION |
18 | 1 Scope 1.1 General |
19 | 1.2 Specifications 1.3 Conformance 2 Normative references |
20 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Referenced terms and definitions 3.1.1 ISO/IEC 74981 terms 3.1.2 ISO/IEC 8822 terms 3.1.3 ISO/IEC 9545 terms 3.1.4 ISO/IEC 88241 terms |
21 | 3.1.5 IEC 611581 terms 3.2 Additional Type 23 terms and definitions |
23 | 3.3 Symbols and abbreviated terms |
24 | 3.4 Conventions 3.4.1 General concept 3.4.2 Convention for the encoding of reserved bits and octets 3.4.3 Conventions for abstract syntax description |
25 | 3.4.4 Conventions for bit description in octets 3.4.5 Conventions for state machine descriptions Figures Figure 1 – Bit description in octets Tables Table 1 – State machine description elements Table 2 – Description of state machine elements |
26 | Table 3 – Conventions used in state machines 4 FAL syntax description 4.1 FALPDU type C abstract syntax 4.1.1 Basic abstract syntax |
27 | 4.1.2 Connect-PDU 4.1.3 ConnectAck-PDU 4.1.4 Scan-PDU |
28 | 4.1.5 Collect-PDU 4.1.6 Select-PDU 4.1.7 Launch-PDU 4.1.8 Token-PDU |
29 | 4.1.9 MyStatus-PDU 4.1.10 Transient1-PDU |
30 | 4.1.11 Dummy-PDU 4.1.12 Transient2-PDU 4.1.13 NTNTest-PDU |
31 | 4.1.14 CyclicDataW-PDU 4.1.15 CyclicDataB-PDU 4.1.16 CyclicDataOut1-PDU |
32 | 4.1.17 CyclicDataOut2-PDU 4.1.18 CyclicDataIn1-PDU 4.1.19 CyclicDataIn2-PDU |
33 | 4.2 FALPDU type F abstract syntax 4.2.1 Basic abstract syntax |
34 | 4.2.2 Persuasion-PDU |
35 | 4.2.3 TestData-PDU 4.2.4 TestDataAck-PDU |
36 | 4.2.5 Setup-PDU 4.2.6 SetupAck-PDU |
37 | 4.2.7 F-Token-PDU 4.2.8 F-MyStatus-PDU 4.2.9 Measure-PDU |
38 | 4.2.10 F-Offset-PDU 4.2.11 F-Update-PDU 4.2.12 F-CyclicData-PDU 4.2.13 Transient1-PDU |
41 | 4.2.14 TransientAck-PDU |
42 | 4.2.15 Transient2-PDU 4.2.16 ParamCheck-PDU |
43 | 4.2.17 Parameter-PDU |
44 | 4.2.18 Timer-PDU 4.3 Data type assignments for type C |
45 | 4.4 Data type assignments for type F |
46 | 5 FAL transfer syntax 5.1 Encoding rules 5.1.1 Unsigned encoding 5.1.2 Octet string encoding |
47 | Table 4 – afFType 5.1.3 SEQUENCE encoding 5.1.4 LOctetString encoding 5.2 FALPDU type C elements encoding 5.2.1 FALARHeader |
48 | Table 5 – priority |
49 | Table 6 – portChoice 5.2.2 Connect-PDU |
50 | Table 7 – portCheckResult Table 8 – dstPortInfo Table 9 – scanState 5.2.3 ConnectAck-PDU 5.2.4 Scan-PDU |
51 | Table 10 – nodeType 5.2.5 Collect-PDU |
52 | Table 11 – loopState Table 12 – Cyclic status Table 13 – Parameter setting mode |
53 | 5.2.6 Select-PDU |
54 | 5.2.7 Launch-PDU 5.2.8 Token-PDU 5.2.9 MyStatus-PDU |
55 | Table 14 – opState Table 15 – errorState |
56 | 5.2.10 Transient1-PDU |
57 | Table 16 – Data type Table 17 – CPW |
58 | Table 18 – CPWC Table 19 – CPWCR Table 20 – cmParam |
59 | Table 21 – Details of param area Table 22 – Details of application parameters |
60 | Table 23 – Details of LB/LW CM area and LB/LW CM additional area Table 24 – Details of LX/LY CM 1 area and LX/LY CM 2 area 5.2.11 Dummy-PDU |
61 | 5.2.12 Transient2-PDU |
62 | Table 25 – Destination module flag |
63 | Table 26 – Command types |
64 | Figure 2 – Structure for memory access information retrieve response Figure 3 – Attribute definitions |
65 | Figure 4 – Access code definitions Table 27 – Access codes of network module memory Table 28 – Access codes of controller memory |
66 | Figure 5 – Structure for RUN request Figure 6 – Structure for RUN response |
67 | Figure 7 – Structure for STOP request Figure 8 – Structure for STOP response Figure 9 – Structure for batch memory read request |
68 | Figure 10 – Structure for batch memory read response Figure 11 – Structure for random memory read request |
69 | Figure 12 – Structure for random memory read response |
70 | Figure 13 – Structure for batch memory write request Figure 14 – Structure for batch memory write response |
71 | Figure 15 – Structure for random memory write request Figure 16 – Structure for random memory write response |
72 | Table 29 – byteValidity 5.2.13 NTNTest-PDU 5.2.14 CyclicDataW-PDU |
73 | 5.2.15 CyclicDataB-PDU |
74 | 5.2.16 CyclicDataOut1-PDU 5.2.17 CyclicDataOut2-PDU |
75 | 5.2.18 CyclicDataIn1-PDU |
76 | 5.2.19 CyclicDataIn2-PDU |
77 | Table 30 – afFType 5.3 FALPDU type F elements encoding 5.3.1 FALARHeader |
78 | Table 31 – dataType |
79 | Table 32 – varField Table 33 – nodeType |
80 | Table 34 – ProtocolVerType |
81 | 5.3.2 Persuasion-PDU |
82 | 5.3.3 TestData-PDU 5.3.4 TestDataAck-PDU |
83 | Table 35 – Link status 5.3.5 Setup-PDU |
84 | Table 36 – Port enable/disable specification |
85 | 5.3.6 SetupAck-PDU |
87 | 5.3.7 F-Token-PDU |
88 | 5.3.8 F-Measure-PDU 5.3.9 F-Offset-PDU |
89 | 5.3.10 F-Update-PDU 5.3.11 F-MyStatus-PDU |
91 | Table 37 – Cyclic transmission parameter hold status Table 38 – Detailed application operation status Table 39 – Error detection status |
93 | Table 40 – Slave-specific event reception status |
94 | 5.3.12 F-CyclicData-PDU |
95 | 5.3.13 Transient1-PDU |
96 | Table 41 – dataSupType of dataType (0x07) Table 42 – FieldSpecificTransient opHeader |
97 | Table 43 – command (dataType: 0x07, dataSubType: 0x0002) Table 44 – subCommand type for each command type Table 45 – Structure of Deliver node information |
98 | Table 46 – Structure of Deliver node information – message Table 47 – Structure of Get statistical information response |
99 | Table 48 – Structure of Acquisition of node details response 5.3.14 TransientAck-PDU |
100 | 5.3.15 Transient2-PDU |
101 | Table 49 – Execution module specification |
102 | Table 50 – Command type |
103 | 5.3.16 ParamCheck-PDU |
104 | 5.3.17 Parameter-PDU |
111 | 5.3.18 Timer-PDU 6 Structure of the FAL protocol state machine |
112 | Figure 17 – Relationships between protocol machines 7 FAL service protocol machine (FSPM) 7.1 Overview 7.2 FSPM type C 7.2.1 Overview |
113 | Figure 18 – Structure of FSPM C 7.2.2 FSPM |
114 | Table 51 – Cyclic data state table Table 52 – Acyclic data state table |
116 | Figure 19 – Structure of FSPM F Table 53 – Management state table 7.3 FSPM type F 7.3.1 Overview |
118 | 7.3.2 FSPM |
119 | Table 54 – Cyclic data state table Table 55 – Acyclic data state table |
122 | Table 56 – Management state table Table 57 – Synchronization state table Table 58 – Measurement state table |
123 | Figure 20 – Structure of ARPM C 8 Application relationship protocol machine (ARPM) 8.1 ARPM type C 8.1.1 Overview 8.1.2 Acyclic transmission |
124 | Table 59 – Acyclic transmission state table |
125 | Table 60 – Acyclic transmission functions Table 61 – Cyclic transmission state table 8.1.3 Cyclic transmission |
130 | Table 62 – Cyclic transmission functions 8.1.4 Connection control |
131 | Table 63 – Connection control state machine – Initial Table 64 – Connection control state machine – Connect |
133 | Table 65 – Connection control state machine – Scan |
136 | Table 66 – Connection control state machine – ScanWait |
139 | Table 67 – Connection control state machine – Collect |
142 | Table 68 – Connection control state machine – CollectWait |
145 | Table 69 – Connection control state machine – Select |
148 | Table 70 – Connection control state machine – TokenStartWait |
151 | Table 71 – Connection control state machine – LaunchWait |
154 | Table 72 – Connection control state machine – TokenReleaseWait |
157 | Table 73 – Connection control state machine – TokenReleased |
162 | Table 74 – Connection control state machine – TokenWait |
167 | Table 75 – Connection control state machine – NTNTestMaster Table 76 – Connection control state machine – NTNTestSlave |
168 | Table 77 – Function list of connection control Table 78 – Common parameter dist state table 8.1.5 Common parameter dist |
172 | Table 79 – Function list of connection control |
173 | Figure 21 – Structure of ARPM F Table 80 – Mapping of internal service and acyclic transmission service 8.2 ARPM type F 8.2.1 Overview |
174 | 8.2.2 Acyclic transmission Table 81 – Acyclic transmission states Table 82 – Acyclic transmission state table |
176 | 8.2.3 Cyclic transmission Table 83 – Acyclic transmission functions Table 84 – Acyclic transmission variables |
177 | Table 85 – Cyclic transmission states Table 86 – Cyclic transmission state table |
179 | 8.2.4 Channel control Table 87 – Cyclic transmission functions Table 88 – Cyclic transmission variables Table 89 – Master station channel control states |
180 | Table 90 – Slave station channel control states Table 91 – Master station state table – MasterDown Table 92 – Master station state table – Listen |
182 | Table 93 – Master station state table – MasterArbitration |
183 | Table 94 – Master station state table – PrimaryMasterScatterTD |
185 | Table 95 – Master station state table – PrimaryMasterSettingUp |
188 | Table 96 – Master station state table – PrimaryMasterHoldToken |
191 | Table 97 – Master station state table – PrimaryMasterSolicitToken |
193 | Table 98 – Master station state table – PrimaryMasterInviting |
195 | Table 99 – Master station state table – MasterWaitTD |
197 | Table 100 – Master station state table – MasterWaitSetup |
198 | Table 101 – Master station state table – MasterSolictToken(without Transmission path delay measurement) |
200 | Table 102 – Master station state table – MasterSolictToken(with Transmission path delay measurement) |
202 | Table 103 – Master station state table – MasterHoldToken |
205 | Table 104 – Master station state table – MasterMeasurement(without Transmission path delay measurement function) Table 105 – Master station state table – MasterMeasurement(with Transmission path delay measurement function) Table 106 – Slave station state table – SlaveDown |
206 | Table 107 – Slave station state table – SlaveWaitTD |
207 | Table 108 – Slave station state table – SlaveWaitSetup |
208 | Table 109 – Slave station state table – SlaveSolicitToken(without Transmission path delay measurement) |
209 | Table 110 – Slave station state table – SlaveSolicitToken(with Transmission path delay measurement) |
211 | Table 111 – Slave station state table – SlaveHoldToken |
214 | Table 112 – Master station channel control functions |
215 | Table 113 – Slave station channel control functions |
216 | Table 114 – Master station channel control variables Table 115 – Slave station channel control variables |
217 | 8.2.5 Parameter dist Table 116 – Master station channel control timers Table 117 – Slave station channel control timers Table 118 – Master station parameter dist states Table 119 – Slave station parameter dist states |
218 | Table 120 – Master station parameter dist state table |
219 | Table 121 – Slave station parameter dist state table |
220 | 8.2.6 Synchronous trigger Table 122 – Master station parameter dist functions Table 123 – Slave station parameter dist functions |
221 | Table 124 – Master station synchronous trigger states Table 125 – Slave station synchronous trigger states Table 126 – Master station synchronous trigger state table Table 127 – Slave station synchronous trigger state table Table 128 – Synchronous trigger functions |
222 | 8.2.7 Timer Table 129 – Timer states – Best effort type Table 130 – Timer states – Fixed cycle type Table 131 – Timer state table – Best effort type Table 132 – Timer state table – Fixed cycle type Table 133 – Timer variables |
223 | 8.2.8 Measure transmission Table 134 – Fixed cycle timer Table 135 – Master station measure transmission states Table 136 – Slave station measure transmission states |
224 | Table 137 – Master station measure transmission state table |
225 | Table 138 – Slave station measure transmission state table |
226 | Table 139 – Master station measure transmission functions Table 140 – Slave station measure transmission functions |
227 | Figure 22 – Structure of type C DMPM Table 141 – Master station measure transmission variables 9 DLL mapping protocol machine (DMPM) 9.1 DMPM type C |
228 | Table 142 – Mapping of type C DMPM service and DL service Table 143 – Destination address for each type C PDU 9.2 DMPM type F |
229 | Figure 23 – Structure of type F DMPM Table 144 – Mapping of type F DMPM service and DL service |
230 | Bibliography |