BS EN 62453-2:2009 2010
$215.11
Field device tool (FDT) interface specification – Concepts and detailed description
| Published By | Publication Date | Number of Pages |
| BSI | 2010 | 158 |
IEC 62453-2:2009 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. It specifies the general objects, general object behavior and general object interactions that provide the base of FDT. This bilingual version (2014-04) corresponds to the monolingual English version, published in 2009-06.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 6 | CONTENTS |
| 14 | INTRODUCTION Figures Figure 1 – Part 2 of the IEC 62453 series |
| 15 | 1 Scope 2 Normative references 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions |
| 16 | 3.2 Symbols and abbreviated terms 3.3 Conventions 4 Fundamentals 4.1 General 4.2 Abstract FDT model |
| 17 | Figure 2 – Abstract FDT model Tables Table 1 – Description of FDT objects |
| 18 | Table 2 – Description of associations between FDT objects |
| 20 | Figure 3 – Frame Application with integrated Communication Channel |
| 21 | Figure 4 – Device Type Manager (DTM) Figure 5 – Communication DTM |
| 22 | Figure 6 – Device DTM Figure 7 – Gateway DTM |
| 23 | Figure 8 – Module DTM |
| 24 | Figure 9 – Block Type Manager (BTM) Figure 10 – Presentation object |
| 25 | Figure 11 – Channel object |
| 26 | 4.3 Modularity Figure 12 – Combined Process / Communication Channel |
| 27 | 4.4 Bus categories 4.5 System and FDT topology Figure 13 – FDT topology for a simple system topology |
| 28 | Figure 14 – FDT topology for a complex system topology |
| 29 | 4.6 Peer to peer and nested communication Figure 15 – Peer to peer communication |
| 30 | 4.7 DTM, DTM Device Type and Hardware Identification Information Figure 16 – Nested communication |
| 31 | Figure 17 – DTM, DTM Device Type and Device Identification Information |
| 32 | 4.8 DTM data persistence and synchronization Figure 18 – Connected Hardware Identification |
| 33 | 4.9 DTM device parameter access Figure 19 – FDT storage and synchronization mechanisms |
| 34 | 4.10 DTM state machine Figure 20 – DTM state machine |
| 35 | Figure 21 – Substates of communication allowed Table 3 – Transitions of DTM states Table 4 – Transitions of DTM ‘communication allowed’ sub states |
| 36 | 4.11 Basic operation phases |
| 37 | 4.12 FDT version interoperability Table 5 – Operation phases |
| 39 | 5 FDT session model and use cases 5.1 Session model overview |
| 40 | 5.2 Actors Figure 22 – Main Use Case Diagram |
| 41 | Table 6 – Actors |
| 42 | 5.3 Use cases Figure 23 – Observation Use Cases |
| 43 | Figure 24 – Operation Use Cases Table 7 – Operation Use Cases |
| 46 | Figure 25 – Maintenance use cases |
| 47 | Table 8 – Maintenance use cases |
| 51 | Figure 26 – Planning use cases Table 9 – Planning use cases |
| 53 | Figure 27 – OEM service |
| 54 | Figure 28 – Administrator use cases Table 10 – Administrator use cases |
| 55 | 6 General concepts 6.1 Address management 6.2 Scanning and DTM assignment Figure 29 – Address setting via DTM presentation object |
| 56 | Figure 30 – Fieldbus scanning |
| 57 | 6.3 Configuration of fieldbus master or communication scheduler |
| 58 | 6.4 Slave redundancy Figure 31 – Fieldbus master configuration tool as part of a DTM |
| 59 | Figure 32 – Redundancy scenarios |
| 61 | 7 FDT service specification 7.1 Service specification overview |
| 62 | 7.2 DTM services Table 11 – Arguments for service PrivateDialogEnabled |
| 63 | Table 12 – Arguments for service SetLanguage Table 13 – Arguments for service SetSystemGuiLabel |
| 64 | Table 14 – Arguments for service GetTypeInformation (for DTM) Table 15 – Arguments for service GetTypeInformation (for BTM) |
| 65 | Table 16 – Arguments for service GetIdentificationInformation (for DTM) Table 17 – Arguments for service GetIdentificationInformation (for BTM) Table 18 – Arguments for service Hardware information (for DTM) |
| 66 | Table 19 – Arguments for service GetActiveTypeInfo Table 20 – Arguments for service GetActiveTypeInfo (for BTM) Table 21 – Arguments for service Initialize (for DTM) |
| 67 | Table 22 – Arguments for service Initialize (for BTM) Table 23 – Arguments for service SetLinkedCommunicationChannel Table 24 – Arguments for service EnableCommunication |
| 68 | Table 25 – Arguments for service ReleaseLinkedCommunicationChannel Table 26 – Arguments for service ClearInstanceData Table 27 – Arguments for service Terminate |
| 69 | Table 28 – Arguments for service GetFunctions |
| 70 | Table 29 – Arguments for service InvokeFunctions Table 30 – Arguments for service GetGuiInformation Table 31 – Arguments for service OpenPresentation |
| 71 | Table 32 – Arguments for service ClosePresentation Table 33 – Arguments for service GetChannels |
| 72 | Table 34 – Arguments for service GetDocumentation Table 35 – Arguments for service InstanceDataInformation |
| 73 | Table 36 – Arguments for service InstanceDataRead Table 37 – Arguments for service InstanceDataWrite Table 38 – Arguments for service Verify |
| 74 | Table 39 – Arguments for service CompareDataValueSets Table 40 – Arguments for service DeviceDataInformation |
| 75 | Table 41 – Arguments for service DeviceDataRead Table 42 – Arguments for service DeviceDataWrite |
| 76 | Table 43 – Arguments for service NetworkManagementInfoRead Table 44 – Arguments for service NetworkManagementInfoWrite Table 45 – Arguments for service DeviceStatus (for DTM) |
| 77 | Table 46 – Arguments for service CompareInstanceDataWithDeviceData (for DTM) Table 47 – Arguments for service WriteDataToDevice (for DTM) |
| 78 | Table 48 – Arguments for service ReadDataFromDevice(for DTM) Table 49 – Arguments for service OnLockInstanceData Table 50 – Arguments for service OnUnlockInstanceData |
| 79 | Table 51 – Arguments for service OnInstanceDataChanged Table 52 – Arguments for service OnInstanceChildDataChanged |
| 80 | 7.3 Presentation object services 7.4 Channel object service Table 53 – Arguments for service Export Table 54 – Arguments for service Import |
| 81 | 7.5 Process Channel object services Table 55 – Arguments for service ReadChannelInformation Table 56 – Arguments for service WriteChannelInformation Table 57 – Arguments for service ReadChannelData |
| 82 | 7.6 Communication Channel object services Table 58 – Arguments for service WriteChannelData Table 59 – Arguments for service GetSupportedProtocols |
| 83 | Table 60 – Arguments for service Connect Table 61 – Arguments for service Disconnect |
| 84 | Table 62 – Arguments for service AbortRequest Table 63 – Arguments for service AbortIndication Table 64 – Arguments for service Transaction |
| 85 | Table 65 – Arguments for service SequenceDefine Table 66 – Arguments for service SequenceStart |
| 86 | Table 67 – Arguments for service ValidateAddChild Table 68 – Arguments for service ChildAdded |
| 87 | Table 69 – Arguments for service ValidateRemoveChild Table 70 – Arguments for service ChildRemoved Table 71 – Arguments for service SetChildrenAddresses |
| 88 | Table 72 – Arguments for service GetChannelFunctions Table 73 – Arguments for service GetGuiInformation |
| 89 | 7.7 Frame Application services Table 74 – Arguments for service Scan Table 75 – Arguments for service OnErrorMessage |
| 90 | Table 76 – Arguments for service OnProgress Table 77 – Arguments for service OnOnlineStatusChanged Table 78 – Arguments for service OnFunctionsChanged |
| 91 | Table 79 – Arguments for service GetDtmInfoList Table 80 – Arguments for service CreateChild (DTM) Table 81 – Arguments for service CreateChild (BTM) |
| 92 | Table 82 – Arguments for service DeleteChild Table 83 – Arguments for service MoveChild Table 84 – Arguments for service GetParentNodes |
| 93 | Table 85 – Arguments for service GetChildNodes Table 86 – Arguments for service GetDtm Table 87 – Arguments for service ReleaseDtm |
| 94 | Table 88 – Arguments for service OnAddedRedundantChild Table 89 – Arguments for service OnRemovedRedundantChild Table 90 – Arguments for service SaveInstanceData |
| 95 | Table 91 – Arguments for service LoadInstanceData Table 92 – Arguments for service GetPrivateDtmStorageInformation Table 93 – Arguments for service LockInstanceData |
| 96 | Table 94 – Arguments for service UnlockInstanceData Table 95 – Arguments for service OnInstanceDataChanged Table 96 – Arguments for service OpenPresentationRequest |
| 97 | Table 97 – Arguments for service ClosePresentationRequest Table 98 – Arguments for service UserDialog |
| 98 | 8 FDT dynamic behavior 8.1 Generate FDT topology Table 99 – Arguments for service RecordAuditTrailEvent |
| 99 | Figure 33 – FDT topology generation triggered by the Frame Applications Figure 34 – FDT topology generation triggered by a DTM |
| 100 | 8.2 Address setting Figure 35 – Set or modify device address – with user interface |
| 101 | Figure 36 – Set or modify device address – with user interface Figure 37 – Set or modify all device addresses – with user interface |
| 102 | 8.3 Communication Figure 38 – Peer to peer communication |
| 103 | Figure 39 – Nested communication |
| 104 | 8.4 Scanning and DTM assignment Figure 40 – Device initiated data transfer |
| 105 | 8.5 Multi-user scenarios Figure 41 – Scanning and DTM assignment |
| 106 | Figure 42 – Multi-user system |
| 107 | Figure 43 – General synchronized locking mechanism |
| 108 | Figure 44 – General non-synchronized locking mechanism Figure 45 – Parameterization in case of synchronized locking mechanism |
| 109 | 8.6 Notification of changes 8.7 DTM instance data state machines |
| 110 | Figure 46 – Modifications state machine of instance data Table 100 – Modifications state machine of instance data |
| 111 | Figure 47 – Persistence state machine of instance data Table 101 – Persistence state machine of instance data |
| 112 | Table 102 – Example life cycle of a DTM |
| 113 | 8.8 Parent component handling redundant slave |
| 114 | 8.9 DTM upgrade Figure 48 – Management of redundant topology |
| 115 | Figure 49 – Associating data to a dataSetId |
| 116 | Figure 50 – Loading data for a supported dataSetId |
| 117 | Annex A (normative) FDT data types definition |
| 118 | Table A.1 – Basic data types Table A.2 – Simple general data types |
| 125 | Table A.3 – Definition of classificationId enumeration values |
| 126 | Table A.4 – General structured data types |
| 135 | Table A.5 – Simple user information data types Table A.6 – Structured user information data type Table A.7 – Structured DTM information data type |
| 136 | Table A.8 – Simple BTM data types Table A.9 – Structured BTM data types |
| 138 | Table A.10 – Simple device identification data types |
| 139 | Table A.11 – Structured device identification data types |
| 141 | Table A.12 – Simple function data types |
| 142 | Table A.13 – Structured function data types |
| 144 | Table A.14 – Simple auditTrail data types Table A.15 – Structured auditTrail data types |
| 145 | Table A.16 – Simple documentation data types Table A.17 – Structured documentation data types |
| 147 | Table A.18 – Simple deviceList data type Table A.19 – Structured deviceList data type |
| 148 | Table A.20 – Simple network management data types Table A.21 – Structured network management data types |
| 149 | Table A.22 – Simple instance data types |
| 151 | Table A.23 – Structured instance data types |
| 153 | Table A.24 – Simple device status data types |
| 154 | Table A.25 – Structured device status data types Table A.26 – Simple online compare data types Table A.27 – Structured online compare data types |
| 155 | Table A.28 – Simple user interface data types Table A.29 – Structured user interface data types |
| 156 | Table A.30 – Fieldbus data types |
