{"id":244051,"date":"2024-10-19T16:01:34","date_gmt":"2024-10-19T16:01:34","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-6-122012\/"},"modified":"2024-10-25T10:59:50","modified_gmt":"2024-10-25T10:59:50","slug":"bs-en-61158-6-122012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-6-122012\/","title":{"rendered":"BS EN 61158-6-12:2012"},"content":{"rendered":"
1.1 General<\/b><\/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 12 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 defines in an abstract way the externally visible behavior provided by the different Types of the fieldbus Application Layer in terms of<\/p>\n
the abstract syntax defining the application layer protocol data units conveyed between communicating application entities,<\/p>\n<\/li>\n
the transfer syntax defining the application layer protocol data units conveyed between communicating application entities,<\/p>\n<\/li>\n
the application context state machine defining the application service behavior visible between communicating application entities; and<\/p>\n<\/li>\n
the application relationship state machines defining the communication behavior visible between communicating application entities; and.<\/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-12, 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 IEC 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
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.<\/p>\n
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 standard to provide access to the FAL to control certain aspects of its operation.<\/p>\n
1.2 Specifications<\/b><\/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-12.<\/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 subparts of IEC 61158-6.<\/p>\n
1.3 Conformance<\/b><\/p>\n
This standard does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems.<\/p>\n
There is no conformance of equipment to the application layer service definition standard. Instead, conformance is achieved through implementation of this application layer protocol specification.<\/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 <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions 3.2 Service convention terms and definitions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.3 Application layer definitions <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 3.4 Common symbols and abbreviations 3.5 Additional symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 3.6 Conventions Figures Figure\u00a01 \u2013 Common structure of specific fields <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure\u00a02 \u2013 Type description example Tables Table\u00a01 \u2013 PDU element description example <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Table\u00a02 \u2013 Example attribute description Table\u00a03 \u2013 State machine description elements <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Table\u00a04 \u2013 Description of state machine elements Table\u00a05 \u2013 Conventions used in state machines <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 4 Application layer protocol specification 4.1 Operating principle 4.2 Node reference model <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figure\u00a03 \u2013 Slave Node Reference Model <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5 FAL syntax description 5.1 Coding principles 5.2 Data types and encoding rules Figure\u00a04 \u2013 Encoding of Time Of Day value <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure\u00a05 \u2013 Encoding of Time Difference value Table\u00a06 \u2013 Transfer Syntax for bit sequences <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table\u00a07 \u2013 Transfer syntax for data type Unsignedn <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5.3 AR coding Figure\u00a06 \u2013 AL Control Request structure Table\u00a08 \u2013 Transfer syntax for data type Integern <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure\u00a07 \u2013 AL Control Response structure Table\u00a09 \u2013 AL Control Description Table\u00a010 \u2013 AL Control Response <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table\u00a011 \u2013 AL Status Codes <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure\u00a08 \u2013 AL State Changed structure Table\u00a012 \u2013 AL State Changed <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure\u00a09 \u2013 PDI Control type description Figure\u00a010 \u2013 Sync Configuration type description Table\u00a013 \u2013 PDI Control Table\u00a014 \u2013 PDI Configuration <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.4 SII coding Table\u00a015 \u2013 Sync Configuration Table\u00a016 \u2013 Slave Information Interface Area <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table\u00a017 \u2013 Slave Information Interface Categories Table\u00a018 \u2013 Mailbox Protocols Supported Types <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table\u00a019 \u2013 Categories Types Table\u00a020 \u2013 Structure Category String <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table\u00a021 \u2013 Structure Category General <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table\u00a022 \u2013 Structure Category FMMU Table\u00a023 \u2013 Structure Category SyncM for each Element <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.5 Isochronous PDI coding Table\u00a024 \u2013 Structure Category TXPDO and RXPDO for each PDO Table\u00a025 \u2013 Structure PDO Entry <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure\u00a011 \u2013 Distributed Clock sync and latch type description <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table\u00a026 \u2013 Distributed Clock sync parameter <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Table\u00a027 \u2013 Distributed Clock latch data <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 5.6 CoE coding Figure\u00a012 \u2013 CoE general structure Table\u00a028 \u2013 CoE elements <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure\u00a013 \u2013 SDO Download Expedited Request structure <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure\u00a014 \u2013 SDO Download Expedited Response structure Table\u00a029 \u2013 SDO Download Expedited Request <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure\u00a015 \u2013 SDO Download Normal Request structure Table\u00a030 \u2013 SDO Download Expedited Response <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table\u00a031 \u2013 SDO Download Normal Request <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure\u00a016 \u2013 Download SDO Segment Request structure Table\u00a032 \u2013 Download SDO Segment Request <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure\u00a017 \u2013 Download SDO Segment Response structure Figure\u00a018 \u2013 SDO Upload Expedited Request structure Table\u00a033 \u2013 Download SDO Segment Response <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure\u00a019 \u2013 SDO Upload Expedited Response structure Table\u00a034 \u2013 SDO Upload Expedited Request <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table\u00a035 \u2013 SDO Upload Expedited Response <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Figure\u00a020 \u2013 SDO Upload Normal Response structure Table\u00a036 \u2013 SDO Upload Normal Response <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Figure\u00a021 \u2013 Upload SDO Segment Request structure Figure\u00a022 \u2013 Upload SDO Segment Response structure Table\u00a037 \u2013 Upload SDO Segment Request <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure\u00a023 \u2013 Abort SDO Transfer Request structure Table\u00a038 \u2013 Upload SDO Segment Response <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table\u00a039 \u2013 Abort SDO Transfer Request <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table\u00a040 \u2013 SDO Abort Codes <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure\u00a024 \u2013 SDO Information Service structure Figure\u00a025 \u2013 Get OD List Request structure Table\u00a041 \u2013 SDO Information Service <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Figure\u00a026 \u2013 Get OD List Response structure Table\u00a042 \u2013 Get OD List Request <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table\u00a043 \u2013 Get OD List Response <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure\u00a027 \u2013 Get Object Description Request structure Figure\u00a028 \u2013 Get Object Description Response structure Table\u00a044 \u2013 Get Object Description Request <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure\u00a029 \u2013 Get Entry Description Request structure Table\u00a045 \u2013 Get Object Description Response <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure\u00a030 \u2013 Get Entry Description Response structure Table\u00a046 \u2013 Get Entry Description Request <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table\u00a047 \u2013 Get Entry Description Response <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Figure\u00a031 \u2013 SDO Info Error Request structure <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Table\u00a048 \u2013 SDO Info Error Request <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table\u00a049 \u2013 Emergency Request <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table\u00a050 \u2013 Emergency Error Codes Table\u00a051 \u2013 Error Code <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table\u00a052 \u2013 Diagnostic Data Table\u00a053 \u2013 Sync Manager Length Error Table\u00a054 \u2013 Sync Manager Address Error Table\u00a055 \u2013 Sync Manager Settings Error <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table\u00a056 \u2013 RxPDO Transmission via mailbox Table\u00a057 \u2013 TxPDO Transmission via mailbox <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table\u00a058 \u2013 RxPDO Remote Transmission Request Table\u00a059 \u2013 TxPDO Remote Transmission Request <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table\u00a060 \u2013 Command object structure Table\u00a061 \u2013 Object Dictionary Structure Table\u00a062 \u2013 Object Code Definitions <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table\u00a063 \u2013 Basic Data Type Area <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table\u00a064 \u2013 Extended Data Type Area <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table\u00a065 \u2013 Enumeration Definition Table\u00a066 \u2013 CoE Communication Area <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table\u00a067 \u2013 Device Type <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table\u00a068 \u2013 Error Register Table\u00a069 \u2013 Manufacturer Device Name <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table\u00a070 \u2013 Manufacturer Hardware Version Table\u00a071 \u2013 Manufacturer Software Version Table\u00a072 \u2013 Identity Object <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table\u00a073 \u2013 Receive PDO Mapping Table\u00a074 \u2013 Transmit PDO Mapping <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table\u00a075 \u2013 Sync Manager Communication Type <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table\u00a076 \u2013 Sync Manager Channel 0-31 <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 5.7 EoE coding Figure\u00a032 \u2013 EoE general structure Table\u00a077 \u2013 Sync Manager Synchronization <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure\u00a033 \u2013 EoE Timestamp structure Table\u00a078 \u2013 Initiate EoE Request <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure\u00a034 \u2013 EoE Fragment Request structure Table\u00a079 \u2013 Initiate EoE Response <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table\u00a080 \u2013 EoE Fragment Request <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure\u00a035 \u2013 Set IP Parameter Request structure Table\u00a081 \u2013 EoE Data <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table\u00a082 \u2013 Set IP Parameter Request <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure\u00a036 \u2013 Set IP Parameter Response structure Table\u00a083 \u2013 Set IP Parameter Response <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure\u00a037 \u2013 Set Address Filter Request structure Table\u00a084 \u2013 EoE Result Parameter <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table\u00a085 \u2013 Set Address Filter Request <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 5.8 FoE Coding Figure\u00a038 \u2013 Set Address Filter Response structure Table\u00a086 \u2013 Set Address Filter Response <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure\u00a039 \u2013 Read Request structure Figure\u00a040 \u2013 Write Request structure Table\u00a087 \u2013 Read Request <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure\u00a041 \u2013 Data Request structure Table\u00a088 \u2013 Write Request <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure\u00a042 \u2013 Ack Request structure Table\u00a089 \u2013 Data Request <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure\u00a043 \u2013 Error Request structure Table\u00a090 \u2013 Ack Request <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table\u00a091 \u2013 Error Request Table\u00a092 \u2013 Error codes of FoE <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 6 FAL protocol state machines 6.1 Overall structure Figure\u00a044 \u2013 Busy Request structure Table\u00a093 \u2013 Busy Request <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure\u00a045 \u2013 Relationship among Protocol Machines <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 6.2 AP-Context state machine 6.3 FAL service protocol machine (FSPM) 6.4 Application Relationship Protocol Machines (ARPMs) Figure\u00a046 \u2013 AR Protocol machines <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure\u00a047 \u2013 ESM Diagramm Table\u00a094 \u2013 State transitions and local management services <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table\u00a095 \u2013 Primitives issued by ESM to DL Table\u00a096 \u2013 Primitives issued by DL to ESM <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table\u00a097 \u2013 Primitives issued by Application to ESM Table\u00a098 \u2013 Primitives issued by ESM to Application Table\u00a099 \u2013 ESM Variables <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table\u00a0100 \u2013 ESM macros <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Table\u00a0101 \u2013 ESM functions <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table 102 \u2013 ESM state table <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table\u00a0103 \u2013 ESM Functions Table\u00a0104 \u2013 Primitives issued by Mailbox handler to DL Table\u00a0105 \u2013 Primitives issued by DL to Mailbox handler <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table\u00a0106 \u2013 Primitives issued by Protocol handler to Mailbox handler Table\u00a0107 \u2013 Primitives issued by Mailbox handler to Protocol handler <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Table\u00a0108 \u2013 Primitives issued by Application to CoESM <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | Table\u00a0109 \u2013 Primitives issued by CoESM to Application Table\u00a0110 \u2013 CoESM state table <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Table\u00a0111 \u2013 Primitives issued by Application to EoESM <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table\u00a0112 \u2013 Primitives issued by EoESM to Application <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Table\u00a0113 \u2013 EoESM state table <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table\u00a0114 \u2013 Primitives issued by Application to FoESM <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table\u00a0115 \u2013 Primitives issued by FoESM to Application Table\u00a0116 \u2013 FoESM state table <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | 6.5 DLL mapping protocol machine (DMPM) <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 12 elements<\/b><\/p>\n |