BS EN 62453-315:2009+A1:2017:2018 Edition
$198.66
Field device tool (FDT) interface specification – Communication profile integration. IEC 61784 CPF 15
Published By | Publication Date | Number of Pages |
BSI | 2018 | 62 |
Communication Profile Family 15 (commonly known as Modbus1) defines communication profiles based on IEC 61158-5-15 and IEC 61158-6-15. The basic profile CP 15/1 (Modbus TCP) is defined in IEC 61784-1. An additional communication profile (Modbus Serial Line) is defined in [2].
This part of the IEC 62453 provides information for integrating Modbus TCP® and Modbus Serial Line® protocol support into FDT based systems.
NOTE This part of IEC 62453 only specifies the mapping of Modbus parameters to FDT data types. For restrictions of protocol specific parameters concerning allowed values and concerning limitations of arrays used in the definition of FDT data types, refer to IEC 61158-5-15 and the MODBUS Application Protocol Specification.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
4 | European Foreword Anchor 3 European foreword to amendment A1 |
5 | Annex ZA (normative) Normative references to international publications with their corresponding European publications |
8 | FOREWORD |
10 | INTRODUCTION |
13 | 1 Scope 2 Normative references 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions |
14 | 3.2 Abbreviated terms 3.3 Conventions 3.3.1 Data type names and references to data types 3.3.2 Vocabulary for requirements 4 Bus category |
16 | 5 Access to instance and device data 5.1 Process Channel objects provided by DTM 5.2 DTM services to access instance and device data 6 Protocol specific behavior 6.1 General 6.2 Broadcasting |
19 | 6.3 Unconfirmed private Modbus request |
20 | 7 Protocol specific usage of general data types |
21 | 8 Protocol specific common data types 8.1 General 8.2 Address information |
22 | 9 Network management data types 10 Communication data types 10.1 General |
23 | 10.2 Connection management data types |
24 | 10.3 Transaction service specific data types 10.3.1 General 10.3.2 Data item addressing |
25 | 10.3.3 Read coils transaction service |
26 | 10.3.4 Read discrete inputs transaction service |
27 | 10.3.5 Read holding registers transaction service |
28 | 10.3.6 Read input registers transaction service |
29 | 10.3.7 Write single coil transaction service |
30 | 10.3.8 Write single register transaction service |
31 | 10.3.9 Read exception status transaction service 10.3.10 Diagnostics transaction service |
32 | 10.3.11 Get Comm event counter transaction service |
33 | 10.3.12 Get Comm event log transaction service |
35 | 10.3.13 Write multiple coils transaction service |
36 | 10.3.14 Write multiple registers transaction service 10.3.15 Report slave ID transaction service |
37 | 10.3.16 Read file record transaction service |
39 | 10.3.17 Write file record transaction service |
40 | 10.3.18 Mask write register transaction service |
41 | 10.3.19 Read/write holding registers transaction service |
42 | 10.3.20 Read FIFO queue transaction service |
43 | 10.3.21 Encapsulated interface transport transaction service |
44 | 10.3.22 Read device identification transaction service |
47 | 10.3.23 Private Modbus transaction service |
48 | 10.3.24 Unconfirmed private Modbus transaction service |
49 | 10.3.25 Modbus exception response |
50 | 11 Channel parameter data types |
53 | 12 Device Identification 12.1 Common device type identification data types |
54 | 12.2 Topology scan data types |
55 | 12.3 Scan identification data types |
57 | 12.4 Device type identification data types — provided by DTM |
58 | 12.5 Mapping of protocol specific device identification objects to FDT data types |
60 | Bibliography |