Advanced usage of TestStand Deployment Utility

I would like to automate the build process for my test stand systems.
Is there a way to call and build a .tsd automatically from labview or command line?
Alternatively is there a way to call post actions after a successfully completed build (i.e.. Zip and move files etc etc)
Any help or pointers would be greatly appreciated.
Chris
Solved!
Go to Solution.

I don't think you can automatically create a tsd.
But once you have a tsd file, you can automate the deployment process by cmd line such as "DeploymentUtility.exe path" -build "tsd_file_path"
After deployment, you can check DeploymentUtility.log in your cfg folder to figure out whether the build is successful or not
Others such as zip or move files are very basic, you can do it using any script language
CmtGetCurrentThreadID()
Chenny Zhenyu Wang
Certified LabVIEW Architect
Certified TestStand Architect

Similar Messages

Problem with deploying FPGA host VIs using TestStand deployment utility

I am using a PCI-7831R FPGA to control an automated test fixture. I have several host VI's that I am calling from TestStand (4.2.1) in order to control the 7831R. The host VI's that TestStand calls are setup as sub-VI's and are used for various things such as opening an FPGA reference (which is bound to a strict type def), downloading and executing the files on the 7831R, reading writing to controls, and finally closing the reference. In the sequence file, I am passing the reference values as a file global so that the host sub-VI's can communicate correctly. I have all functionality working correctly in TestStand on my development PC. When I go to deploy this to a production PC, I get errors when the sequence file trys to load the first host VI. The error basically states that the VI is broken - try to open and run it (which I can't because I have no development license on the production PC). I am currently trying to deploy this to another development PC to see if I can track down where the VI might be breaking.
I have included the lvbitx and strict type def control that the host subVI's reference in my deployment files. I can't think of anything that I might be missing. Is there any good documentation on exactly which files I need to include in the deployment when using FPGA Host VIs (the TestStand reference manual is pretty vague at best)? It seems that any documentation that I read says the TestStand deployment utility will analyze all VI dependencies (other than shared variables). On a side question, is the strict type def considered a shared variable?
Has anyone successfully deployed a sequence that calls host VI's? Any help would be greatly appreciated. If any of the above needs further clarification please ask away and I will be happy to give more details.
Thanks,
Mike

Hi hawkstringer
Do you encounter this problem using a deployed version of your code? Note that the subject of this topic is about deploying an FPGA application.
I forgot I posted here, in the mean time I've managed to deploy my application. I think my problem was solved when I included all necessary drivers and components (but I'm not absolutely sure). I included the following:
NI IVI Compliance Package
NI FlexRIO
NI PXI Platform Services Configuration Support
NI R Series Multifunction RIO
NI DAQmx Core Runtime
NI DAQmx MAX Configuration Support
NI RIO
Good luck!

Assessing Command 'Analyze Source Files' via Command Line when running TestSTand Deployment Utility

Our Software Configuration Manager is running the TestStand Command Line Deployment Build Tool (Ref: https://decibel.ni.com/content/docs/DOC-38947).
        When he builds the application, the code will not be at the same location it was in development.
If you are Manually running the TestStand Deployment Utility, This is not a problem because everything is relative in the workspace.   Simply go to the Distributed Files Tab (of TestSTand Deployment Utility) and hit the, "Analyze Source Files" button. This finds the required files and apparently creates an updated hard path to be used during the build (probably in the *.tsd).
PROBLEM: We auto-run the Command Line Deployment Build Tool (Command Line), and we do not have access to the, 'Analyze Source Files' command.
            As a result, our build consist of many warnings and the output is missing many files (the location of the files have not been updated).
If we could access the 'Analyze Source Files' Command via command line, that would fix the issue.
FYI: We use an automatic builder called Quick Build as our builder.
Attachments:
TestSTand Deployment Utility-Distributed Files Tab.PNG ‏76 KB

Unfortunately it looks like Analyze Source Files does not have a command equivalent for the command line based on this article and attached PDF:
https://decibel.ni.com/content/docs/DOC-38947
That may be a good post for the TestStand Idea Exchange for consideration in future versions of TestStand.
Michael K.

TestStand Deployment Utility API

Is there any API for the TestStand Deployment Utility I can use in labview to automatically launch a TSD file and build the deployment. I would like to create a little labview program which automates the whole process of creating deployments for me, especially when it is a minor change in subVI underneath, and none of the deployment configuration needs changing.
Any info would be appreciated!

Hi kewsvnet
Sorry the the delay in getting back to you.
There isn't currently a TestStand Deployment Utility API for LabVIEW, the closest I think you can get at the moment is to do a command-line deployment build by calling the System Exec VI.
i.e.
"C:\Program Files\National Instruments\Teststand 2010\Components\Tools\Deployment Utility\DeploymentUtility.exe" build "C:\mydeployment.tsd"
As the string input should build mydeployment.tsd
Note:This is an undocumented internal feature we use for Testing the deployment utility. The interface is very limited - you can do a build but there is no way
to set parameters and no return value so you have to parse the log to determine if the build succeeded. There is further discussion of this here in a previous forum post.
Kind Regards
Chris | Applications Engineer NIUK

TestStand Deployment Utility Error

I am getting the error below when attempting to build a TestStand deployment. I am running TestStand 4.2.1.83 and LabVIEW 2009 Service Pack 1 Version 9.0.1f3. Any help would be appreciated as I cannot find any of the VIs mentioned in the error. Thanks!
Starting Log.
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
10:15 AM
Internal error code 6503 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Exception occured in LabVIEW: LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select <b>File>>Open</b> to open the VI and then verify that you are able to run it. in Dynamically Call Build VI Distribution LV 8.6 or Above - TestStand.vi->TestStand - Call Build VI Distribution for Unique VI Hierarchies LV 8.6 or Above.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build process is done.
10:15 AM
Aborted
Solved!
Go to Solution.

Hello George Mah,
I found CARs # 258761 and # 3OP9RE6I for TestStand which may be related to this issue and to error 6503. The error was created because VIs with duplicate names were included in a deployment. Would you verify that you do not have any duplicate VIs in your project? Are you noticing anything else strange with your deployments? Have you tried creating a blank deployment that only includes the TestStand engine or a run-time engine?
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

Error code 1127 when using teststand deployment utility

I'm have installed on my pc Teststand 3.0 and labview 7.0 -this error occurs during build
Error Code:1127
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Open VI Reference in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

>>>>>>>ok, I'm getting a different error code: error code 7 instead of a error code 1127 with the error:
Error Code:7 Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW
error: Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI
Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI
Distribution AX Wrapper.vi.ProxyCaller
>>>>>>>>And I did a mass compile of the directory mentioned above and I got this error:
#### Starting Mass Compile: Thu, Jul 15, 2004 9:44:04 PM
Directory: "C:\Program Files\National Instruments\TestStand
3.0\Components\NI\Tools\Deployment Utility"
CompileFolder: error 13 at C:\Program Files\National Instruments\TestStand 3.0\Compon
ents\NI\Tools\Deployment Utility\DeploymentUtility.exe
#### Finished Mass Compile: Thu, Jul 15, 2004 9:44:17 PM

Teststand deployment utility used for different versions of TestStand

I am in a situation where I developed a test sequence in TestStand 3.5 and used the deployment utility to deliver an installer to a customer with TestStand 2010 Base deployment Engine. We are seeing the following error "This installer installs file to the TestStand directory. You must first install TestStand or the TestStand runtime engine version 3.5 to create the TestStand directory."
My question becomes, is it even possible to make an installer with TestStand 3.5 and have someone else use with TestStand 2010 Base deployment engine? What then needs to happen to get past the error if it is possible?
Thanks,
Bill
John 3:16

No you cannot use 3.5 sequences on the 2010 engine.
You need to install the 3.5 engine on that machine. The license will still work and you will need to use the version selector to go between the two. You can include the engine in your installer build.
TestStand is a scripting language. Because sequence files are not compiled it is possible to use unsupported functions on the wrong version. Therefore, the engine just won't run other versions. Also, you need to switch versions because they use different adapters, engines, dlls, folders, etc... The version selector changes settings on your machine for all those things for that version.
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

TestStand deployment utility crashes

Hi,
Trying to deploy a dummy test with the basics that will be used in production. It includes (all LabView) database access, report generation, DAQ control & GPIB IF and steps to exercise all to ensure it is working properly. In the editor, sequence runs fine, hits the database table with data, generates the test report and all that but...problem is when I go thru the deployment steps and use the deployment utility it crashes. Fast forward thru some debugging and head banging and I get to the root problem. I created a report class in LabView to handle the report tasks. The class control contains a class object reference to the actual report that is being generated. This reference is created using the New Report.vi that comes with LabView. Throughout the sequence I populate the report with the data I collect and print it as a pdf at the end. All this works great in the Dev environment for TestStand.
So now to the problem... when this report object is included in the class object it causes the deployment utility to error out with the following info from the log...
+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
3:02 PM
LabVIEW Version: 10.0f2 (2010) (32-bit) English
Internal error code -2147023170 Processing VIs...
The remote procedure call failed.
in Dynamically Call Method in LLB - TestStand.vi:3->Dynamically Call Update Paths in Projects - TestStand.vi->Update LabVIEW Project Links - TestStand.vi->Package VIs - TestStand.vi->Build Create Image - TestStand.vi->Build - TestStand.vi->Distribution Wizard GUI - TestStand.vi->Deployment Utility Splash Screen - TestStand.vi
An installer was not created due to an error
The build is finished
3:06 PM
Aborted
+++++++++++++++++++++++++++++++++++++++
I have built a test sequence, LV project with a class object that has only 1 thing... the reference I mentioned above. With this config it still errors out. Next I deleted that object and put in class reference used in another part of the project and it completes the build as expected. I used the TestStand Workspace method in the deployment utility.
Any ideas? (hope that is enough info...)

OK, I included the folder with the report VI's in it and I get the same result. First build below is without the class object on the diagram,
2nd is with it. I tried a couple of things including adding the New Report VI to the diagram, same result.
+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
1:49 PM
LabVIEW Version: 10.0f2 (2010) (32-bit) English
Making an installer, please wait...
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Scanning files...
Updating files...
Creating merged database...
Creating installer files...
Build complete successfully.
Copying additional setup files
Compressing installer files
Done building deployment
The installer is finished
Loading product deployment information
The build is finished
1:52 PM
Warning: The installer does not include the following LabVIEW Run-Time Engine(s) required to execute VIs:
This Installer includes VIs compiled with LabVIEW 10.0.
+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
1:53 PM
LabVIEW Version: 10.0f2 (2010) (32-bit) English
Internal error code -2147023170 Processing VIs...
The remote procedure call failed.
in Dynamically Call Method in LLB - TestStand.vi:3->Dynamically Call Update Paths in Projects - TestStand.vi->Update LabVIEW Project Links - TestStand.vi->Package VIs - TestStand.vi->Build Create Image - TestStand.vi->Build - TestStand.vi->Distribution Wizard GUI - TestStand.vi->Deployment Utility Splash Screen - TestStand.vi
An installer was not created due to an error
The build is finished
1:55 PM
Aborted
+++++++++++++++++++++++++++++++++++++++

LabVIEW VI causes TestStand Deployment to fail

Hello,
I have a problem with the attached VI. Any time I include it in a deployment, I get an Error that says "Internal Error Code 1 processing VIs... Installer not created due to an Error"
The VI and a simple sequence file are attached.
Attachments:
IsMyProcessRunning.vi ‏13 KB
ProcessTest.seq ‏5 KB

Simon,
The following (below) is the Deployment improvements for TestStand 4.2. I haven't been able to look at the VI of the original post so I dont know of the actual problem but there are still issues with the deployment tool in TS4.2
Regards
Ray Farmer
TestStand Deployment Utility Improvements
The TestStand Deployment Utility now uses improved internal caching to accelerate analysis and build times. Additionally, the LabVIEW VI Options dialog box includes the following new options so you can choose between faster performance and improved error handling:
Check for Broken VIs During Analysis—When enabled, the TestStand Deployment Utility checks for broken VIs during analysis. This option is disabled by default to improve performance. Enable this option when you want to debug VI errors.
Check for Broken VIs After Build—When enabled, the TestStand Deployment Utility checks for broken VIs in the image directory when building an image. This option is enabled by default to ensure that distributed files do not contain broken VIs. Disable this option for better performance if you are rebuilding and have not made changes to VIs.
Remove Unused SubVIs—Removes unused polymorphic subVIs and disconnects type definitions when building. This option is disabled by default for backward compatibility. Enable this option for better performance and to deliver a smaller number of subVIs.
Note Enabling the Remove Unused SubVIs option disables certain editing and debugging options on the deployed system, such as wiring a new type to a polymorphic VI or making type changes across several VIs by editing a type definition.
The Deployment Utility also better integrates with LabVIEW 8.6.1 or later for improved build speeds and deployment of advanced LabVIEW features, such as VIs that include LabVIEW object-oriented programming.
The Installer Properties section of the Distributed Files tab of the TestStand Deployment Utility also includes a new Force File to Install option. Enable this option to force the installers the deployment utility builds to always overwrite existing files.
Refer to Chapter 14, Deploying TestStand Systems, of the NI TestStand Reference Manual and to TestStand Deployment Utility for more information about the TestStand Deployment Utility.
Regards
Ray Farmer

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

Deployment Utility - log file errors/warnings not clear

Hi,
I'm doing my first deployment and have few questions:
1) I tried to deploy ONLY the TS user directories. I checked the 'Deploy Files in TestStand User Directories' option and did not check 'Install TestStand Engine' since I deploy it into a system with TS3.0+CVI7.0 software(same as the source).
The process was successful by I get the following warnings in the log file.
Starting Log.
Building...
5:47 PM
An installer is being created.
The installer is finished
The build process is done.
5:48 PM
Warning: You may need to add any sequence files referenced by the following expressions:
"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Single Pass', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
+++++++++++++++++++++++++++++++++++++++
What does it mean? What to do about it?
2) The utility does not include the cfg/TypePalettes where I have a my own file.
Is there a reason to it? Do I need to include it manually?
3) When I included workspace in the utility I get the following errors:
Starting Log.
Processing Workspace...
Done processing workspace file
+++++++++++++++++++++++++++++++++++++++
Processing Workspace...
Done processing workspace file
Building...
6:08 PM
Error could not open LabVIEW
Distributing VIs requires the LabVIEW Development System
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build process is done.
6:08 PM
Error Code:-2147221164
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
+++++++++++++++++++++++++++++++++++++++
In order to eliminate the problem source I un-checked the files presented by the 'Analyze Source Files' until all of them are un-checked. Even in that case I get the error message.
What does the message mean?
What to do about it?
I don't use any LV in my system!!!!!
Thanks and my apology for the long message
Rafi

Hi Rafi,
On #1 the warnings appear whenever you have an expression that specifies a sequence file because many expressions are not valid until runtime, you can ignore it as long as ALL sequences that expression may evaluate to are included in the Workspace.
>2) The utility does not include the cfg/TypePalettes where I have a my own file.
>Is there a reason to it? Do I need to include it manually?
No it does not include it because it is not needed unless you plan to edit on the deployed sequence (generally not recommended). If you add a custom type to a sequence the sequence file will have a copy of the type. You can include the types palettes manually in the workspace if desired.
>3) When I included workspace in the utility I get the following errors:
>What does the message mean?
The deployment utility thinks you have a VI to deploy, it is trying to load LabVIEW and failing because LabVIEW is not installed.
>What to do about it? I don't use any LV in my system!!!!!
Somewhere there is a .vi or .llb in the system. Find the VI(s) and uncheck them. I did find a bug that the deployment utility caches the flag indicating if a VI is present, but it is easily worked around: Save a tsd file, Press the New button and then reload the tsd.
-Rick Francis

Deployment Utility Errors

Hi,
We're having a problem with building an installer using the TestStand Deployment Utility. We added some sequence files, VIs and image files to an existing installer and now it doesn't work.
Below is an extract from the log file:
Internal error code -2147023170 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
The remote procedure call failed.
in Dynamically Call Build VI Distribution LV 8.6 or Above - TestStand.vi->TestStand - Call Build VI Distribution for Unique VI Hierarchies LV 8.6 or Above.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build process is done.
9:19 AM
Aborted
If we split it into 2 installers, with the majority of the LabVIEW VIs in one and the rest of the code in the other both installers build properly and when installed on another PC everything seems to work as expected.
We have mass compiled all of the VIs, and opened and re-saved all of the new ones. We also tried adding more memory to the PC as we wondered if the installer was just too big (there are over 2000 custom VIs) but that didn't help.
We are using LabVIEW 2009 and TestStand 4.2.1.
Any suggestions would be greatly appreciated!

CJames,
The error message you are getting means that the connection from the Deployment Utility to LabVIEW was broken unexpectedly, probably because LabVIEW had some problem it could not recover from. From your investigation it seems like the problem is that your deployment is so big that LabVIEW is running out of memory while deploying. There are several ways you can fix or mitigate this problem.
The easiest way would be to set the /3gb switch which makes LabVIEW run in large address-aware mode. For more information please read this KB. This will allow LabVIEW to use more virtual memory and it should allow the build to complete, however, this is only a temporary solution because if your project continues growing there will come a point where even this new amount of memory will not be sufficient.
Another thing you can do from the architectural point of view is splitting your VIs into different projects (and calling the VIs in the context of a project from within TestStand). The Deployment Utility will create a different deployment for every project, which means that some of your VIs which are currently being loaded together while deploying would not be loaded together anymore. This, however, is more complicated because you have to make sure that the VIs are not part of the project anymore (that is, they are not dependencies which would include them anyway) and you have to make sure that they are divided in logical groups.
Hope this helps,
- Francisco

Deployment Utility

As far as I can tell, it's impossible to get the Teststand Deployment Utility to work.
It also appears to be impossible to make contact with anyone at NI who can shed light on the total dysfunctionality of the utility.

Hey Paul,
I'm the TestStand Product Support Engineer at NI, and I'm sorry to hear you're having trouble with the Deployment Utility. I've been working with one of our Applications Engineers on some issues you brought to us, so I'm assuming this is related to the same issue--if not, please let us know. Regarding the existing issue, we'd like to set up a remote screenshare session with you to take a look at what's going on. The Applications Engineer should be contacting you soon to figure out a time that works for all of us.
If you would like to get some input from the other forum users, please feel free to post some details on the issue you're experiencing. I'll look forward to working with you soon to troubleshoot this.
Daniel E.
TestStand Product Support Engineer
National Instruments

Deployment Utility copies my MAX configuration to the target system

Hi,
I am creating an Installer for TestStand 3.5 and I have found that my MAX device configuration is carried to the target system. How can I prevent the installer from coping this configuration to the target system? My Labview VIs use VISA 4.1 to access Serial Ports.

Hello goldee,
In the TestStand Deployment Utility, select the Installer Options tab, and then click the Drivers and Components... button. Make sure the Include Hardware Configuration from Measurement & Automation Explorer checkbox is unchecked.
Let me know if that fixes it or not.
Kristen
National Instruments

TestStand Deployment Not Installing Files

TestStand 3.1
We have created a custom OI and Process Model and we have attempted to
create an installer using the TestStand Deployment Utility. The
problem is that when the installer is first run on the target system,
some files are not being installed. We had a similar problem with
the Distribution Kit functiontionality of CVI 6, and were never able to
fully resolve the issue.
Basically the installer examines files that already exist on the target
machine and will not overwrite them if they have been modified.
The installer is smart enough to examine version numbers inherent to
DLLs and EXE files (and adding REINSTALLMODE=amus to setup.ini causes
these types of files to always be overwritten). However, for
other files such as *.ini and *.seq files, there seems to be no way to
force the installer to overwrite these files.
The workaround that we used previously was to run the installer 3 times
(once to install, once to uninstall which deletes all files including
the old versions that were not overwritten, and then once to actually
install the desired files). Is there a way around this with the
TestStand Deployment Utility? We are actually considering
bypassing the installer altogether and just copying the files in the
image directory that the Deployment Utility creates.
Thanks,
Peter

Hi Peter,
Thanks for the information. I am not sure if the installer will recognize the sequence file version number. Are you deploying a Process Model from the NI folder, or have you copied it into the User folder? Are you adding the Process Model and INI files to a project in your workspace and deploying the workspace or are you deploying them by selecting to Deploy Files in TestStand User Directories on the System Source tab of the Deployment Utility?
In other words, what file specifically are not being installed correctly? What is their path on the development machine and what is the target path?
One last question, if the target is a new system and has not had a TestStand test system deployed to it, how does it have sequence and TestStand INI files on it already? Are you installing TestStand on the target machine before deploying a test system?
Regards,
Eric M

Advanced usage of TestStand Deployment Utility

Similar Messages

Maybe you are looking for