| |||||||||
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations | |||||||||
| Up to FDT Specification 2.1 FDT Overview 2.2 Where FDT Fits 2.3 General FDT Architecture and Components 2.4 Overview of Objects and Interfaces 2.4.1 The Device Type Manager (DTM) 2.4.2 The Block Type Manager (BTM) 2.4.3 The FDT Frame Application 2.5 Synchronization and Serialization Issues 2.6 Parameter interchange via XML 2.6.1 Examples of usage 2.7 Persistent Storage Story 2.7.1 Persistence Overview 2.7.2 Persistence Interfaces 2.8 Basic features of a session model 2.9 Basic Operation phases 2.9.1 Roles and Access Rights 2.9.2 Operation Phases 2.10 Abstract FDT Object Model 2.11 Fieldbus independent Integration 2.12 Scanning and DTM Assignment | 2.9.2 Operation PhasesIf a Frame Application requests available functions from the DTM (GetFunctions()), it passes the operation phase, which can be used by a DTM to adapt the availability of functions and the appearance of the user interface. There are five operation phases:
The following table describes the usage of operation phases in different Frame Application types.
Table 1. Operation phases For example the DTM allows the maintenance actor during commissioning phase the complete online parameterization, but during runtime phase it doesn’t allow it or it allows it only for some of its parameters | ||||||||
© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL. This website is published for support of M&M products as granted in license conditions, chapter 2.1. Last updated 2015-02-05 15:17 Email: FDT Technical Support Line. | |||||||||