{"id":422715,"date":"2024-10-20T06:42:33","date_gmt":"2024-10-20T06:42:33","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-6-42019-2\/"},"modified":"2024-10-26T12:34:43","modified_gmt":"2024-10-26T12:34:43","slug":"bs-en-iec-61158-6-42019-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-6-42019-2\/","title":{"rendered":"BS EN IEC 61158-6-4:2019"},"content":{"rendered":"
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 part of IEC 61158 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 4 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 International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 4 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 document is to define the protocol provided to<\/p>\n
define the wire-representation of the service primitives defined in IEC 61158-5-4, and<\/p>\n<\/li>\n
define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n
This document specifies the protocol of the Type 4 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO\/IEC 7498-1) and the OSI application layer structure (ISO\/IEC 9545).<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1 Scope 1.1 General 1.2 Specifications <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1.3 Conformance 2 Normative references 3 Terms, definitions, symbols, abbreviations and conventions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.1 Referenced terms and definitions 3.1.1 ISO\/IEC 7498-1 terms 3.1.2 ISO\/IEC 8822 terms 3.1.3 ISO\/IEC 9545 terms 3.1.4 ISO\/IEC 8824-1 terms 3.1.5 Fieldbus data-link layer terms <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 3.2 Abbreviations and symbols 3.3 Conventions 3.3.1 General concept <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 3.3.2 Conventions for state machines for Type 4 Figures Figure 1 \u2013 State transition diagram Tables Table 1 \u2013 State machine description elements <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4 FAL syntax description 4.1 FAL-AR PDU abstract syntax 4.1.1 General 4.1.2 Abstract syntax of APDU header Table 2 \u2013 APDU header <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.1.3 Abstract syntax of APDU body <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Table 3 \u2013 APDU body <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4.2 Data types 5 Transfer syntaxes 5.1 APDU encoding 5.1.1 APDU Header encoding Figure 2 \u2013 APDU header structure <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figure 3 \u2013Subfields of ControlStatus for Request Figure 4 \u2013 Subfields of ControlStatus for Response with error <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.1.2 APDU body encoding Figure 5 \u2013 Subfields of ControlStatus for Response with no error Figure 6 \u2013 DataFieldFormat encoding <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 7 \u2013 Structure of request APDU body Figure 8 \u2013 Structure of response APDU body Figure 9 \u2013 Variable identifier Figure 10 \u2013 Code subfield of variable identifier <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.2 Variable object encoding and packing 5.2.1 Encoding of simple variables <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.2.2 Encoding of constructed variables Figure 11 \u2013 Sequence of data in the APDU body subfield <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.2.3 Alignment Figure 12 \u2013 MSG consists of APDU header and APDU body <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.2.4 Variable object attributes Table 4 \u2013 Transfer syntax for Array Table 5 \u2013 Transfer syntax for Structure Table 6 \u2013 Common variable object attributes <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.3 Error codes Table 7 \u2013 Variable type identifiers Table 8 \u2013 FIFO variable object attributes <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 6 FAL protocol state machines Table 9 \u2013 Error codes <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 7 AP-context state machine Figure 13 \u2013 Summary of FAL architecture <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 8 FAL service protocol machine (FSPM) 8.1 Primitives exchanged between FAL User and FSPM 8.2 FSPM states 8.2.1 General 8.2.2 FSPM proxy object states Table 10 \u2013 Primitives exchanged between FAL-User and FSPM <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure 14 \u2013 FSPM proxy object state machine Table 11 \u2013 REQUEST.req FSPM constraints <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table 12 \u2013 REQUEST.req FSPM actions <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Table 13 \u2013 RESPONSE.cnf FSPM constraints <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 14 \u2013 RESPONSE.cnf FSPM actions <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 8.2.3 FSPM real object state machine description Table 15 \u2013 AR Send.ind proxy FSPM constraints Table 16 \u2013 AR Send.ind proxy FSPM actions <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 15 \u2013 FSPM real object state machine Table 17 \u2013 AR Send.ind real FSPM constraints Table 18 \u2013 AR Send.ind real FSPM Actions <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 9 Application relationship protocol machine (ARPM) 9.1 Primitives exchanged between ARPM and FSPM 9.2 ARPM States 9.2.1 General 9.2.2 Sender state transitions Figure 16 \u2013 ARPM state machine Table 19 \u2013 Primitives issued by FSPM to ARPM Table 20 \u2013 Primitives issued by ARPM to FSPM Table 21 \u2013 Primitives issued by ARPM to ARPM <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 9.2.3 Receiver state transitions Table 22 \u2013 AR Send.req ARPM constraints Table 23 \u2013 AR Send.req ARPM actions Table 24 \u2013 AR Acknowledge.req ARPM constraints Table 25 \u2013 AR Acknowledge.req ARPM actions <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 10 DLL mapping protocol machine (DMPM) 10.1 Data-link Layer service selection 10.1.1 General 10.1.2 DL-UNITDATA request 10.1.3 DL-UNITDATA indication 10.1.4 DL-UNITDATA response 10.1.5 DLM-Set primitive and parameters 10.1.6 DLM-Get primitive and parameters 10.2 Primitives exchanged between ARPM and DLPM Table 26 \u2013 AR Send.ind ARPM constraints Table 27 \u2013 AR Send.req ARPM actions <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 10.3 Primitives exchanged between DLPM and data-link layer 10.4 DLPM states 10.4.1 States Figure 17 \u2013 DLPM state machine Table 28 \u2013 Primitives issued by ARPM to DLPM Table 29 \u2013 Primitives issued by DLPM to ARPM Table 30 \u2013 Primitives issued by DLPM to data-link layer Table 31 \u2013 Primitives issued by data-link layer to DLPM <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 10.4.2 Sender state transitions Table 32 \u2013 AR Send.req DLPM constraints Table 33 \u2013 AR Send.req DLPM actions Table 34 \u2013 AR Acknowledge.req DLPM constraints <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 10.4.3 Receiver state transitions 11 Protocol options Table 35 \u2013 AR Acknowledge.req DLPM actions Table 36 \u2013 DL-UNITDATA.ind DLPM constraints Table 37 \u2013 DL-UNITDATA.ind DLPM actions <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 4 elements<\/b><\/p>\n |