This subclause describes the different states of DTM instance data with regard to modifications and persistence. The persistence mechanism itself is described in 773H4.8.
LICENSED TO MECON Limited. - RANCHI/BANGALORE,FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.
8.7.2 Modifications state machine
This state machine (see 774HFigure 46) reflects the possible states of instance data concerning modifications.
InitNew
default
modification which causes a valid Instance Data
validModified
allDataLoaded Download All Data
zombie Clear Instance Data
final remove
All changes of dtm data, which were not downloaded
Clear Instance Data Clear Instance Data
Download All Data
Only valid if the newly created Instance Data containes enough
information to establish a proper
communication
Upload Al lData
invalidModified modification which causes
an invalid Instance Data
Upload Al lData modification which causes
a valid Instance Data
modification which causes an invalid Instance Data
Clear Instance Data
Figure 46 – Modifications state machine of instance data The states of the modifications state machine are explained in 775HTable 100.
Table 100 – Modifications state machine of instance data
State Meaning
Default The contents of the instance data are the default data. This state will typically appear after creation of new instance data
validModified The instance data was modified in a consistent manner
invalidModified The data set was modified. The data are not in a consistent state allDataLoaded The data was loaded from or into the related device.
NOTE This state means not, that the data within the device are equal to the data found within the related instance data. Due to the fact that a user can use tools out of the scope of FDT, FDT- cannot guarantee such a state zombie The instance data is prepared to delete, no access to this data is allowed
The data set state can be used to verify which devices are in sync with their DTMs and which devices need to be reloaded. For example, ‘allDataLoaded’ indicates that a device is in sync with the DTM and shall not be loaded again. This state shall be changed only if data is really changed and not, for example if a lock is requested or a Presentation Object is active without changing the data set, because reloading a device is a time consuming action.
IEC 1115/09
LICENSED TO MECON Limited. - RANCHI/BANGALORE,FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.
8.7.3 Persistence state machine
This state machine reflects the possible states of instance data concerning the persistence of data (see 776HFigure 47).
Figure 47 – Persistence state machine of instance data The states of the persistence state machine are explained in 777HTable 101.
Table 101 – Persistence state machine of instance data
State Meaning
persistent The content of the instance related data is persistent. This state will typically appear after the data was saved by the DTM using the persistence service SaveInstanceData (see 778H7.7.5.1) of the Frame Application.
transient The instance data was modified. These changes are not saved in a persistent way. All modified data within the DTM is temporary and not synchronized with other DTM instances or with the Frame Application.
A DTM shall request to store the instance data set at minimum if one of the following conditions occurs:
• if the last Presentation Object, which is able to change parameter values has been terminated;
• after parameters have been read from or written to the device (services ReadDataFromDevice / WriteDataToDevice);
• after parameter values are changed by another component (InstanceDataWrite) and no Presentation Object which is able to change parameter values is active.
8.7.4 Modification in device
It is useful to keep the device data set and the DTM instance data set in sync. When invoked in online mode, the DTM should ask the user whether the data in the DTM and in the device should be synchronized. This behavior is mandatory for Presentation Objects with applicationId “fdtOfflineParameterize” and “fdtOnlineParameterize”.
The mandatory flag <fdt:modifiedInDevice> will present the synchronization state.
8.7.4.1 Presentation fdtOnlineParameterize
After the user closes the DTM user interface, the DTM shall ask the user if the instance data set and the current device configuration should be synchronized. This may overwrite already existing parameter modifications within the instance data set (status not equal to
‘allDataLoaded’, refer to 779H8.7.3). If this is the case, the DTM shall include this information in the message mentioned above.
IEC 1116/09
LICENSED TO MECON Limited. - RANCHI/BANGALORE,FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.
If the user confirms the synchronization, the DTM shall load the complete device data set into the instance data set. If the DTM can guarantee consistency of device data and instance data set, it could upload only the modified device parameters under consideration of device specific business rules.
8.7.4.2 Presentation fdtOfflineParameterize
If the user closes the DTM user interface and if the DTM can connect to the device, (meaning the DTM is in a state of ‘communication allowed’), the DTM shall ask the user if a complete write should be initiated to synchronize the instance data set and the current device configuration.
If the user confirms the download, the DTM shall download the complete instance data set into the device. If the DTM can guarantee consistency of device data and instance data set, it could write only the modified parameters under consideration of device specific business rules.
8.7.5 Storage life cycle
The following table (780HTable 102) describes the states of the instance data set during a ‘life’
cycle of a DTM. The states of instance data set are defined by dataSetState (see 781HFigure 46) and storabeState (see 782HFigure 47).
Table 102 – Example life cycle of a DTM
Scenario storageSt ate
dataSetState modifiedInDe vice
Remarks
DTM is initialized transient default False After DTM is initialized
and storing the data
persistent default False
After failed read of
device data persistent default False no change of the states, because due to the unsuccessful read the data set is not changed After successful read
device data
transient allDataLoaded False After reading from
device and storing the data set
persistent allDataLoaded False
After modification of device data set via e.g. the GUI Online Parameterize
transient, because flag
<modifiedI nDevice>
has changed
validModified True The device
accepted new data, therefore a read from device is necessary in order to synchronize the data sets After storing the data
set
persistent validModified True After read data from
device
transient, because dataSetSt ate is changed
allDataLoaded False
LICENSED TO MECON Limited. - RANCHI/BANGALORE,FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.
Scenario storageSt
ate dataSetState modifiedInDe
vice Remarks
After modification of instance data set
transient If changes comply to business rules of device:
validModified Otherwise:
invalidModified
False
After storing the data set
persistent validModified False After release of the
DTM
-/- -/-
After DTM started with persistent data
persistent validModified False