{"id":454366,"date":"2024-10-20T09:35:08","date_gmt":"2024-10-20T09:35:08","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-62453-3022023-tc-2024\/"},"modified":"2024-10-26T17:47:36","modified_gmt":"2024-10-26T17:47:36","slug":"bs-en-iec-62453-3022023-tc-2024","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-62453-3022023-tc-2024\/","title":{"rendered":"BS EN IEC 62453-302:2023 – TC 2024"},"content":{"rendered":"
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
49<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | INTRODUCTION Figure 1 \u2013 Part 302 of the IEC 62453 series <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 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 \u2013 Protocol identifiers Table 2 \u2013 Physical layer identifiers for DeviceNet Table 3 \u2013 Physical layer identifiers for ControlNet <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 4 \u2013 Physical layer identifiers for Ethernet\/IP Table 5 \u2013 Physical layer identifiers for CompoNet Table 6 \u2013 Data link layer identifiers <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 5 Access to instance and device data 6 Protocol specific behavior 7 Protocol specific usage of general data types Table 7 \u2013 Protocol specific usage of general data types <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 8 Protocol specific common data types Table 8 \u2013 Simple protocol specific common data types <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 9 \u2013 Structured protocol specific common data types <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 9 Network management data types 9.1 General 9.2 Node address 9.3 Scanner\/master \u2013 Bus parameter set (CIP) Table 10 \u2013 Simple fieldbus configuration data types <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table 11 \u2013 Structured fieldbus configuration data types <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 10 Communication data types <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 12 \u2013 Simple communication data types Table 13 \u2013 Structured communication data types <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 11 Channel parameter data types Table 14 \u2013 Simple channel parameter data types <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 15 \u2013 Structured channel parameter data types <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 12 Device identification 12.1 Device type identification data types <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 12.2 Topology scan data types 12.3 Scan identification data types Table 16 \u2013 Identification data types with protocol specific mapping Table 17 \u2013 Simple identification data types with protocol independent semantics Table 18 \u2013 Structured identification data types with protocol independent semantics <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 12.4 Device type identification data types Table 19 \u2013 Simple scan identification data types Table 20 \u2013 Structured scan identification data types <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 21 \u2013 Structured device type identification data types <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Annex A (informative) Implementation hints A.1 Addressing in CompoNet DTMs Table A.1 \u2013 CompoNet relationship between Device Category, Node Address, MAC ID <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | A.2 Displaying addresses of CompoNet DTMs A.3 Handling of Config1 and Config2 elements in EtherNet\/IP Figure A.1 \u2013 Examples of DTM naming for CompoNet <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Field device tool (FDT) interface specification – Communication profile integration. IEC 61784 CPF 2<\/b><\/p>\n |