BS EN IEC 62453-302:2023 2024
$167.15
Field device tool (FDT) interface specification – Communication profile integration. IEC 61784 CPF 2
Published By | Publication Date | Number of Pages |
BSI | 2024 | 42 |
Communication Profile Family 2 (commonly known as CIPTM1) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNetTM2), CP 2/2 (EtherNet/IPTM3), and CP 2/3 (DeviceNetTM1) are defined in IEC 61784-1 and IEC 61784-2. An additional communication profile (CompoNetTM1), also based on CIPTM, is defined in [15]. This part of IEC 62453 provides information for integrating the CIPTM technology into the FDT interface specification (IEC 62453-2). This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications |
7 | English CONTENTS |
9 | FOREWORD |
11 | INTRODUCTION Figure 1 – Part 302 of the IEC 62453 series |
12 | 1 Scope 2 Normative references |
13 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Symbols and abbreviated terms |
14 | 3.3 Conventions 3.3.1 Data type names and references to data types 3.3.2 Vocabulary for requirements 4 Bus category Tables Table 1 – Protocol identifiers Table 2 – Physical layer identifiers for DeviceNet Table 3 – Physical layer identifiers for ControlNet |
15 | Table 4 – Physical layer identifiers for Ethernet/IP Table 5 – Physical layer identifiers for CompoNet Table 6 – Data link layer identifiers |
16 | 5 Access to instance and device data 6 Protocol specific behavior 7 Protocol specific usage of general data types Table 7 – Protocol specific usage of general data types |
17 | 8 Protocol specific common data types Table 8 – Simple protocol specific common data types |
19 | Table 9 – Structured protocol specific common data types |
21 | 9 Network management data types 9.1 General 9.2 Node address 9.3 Scanner/master – Bus parameter set (CIP) Table 10 – Simple fieldbus configuration data types |
23 | Table 11 – Structured fieldbus configuration data types |
29 | 10 Communication data types |
30 | Table 12 – Simple communication data types Table 13 – Structured communication data types |
32 | 11 Channel parameter data types Table 14 – Simple channel parameter data types |
33 | Table 15 – Structured channel parameter data types |
34 | 12 Device identification 12.1 Device type identification data types |
35 | 12.2 Topology scan data types 12.3 Scan identification data types Table 16 – Identification data types with protocol specific mapping Table 17 – Simple identification data types with protocol independent semantics Table 18 – Structured identification data types with protocol independent semantics |
36 | 12.4 Device type identification data types Table 19 – Simple scan identification data types Table 20 – Structured scan identification data types |
37 | Table 21 – Structured device type identification data types |
38 | Annex A (informative) Implementation hints A.1 Addressing in CompoNet DTMs Table A.1 – CompoNet relationship between Device Category, Node Address, MAC ID |
39 | A.2 Displaying addresses of CompoNet DTMs A.3 Handling of Config1 and Config2 elements in EtherNet/IP Figure A.1 – Examples of DTM naming for CompoNet |
40 | Bibliography |