BS EN 61158-6-9:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 9 elements
| Published By | Publication Date | Number of Pages |
| BSI | 2012 | 100 |
IEC 61158-6-9:2010(E) specifies the protocol of the Type 9 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545). It defines the protocol provided to define the wire-representation of the service primitives defined in IEC 61158-5-5:2010, and the externally visible behavior associated with their transfer. This second edition cancels and replaces the first edition published in 2007 and constitutes a technical revision. The main changes with respect to the previous edition are: corrections, in Table 32.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | CONTENTS |
| 9 | INTRODUCTION |
| 10 | 1 Scope 1.1 General 1.2 Specifications |
| 11 | 1.3 Conformance 2 Normative references 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and definitions from other ISO/IEC standards |
| 12 | 3.2 IEC/TR 61158-1 terms |
| 16 | 3.3 Abbreviations and symbols |
| 17 | 3.4 Conventions 3.5 Conventions used in state machines Tables Table 1 – Conventions used for state machines |
| 18 | 4 Abstract syntax 4.1 FAL-AR PDU abstract syntax |
| 21 | 4.2 Abstract syntax of PDUBody |
| 24 | 4.3 Type definitions for ASEs |
| 29 | 4.4 Abstract syntax of data types |
| 30 | 5 Transfer syntax 5.1.1 General 5.1.2 Coding rules Figures Figure 1 – Insertion of identification information in the FMS PDU |
| 31 | 5.1.3 Structure of the identification information Figure 2 – Identification |
| 32 | Figure 3 – Coding with identification Figure 4 – Coding without identification Figure 5 – Representation of the value true |
| 33 | Figure 6 – Representation of the value false Figure 7 – Coding of data of data type Integer16 |
| 34 | Figure 8 – Coding of data of data type Unsigned16 Figure 9 – Coding of data of data type Floating Point |
| 35 | Figure 10 – Coding of data of data type Visible String Figure 11 – Coding of data of data type Octet String |
| 36 | Figure 12 – Coding of data of type Date Table 2 – Coding for Date type |
| 37 | Figure 13 – Coding of data of data type Time-of-day Figure 14 – Coding of data of data type Time-difference |
| 38 | Figure 15 – Coding of data of data type Bit String Figure 16 – Coding of data of data type Time-value |
| 39 | Figure 17 – Coding of data of user data definitions with identifier Figure 18 – Coding of data of user data definitions without identifier Figure 19 – Coding of ID info for a SEQUENCE |
| 40 | 6 Structure of FAL protocol state machines |
| 41 | Figure 20 – Relationships among protocol machines and adjacent layers |
| 42 | 7 AP-Context state machines 7.1 VCR PM structure 7.2 VCR PM state machine Figure 21 – Relationships among protocol machines and adjacent layers |
| 43 | Figure 22 – VCR state machine |
| 44 | Table 3 – AP-VCR state machine transactions |
| 52 | Table 4 – Primitives issued by FAL-User to VCR PM |
| 53 | Table 5 – Primitives issued by VCR PM to FAL-User Table 6 – Primitives issued by VCR PM to FSPM |
| 54 | 8 FAL service protocol machine (FSPM) 8.1 General 8.2 FSPM state tables Figure 23 – State transition diagram of FSPM Table 7 – Primitives issued by FSPM to VCR PM |
| 55 | Table 8 – FSPM state table – sender transactions |
| 56 | Table 9 – FSPM state table – receiver transactions |
| 57 | 8.3 Functions used by FSPM 8.4 Parameters of FSPM/ARPM primitives 9 Application relationship protocol machines (ARPMs) 9.1 AREP mapping to data-link layer Table 10 – Function SelectArep() Table 11 – Parameters used with primitives exchanged between FSPM and ARPM |
| 67 | 9.2 Application relationship protocol machines (ARPMs) |
| 68 | Figure 24 – State transition diagram of the QUU ARPM Table 12 – QUU ARPM states Table 13 – QUU ARPM state table – sender transactions |
| 69 | Table 14 – QUU ARPM state table – receiver transactions |
| 70 | Figure 25 – State transition diagram of QUB ARPM Table 15 – QUB ARPM states |
| 71 | Table 16 – QUB ARPM state table – sender transactions |
| 72 | Table 17 – QUB ARPM state table – receiver transactions |
| 78 | Figure 26 – State transition diagram of the BNU ARPM Table 18 – BNU ARPM states |
| 79 | Table 19 – BNU ARPM state table – sender transactions |
| 80 | Table 20 – BNU ARPM state table – receiver transactions |
| 83 | 9.3 AREP state machine primitive definitions Table 21 – Primitives issued from ARPM to DMPM Table 22 – Primitives issued by DMPM to ARPM |
| 84 | Table 23 – Parameters used with primitives exchanged between ARPM and DMPM |
| 85 | 9.4 AREP state machine functions Table 24 – Function GetArepId() Table 25 – Function BuildFAS-PDU Table 26 – Function FAS_Pdu_Type Table 27 – Function AbortIdentifier Table 28 – Function AbortReason |
| 86 | 10 DLL mapping protocol machine (DMPM) 10.1 DMPM States 10.2 DMPM state table Figure 27 – State transition diagram of DMPM Table 29 – Function AbortDetail Table 30 – DMPM state descriptions |
| 87 | Table 31 – DMPM state table – sender transactions |
| 89 | Table 32 – DMPM state table – receiver transactions |
| 93 | 10.3 Primitives exchanged between data-link layer and DMPM |
| 94 | Table 33 – Primitives exchanged between data-link layer and DMPM |
| 96 | 10.4 Functions used by DMPM Table 34 – Function PickArep |
| 97 | Table 35 – Function FindAREP Table 36 – Function LocateQubArep Table 37 – Function SetIdentifier() |
| 98 | Bibliography |
