This part of IEC 62056 specifies the DLMS®/COSEM application layer in terms of structure, services and protocols for DLMS®/COSEM clients and servers, and defines rules to specify the DLMS®/COSEM communication profiles.
It defines services for establishing and releasing application associations, and data communication services for accessing the methods and attributes of COSEM interface objects, defined in IEC 62056-6-2:2021 using either logical name (LN) or short name (SN) referencing.
Annex A (normative) defines how to use the COSEM application layer in various communication profiles. It specifies how various communication profiles can be constructed for exchanging data with metering equipment using the COSEM interface model, and what are the necessary elements to specify in each communication profile. The actual, media-specific communication profiles are specified in separate parts of the IEC 62056 series.
Annex B (normative) specifies the SMS short wrapper.
Annex C (normative) specifies the gateway protocol.
Annex D, Annex E and Annex F (informative) include encoding examples for APDUs.
Annex G (normative) provides NSA Suite B elliptic curves and domain parameters.
Annex H (informative) provides an example of an End entity signature certificate using P-256 signed with P-256.
Annex I (normative) specifies the use of key agreement schemes in DLMS®/COSEM.
Annex J (informative) provides examples of exchanging protected xDLMS APDUs between a third party and a server.
Annex K (informative) lists the main technical changes in this edition of the standard.

  • Standard
    380 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 23 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 document defines in an abstract way the externally visible service provided by the
different Types of the fieldbus Application Layer in terms of
a) an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form that they
take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
b) 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-1) 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.

  • Standard
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 10 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
a 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 document defines in an abstract way the externally visible behavior provided by the
Type 10 fieldbus application layer in terms of:
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machine defining the application service behavior visible
between communicating application entities, and
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
• define the wire-representation of the service primitives defined in IEC 61158-5-10 and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 10 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure
(ISO/IEC 9545).

  • Standard
    1185 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 document specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 2 fieldbus application layer in terms of
• the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
• the transfer syntax defining encoding rules that are applied to the application layer protocol
data units;
• the application context state machine defining the application service behavior visible
between communicating application entities;
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the wire-representation of the service primitives defined in IEC 61158-5-2, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure
(ISO/IEC 9545)

  • Standard
    293 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 4 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 document defines in an abstract way the externally visible service provided by the Type 4
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service;
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
• 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 Type 4 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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.

  • Standard
    74 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 document 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 24 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 document defines in an abstract way the externally visible service provided by the different
Types of fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this International Standard is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• 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-1) 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.

  • Standard
    105 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 27 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 document defines in an abstract way the externally visible service provided by the different
Types of fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• 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-1) 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.

  • Standard
    143 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 10 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 document defines in an abstract way the externally visible service provided by the Type 10
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
• 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 Type 10 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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.

  • Standard
    767 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 4 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 document specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 4 fieldbus application layer in terms of
• the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
• the transfer syntax defining encoding rules that are applied to the application layer protocol
data units;
• the application context state machine defining the application service behavior visible
between communicating application entities;
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the wire-representation of the service primitives defined in IEC 61158-5-4, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 4 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure
(ISO/IEC 9545).

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 24 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 document defines in an abstract way the externally visible behavior provided by the Type
24 fieldbus application layer in terms of
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machines defining the application service behavior visibly
between communicating application entities, and
• the application relationship state machines defining the communication behavior visibly
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the representation-on-wire of the service primitives defined in IEC 61158-5-24, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 24 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure
(ISO/IEC 9545)

  • Standard
    148 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of
a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units;
c) the application context state machine defining the application service behavior visible between communicating application entities;
d) the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this document is to define the protocol provided to
a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and
b) define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).

  • Standard
    210 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 document defines in an abstract way the externally visible service provided by the Type 2
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service;
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model; and
• 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 Type 2 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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.

  • Standard
    244 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 27 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
a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service,
c) the parameters associated with each primitive action and event, and the form which they take, and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this International Standard is to define the services provided to
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.
This International Standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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 289 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this International Standard to provide access to the FAL to control certain aspects of its operation.

  • Standard
    222 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be considered 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 28 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, in which one or more specified actions are required to be completed with
some defined level of certainty.
This document defines in an abstract way the externally visible service provided by the different
Types of the fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• 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-1) 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 to request and
response 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 behavioural 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 behaviour. 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.

  • Standard
    70 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 Type 2 fieldbus application layer in terms of:
a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form which they take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
a) the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and
b) 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 Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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 318 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.

  • Standard
    120 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 23 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 document defines in an abstract way the externally visible behavior provided by the
different Types of the fieldbus Application Layer in terms of:
a) the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
b) the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
c) the application context state machine defining the application service behavior visible
between communicating application entities; and
d) the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
a) define the wire-representation of the service primitives defined in IEC 61158-5-23, and
b) define the externally visible behavior associated with their transfer.
This document specifies the protocol 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.

  • Standard
    312 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be considered 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 28 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
can cause failure of the applications requesting the actions, with attendant risk to equipment,
plant and possibly human life.
This document defines in an abstract way the externally visible behavior provided by the
Type 28 of the fieldbus Application Layer in terms of:
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machine defining the application service behavior visible
between communicating application entities; and
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
• the wire-representation of the service primitives defined in IEC 61158-5-28, and
• the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 28 IEC fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application
Layer Structure (ISO/IEC 9545).

  • Standard
    28 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-5-4:2023 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 4 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.

  • Standard
    74 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-5-10:2023 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 10 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.

  • Standard
    767 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-5-2:2023 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 2 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.

  • Standard
    244 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-24:2023 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 24 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.

  • Standard
    148 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-23:2023 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 23 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.

  • Standard
    312 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-2:2023 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 2 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.

  • Standard
    293 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-4:2023 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 4 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.

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-10:2023 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 10 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 a 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.

  • Standard
    1185 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). 1.2 Specifications The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-2. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. 1.3 Conformance This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.

  • Standard
    210 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 2 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 Type 2 fieldbus application layer in terms of: a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, b) the primitive actions and events of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this document is to define the services provided to: a) the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and b) 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 Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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 318 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 [...] 1.3 Conformance [...]

  • Standard
    120 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-5-24:2023 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 24 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.

  • Standard
    105 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-5-25:2023 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 23 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.

  • Standard
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-26:2023 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 26 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.

  • Standard
    206 pages
    English language
    sale 15% off

IEC 61158-6-23:2023 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 23 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.

  • Standard
    309 pages
    English language
    sale 15% off

IEC 61158-6-4:2023 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 4 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.

  • Standard
    41 pages
    English language
    sale 15% off

IEC 61158-6-2:2023 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 2 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.

  • Standard
    289 pages
    English language
    sale 15% off

IEC 61158-6-10:2023 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 10 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 a 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.

  • Standard
    1179 pages
    English language
    sale 15% off

IEC 61158-5-10:2023 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 10 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.

  • Standard
    762 pages
    English language
    sale 15% off

IEC 61158-5-4:2023 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 4 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.

  • Standard
    71 pages
    English language
    sale 15% off

IEC 61158-6-24:2023 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 24 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.

  • Standard
    145 pages
    English language
    sale 15% off

IEC 61158-5-2:2023 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 2 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.

  • Standard
    240 pages
    English language
    sale 15% off

IEC 61158-5-26:2023 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 26 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 document defines in an abstract way the externally visible service provided by the Type26 fieldbus application layer in terms of:
an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service;
the primitive actions and events of the service;
the parameters associated with each primitive action and event, and the form which they take; and
the interrelationship between these actions and events, and their valid sequences.

  • Standard
    116 pages
    English language
    sale 15% off

IEC 61158-5-24:2023 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 24 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.

  • Standard
    102 pages
    English language
    sale 15% off

IEC 61158-5-25:2023 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 23 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.

  • Standard
    120 pages
    English language
    sale 15% off

IEC 62055-42:2022, specifies a token generation mechanism and token structure for smart prepayment functionality in markets where IEC 62055-41 compliant systems are not used, and where a different security mechanism is required by project-specific or national requirements. This document specifies token structure, authentication and an anti-replay mechanism, token operating model, and protocol. This document is informed by the STS Association key management services, and by the key management mechanisms used within the DLMS/COSEM security model within IEC 62056‑6‑2. Reference is made to the international STS token standards (IEC 62055-41, IEC 62055-51 and IEC 62055-52) for payment metering systems, and interworking has been considered where appropriate in terms of token carrier ranges in the decimal domain. IEC 62055-41 tokens and those described in this document are not interoperable, however their domains are designed to be mutually exclusive to ensure the two kinds of tokens do not interfere with each other. Metering application processing and functionality, HAN interface commands and attributes, WAN interface commands and attributes are outside the scope of this document; however, reference is made to other standards in this regard. The mechanism for auditing and retrieving data from the meter relating to tariffication, meter readings, profile data and other legal metrology information is outside the scope of this document; however, this is defined as part of any overall metering solution. Such interfaces for retrieving data from a meter may be defined using suitable protocols such as DLMS/COSEM as defined in the IEC 62056 series.

  • Standard
    84 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-4:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This third edition includes the following significant technical changes with respect to the previous edition: a) additional user parameters to services; b) additional services to support distributed objects; c) additional secure services.

  • Standard
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-21:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This second edition includes the following significant technical changes with respect to the previous edition: - added WriteAndRead service; - miscellaneous editorial corrections.

  • Standard
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-25:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).

  • Standard
    127 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-2:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This fourth edition includes the following significant technical changes with respect to the previous edition: - clarifications of response PDU formats in case of failure in 4.1.5; - clarifications of connection request priority definition and handling in 4.1.6.5 and 4.1.6.6; - clarification of connection remaining path in 4.1.6.12; - extensions of general syntax in 4.1.8.1; - extensions and clarifications of Identity object PDUs in 4.1.8.2; - updates of Assembly object PDUs in 4.1.8.4; - extensions and clarification of Time sync object PDUs in 4.1.8.6; - updates of Parameter object PDUs in 4.1.8.7; - extensions of Connection Manager object PDUs in 4.1.8.8; - clarifications of Connection object PDUs in 4.1.8.9; - extensions and clarifications of message and connection paths in 4.1.9; - updates of object and service class codes in 4.1.10 and error codes in 4.1.11; - updates of data types in 4.2.4, 5.1.3 and 5.2.3; - updates of the encapsulation abstract syntax in 4.3; - updates to the DLL mapping protocol machine 2 in Clause 11; - miscellaneous editorial corrections.

  • Standard
    276 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-19:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This fourth edition includes the following significant technical changes with respect to the previous edition: - improving the hotplug and redundancy features; - improving the phase switching and the error handling; - editorial improvements.

  • Standard
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-3:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This fourth edition includes the following significant technical changes with respect to the previous edition: - corrected substitutions in Table 4; - corrections in 5.3.14; - corrections in 5.5.6; - corrections in 5.17.15; - corrections in 5.17.16.2; - spelling and grammar.

  • Standard
    381 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 61158-6-23:2019 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 2 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 specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). This second edition includes the following significant technical changes with respect to the previous edition: - addition of the transmission extended mode and related attribute (Clauses 3.2.28, 4.1.9, 4.4, 5.2.9.2, and 5.3); - update of Table 4, Table 5, Table 16 and Table 48.

  • Standard
    228 pages
    English language
    sale 10% off
    e-Library read for
    1 day