
Saving Parameter Sets
When a device is removed or GTT is closed, parameter sets are automatically saved.
There is currently a limitation on saving parameter sets to databases.
The parameter set is not immediately saved to the database. It is saved in the moment when the device is removed from the device list. Therefore, if the signal flow is modified (for which there is an associated parameter set) when the device is not in device list, the old parameter sets are retrieved from the database when the device is dragged to device list next time.
A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.
A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.
A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.
Once you have saved the set file, both the .set and .setr files will be accessible in the folder you selected.
If the set file is generated using a different panel, such as the IESS panel, the .setr file will not be generated by default. However, you can utilize any of the methods mentioned earlier to generate the .setr file if needed.
Loading a Set File
In the context menu of any set Click on “Load Set file”. This opens a dialog to select the .set file to be loaded. On selecting the .set file, tuning data will be loaded on to the selected set. On clicking Undo, load action will be undone and old preset values will be displayed in the screen.
Only matching (CoreId, InstanceId, BlockId, and SublockId) object’s tuning data will be loaded.
Notifications to the user during load:
All the mismatched object details will be displayed in event log.
Tuning data will be loaded only on to the set in the parameter set column. Not on to the state variables.