🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 62453-2:2022

BS EN IEC 62453-2:2022

$215.11

Field device tool (FDT) interface specification – Concepts and detailed description

Published By Publication Date Number of Pages
BSI 2022 172
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

IEC 62453-2:2022 is available as IEC 62453-2:2022 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-2:2022 explains the common principles of the field device tool concept. These principles can be used in various industrial applications such as engineering systems, configuration programs and monitoring and diagnostic applications. This document specifies the general objects, general object behavior and general object interactions that provide the base of FDT.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
6 Blank Page
7 English
CONTENTS
15 FOREWORD
17 INTRODUCTION
Figures
Figure 1 – Part 2 of the IEC 62453 series
18 1 Scope
2 Normative references
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
19 3.2 Symbols and abbreviated terms
3.3 Conventions
3.3.1 Use of UML
3.3.2 State availability statement
3.3.3 Data type names and references to data types
4 Fundamentals
4.1 General
20 4.2 Abstract FDT model
4.2.1 FDT model overview
Figure 2 – Abstract FDT model
21 Tables
Table 1 – Description of FDT objects
22 Table 2 – Description of associations between FDT objects
23 4.2.2 Frame Application (FA)
24 4.2.3 Device Type Manager (DTM)
Figure 3 – Frame Application with integrated Communication Channel
Figure 4 – Device Type Manager (DTM)
25 Figure 5 – Communication DTM
26 Figure 6 – Device DTM
Figure 7 – Gateway DTM
27 Figure 8 – Composite Device DTM
28 Figure 9 – Module DTM
29 Figure 10 – Block Type Manager (BTM)
30 Figure 11 – Presentation object
31 4.2.4 Channel object
Figure 12 – Channel object
32 Figure 13 – Communication Channel
33 4.3 Modularity
4.4 Bus categories
Figure 14 – Combined Process/Communication Channel
34 4.5 Identification
4.5.1 DTM instance identification
Figure 15 – Identification of connected devices
35 4.6 System and FDT topology
Figure 16 – FDT topology for a simple system topology
36 4.7 FDT Communication
4.7.1 General
Figure 17 – FDT topology for a complex system topology
37 4.7.2 Handling of communication requests
4.7.3 Handling of communication errors
4.7.4 Handling of loss of connection
4.7.5 Point-to-point communication
38 4.7.6 Nested communication
Figure 18 – Point-to-point communication
39 Figure 19 – Nested communication
40 4.8 DTM, DTM Device Type and hardware identification information
4.8.1 DTM and DTM Device Type
Figure 20 – DTM, DTM Device Type and device identification information
41 4.8.2 Supported hardware identification
4.8.3 Connected hardware identification
Figure 21 – Connected hardware identification
42 4.9 DTM data persistence and synchronization
Figure 22 – FDT storage and synchronization mechanisms
43 4.10 DTM device parameter access
4.11 DTM state machine
4.11.1 DTM states
Figure 23 – DTM state machine
44 4.11.2 ‘Communication allowed’ substates
Figure 24 – Substates of communication allowed
Table 3 – Transitions of DTM states
45 4.12 Basic operation phases
4.12.1 Roles and access rights
4.12.2 Operation phases
Table 4 – Transitions of DTM ‘communication allowed’ substates
46 4.13 FDT version interoperability
4.13.1 Version interoperability overview
Table 5 – Operation phases
47 4.13.2 DTM and device versions
4.13.3 Persistence
48 4.13.4 Nested communication
5 FDT session model and use cases
5.1 Session model overview
49 5.2 Actors
Figure 25 – Main use case diagram
50 Table 6 – Actors
51 5.3 Use cases
5.3.1 Use case overview
5.3.2 Observation
5.3.3 Operation
Figure 26 – Observation use cases
52 Figure 27 – Operation use cases
53 Table 7 – Operation use cases
55 5.3.4 Maintenance
Figure 28 – Maintenance use cases
56 Table 8 – Maintenance use cases
58 5.3.5 Planning
59 Figure 29 – Planning use cases
Table 9 – Planning use cases
61 5.3.6 OEM service
5.3.7 Administration
Figure 30 – OEM Service
Figure 31 – Administrator use cases
62 6 General concepts
6.1 Address management
Table 10 – Administrator use cases
63 6.2 Scanning and DTM assignment
6.2.1 Scanning overview
6.2.2 Scanning
Figure 32 – Address setting via DTM Presentation object
64 6.2.3 DTM assignment
6.2.4 Manufacturer-specific device identification
Figure 33 – Fieldbus scanning
65 6.2.5 Scan for communication hardware
6.3 Configuration of Fieldbus Master or Communication Scheduler
66 6.4 PLC tool support
6.4.1 General
Figure 34 – Fieldbus master configuration tool as part of a DTM
67 6.4.2 Process image modifications while PLC is running
Figure 35 – Process Image
Figure 36 – Transfer of layout information using ProcessImage services
68 6.5 Slave redundancy
6.5.1 Redundancy overview
Figure 37 – Redundancy scenarios
69 6.5.2 Redundancy support in Frame Application
6.5.3 Parent component for redundant fieldbus
70 6.5.4 Redundancy support in Device DTM
6.5.5 Scan and redundant slaves
7 FDT service specification
7.1 Service specification overview
71 7.2 DTM services
7.2.1 General services
Table 11 – Arguments for service PrivateDialogEnabled
72 Table 12 – Arguments for service SetLanguage
73 7.2.2 DTM services related to installation
Table 13 – Arguments for service SetSystemGuiLabel
74 7.2.3 DTM services related to DTM/device information
Table 14 – Arguments for service GetTypeInformation (for DTM)
Table 15 – Arguments for service GetTypeInformation (for BTM)
Table 16 – Arguments for service GetIdentificationInformation (for DTM)
75 Table 17 – Arguments for service GetIdentificationInformation (for BTM)
Table 18 – Arguments for service Hardware information (for DTM)
Table 19 – Arguments for service GetActiveTypeInfo
76 7.2.4 DTM services related to the DTM state machine
Table 20 – Arguments for service GetActiveTypeInfo (for BTM)
Table 21 – Arguments for service Initialize (for DTM)
77 Table 22 – Arguments for service Initialize (for BTM)
Table 23 – Arguments for service SetLinkedCommunicationChannel
Table 24 – Arguments for service EnableCommunication
78 Table 25 – Arguments for service ReleaseLinkedCommunicationChannel
Table 26 – Arguments for service ClearInstanceData
79 7.2.5 DTM services related to functions
Table 27 – Arguments for service Terminate
Table 28 – Arguments for service GetFunctions
80 Table 29 – Arguments for service InvokeFunctions
Table 30 – Arguments for service GetGuiInformation
81 Table 31 – Arguments for service OpenPresentation
Table 32 – Arguments for service ClosePresentation
82 7.2.6 DTM services related to Channel objects – service GetChannels
7.2.7 DTM services related to documentation – service GetDocumentation
7.2.8 DTM services to access the instance data
Table 33 – Arguments for service GetChannels
Table 34 – Arguments for service GetDocumentation
83 Table 35 – Arguments for service InstanceDataInformation
Table 36 – Arguments for service InstanceDataRead
84 7.2.9 DTM services to evaluate the instance data
Table 37 – Arguments for service InstanceDataWrite
Table 38 – Arguments for service Verify
Table 39 – Arguments for service CompareDataValueSets
85 7.2.10 DTM services to access the device data
Table 40 – Arguments for service DeviceDataInformation
Table 41 – Arguments for service DeviceDataRead
86 7.2.11 DTM services related to network management information
Table 42 – Arguments for service DeviceDataWrite
Table 43 – Arguments for service NetworkManagementInfoRead
87 7.2.12 DTM services related to online operation
Table 44 – Arguments for service NetworkManagementInfoWrite
Table 45 – Arguments for service DeviceStatus (for DTM)
88 Table 46 – Arguments for service CompareInstanceDataWithDeviceData (for DTM)
Table 47 – Arguments for service WriteDataToDevice (for DTM)
89 7.2.13 DTM services related to data synchronization
Table 48 – Arguments for service ReadDataFromDevice(for DTM)
Table 49 – Arguments for service OnLockInstanceData
90 Table 50 – Arguments for service OnUnlockInstanceData
Table 51 – Arguments for service OnInstanceDataChanged
Table 52 – Arguments for service OnInstanceChildDataChanged
91 7.2.14 DTM services related to import and export
7.3 Presentation object services
Table 53 – Arguments for service Export
Table 54 – Arguments for service Import
92 7.4 Channel object service
7.4.1 Channel object service overview
7.4.2 Service ReadChannelInformation
7.4.3 Service WriteChannelInformation
7.5 Process Channel object services – services for I/O related information
7.5.1 Service ReadChannelData
Table 55 – Arguments for service ReadChannelInformation
Table 56 – Arguments for service WriteChannelInformation
Table 57 – Arguments for service ReadChannelData
93 7.5.2 Service WriteChannelData
7.6 Communication Channel object services
7.6.1 Services related to communication
Table 58 – Arguments for service WriteChannelData
Table 59 – Arguments for service GetSupportedProtocols
94 Table 60 – Arguments for service Connect
95 Table 61 – Arguments for service Disconnect
Table 62 – Arguments for service AbortRequest
Table 63 – Arguments for service AbortIndication
96 Table 64 – Arguments for service Transaction
97 7.6.2 Services related to sub-topology management
Table 65 – Arguments for service SequenceDefine
Table 66 – Arguments for service SequenceStart
Table 67 – Arguments for service ValidateAddChild
98 Table 68 – Arguments for service ChildAdded
Table 69 – Arguments for service ValidateRemoveChild
99 7.6.3 Services related to GUI and functions
Table 70 – Arguments for service ChildRemoved
Table 71 – Arguments for service SetChildrenAddresses
100 7.6.4 Service Scan
Table 72 – Arguments for service GetChannelFunctions
Table 73 – Arguments for service GetGuiInformation
Table 74 – Arguments for service Scan
101 7.7 Frame Application services
7.7.1 General state availability
7.7.2 FA services related to general events
Table 75 – Arguments for service OnErrorMessage
Table 76 – Arguments for service OnProgress
102 7.7.3 FA services related to topology management
Table 77 – Arguments for service OnOnlineStatusChanged
Table 78 – Arguments for service OnFunctionsChanged
Table 79 – Arguments for service GetDtmInfoList
103 Table 80 – Arguments for service CreateChild (DTM)
Table 81 – Arguments for service CreateChild (BTM)
Table 82 – Arguments for service DeleteChild
104 Table 83 – Arguments for service MoveChild
Table 84 – Arguments for service GetParentNodes
Table 85 – Arguments for service GetChildNodes
105 7.7.4 FA services related to redundancy
Table 86 – Arguments for service GetDtm
Table 87 – Arguments for service ReleaseDtm
Table 88 – Arguments for service OnAddedRedundantChild
106 7.7.5 FA services related to storage of DTM data
Table 89 – Arguments for service OnRemovedRedundantChild
Table 90 – Arguments for service SaveInstanceData
Table 91 – Arguments for service LoadInstanceData
107 7.7.6 FA services related to DTM data synchronization
Table 92 – Arguments for service GetPrivateDtmStorageInformation
Table 93 – Arguments for service LockInstanceData
108 7.7.7 FA service related to process image validation – service ValidateProcessImage
Table 94 – Arguments for service UnlockInstanceData
Table 95 – Arguments for service OnInstanceDataChanged
Table 96 – Arguments for service ValidateProcessImage
109 7.7.8 FA services related to presentation
Table 97 – Arguments for service OpenPresentationRequest
Table 98 – Arguments for service ClosePresentationRequest
110 7.7.9 FA Services related to audit trail – service RecordAuditTrailEvent
8 FDT dynamic behavior
8.1 Generate FDT topology
8.1.1 FDT topology generation triggered by the Frame Application
Table 99 – Arguments for service UserDialog
Table 100 – Arguments for service RecordAuditTrailEvent
111 8.1.2 FDT topology generation triggered by the DTM
Figure 38 – FDT topology generation triggered by the Frame Applications
Figure 39 – FDT topology generation triggered by a DTM
112 8.2 Address setting
8.2.1 Address setting overview
8.2.2 Set or modify device address – with user interface
8.2.3 Set or modify device address – without user interface
Figure 40 – Set or modify device address – with user interface
113 8.2.4 Display or modify all child device addresses with user interface
Figure 41 – Set or modify device address – without user interface
Figure 42 – Set or modify all device addresses – with user interface
114 8.3 Communication
8.3.1 Communication overview
8.3.2 Point-to-point communication
8.3.3 Nested communication
Figure 43 – Point-to-point communication
115 8.3.4 Device-initiated data transfer
Figure 44 – Nested communication
116 8.4 Scanning and DTM assignment
Figure 45 – Device-initiated data transfer
117 8.5 Multi-user scenarios
8.5.1 General
Figure 46 – Scanning and DTM assignment
118 Figure 47 – Multi-user system
119 8.5.2 Synchronized and non-synchronized locking mechanism for DTMs
Figure 48 – General synchronized locking mechanism
120 Figure 49 – General non-synchronized locking mechanism
Figure 50 – Parameterization in the case of synchronized locking mechanism
121 8.5.3 Additional rules
8.6 Notification of changes
8.7 DTM instance data state machines
8.7.1 Instance data set overview
122 8.7.2 Modifications state machine
Figure 51 – Modifications state machine of instance data
Table 101 – Modifications state machine of instance data
123 8.7.3 Persistence state machine
8.7.4 Modification in device
Figure 52 – Persistence state machine of instance data
Table 102 – Persistence state machine of instance data
124 8.7.5 Storage life cycle
Table 103 – Example life cycle of a DTM
125 8.8 Parent component handling redundant slave
126 8.9 DTM upgrade
8.9.1 General rules
Figure 53 – Management of redundant topology
127 8.9.2 Saving data from a DTM to be upgraded
8.9.3 Loading data in the replacement DTM
Figure 54 – Associating data to a dataSetId
128 Figure 55 – Loading data for a supported dataSetId
129 Annex A (normative) FDT data types definition
A.1 General
130 A.2 Basic data types
A.3 General data types
Table A.1 – Basic data types
Table A.2 – Simple general data types
137 Table A.3 – Definition of classificationId enumeration values
139 Table A.4 – General structured data types
146 A.4 User information data types
Table A.5 – Simple user information data types
147 A.5 DTM information data type
A.6 BTM data types
Table A.6 – Structured user information data type
Table A.7 – Structured DTM information data type
148 Table A.8 – Simple BTM data types
149 A.7 Device and Scan identification data types
Table A.9 – Structured BTM data types
150 Table A.10 – Simple device identification data types
151 Table A.11 – Structured device identification data types
153 A.8 Function data types
154 Table A.12 – Simple function data types
155 Table A.13 – Structured function data types
156 A.9 AuditTrail data types
Table A.14 – Simple auditTrail data types
157 A.10 Documentation data types
Table A.15 – Structured auditTrail data types
Table A.16 – Simple documentation data types
158 A.11 DeviceList data type
Table A.17 – Structured documentation data types
159 Table A.18 – Simple deviceList data type
Table A.19 – Structured deviceList data type
160 A.12 Network management data types
Table A.20 – Simple network management data types
161 A.13 Instance data types
Table A.21 – Structured network management data types
162 Table A.22 – Simple instance data types
164 Table A.23 – Structured instance data types
166 A.14 DeviceStatus data types
A.15 OnlineCompare data types
Table A.24 – Simple device status data types
Table A.25 – Structured device status data types
Table A.26 – Simple online compare data types
167 A.16 UserInterface data types
Table A.27 – Structured online compare data types
Table A.28 – Simple user interface data types
168 A.17 Fieldbus-specific data types
Table A.29 – Structured user interface data types
169 Table A.30 – Fieldbus data types
170 Bibliography

Related products

BS EN IEC 62453-2:2022
$215.11