{"id":244918,"date":"2024-10-19T16:06:03","date_gmt":"2024-10-19T16:06:03","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-clc-iec-tr-62453-52-312019\/"},"modified":"2024-10-25T11:05:38","modified_gmt":"2024-10-25T11:05:38","slug":"bsi-pd-clc-iec-tr-62453-52-312019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-clc-iec-tr-62453-52-312019\/","title":{"rendered":"BSI PD CLC IEC\/TR 62453-52-31:2019"},"content":{"rendered":"
This part of the IEC 62453-52-xy series, which is a Technical Report, provides information for integrating the PROFIBUS1 technology into the CLI-based implementation of FDT interface specification (IEC TR 62453-42). This part of IEC 62453 specifies implementation of communication and other services based on IEC 62453-303-1. This document neither contains the FDT specification nor modifies it.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | INTRODUCTION Figures Figure 1 \u2013 Part 52-31 of the IEC 62453 series <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
15<\/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 Datatype names and references to datatypes 3.3.2 Vocabulary for requirements 3.3.3 Use of UML 4 Bus category <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 5 Access to instance and device data 5.1 General 5.2 IO signals provided by DTM 5.3 Data interfaces 5.3.1 General 5.3.2 Mapping of PROFIBUS datatypes to FDT datatypes Tables Table 1 \u2013 Mapping of datatypes <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.3.3 SemanticInfo Table 2 \u2013 Usage of general datatypes <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 6 Protocol specific behaviour 6.1 PROFIBUS device model <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 6.2 Configuration and parameterization of PROFIBUS devices 6.2.1 General Figure 2 \u2013 FDT PROFIBUS Device Model <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 6.2.2 Monolithic DTM for a modular PROFIBUS device 6.2.3 Composite DTM for a modular PROFIBUS device <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.3 Support for DP-V0 configuration 6.4 PROFIBUS slaves operating without a class 1 PROFIBUS master 6.5 PROFIBUS-related information of a slave DTM 6.5.1 General <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.5.2 PROFIBUS Network Data (PND) <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Table 3 \u2013 PROFIBUS Network Information <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 6.5.3 GSD Information <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 6.5.4 Process Data Items 7 Protocol specific usage of general datatypes 7.1 General datatypes <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 7.2 Protocol specific handling of the datatype STRING 8 Network management datatypes 8.1 General Figure 3 \u2013 ProfibusNetworkData Table 4 \u2013 Protocol specific usage of general datatypes <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 8.2 Configuration 8.3 Process Data Items 8.4 Parameterization <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 9 Communication datatypes 9.1 General 9.2 ProfibusAbortMessage 9.3 DP-V0 Communication 9.3.1 General Figure 4 \u2013 ProfibusAbortMessage Table 5 \u2013 ProfibusAbortMessage datatype <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 9.3.2 Dpv0ConnectRequest Table 6 \u2013 Availability of services for Master Class 1 (C1) Table 7 \u2013 Availability of services for Master Class 2 (C2) <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 9.3.3 Dpv0ConnectResponse Figure 5 \u2013 Dpv0ConnectRequest Figure 6 \u2013 Dpv0ConnectResponse Table 8 \u2013 Dpv0ConnectRequest datatype <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 9.3.4 Dpv0DisconnectRequest 9.3.5 Dpv0DisconnectResponse Figure 7 \u2013 Dpv0DisconnectRequest Figure 8 \u2013 Dpv0DisconnectResponse Table 9 \u2013 Dpv0ConnectResponse datatype Table 10 \u2013 Dpv0DisconnectRequest datatype <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 9.3.6 Dpv0TransactionRequest Figure 9 \u2013 Dpv0ReadConfigurationDataRequest Table 11 \u2013 Dpv0DisconnectResponse datatype Table 12 \u2013 Dpv0ReadConfigurationDataRequest datatype <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 10 \u2013 Dpv0ReadDiagnosisDataRequest Figure 11 \u2013 Dpv0ReadInputDataRequest Table 13 \u2013 Dpv0ReadDiagnosisDataRequest datatype <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 12 \u2013 Dpv0ReadOutputDataRequest Table 14 \u2013 Dpv0ReadInputDataRequest datatype Table 15 \u2013 Dpv0ReadOutputDataRequest datatype <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure 13 \u2013 Dpv0ReadUserParameterRequest Figure 14 \u2013 Dpv0WriteOutputDataRequest Table 16 \u2013 Dpv0ReadUserParameterRequest datatype <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 9.3.7 Dpv0TransactionResponse Figure 15 \u2013 Dpv0WriteUserParameterRequest Table 17 \u2013 Dpv0WriteOutputDataRequest datatype Table 18 \u2013 Dpv0WriteUserParameterRequest datatype <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 16 \u2013 Dpv0ReadConfigurationDataResponse Table 19 \u2013 Dpv0ReadConfigurationDataResponse datatype <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 17 \u2013 Dpv0ReadDiagnosisDataResponse Figure 18 \u2013 Dpv0ReadInputDataResponse Table 20 \u2013 Dpv0ReadDiagnosisDataResponse datatype <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 19 \u2013 Dpv0ReadOutputDataResponse Table 21 \u2013 Dpv0ReadInputDataResponse datatype Table 22 \u2013 Dpv0ReadOutputDataResponse datatype <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 20 \u2013 Dpv0ReadUserParameterResponse Figure 21 \u2013 Dpv0WriteOutputDataResponse Table 23 \u2013 Dpv0ReadUserParameterResponse datatype <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 9.4 DP-V1 Communication 9.4.1 Dpv1ConnectRequest Figure 22 \u2013 Dpv0WriteUserParameterResponse Table 24 \u2013 Dpv0WriteOutputDataResponse datatype Table 25 \u2013 Dpv0WriteUserParameterResponse datatype <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 9.4.2 Dpv1ConnectResponse Figure 23 \u2013 Dpv1ConnectRequest Table 26 \u2013 Dpv1ConnectRequest datatype <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 24 \u2013 Dpv1ConnectResponse Table 27 \u2013 Dpv1ConnectResponse datatype <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 9.4.3 Dpv1DisconnectRequest 9.4.4 Dpv1DisconnectResponse Figure 25 \u2013 Dpv1DisconnectRequest Figure 26 \u2013 Dpv1DisconnectResponse Table 28 \u2013 Dpv1DisconnectRequest datatype Table 29 \u2013 Dpv1DisconnectResponse datatype <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 9.4.5 Dpv1TransactionRequest Figure 27 \u2013 Dpv1ReadRequest Table 30 \u2013 Dpv1ReadRequest datatype <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 9.4.6 Dpv1TransactionResponse Figure 28 \u2013 Dpv1WriteRequest Table 31 \u2013 Dpv1WriteRequest datatype <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure 29 \u2013 Dpv1ReadResponse Figure 30 \u2013 Dpv1WriteResponse Table 32 \u2013 Dpv1ReadResponse datatype <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 9.5 Error information provided by Communication Channel 10 Datatypes for process data information 10.1 General 10.2 ProfibusIOSignalInfo Table 33 \u2013 Dpv1WriteResponse datatype <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 11 Device identification 11.1 General Figure 31 \u2013 ProfibusIOSignalInfo Table 34 \u2013 ProfibusIOSignalInfo datatype <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 11.2 ProfibusDeviceScanInfo datatype 11.2.1 General Figure 32 \u2013 ProfibusDeviceScanInfo <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 11.2.2 Datatypes derived from ProfibusBaseScanInfo Figure 33 \u2013 Datatypes derived from ProfibusBaseScanInfo Table 35 \u2013 ProfibusDeviceScanInfo datatype <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 36 \u2013 Datatypes derived from ProfibusBaseScanInfo <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 11.3 ProfibusDeviceIdentInfo datatype 11.3.1 General Figure 34 \u2013 ProfibusDeviceIdentInfo <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 11.3.2 Datatypes derived from ProfibusBaseIdentInfo Figure 35 \u2013 Datatypes derived from ProfibusBaseIdentInfo Table 37 \u2013 ProfibusDeviceIdentInfo datatype <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 38 \u2013 Datatypes derived from ProfibusBaseIdentInfo <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 11.4 Mapping of Information Source <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table 39 \u2013 Profile specific mapping of identity information <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Field device tool (FDT) interface specification – Communication implementation for common language infrastructure. IEC 61784 CP 3\/1 and CP 3\/2<\/b><\/p>\n |