{"id":244054,"date":"2024-10-19T16:01:35","date_gmt":"2024-10-19T16:01:35","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-6-142012\/"},"modified":"2024-10-25T10:59:50","modified_gmt":"2024-10-25T10:59:50","slug":"bs-en-61158-6-142012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-6-142012\/","title":{"rendered":"BS EN 61158-6-14:2012"},"content":{"rendered":"
1.1<\/b> General<\/p>\n
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 \u201cwindow between corresponding application programs.\u201d<\/p>\n
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 \u201ctime-critical\u201d 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.<\/p>\n
This standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 14 fieldbus application layer in terms of<\/p>\n
the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;<\/p>\n<\/li>\n
the transfer syntax defining encoding rules that are applied to the application layer protocol data units;<\/p>\n<\/li>\n
the application context state machine defining the application service behavior visible between communicating application entities;<\/p>\n<\/li>\n
the application relationship state machines defining the communication behavior visible between communicating application entities.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this standard is to define the protocol provided to<\/p>\n
define the wire-representation of the service primitives defined in IEC 61158-5-14, and<\/p>\n<\/li>\n
define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
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).<\/p>\n
1.2<\/b> Specifications<\/p>\n
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.<\/p>\n
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.<\/p>\n
1.1<\/b> General<\/p>\n
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 \u201cwindow between corresponding application programs.\u201d<\/p>\n
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 \u201ctime-critical\u201d 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.<\/p>\n
This standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 14 fieldbus application layer in terms of<\/p>\n
the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;<\/p>\n<\/li>\n
the transfer syntax defining encoding rules that are applied to the application layer protocol data units;<\/p>\n<\/li>\n
the application context state machine defining the application service behavior visible between communicating application entities;<\/p>\n<\/li>\n
the application relationship state machines defining the communication behavior visible between communicating application entities.<\/p>\n<\/li>\n<\/ol>\n
The purpose of this standard is to define the protocol provided to<\/p>\n
define the wire-representation of the service primitives defined in IEC 61158-5-14, and<\/p>\n<\/li>\n
define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
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).<\/p>\n
1.2<\/b> Specifications<\/p>\n
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.<\/p>\n
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1 Scope 1.1 General 1.2 Specifications <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1.3 Conformance 2 Normative references 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Referenced terms and definitions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.2 Fieldbus application layer specific terms and definitions <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3.3 Abbreviations and symbols <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 3.4 Conventions Figures Figure 1\u00a0\u2013\u00a0State transition diagram <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4 Abstract syntax 4.1 Fixed format PDU description Tables Table 1\u00a0\u2013\u00a0State machine description elements <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4.2 Object definitions in FAL management ASE Table 2\u00a0\u2013\u00a0Definition of Type\u00a014 MOB header object Table 3\u00a0\u2013\u00a0Definition of Type\u00a014 device descriptor object <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table 4\u00a0\u2013\u00a0Definition of the time synchronization object <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Table 5\u00a0\u2013\u00a0Definition of maximum response time object Table 6\u00a0\u2013\u00a0Definition of the Type\u00a014 communication scheduling management object Table 7\u00a0\u2013\u00a0Definition of the device application information object <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table 8\u00a0\u2013\u00a0Definition of FB application information header Table 9 \u2013 Definition of domain application information header <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Table 10\u00a0\u2013\u00a0Definition of Type\u00a014 link object header Table 11\u00a0\u2013\u00a0Definition of Type\u00a014 FRT link object header <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Table 12\u00a0\u2013\u00a0Definition of FB application information object Table 13\u00a0\u2013\u00a0Definition of Type\u00a014 link object <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table 14\u00a0\u2013\u00a0Definition of Type\u00a014 FRT link object <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.3 Definition of objects used in Type\u00a014 application access entity Table 15\u00a0\u2013\u00a0Definition of domain application information object Table 16\u00a0\u2013\u00a0Definition of domain object <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 17\u00a0\u2013\u00a0Definition of simple variable object Table 18\u00a0\u2013\u00a0Definition of event object <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table 19\u00a0\u2013\u00a0Definition of Type\u00a014 socket mapping object Table 20\u00a0\u2013\u00a0Definition of Type\u00a014 socket timer object <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5 Transfer syntax 5.1 Encodingof basic data types Table 21\u00a0\u2013\u00a0Definition of ErrorType object Table 22\u00a0\u2013\u00a0Encoding of Boolean value TRUE Table 23\u00a0\u2013\u00a0Encoding of Boolean value FALSE <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 24\u00a0\u2013\u00a0Encoding of Unsigned8 data type Table 25\u00a0\u2013\u00a0Encoding of Unsigned16 data type Table 26\u00a0\u2013\u00a0Encoding of Unsigned32 data type <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table 27\u00a0\u2013\u00a0Encoding of Unsigned64 data type Table 28\u00a0\u2013\u00a0Encoding of Int8 data type Table 29\u00a0\u2013\u00a0Encoding of Int16 data type <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table 30\u00a0\u2013\u00a0Encoding of Int32 data type Table 31\u00a0\u2013\u00a0Encoding of Int64 data type Table 32\u00a0\u2013\u00a0Encoding of Real type <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table 33\u00a0\u2013\u00a0Encoding of VisibleString data type Table 34\u00a0\u2013\u00a0Encoding of OctetString data type Table 35\u00a0\u2013\u00a0Encoding of BitString data type <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Table 36\u00a0\u2013\u00a0Encoding of TimeOfDay data type <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 37\u00a0\u2013\u00a0Encoding of BinaryDate data type Table 38\u00a0\u2013\u00a0Encoding of PrecisionTimeDifference data type <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 5.2 Encoding of Type\u00a014 APDU header 5.3 Encoding of FAL management entity service parameters Table 39\u00a0\u2013\u00a0Encoding of Type\u00a014 application layer service message header Table 40\u00a0\u2013\u00a0Encoding of EM_DetectingDevice request parameters <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 41\u00a0\u2013\u00a0Encoding of EM_OnlineReply request parameters Table 42\u00a0\u2013\u00a0Encoding of EM_GetDeviceAttribute request parameters Table 43\u00a0\u2013\u00a0Encoding of EM_GetDeviceAttribute positive response parameters <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 44\u00a0\u2013\u00a0Encoding of EM_GetDeviceAttribute negative response parameters <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table 45\u00a0\u2013\u00a0Encoding of EM_ActiveNotification request parameters <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table 46\u00a0\u2013\u00a0Encoding of EM_ConfiguringDevice request parameters <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table 47\u00a0\u2013\u00a0Encoding of EM_ConfiguringDevice positive response parameters Table 48\u00a0\u2013\u00a0Encoding of EM_ConfiguringDevice negative response parameters Table 49\u00a0\u2013\u00a0Encoding of EM_SetDefaultValue request parameters Table 50\u00a0\u2013\u00a0Encoding of EM_SetDefaultValue positive response parameters <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 5.4 Encoding of AAE Services Table 51\u00a0\u2013\u00a0Encoding of clear device attribute service refuse packet Table 52\u00a0\u2013\u00a0Encoding of DomainDownload request parameters Table 53\u00a0\u2013\u00a0Encoding of domain download service response packet Table 54\u00a0\u2013\u00a0Encoding of DomainDownload negative response parameters <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table 55\u00a0\u2013\u00a0Encoding of DomainUpload request parameters Table 56\u00a0\u2013\u00a0Encoding of DomainUpload positive response parameters Table 57\u00a0\u2013\u00a0Encoding of DomainUpload negative response parameters <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table 58 \u2013 Encoding of EventRoport request parameters Table 59\u00a0\u2013\u00a0Encoding of EventRoportAcknowledge request parameters Table 60\u00a0\u2013\u00a0Encoding of EventRoportAcknowledge positive response parameters Table 61\u00a0\u2013\u00a0Encoding of EventRoportAcknowledge negative response parameters <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table 62\u00a0\u2013\u00a0Encoding of ReportConditionChanging request parameters Table 63\u00a0\u2013\u00a0Encoding of ReportConditionChanging positive response parameters Table 64\u00a0\u2013\u00a0Encoding of ReportConditionChanging negative response parameters Table 65\u00a0\u2013\u00a0Encoding of Read request parameters <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table 66\u00a0\u2013\u00a0Encoding of Read positive response parameters Table 67\u00a0\u2013\u00a0Encoding of Read negative response parameters Table 68\u00a0\u2013\u00a0Encoding of Write request parameters Table 69\u00a0\u2013\u00a0Encoding of Write positive response parameters <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 70\u00a0\u2013\u00a0Encoding of Write negative response parameters Table 71\u00a0\u2013\u00a0Encoding of VariableDistribute request parameters Table 72\u00a0\u2013\u00a0Encoding of FRTRead request parameters Table 73\u00a0\u2013\u00a0Encoding of FRTRead positive response parameters Table 74\u00a0\u2013\u00a0Encoding of FRTRead negative response parameters <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 6 Structure of FAL protocol state machines Table 75\u00a0\u2013\u00a0Encoding of FRTWrite request parameters Table 76\u00a0\u2013\u00a0Encoding of FRTWrite positive response parameters Table 77\u00a0\u2013\u00a0Encoding of FRTWrite negative response parameters Table 78\u00a0\u2013\u00a0Encoding of FRTVariableDistribute request parameters <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 7 AP-Context state machine 7.1 Primitives exchanged between ALU and ALE 7.2 Protocol state machine descriptions Figure 2\u00a0\u2013\u00a0Exchanged primitives of protocol state machine Table 79\u00a0\u2013\u00a0Primitives delivered by ALU to ALE Table 80\u00a0\u2013\u00a0Primitives delivered by ALE to ALU <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 7.3 State transitions Figure 3\u00a0\u2013\u00a0ACE protocol state machine Table 81\u00a0\u2013\u00a0ACE state descriptions Table 82\u00a0\u2013\u00a0ACE state transitions (sender) <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 83\u00a0\u2013\u00a0ACE state transitions (receiver) <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 7.4 Function descriptions 8 FAL management state machines 8.1 Primitives Table 84\u00a0\u2013\u00a0APServiceType() descriptions Table 85\u00a0\u2013\u00a0Primitives delivered by application layer user to FME <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 86\u00a0\u2013\u00a0Primitives delivered by FME to application layer user Table 87\u00a0\u2013\u00a0Primitive parameters exchanged between FME and application layer user Table 88\u00a0\u2013\u00a0Primitives delivered by FME to ESME Table 89\u00a0\u2013\u00a0Primitives delivered by ESME to FME <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 8.2 Protocol state machine descriptions 8.3 State transitions Figure 4\u00a0\u2013\u00a0FME protocol state machine Table 90\u00a0\u2013\u00a0Primitives parameters exchanged between FME and ESME <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Table 91\u00a0\u2013\u00a0State transitions of Type\u00a014 FME <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 8.4 Function descriptions <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 92\u00a0\u2013\u00a0RcvNewIpAddress() descriptions Table 93\u00a0\u2013\u00a0Attribute_Set() descriptions Table 94\u00a0\u2013\u00a0RestoreDefaults() descriptions Table 95\u00a0\u2013\u00a0NewAddress() descriptions Table 96\u00a0\u2013\u00a0Restart_Type\u00a014RepeatTimer() descriptions <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 97\u00a0\u2013\u00a0Clear_DuplicatePdTagFlag() descriptions Table 98\u00a0\u2013\u00a0Type\u00a014RepeatTimerExpire() descriptions Table 99\u00a0\u2013\u00a0Send_EM_ReqRspMessage() descriptions Table 100\u00a0\u2013\u00a0Send_EM_CommonErrorRsp() descriptions <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 101\u00a0\u2013\u00a0SntpSyncLost() descriptions Table 102\u00a0\u2013\u00a0IPAddressCollision() descriptions Table 103\u00a0\u2013\u00a0RecvMsg() descriptions Table 104\u00a0\u2013\u00a0QueryMatch() descriptions Table 105\u00a0\u2013\u00a0MessageIDMatch() descriptions <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 9 Application access entity protocol machine 9.1 Primitives Table 106\u00a0\u2013\u00a0DevId_Match() descriptions Table 107\u00a0\u2013\u00a0PdTag_Match() descriptions Table 108\u00a0\u2013\u00a0Set_Attribute_Data() descriptions Table 109\u00a0\u2013\u00a0Set_DuplicatePdTagFlag() descriptions <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 110\u00a0\u2013\u00a0Primitives issued by ALU to AAE Table 111\u00a0\u2013\u00a0Primitives issued by AAE to ALU Table 112\u00a0\u2013\u00a0Primitives parameters exchanged between AAE and ALU Table 113\u00a0\u2013\u00a0Primitives issued by AAE to ESME <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 9.2 AAE state machine Figure 5\u00a0\u2013\u00a0AAE state transition diagrams Table 114\u00a0\u2013\u00a0Primitives issued by ESME to AAE Table 115\u00a0\u2013\u00a0Primitive parameters exchanged between AAE and ESME Table 116\u00a0\u2013\u00a0AAE state descriptions <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 117\u00a0\u2013\u00a0AAE state transitions (sender) <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 118\u00a0\u2013\u00a0AAE state transitions (receiver) Table 119\u00a0\u2013\u00a0ServiceType() descriptions <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 9.3 Event ASE protocol machine Figure 6\u00a0\u2013\u00a0Event ASE state transition diagrams Table 120\u00a0\u2013\u00a0State value of event management <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 9.4 Domain ASE protocol machine Table 121\u00a0\u2013\u00a0Event ASE state transition table Table 122\u00a0\u2013\u00a0Domain state value <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 7\u00a0\u2013\u00a0Domain ASE state transition diagram Table 123\u00a0\u2013\u00a0Domain ASE state transition table <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 124\u00a0\u2013\u00a0Domain_DownloadSucceed() description <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 10 Application relationship state machine 10.1 Primitives Table 125\u00a0\u2013\u00a0Domain_WriteBuffer() description Table 126\u00a0\u2013\u00a0IncreamentInvokeDomainCounter() description Table 127\u00a0\u2013\u00a0DecreamentInvokeDomainCounter() description Table 128\u00a0\u2013\u00a0Primitives issued by FME(or AAE) to AREP <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 10.2 AREP state description Table 129\u00a0\u2013\u00a0Primitives issued by AREP to FME(or AAE) Table 130\u00a0\u2013\u00a0Primitives parameters exchanged between AREP and FME(or AAE) Table 131\u00a0\u2013\u00a0Primitives issued by AREP to ESME Table 132\u00a0\u2013\u00a0Primitives issued by ESME to AREP Table 133\u00a0\u2013\u00a0Primitive parameters exchanged between AREP and ESME <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 10.3 State transitions Figure 8\u00a0\u2013\u00a0AREP state transition diagrams Table 134\u00a0\u2013\u00a0AREP state descriptions Table 135\u00a0\u2013\u00a0AREP state transitions <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 10.4 Function descriptions 11 DLL mapping protocol machine 11.1 Concept 11.2 Primitives Table 136\u00a0\u2013\u00a0AREPType() descriptions Table 137\u00a0\u2013\u00a0ServiceType() descriptions <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 11.3 State description 11.4 State transitions Figure 9\u00a0\u2013\u00a0ESME state transition Table 139\u00a0\u2013\u00a0Primitives parameters exchanged between Transport Layer and ESME Table 140\u00a0\u2013\u00a0ESME state description <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 11.5 Function description Table 141\u00a0\u2013\u00a0ECFME state transitions Table 142\u00a0\u2013\u00a0ServiceType()description <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 14 elements<\/b><\/p>\n |