BS EN 61158-6-15:2012
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 15 elements
Published By | Publication Date | Number of Pages |
BSI | 2012 | 110 |
IEC 61158-6-15:2010(E) specifies the protocol of the Type 15 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-15: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 editorial corrections.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | CONTENTS |
10 | INTRODUCTION |
11 | 1 Scope 1.1 General 1.2 Specifications |
12 | 1.3 Conformance 2 Normative references 3 Terms and definitions, abbreviations, symbols and conventions 3.1 Terms and definitions |
19 | 3.2 Abbreviations and symbols |
21 | 3.3 Conventions |
23 | 3.4 Conventions used in state machines Tables Table 1 – Conventions used for state machines |
24 | 4 Abstract syntax for client/server 5 Transfer syntax for client/server 5.1 General 5.2 Common APDU structure Figures Figure 1 – APDU Format |
26 | Figure 2 – Client to server confirmed service request Figure 3 – Normal response from server to client Figure 4 – Exception response from server to client |
27 | Figure 5 – Client to server unconfirmed service request Table 2 – Exception code |
28 | 5.3 Service-specific APDU structures Table 3 – Read discretes request Table 4 – Read discretes response |
29 | Table 5 – Read coils request Table 6 – Read coils response |
30 | Table 7 – Write single coil request Table 8 – Write single coil response |
31 | Table 9 – Write multiple coils request Table 10 – Write multiple coils response |
32 | Table 11 – Broadcast write single coil request |
33 | Table 12 – Broadcast write multiple coils request Table 13 – Read input registers request |
34 | Table 14 – Read input registers response Table 15 – Read holding registers request |
35 | Table 16 – Read holding registers response Table 17 – Write single holding register request |
36 | Table 18 – Write single holding register response Table 19 – Write multiple holding registers request |
37 | Table 20 – Write multiple holding registers response |
38 | Table 21 – Mask write holding register request Table 22 – Mask write holding register request |
39 | Table 23 – Read/Write multiple holding registers request |
40 | Table 24 – Read/Write multiple holding registers response Table 25 – Read FIFO request |
41 | Table 26 – Read FIFO response |
42 | Table 27 – Broadcast write single holding register request |
43 | Table 28 – Broadcast write multiple holding registers request |
44 | Table 29 – Read file record request |
45 | Table 30 – Read file record response |
46 | Table 31 – Write file record request |
48 | Table 32 – Write file record response |
49 | Table 33 – Read device identification request |
50 | Table 34 – Device identification categories Table 35 – Read device ID code |
51 | Table 36 – Read device identification response |
52 | Table 37 – Conformity level |
53 | 5.4 Data representation ‘on the wire’ 6 Abstract syntax for publish/subscribe Table 38 – Requested vs. returned known objects |
54 | 7 Transfer syntax for publish/subscribe 7.1 General 7.2 APDU structure Figure 6 – Publish/subscribe APDU |
55 | 7.3 Sub-message structure Table 39 – APDU structure |
56 | Table 40 – Sub-message structure Table 41 – Publish/subscribe service identifier encoding |
57 | 7.4 APDU interpretation |
58 | Table 42 – Attributes changed modally and affecting APDUs interpretations |
59 | 7.5 Service specific APDU structures Table 43 – Issue request |
60 | Figure 7 – Flags of issue request Table 44 – Meaning of issue request flags |
61 | Table 45 – Interpretation of issue |
62 | Figure 8 – Flags of heartbeat request Table 46 – Heartbeat request |
63 | Table 47 – Meaning of heartbeat request flags |
64 | Table 48 – Interpretation of heartbeat |
65 | Table 49 – VAR request |
66 | Figure 9 – Flags of VAR request Table 50 – Meaning of VAR request flags |
67 | Table 51 – Interpretation of VAR |
68 | Figure 10 – Flags of GAP request Table 52 – GAP request |
69 | Table 53 – Meaning of GAP request flags Table 54 – Interpretation of GAP |
70 | Figure 11 – Flags of ACK request Table 55 – ACK request |
71 | Table 56 – Meaning of ACK request flags Table 57 – Interpretation of ACK |
72 | Table 58 – Header request |
73 | Table 59 – Change in state of the receiver Table 60 – INFO_DST request |
74 | Figure 12 – Flags of INFO_DST request Table 61 – Meaning of INFO_DST request flags |
75 | Figure 13 – Flags of INFO_REPLY request Table 62 – INFO_REPLY request |
76 | Table 63 – Meaning of INFO_REPLY request flags |
77 | Figure 14 – Flags of INFO_SRC request Table 64 – INFO_SRC request Table 65 – Meaning of INFO_SRC request flags |
78 | Table 66 – INFO_TS request |
79 | Figure 15 – Flags of INFO_TS request Table 67 – Meaning of INFO_TS request flags |
80 | Figure 16 – Flags of PAD request Table 68 – PAD request Table 69 – Meaning of PAD request flags |
81 | 7.6 Common data representation for publish/subscribe Table 70 – Semantics |
82 | Figure 17 – Encoding of octet Figure 18 – Encoding of boolean Figure 19 – Encoding of unsigned short Figure 20 – Encoding of unsigned long |
83 | Figure 21 – Encoding of unsigned long long Figure 22 – Encoding of float Figure 23 – Encoding of double |
85 | 8 Structure of FAL protocol state machines |
86 | Figure 24 – Relationships among protocol machines and adjacent layers |
87 | 9 AP-context state machines for client/server 10 FAL service protocol machine (FSPM) for client/server 10.1 General 10.2 FSPM state tables Figure 25 – State transition diagram of FSPM |
88 | Figure 26 – Transaction state machine, per connection |
89 | Table 71 – FSPM state table – client transactions |
94 | 10.3 Functions used by FSPM 10.4 Parameters of FSPM/ARPM primitives 10.5 Client/server server transactions Table 72 – FSPM state table – server transactions Table 73 – Function MatchInvokeID() Table 74 – Function HighBit() Table 75 – Parameters used with primitives exchanged between FSPM and ARPM |
95 | Figure 27 – Client/server server transactions |
96 | 11 Application relationship protocol machines (ARPMs) for client/server 11.1 Application relationship protocol machines (ARPMs) Figure 28 – State transition diagram of the Client ARPM Table 76 – Client ARPM states Table 77 – Client ARPM state table Table 78 – Server ARPM states |
97 | 11.2 AREP state machine primitive definitions Figure 29 – State transition diagram of the server ARPM Table 79 – Server ARPM state table Table 80 – Primitives issued from ARPM to DMPM Table 81 – Primitives issued by DMPM to ARPM |
98 | 11.3 AREP state machine functions 12 DLL mapping protocol machine (DMPM) for client/server 12.1 AREP mapping to data link layer Table 82 – Parameters used with primitives exchanged between ARPM and DMPM |
99 | 12.2 DMPM states 12.3 DMPM state machine Figure 30 – State transition diagram of DMPM Table 83 – DMPM state descriptions Table 84 – DMPM state table – client transactions |
100 | 12.4 Primitives exchanged between data link layer and DMPM 12.5 Client/server on TCP/IP Figure 31 – APDU Format Table 85 – DMPM state table – server transactions Table 86 – Primitives exchanged between data-link layer and DMPM |
101 | Figure 32 – TCP/IP PDU Format Table 87 – Encapsulation parameters for client/server on TCP/IP |
104 | 13 AP-Context state machines for publish/subscribe 14 Protocol machines for publish/subscribe 14.1 General |
105 | Figure 33 – Publish/subscribe receiver |
106 | 14.2 Publish/subscribe on UDP |
107 | Bibliography |