{"id":244064,"date":"2024-10-19T16:01:39","date_gmt":"2024-10-19T16:01:39","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-6-222012\/"},"modified":"2024-10-25T10:59:58","modified_gmt":"2024-10-25T10:59:58","slug":"bs-en-61158-6-222012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-6-222012\/","title":{"rendered":"BS EN 61158-6-22: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 22 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.<\/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-22:2010; 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<\/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-22:2010.<\/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<\/b> Conformance<\/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 | ||||||
10<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1 Scope 1.1 General <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1.2 Specifications 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Terms and definitions from other ISO\/IEC standards 3.2 Fieldbus application-layer specific definitions <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.3 Abbreviations and symbols <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 3.4 Conventions <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4 Application layer protocol specification 4.1 Operating principle Tables Table 1\u00a0\u2013\u00a0PDU element definition Table\u00a02\u00a0\u2013\u00a0Object definition <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4.2 Device reference models <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figures Figure 1\u00a0\u2013\u00a0RTFL device reference model <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4.3 Application layer structure 5 FAL syntax description 5.1 Introduction and coding principles 5.2 Data type encoding Figure 2\u00a0\u2013\u00a0RTFN device reference model <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 3\u00a0\u2013\u00a0Encoding of TimeOfDay value Table 3\u00a0\u2013\u00a0Transfer syntax for bit sequences <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 4\u00a0\u2013\u00a0Encoding of TimeDifference value <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Table 4\u00a0\u2013\u00a0Transfer syntax for Integer data type Table 5\u00a0\u2013\u00a0Transfer syntax for Unsigned data type <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.3 CeS encoding Table 6\u00a0\u2013\u00a0Object dictionary structure <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figure 5\u00a0\u2013\u00a0Object dictionary addressing schema Table 7\u00a0\u2013\u00a0Object dictionary object type definitions <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table 8\u00a0\u2013\u00a0Basic data type definitions <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Table 9\u00a0\u2013\u00a0Complex data type definition <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table 10\u00a0\u2013\u00a0Communication section <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Table 11\u00a0\u2013\u00a0Device type Table 12\u00a0\u2013\u00a0Error register encoding Table 13\u00a0\u2013\u00a0Error register <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table 14\u00a0\u2013\u00a0Object definition template Table 15\u00a0\u2013\u00a0Encoding of event log entries <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Table 16\u00a0\u2013\u00a0Event log Table 17\u00a0\u2013\u00a0Manufacturer device name <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 18\u00a0\u2013\u00a0Manufacturer HW version Table 19\u00a0\u2013\u00a0Manufacturer SW version Table 20\u00a0\u2013\u00a0CL configuration <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table 21\u00a0\u2013\u00a0Time sync IRQ configuration encoding Table 22\u00a0\u2013\u00a0Time sync IRQ configuration <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 23\u00a0\u2013\u00a0Time sync IRQ state <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table 24\u00a0\u2013\u00a0Store parameters read information Table 25\u00a0\u2013\u00a0Store parameters <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table 26\u00a0\u2013\u00a0Restore parameters read information Table 27\u00a0\u2013\u00a0Restore default parameters <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Table 28\u00a0\u2013\u00a0Diagnostic information <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 29\u00a0\u2013\u00a0Diagnostic threshold <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 30\u00a0\u2013\u00a0IP address EMCY <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table 31\u00a0\u2013\u00a0Inhibit time EMCY Table 32\u00a0\u2013\u00a0Encoding of consumer heartbeat entries <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table 33\u00a0\u2013\u00a0Consumer heartbeat list Table 34\u00a0\u2013\u00a0Producer heartbeat parameter <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 35\u00a0\u2013\u00a0Identity object <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table 36\u00a0\u2013\u00a0SDO protocol timeout Table 37\u00a0\u2013\u00a0Enable client SDO parameter <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table 38\u00a0\u2013\u00a0Enable EMCY Table 39\u00a0\u2013\u00a0PDO timeout tolerance Table 40\u00a0\u2013\u00a0Store EDS <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table 41\u00a0\u2013\u00a0Storage format Table 42\u00a0\u2013\u00a0OS command <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 43\u00a0\u2013\u00a0OS command mode <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Table 44\u00a0\u2013\u00a0OS debugger interface <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 45\u00a0\u2013\u00a0OS prompt <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table 46\u00a0\u2013\u00a0Module list Table 47\u00a0\u2013\u00a0Emergency subscriber encoding Table 48\u00a0\u2013\u00a0Emergency subscriber <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 49\u00a0\u2013\u00a0Client SDO parameter encoding Table 50\u00a0\u2013\u00a0Client SDO parameter <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 51\u00a0\u2013\u00a0Receive PDO communication parameter <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 52\u00a0\u2013\u00a0Transmit PDO communication parameter <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 53\u00a0\u2013\u00a0Mapping format Table 54\u00a0\u2013\u00a0Receive PDO mapping parameter <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 55\u00a0\u2013\u00a0Transmit PDO mapping parameter <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 56\u00a0\u2013\u00a0Initiate SDO expedited download request Table 57\u00a0\u2013\u00a0Initiate SDO expedited download response Table 58\u00a0\u2013\u00a0Initiate SDO normal download request <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Table 59\u00a0\u2013\u00a0Initiate SDO normal download response Table 60\u00a0\u2013\u00a0SDO download request Table 61\u00a0\u2013\u00a0SDO download response <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 62\u00a0\u2013\u00a0Initiate SDO expedited upload request Table 63\u00a0\u2013\u00a0Initiate SDO expedited upload response Table 64\u00a0\u2013\u00a0Initiate SDO normal upload response <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 65 \u2013 SDO upload request Table 66\u00a0\u2013\u00a0SDO upload response Table 67\u00a0\u2013\u00a0SDO abort request Table 68\u00a0\u2013\u00a0SDO abort codes <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 69\u00a0\u2013\u00a0Process data write request via MSC <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 70\u00a0\u2013\u00a0Process data write request via CDC Table 71\u00a0\u2013\u00a0Emergency request Table 72\u00a0\u2013\u00a0Emergency error codes <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 73\u00a0\u2013\u00a0Heartbeat request via MSC Table 74\u00a0\u2013\u00a0Heartbeat request via CDC <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 5.4 ISO\/IEC 8802-3 DLPDU communication inside Type 22 RTFL 5.5 Management encoding 6 FAL protocol state machines Figure 6\u00a0\u2013\u00a0Relationships among protocol machines and adjacent layers Table 75\u00a0\u2013\u00a0Send frame request Table 76\u00a0\u2013\u00a0Application layer management request <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 6.1 Overview <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 6.2 Fieldbus service protocol machine (FSPM) 6.3 Application relationship protocol machine (ARPM) 6.4 DLL mapping protocol machine Figure 7\u00a0\u2013\u00a0ALSM protocol machine <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 7 AP-context state machine 8 FAL service protocol machine (FSPM) 9 Application layer state machine (ALSM) 9.1 Description <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure 8\u00a0\u2013\u00a0ALSM diagram Table 77\u00a0\u2013\u00a0State transitions and management services <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 9.2 States <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 9.3 Primitive definitions Table 78\u00a0\u2013\u00a0Primitives issued by ALSM to DLL Table 79\u00a0\u2013\u00a0Primitives issued by DLL to ALSM Table 80\u00a0\u2013\u00a0Primitives issued by FSPM to ALSM Table 81\u00a0\u2013\u00a0Primitives issued by ALSM to FSPM <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 9.4 State table 9.5 AL-service forwarding depending on AL-state Table 82\u00a0\u2013\u00a0ALSM state table <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 10 DLL mapping protocol machine (DMPM) 10.1 Overview 10.2 Primitives exchanged between ALSM and DMPM Table 83\u00a0\u2013\u00a0Application layer states and communication services Table 84\u00a0\u2013\u00a0Primitives issued by ALSM to DMPM <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 85\u00a0\u2013\u00a0Primitives issued by DMPM to ALSM <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 10.3 Primitives exchanged between DLL and DMPM Table 86\u00a0\u2013\u00a0Primitives issued by DMPM to DLL <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table 87\u00a0\u2013\u00a0Primitives issued by DLL to DMPM <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 10.4 ALSM to DLL mapping Table 88\u00a0\u2013\u00a0ALSM to DLL mapping <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 22 elements<\/b><\/p>\n |