🔥🔥 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-27:2023

BS EN IEC 61158-6-27:2023

$215.11

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

Published By Publication Date Number of Pages
BSI 2023 224
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 27 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service, c) the parameters associated with each primitive action and event, and the form which they take, and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this International Standard is to define the services provided to a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This International Standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 289 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this International Standard to provide access to the FAL to control certain aspects of its operation. 1.2 Specifications […] 1.3 Conformance […]

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
7 English
CONTENTS
12 FOREWORD
14 INTRODUCTION
15 1 Scope
1.1 General
1.2 Specifications
16 1.3 Conformance
2 Normative references
17 3 Terms, definitions, abbreviated terms, symbols and conventions
3.1 Referenced terms and definitions
3.1.1 Terms and definitions from ISO/IEC 74981
3.1.2 Terms and definitions from ISO/IEC 9545
18 3.1.3 Terms and definitions from ISO/IEC 88241
3.1.4 Terms and definitions from ISO/IEC 10731
3.1.5 Terms and definitions from ISO/IEC 19501
3.2 Additional terms and definitions
27 3.3 Abbreviations and symbols
29 3.4 Conventions
3.4.1 General conventions
3.4.2 PDU data type conventions
3.4.3 State machine conventions
30 Tables
Table 1 – State transition descriptions
Table 2 – Description of state machine elements
31 4 Abstract syntax
4.1 General
Table 3 – Conventions used in state machines
32 4.2 Basic Data types
33 4.3 FAL PDU types
4.3.1 General
34 Table 4 – Multicast address
Table 5 – Length_or_type
35 Table 6 – IPv4 Header
Table 7 – IPv6 Header
Table 8 – UDP Header
36 4.3.2 Top of APDU types: _APDU
4.3.3 PDUs for field system management service
38 Table 9 – Node address
39 4.3.4 Detailed definitions of _FID-PDUs
53 4.3.5 PDUs for field device control service
62 4.3.6 PDUs for message service
63 4.4 Detailed definitions of _FDCService-PDUs
4.4.1 Enhanced PDU type
77 4.5 Device profile
5 Transfer syntax
5.1 Concepts
78 5.2 Encode rules
5.2.1 INTEGER and its subtypes
Figures
Figure 1 – Encode of Integer subtypes
79 5.2.2 REAL type and its subtypes
Figure 2 – Example of transfer of INTEGER value
Figure 3 – Encode of Unsigned subtypes
80 Figure 4 – Float32 type encode
Figure 5 – Float64 type encode
81 5.2.3 BIT STRING type
Figure 6 – Bit field definition example with named bits
82 5.2.4 OCTET STRING type and IA5String type
5.2.5 NULL type
5.2.6 Structure type and Array type
Figure 7 – Bit field definition example with field size
83 6 Structure of FAL protocol state machine
Figure 8 – SEQUENCE type encode
84 Table 10 – Mapping for Protocol State Machines
85 7 AP-context state machine (APC SM)
7.1 Overview
Figure 9 – Structure of FAL protocol state machines
86 7.2 State descriptions
7.3 Triggering events
Figure 10 – State chart diagram of APC SM
Table 11 – State descriptions of APC SM
87 7.4 Action descriptions at state transitions
Table 12 – Trigger event descriptions of APC SM
88 Table 13 – Transitions of APC SM
89 8 FAL service protocol machines (FSPM)
8.1 Overview
8.2 RT Protocol Machine (RT PM)
8.2.1 Link layer discovery
8.2.2 MAC bridges
91 Figure 11 – Master CTC state transition chart
92 Table 14 – Master CTC state transition table
101 Figure 12 – Slave CTC state transition chart
Table 15 – Slave CTC state transition table
106 Table 16 – List of CTC macros
108 Table 17 – The primitives and parameters for FDC interface issued by FDC
109 Table 18 – The primitives and parameters for FSM interface issued by CTC
Table 19 – The list of primitives and parameters (FSM source)
110 8.2.3 Virtual bridges
8.2.4 IP suite
8.2.5 DLL mapping protocol machine (DMPM)
Table 20 – The list of primitives and parameters (FSMUL source)
111 Figure 13 – Structuring of the protocol machines within the DMPM (bridge)
Figure 14 – SRC state transition chart
112 Table 21 – SRC state transition table
113 Table 22 – List of SRC macros
114 Table 23 – List of SRC functions
115 8.3 Field System Management Protocol Machine (FSM PM)
8.3.1 Overview
Table 24 – Primitives and parameters for SRC-CTC interface
Table 25 – Send frame primitive and parameters
Table 26 – Receive frame primitives and parameters
Table 27 – Primitives and parameters of repeat select service
116 Figure 15 – Example of network configuration
117 8.3.2 Discovery and basic configuration
Figure 16 – Network initialization procedures
118 Figure 17 – Neighboring node notification sequence
119 Figure 18 – Connected node detection sequence
120 8.3.3 Starting up of system
Figure 19 – Example of neighboring node information
121 Figure 20 – FSMUL state transition chart for the master with SM function
122 Table 28 – FSMUL state transition table for the master with SM function
134 Figure 21 – FSMUL state transition chart for the master without SM function
Table 29 – FSMUL state transition table for the master without SM function
143 Figure 22 – FSMUL state transition chart for a slave
Table 30 – FSMUL state transition table for a slave
147 Table 31 – List of FSMUL macros
149 8.3.4 Sync methods
150 Figure 23 – Sequence of SM delay time notification by CDO writing
152 Figure 24 – Delay measurement sequence (SM: BM)
153 Figure 25 – Master delay measurement sequence for the BM (SM: master with band master function (BM))
154 Figure 26 – Delay measurement sequence for the master other than the BM (SM: BM)
156 Figure 27 – Delay measurement sequence (SM: S#1)
157 Figure 28 – Master delay measurement sequence for the BM (SM: S#1)
158 8.3.5 Plug-and-play entry
159 8.4 Field Deice Control Protocol Machine (FDC PM)
8.4.1 Protocol overview
Figure 29 – Plug-and-play entry sequence
160 Table 32 – FDC protocol mode
161 8.4.2 Cyclic communication mode
Figure 30 – Example communication cycle of FDC master AP
162 Figure 31 – Example communication cycle of FDC slave AP
163 Figure 32 – Synchronous command communication in sync state
164 Figure 33 – Asynchronous command communication in sync state
165 8.4.3 Event driven communication mode
Figure 34 – Asynchronous command communication in async state
166 8.4.4 Master Protocol Machine (FDCPM-M)
Figure 35 – Event-driven communication
167 Figure 36 – State chart diagram of FDCPM-M
Table 33 – State descriptions of FDCPM-M
168 Table 34 – Trigger event descriptions of FDCPM-M
169 Table 35 – Transitions of main SM of FDCPM-M
171 Table 36 – Transitions of submachine of FDCPM-M
174 8.4.5 Slave Protocol Machine (FDCPM-S)
175 Figure 37 – State chart diagram of FDCPM-S
Table 37 – State descriptions of FDCPM-S
176 Table 38 – Trigger event descriptions of FDCPM-S
177 Table 39 – Transitions of main SM of FDCPM-S
179 Table 40 – Transitions of submachine of FDCPM-S
184 8.4.6 Error procedure summary
186 8.5 Message Protocol Machine (MSG PM)
8.5.1 Protocol overview
187 Figure 38 – PDU transmission flow for user message
188 8.5.2 Requester Protocol Machine (MSGPM-RQ)
Figure 39 – PDU transmission flow for one-way message
189 Figure 40 – State chart diagram of MSGPM-RQ
Table 41 – State descriptions of MSGPM-RQ
190 Table 42 – Trigger event descriptions of MSGPM-RQ
Table 43 – Transitions of MSGPM-RQ
191 8.5.3 Responder Protocol Machine (MSGPM-RS)
Figure 41 – State chart diagram of MSGPM-RS
Table 44 – State descriptions of MSGPM-RS
192 Table 45 – Trigger event descriptions of MSGPM-RS
Table 46 – Transitions of MSGPM-RS
193 9 Application relationship protocol machine (ARPM)
9.1 General
9.2 ARPM for FDC ASE
9.2.1 Overview
Figure 42 – Example of single transfer process
194 9.2.2 ARPM for FDC Master (ARPM-FDCM)
Figure 43 – Example of dual transfer process
195 Figure 44 – State chart diagram of ARPM-FDCM
196 Table 47 – State descriptions of ARPM-FDCM
198 Table 48 – Trigger event descriptions of ARPM-FDCM
Table 49 – Transitions of main SM of ARPM-FDCM
200 Table 50 – Transitions of submachine of ARPM-FDCM
201 9.2.3 ARPM for FDC Slave (ARPM-FDCS)
Figure 45 – Statechart diagram of ARPM-FDCS
202 Table 51 – State descriptions of ARPM-FDCS
204 Table 52 – Trigger event descriptions of ARPM-FDCS
205 Table 53 – Transitions of main SM of ARPM-FDCS
206 Table 54 – Transitions of submachine of ARPM-FDCS
208 9.3 ARPM for MSG ASE (ARPM-MSG)
9.3.1 State descriptions
9.3.2 Triggering events
Figure 46 – Statechart diagram of ARPM-MSG
Table 55 – State descriptions of ARPM-MSG
Table 56 – Trigger event descriptions of ARPM-MSG
209 9.3.3 Action descriptions at state transitions
10 DLL mapping protocol machines (DMPMs)
Table 57 – Transitions of ARPM-MSG
210 Annex A (informative)Device profile and FDC command sets
Table A.1 – Example of registered device profiles
211 Table A.2 – Example command list of the profile ’00’H
212 Annex B (normative)Virtual memory space and Device Information
B.1 Overview
B.2 Communication Data Object
Figure B.1 – Memory map of virtual memory space
Table B.1 – Memory map of CDO area
213 B.3 Device Information
B.3.1 Device identifier area structure
Figure B.2 – Memory map of device ID area
214 B.3.2 Detail specifications of device IDs
Table B.2 – Specifications of device IDs
222 Annex C (informative)Basic message function
Table C.1 – Example of message command set
223 Bibliography

Related products

BS EN IEC 61158-6-27:2023
$215.11