Shopping Cart

No products in the cart.

BS EN 61158-6-14:2012

$215.11

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

Published By Publication Date Number of Pages
BSI 2012 92
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]

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 standard 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 14 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 standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 14 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 standard is to define the protocol provided to

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

  2. define the externally visible behavior associated with their transfer.

This standard specifies the protocol of the Type 14 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layer structure (ISO/IEC 9545).

1.2 Specifications

The principal objective of this standard is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-14.

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 protocols standardized in the IEC 61158-6 series.

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 standard 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 14 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 standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 14 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 standard is to define the protocol provided to

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

  2. define the externally visible behavior associated with their transfer.

This standard specifies the protocol of the Type 14 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layer structure (ISO/IEC 9545).

1.2 Specifications

The principal objective of this standard is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-14.

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 protocols standardized in the IEC 61158-6 series.

PDF Catalog

PDF Pages PDF Title
6 CONTENTS
11 INTRODUCTION
12 1 Scope
1.1 General
1.2 Specifications
13 1.3 Conformance
2 Normative references
3 Terms, definitions, symbols, abbreviations and conventions
3.1 Referenced terms and definitions
15 3.2 Fieldbus application layer specific terms and definitions
18 3.3 Abbreviations and symbols
19 3.4 Conventions
Figures
Figure 1 – State transition diagram
20 4 Abstract syntax
4.1 Fixed format PDU description
Tables
Table 1 – State machine description elements
28 4.2 Object definitions in FAL management ASE
Table 2 – Definition of Type 14 MOB header object
Table 3 – Definition of Type 14 device descriptor object
29 Table 4 – Definition of the time synchronization object
30 Table 5 – Definition of maximum response time object
Table 6 – Definition of the Type 14 communication scheduling management object
Table 7 – Definition of the device application information object
31 Table 8 – Definition of FB application information header
Table 9 – Definition of domain application information header
32 Table 10 – Definition of Type 14 link object header
Table 11 – Definition of Type 14 FRT link object header
33 Table 12 – Definition of FB application information object
Table 13 – Definition of Type 14 link object
34 Table 14 – Definition of Type 14 FRT link object
35 4.3 Definition of objects used in Type 14 application access entity
Table 15 – Definition of domain application information object
Table 16 – Definition of domain object
36 Table 17 – Definition of simple variable object
Table 18 – Definition of event object
37 Table 19 – Definition of Type 14 socket mapping object
Table 20 – Definition of Type 14 socket timer object
38 5 Transfer syntax
5.1 Encodingof basic data types
Table 21 – Definition of ErrorType object
Table 22 – Encoding of Boolean value TRUE
Table 23 – Encoding of Boolean value FALSE
39 Table 24 – Encoding of Unsigned8 data type
Table 25 – Encoding of Unsigned16 data type
Table 26 – Encoding of Unsigned32 data type
40 Table 27 – Encoding of Unsigned64 data type
Table 28 – Encoding of Int8 data type
Table 29 – Encoding of Int16 data type
41 Table 30 – Encoding of Int32 data type
Table 31 – Encoding of Int64 data type
Table 32 – Encoding of Real type
42 Table 33 – Encoding of VisibleString data type
Table 34 – Encoding of OctetString data type
Table 35 – Encoding of BitString data type
43 Table 36 – Encoding of TimeOfDay data type
44 Table 37 – Encoding of BinaryDate data type
Table 38 – Encoding of PrecisionTimeDifference data type
45 5.2 Encoding of Type 14 APDU header
5.3 Encoding of FAL management entity service parameters
Table 39 – Encoding of Type 14 application layer service message header
Table 40 – Encoding of EM_DetectingDevice request parameters
46 Table 41 – Encoding of EM_OnlineReply request parameters
Table 42 – Encoding of EM_GetDeviceAttribute request parameters
Table 43 – Encoding of EM_GetDeviceAttribute positive response parameters
47 Table 44 – Encoding of EM_GetDeviceAttribute negative response parameters
48 Table 45 – Encoding of EM_ActiveNotification request parameters
49 Table 46 – Encoding of EM_ConfiguringDevice request parameters
50 Table 47 – Encoding of EM_ConfiguringDevice positive response parameters
Table 48 – Encoding of EM_ConfiguringDevice negative response parameters
Table 49 – Encoding of EM_SetDefaultValue request parameters
Table 50 – Encoding of EM_SetDefaultValue positive response parameters
51 5.4 Encoding of AAE Services
Table 51 – Encoding of clear device attribute service refuse packet
Table 52 – Encoding of DomainDownload request parameters
Table 53 – Encoding of domain download service response packet
Table 54 – Encoding of DomainDownload negative response parameters
52 Table 55 – Encoding of DomainUpload request parameters
Table 56 – Encoding of DomainUpload positive response parameters
Table 57 – Encoding of DomainUpload negative response parameters
53 Table 58 – Encoding of EventRoport request parameters
Table 59 – Encoding of EventRoportAcknowledge request parameters
Table 60 – Encoding of EventRoportAcknowledge positive response parameters
Table 61 – Encoding of EventRoportAcknowledge negative response parameters
54 Table 62 – Encoding of ReportConditionChanging request parameters
Table 63 – Encoding of ReportConditionChanging positive response parameters
Table 64 – Encoding of ReportConditionChanging negative response parameters
Table 65 – Encoding of Read request parameters
55 Table 66 – Encoding of Read positive response parameters
Table 67 – Encoding of Read negative response parameters
Table 68 – Encoding of Write request parameters
Table 69 – Encoding of Write positive response parameters
56 Table 70 – Encoding of Write negative response parameters
Table 71 – Encoding of VariableDistribute request parameters
Table 72 – Encoding of FRTRead request parameters
Table 73 – Encoding of FRTRead positive response parameters
Table 74 – Encoding of FRTRead negative response parameters
57 6 Structure of FAL protocol state machines
Table 75 – Encoding of FRTWrite request parameters
Table 76 – Encoding of FRTWrite positive response parameters
Table 77 – Encoding of FRTWrite negative response parameters
Table 78 – Encoding of FRTVariableDistribute request parameters
58 7 AP-Context state machine
7.1 Primitives exchanged between ALU and ALE
7.2 Protocol state machine descriptions
Figure 2 – Exchanged primitives of protocol state machine
Table 79 – Primitives delivered by ALU to ALE
Table 80 – Primitives delivered by ALE to ALU
59 7.3 State transitions
Figure 3 – ACE protocol state machine
Table 81 – ACE state descriptions
Table 82 – ACE state transitions (sender)
62 Table 83 – ACE state transitions (receiver)
65 7.4 Function descriptions
8 FAL management state machines
8.1 Primitives
Table 84 – APServiceType() descriptions
Table 85 – Primitives delivered by application layer user to FME
66 Table 86 – Primitives delivered by FME to application layer user
Table 87 – Primitive parameters exchanged between FME and application layer user
Table 88 – Primitives delivered by FME to ESME
Table 89 – Primitives delivered by ESME to FME
67 8.2 Protocol state machine descriptions
8.3 State transitions
Figure 4 – FME protocol state machine
Table 90 – Primitives parameters exchanged between FME and ESME
68 Table 91 – State transitions of Type 14 FME
69 8.4 Function descriptions
70 Table 92 – RcvNewIpAddress() descriptions
Table 93 – Attribute_Set() descriptions
Table 94 – RestoreDefaults() descriptions
Table 95 – NewAddress() descriptions
Table 96 – Restart_Type 14RepeatTimer() descriptions
71 Table 97 – Clear_DuplicatePdTagFlag() descriptions
Table 98 – Type 14RepeatTimerExpire() descriptions
Table 99 – Send_EM_ReqRspMessage() descriptions
Table 100 – Send_EM_CommonErrorRsp() descriptions
72 Table 101 – SntpSyncLost() descriptions
Table 102 – IPAddressCollision() descriptions
Table 103 – RecvMsg() descriptions
Table 104 – QueryMatch() descriptions
Table 105 – MessageIDMatch() descriptions
73 9 Application access entity protocol machine
9.1 Primitives
Table 106 – DevId_Match() descriptions
Table 107 – PdTag_Match() descriptions
Table 108 – Set_Attribute_Data() descriptions
Table 109 – Set_DuplicatePdTagFlag() descriptions
74 Table 110 – Primitives issued by ALU to AAE
Table 111 – Primitives issued by AAE to ALU
Table 112 – Primitives parameters exchanged between AAE and ALU
Table 113 – Primitives issued by AAE to ESME
75 9.2 AAE state machine
Figure 5 – AAE state transition diagrams
Table 114 – Primitives issued by ESME to AAE
Table 115 – Primitive parameters exchanged between AAE and ESME
Table 116 – AAE state descriptions
76 Table 117 – AAE state transitions (sender)
77 Table 118 – AAE state transitions (receiver)
Table 119 – ServiceType() descriptions
78 9.3 Event ASE protocol machine
Figure 6 – Event ASE state transition diagrams
Table 120 – State value of event management
79 9.4 Domain ASE protocol machine
Table 121 – Event ASE state transition table
Table 122 – Domain state value
80 Figure 7 – Domain ASE state transition diagram
Table 123 – Domain ASE state transition table
82 Table 124 – Domain_DownloadSucceed() description
83 10 Application relationship state machine
10.1 Primitives
Table 125 – Domain_WriteBuffer() description
Table 126 – IncreamentInvokeDomainCounter() description
Table 127 – DecreamentInvokeDomainCounter() description
Table 128 – Primitives issued by FME(or AAE) to AREP
84 10.2 AREP state description
Table 129 – Primitives issued by AREP to FME(or AAE)
Table 130 – Primitives parameters exchanged between AREP and FME(or AAE)
Table 131 – Primitives issued by AREP to ESME
Table 132 – Primitives issued by ESME to AREP
Table 133 – Primitive parameters exchanged between AREP and ESME
85 10.3 State transitions
Figure 8 – AREP state transition diagrams
Table 134 – AREP state descriptions
Table 135 – AREP state transitions
86 10.4 Function descriptions
11 DLL mapping protocol machine
11.1 Concept
11.2 Primitives
Table 136 – AREPType() descriptions
Table 137 – ServiceType() descriptions
87 11.3 State description
11.4 State transitions
Figure 9 – ESME state transition
Table 139 – Primitives parameters exchanged between Transport Layer and ESME
Table 140 – ESME state description
88 11.5 Function description
Table 141 – ECFME state transitions
Table 142 – ServiceType()description
89 Bibliography
BS EN 61158-6-14:2012
$215.11