IEC PAS 62453-1:2006
Superseded
A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.
View Superseded by
Field Device Tool (FDT) interface specification - Part 1: Concepts and detailed description
Hardcopy , PDF , PDF 3 Users , PDF 5 Users , PDF 9 Users
30-06-2009
IEC 62453-302:2016
IEC TR 62453-502:2009
IEC TR 62453-506:2009
IEC TR 62453-501:2009
IEC TR 62453-509:2009
IEC TR 62453-515:2009
IEC 62453-301:2009+AMD1:2016 CSV
IEC TR 62453-503-1:2009
IEC TR 62453-503-2:2009
IEC TR 62453-61:2009
IEC TR 62453-41:2016
IEC 62453-306:2009
IEC 62453-309:2016
IEC 62453-315:2009+AMD1:2016 CSV
IEC 62453-2:2016
IEC 62453-303-1:2009+AMD1:2016 CSV
IEC 62453-303-2:2009+AMD1:2016 CSV
IEC 62453-1:2016
English
24-05-2006
FOREWORD
INTRODUCTION
1 Scope
1.1 Performance
1.2 Audience
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Concept
5.1 Status
5.2 State of the art
5.3 Aims
5.4 Technological orientation
5.5 Solution concept
5.6 Migration to Device Type Manager (DTM)
6 FDT fundamentals
6.1 FDT overview
6.2 Where FDT fits
6.3 General FDT architecture and components
6.4 Overview of objects and interfaces
6.5 Synchronization and serialization issues
6.6 Parameter interchange via XML
6.7 Persistent storage story
6.8 Basic features of a session model
6.9 Basic operation phases
6.10 Abstract FDT object model
6.11 Fieldbus independent integration
6.12 Scanning and DTM assignment
7 FDT version interoperability guidance
7.1 Overview
7.2 General
7.3 Component interoperability
7.4 FDT type library
7.5 DTM and device versions
7.6 Persistence
7.7 Nested communication
7.8 Implementation hints
8 FDT interface specification
8.1 Overview of the FDT interfaces
8.2 FDT objects
8.3 Device Type Manager
8.4 DTM ActiveXControl
8.5 FDT Channel
8.6 Channel ActiveXControl
8.7 Block Type Manager
8.8 BTM ActiveXControl
8.9 Frame Application
8.10 General concepts
9 FDT session model and use cases
9.1 Actors
9.2 Use cases
9.3 DTM use case realization
9.4 Frame Application use case realization
10 FDT sequence charts
10.1 DTM peer to peer communication
10.2 Nested communication
10.3 Topology scan
10.4 Registration of protocol specific FDT schemas
10.5 Configuration of a fieldbus master
10.6 Starting and releasing applications
10.7 Channel access
10.8 DCS Channel assignment
10.9 Printing of DTM specific documents
10.10 Printing of frame application specific documents
10.11 Propagation of changes
10.12 Locking
10.13 Instantiation and release
10.14 Persistent storage of a DTM
10.15 Audit trail
10.16 Comparison of two instance data sets
10.17 Failsafe data access
10.18 Set or modify device address with user interface
10.19 Set or modify known device addresses without user
interface
10.20 Display or modify all child device addresses with user
interface
10.21 Device initiated data transfer
10.22 Starting and releasing DTM user interface in modal dialog
10.23 Parent component handling redundant slave
10.24 Initialization of a channel ActiveX control
10.25 DTM upgrade
10.26 Usage of IDtmSingleDeviceDataAccess::
ReadRequest/WriteRequest
10.27 Instantiation of DTM and BTM
11 Installation issues
11.1 Registry and device information
12 Description of data types, parameters and structures
12.1 Ids
12.2 Data type definitions
Annex A (normative) FDT IDL
Annex B (normative) FDT XML schemas
B.1 FDTDataTypesSchema
B.2 FDTApplicationIdSchema
B.3 FDTUserInformationSchema
B.4 DTMInformationSchema
B.5 DTMFunctionCallSchema
B.6 DTMParameterSchema
B.7 DTMDocumentationSchema
B.8 DTMProtocolsSchema
B.9 DTMSystemTagListSchema
B.10 DTMAuditTrailSchema
B.11 DTMDeviceStatusSchema
B.12 DTMFunctionsSchema
B.13 DTMChannelFunctionsSchema
B.14 DTMOnlineCompareSchema
B.15 FDTFailSafeDataSchema
B.16 DTMTopologyScanSchema
B.17 FDTOperationPhaseSchema
B.18 DTMInitSchema
B.19 FDTUserMessageSchema
B.20 DTMInfoListSchema
B.21 FDTTopologyImportExportSchema
B.22 DTMDeviceListSchema
B.23 DTMSystemGuiLabelSchema
B.24 DTMStateSchema
B.25 DTMEnvironmentSchema
B.26 FDTConnectResponseSchema
B.27 TypeRequestSchema
B.28 FDTScanRequestSchema
B.29 FDTxxxIdentSchema
B.30 FDTxxxDeviceTypeIdentSchema
B.31 FDTxxxScanIdentSchema
B.32 DTMIdentSchema
B.33 DTMScanIdentSchema
B.34 DTMDeviceTypeIdentSchema
B.35 DTMItemListSchema
B.36 BtmDataTypesSchema
B.37 BtmInformationSchema
B.38 BtmParameterSchema
B.39 BtmInitSchema
B.40 BtmInfoListSchema
Annex C (informative) FDT XML Styles - Documentation
Annex D (normative) FDT XSL Transformation
D.1 Identification transformation
D.2 Hint:
Annex E (normative) Channel schema
E.1 FDT Basic Channel Parameter Schema
E.2 Template for Channel Schema
Annex F (informative) History - List of changes
BIBLIOGRAPHY
Figures
Tables
includes the engineering and commissioning of field devices. Functionality for documentation and audit trail support is also considered. Examples and use cases are mainly given for actors, sensors and remote I/Os. Of course, FDT is prepared to be used for devices like drives, analyzers, recorders, etc. as well. The FDT interfaces are designed in such a way as to support all significant fieldbus protocols. The main focus of this version of FDT does not lie on any specific fieldbus protocol. Due to the scalable structure of FDT it will be easy to add new schemas in order to extend the scope to new protocols.
DocumentType |
Miscellaneous Product
|
Pages |
351
|
PublisherName |
International Electrotechnical Committee
|
Status |
Superseded
|
SupersededBy |
|
Standards | Relationship |
NEN NPR IEC/PAS 62453-1 : 2006 | Identical |
08/30179977 DC : DRAFT MAR 2008 | BS EN 62453-302 - FIELD DEVICE TOOL INTERFACE SPECIFICATION - PART 302: COMMUNICATION PROFILE INTEGRATION - IEC 61784 CPF 2 |
ISO/IEC 19501:2005 | Information technology — Open Distributed Processing — Unified Modeling Language (UML) Version 1.4.2 |
IEC 61158-5:2003 | Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 5: Application layer service definition |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.