{"id":245559,"date":"2024-10-19T16:09:06","date_gmt":"2024-10-19T16:09:06","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-clc-tr-62453-51-202019-tc\/"},"modified":"2024-10-25T11:09:26","modified_gmt":"2024-10-25T11:09:26","slug":"bsi-pd-clc-tr-62453-51-202019-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-clc-tr-62453-51-202019-tc\/","title":{"rendered":"BSI PD CLC\/TR 62453-51-20:2019 – TC"},"content":{"rendered":"
IEC TR 62453-51?20:2017(E) provides information for integrating the CIP\u2122 technology into the COM-based implementation of FDT interface specification (IEC TR 62453-41). The Communication Profile Family 2 (commonly known as CIP\u2122 defines communication profiles based on IEC 61158?2 Type 2, IEC 61158?3?2, IEC 61158?4?2, IEC 61158?5?2, and IEC 61158?6?2, IEC 62026?3. The basic profiles CP 2\/1 (ControlNet\u2122, CP 2\/2 (EtherNet\/IP\u2122, and CP 2\/3 (DeviceNet\u21221) are defined in IEC 61784?1 and IEC 61784?2. An additional communication profile (CompoNet\u2122),also based on CIP\u2122, is defined in [15]. This document specifies implementation of communication and other services based on IEC 62453?302. <\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
39<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | INTRODUCTION Figure 1 \u2013 Part 51-20 of the IEC 62453 series <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Symbols and abbreviated terms 3.3 Conventions 3.3.1 Data type names and references to data types 3.3.2 Vocabulary for requirements <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 4 Bus category 5 Access to instance and device data 6 Protocol specific behaviour 7 Protocol specific usage of general data types Table 1 \u2013 Protocol specific usage of general attributes <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 8 Protocol specific common data types 8.1 Common data types \u2013 DTMCIPDataTypeSchema <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 8.2 Data types for Ethernet\/IP \u2013 DTMEIPDataTypeSchema <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 9 Network management data types 9.1 General 9.2 Node address 9.3 Scanner\/Master \u2013 Bus Parameter Set (CIP) \u2013 FDTCIPDTMParameterSchema <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 10 Communication data types <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 11 Channel parameter data types <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 12 Device identification 12.1 Device type identification data types \u2013 FDTCIPIdentSchema <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 12.2 Topology scan data types 12.3 Scan identification data types \u2013 FDTCIPScanIdentSchema 12.4 Device type identification data types \u2013 FDTCIPDeviceTypeIdentSchema <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Annex A (informative) Implementation hints A.1 XML Characters A.2 Support for FDT 1.2 A.3 Addressing examples in CompoNet DTMs <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | A.4 Unique identification of a connection A.5 Relation between connections and device internal modularity <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | A.6 Handling of process channels <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | A.7 Identification of Modules in Modular Devices <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Field device tool (FDT) interface specification – Communication implementation for common object model. IEC 61784 CPF 2<\/b><\/p>\n |