{"id":244043,"date":"2024-10-19T16:01:33","date_gmt":"2024-10-19T16:01:33","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-6-22012\/"},"modified":"2024-10-25T10:59:47","modified_gmt":"2024-10-25T10:59:47","slug":"bs-en-61158-6-22012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-6-22012\/","title":{"rendered":"BS EN 61158-6-2:2012"},"content":{"rendered":"
IEC 61158-6-2:2010 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 “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. It specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with respect to the previous edition are: – update of normative and bibliographic references; – update of abbreviations; – update list of service request\/response PDUs (Time Sync and Parameter ASEs\/objects); – update of Time Sync ASE\/object; – new Parameter ASE\/object; – update\/add object and services codes for Time Sync and Parameter ASEs; – new QoS specification. This bilingual version published in 2012-07 corresponds to the English version published in 2010-08.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 1 Scope 1.1 General 1.2 Specifications <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and definitions from other ISO\/IEC standards <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 3.2 Terms and definitions from IEC\u00a061158 5 2 3.3 Additional terms and definitions <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.4 Abbreviations and symbols 3.5 Conventions <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figures Figure 1 \u2013 Attribute table format and terms Figure 2 \u2013 Service request\/response parameter <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Tables Table 1 \u2013 Get_Attribute_All response service rules Table 2 \u2013 Example class level object\/service specific response data of Get_Attribute_All <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Table 3 \u2013 Example Get_Attribute_All data array method <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table 4 \u2013 Set_Attribute_All request service rules Table 5 \u2013 Example Set_Attribute_All attribute ordering method Table 6 \u2013 Example Set_Attribute_All data array method <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 3.6 Conventions used in state machines Figure 3 \u2013 Example of an STD <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 4 Abstract syntax 4.1 FAL PDU abstract syntax Table 7 \u2013 State event matrix format Table 8 \u2013 Example state event matrix <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 9 \u2013 UCMM_PDU header format Table 10 \u2013 UCMM command codes <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table 11 \u2013 Transport class 0 header <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table 12 \u2013 Transport class 1 header Table 13 \u2013 Transport class 2 header Table 14 \u2013 Transport class 3 header Table 15 \u2013 Classes 4 to 6 header format <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 16 \u2013 Real-time data header \u2013 exclusive owner <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table 17 \u2013 Real-time data header\u2013 redundant owner <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table 18 \u2013 Forward_Open request format <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Table 19 \u2013 Forward_Open_Good response format Table 20 \u2013 Forward_Open_Bad response format <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 21 \u2013 Large_Forward_Open request format <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Table 22 \u2013 Large_Forward_Open_Good response format Table 23 \u2013 Large_Forward_Open_Bad response format <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 24 \u2013 Forward_Close request format Table 25 \u2013 Forward_Close_Good response format <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 26 \u2013 Forward_Close_Bad response format <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table 27 \u2013 Unconnected_Send request format Table 28 \u2013 Unconnected_Send_Good response format <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table 29 \u2013 Unconnected_Send_Bad response format Table 30 \u2013 Get_Connection_Data request format <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table\u00a031 \u2013 Get_Connection_Data response format Table 32 \u2013 Search_Connection_Data request format <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 33 \u2013 Get_Object_Owner request format Table 34 \u2013 Forward_Open_Good response format <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 4 \u2013 Network connection parameters <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 5 \u2013 Time tick Table 35 \u2013 Time-out multiplier Table 36 \u2013 Time tick units <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Figure 6 \u2013 Connection establishment time-out <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 37 \u2013 Selection of connection ID Table 38 \u2013 Transport class, trigger and Is_Server format <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table 39 \u2013 MR_Request_Header format Table\u00a040 \u2013 MR_Response_Header format <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 41 \u2013 Structure of Get_Attribute_All_ResponsePDU body Table 42 \u2013 Structure of Set_Attribute_All_RequestPDU body Table 43 \u2013 Structure of Get_Attribute_List_RequestPDU body Table 44 \u2013 Structure of Get_Attribute_List_ResponsePDU body Table 45 \u2013 Structure of Set_Attribute_List_RequestPDU body <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 46 \u2013 Structure of Set_Attribute_List_ResponsePDU body Table 47 \u2013 Structure of Reset_RequestPDU body Table 48 \u2013 Structure of Reset_ResponsePDU body Table 49 \u2013 Structure of Start_RequestPDU body Table 50 \u2013 Structure of Start_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 51 \u2013 Structure of Stop_RequestPDU body Table 52 \u2013 Structure of Stop_ResponsePDU body Table 53 \u2013 Structure of Create_RequestPDU body Table 54 \u2013 Structure of Create_ResponsePDU body Table 55 \u2013 Structure of Delete_RequestPDU body Table 56 \u2013 Structure of Delete_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 57 \u2013 Structure of Get_Attribute_Single_ResponsePDU body Table 58 \u2013 Structure of Set_Attribute_Single_RequestPDU body Table 59 \u2013 Structure of Set_Attribute_Single_ResponsePDU body Table 60 \u2013 Structure of Find_Next_Object_Instance_RequestPDU body Table 61 \u2013 Structure of Find_Next_Object_Instance_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Table 62 \u2013 Structure of Apply_Attributes_RequestPDU body Table 63 \u2013 Structure of Apply_Attributes_ResponsePDU body Table 64 \u2013 Structure of Save_RequestPDU body Table 65 \u2013 Structure of Save_ResponsePDU body Table 66 \u2013 Structure of Restore_RequestPDU body Table 67 \u2013 Structure of Restore_ResponsePDU body <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 68 \u2013 Structure of Group_Sync_RequestPDU body Table 69 \u2013 Structure of Group_Sync_ResponsePDU body Table 70 \u2013 Identity object class attributes Table 71 \u2013 Identity object instance attributes <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 72 \u2013 Identity object bit definitions for status instance attribute <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 73 \u2013 Bits 4 \u2013 7 of status instance attribute Table 74 \u2013 Class level object\/service specific response data of Get_Attribute_All <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Table 75 \u2013 Instance level object\/service specific response data of Get_Attribute_All Table 76 \u2013 Modified instance level object\/service specific response data of Get_Attribute_All <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 77 \u2013 Object-specific parameter for Reset Table 78 \u2013 Message Router object class attributes Table 79 \u2013 Message Router object instance attributes <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 80 \u2013 Class level object\/service specific response data of Get_Attribute_All Table 81 \u2013 Instance level object\/service specific response data of Get_Attribute_All Table 82 \u2013 Assembly object class attributes Table 83 \u2013 Assembly object instance attributes <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table\u00a084 \u2013 Acknowledge Handler object class attributes <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 85 \u2013 Acknowledge Handler object instance attributes Table 86 \u2013 Structure of Add_AckData_Path_RequestPDU body Table 87 \u2013 Structure of Remove_AckData_Path_RequestPDU body <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 88 \u2013 Time Sync object instance attributes <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 89 \u2013 ClockIdentity encoding for different network implementations Table 90 \u2013 ClockClass values <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 91 \u2013 TimeAcuracy values Table 92 \u2013 TimePropertyFlags bit values <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 93 \u2013 TimeSource values Table 94 \u2013 Types of Clock Table 95 \u2013 Parameter object class attributes <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 96 \u2013 Parameter Class Descriptor bit values <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 97 \u2013 Parameter object instance attributes Table 98 \u2013 Semantics of Descriptor Instance attribute <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 99 \u2013 Minimum and Maximum Value semantics <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 100 \u2013 Scaling Formula attributes Table 101 \u2013 Scaling links <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 102 \u2013 Structure of Get_Enum_String_RequestPDU body Table 103 \u2013 Structure of Get_Enum_String_ResponsePDU body Table 104 \u2013 Enumerated strings Type versus Parameter data type <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table 105 \u2013 Connection Manager object class attributes Table 106 \u2013 Connection Manager object instance attributes <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 107 \u2013 Connection object class attributes <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table 108 \u2013 Connection object instance attributes <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Table 109 \u2013 Values assigned to the state attribute Table 110 \u2013 Values assigned to the instance_type attribute <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure 7 \u2013 Transport Class Trigger attribute Table 111 \u2013 Possible values within Direction Bit Table 112 \u2013 Possible values within Production Trigger Bits <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Table\u00a0113 \u2013 Possible values within Transport Class Bits <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Table 114 \u2013 Transport Class_Trigger attribute Table 115 \u2013 Values defined for the CP2\/3_produced_connection_id attribute <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Figure 8 \u2013 CP2\/3_initial_comm_characteristics attribute format Table 116 \u2013 Values defined for the CP2\/3_consumed_connection_id attribute <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 117 \u2013 Values for the Initial Production Characteristics nibble <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 118 \u2013 Values for the Initial Consumption Characteristics nibble <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 119 \u2013 Values for the watchdog_timeout_action <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 120 \u2013 Structure of Connection_Bind_RequestPDU body <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table 121 \u2013 Object specific status for Connection_Bind service Table 122 \u2013 Structure of Producing_Application_Lookup_RequestPDU body Table 123 \u2013 Structure of Producing_Application_Lookup_ResponsePDU body Table 124 \u2013 Producing_Application_Lookup Service status codes <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 9 \u2013 Segment type <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Figure 10 \u2013 Port segment Table 125 \u2013 Possible port segment examples <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table 126 \u2013 TCP\/IP link address examples <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure 11 \u2013 Logical segment encoding <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 127 \u2013 Electronic key segment format <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 128 \u2013 Logical segments examples Table 129 \u2013 Network segments <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure 12 \u2013 Extended network segment Table 130 \u2013 Extended subtype definitions Table 131 \u2013 Data segment <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table 132 \u2013 ANSI_Extended_Symbol segment Table 133 \u2013 Addressing categories <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 134 \u2013 Class code ID ranges Table 135 \u2013 Attribute ID ranges Table 136 \u2013 Service code ranges <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table 137 \u2013 Class codes Table 138 \u2013 Reserved class attributes for all object class definitions <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table 139 \u2013 Common services list <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table 140 \u2013 Acknowledge Handler object specific services list Table 141 \u2013 Parameter object specific services list Table 142 \u2013 Services specific to Connection Manager Table 143 \u2013 Services specific to Connection object <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table 144 \u2013 Device type numbering <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table 145 \u2013 Connection Manager service request error codes <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Table 146 \u2013 General status codes <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 147 \u2013 Identity object status codes <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 4.2 Data abstract syntax specification <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 4.3 Encapsulation abstract syntax Figure 13 \u2013 Encapsulation message <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | Table 148 \u2013 Encapsulation header Table 149 \u2013 Encapsulation command codes <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Table 150 \u2013 Encapsulation status codes <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table 151 \u2013 Options flags Table 152 \u2013 Nop request encapsulation header Table 153 \u2013 RegisterSession request encapsulation header <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | Table 154 \u2013 RegisterSession request data portion Table 155 \u2013 Options flags Table 156 \u2013 RegisterSession reply encapsulation header Table 157 \u2013 RegisterSession reply data portion <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table 158 \u2013 UnRegisterSession request encapsulation header Table 159 \u2013 ListServices request encapsulation header <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Table 160 \u2013 ListServices reply encapsulation header Table 161 \u2013 ListServices reply data portion Table 162 \u2013 Service type codes Table 163 \u2013 Communications capability flags <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table 164 \u2013 ListIdentity request encapsulation header Table 165 \u2013 ListIdentity reply encapsulation header <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Table 166 \u2013 ListIdentity reply data portion Table 167 \u2013 ListInterfaces request encapsulation header <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Table 168 \u2013 ListInterfaces reply encapsulation header Table 169 \u2013 SendRRData request encapsulation header Table 170 \u2013 SendRRData request data portion <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Table 171 \u2013 SendRRData reply encapsulation header Table 172 \u2013 SendUnitData request encapsulation header <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Table 173 \u2013 SendUnitData request data portion Table 174 \u2013 Common packet format Table 175 \u2013 Address and data item structure Table 176 \u2013 Address type ID\u2019s <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table 177 \u2013 Data type ID\u2019s Table 178 \u2013 Null address type Table 179 \u2013 Connected address type <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table 180 \u2013 Sequenced address type Table 181 \u2013 UCMM data type Table 182 \u2013 Connected data type Table 183 \u2013 Sockaddr info items <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | 5 Transfer syntax 5.1 Compact encoding <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Table 184 \u2013 BOOLEAN encoding Table 185 \u2013 Example compact encoding of a BOOL value Table 186 \u2013 Encoding of SignedInteger values Table 187 \u2013 Example compact encoding of a SignedInteger value Table 188 \u2013 UnsignedInteger values <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Table 189 \u2013 Example compact encoding of an UnsignedInteger Table 190 \u2013 FixedLengthReal values Table 191 \u2013 Example compact encoding of a REAL value Table 192 \u2013 Example compact encoding of a LREAL value Table 193 \u2013 FixedLengthReal values <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table 194 \u2013 STRING value Table 195 \u2013 STRING2 value Table 196 \u2013 STRINGN value Table 197 \u2013 SHORT_STRING value Table 198 \u2013 Example compact encoding of a STRING value <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure 14 \u2013 FixedLengthBitString compact encoding bit placement rules Figure 15 \u2013 Example compact encoding of a SWORD FixedLengthBitString Figure 16 \u2013 Example compact encoding of a WORD FixedLengthBitString Table 199 \u2013 Example compact encoding of STRING2 value Table 200 \u2013 SHORT_STRING type <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Figure 17 \u2013 Example compact encoding of a DWORD FixedLengthBitString Figure 18 \u2013 Example compact encoding of a LWORD FixedLengthBitString Table\u00a0201 \u2013 Example compact encoding of a single dimensional ARRAY <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Table 202 \u2013 Example compact encoding of a multi\u00addimensional ARRAY Table 203 \u2013 Example compact encoding of a STRUCTURE <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 5.2 Data type reporting <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Table 204 \u2013 Identification codes and descriptions of elementary data types <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Figure 19 \u2013 Example 2 of formal encoding of a structure type specification Table 205 \u2013 Example 1 of formal encoding of a structure type specification <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Figure 20 \u2013 Example of abbreviated encoding of a structure type specification Figure 21 \u2013 Example 1 of formal encoding of an array type specification <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Figure 22 \u2013 Example 2 of formal encoding of an array type specification Figure 23 \u2013 Example 1 of abbreviated encoding of an array type specification <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | 6 Structure of FAL protocol state machines 7 AP-Context state machine 7.1 Overview 7.2 Connection object state machine Figure 24 \u2013 Example 2 of abbreviated encoding of an array type specification <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Figure 25 \u2013 I\/O Connection object state transition diagram Table 206 \u2013 I\/O Connection state event matrix <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Figure 26 \u2013 Bridged Connection object state transition diagram <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Table 207 \u2013 Bridged Connection state event matrix <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Figure 27 \u2013 Explicit Messaging Connection object state transition diagram <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table 208 \u2013 Explicit Messaging Connection state event matrix <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | 8 FAL service protocol machine (FSPM) 8.1 General 8.2 Primitive definitions <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | Table 209 \u2013 Primitives issued by FAL user to FSPM <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Table\u00a0210 \u2013 Primitives issued by FAL user to FSPM <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | 8.3 Parameters of primitives Table 211 \u2013 Primitives issued by FSPM to FAL user <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | 8.4 FSPM state machines Table 212 \u2013 Parameters used with primitives exchanged between FAL user and FSPM <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | 9 Application relationship protocol machines (ARPMs) 9.1 General 9.2 Connection-less ARPM (UCMM) <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Table 213 \u2013 Primitives issued by FSPM to ARPM Table 214 \u2013 Primitives issued by ARPM to FSPM <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | Table 215 \u2013 Parameters used with primitives exchanged between FSPM and ARPM Table 216 \u2013 UCMM client states <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Figure 28 \u2013 State transition diagram of UCMM client Table 217 \u2013 State event matrix of UCMM client <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Figure 29 \u2013 State transition diagram of high\u2013end UCMM server Table\u00a0218 \u2013 High-end UCMM server states <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table 219 \u2013 State event matrix of high-end UCMM server <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Figure 30 \u2013 State transition diagram of low\u2013end UCMM server Table 220 \u2013 Low-end UCMM server states <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table 221 \u2013 State event matrix of low\u2013end UCMM server <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Figure 31 \u2013 Sequence diagram for a UCMM with one outstanding message <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Figure\u00a032 \u2013 Sequence diagram for a UCMM with multiple outstanding messages <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | 9.3 Connection-oriented ARPMs (transports) Figure 33 \u2013 TPDU buffer Table 222 \u2013 Notification <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table\u00a0223 \u2013 Transport classes Table 224 \u2013 Primitives issued by FSPM to ARPM <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table 225 \u2013 Primitives issued by ARPM to FSPM Table 226 \u2013 Parameters used with primitives exchanged between FSPM and ARPM <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Figure 34 \u2013 Data flow diagram using a client transport class 0 and server transport class 0 Figure 35 \u2013 Sequence diagram of data transfer using transport class 0 <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Figure 36 \u2013 Class 0 client STD Table\u00a0227 \u2013 Class 0 transport client states Table 228 \u2013 Class 0 client SEM <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Figure 37 \u2013 Class 0 server STD Table\u00a0229 \u2013 Class 0 transport server states Table 230 \u2013 Class 0 server SEM <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Figure 38 \u2013 Data flow diagram using client transport class 1 and server transport class\u00a01 <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Figure 39 \u2013 Sequence diagram of data transfer using client transport class 1 and server transport class 1 <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Table\u00a0231 \u2013 Class 1 transport client states <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Figure 40 \u2013 Class 1 client STD Table 232 \u2013 Class 1 client SEM <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Figure 41 \u2013 Class 1 server STD Table\u00a0233 \u2013 Class 1 transport server states <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Table 234 \u2013 Class 1 server SEM <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Figure 42 \u2013 Data flow diagram using client transport class 2 and server transport class\u00a02 <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Figure 43 \u2013 Diagram of data transfer using client transport class 2 and server transport class 2 without returned data <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Figure 44 \u2013 Sequence diagram of data transfer using client transport class 2 and server transport class 2 with returned data <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Figure 45 \u2013 Class 2 client STD Table\u00a0235 \u2013 Class 2 transport client states <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table 236 \u2013 Class 2 client SEM <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Figure 46 \u2013 Class 2 server STD Table\u00a0237 \u2013 Class 2 transport server states <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Table 238 \u2013 Class 2 server SEM <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Figure 47 \u2013 Data flow diagram using client transport class\u00a03 and server transport class\u00a03 <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Figure 48 \u2013 Sequence diagram of data transfer using client transport class 3 and server transport class 3 without returned data <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | Figure 49 \u2013 Sequence diagram of data transfer using client transport class 3 and server transport class 3 with returned data <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Table\u00a0239 \u2013 Class 3 transport client states <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | Figure 50 \u2013 Class\u00a03 client STD Table 240 \u2013 Class\u00a03 client SEM <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | Table\u00a0241 \u2013 Class 3 transport server states <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Figure 51 \u2013 Class\u00a03 server STD <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Table 242 \u2013 Class\u00a03 server SEM <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Figure 52 \u2013 Data flow diagram using transport classes 4 and 5 <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Figure 53 \u2013 Sequence diagram of message exchange using transport classes 4 and 5 Table 243 \u2013 Write and trigger events in class\u00a04 and 5 transport <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Figure 54 \u2013 Sequence diagram of messages overwriting each other <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | Figure 55 \u2013 Sequence diagram of queued message exchange using transport classes 4 and 5 Figure 56 \u2013 Sequence diagram of retries using transport classes 4 and 5 <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Figure 57 \u2013 Sequence diagram of idle traffic using transport classes 4 and 5 <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Figure 58 \u2013 Classes\u00a04 and 5 basic structure <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Figure 59 \u2013 Class\u00a06 basic structure Table\u00a0244 \u2013 Common states for transport classes 4 to 6 <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Figure 60 \u2013 Classes 4 to 6 general STD Table 245 \u2013 Classes 4 to 6 general SEM <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Figure 61 \u2013 Class\u00a04 sender STD Table\u00a0246 \u2013 Class 4 transport sender states <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | Table 247 \u2013 Class\u00a04 sender SEM <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Table\u00a0248 \u2013 Class 4 transport receiver states <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Figure 62 \u2013 Class\u00a04 receiver STD <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Table 249 \u2013 Class\u00a04 receiver SEM <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | Figure 63 \u2013 Sequence diagram of three fragments using transport class\u00a05 <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Figure 64 \u2013 Sequence diagram of fragmentation with retries using transport class\u00a05 Figure 65 \u2013 Sequence diagram of two fragments using transport class\u00a05 <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | Figure 66 \u2013 Sequence diagram of aborted message using transport class\u00a05 <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | Figure 67 \u2013 Class\u00a05 sender STD Table\u00a0250 \u2013 Class 5 transport sender states <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | Table 251 \u2013 Class\u00a05 sender SEM <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | Figure 68 \u2013 Class\u00a05 receiver STD Table\u00a0252 \u2013 Class 5 transport receiver states <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | Table 253 \u2013 Class\u00a05 receiver SEM <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Figure 69 \u2013 Data flow diagram for transport class\u00a06 <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | Figure 70 \u2013 Sequence diagram of message exchange using transport class 6 Figure 71 \u2013 Sequence diagram of retries using transport class 6 <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Figure 72 \u2013 Sequence diagram of idle traffic using transport class 6 <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Figure 73 \u2013 Sequence diagram of request overwriting null Figure 74 \u2013 Sequence diagram of response overwriting ACK of null <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Figure 75 \u2013 Sequence diagram of three fragments using transport class\u00a06 <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | Figure 76 \u2013 Sequence diagram of fragmentation with retries using transport class\u00a06 Figure 77 \u2013 Sequence diagram of two fragments using transport class 6 <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Figure 78 \u2013 Sequence diagram of aborted fragmented sequence using transport class\u00a06 <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | Figure 79 \u2013 Class\u00a06 client STD Table\u00a0254 \u2013 Class 6 transport client states <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Table 255 \u2013 Class\u00a06 client state event matrix <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | Table\u00a0256 \u2013 Class 6 transport server states <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | Figure 80 \u2013 Class\u00a06 server STD <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Table 257 \u2013 Class\u00a06 server SEM <\/td>\n<\/tr>\n | ||||||
250<\/td>\n | 10 DLL mapping protocol machine 1 (DMPM 1) 10.1 General 10.2 Link producer Figure 81 \u2013 Data flow diagram for a link producer and consumer <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | 10.3 Link consumer 10.4 Primitive definitions Table 258 \u2013 Primitives issued by ARPM to DMPM Table 259 \u2013 Primitives issued by DMPM to ARPM Table 260 \u2013 Parameters used with primitives exchanged between ARPM and DMPM <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Table 261 \u2013 Primitives exchanged between data-link layer and DMPM Table 262 \u2013 Parameters used with primitives exchanged between DMPM and Data-link <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | 10.5 DMPM state machine Figure 82 \u2013 State transition diagram for a link producer Table 263 \u2013 Link producer states Table 264 \u2013 State event matrix of link producer <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | 10.6 Data-link Layer service selection 11 DLL mapping protocol machine 2 (DMPM 2) 11.1 General Figure 83 \u2013 State transition diagram for a link consumer Table 265 \u2013 Link consumer states Table 266 \u2013 State event matrix of link consumer <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 11.2 Mapping of UCMM PDUs <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | Table 267 \u2013 Network Connection ID selection <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Table 268 \u2013 Example multicast assignments <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 11.3 Mapping of transport class 0 and class 1 PDUs Table 269 \u2013 UDP data format for class 0 and class 1 <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | 11.4 Mapping of transport class 2 and class 3 PDU\u2019s 11.5 Mapping of transport classes 4 to 6 11.6 IGMP Usage <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | 11.7 Quality of Service (QoS) for CP\u00a02\/2 messages <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | Figure 84 \u2013 DS field in the IP header Figure 85 \u2013 IEEE\u00a0802.1Q tagged frame Table 270 \u2013 Default DSCP and IEEE\u00a0802.1D mapping <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | 11.8 Management of an encapsulation session <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | 12 DLL mapping protocol machine 3 (DMPM 3) <\/td>\n<\/tr>\n | ||||||
267<\/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 |