History Configuration
The history configuration defines what columns and in which order they should be written to the history files.
The LTT GUI creates a so called history log file for every station (DUT) and test order. The main purpose of the history files is to log failed limit tests during test execution. But also other generic status information will be logged to the history files. You can create custom history log entries by yourself from any TestStand sequence.
Each history log entry is put into a separate line in the history file and is accompanied by a number of auxiliary information, such as date, time, climatic chamber temperature and so on.
You can choose what additional information are logged with each log entry and in which order they should appear in the file.
Available Column IDs
There is a predefined set of available data, which you can pick by using a certain identifier. The following table gives a list of all possible data you can pick.
DATE
The current date.
TIME
The current time.
INFORMATION
The actual log message. This is either an error message (limit or runtime error) or a custom log message (how to create a log entry?).
MEASUREMENT_VALUE
The actual measurement value, in case this log entry is a limit error.
MEASUREMENT_UNIT
The measurement value unit, in case this log entry is a limit error.
LIMIT_MIN
The measurement value min. limit, in case this log entry is a limit error.
LIMIT_MAX
The measurement value max. limit, in case this log entry is a limit error.
MEASUREMENT_ID
The measurement ID, in case this log entry is a limit error (more info).
ERROR_COUNTER
The count of how many times this measurement already had a limit violation (more info).
OPERATION_MODE
The current operation mode (more info).
STATUS
The current station status (more info).
TEST_CYCLES
The current test cycle (more info).
TCC
The current TCC value (more info).
DUT_VOLTAGE
The current DUT voltage (more info).
CHAMBER_TEMPERATURE
The current climatic chamber temperature (more info).
CHAMBER_HUMIDITY
The current climatic chamber humidity. This value is only available if your temperature sensor also supports measuring humidity (for example the Omega iThx) (more info).
STEP_TIME
The time passed since the station status was last updated (more info).
TOTAL_TEST_TIME
The time this test had run in total so far.
ELECTRICAL_TEST_TIME
The time this test had run in total so far, but only in electrically active operation modes (more info).
TEST_STATION
The test station index (more info).
DUT_NAME
The DUT name (more info).
DUT_TYPE
The DUT type (more info).
CABLE_ID
The cable ID (more info).
VIBRATION_AXIS
The vibration axis, if applicable (more info).
COMMENT
A custom comment, which can be set afterwards (more info).
CUSTOM
Used for custom columns (see below)
For each history column you write a line
where you set the ID to one of those in the table above and provide a name for the column header. The default history configuration already contains all available columns in a certain order. You can change the order and/or maybe remove some unwanted columns or add additional custom columns.
Format Specifier
You can also add an optional format attribute to each HistoryColumn entry.
The following format specifier are available:
Fx
Floating point number with x digits after the decimal separator, examples: F1, F2, F3
D
Decimal number
dd.MM.yyyy
date format
HH:mm:ss.fff
time format
If no format is specified, string is assumed.
History File Split Size
Usually history files will be split into several chunks if the file size exceeds a certain limit. The default file split size is 1 MB (1048576 bytes). You can change this value by adding a size_limit attribute to the top level <LttHistoryColumnConfig> element.
The above will set the file split size to 10 MB.
History File Column Separator
By default the history columns are separated by a semicolon ;. You can change the column separator with the following attribute:
The above will set | as a column separator.
Custom Columns
You can define any number of custom columns for the history files. To do so add HistoryColumn entries with the ID CUSTOM. The provided name will be the column header.
Custom columns get their values from TestStand. Those so called runtime values are displayed in GUI for each station display as well as inserted into the history file's custom column with the matching name.
Last updated
Was this helpful?

