This part of IEC 62453, which is a Technical report, defines how the common FDT principles are implemented based on the MS COM technology, including the object behavior and object interaction via COM interfaces. This part specifies the technology specific implementation of the protocol specific functionality and communication services. This part of IEC 62453 is informative, however when this part is applied its requirements shall be implemented as specified. This part specifies FDT version 1.2.1.

PDF Catalog

PDF Pages	PDF Title
334	undefined
339	CONTENTS
349	FOREWORD
351	INTRODUCTION Figures Figure 1 – Part 41 of the IEC 62453 series
352	1 Scope 2 Normative references 3 Terms, definitions, abbreviations and conventions 3.1 Terms and definitions
353	3.2 Abbreviations 3.3 Conventions
354	4 Implementation concept 4.1 Technological orientation 4.2 Implementation of abstract FDT object model 4.2.1 General 4.2.2 FDT Frame Application (FA)
355	4.2.3 Device Type Manager (DTM) Figure 2 − Frame Application interfaces Figure 3 − DTM interfaces
356	4.2.4 Presentation object 4.2.5 FDT-Channel object 4.3 Object interaction 4.3.1 Parameter interchange via XML Figure 4 − FDT Client/server relationship via XML
358	4.3.2 Examples of usage Figure 5 − Data access and storage
359	Figure 6 − Communication Figure 7 − Documentation
360	4.4 Implementation of DTM data persistence and synchronization 4.4.1 Persistence overview Figure 8 − Parameter verification in case of failsafe devices
361	4.4.2 Persistence interfaces 4.5 DTM state machine Figure 9 − State machine of a DTM
362	Tables Table 1 – Definition of DTM state machine
363	5 General concepts 5.1 General 5.2 Overview of task related FDT interfaces Table 2 − Task related DTM interfaces
364	Table 3 − Task related DTM ActiveX® interfaces Table 4 − Task related FDT-Channel interfaces Table 5 − Task related Channel ActiveX( interfaces
365	Table 6 − Task related BTM interfaces Table 7 − Task related BTM ActiveX( interfaces Table 8 − Task related Frame Application interfaces
366	5.3 Return values of interface methods 5.4 Dual interfaces 5.5 Unicode 5.6 Asynchronous versus synchronous behavior
367	5.7 ProgIds 5.8 Implementation of DTM, DTM device type and hardware identification information 5.8.1 Device identification Figure 10 − Device identification
369	Figure 11 − Structural overview
370	5.8.2 Protocol-specific transformation style sheet (xsl) 5.8.3 Semantic identification information 5.8.4 Device assignment Table 9 − Semantic identification information
371	5.8.5 Regular expression specification 5.9 Implementation of slave redundancy 5.9.1 General Table 10 − Regular expressions
372	5.9.2 Topology import/export 6 Implementation of FDT services: FDT interfaces 6.1 Overview of the FDT interfaces 6.2 FDT objects 6.2.1 FDT object model
373	Figure 12 − Interfaces of FDT objects – DTM and DtmActiveXControl
374	Figure 13 − Interfaces of FDT object – Frame Application Figure 14 − FDT objects – FDT-Channel
375	6.2.2 Avalability of interface methods Figure 15 − FDT objects – BTM and BtmActiveXControl
376	Table 11 − Availability of DTM methods in different states
378	Table 12 − Availability of Frame Application interfaces
379	6.3 Device Type Manager 6.3.1 Interface IDtm
388	6.3.2 Interface IDtm2
389	6.3.3 Interface IDtmActiveXInformation
391	6.3.4 Interface IDtmApplication
393	6.3.5 Interface IDtmChannel
394	6.3.6 Interface IDtmDocumentation
395	6.3.7 Interface IDtmDiagnosis
397	6.3.8 Interface IDtmImportExport
399	6.3.9 Interface IDtmInformation
400	6.3.10 Interface IDtmInformation2
401	6.3.11 Interface IDtmOnlineDiagnosis
402	6.3.12 Interface IDtmOnlineParameter
405	6.3.13 Interface IDtmParameter
406	6.3.14 Interface IFdtCommunicationEvents
409	6.3.15 Interface IFdtCommunicationEvents2
410	6.3.16 Interface IFdtEvents
413	6.3.17 Interface IDtmHardwareIdentification
415	6.3.18 Interface IDtmSingleDeviceDataAccess
418	6.3.19 Interface IDtmSingleInstanceDataAccess
420	6.4 DTM ActiveXControl 6.4.1 Interface IDtmActiveXControl 6.4.2 Init
421	6.4.3 PrepareToRelease
422	6.5 FDT Channel 6.5.1 Interface IFdtChannel
425	6.5.2 Interface IFdtChannelActiveXInformation
427	6.5.3 Interface IFdtCommunication
434	6.5.4 Interface IFdtChannelSubTopology
438	6.5.5 Interface IFdtChannelSubTopology2 6.5.6 Interface IFdtChannelScan
440	6.5.7 Interface IFdtFunctionBlockData
442	6.6 Channel ActiveXControl 6.6.1 Interface IFdtChannelActiveXControl
443	6.6.2 Interface IFdtChannelActiveXControl2
444	6.7 Block Type Manager
445	6.7.1 Interface IBtm
446	6.7.2 Interface IBtmInformation 6.7.3 Interface IBtmParameter
447	6.8 BTM ActiveXControl 6.8.1 General 6.8.2 Interface IBtmActiveXControl
448	6.9 Frame Application 6.9.1 Interface IDtmEvents
457	6.9.2 Interface IDtmEvents2
458	6.9.3 Interface IDtmScanEvents
460	6.9.4 Interface IDtmAuditTrailEvents
462	6.9.5 Interface IFdtActiveX
463	6.9.6 Interface IFdtActiveX2
466	6.9.7 Interface IFdtBulkData
468	6.9.8 Interface IFdtContainer
471	6.9.9 Interface IFdtDialog
472	6.9.10 Interface IFdtTopology
478	6.9.11 Interface IDtmRedundancyEvents
479	6.9.12 Interface IDtmSingleDeviceDataAccessEvents
482	6.9.13 Interface IDtmSingleInstanceDataAccessEvents
483	6.9.14 Interface IFdtBtmTopology
484	7 FDT sequence charts 7.1 DTM peer to peer communication 7.1.1 General 7.1.2 Establish a peer-to-peer connection between DTM and device 7.1.3 Asynchronous connect for a peer-to-peer connection Figure 16 − Peer to peer connection between DTM and device
485	7.1.4 Asynchronous disconnect for a peer-to-peer connection 7.1.5 Asynchronous transaction for a peer-to-peer connection Figure 17 − Asynchronous connect (peer to peer) Figure 18 − Asynchronous disconnect (peer to peer)
486	7.2 Nested communication 7.2.1 General Figure 19 − Asynchronous transaction (peer to peer)
487	7.2.2 Generate system topology Figure 20 − System-topology
488	Figure 21 − Generation of system topology by Frame Application
489	7.2.3 Establish a system connection between DTM and device Figure 22 – Generation of system topology – Participation of DTM
490	7.2.4 Asynchronous transaction for a system connection Figure 23 – System connection (across communication hierarchy)
491	7.3 Topology scan 7.3.1 Scan network Figure 24 − Asynchronous transactions (system connection)
492	7.3.2 Cancel topology scan Figure 25 − Scan network topology
493	7.3.3 Provisional scan result notifications Figure 26 − Cancel topology scan
494	7.3.4 Scan for communication hardware Figure 27 − Provisional topology scan
495	7.3.5 Manufacturer-specific device identification Figure 28 − Scan for communication hardware
497	7.4 Registration of protocol-specific FDT schemas Figure 29 − Manufacturer-specific device identification
498	Figure 30 − Add protocol-specific schemas to Frame Applications schema sub path
499	7.5 Configuration of a fieldbus master Figure 31 − Frame Application reads protocol-specificdevice identification information of DTMDeviceTypes
500	7.6 Starting and releasing applications Figure 32 − Bus master configuration
501	7.7 Channel access Figure 33 − Starting and releasing applications
502	7.8 DCS Channel assignment Figure 34 − Channel access
503	Figure 35 − DCS channel assignment single DTM
504	Figure 36 − Sequence of channel assignement for a single DTM
505	Figure 37 − Modular DTM structure
506	7.9 Printing of DTM-specific documents Figure 38 − Channel assignment for modular DTMs
507	7.10 Printing of Frame Application-specific documents 7.10.1 General Figure 39 − Printing of DTM-specific documents
508	7.10.2 Processing a document Figure 40 − Printing of Frame Application-specific documents
509	Figure 41 − Report generation (Frame Application style)
510	7.10.3 Rules for use of DTM-specific style sheets Figure 42 − Report generation (device vendor-specific style)
511	7.11 Propagation of changes Figure 43 − Propagation of changes
512	7.12 Locking 7.12.1 Locking for non-synchronized DTMs
513	7.12.2 Locking for synchronized DTMs Figure 44 − Locking for non-synchronized DTMs
514	Figure 45 − Locking for synchronized DTMs
515	7.13 Instantiation and release 7.13.1 Instantiation of a new DTM 7.13.2 Instantiation of an existing DTM Figure 46 − Instantiation of a new DTM
516	7.13.3 Instantiation of a DTM ActiveX( user interface 7.13.4 Release of a DTM user interface Figure 47 − Instantiation of an existing DTM Figure 48 − Instantiation of a DTM user interface
517	7.14 Persistent storage of a DTM 7.14.1 State machine of instance data Figure 49 − Release of a DTM user interface
518	Figure 50 − State machine of instance data set Table 13 – Description of instance data set states
519	7.14.2 Saving instance data of a DTM Figure 51 – Persistence states of a data set Table 14 – Description of persistent states
520	7.14.3 Reload of a DTM object for another instance 7.14.4 Copy and versioning of a DTM instance Figure 52 − Saving instance data of a DTM
521	7.15 Audit trail Figure 53 − Copy and versioning of a DTM instance
522	7.16 Comparison of two instance data sets 7.16.1 Comparison without user interface Figure 54 − Audit trail
523	7.16.2 Comparison with user interface Figure 55 − Comparison without user interface
524	7.17 Failsafe data access Figure 56 − Comparison with user interface
525	7.18 Set or modify device address with user interface Figure 57 − Failsafe data access
526	7.19 Set or modify known device addresses without user interface Figure 58 − Set or modify device address with user interface
527	7.20 Display or modify all child device addresses with user interface Figure 59 − Set or modify known device addresses without user interface
528	7.21 Device initiated data transfer Figure 60 − Display or modify all child device addresses with user interface
529	7.22 Starting and releasing DTM user interface in modal dialog Figure 61 − Device initiated data transfer
530	7.23 Parent component handling redundant slave Figure 62 − Modal DTM user interface
531	Figure 63 − Handling of a redundant slave
532	7.24 Initialization of a Channel ActiveX control 7.24.1 General 7.24.2 Supports IFdtChannelActiveXcontrol2 7.24.3 Does not support IFdtChannelActiveXControl2 Figure 64 − Init of Channel ActiveX with IFdtChannelActiveXControl2
533	7.25 DTM upgrade 7.25.1 General 7.25.2 Saving data from a DTM to be upgraded Figure 65 − Init of Channel ActiveX® without IFdtChannelActiveXControl2
534	7.25.3 Loading data in the replacement DTM Figure 66 − Saving data from a DTM to be upgraded
535	7.26 Usage of IDtmSingleDeviceDataAccess::ReadRequest / Write Request Figure 67 − Loading data in the replacement DTM
536	7.27 Instantiation of DTM and BTM Figure 68 − Usage of IDtmSingleDeviceDataAccess
537	Figure 69 − General sequence of creation and instantiation of blocks
538	8 Installation issues 8.1 Registry and device information 8.1.1 Visibility of business objects of a DTM 8.1.2 Component categories Table 15 – Component categories
539	8.1.3 Registry entries 8.1.4 Installation issues Table 16 – Combinations of categories Table 17 – Example for DTM registration
540	8.1.5 Microsoft’s standard component categories manager 8.1.6 Building a Frame Application-database of supported devices 8.1.7 DTM registration
541	8.2 Paths and file information 8.2.1 Path information provided by a DTM 8.2.2 Paths and persistency 8.2.3 Multi-user systems
542	9 Description of data types, parameters and structures 9.1 Ids 9.2 Data type definitions Table 18 – FDT-specific Ids Table 19 – Basic data types
543	Table 20 – Helper objects for documentation
544	Annex A (normative)FDT IDL
560	Annex B (normative)Mapping of services to interface methods B.1 General B.2 DTM services Table B.1 − General services Table B.2 − DTM services related to installation
561	Table B.3 − DTM services related to DTM information Table B.4 − DTM services related to DTM state machine
562	Table B.5 − DTM services related to function Table B.6 − DTM services related to documentation Table B.7 − DTM services to access the instance data
563	Table B.8 − DTM services to access diagnosis Table B.9 − DTM services to access the device data Table B.10 − DTM services related to network management information Table B.11 − DTM services related to online operation
564	B.3 Presentation object services B.4 General channel services Table B.12 − DTM services related to FDT-Channel objects Table B.13 − DTM services related to import and export Table B.14 − DTM services related to data synchronization
565	B.5 Process channel services B.6 Communication Channel Services Table B.15 − General channel services Table B.16 − Channel services for IO related information Table B.17 − Channel services related to communication
566	B.7 Frame Application Services Table B.18 − Channel services related sub-topology management Table B.19 − Channel services related to functions Table B.20 − Channel services related to scan Table B.21 − FA services related to general events
567	Table B.22 − FA services related to topology management Table B.23 − FA services related to redundancy Table B.24 − FA services related to storage of DTM data
568	Table B.25 − FA services related to DTM data synchronization Table B.26 − FA services related to presentation Table B.27 − FA services related to audit trail
569	Annex C (normative)FDT XML schemas C.1 General C.2 FDTDataTypesSchema Table C.1 – Description of general XML attributes
574	Table C.2 – Description of general XML elements
576	Table C.3 – Device classification ID
577	Table C.4 – Device classification according to IEC TR 62390:2005, Annex G
585	C.3 FDTApplicationIdSchema C.4 FDTUserInformationSchema Table C.5 – Description of applicationId attribute Table C.6 – Description of applicationId elements
586	Table C.7 – Description of user information attributes Table C.8 – Description of user information elements
587	C.5 DTMInformationSchema Table C.9 – Description of DTM information attributes Table C.10 – Description of DTM information elements
590	C.6 DTMFunctionCallSchema
591	C.7 DTMParameterSchema Table C.11 – Description of function call attributes Table C.12 – Description of parameter document attributes
592	Table C.13 – Description of parameter document elements
599	C.8 DTMDocumentationSchema
600	Table C.14 – Description of documentation attributes Table C.15 – Description of documentation elements
601	C.9 DTMProtocolsSchema
602	C.10 DTMSystemTagListSchema Table C.16 – Description of protocols element Table C.17 – Description of system tag attributes Table C.18 – Description of system tag elements
603	C.11 DTMAuditTrailSchema
604	Table C.19 – Description of audit trail attributes Table C.20 – Description of audit trail elements
605	C.12 DTMDeviceStatusSchema Table C.21 – Description of device status attribute Table C.22 – Description of device status elements
606	C.13 DTMFunctionsSchema Table C.23 – Description of function attributes
607	Table C.24 – Description of function elements
610	C.14 DTMChannelFunctionsSchema Table C.25 – Description of channel functions attributes
611	Table C.26 – Description of channel function elements
613	C.15 DTMOnlineCompareSchema Table C.27 – Description of comparison attribute Table C.28 – Description of comparison elements
614	C.16 FDTFailSafeDataSchema C.17 DTMTopologyScanSchema Table C.29 – Description of fail safe attributes Table C.30 – Description of fail safe elements
615	C.18 FDTOperationPhaseSchema Table C.31 – Description of topology scan elements Table C.32 – Description of operation phase attribute Table C.33 – Description of operation phase element
616	C.19 DTMInitSchema C.20 FDTUserMessageSchema Table C.34 – Description of DTM init element Table C.35 – Description of user message attributes
617	Table C.36 – Description of user message elements
618	C.21 DTMInfoListSchema Table C.37 – Description of DTM info list elements
619	C.22 FDTTopologyImportExportSchema Table C.38 – Description of topology attributes Table C.39 – Description of topology elements
623	C.23 DTMDeviceListSchema Table C.40 – Description of device list attributes
624	Table C.41 – Description of device list elements
625	C.24 DTMSystemGuiLabelSchema C.25 DTMStateSchema Table C.42 – Description of gui label element
626	C.26 DTMEnvironmentSchema Table C.43 – Description of DTM state element Table C.44 – Description of frame version element
627	C.27 FDTConnectResponseSchema C.28 TypeRequestSchema Table C.45 – Description of connect response element Table C.46 – Description of type request element
628	C.29 FDTScanRequestSchema Table C.47 – Description of scan request attributes Table C.48 – Description of scan request elements
629	C.30 FDTxxxIdentSchema C.31 FDTxxxDeviceTypeIdentSchema
630	C.32 FDTxxxScanIdentSchema C.33 DTMIdentSchema Table C.49 – Description of common identification attributes
631	C.34 DTMScanIdentSchema Table C.50 – Description of common identification element Table C.51 – Description of scan identification attributes Table C.52 – Description of scan identification elements
633	C.35 DTMDeviceTypeIdentSchema Table C.53 – Description of device type identification element
635	C.36 DTMItemListSchema Table C.54 – Description of item list attributes
636	Table C.55 – Description of item list elements
640	C.37 BtmDataTypesSchema Table C.56 – Description of BTM data type attributes
641	Table C.57 – Description of BTM data type elements
642	C.38 BtmInformationSchema Table C.58 – Description of BTM information elements
643	C.39 BtmParameterSchema Table C.59 – Description of BTM parameter elements
645	C.40 BtmInitSchema Table C.60 – Description of BTM init element
646	C.41 BtmInfoListSchema Table C.61 – Description of BTM info list element
647	Annex D (informative)FDT XML styles – Documentation
651	Annex E (informative)FDT XSL Transformation E.1 Identification transformation E.2 Hint
652	Figure E.1 – XSLT role
653	Annex F (normative)Channel schema F.1 FDTBasicChannelParameterSchema Table F.1 – Description of basic channel attribute Table F.2 – Description of basic channel elements
654	F.2 Template for Channel Schema Table F.3 – Description of xxx channel parameter attribute Table F.4 – Description of xxx channel parameter elements
655	Annex G (normative)FDT version interoperability guide G.1 Overview G.2 General G.3 Component interoperability
656	Table G.1 − Interoperability between components of different versions
657	G.4 FDT type library G.5 DTM and device versions G.6 Persistence
658	G.7 Nested communication G.7.1 General G.7.2 Data exchange G.7.3 Communication channel upgrade G.7.4 Scenarios
659	G.7.5 OnAddChild G.8 Implementation hints G.8.1 Interfaces G.8.2 Persistence
660	Annex H (informative)Implementation with Net technology H.1 How FDT supports .NET based development H.2 Microsoft .NET Framework 1.1 and 2.0 compatibility H.3 Side-by-side installation and related problems
661	H.4 How to avoid compatibility issues
662	Annex I (informative)Trade names
663	Bibliography

Published By	Publication Date	Number of Pages
BSI	2020	664


PDF Format	Searchable	Printable	Preview Now

Status	Definitive
Pages	664
Publication Date	2020-02-24
ISBN	978 0 539 08002 5
Standard Number	PD CLC/TR IEC 62453-41:2019 – TC
Title	Tracked Changes. Field device tool (FDT) interface specification – Object model integration profile. Common object model
Descriptors	Interfaces (data processing), Process control, Computer networks, Communication networks, Automatic control systems, Open systems interconnection, Fieldbus, Data transmission, Bus networks, Communication procedures, Industrial, Control equipment, Application layer (OSI)
Publisher	BSI
Committee	GEL/65/3
ICS Codes	35.110 - Networking

BSI PD CLC/TR IEC 62453-41:2019 – TC:2020 Edition

PDF Catalog

Related products

BSI PD CLC/TR IEC 62453-41:2019

BSI PD CLC/TR IEC 62453-41:2019