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