BS EN 61158-5-10:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 10 elements
Published By | Publication Date | Number of Pages |
BSI | 2012 | 774 |
IEC 61158-5-10:2010(E) specifies the structure and services of the type 10 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main change with respect to the previous edition are: – corrections; – improvements; – optimization of the synchronization; – optimization of the startup time from power down.
PDF Catalog
PDF Pages | PDF Title |
---|---|
8 | CONTENTS |
20 | INTRODUCTION |
21 | 1 Scope 1.1 Overview |
22 | 1.2 Specifications 1.3 Conformance 2 Normative references |
24 | 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Referenced terms and definitions |
25 | 3.2 Additional terms and definitions for distributed automation |
27 | 3.3 Additional terms and definitions for decentralized periphery |
35 | 3.4 Additional terms and definitions for media redundancy |
36 | 3.5 Abbreviations and symbols |
37 | 3.6 Additional abbreviations and symbols for distributed automation 3.7 Additional abbreviations and symbols for decentralized periphery |
38 | 3.8 Additional abbreviations and symbols for media redundancy 3.9 Conventions |
41 | 4 Concepts 5 Data type ASE 5.1 General |
42 | Figures Figure 1 – Data type class hierarchy example |
44 | 5.2 Formal definition of data type objects |
45 | 5.3 FAL defined data types |
46 | Tables Table 1 – V2 octets Table 2 – L2 octets |
49 | Table 3 – PERSISTDEF Table 4 – VARTYPE |
50 | Table 5 – ITEMQUALITYDEF |
52 | Table 6 – STATEDEF Table 7 – GROUPERRORDEF |
54 | Table 8 – ACCESSRIGHTSDEF Table 9 – HRESULT |
56 | Table 10 – E2 octets |
57 | Table 11 – E2 value range Table 12 – Unipolar2.16 octets Table 13 – Unipolar2.16 value range |
59 | Table 14 – N2 value range Table 15 – N4 value range |
60 | Table 16 – X2 value range |
61 | Table 17 – X4 value range Table 18 – C4 value range |
63 | Table 19 – T2 value range Table 20 – T2 value range |
64 | Table 21 – D2 value range Table 22 – R2 value range |
65 | Table 23 – UUID for decentralized peripherals |
66 | Table 24 – UUID for distributed automation |
67 | Figure 2 – NetworkTime date relation Table 25 – NetworkTime values Table 26 – NetworkTime octets |
69 | Table 27 – UNICODEString values Table 28 – UTF-8 character encoding scheme |
80 | Table 29 – OctetString2+Unsigned8 octets |
81 | Table 30 – Float32+Unsigned8 octets Table 31 – Unsigned8+Unsigned8 octets |
84 | Table 32 – Data Types for Value in a VARIANT |
85 | Table 33 – Unsigned16_S octets Table 34 – Unsigned16_S meaning Table 35 – Integer16_S octets |
86 | Table 36 – Integer16_S meaning Table 37 – Unsigned8_S octets Table 38 – Unsigned8_S meaning |
87 | Table 39 – OctetString_S octets Table 40 – OctetString_S status bits Table 41 – F message trailer with 4 octets |
88 | 5.4 Data type ASE service specification 6 Communication model for common services 6.1 Concepts 6.2 ASE data types Table 42 – F message trailer with 5 octets |
89 | 6.3 ASEs |
94 | Table 43 – Get |
96 | Table 44 – Set |
99 | Table 45 – Identify |
100 | Table 46 – Hello |
102 | Figure 3 – PTCP applications |
107 | Table 47 – Start bridge |
108 | Table 48 – Start slave |
109 | Table 49 – Start master |
110 | Table 50 – Stop bridge |
111 | Table 51 –Stop slave Table 52 – Stop master |
112 | Table 53 – Sync state change |
113 | Figure 4 – Clock drift measurement |
114 | Figure 5 – Multiple synchronization |
116 | Figure 6 – MRP stack |
121 | Table 54 – Start MRM |
122 | Table 55 – Stop MRM |
123 | Table 56 – Redundancy state change |
124 | Table 57 – Start MRC |
125 | Table 58 – Stop MRC Table 59 – Neighborhood changed |
127 | Figure 7 – Ring topology with one manager and clients Figure 8 – MRM in an open ring |
128 | Figure 9 – More than one MRM in the ring |
129 | Figure 10 – Media redundancy diagnosis dependencies |
130 | Table 60 – MRP network/connection parameters |
131 | Table 61 – MRM parameters Table 62 – MRC parameters |
132 | Table 63 – Set Prov Data |
133 | Table 64 – Set Prov Status |
134 | Table 65 – PPM Activate |
135 | Table 66 – Close Table 67 – Start |
136 | Table 68 – Error Table 69 – Get Cons Data |
137 | Table 70 – Get cons status Table 71 – Set RedRole |
138 | Table 72 – CPM activate |
142 | Table 73 – APMS Activate |
143 | Table 74 – APMR Activate |
144 | Table 75 – APMS A Data |
145 | Table 76 – APMR A Data Table 77 – APMR Ack |
146 | Table 78 – APMS Error Table 79 – APMS Error ERRCLS/ERRCODE |
147 | Table 80 – APMR Error Table 81 – APMR Error ERRCLS/ERRCODE Table 82 – APMS_Close |
148 | Table 83 – APMR_Close |
149 | Table 84 – Connect |
150 | Table 85 – Release |
151 | Table 86 – Read |
152 | Table 87 – Write |
153 | Table 88 – Control |
158 | Table 89 – System capabilities |
159 | Table 90 – Auto negotiation support and status Table 91 – MDI Power Support |
160 | Table 92 – Link aggregation status |
163 | Table 93 – Remote systems data change |
166 | Table 94 – Allowed values of ReductionRatio |
167 | Table 95 – Frame IDs for RT_CLASS_3 Table 96 – Sync Frame Table 97 – FrameSendOffset |
168 | Table 98 – Tx Port Entry |
169 | Figure 11 – Locating the destination for redundant RT frames |
171 | Table 99 – Port state change Table 100 – Set port state |
172 | Table 101 – Flush filtering data base Table 102 – IFW IRT Schedule Add |
173 | Table 103 – IFW IRT Schedule Remove Table 104 – IFW Schedule |
176 | Figure 12 – Example of periods at a local port |
178 | Table 105 – MAU type change Table 106 – Set MAU type |
181 | Table 107 – IP Multicast address Table 108 – Set ARP Cache |
183 | Table 109 – Enterprise number |
184 | Table 110 – Vendor OUI |
185 | Table 111 –IRT Schedule Add Table 112 – IRT Schedule Remove |
186 | Table 113 –Schedule Table 114 – N Data |
187 | Table 115 – A Data |
188 | Table 116 – C Data |
189 | 7 Communication model for distributed automation 7.1 Concepts |
191 | Figure 13 – FAL ASEs communication architecture |
192 | Figure 14 – Runtime object model |
193 | Figure 15 – Relationship between engineering and runtime |
194 | Figure 16 – Navigation in the runtime object model |
195 | 7.2 ASE data types |
196 | Table 117 – Connectable data types |
197 | Table 118 – Supported data types according to the Base Object Version |
199 | 7.3 ASEs Table 119 – Usage of character sets |
201 | Table 120 – QueryInterface (Unknown interface) |
202 | Table 121 – AddRef (Unknown interface) |
203 | Table 122 – Release (Unknown interface) |
204 | Table 123 – GetTypeInfoCount (Dispatch interface) |
205 | Table 124 – GetTypeInfo (Dispatch interface) |
206 | Table 125 – GetIDsOfNames (Dispatch interface) |
207 | Table 126 – Invoke (Dispatch interface) |
212 | Table 127 – CRC table for the PDev stamp calculation (hexadecimal values) |
213 | Table 128 – get_Producer (Physical device interface) |
214 | Table 129 – get_Product (Physical device interface) |
215 | Table 130 – get_SerialNo (Physical device interface) |
216 | Table 131 – get_ProductionDate (Physical device interface) |
217 | Table 132 – Revision (Physical device interface) |
218 | Table 133 – get_LogicalDevice (Physical device interface) |
219 | Table 134 – Type (Physical device interface) |
220 | Table 135 – PROFInetRevision (Physical device interface) |
221 | Table 136 – get_PDevStamp (Physical device interface) |
222 | Table 137 – get_Count (Browse interface) |
223 | Table 138 – BrowseItems (Browse interface) |
224 | Table 139 – get_Count2 (Browse interface) |
226 | Table 140 – BrowseItems2 (Browse interface) |
227 | Table 141 – Save (Persist interface) |
228 | Table 142 – Save2 (Persist interface) |
233 | Figure 17 – Operating state block diagram |
234 | Figure 18 – Device status model for the common diagnosis Table 143 – get_Name (Logical Device interface) |
235 | Table 144 – get_Producer (Logical Device interface) |
236 | Table 145 – get_Product (Logical Device interface) |
237 | Table 146 – get_SerialNo (Logical Device interface) |
238 | Table 147 – get_ProductionDate (Logical Device interface) |
239 | Table 148 – Revision (Logical Device interface) |
240 | Table 149 – get_ACCO (Logical Device interface) |
241 | Table 150 – get_RTAuto (Logical Device interface) |
242 | Table 151 – PROFInetRevision (Logical Device interface) |
243 | Table 152 – ComponentInfo (Logical Device interface) |
244 | Table 153 – get_State (State interface) |
246 | Table 154 – Activate (State interface) |
247 | Table 155 – Deactivate (State interface) |
248 | Table 156 – Reset (State interface) |
249 | Table 157 – AdviseState (State interface) |
250 | Table 158 – UnadviseState (State interface) |
251 | Table 159 – get_Time (Time interface) |
252 | Table 160 – put_Time (Time interface) |
253 | Table 161 – get_Count (Browse interface) |
254 | Table 162 – BrowseItems (Browse interface) |
255 | Table 163 – get_Count2 (Browse interface) |
257 | Table 164 – BrowseItems2 (Browse interface) |
258 | Table 165 – GroupError (Group error interface) |
260 | Table 166 – AdviseGroupError (Group Error interface) |
261 | Table 167 – UnadviseGroupError (Group Error interface) |
263 | Table 168 – PingFactor values |
265 | Figure 19 – ACCO ASE structure |
266 | Figure 20 – Productive operation of data connections |
272 | Table 169 – QoS subtypes in the ORPC communication channel |
273 | Table 170 – QoS subtypes in the RT communication channel Table 171 – QoS Types and Values |
275 | Table 172 – Epsilon value for connectable data types |
277 | Table 173 – Quality Codes |
278 | Figure 21 – Quality code transfer – standard behavior |
279 | Figure 22 – Startup of a connection Figure 23 – Quality code with communication fault |
280 | Figure 24 – Quality code when a connection is cleared Figure 25 – Quality code when a connection is deactivated |
281 | Figure 26 – Quality code during the transfer of “incorrect” connection data |
282 | Figure 27 – Quality code for provider in “CBAReady” state Figure 28 – Quality code when clearing an object from the provider |
283 | Figure 29 – Quality code when a connection is forced Figure 30 – Quality code at QoS violation |
285 | Table 174 – Quality code priority table |
290 | Figure 31 – Push mode |
291 | Figure 32 – Pull mode overview |
292 | Figure 33 – Detailed sequence chart of the pull mode |
293 | Figure 34 – QoS and ORPC communication channel |
294 | Figure 35 – QoS Violation within Pull Mode |
295 | Figure 36 – Monitoring the providers heartbeat Table 175 – Maximum ORPC substitute value apply time |
296 | Table 176 – Maximum GetConnectionData hold time |
297 | Figure 37 – State machine RemoteACCO Figure 38 – State machine RemoteACCOProvider |
298 | Figure 39 – State machine RemoteACCOProviderORPC Figure 40 – State machine ARORPC – Provider |
299 | Figure 41 – State machine GetConnectionData – Provider Figure 42 – State machine ProviderConnection |
300 | Figure 43 – State machine ProvConnActivation Figure 44 – State machine WorkerORPC |
301 | Figure 45 – Communication stack of distributed automation devices |
302 | Figure 46 – Application relations between devices Figure 47 – Communication relations |
303 | Table 177 – Usage of RT Variants |
304 | Figure 48 – RT communication channel Table 178 – Mapping QoS Value to RT cycle time |
305 | Table 179 – Maximum RT Substitute Value Apply Time |
306 | Figure 49 – Interaction between provider and consumer |
308 | Figure 50 – State machine ARSRT – Consumer |
309 | Figure 51 – State machine ARSRT – Provider |
310 | Figure 52 – State machine AccoDataCR – Consumer Figure 53 – State machine AccoDataCR – Provider |
311 | Figure 54 – RT frame layout |
312 | Figure 55 – Establishing an AccoDataCR |
313 | Figure 56 – Flowchart of the copy cycle for local connections |
317 | Figure 57 – State machine connect attempt |
324 | Figure 58 – Productive operation of data connections (ORPC channel) |
325 | Figure 59 – Productive operation of data connections (RT channel) Figure 60 – Productive operation of data connections (Local channel) |
326 | Figure 61 – Data flow for cyclic RT |
327 | Table 180 – Time Intervals and Timeouts |
328 | Figure 62 – Failure of the provider in productive operation (ORPC push mode) |
329 | Figure 63 – Failure of the provider in productive operation (ORPC pull mode) |
330 | Figure 64 – Scenario 1: Provider failure in productive operation (RT) |
331 | Figure 65 – Scenario 2: Recovery from provider failure in productive operation (RT) Figure 66 – Failure of the consumer (push mode) |
332 | Figure 67 – Failure of the consumer (pull mode) |
333 | Figure 68 – Failure of the consumer |
335 | Figure 69 – Failure of the provider when setting up connections |
336 | Figure 70 – Information levels Figure 71 – ACCO ASE status model for the common diagnosis |
337 | Figure 72 – ACCO ASE status model for the detailed diagnosis |
338 | Table 181 – Error codes for the ACCO ASE detailed diagnosis |
340 | Table 182 – AddConnections (ACCO Management interface) |
341 | Table 183 – RemoveConnections (ACCO Management interface) |
343 | Table 184 – ClearConnections (ACCO Management interface) |
344 | Table 185 – SetActivationState (ACCO Management interface) |
345 | Table 186 – GetInfo (ACCO Management interface) |
346 | Table 187 – GetIDs (ACCO Management interface) |
347 | Table 188 – GetConnections (ACCO Management interface) |
349 | Table 189 – ReviseQoS (ACCO Management interface) |
350 | Table 190 – get_PingFactor (ACCO Management interface) |
351 | Table 191 – put_PingFactor (ACCO Management interface) |
352 | Table 192 – get_CDBCookie (ACCO Management interface) |
353 | Table 193 – GetConsIDs (ACCO Management interface) |
354 | Table 194 – GetConsConnections (ACCO Management interface) |
355 | Table 195 – DiagConsConnections (ACCO Management interface) |
356 | Table 196 – GetProvIDs (ACCO Management interface) |
358 | Table 197 – GetProvConnections (ACCO Management interface) |
360 | Table 198 – GetDiagnosis (ACCO Management interface) |
362 | Table 199 – Request |
369 | Table 200 – Connect (ACCO Server interface) |
371 | Table 201 – Disconnect (ACCO Server interface) |
372 | Table 202 – DisconnectMe (ACCO Server interface) |
373 | Table 203 – SetActivation (ACCO Server interface) |
374 | Table 204 – Ping (ACCO Server interface) |
375 | Table 205 – Connect2 (ACCO Server interface) |
377 | Table 206 – GetConnectionData (ACCO Server interface) |
379 | Figure 73 – Structure of the transmitted connection data |
380 | Table 207 – OnDataChanged (ACCO Callback interface) Table 208 – Version |
381 | Table 209 – Flags |
382 | Table 210 – Gnip (ACCO Callback interface) |
383 | Table 211 – ReadItems (ACCO Sync interface) |
385 | Table 212 – WriteItems (ACCO Sync interface) |
387 | Table 213 – WriteItemsQCD (ACCO Sync interface) |
388 | Table 214 – GroupError (Group Error interface) |
389 | Table 215 – AdviseGroupError (Group Error interface) |
390 | Table 216 – UnadviseGroupError (Group Error interface) |
392 | Table 217 – ConnectCR (ACCO Server SRT interface) |
394 | Table 218 – DisconnectCR (ACCO Server SRT interface) |
395 | Table 219 – Connect (ACCO Server SRT interface) |
396 | Table 220 – Disconnect (ACCO Server SRT interface) |
398 | Table 221 – DisconnectMe (ACCO Server SRT interface) |
399 | Table 222 – SetActivation (ACCO Server SRT interface) |
404 | Table 223 – Hresult values for access to properties of Custom RT-Auto objects |
405 | Table 224 – Hresult values for access to properties of the System RT-Auto object Table 225 – Common hresult values on access to properties of RT-Auto objects Table 226 – Quality code for access to properties of Custom RT-Auto objects |
406 | Table 227 – Quality code for access to properties of the System RT-Auto object Table 228 – get_Name (RT-Auto interface) |
407 | Table 229 – Revision (RT-Auto interface) |
408 | Table 230 – ComponentInfo (RT-Auto interface) |
409 | Table 231 – get_Count (Browse interface) |
410 | Table 232 – BrowseItems (Browse interface) |
412 | Table 233 – get_Count2 (Browse interface) |
413 | Table 234 – BrowseItems2 (Browse interface) |
415 | Table 235 – get_StateCollection (System properties interface) |
416 | 7.4 ARs Table 236 – get_StampCollection (System Properties interface) |
418 | Table 237 – CoCreateInstance |
419 | Table 238 – CoDisconnectObject Table 239 – Call |
420 | 7.5 Summary of FAL classes Table 240 – Distributed automation FAL class summary |
421 | 7.6 Summary of FAL services Table 241 – Assignment of the services to client and server |
423 | 8 Communication model for decentralized periphery 8.1 Concepts |
424 | Table 242 – Requirements and features |
425 | Figure 74 – Example of communication between controlling devices and field devices Figure 75 – Example of communication between an engineering station and several controlling and field devices |
426 | Figure 76 – Example of communication between field devices and a server station Figure 77 – Example of communication between field devices |
428 | Figure 78 – Structural units of one arbitrary API of an IO device (general) |
429 | Figure 79 – Example 1 structural units for interfaces and ports within API 0 |
430 | Figure 80 – Example 2 structural units for interfaces and ports within API 0 |
432 | Figure 81 – Overview of application processes |
433 | Figure 82 – IO device with APs, slots and subslots |
436 | Figure 83 – Application Process with application process objects (APOs) |
437 | Figure 84 – Access to a remote APO |
438 | Figure 85 – Access to a remote APO for provider/consumer association |
439 | Figure 86 – Example of one AR with two AREPs |
440 | 8.2 ASE data types 8.3 ASEs |
441 | Figure 87 – Relation of a record data object to one real object |
442 | Figure 88 – Relation of a record data object to two real objects |
444 | Table 243 – Persistence behavior for record data objects |
445 | Table 244 – Read |
447 | Table 245 – Read Query |
449 | Table 246 – Write |
452 | Figure 89 – Overview IO ASE service interactions |
459 | Table 247 – Set input |
460 | Table 248 – Set Input IOCS |
461 | Table 249 – Get Input |
462 | Table 250 – Get Input IOCS |
463 | Table 251 – New Input |
464 | Table 252 – Set input APDU data status |
465 | Table 253 – New Input APDU Data Status |
466 | Table 254 – Read Input Data |
468 | Table 255 – Set Output |
469 | Table 256 – Set Output IOCS |
470 | Table 257 – Get Output |
471 | Table 258 – Get Output IOCS |
472 | Table 259 – New Output |
473 | Table 260 – Set Output APDU Data Status |
474 | Table 261 – New Output APDU Data Status |
475 | Table 262 – Read Output Data |
478 | Table 263 – Read Output Substitute Data |
480 | Table 264 – Write Output Substitute Data |
484 | Table 265 – Read Logbook |
485 | Table 266 – Logbook Event |
489 | Table 267 – Dependencies within channel properties |
492 | Table 268 – Ext Channel Error type |
493 | Table 269 – Ext Channel Add Value for Accumulative Info |
494 | Table 270 – Dependencies within Channel Properties for manufacturer specific diagnosis |
495 | Table 271 – Read Device Diagnosis |
497 | Table 272 – Diagnosis Item |
503 | Table 273 – Diagnosis Event |
506 | Table 274 – State table Diagnosis entry |
507 | Table 275 – Functions used in state tables |
508 | Table 276 – State table maintenance required entry |
509 | Table 277 – State table maintenance demanded entry |
510 | Table 278 – State table qualified entry |
515 | Table 279 – Alarm type |
516 | Table 280 – Channel Diagnosis Table 281 – Manufacturer Specific Diagnosis Table 282 – Submodule Diagnosis State |
517 | Table 283 – AR Diagnosis State |
518 | Table 284 – User Structure Identifier |
519 | Table 285 – Semantics of Specifier |
523 | Table 286 – Alarm Notification |
527 | Table 287 – Alarm Ack |
528 | Figure 90 – Example of a resource model at the alarm source |
533 | Table 288 – Module State |
535 | Table 289 – Usage with respect to CR type |
536 | Table 290 – Detail |
537 | Table 291 – ARInfo Table 292 – Ident Info |
543 | Table 293 – Connect |
551 | Table 294 – Connect Device Access |
553 | Table 295 – Release |
554 | Table 296 – Abort Table 297 – End Of Parameter |
555 | Table 298 – Application Ready |
557 | Table 299 – Ready For Companion |
558 | Table 300 – Read Expected Identification |
561 | Table 301 – Read Real Identification |
564 | Table 302 – Read Identification Difference |
566 | Table 303 – Read AP Data |
567 | Table 304 – Read I&M0 Filter Data |
571 | Table 305 – Read I&M0 Data |
573 | Table 306 – Write I&M1 Data |
575 | Table 307 – Read I&M1 Data |
577 | Table 308 – Write I&M2 Data |
579 | Table 309 – Read I&M2 Data |
581 | Table 310 – Write I&M3 Data |
583 | Table 311 – Read I&M3 Data |
585 | Table 312 – Write I&M4 Data |
587 | Table 313 – Read I&M4 Data |
592 | Figure 91 – General isochronous application model (example) |
593 | Table 314 – Write IsoM Data |
595 | Table 315 – Read IsoM Data |
597 | Table 316 – SYNCH Event |
598 | Figure 92 – ASE relations in an IO device operating in isochronous mode Figure 93 – State machine relations in an IO device operating in isochronous mode |
600 | Table 317 – Primitives issued by the AL to the SyncCtl state machine Table 318 – Primitive issued by the SyncCtl state machine to the user Table 319 – Primitives issued by the Input state machine to the user Table 320 – Primitive issued by the Output state machine to the user Table 321 – Primitives issued by the SyncCtl to the output state machine |
601 | Table 322 – Primitives issued by the output to the SyncCtl state machine Table 323 – Primitives issued by the SyncCtl to the input state machine Table 324 – Primitives issued by the output state machine to the AL Table 325 – Primitives issued by the AL to the output state machine |
602 | Figure 94 – SyncCtl state diagram Table 326 – Primitives issued by the input state machine to the AL Table 327 – Primitives issued by the AL to the input state machine |
603 | Table 328 – SyncCtl state table |
604 | Figure 95 – Output state diagram |
605 | Table 329 – Output state table |
609 | Figure 96 – Input state diagram |
610 | Table 330 – Input state table |
615 | Table 331 – Subslot number for interface submodules |
616 | Table 332 – Subslot number for port submodules |
618 | Table 333 – Subslot Number for Interface Submodules Table 334 – Subslot Number for Sync Interface Submodules |
619 | Table 335 – Sync Properties Role |
620 | Table 336 – Sync Class Table 337 – Fiber Optic Types |
621 | Table 338 – Fiber Optic Cable Types |
625 | Table 339 – Write Expected Port Data |
628 | Table 340 – Write Adjusted Port Data |
630 | Table 341 – Read real port data |
633 | Table 342 – Read Expected Port Data |
635 | Table 343 – Read Adjusted Port Data |
638 | Table 344 – Write IR Data |
642 | Table 345 – Read IR Data |
646 | Table 346 – Write Sync Data |
649 | Table 347 – Read Real Sync Data |
652 | Table 348 – Read Expected Sync Data |
655 | Table 349 – Read PDev Data |
660 | Table 350 – Sync State Info |
662 | Table 351 – Write Fiber Optic Data |
665 | Table 352 – Read Real Fiber Optic Data |
667 | Table 353 – Write MRP Interface Data |
670 | Table 354 – Read MRP Interface Data |
672 | Table 355 – Write MRP Port Data |
674 | Table 356 – Read MRP Port Data |
676 | Table 357 – Write FSU Data |
678 | Table 358 – Read FSU Data |
680 | Table 359 – Write Network Component Data |
683 | Table 360 – Read Network Component Data |
685 | Table 361 – Read Real Interface Data |
689 | Table 362 – Set Time |
691 | Figure 97 – Assignment of communication relationship to application relationship |
695 | Figure 98 – Implicit application relationship |
696 | Figure 99 – Example IO application relationship (one-to-one) |
697 | Figure 100 – Example IO application relationship one-to-many |
700 | Table 363 – Device Access Table 364 – Companion AR |
704 | Table 365 – Media Redundancy |
705 | Table 366 – Frame ID |
710 | Table 367 – Read AR Data |
713 | 8.4 Behavior of an IO device Figure 101 – Overview ASE state machines for IO device |
715 | Figure 102 – State diagram application startup IO device |
716 | Table 368 – State table application startup IO device |
722 | Table 369 – State table functions for startup IO device |
723 | Figure 103 – State diagram neighborhood check |
724 | Table 370 – State table neighborhood check |
731 | Table 371 – State table functions for neighborhood check |
732 | Figure 104 – State diagram PD parameter check IO device Table 372 – State table PD parameter check IO device |
737 | Table 373 – State table functions PD parameter check IO device |
738 | Table 374 – State table fiber optic maintenance required |
739 | Table 375 – State table fiber optic maintenance demanded |
740 | Table 376 – State table fiber optic diagnosis |
742 | Figure 105 – State diagram for a submodule Table 377 – State table for a submodule |
752 | Table 378 – State table for plug |
754 | Table 379 – State table for pull |
755 | Table 380 – State table of PTCP behavior |
756 | Table 381 – Functions used by PTCP behavior |
757 | 8.5 Behavior of an IO controller |
758 | Figure 106 – State diagram IO controller during startup |
759 | Table 382 – State table IO controller during startup |
760 | 8.6 Application characteristics Table 383 – Functions used by state table IO controller |
761 | Figure 107 – Example of network topology including slower wireless segments |
762 | Figure 108 – Example of media redundancy including wireless segments |
763 | Annex A (informative) Device instances Figure A.1 – Instance model |
765 | Annex B (informative) Components of an Ethernet interface Figure B.1 – Scheme of an Ethernet interface |
766 | Figure B.2 – Scheme of an Ethernet interface with bridging ability |
767 | Figure B.3 – Scheme of an Ethernet interface with optical ports |
768 | Figure B.4 – Scheme of an Ethernet interface with bridging ability using radio communication Figure B.5 – Scheme of an Ethernet interface with radio communication |
769 | Annex C (informative) Scheme of MAC address assignment Figure C.1 – Scheme of MAC address assignment |
770 | Annex D (informative) Collection of objects Figure D.1 – Example for an intersection of IO device, slot, and AR |
771 | Annex E (informative) Measurement of the fast startup time Figure E.1 – Measurement of the fast startup time |
772 | Bibliography |