
Using the below options you can configure the Parameter Set Data
To configure parameter set data:
User settings created using an older version of GTT (W onwards) all the data would be treated as User data including the header part if it was included.
You must clear the header information manually if user data already includes header information. The header part can then be included as required. This is because earlier header metadata was editable which is now controlled due to separate edit sections. This is a one-time process and would not require X release onwards.
To create a set file:
Store the parameter data in the directory with the file extension *.set.
To load the set file:
Locate the set file and open the file. Tuning data will be loaded onto the chosen set after selecting the .set file. When you click Undo, the load action is reversed, and the screen displays the previous preset values.
Only matching (CoreId, InstanceId, BlockId, and SublockId) objects tuning data will be loaded.
Following are the notifications you will get during the load:
All the mismatched object details will be displayed in the event log.
Tuning data will be loaded only to the set in the parameter set column. Not on to the state variables.
Similarly, you can also load a human-readable set file (.setr file).
Tuning data is loaded onto the chosen set upon selection of the .setr file. When you click Undo, the load action is reversed, and the screen displays the previous preset values.
Only tuning data for objects with matching (CoreId, InstanceId, BlockId, and SublockId) identifiers will be loaded. The following message appears following the loading of the tuning data from Setr.
The following notifications are displayed in the cases mentioned below:
All the mismatched object details will be displayed in the event log.