This part of IEC 61158 provides common elements for basic time-critical messaging communications between devices in an automation environment. 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 standard defines in an abstract way the externally visible service provided by the Type 12 fieldbus data-link layer in terms of<\/p>\n
the primitive actions and events of the service;<\/p>\n<\/li>\n
the parameters associated with each primitive action and event, and the form which they take;<\/p>\n<\/li>\n
the interrelationship between these actions and events, and their valid sequences.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this standard is to define the services provided to<\/p>\n
the Type 12 fieldbus application layer at the boundary between the application and data-link layers of the fieldbus reference model;<\/p>\n<\/li>\n
systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 1.1 Overview 1.2 Specifications 1.3 Conformance <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 2 Normative references 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 3.3 Data-link service terms and definitions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 3.4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 3.5 Common conventions <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4 Data-link layer services and concepts 4.1 Operating principle <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 4.2 Topology 4.3 Data-link layer overview Figure 1 \u2013 Mapping of logical data in an Ethernet frame consisting of a single Type\u00a012 DLPDU <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 4.4 Error detection overview 4.5 Parameter and process data handling introduction 4.6 Node reference model Figures <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.7 Operation overview Figure 2 \u2013 Type\u00a012 data-link reference model <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Figure 3 \u2013 Type\u00a012 segments in open mode Figure 4 \u2013 Type\u00a012 segment in direct mode <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 4.8 Addressing Figure 5 \u2013 Addressing mode overview <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Figure 6 \u2013 Fieldbus memory management unit overview <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 4.9 Slave classification 4.10 Structure of the communication layer in the slave <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 5 Communication services 5.1 Overview Figure 7 \u2013 Layering of communication <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5.2 Read services Figure 8 \u2013 Flow of Type\u00a012 service primitives Table 1 \u2013 Auto-increment physical read (APRD) <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Tables Table 2 \u2013 Configured-addresse physical read (FPRD) <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Table 3 \u2013 Broadcast read (BRD) Table 4 \u2013 Logical read (LRD) <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 5.3 Write services Table 5 \u2013 Auto-increment physical write (APWR) Table 6 \u2013 Configured-address physical write (FPWR) <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Table 7 \u2013 Broadcast write (BWR) <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.4 Combined read\/write services Table 8 \u2013 Logical write (LWR) Table 9 \u2013 Auto-increment physical read\/write (APRW) <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Table 10 \u2013 Configured-address physical read\/write (FPRW) <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Table 11 \u2013 Broadcast read\/write (BRW) Table 12 \u2013 Logical read\/write (LRW) <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Table 13 \u2013 Auto-increment physical read \/ multiple write (ARMW) Table\u00a014 \u2013 Configured-address physical read \/ multiple write (FRMW) <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 5.5 Network services Table 15 \u2013 Provide network variable (PNV) <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 5.6 Mailbox <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Figure 9 \u2013 Successful mailbox write sequence Figure 10 \u2013 Successful mailbox read sequence <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | Table 16 \u2013 Mailbox write <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | Table 17 \u2013 Mailbox read update <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | Table 18 \u2013 Mailbox read <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 6 Local interactions 6.1 Read local 6.2 Write local Table 19 \u2013 Read local Table 20 \u2013 Write local <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 6.3 Event local Table 21 \u2013 Event local <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Data-link layer service definition. Type 12 elements<\/b><\/p>\n |