🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 61158-6-4:2019

BS EN IEC 61158-6-4:2019

$189.07

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

Published By Publication Date Number of Pages
BSI 2019 46
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

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]

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 International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 4 fieldbus application layer in terms of

  1. the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;

  2. the transfer syntax defining encoding rules that are applied to the application layer protocol data units;

  3. the application context state machine defining the application service behavior visible between communicating application entities;

  4. 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

  1. define the wire-representation of the service primitives defined in IEC 61158-5-4, and

  2. 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).

PDF Catalog

PDF Pages PDF Title
2 National foreword
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
7 CONTENTS
10 FOREWORD
12 INTRODUCTION
13 1 Scope
1.1 General
1.2 Specifications
14 1.3 Conformance
2 Normative references
3 Terms, definitions, symbols, abbreviations and conventions
15 3.1 Referenced terms and definitions
3.1.1 ISO/IEC 7498-1 terms
3.1.2 ISO/IEC 8822 terms
3.1.3 ISO/IEC 9545 terms
3.1.4 ISO/IEC 8824-1 terms
3.1.5 Fieldbus data-link layer terms
16 3.2 Abbreviations and symbols
3.3 Conventions
3.3.1 General concept
17 3.3.2 Conventions for state machines for Type 4
Figures
Figure 1 – State transition diagram
Tables
Table 1 – State machine description elements
18 4 FAL syntax description
4.1 FAL-AR PDU abstract syntax
4.1.1 General
4.1.2 Abstract syntax of APDU header
Table 2 – APDU header
19 4.1.3 Abstract syntax of APDU body
20 Table 3 – APDU body
21 4.2 Data types
5 Transfer syntaxes
5.1 APDU encoding
5.1.1 APDU Header encoding
Figure 2 – APDU header structure
22 Figure 3 –Subfields of ControlStatus for Request
Figure 4 – Subfields of ControlStatus for Response with error
23 5.1.2 APDU body encoding
Figure 5 – Subfields of ControlStatus for Response with no error
Figure 6 – DataFieldFormat encoding
24 Figure 7 – Structure of request APDU body
Figure 8 – Structure of response APDU body
Figure 9 – Variable identifier
Figure 10 – Code subfield of variable identifier
25 5.2 Variable object encoding and packing
5.2.1 Encoding of simple variables
26 5.2.2 Encoding of constructed variables
Figure 11 – Sequence of data in the APDU body subfield
27 5.2.3 Alignment
Figure 12 – MSG consists of APDU header and APDU body
28 5.2.4 Variable object attributes
Table 4 – Transfer syntax for Array
Table 5 – Transfer syntax for Structure
Table 6 – Common variable object attributes
29 5.3 Error codes
Table 7 – Variable type identifiers
Table 8 – FIFO variable object attributes
30 6 FAL protocol state machines
Table 9 – Error codes
31 7 AP-context state machine
Figure 13 – Summary of FAL architecture
32 8 FAL service protocol machine (FSPM)
8.1 Primitives exchanged between FAL User and FSPM
8.2 FSPM states
8.2.1 General
8.2.2 FSPM proxy object states
Table 10 – Primitives exchanged between FAL-User and FSPM
33 Figure 14 – FSPM proxy object state machine
Table 11 – REQUEST.req FSPM constraints
34 Table 12 – REQUEST.req FSPM actions
35 Table 13 – RESPONSE.cnf FSPM constraints
36 Table 14 – RESPONSE.cnf FSPM actions
37 8.2.3 FSPM real object state machine description
Table 15 – AR Send.ind proxy FSPM constraints
Table 16 – AR Send.ind proxy FSPM actions
38 Figure 15 – FSPM real object state machine
Table 17 – AR Send.ind real FSPM constraints
Table 18 – AR Send.ind real FSPM Actions
39 9 Application relationship protocol machine (ARPM)
9.1 Primitives exchanged between ARPM and FSPM
9.2 ARPM States
9.2.1 General
9.2.2 Sender state transitions
Figure 16 – ARPM state machine
Table 19 – Primitives issued by FSPM to ARPM
Table 20 – Primitives issued by ARPM to FSPM
Table 21 – Primitives issued by ARPM to ARPM
40 9.2.3 Receiver state transitions
Table 22 – AR Send.req ARPM constraints
Table 23 – AR Send.req ARPM actions
Table 24 – AR Acknowledge.req ARPM constraints
Table 25 – AR Acknowledge.req ARPM actions
41 10 DLL mapping protocol machine (DMPM)
10.1 Data-link Layer service selection
10.1.1 General
10.1.2 DL-UNITDATA request
10.1.3 DL-UNITDATA indication
10.1.4 DL-UNITDATA response
10.1.5 DLM-Set primitive and parameters
10.1.6 DLM-Get primitive and parameters
10.2 Primitives exchanged between ARPM and DLPM
Table 26 – AR Send.ind ARPM constraints
Table 27 – AR Send.req ARPM actions
42 10.3 Primitives exchanged between DLPM and data-link layer
10.4 DLPM states
10.4.1 States
Figure 17 – DLPM state machine
Table 28 – Primitives issued by ARPM to DLPM
Table 29 – Primitives issued by DLPM to ARPM
Table 30 – Primitives issued by DLPM to data-link layer
Table 31 – Primitives issued by data-link layer to DLPM
43 10.4.2 Sender state transitions
Table 32 – AR Send.req DLPM constraints
Table 33 – AR Send.req DLPM actions
Table 34 – AR Acknowledge.req DLPM constraints
44 10.4.3 Receiver state transitions
11 Protocol options
Table 35 – AR Acknowledge.req DLPM actions
Table 36 – DL-UNITDATA.ind DLPM constraints
Table 37 – DL-UNITDATA.ind DLPM actions
45 Bibliography

Related products

BS EN IEC 61158-6-4:2019
$189.07