Test Limits Text File Structure

Each row in the test limits file corresponds to a test. The import mode and the columns in the test limits file define how the Import/Export Test Limits tool matches rows to the sequence file.

Tags enclosed in angle brackets denote the properties recognized during import or export. The Import/Export Test Limits tool ignores any column with an unknown tag and any text above or on the same line as the opening <SemiconductorModuleTests> tag or below or on the same line as the required closing </SemiconductorModuleTests> tag. You can place comments above the <SemiconductorModuleTests> tag, below the </SemiconductorModuleTests> tag, or to the right of the recognized data columns, as shown in the following table:

Column Tag Description Format
<SequenceName> Name of the sequence. The tool uses this column, if present, to match each row in the test limits file to locations in the sequence file. String
<StepName> Name of the step. The tool uses this column, if present, to match each row in the test limits file to locations in the sequence file. String
<StepId> Unique ID of the step automatically generated by TestStand. The tool uses this column, if present, to match each row in the test limits file to locations in the sequence file. String
<TestName> Name of the test. String
<TestNumber> Number of the test. Importing an empty string indicates the lack of a test number. When you enable the Update limits in matching tests option, the tool uses this column, if present, to match each row in the test limits file to locations in the sequence file. If a step does not contain any tests, this field displays No Tests.
Note Use the ECU Action step instead of the ECU Multi Test step if the step does not contain any tests.
 Number
<Pin> Name of the pin or pin group. For a pin group, test data for individual pins in the pin group are not included in the file. String
<LowLimitExpression> Lower limit expression. Blank for Pass/Fail tests. String
<HighLimitExpression> Upper limit expression. Blank for Pass/Fail tests. String
<ScalingFactor> Scaling factor used to display the data, high limit, and low limit fields. The Units Prefix column of the Supported Scaling factors table lists valid values for scaling factors.
Note If you use the <ScalingFactor> column, you cannot use the individual field <LowLimitScalingFactor>, <HighLimitScalingFactor>, and <DataScalingFactor> columns.
 String
<LowLimitScalingFactor> Scaling factor used to display the low limit field. The Units Prefix column of the Supported Scaling factors table lists valid values for scaling factors. String
<HighLimitScalingFactor> Scaling factor used to display the high limit field. The Units Prefix column of the Supported Scaling factors table lists valid values for scaling factors. String
<DataScalingFactor> Scaling factor used to display the data field. The Units Prefix column of the Supported Scaling factors table lists valid values for scaling factors. String
<ComparisonType> Evaluation Comparison Mode. Included in file only when property contains non-default value. Blank for Pass/Fail tests. String
<Units> Base units of the limits. Blank for Pass/Fail tests. String
<EvaluationType> Evaluation type. Valid values are Pass/Fail or Numeric Limit. String
<TestNameExpression> Test name expression. Included in file only when non-empty test name expressions exist in the sequence file. String
<TestNumberExpression> Test number expression. Included in file only when non-empty test number expressions exist in sequence file. String
<PublishedDataId> Published data ID. Included in file only when non-empty published data IDs exist in the sequence file. String
<TestDataSource> Test data source expression. Included in file only when non-empty test data source expressions exist in the sequence file. String
<ExportLocation> Expression for location to which to export data (Export Data To column in the Tests table). Included in file only when non-empty export data to expressions exist in the sequence file. String
<NumericFormat> Test numeric display format that applies to the high limit, low limit, and data. During export, the ECU Software Toolkit retrieves the value from the Data property of the test. Included in file only when non-default numeric formats exist for any tests in the sequence file. String