EN 61158-4-16:2008

FOREWORD
INTRODUCTION
1 Scope
  1.1 General
  1.2 Specifications
  1.3 Procedures
  1.4 Applicability
  1.5 Conformance
2 Normative references
3 Terms, definitions, symbols, abbreviations and
  conventions
  3.1 Reference model terms and definitions
  3.2 Service convention terms and definitions
  3.3 Other terms and definitions
  3.4 Abbreviations
  3.5 Symbols
  3.6 DLPDU IDN concept
4 DL-protocol overview
5 Basic DLPDU structure
  5.1 Overview
  5.2 MST DLPDU
  5.3 MDT DLPDU
  5.4 AT DLPDU
6 Network management methods
  6.1 Overview
  6.2 Enable and disable cyclic communication
  6.3 File transfer
  6.4 Status procedures
7 Data transmission methods
  7.1 Overview
  7.2 SVC
  7.3 RTC
8 DL management
  8.1 Overview
  8.2 Access to PhL
9 Error handling and monitoring
  9.1 Invalid telegrams
  9.2 Response to MDT and AT telegram failure
  9.3 Reaction to handshake timeout
  9.4 Service channel error messages
  9.5 Reaction to error messages in the service channel
  9.6 Error counters in the master and the slave
  9.7 Error effects on communication phases
  9.8 Monitoring in the master
  9.9 Monitoring in the slave
Annex A (normative) - IDN - Identification numbers
  A.1 IDN specification
  A.2 Identification numbers in numerical orders
  A.3 Detailed specification of communication-related
      IDNs
Annex ZA (normative) Normative references to international
         publications with their corresponding European
         publications
Bibliography

It provides basic time-critical messaging communications between devices in an automation environment. This protocol provides communication opportunities to all participating data-link entities in a synchronously-starting cyclic manner, according to a pre-established schedule, and in a cyclic or acyclic asynchronous manner, as requested each cycle by each of those data-link entities. Thus this protocol can be characterized as one which provides cyclic and acyclic access asynchronously but with a synchronous restart of each cycle. It includes the following significant changes with respect to the previous edition deletion of the former Type 6 fieldbus, and the placeholder for a Type 5 fieldbus data-link layer, for lack of market relevance; addition of new types of fieldbuses; division of this part into multiple parts numbered.