Deploying ECU Software Toolkit Test Programs
- Updated2023-02-17
- 3 minute(s) read
Deploying ECU Software Toolkit Test Programs
Complete the following steps to use the TestStand Deployment Utility to deploy a test program.
- Complete the following steps on the Mode tab of the deployment
utility:
- Select the Deployable Image Only option.
- Select the Create new Full Deployment option. NI recommends that you create a new Full Deployment, save the deployment to increment the Deployment Version, and store the deployment in a source code control system each time you create or update a deployment.
- Complete the following steps on the System Source tab:
- Place a checkmark in the From Directory checkbox and specify the test program directory.
- Place a checkmark in the Include Subdirectories checkbox.
- In the Location of Deployable Image field, specify the location in which to save the deployable image.
- Click the Distributed Files tab and select Yes to analyze the source files.
- Click the Build Status tab to display the analysis results. Resolve any issues before completing the next step.
- Complete the following steps on the Distributed Files tab:
- Select the files to include in the distribution. Use the Distributed Files pull-down menu to filter the display.
- If you have LabVIEW code in the sequence, click the LabVIEW Options button to launch the LabVIEW VI Options dialog box, which you use to specify LabVIEW options.
- In the LabVIEW VI Options dialog box, enable the following options in the Packed Project Library Options section of the dialog box and use the default values for the other options in this dialog box.
- Output VIs to a Packed Project Library ()
- Copy files from vi.lib before Build
- Copy files from user.lib before Build
- Copy files from instr.lib before Build
- Click OK in the LabVIEW VI Options dialog box.
- Complete the following steps on the Distributed Files tab:
- Click the Save As button if this is the first time you are configuring a deployment for the test program to save the distribution configuration for the deployment. Click the Save button when you modify an existing deployment to increment the version number of the deployment.
- Click the Build button to build the distribution.
- Click the Save button to auto-increment the Deployment Version field on the Mode tab.
- Complete the remaining tasks in the Deployment Process Overview to transfer the deployment to a tester and validate the deployment.
Consider the NI recommendations for installers, and protections for test programs and test limits as you design and create deployments for an ECU test system.
Installer Settings for Deploying ECU Software Toolkit Test Programs
Use the following recommended settings to create a simple installer with the deployment utility:
- Use the Deployment Version option on the Mode tab of the deployment utility to specify a version for the distribution. Increment the version with each release of the test program distribution.
- Do not enable the Install TestStand Runtime option or include any software in the Drivers and Components dialog box. Do not use the test program deployment to control the software installed on an ECU test station.
- Enable the Do not Ask User for Installation Directory option on the Installer Options tab of the deployment utility and set the Default Installation Directory option to install the test program in the same location on all test stations.
After you create a deployment, save the deployment specification file (.tsd) so you can use the same configuration to build newer versions of the installer or to create patches. Additionally, on the Build Status tab of the deployment utility, save the deployment build status log files to use to troubleshoot issues.
Protecting Test Programs and Test Limits from Editing and Viewing
You can password protect sequence files to deter editing and viewing sequence files in the sequence editor and in operator interfaces.
To protect test limits files, use the Embed Test Limits File option on the Test limits Files panel of the Test Program Editor to embed the external test limits files in the test program sequence file before you password-protect the test program sequence file.
Related Information
- TestStand Deployment Utility
- Deploying TestStand Systems
- Mode Tab - TestStand Deployment Utility
- System Source Tab - TestStand Deployment Utility
- Distributed Files Tab - TestStand Deployment Utility
- Build Status Tab - TestStand Deployment Utility
- LabVIEW VI Options Dialog Box
- Deployment Process Overview
- Installer Options Tab - TestStand Deployment Utility
- Drivers and Components Dialog Box
- Advanced Tab - Sequence File Properties Dialog Box