Diese Seite gibt es noch nicht auf Deutsch, daher wird die englische Fassung angezeigt.
The following configuration files are generated through the GUI and not meant to be edited manually. Any manual changes to those files will be overwritten by the next GUI start or stop.
The purpose of the generated configuration files is mainly documentation, and in case of limit files, exchange. The files are also used by any LTT TestStand sequence file, rather than accessing the information from the configuration database.
Limits Configuration
You will find the limit configuration files at
[Install Location]\50_LTT_SW\LTT Limit Files.
<LttLimitConfig DutType="Type1">
<Signal name="U_24V">
<Limit name="default" id="1000" val1="-1" val2="1" />
<Limit name="active" id="1001" val1="12" val2="12.5" />
<Limit name="over" id="1002" val1="15.8" val2="16.5" />
<Limit name="under" id="1003" val1="8.7" val2="9.2" />
</Signal>
<Signal name="U_Kl30">
<Limit name="default" id="1010" val1="0" val2="90" />
</Signal>
<Signal name="U_Ubatt">
<Limit name="default" id="1020" val1="0" val2="90" />
</Signal>
</LttLimitConfig>
In the F5 - limit configuration dialog you can configure limits for every signal defined in the signals definition dialog. Limits are defined per DUT type, so you can have different limits for the same signal in different DUT types. For that reason you will find in the above folder different limits configuration files, one for each DUT type. The files will have a file name with the following pattern: limits_for_[DUT type name].xml.
Limit configuration files are only present if you have actually configured some limits for a DUT type. After a fresh installation the LTT Limit Files folder is empty.
All limits are stored in configuration database, but are also exported to XML. The Action Logs mechanism use those files as a form of documentation of the parameter changes over time. The exported limit configuration files are also used to transfer limits from one LTT to another (more info).
Do not make any changes in this files as they will be overwritten by the GUI.
Recording Configuration
Click to open the recording configuration file
ltt_recording_config.xml.
The recording configuration file is an automatically generated file and contains all settings made in the Data Recording dialog.
Do not make any changes in this file as they will be overwritten by the GUI.
Test Configuration
Click to open the test configuration file ltt_test_config.xml.
The test configuration file is an automatically generated file and contains all settings made in the F10 - test parameter configuration and F11 - test configuration dialogs. It also contains some settings from the F3 - project wizard.
All test configuration settings are stored in configuration database, but are also exported to XML. The Action Logs mechanism use this file as a form of documentation of the parameter changes over time.
The LTT TestStand process model also uses some of those informations for its own purpose.
As a summary, you will find in the test configuration file the following informations:
- what DUT types are available?
- what test groups are available?
- how many test stations are present and what test orders / DUT's are configured for them?
- what operation modes are available and what parameters do they have (per test group)?
- what operation mode <> TCC mappings are configured?
- what power supplies / temperature sensors are assigned to what test group?
Do not make any changes in this file as they will be overwritten by the GUI.