Overview of Test Program Components
- 更新日2023-02-17
- 6分で読める
Overview of Test Program Components
An ECU test program can include a pin map file, a main sequence file, subordinate sequence files, code modules, test limits files, and configurations.
- Specify the pin map, InstrumentStudio project, and test limits files
- Create and edit test program configurations
- Configure other settings for the test program
Select or click the Edit Test Program: <filename> button on the ECU Software Toolkit toolbar to launch the Test Program Editor for the sequence file.
Use the TestStand Sequence Editor to complete test program development, configuration, debugging, and execution tasks.
Use the following figure and table to learn about the components of test programs and test stations.
| Component | Description |
|---|---|
| TestStand Sequence Editor | The TestStand Sequence Editor is the development environment in
which you create, edit, execute, and debug sequences and the tests
sequences call. Complete the following steps to launch the sequence editor.
|
| Pin Map | A pin map defines the instrumentation on the
tester, defines the pins on the DUT, and defines how the DUT pins are
connected to the tester instrumentation for each test site. Use the
Pin Map Editor to view, create, modify, and save pin map
files. The pin map file also serves as the channel map file. Select or click the Edit Pin Map File
button on the ECU Software Toolkit toolbar to launch the Pin Map Editor. Alternatively, you
can select and then select Pin Map in the
Test Program Editor to launch the Pin Map
panel. Click the Open file for edit |
| Test Program Configurations | Test program configurations define values for conditions that a
test program can reference at run time and the test limits file that
loads before running a test lot. A test program can use multiple
configurations to implement multiple test flows using the same sequences
and code modules. Select and then select Configuration Definition in the Test Program Editor to define configuration settings. |
| Test Limits Files | Test limits files define test limits the test
program loads before running a test lot. The test program replaces test
limits in test steps in the sequence file with those specified in the
test limits file. You can embed test limits in the sequence file to
prevent viewing or tampering with the limits. Select and select Test Limits Files in the Test Program Editor to specify one or more test limits files to make available to the test program configurations. The test program configuration specifies the test limits file that loads before running a test lot. You can
create a test limits file by selecting or by clicking the Export Test Limits
from |
| Main Sequence File | The main sequence file contains the sequences that define the
test flow by specifying the test steps to execute and the
order in which to execute them. The sequence file contains one main
sequence named MainSequence and can optionally include one or more
subsequences with corresponding test steps. You can use multiple
sequences in a test program to keep the test code modular and organized.
The ProcessSetup and ProcessCleanup sequences are special sequences that TestStand calls at certain times. TestStand calls ProcessSetup once before starting execution and calls ProcessCleanup after execution completes. Initialization and cleanup of instrumentation typically occurs within these sequences. |
| Test Steps | Test steps in the sequence called by the ECU Action or ECU Multi Test step are instances of TestStand and ECU Toolkit Measurement Control step types that control instrumentation on the tester, take measurements from the DUT, and pass measurement values back to ECU Multi Test steps. ECU Multi Test steps perform tests by comparing measurement values obtained by test steps inside the called sequence to test limits stored on the step. You also define test numbers and names in the ECU Multi Test step. |
| Lot Settings | The test program can use lot information to determine how to
execute tests. For example, lot settings might dictate which steps
execute, what temperature to apply to a DUT, what voltage to use, and so
on. You can customize how ECU Software Toolkit obtains the
settings. Select in the TestStand Sequence Editor or click the Configure Lot button in the default ECU Software Toolkit operator interface to launch the Configure Lot Settings dialog box. |
| Reporting and Data Logging | You can generate ECU Software Toolkit reports and data logs, such as Test Results Logs. You can customize the filename of the report or data log file. |
| Test Step Debugging Tools | TestStand includes several tools for debugging sequences and related components in a TestStand test program and in ECU Software Toolkit test programs. Additionally, the TestStand Sequence Editor integrates with supported application development environments to debug test steps. |
| Instrument Drivers | NI provides instrument drivers to configure, customize, and implement your instrument control applications. The ECU Software Toolkit has native support for multiple NI instrument drivers. |
| Soft Front Panels | Most NI modular instruments include soft front panels (SFP) to allow you to quickly configure, troubleshoot, or debug your instrument or DUT. Launch the soft front panels from MAX by selecting . You can also use InstrumentStudio, a software-based front panel application, to monitor, control, and record measurements from supported devices. |
| Measurement and Automation Explorer | The ECU Software Toolkit pin map defines the instruments required
for a test. Measurement & Automation Explorer (MAX) helps you
configure the instrument connected to the system. For a test program to
execute properly, the instrument names in the pin map must correspond
with instrument names configured in the system. MAX helps you complete
the following tasks:
(Windows 8.1/8) Click the NI Launcher tile on the Start screen and select NI MAX to launch MAX. (Windows 7) Select to launch MAX. |
button to launch the
Pin Map Editor. 
button on the ECU
Software Toolkit toolbar to export test limits from a sequence file
into a tab-delimited test limits text file. You can import a test
limits file by selecting 
button on the ECU
Software Toolkit toolbar to import test limits from a tab-delimited
test limits text file into a sequence file. When you import test
limits from a text file, you can update limits in matching tests or
replace all tests in matching steps.