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