{"id":245453,"date":"2024-10-19T16:08:37","date_gmt":"2024-10-19T16:08:37","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-6-22019\/"},"modified":"2024-10-25T11:08:43","modified_gmt":"2024-10-25T11:08:43","slug":"bs-en-iec-61158-6-22019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-6-22019\/","title":{"rendered":"BS EN IEC 61158-6-2:2019"},"content":{"rendered":"
1.1 General<\/b><\/p>\n
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 \u201cwindow between corresponding application programs.\u201d<\/p>\n
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 2 fieldbus. The term \u201ctime-critical\u201d 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.<\/p>\n
This International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of<\/p>\n
the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;<\/p>\n<\/li>\n
the transfer syntax defining encoding rules that are applied to the application layer protocol data units;<\/p>\n<\/li>\n
the application context state machine defining the application service behavior visible between communicating application entities;<\/p>\n<\/li>\n
the application relationship state machines defining the communication behavior visible between communicating application entities.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this document is to define the protocol provided to<\/p>\n
define the wire-representation of the service primitives defined in IEC 61158-5-2, and<\/p>\n<\/li>\n
define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
This document specifies the protocol 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).<\/p>\n
1.2 Specifications<\/b><\/p>\n
The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-2.<\/p>\n
A secondary objective is to provide migration paths from previously-existing industrial communications protocols.<\/p>\n
1.3 Conformance<\/b><\/p>\n
This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.<\/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 | ||||||
19<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 1 Scope 1.1 General 1.2 Specifications <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions from other ISO\/IEC standards 3.1.1 Terms and definitions from ISO\/IEC\u00a074981 <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.1.2 Terms and definitions from ISO\/IEC\u00a09545 3.1.3 Terms and definitions from ISO\/IEC\u00a088241 <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.1.4 Terms and definitions from ISO\/IEC\u00a088251 3.2 Terms and definitions from IEC\u00a06115852 3.3 Additional terms and definitions <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 3.4 Abbreviated terms and symbols 3.5 Conventions 3.5.1 General concept <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 3.5.2 Attribute specification 3.5.3 Common services Figures Figure\u00a01 \u2013 Attribute table format and terms Figure\u00a02 \u2013 Service request\/response parameter <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Tables Table\u00a01 \u2013 Get_Attributes_All response service rules Table\u00a02 \u2013 Example class level object\/service specific response data of Get_Attributes_All <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table\u00a03 \u2013 Example Get_Attributes_All data array method <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table\u00a04 \u2013 Set_Attributes_All request service rules Table\u00a05 \u2013 Example Set_Attributes_All attribute ordering method Table\u00a06 \u2013 Example Set_Attributes_All data array method <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 3.5.4 State machine conventions Figure\u00a03 \u2013 Example of an STD <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 4 Abstract syntax 4.1 FAL PDU abstract syntax 4.1.1 General Table\u00a07 \u2013 State event matrix format Table\u00a08 \u2013 Example state event matrix <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 4.1.2 PDU structure <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 4.1.3 UCMM_PDUs <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table\u00a09 \u2013 UCMM_PDU header format Table\u00a010 \u2013 UCMM command codes <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 4.1.4 Transport_Headers Table\u00a011 \u2013 Transport class 0 header Table\u00a012 \u2013 Transport class 1 header Table\u00a013 \u2013 Transport class 2 header Table\u00a014 \u2013 Transport class 3 header <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table\u00a015 \u2013 Real-time data header \u2013 exclusive owner Table\u00a016 \u2013 Real-time data header\u2013 redundant owner <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 4.1.5 CM_PDUs <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table\u00a017 \u2013 Forward_Open request format Table\u00a018 \u2013 Forward_Open_Good response format <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table\u00a019 \u2013 Forward_Open_Bad response format <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table\u00a020 \u2013 Large_Forward_Open request format Table\u00a021 \u2013 Large_Forward_Open_Good response format <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table\u00a022 \u2013 Large_Forward_Open_Bad response format <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table\u00a023 \u2013 Forward_Close request format Table\u00a024 \u2013 Forward_Close_Good response format <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table\u00a025 \u2013 Forward_Close_Bad response format Table\u00a026 \u2013 Unconnected_Send request format <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Table\u00a027 \u2013 Unconnected_Send_Good response format <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table\u00a028 \u2013 Unconnected_Send_Bad response format <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table\u00a029 \u2013 Unconnected_Send request format (modified) Table\u00a030 \u2013 Unconnected_Send_Good response format (modified) <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table\u00a031 \u2013 Unconnected_Send_Bad response format (modified) Table\u00a032 \u2013 Get_Connection_Data request format Table\u00a033 \u2013 Get_Connection_Data response format <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table\u00a034 \u2013 Search_Connection_Data request format <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 4.1.6 CM PDU components Table\u00a035 \u2013 Get_Connection_Owner request format Table\u00a036 \u2013 Get_Connection_Owner response format <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure\u00a04 \u2013 Network connection parameters <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table\u00a037 \u2013 Time-out multiplier <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure\u00a05 \u2013 Priority\/Tick_time bit definition Table\u00a038 \u2013 Tick time units <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table\u00a039 \u2013 Encoded application path ordering <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 4.1.7 MR headers Table\u00a040 \u2013 Transport class, trigger and Is_Server format Table\u00a041 \u2013 MR_Request_Header format <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 4.1.8 OM_Service_PDU Table\u00a042 \u2013 MR_Response_Header format Table\u00a043 \u2013 Structure of Get_Attributes_All_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table\u00a044 \u2013 Structure of Set_Attributes_All_RequestPDU body Table\u00a045 \u2013 Structure of Get_Attribute_List_RequestPDU body Table\u00a046 \u2013 Structure of Get_Attribute_List_ResponsePDU body Table\u00a047 \u2013 Structure of Set_Attribute_List_RequestPDU body <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table\u00a048 \u2013 Structure of Set_Attribute_List_ResponsePDU body Table\u00a049 \u2013 Structure of Reset_RequestPDU body Table\u00a050 \u2013 Structure of Reset_ResponsePDU body Table\u00a051 \u2013 Structure of Start_RequestPDU body Table\u00a052 \u2013 Structure of Start_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table\u00a053 \u2013 Structure of Stop_RequestPDU body Table\u00a054 \u2013 Structure of Stop_ResponsePDU body Table\u00a055 \u2013 Structure of Create_RequestPDU body Table\u00a056 \u2013 Structure of Create_ResponsePDU body Table\u00a057 \u2013 Structure of Delete_RequestPDU body Table\u00a058 \u2013 Structure of Delete_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table\u00a059 \u2013 Structure of Get_Attribute_Single_ResponsePDU body Table\u00a060 \u2013 Structure of Set_Attribute_Single_RequestPDU body Table\u00a061 \u2013 Structure of Set_Attribute_Single_ResponsePDU body Table\u00a062 \u2013 Structure of Find_Next_Object_Instance_RequestPDU body <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table\u00a063 \u2013 Structure of Find_Next_Object_Instance_ResponsePDU body Table\u00a064 \u2013 Structure of Apply_Attributes_RequestPDU body Table\u00a065 \u2013 Structure of Apply_Attributes_ResponsePDU body Table\u00a066 \u2013 Structure of Save_RequestPDU body Table\u00a067 \u2013 Structure of Save_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table\u00a068 \u2013 Structure of Restore_RequestPDU body Table\u00a069 \u2013 Structure of Restore_ResponsePDU body Table\u00a070 \u2013 Structure of Get_Member_ResponsePDU body Table\u00a071 \u2013 Structure of Set_Member_RequestPDU body Table\u00a072 \u2013 Structure of Set_Member_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table\u00a073 \u2013 Structure of Insert_Member_RequestPDU body Table\u00a074 \u2013 Structure of Insert_Member_ResponsePDU body Table\u00a075 \u2013 Structure of Remove_Member_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure\u00a06 \u2013 Member ID\/EX description (WORD) Table\u00a076 \u2013 Common structure of _Member_RequestPDU body (basic format) Table\u00a077 \u2013 Common structure of _Member_ResponsePDU body (basic format) <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table\u00a078 \u2013 Common structure of _Member_RequestPDU body (extended format) Table\u00a079 \u2013 Common structure of _Member_ResponsePDU body (extended format) Table\u00a080 \u2013 Extended Protocol ID <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table\u00a081 \u2013 Structure of _Member_RequestPDU body (Multiple Sequential Members) Table\u00a082 \u2013 Structure of _Member_ResponsePDU body (Multiple Sequential Members) <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table\u00a083 \u2013 Structure of _Member_RequestPDU body (International String Selection) Table\u00a084 \u2013 Structure of _Member_ResponsePDU body (International String Selection) Table\u00a085 \u2013 Structure of Group_Sync_RequestPDU body Table\u00a086 \u2013 Structure of Group_Sync_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table\u00a087 \u2013 Structure of Multiple_Service_Packet_RequestPDU body Table\u00a088 \u2013 Structure of Multiple_Service_Packet_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table\u00a089 \u2013 Identity object class attributes Table\u00a090 \u2013 Identity object instance attributes <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table\u00a091 \u2013 Identity object bit definitions for status instance attribute <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table\u00a092 \u2013 Default values for extended device status field (bits 4 to 7)of status instance attribute Table\u00a093 \u2013 Identity object bit definitions for protection mode instance attribute Table\u00a094 \u2013 Class level object\/service specific response data of Get_Attributes_All <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Table\u00a095 \u2013 Instance level object\/service specific response data of Get_Attributes_All Table\u00a096 \u2013 Object-specific request parameter for Reset <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table\u00a097 \u2013 Reset service parameter values Table\u00a098 \u2013 Communication link attributes that shall be preserved Table\u00a099 \u2013 Structure of Flash_LEDs_RequestPDU body <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Table\u00a0100 \u2013 Message Router object class attributes Table\u00a0101 \u2013 Message Router object instance attributes Table\u00a0102 \u2013 Class level object\/service specific response data of Get_Attributes_All <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Table\u00a0103 \u2013 Instance level object\/service specific response data of Get_Attributes_All Table\u00a0104 \u2013 Structure of Symbolic_Translation_RequestPDU body Table\u00a0105 \u2013 Structure of Symbolic_Translation_ResponsePDU body Table\u00a0106 \u2013 Object specific status for Symbolic_Translation service <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table\u00a0107 \u2013 Assembly object class attributes Table\u00a0108 \u2013 Assembly object instance attributes <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table\u00a0109 \u2013 Assembly Instance ID ranges Table\u00a0110 \u2013 Acknowledge Handler object class attributes <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table\u00a0111 \u2013 Acknowledge Handler object instance attributes Table\u00a0112 \u2013 Structure of Add_AckData_Path_RequestPDU body Table\u00a0113 \u2013 Structure of Remove_AckData_Path_RequestPDU body <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table\u00a0114 \u2013 Time Sync object class attributes Table\u00a0115 \u2013 Time Sync object instance attributes <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table\u00a0116 \u2013 ClockIdentity encoding for different network implementations Table\u00a0117 \u2013 ClockClass values Table\u00a0118 \u2013 TimeAccuracy values <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table\u00a0119 \u2013 TimePropertyFlags bit values Table\u00a0120 \u2013 TimeSource values <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table\u00a0121 \u2013 Types of Clock Table\u00a0122 \u2013 Network protocol to PortPhysicalAddressInfo mapping <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table\u00a0123 \u2013 Parameter object class attributes Table\u00a0124 \u2013 Parameter Class Descriptor bit values <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table\u00a0125 \u2013 Parameter object instance attributes <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table\u00a0126 \u2013 Semantics of Descriptor Instance attribute Table\u00a0127 \u2013 Descriptor Scaling bits usage <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table\u00a0128 \u2013 Minimum and Maximum Value semantics <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table\u00a0129 \u2013 Scaling Formula attributes Table\u00a0130 \u2013 Scaling links <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Table\u00a0131 \u2013 Class level object\/service specific response data of Get_Attributes_All Table\u00a0132 \u2013 Instance level object\/service specific response dataof Get_Attributes_All (Parameter object stub) <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table\u00a0133 \u2013 Instance level object\/service specific response dataof Get_Attributes_All (full Parameter object) <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table\u00a0134 \u2013 Structure of Get_Enum_String_RequestPDU body Table\u00a0135 \u2013 Structure of Get_Enum_String_ResponsePDU body Table\u00a0136 \u2013 Enumerated strings Type versus Parameter data type <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table\u00a0137 \u2013 Connection Manager object class attributes Table\u00a0138 \u2013 Connection Manager object instance attributes <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table\u00a0139 \u2013 Class level object\/service specific response data of Get_Attributes_All Table\u00a0140 \u2013 Instance level object\/service specific response data of Get_Attributes_All <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table\u00a0141 \u2013 Instance level object\/service specific request data of Set_Attributes_All Table\u00a0142 \u2013 Connection object class attributes <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table\u00a0143 \u2013 Connection object instance attributes <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table\u00a0144 \u2013 Values assigned to the state attribute <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Figure\u00a07 \u2013 Transport Class Trigger attribute Table\u00a0145 \u2013 Values assigned to the instance_type attribute <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table\u00a0146 \u2013 Possible values within Direction Bit Table\u00a0147 \u2013 Possible values within Production Trigger Bits <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table\u00a0148 \u2013 Possible values within Transport Class Bits Table\u00a0149 \u2013 TransportClass_Trigger attribute values summary <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table\u00a0150 \u2013 Transport Class 0 client behavior summary Table\u00a0151 \u2013 Transport Class 1, 2 and 3 client behavior summary <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Figure\u00a08 \u2013 CP2\/3_initial_comm_characteristics attribute format Table\u00a0152 \u2013 Values defined for the CP2\/3_produced_connection_id attribute Table\u00a0153 \u2013 Values defined for the CP2\/3_consumed_connection_id attribute <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table\u00a0154 \u2013 Values for the Initial Production Characteristics nibble <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table\u00a0155 \u2013 Values for the Initial Consumption Characteristics nibble <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Table\u00a0156 \u2013 Values for the watchdog_timeout_action <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Table\u00a0157 \u2013 Structure of Connection_Bind_RequestPDU body Table\u00a0158 \u2013 Object specific status for Connection_Bind service Table\u00a0159 \u2013 Structure of Producing_Application_Lookup_RequestPDU body <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 4.1.9 Message and connection paths Table\u00a0160 \u2013 Structure of Producing_Application_Lookup_ResponsePDU body Table\u00a0161 \u2013 Producing_Application_Lookup Service status codes <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | Figure\u00a09 \u2013 Segment type <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Figure\u00a010 \u2013 Port segment Table\u00a0162 \u2013 Possible port segment examples <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table\u00a0163 \u2013 TCP\/IP link address examples <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | Figure\u00a011 \u2013 Logical segment encoding Table\u00a0164 \u2013 Extended Logical Type <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Table\u00a0165 \u2013 Electronic key segment format <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table\u00a0166 \u2013 Logical segments examples <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Table\u00a0167 \u2013 Network segments <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Figure\u00a012 \u2013 Extended network segment Table\u00a0168 \u2013 Extended subtype definitions <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Figure\u00a013 \u2013 Symbolic segment encoding Table\u00a0169 \u2013 Symbolic segment examples <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table\u00a0170 \u2013 Data segment Table\u00a0171 \u2013 ANSI_Extended_Symbol segment <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | 4.1.10 Class, attribute and service codes Table\u00a0172 \u2013 Addressing categories Table\u00a0173 \u2013 Class code ID ranges <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Table\u00a0174 \u2013 Attribute ID ranges Table\u00a0175 \u2013 Service code ranges <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table\u00a0176 \u2013 Class codes <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Table\u00a0177 \u2013 Reserved class attributes for all object class definitions Table\u00a0178 \u2013 Common services list <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Table\u00a0179 \u2013 Identity object specific services list Table\u00a0180 \u2013 Message Router object specific services list Table\u00a0181 \u2013 Acknowledge Handler object specific services list Table\u00a0182 \u2013 Parameter object specific services list <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Table\u00a0183 \u2013 Services specific to Connection Manager Table\u00a0184 \u2013 Services specific to Connection object <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 4.1.11 Error codes Table\u00a0185 \u2013 Device type numbering <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Table\u00a0186 \u2013 Connection Manager service request error codes <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Table\u00a0187 \u2013 General status codes <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Table\u00a0188 \u2013 Extended status code for a general status of "Key Failure in path <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table\u00a0189 \u2013 Identity object status codes <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | 4.2 Data abstract syntax specification 4.2.1 Transport format specification 4.2.2 Abstract syntax notation <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | 4.2.3 Control network data specification <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | 4.2.4 Data type specification \/ dictionaries <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | 4.3 Encapsulation abstract syntax 4.3.1 Encapsulation protocol Figure\u00a014 \u2013 Encapsulation message <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Table\u00a0190 \u2013 Encapsulation header Table\u00a0191 \u2013 Encapsulation command codes <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | 4.3.2 Command descriptions Table\u00a0192 \u2013 Encapsulation status codes <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | Table\u00a0193 \u2013 Nop request encapsulation header Table\u00a0194 \u2013 RegisterSession request encapsulation header <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Table\u00a0195 \u2013 RegisterSession request data portion Table\u00a0196 \u2013 RegisterSession reply encapsulation header <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Table\u00a0197 \u2013 RegisterSession reply data portion (successful) Table\u00a0198 \u2013 UnRegisterSession request encapsulation header <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table\u00a0199 \u2013 ListServices request encapsulation header Table\u00a0200 \u2013 ListServices reply encapsulation header <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Table\u00a0201 \u2013 ListServices reply data portion (successful) Table\u00a0202 \u2013 Communications capability flags <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table\u00a0203 \u2013 ListIdentity request encapsulation header <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Table\u00a0204 \u2013 ListIdentity reply encapsulation header Table\u00a0205 \u2013 ListIdentity reply data portion (successful) <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Table\u00a0206 \u2013 CPF\u00a02 identity item <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table\u00a0207 \u2013 ListInterfaces request encapsulation header Table\u00a0208 \u2013 ListInterfaces reply encapsulation header <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table\u00a0209 \u2013 SendRRData request encapsulation header Table\u00a0210 \u2013 SendRRData request data portion <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table\u00a0211 \u2013 SendRRData reply encapsulation header Table\u00a0212 \u2013 SendUnitData request encapsulation header Table\u00a0213 \u2013 SendUnitData request data portion <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | 4.3.3 Common packet format Table\u00a0214 \u2013 Common packet format Table\u00a0215 \u2013 CPF item format Table\u00a0216 \u2013 Item Type ID numbers <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table\u00a0217 \u2013 Null address item Table\u00a0218 \u2013 Connected address item <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Table\u00a0219 \u2013 Sequenced address item Table\u00a0220 \u2013 Unconnected data item Table\u00a0221 \u2013 Connected data item <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Table\u00a0222 \u2013 Sockaddr info items <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | 5 Transfer syntax 5.1 Compact encoding 5.1.1 Encoding rules Table\u00a0223 \u2013 Usage of CPF items <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 5.1.2 Encoding constraints 5.1.3 Examples Table\u00a0224 \u2013 BOOLEAN encoding Table\u00a0225 \u2013 Example compact encoding of a BOOL value Table\u00a0226 \u2013 Encoding of SignedInteger values Table\u00a0227 \u2013 Example compact encoding of a SignedInteger value <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Table\u00a0228 \u2013 UnsignedInteger values Table\u00a0229 \u2013 Example compact encoding of an UnsignedInteger Table\u00a0230 \u2013 FixedLengthReal values Table\u00a0231 \u2013 Example compact encoding of a REAL value Table\u00a0232 \u2013 Example compact encoding of a LREAL value <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Table\u00a0233 \u2013 FixedLengthReal values Table\u00a0234 \u2013 STRING value Table\u00a0235 \u2013 STRING2 value Table\u00a0236 \u2013 STRINGN value <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Figure\u00a015 \u2013 FixedLengthBitString compact encoding bit placement rules Table\u00a0237 \u2013 SHORT_STRING value Table\u00a0238 \u2013 Example compact encoding of a STRING value Table\u00a0239 \u2013 Example compact encoding of STRING2 value Table\u00a0240 \u2013 SHORT_STRING type <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Figure\u00a016 \u2013 Example compact encoding of a SWORD FixedLengthBitString Figure\u00a017 \u2013 Example compact encoding of a WORD FixedLengthBitString Figure\u00a018 \u2013 Example compact encoding of a DWORD FixedLengthBitString Figure\u00a019 \u2013 Example compact encoding of a LWORD FixedLengthBitString <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Table\u00a0241 \u2013 Example compact encoding of a single dimensional ARRAY Table\u00a0242 \u2013 Example compact encoding of a multi\u00addimensional ARRAY <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | 5.2 Data type reporting 5.2.1 Object data representation Table\u00a0243 \u2013 Example compact encoding of a STRUCTURE <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | 5.2.2 Elementary data type reporting Table\u00a0244 \u2013 Identification codes and descriptions of elementary data types <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | 5.2.3 Constructed data type reporting Table\u00a0245 \u2013 Identification codes and descriptions of constructed data types Table\u00a0246 \u2013 Formal structure encoding definition <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Figure\u00a020 \u2013 Example 1 of formal encoding of a structure type specification Figure\u00a021 \u2013 Example 2 of formal encoding of a structure type specification Table\u00a0247 \u2013 Formal structure with handles encoding definition <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Figure\u00a022 \u2013 Example 3 of formal encoding of a handle structure type specification Figure\u00a023 \u2013 Example 4 of formal encoding of a handle structure type specification Table\u00a0248 \u2013 Abbreviated structure encoding definition <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Figure\u00a024 \u2013 Example 5 of abbreviated encoding of a structure type specification Table\u00a0249 \u2013 Formal array encoding definition <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Figure\u00a025 \u2013 Example 1 of formal encoding of an array type specification Figure\u00a026 \u2013 Example 2 of formal encoding of an array type specification <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Figure\u00a027 \u2013 Example 1 of abbreviated encoding of an array type specification Figure\u00a028 \u2013 Example 2 of abbreviated encoding of an array type specification Table\u00a0250 \u2013 Abbreviated array encoding definition <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | 6 Structure of FAL protocol state machines 7 AP-Context state machine 7.1 Overview 7.2 Connection object state machine 7.2.1 I\/O Connection instance behavior Figure\u00a029 \u2013 I\/O Connection object state transition diagram <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Table\u00a0251 \u2013 I\/O Connection state event matrix <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | 7.2.2 Bridged Connection instance behavior Figure\u00a030 \u2013 Bridged Connection object state transition diagram Table\u00a0252 \u2013 Bridged Connection state event matrix <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | 7.2.3 Explicit Messaging Connection instance behavior <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Figure\u00a031 \u2013 Explicit Messaging Connection object state transition diagram Table\u00a0253 \u2013 Explicit Messaging Connection state event matrix <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | 8 FAL service protocol machine (FSPM) 8.1 General 8.2 Primitive definitions <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Table\u00a0254 \u2013 Primitives issued by FAL user to FSPM Table\u00a0255 \u2013 Primitives issued by FAL user to FSPM <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Table\u00a0256 \u2013 Primitives issued by FSPM to FAL user <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 8.3 Parameters of primitives 8.4 FSPM state machines Table\u00a0257 \u2013 Parameters used with primitives exchanged between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | 9 Application relationship protocol machines (ARPMs) 9.1 General 9.2 Connection-less ARPM (UCMM) 9.2.1 General 9.2.2 Primitive definitions <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | 9.2.3 Parameters of primitives Table\u00a0258 \u2013 Primitives issued by FSPM to ARPM Table\u00a0259 \u2013 Primitives issued by ARPM to FSPM Table\u00a0260 \u2013 Parameters used with primitives exchanged between FSPM and ARPM <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | 9.2.4 UCMM state machines Figure\u00a032 \u2013 State transition diagram of UCMM client9 Table\u00a0261 \u2013 UCMM client states <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | Table\u00a0262 \u2013 State event matrix of UCMM client <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Figure\u00a033 \u2013 State transition diagram of high\u2013end UCMM server Table\u00a0263 \u2013 High-end UCMM server states <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Table\u00a0264 \u2013 State event matrix of high-end UCMM server <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Figure\u00a034 \u2013 State transition diagram of low\u2013end UCMM server Table\u00a0265 \u2013 Low-end UCMM server states <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 9.2.5 Examples of UCMM sequences Table\u00a0266 \u2013 State event matrix of low\u2013end UCMM server <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | Figure\u00a035 \u2013 Sequence diagram for a UCMM with one outstanding message <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | 9.2.6 Management UCMM Figure\u00a036 \u2013 Sequence diagram for a UCMM with multiple outstanding messages <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | 9.3 Connection-oriented ARPMs (transports) 9.3.1 Transport PDU buffer 9.3.2 Transport classes Figure\u00a037 \u2013 TPDU buffer Table\u00a0267 \u2013 Notification <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | 9.3.3 Common primitive definitions Table\u00a0268 \u2013 Transport classes Table\u00a0269 \u2013 Primitives issued by FSPM to ARPM <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 9.3.4 Parameters of common primitives 9.3.5 Transport state machines \u2013 class 0 Table\u00a0270 \u2013 Primitives issued by ARPM to FSPM Table\u00a0271 \u2013 Parameters used with primitives exchanged between FSPM and ARPM <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Figure\u00a038 \u2013 Data flow diagram using a client transport class 0 and server transport class 0 Figure\u00a039 \u2013 Sequence diagram of data transfer using transport class 0 <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | Figure\u00a040 \u2013 Class 0 client STD Table\u00a0272 \u2013 Class 0 transport client states Table\u00a0273 \u2013 Class 0 client SEM <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Figure\u00a041 \u2013 Class 0 server STD Table\u00a0274 \u2013 Class 0 transport server states Table\u00a0275 \u2013 Class 0 server SEM <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | 9.3.6 Transport state machines \u2013 class 1 Figure\u00a042 \u2013 Data flow diagram using client transport class 1and server transport class\u00a01 <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Figure\u00a043 \u2013 Sequence diagram of data transferusing client transport class 1 and server transport class 1 <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | Table\u00a0276 \u2013 Class 1 transport client states <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Figure\u00a044 \u2013 Class 1 client STD Table\u00a0277 \u2013 Class 1 client SEM <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | Figure\u00a045 \u2013 Class 1 server STD Table\u00a0278 \u2013 Class 1 transport server states <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | 9.3.7 Transport state machines \u2013 class 2 Table\u00a0279 \u2013 Class 1 server SEM <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Figure\u00a046 \u2013 Data flow diagram using client transport class 2and server transport class\u00a02 <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Figure\u00a047 \u2013 Diagram of data transfer using client transport class 2and server transport class 2 without returned data <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Figure\u00a048 \u2013 Sequence diagram of data transfer using client transport class 2and server transport class 2 with returned data <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | Figure\u00a049 \u2013 Class 2 client STD Table\u00a0280 \u2013 Class 2 transport client states <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Table\u00a0281 \u2013 Class 2 client SEM <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | Figure\u00a050 \u2013 Class 2 server STD Table\u00a0282 \u2013 Class 2 transport server states <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Table\u00a0283 \u2013 Class 2 server SEM <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | 9.3.8 Transport state machines \u2013 class 3 <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | Figure\u00a051 \u2013 Data flow diagram using client transport class\u00a03and server transport class\u00a03 <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | Figure\u00a052 \u2013 Sequence diagram of data transfer using client transport class 3 and server transport class 3 without returned data <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Figure\u00a053 \u2013 Sequence diagram of data transfer using client transportclass 3 and server transport class 3 with returned data <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | Table\u00a0284 \u2013 Class 3 transport client states <\/td>\n<\/tr>\n | ||||||
249<\/td>\n | Figure\u00a054 \u2013 Class\u00a03 client STD Table\u00a0285 \u2013 Class\u00a03 client SEM <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | Table\u00a0286 \u2013 Class 3 transport server states <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Figure\u00a055 \u2013 Class\u00a03 server STD <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | Table\u00a0287 \u2013 Class\u00a03 server SEM <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | 9.3.9 Transport state machines \u2013 classes 4, 5, 6 9.3.10 Transport state machines \u2013 class 4 9.3.11 Transport state machines \u2013 class 5 9.3.12 Transport state machines \u2013 class 6 10 DLL mapping protocol machine 1 (DMPM 1) 10.1 General Figure\u00a056 \u2013 Data flow diagram for a link producer and consumer <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 10.2 Link producer 10.3 Link consumer 10.4 Primitive definitions 10.4.1 Primitives exchanged between DMPM and ARPM 10.4.2 Parameters of ARPM\/DMPM primitives Table\u00a0288 \u2013 Primitives issued by ARPM to DMPM Table\u00a0289 \u2013 Primitives issued by DMPM to ARPM <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | 10.4.3 Primitives exchanged between data-link layer and DMPM 10.4.4 Parameters of DMPM\/Data-link Layer primitives Table\u00a0290 \u2013 Parameters used with primitives exchanged between ARPM and DMPM Table\u00a0291 \u2013 Primitives exchanged between data-link layer and DMPM Table\u00a0292 \u2013 Parameters used with primitives exchanged between DMPM and Data-link <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | 10.4.5 Network connection ID Table\u00a0293 \u2013 Selection of connection ID <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | 10.5 DMPM state machine 10.5.1 DMPM states Figure\u00a057 \u2013 State transition diagram for a link producer Table\u00a0294 \u2013 Link producer states Table\u00a0295 \u2013 State event matrix of link producer <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | 10.5.2 Functions used by DMPM 10.6 Data-link Layer service selection 11 DLL mapping protocol machine 2 (DMPM 2) 11.1 General Figure\u00a058 \u2013 State transition diagram for a link consumer Table\u00a0296 \u2013 Link consumer states Table\u00a0297 \u2013 State event matrix of link consumer <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 11.2 Mapping of UCMM PDUs 11.2.1 General Table\u00a0298 \u2013 UCMM request <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | 11.2.2 Common requirements for Connection Manager PDU\u2019s Table\u00a0299 \u2013 UCMM reply <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | Table\u00a0300 \u2013 Network Connection ID selection <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | 11.2.3 Forward_open PDU for class 2 and class 3 connections 11.2.4 Forward_open for class 0 and class 1 connections <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | Table\u00a0301 \u2013 Sockaddr Info usage <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | 11.2.5 Forward_close Table\u00a0302 \u2013 Example multicast assignments <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | 11.3 Mapping of transport class 0 and class 1 PDUs 11.3.1 Class 0 and class 1 PDUs 11.3.2 No dependency on TCP connections 11.3.3 Class 0 and class 1 packet ordering Table\u00a0303 \u2013 UDP data format for class 0 and class 1 <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | 11.3.4 Screening incoming connected data 11.4 Mapping of transport class 2 and class 3 PDU\u2019s <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | 11.5 Mapping of transport classes 4 to 6 11.6 IGMP Usage 11.6.1 Background (informative) Table\u00a0304 \u2013 Transport class 2 and class 3 connected data <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | 11.6.2 IGMP Membership Report messages 11.6.3 IGMP Leave Group messages <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | 11.7 Quality of Service (QoS) for CP\u00a02\/2 messages 11.7.1 Overview 11.7.2 DSCP format <\/td>\n<\/tr>\n | ||||||
273<\/td>\n | 11.7.3 IEEE\u00a0802.1D\/IEEE\u00a0802.Q format 11.7.4 Mapping CPF\u00a02 traffic to DSCP and IEEE\u00a0802.1D Figure\u00a059 \u2013 DS field in the IP header Figure\u00a060 \u2013 IEEE\u00a0802.1Q tagged frame Table\u00a0305 \u2013 Default DSCP and IEEE\u00a0802.1D mapping <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | 11.7.5 CP\u00a02\/2 usage of DSCP 11.7.6 CP\u00a02\/2 usage of IEEE\u00a0802.1D\/IEEE\u00a0802.1Q 11.7.7 User considerations with IEEE\u00a0802.1D\/IEEE\u00a0802.1Q <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | 11.8 Management of an encapsulation session 11.8.1 Phases of an encapsulation session 11.8.2 Establishing a session 11.8.3 Terminating a session 11.8.4 Maintaining a session <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | 11.8.5 TCP connection management 12 DLL mapping protocol machine 3 (DMPM 3) <\/td>\n<\/tr>\n | ||||||
277<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 2 elements<\/b><\/p>\n |