Shopping Cart

No products in the cart.

BS EN IEC 61158-6-19:2019

$142.49

Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 19 elements

Published By Publication Date Number of Pages
BSI 2019 28
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

1.1 General

The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.”

This part of IEC 61158 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 19 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.

This International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of:

  1. an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service;

  2. the primitive actions and events of the service;

  3. the parameters associated with each primitive action and event, and the form which they take; and

  4. the interrelationship between these actions and events, and their valid sequences.

The purpose of this document is to define the services provided to:

  1. the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and

  2. Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.

This document specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545).

FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.

Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

1.2 Specifications

The principal objective of this document is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for timecritical communications.

A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6.

1.3 Conformance

This document does not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems.

There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfill any given Type of application layer services as defined in this document.

PDF Catalog

PDF Pages PDF Title
2 National foreword
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
6 CONTENTS
8 FOREWORD
10 INTRODUCTION
11 1 Scope
1.1 General
12 1.2 Specifications
1.3 Conformance
2 Normative references
13 3 Terms, definitions, symbols, abbreviations and conventions
3.1 Referenced terms and definitions
3.1.1 ISO/IEC 74981 terms
3.1.2 ISO/IEC 8822 terms
3.1.3 ISO/IEC 9545 terms
3.1.4 ISO/IEC 8824-1 terms
14 3.1.5 Fieldbus Data Link Layer terms
3.2 Additional terms and definitions
15 3.3 Additional abbreviations and symbols
16 3.4 Conventions
4 Abstract syntax
5 Transfer syntax
5.1 Introduction
5.2 RTC PDU merged abstract and transfer syntax
6 Structure of FAL protocol state machines
Tables
Table 1 – RTC PDU attribute format
17 Figures
Figure 1 – Relationships among protocol machines and adjacent layers
18 7 AP-context state machine
7.1 Overview
7.2 States
7.2.1 Idle
7.2.2 Running
Figure 2 – APCSM state diagram
19 7.3 States, events and transitions
8 FAL service protocol machine (FSPM)
8.1 Overview
8.2 MGT services
8.2.1 Get network status
8.2.2 Get device status
8.2.3 Network status change report
8.2.4 Device status change report
8.2.5 Set device status
8.2.6 Enable RTC
Table 2 – APCSM state-event table
20 8.2.7 Enable hot-plug
8.2.8 Notify RTC
8.2.9 Disable RTC
8.2.10 Notify error
8.3 IDN services
8.3.1 Read
8.3.2 Write
8.4 CYCIDN services
8.4.1 Read_cyclic
8.4.2 Write_cyclic
8.4.3 Notify_cyclic
9 Application relationship protocol machine (ARPM)
9.1 Overview
21 9.2 Master ARPM
9.2.1 Overview
9.2.2 State descriptions
Figure 3 – ARPM master AR state diagram
22 9.2.3 States, events and transitions
9.3 Slave ARPM
9.3.1 Overview
9.3.2 State descriptions
Figure 4 – ARPM slave AR state diagram
Table 3 – Master ARPM state-event table
23 9.3.3 States, events and transitions
9.4 Primitives received from the FSPM
9.4.1 FSP-get network status
9.4.2 FSP-get device status
9.4.3 FSP-set device status
Table 4 – Slave ARPM state-event table
24 9.4.4 FSP-enable RTC
9.4.5 FSP-enable Hot-plug
9.4.6 FSP-disable RTC
9.4.7 FSP-read
9.4.8 FSP-write
9.4.9 FSP-read_cyclic
9.4.10 FSP-write_cyclic
25 9.5 Indications received from the DMPM
9.5.1 ARP-network status change report
9.5.2 ARP-device status change report
9.5.3 ARP-notify RTC enabled
9.5.4 ARP-notify RTC disabled
9.5.5 ARP-notify_cyclic
9.5.6 ARP-notify Error
10 DLL mapping protocol machine (DMPM)
10.1 Overview
26 10.2 Primitives received from the ARPM
10.3 Indications received from the DL
Table 5 – ARPM to DL mapping
Table 6 – DL to ARPM mapping
27 Bibliography
BS EN IEC 61158-6-19:2019
$142.49