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