{"id":245407,"date":"2024-10-19T16:08:25","date_gmt":"2024-10-19T16:08:25","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-5-22019\/"},"modified":"2024-10-25T11:08:28","modified_gmt":"2024-10-25T11:08:28","slug":"bs-en-iec-61158-5-22019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-5-22019\/","title":{"rendered":"BS EN IEC 61158-5-2:2019"},"content":{"rendered":"
IEC 61158-5-2:2019 (E) defines the services provided to the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and Systems Management at the boundary between the application layer and Systems Management of the fieldbus reference model. This standard specifies the structure and services 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) This fourth edition cancels and replaces the third edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: \u2022addition of a data type in 5.3.2; \u2022clarifications of Object management ASE in 6.2.1; <\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | National foreword <\/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 | CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1 Scope 1.1 General <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 ISO\/IEC\u00a074981 terms <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3.2 ISO\/IEC\u00a08822 terms 3.3 ISO\/IEC\u00a09545 terms 3.4 ISO\/IEC\u00a088241 terms 3.5 Type 2 fieldbus data-link layer terms 3.6 Type 2 fieldbus application-layer specific definitions <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.7 Type 2 abbreviated terms and symbols <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.8 Conventions 3.8.1 Overview <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 3.8.2 General conventions 3.8.3 Conventions for class definitions <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 3.8.4 Conventions for service definitions <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4 Common concepts 5 Data type ASE 5.1 General 5.2 Formal definition of data type objects <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.3 FAL defined data types 5.3.1 Fixed length types <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 5.3.2 String types <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.3.3 Structure types <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Tables Table\u00a01 \u2013 Valid IANA MIB printer codes for character set selection <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.4 Data type ASE service specification 6 Communication model specification 6.1 Concepts 6.1.1 General 6.1.2 General concepts <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.1.3 Relationships between ASEs <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 6.1.4 Naming and addressing Figures Figure\u00a01 \u2013 Overview of ASEs and object classes <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 6.1.5 Data types Figure\u00a02 \u2013 Addressing format using MAC, class, instance and attribute IDs <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table\u00a02 \u2013 Common elements <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table\u00a03 \u2013 ST language elements <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table\u00a04 \u2013 Type conversion operations <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table\u00a05 \u2013 Values of implementation-dependent parameters Table\u00a06 \u2013 Extensions to IEC\u00a0611313:2003 <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 6.2 ASEs 6.2.1 Object management ASE <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure\u00a03 \u2013 Identity object state transition diagram <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table\u00a07 \u2013 Identity object state event matrix <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure\u00a04 \u2013 Explicit and Implicit Setting interaction <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Figure\u00a05 \u2013 Static Assembly state transition diagram Table\u00a08 \u2013 Static Assembly state event matrix <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Figure\u00a06 \u2013 Dynamic Assembly state transition diagram Table\u00a09 \u2013 Static Assembly instance attribute access <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table\u00a010 \u2013 Dynamic Assembly state event matrix Table\u00a011 \u2013 Dynamic Assembly instance attribute access <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table\u00a012 \u2013 Message Router object Forward_Open parameters <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table\u00a013 \u2013 Acknowledge Handler object state event matrix <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table\u00a014 \u2013 Producing I\/O application object state event matrix <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure\u00a07 \u2013 Typical timing relationships for acknowledged data production <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure\u00a08 \u2013 Example of a COS system with two acking devices Figure\u00a09 \u2013 Message flow in COS connection \u2013 one Connection object, one consumer <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure\u00a010 \u2013 Message flow in COS connection \u2013 multiple consumers <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table\u00a015 \u2013 PTPEnable attribute default values <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table\u00a016 \u2013 Profile identification <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table\u00a017 \u2013 Profile default settings and ranges Table\u00a018 \u2013 Profile transports <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table\u00a019 \u2013 Default PTP clock settings Table\u00a020 \u2013 Hand_Set clock quality management <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure\u00a011 \u2013 Path Reconfiguration in a ring topology Table\u00a021 \u2013 Path Reconfiguration Signalling message <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Figure\u00a012 \u2013 CPF2 time synchronization offset clock model <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure\u00a013 \u2013 CPF2 time synchronization system with offset clock model <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Figure\u00a014 \u2013 CPF2 time synchronization group startup sequence <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Figure\u00a015 \u2013 Parameter object state transition diagram Table\u00a022 \u2013 Parameter object state event matrix <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table\u00a023 \u2013 Status codes <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table\u00a024 \u2013 Get_Attributes_All service parameters <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table\u00a025 \u2013 Set_Attributes_All service parameters <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table\u00a026 \u2013 Get_Attribute_List service parameters <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table\u00a027 \u2013 Set_Attribute_List service parameters <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Table\u00a028 \u2013 Reset service parameters <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Table\u00a029 \u2013 Start service parameters <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Table\u00a030 \u2013 Stop service parameters <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Table\u00a031 \u2013 Create service parameters <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Table\u00a032 \u2013 Delete service parameters <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table\u00a033 \u2013 Get_Attribute_Single service parameters <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table\u00a034 \u2013 Set_Attribute_Single service parameters <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table\u00a035 \u2013 Find_Next_Object_Instance service parameters <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Figure\u00a016 \u2013 Example of Find_Next_Object_Instance service <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Table\u00a036 \u2013 NOP service parameters <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Table\u00a037 \u2013 Apply_Attributes service parameters <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table\u00a038 \u2013 Save service parameters <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table\u00a039 \u2013 Restore service parameters <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Table\u00a040 \u2013 Get_Member service parameters <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table\u00a041 \u2013 Set_Member service parameters <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Table\u00a042 \u2013 Insert_Member service parameters <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Table\u00a043 \u2013 Remove_Member service parameters <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Table\u00a044 \u2013 Group_Sync service parameters <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Table\u00a045 \u2013 Add_AckData_Path service parameters <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Table\u00a046 \u2013 Remove_AckData_Path service parameters <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Table\u00a047 \u2013 Get_Enum_String service parameters <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Table\u00a048 \u2013 Symbolic_Translation service parameters <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table\u00a049 \u2013 Flash_LEDs service parameters <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Table\u00a050 \u2013 Multiple_Service_Packet service parameters <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | 6.2.2 Connection manager ASE <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Table\u00a051 \u2013 CM_Open service parameters <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Table\u00a052 \u2013 CM_Close service parameters <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Table\u00a053 \u2013 CM_ Unconnected_Send service parameters <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Table\u00a054 \u2013 CM_Get_Connection_Data service parameters <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Table\u00a055 \u2013 CM_Search_Connection_Data service parameters <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table\u00a056 \u2013 CM_Get_Connection_Data service parameters <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | 6.2.3 Connection ASE <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table\u00a057 \u2013 I\/O Connection object attribute access <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table\u00a058 \u2013 Bridged Connection object attribute access <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table\u00a059 \u2013 Explicit messaging object attribute access <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Figure\u00a017 \u2013 Transmission Trigger Timer behavior <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Figure\u00a018 \u2013 Inactivity watchdog timer Figure\u00a019 \u2013 Using tools for configuration <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Figure\u00a020 \u2013 Production Inhibit Timer behavior <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Table\u00a060 \u2013 Connection_Bind service parameters <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Table\u00a061 \u2013 Service_Name service parameters <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | 6.3 ARs 6.3.1 Overview <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table\u00a062 \u2013 How production trigger, transport class, and CM_RPI determinewhen data is produced <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Figure\u00a021 \u2013 Context of transport services within the connection model Figure\u00a022 \u2013 Application\u2013to\u2013application view of data transfer <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Figure\u00a023 \u2013 Data flow diagram for a link producer <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Figure\u00a024 \u2013 Data flow diagram for a link consumer <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Figure\u00a025 \u2013 Triggers <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Figure\u00a026 \u2013 Binding transport instances to the producer and consumer of a transport connection that does not have a reverse data path Figure\u00a027 \u2013 Binding transport instances to the producers and consumers of a transport connection that does have a reverse data path <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Figure\u00a028 \u2013 Binding transport instances to the producer and consumers of a multipoint connection when the transport connection does not have a reverse data path Figure\u00a029 \u2013 Binding transport instances to the producers and consumers of a multipoint connection when the transport connection does have reverse data paths <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | 6.3.2 UCMM AR formal model <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | 6.3.3 Transport AR formal model Table\u00a063 \u2013 Transport classes <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 6.3.4 AR ASE services <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Table\u00a064 \u2013 UCMM_Create service parameters <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Table\u00a065 \u2013 UCMM_Delete service parameters <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Table\u00a066 \u2013 UCMM_Write service parameters <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | Table\u00a067 \u2013 UCMM_Abort service parameters <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Table\u00a068 \u2013 TR_Write service parameters <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Table\u00a069 \u2013 TR_Trigger service parameters Table\u00a070 \u2013 TR_Packet_arrived service parameters <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Table\u00a071 \u2013 TR_Ack_received service parameters Table\u00a072 \u2013 TR_Verify service parameters <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 6.4 Summary of FAL classes Table\u00a073 \u2013 TR_Status_updated service parameters <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | 6.5 Permitted FAL services by AR type Table\u00a074 \u2013 FAL class summary <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Table\u00a075 \u2013 FAL services by AR type <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 2 elements<\/b><\/p>\n |