Skip to end of metadata
Go to start of metadata





Installation, Licensing, and Support


Where can I download the EFT Module for TestStand?

Contact and we will send you the installation media, which includes a 30-day trial.


Where does the EFT Module get installed?

The EFT Module contains many different components, including applications (EXEs), TestStand Step Types, Documentation, and Reference Examples & Templates. Each component gets installed to a different area, though most are located within the TestStand Public folder.

For a full list of installation directories, see EFT Module - Component Installation Locations

How do I license my EFT Module for TestStand?

Refer to the Knowledge Base article on license activation: EFT Module Licensing (Obtaining, Activating, Transferring)


What types of license are available?

Every purchased copy of the EFT Module for TestStand comes with two license keys

License TypeCostActivationsUsage
Developer$3,995 per developerOne activation per license keyCreating and modifying TestStand Sequences with EFT tools, including the Hardware Access Framework.
Execution DeploymentIncluded with Developer LicenseUnlimited activations per license keyExecution of TestStand sequences that use EFT tools (Manufacturing Operator Interface, Sequences using the HAF, Database Reporting)


Each purchased developer license comes with support and upgrades for 1 year from the purchase date. Additional upgrades and tech support may be provided on a yearly basis for an additional $1495 per license per year. See EFT Module - License Details for more information.

For more information, see EFT Module - License Details



Will my license expire and cause my production to stop?

No.  Licenses (both development and deployment) do not expire for a particular installation version.  However, if you choose to upgrade versions for new features, you may be required to upgrade your license.


What are the various components and features of the EFT Module for TestStand?

The major components of the EFT Module are:

  • Manufacturing Operator Interface
  • Hardware Access Framework
  • SQL Database Reporting
  • Test Architecture

For specifics on each component, see Component Overview


Is source code provided / is the EFT Extensible?

Source code is provided for some portions of the EFT, while other portions are extensible by overriding or replacing sub-components. See Component Exensibility and Source Code for more details.


Why do I have two UUT Test Files Folders?

In versions of the EFT earlier that 2.3.9, the UUT Test Files folder was located at <User Documents>\UUT Test Files\. If you have installed a version of the EFT before 2.3.9 and then upgraded to a version 2.3.9 or later, you will have two UUT Test Files locations, one in public documents and one in your user documents. In that situation it is recommended that you cut and paste anything in the user documents location to the public documents location, without overwriting--the code already installed in the Public Documents folder will be the most up-to-date and should not be overwritten. After that you can remove the UUT Test Files folder from the User Documents location. Note that this cut-paste operation may affect any custom code you have written that references absolute paths in the old location, so it is recommended that you make a backup you can easily restore before you move anything. If you are concerned about absolute paths in your code, you can maintain both the User Documents and the Public Documents UUT Test Files locations, but only the Public Documents UUT Test Files location will be updated in new EFT releases.   



Operator Interface


How do I set what part numbers/sequences/fixtures are available in the drop-down menus?

The EFT Manufacturing Operator Interface utilizes a Test Manager screen that allows Manufacturing Engineers and Supervisors (with an appropriate login) to define which Test Sequences are executed by which UUTs using which Fixtures/ITAs.  Refer to EFT Manufacturing OI - Test Sequence Loading and Mapping for more information on mapping test sequences to UUTs.


Can I use the EFT Manufacturing Operator Interface to test sequences that are not configured in the drop-down menu?

Yes!  While the EFT Manufacturing OI is set up to allow part-number based sequence selection, users are still able to select File > Open Sequence File to select a specific sequence file.  However, ITA/Fixture ID Checking will not work in this mode.  Browsing for a sequence file is best performed from the Debug Sequence File interface, as described in EFT Manufacturing OI - Debug Interface.


How do I configure a Part Number and/or Sequence to be able to be tested on multiple different fixtures?


What types of Fixture/ITA electronic identification are available?



Can I customize the Operator Interface?


What debugging features are available?


How do I add new users, will their names show up in the TestStand reports?




Hardware Access Framework


How do I create a new HAF Configuration File?

  1. Open the HAF Configurator.exe
  2. Click File>New


Where does TestStand expect HAF files?

HAF files are automatically loaded by TestStand from the TestStand Public Directory located on the main computer drive (see HAF File Locations).
These files are used in development and execution and include the LabVIEW code, TestStand Step Type Palettes, Icons, and more. 


Initializing HAF keeps throwing errors it can't find an instrument, how do I configure my instruments in the HAF Configuration File?

Instruments are defined in the first section if the HAF Configuration File. 'InstName' can be whatever you want to call the instrument for the rest of the configuration file.
'Address' however, needs to match a named instrument or alias in NI MAX. COM ports are acceptable for non-NI components (see HAF manual or HAF Driver Descriptions).

Why do I get Error 7 when Initializing HAF?

Error 7, (executing substep 'Pre'. Channel Config not found.) occurs when the Initialize HAF step can't find the channel configuration file.
There's multiple possible causes for this issue, see Error 7 on Initializing HAF for troubleshooting.


How can I programmatically change HAF parameters for run-time?

HAF parameters can be programmatically changed during run-time using Pre/Post-Expressions.
Some typical use cases are for multi-threaded Process Models, looping measurements, and functional blocks
See Programmatic access to HAF parameters (including aliases).

Can I use HAF with multi-threaded Process Models?

Yes! The HAF is fully capable of being used in Batch and even Parallel Process Models. Some rules apply based on hardware limitations.
Multi-threaded testing is used to test multiple UUTs in a batch or fully independent sockets. This type of testing can enhance throughput among other benefits.
See Using HAF with Batch Process Model on how to implement the HAF for multi-threaded Process Models.


How do I loop on measurements?

See Looping Measurements, please read Programmatic access to HAF parameters (including aliases) prior.

How can I create repeated functional blocks?

See Repeated functional sequences, please read Programmatic access to HAF parameters (including aliases) prior.



How can I use HAF VIs inside of custom code modules?


My Insertion Palette is missing step types, how can I fix this?

See Disorganized HAF Insertion Palette for the Insertion Palette Cleanup Utility.















  • No labels