{"id":244062,"date":"2024-10-19T16:01:39","date_gmt":"2024-10-19T16:01:39","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61158-6-202012\/"},"modified":"2024-10-25T10:59:56","modified_gmt":"2024-10-25T10:59:56","slug":"bs-en-61158-6-202012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61158-6-202012\/","title":{"rendered":"BS EN 61158-6-20: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 20 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 Type 20 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 define<\/p>\n
the wire-representation of the service primitives defined in IEC 61158-5-20, and<\/p>\n<\/li>\n
the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
This standard specifies the protocol of the Type 20 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
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-20.<\/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 IEC 61158-6.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1 Scope 1.1 General 1.2 Specifications <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1.3 Conformance 2 Normative references <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and definitions from other ISO\/IEC standards 3.2 IEC\/TR 61158-1 terms <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.3 Type 20 fieldbus application-layer specific definitions <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.4 Abbreviations and symbols <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3.5 Conventions 3.6 Conventions used in state machines Tables Table\u00a01 \u2013 Conventions used for state machines <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4 Abstract syntax 5 Transfer syntax 5.1 General <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.2 Common APDU structure Figures Figure\u00a01 \u2013 APDU format Figure\u00a02 \u2013 Normal response from slave to master <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figure\u00a03 \u2013 Command error response from slave to master Table\u00a02 \u2013 Response code values Table\u00a03 \u2013 Device status values <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.3 Service-specific APDU structures Figure\u00a04 \u2013 Communication error response from slave to master Table\u00a04 \u2013 Response code values Table\u00a05 \u2013 Communication error codes <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Table\u00a06 \u2013 Identify request APDU <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Table\u00a07 \u2013 Identify response value field Table\u00a08 \u2013 Identify command specific response codes <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Table\u00a09 \u2013 Read primary variable response value field Table\u00a010 \u2013 Read primary variable command specific response codes Table\u00a011 \u2013 Read loop current and percent of range value field <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Table\u00a012 \u2013 Read loop current and percent of range command specific response codes Table\u00a013 \u2013 Read dynamic variables and loop current value field Table\u00a014 \u2013 Read dynamic variables and loop current command specific response codes <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Table\u00a015 \u2013 Write polling address value field Table\u00a016 \u2013 Loop current mode codes Table\u00a017 \u2013 Write polling address command specific response codes <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Table\u00a018 \u2013 Read loop configuration value field Table\u00a019 \u2013 Read loop configuration command specific response codes Table\u00a020 \u2013 Read dynamic variable families classifications value field <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table\u00a021 \u2013 Read dynamic variable families classifications command specific response codes Table\u00a022 \u2013 Read device variables with status request value field Table\u00a023 \u2013 Read device variables with status value field <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table\u00a024 \u2013 Variable status values Table\u00a025 \u2013 Read device variables with status command specific response codes <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Table\u00a026 \u2013 Read message response value field Table\u00a027 \u2013 Read message command specific response codes Table\u00a028 \u2013 Read tag, descriptor, date response value field Table\u00a029 \u2013 Read tag, descriptor, date command specific response codes <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Table\u00a030 \u2013 Read primary variable transducer information response value field Table\u00a031 \u2013 Read primary variable transducer information command specific response codes <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table\u00a032 \u2013 Read device information response value field Table\u00a033 \u2013 Read device information command specific response codes Table\u00a034 \u2013 Read final assembly number response value field <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Table\u00a035 \u2013 Read final assembly number command specific response codes Table\u00a036 \u2013 Write message value field Table\u00a037 \u2013 Write message command specific response codes Table\u00a038 \u2013 Write tag, descriptor, date value field <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table\u00a039 \u2013 Write tag, descriptor, date command specific response codes Table\u00a040 \u2013 Write final assembly number value field Table\u00a041 \u2013 Write final assembly number command specific response codes <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.4 Data coding rules Table\u00a042 \u2013 Read long tag response value field Table\u00a043 \u2013 Read long tag command-specific response codes Table\u00a044 \u2013 Write long tag value field Table\u00a045 \u2013 Write long tag command specific Response codes <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure\u00a05 \u2013 Coding without identification Figure\u00a06 \u2013 Coding of Integer type data Figure\u00a07 \u2013 Coding of Integer16 type data Figure\u00a08 \u2013 Coding of Unsigned type data Figure\u00a09 \u2013 Coding of Unsigned16 type data <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure\u00a010 \u2013 Coding of single precision Floating Point type data <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure\u00a011 \u2013 Coding of double precision Floating Point type data Figure\u00a012 \u2013 Coding of Date type data Table\u00a046 \u2013 Coding for Date type <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table\u00a047 \u2013 Coding for one octet Enumerated Type <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table\u00a048 \u2013 One octet bit field Table\u00a049 \u2013 Packed ASCII character set <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 6 Structure of FAL protocol state machines Table\u00a050 \u2013 AccepTable\u00a0subset of ISO Latin-1 characters <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 7 AP-context state machines 8 FAL service protocol machine (FSPM) 8.1 General Figure\u00a013 \u2013 Relationships among protocol machines and adjacent layers <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 8.2 FSPM state tables Figure\u00a014 \u2013 State transition diagram of FSPM Table\u00a051 \u2013 FSPM state Table\u00a0\u2013 client transactions <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table\u00a052 \u2013 FSPM state Table\u00a0\u2013 server transactions <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 8.3 Functions used by FSPM 8.4 Parameters of FSPM\/ARPM primitives Table\u00a053 \u2013 Function Command () Table\u00a054 \u2013 Function CommErr () Table\u00a055 \u2013 Function CommandErr () Table\u00a056 \u2013 Function Resp () Table\u00a057 \u2013 Function Device () Table\u00a058 \u2013 Parameters used with primitives exchanged between FSPM and ARPM <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 9 Application relationship protocol machines (ARPMs) 9.1 AREP mapping to data link layer <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 9.2 Application relationship protocol machines (ARPMs) Figure\u00a015 \u2013 State transition diagram of the client ARPM Table\u00a059 \u2013 Client ARPM states <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure\u00a016 \u2013 State transition diagram of the server ARPM Table\u00a060 \u2013 Client ARPM state table Table\u00a061 \u2013 Server ARPM states Table\u00a062 \u2013 Server ARPM state table <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 9.3 AREP state machine primitive definitions 9.4 AREP state machine functions 10 DLL mapping protocol machine (DMPM) Table\u00a063 \u2013 Primitives issued from ARPM to DMPM Table\u00a064 \u2013 Primitives issued by DMPM to ARPM Table\u00a065 \u2013 Parameters used with primitives exchanged between ARPM and DMPM <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 10.1 DMPM states 10.2 DMPM state machines 10.3 Primitives exchanged between data link layer and DMPM Figure\u00a017 \u2013 State transition diagram of DMPM Table 66 \u2013 DMPM state descriptions Table\u00a067 \u2013 DMPM state Table\u00a0\u2013 Client transactions Table\u00a068 \u2013 DMPM state Table\u00a0\u2013 Server transactions <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 10.4 Functions used by DMPM Table\u00a069 \u2013 Primitives exchanged between data-link layer and DMPM <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 20 elements<\/b><\/p>\n |