Deploying TestStand

I am trying to use the Deployment Utility to deploy TestStand to a target. I have modified the TestExec.prj through CVI and have created an installer using CVI to do that. I have also modified the modelsupport2.prj with some additional GUI's. I have also made the necessary changes to all the other files required. I have sone this several times with other versions of TestStand.
For some reason, the deployment utility is not picking up the files located in /All Users/Documents/TestStand 4.1.1/Components/
Therefore it is not getting the modified GUI, the Language files requires, the modelsupport2 files, etc. etc. etc.
I have tried multiple deployments selecting different settings, but nothing seems to work. I finally copied iver the components directory from the development machine to the target and now my modelPanels GUI (which is all modifed in modelsupport2.dll) and it seems to work. However, this is not the correct way, right????
Please advise.

Hi Kelly,
All the files that were modifed in the modelsupport2.dll have been modified in the TestStand public directories, so I know that is not the problem. The files in the normal TestStand directories remain unchanged.
I have also tried to select the "Display files in the TestStand Public Directories", but this is where I run into other problems. The deployment utility reports several errors and warnings that will cause my deployment to fail. The errors reported are as follows:
1. You may need to add any sequence files referenced by the following expressions: (Too many to list, but all have to do with reportgen)
2. The following files were not found: (too many to list, but all are .vi's. I don't even have LabView installed!)
3. The following vi's could not be loaded: (Again, too may to list, but see above.... Labview not installed!)
Regarding the vi's, I have tried to deselect any of the items that seem to be LabView related, but It still gives me those errors/warnings. I have also tried to exclude any LabView items by excluding them in the Labview sections, but that does not help either.
Please explain if possible.
Thanks,
Gregg

Similar Messages

What is the difference between Deploy TestStand system(3.1) and Run Engine Installation wizard(1.0) in Tools menu

Hi,
In TestStand

If you want to run a TS script that calls VIs on a Runtime engine only system you have to use the Deploy TestStand utility to do that. Since a Runtime Engine only system does not have vi.lib you must search all the .seq for VI calls and then traverse all the SubVis to find all the calls to VIs in vi.lib. The Deploy TestStand does that for you. It moves all the VIs and SubVIs to a SupportVI directory and mass compiles them. Once all VIs are within the same directory the runtime engine can find them.
Note: This is a very nasty poorly written tool. I had a deploy that would take about 6 hours to complete. I wrote my own that takes about 4 minutes to complete.

ActiveX Automation server error on deployed TestStand

I'm trying to deploy TestSTand 2.0 + LabVIEW 6.1 on a PC under Win-2K.
I created and deployed TS Engine and Operator Interface for LV.
I try to deploy the "Auto.seq" test from the TS exemples.
Of course, it works on my Development system.
On the deployed system, I got an error : -18351; An error occurred reading an ActiveX Automation server type library.
Step 'Read Database Option - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'
Step 'Read Database Option - Read Options' of sequence 'Get Database Options' in 'SequentialModel.seq'
After having ignored those 2 errors, the tests goes on normally and the report looks fine.
I also get this error opening the database configuration:
Step 'Read Database Option - Construct' of sequence 'Edit Database Options' in 'Database.seq'
From answers already given for similar subjects, I've checked that TsDBOptions.dll is present and registered (done regsvr32...) on the PC.
Can someone help ?
Note: upgrading to more recent TS + LV versions is not a solution!

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

Deploy teststand system Labview instrument drivers

I'm trying to deploy a teststand application but I have an error with some Labview VI's.
I'm using some VI's to control an Agilent 34401A, so Labview instruments library that
is in the default package was used. The error says that Labiew Could no open the following VIs...
I don't want to install the Labview development system on the target machine, so I don't know
how to fix this problem.
I tried to copy the library to a different location an removing the VIs that are not wired (VI Tree.vi),
but I have the same error. (On the sequence was changed the path to the new VI location).
Thanks
Marcos

Marcos,
You can execute VIs using the LabVIEW Runtime Engine, but all of the source VIs must be processed to collect their required dependencies and insure they are compiled in the current version of LabVIEW. The Deployment Utility process VIs from your sequences automatically. The TestStand Reference Manual has a chapter on deploying TestStand systems that should help you get started.
-Rick Francis

Deploy TestStand System error

When I try to run:
Tools>>Deploy TestStand System>>Deployed Files>>LabVIEW Options>>Lock VI Diagrams
I get the following error after I hit the Build key:
Failure : linker.cpp line 2022
LabVIEW version 6.1
I suspect I need version 7.0?? Can anyone confirm this or let me know what I'm doing wrong?

Rick,
I've only got one simple vi in my sequence. I can run the build utility with no errors until I select the "Lock VI Diagrams" option. Note that my error code is now 1035 instead of 2022 like it was previously. The 2022 error was caused by not suppling password in the Lock VI Diagram box.
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node 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
Attachments:
deployment_trial.zip ‏14 KB

Trouble deploying TestStand

Hi,
I have tried many suggestions and configurations but I still cant get my deployed TestStand to run in other PC. I kept getting "Unable to launch the 'LabVIEW .Application' ActiveX automation server. TestStand cannot find a LabVIEW Development System installed in this computer." My test sequence also uses custom process model. Below are the things that I have done:
1. Configured the LabVIEW adapter to use RTE and enable "Always Run VI in LabVIEW RTE" in the LabVIEW Advanced Settings under Module tab.
2. Added configuration .ini files that will be used, including TestExec.ini and TestStandModelModelOptions.ini in workspace.
3. Enable "Install TestStand Engine" and leave Engine Options/ Drivers and Components as default.
Below are my questions:
1. Since I am using custom process model, where should I save this .seq in?Is it in my working directory or TestStand components folder? Reason why I am asking this is because I tried both ways, the latter gave me
"Warning: This problem will cause an error when building a deployable image or an installer. The following file(s) were not found:
rfid_read_write.seq in step 'Reset Test Sequence', sequence 'MainSequence', sequence file 'C:\Program Files (x86)\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\SequentialModel_RFID.seq'"
Obviously rfid_read_write.seq has already been included and present.
2. Should I also include this custom process model .seq file in the workspace/deployment?
3. How to solve the unable to launch LabVIEW.Application issue?
Thanks.

Hi, it looks like the app has trouble starting up:
05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
Did you have any errors on the compile of the code?
You also want to check if the app is deployed (if so you may want to remove it before re-deploying it)

Deploy Teststand system hangs

When I start the Deploy TestStand system dialog and start a build it gets this far
Saving File:
C:\Documents and Settings\cglidden\My Documents\TestStand Deployment\DCT 3p1\Installer\DCTwPick.tsd
Processing Workspace...
Done processing workspace file
Beginning build process, please wait.
8:18 AM
and then hangs. I am using TestStand 3.1 on a Win 2K machine and am deploying because the sequence uses LabVIEW 7.0 VIs. I had a problem before with the utility hanging later in the process but the same fixes do not work here. There is no hidden dialog box stopping things either.
Any ideas?
Thanks,
Chas

Hi Chas,
Are you able to create a simple sequence with just a
message box and deploy that?
Thanks,
Terry S.
Staff Software Engineer
National Instruments

How do I deploy teststand 3.5 to a different directory?

Hi:
We are currently upgrading from a Teststand 2.0.1 infrastructure to Teststand 3.5. To reduce the amount of changes in our existing infrastructure, I'd like to remove the old Teststand 2 directory (c:\teststand) and install Teststand 3.5 to the same directory (c:\teststand rather than c:\Program Files\National Instruments\Teststand 3.5). This will save us going through and changing any sequences or DLLs that are pointing at the absolute directory path c:\teststand. I was able to do this with the regular Teststand 3.5 installer without a problem by choosing 'Custom' and then changing the Teststand directory. Everything then worked fine on the test PC after installation.
However, now I'm trying to create a run-time-engine installer using the Teststand Deployment utility, and I can not figure out how to change from the default Teststand install directory of c:\Program Files\National Instruments\Teststand 3.5. Is there a way to do this? Can this perhaps be done with a spec file, or do spec files not work with the deployment utility?
Thanks,
Dave

Hi Dave,
Sorry for the delay in response. Here's what I've found.
You can modify the setup.ini file that is created with the Deployment
Utility to give you more flexibility with your TestStand Installation.
In the setup.ini file, add
Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR
to
[SingleDirectoryDialog]
DirText1=4
DirText2=7
which results in:
[SingleDirectoryDialog]
DirText1=4
DirText2=7
Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR
This will result in the installer asking for two paths instead of
one. By default (with this change) they will not be labeled. (See
attached screenshot)
The first dialog box is the NI Default directory. Anything shared
between multiple NI products will be installed there. In the future,
when other NI products are installed, they will default to whatever was
entered in this dialog.
The second dialog box is the location that TestStand components will be
installed to. This includes the TestStand engine, components, process
models, etc.
If you wanted to add labels to these path prompts, you would need to
modify the resource strings. This can be done in Visual Studio if you
have a copy. I believe Visual Studio Express Edition is now available for free on Microsoft's website.
Hope this helps Dave, have a good one and let me know if you have any questions.
Dan Weiland
Applications Engineer
National Instruments
www.ni.com/support
Dan Weiland

Deploy teststand with labview ui

Hi,
I'm using teststand now since 9 months and now I have to distribute my application to a testing machine. I have some questions about this process. But first I discribe my application:
I have a labview ui, which has 3 main tasks:
1.) Start selected teststand sequences for automatic testing.
2.) Give operator the possibility to manually control the testing environment (purely written in labview)
3.) Run continous data aquisition, which provides data for teststand and manual testing.
Sharing data between labview and teststand is done mainly via global variables (e.g. reference to tdms file). Because of 1.) and 2.) above teststand and labview share a lot of VIs for communicating with the testing environment.
OK, now my questions:
I'm searching for the best way to deploy this application via an installer. I know, that there is a teststand deployment tool (which I havn't used, yet) and I know how to build installers with the labview project manager.
1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?
2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
Thanks for any help in advance.
Marc
CLD

Hi,
I would recommend the Deployment Tool for your TestStand and OI. I would also keep your Test Sequence files seperate from your TestStand Engine amd UI deployment.
[1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?}
This is going to cause you a problem because LabVIEW doesn't like / will not load the same VI into memory from two different locations.
The Deployment Tool will probably object as well therefore you will not beable to create a deployment package.
The Deployment Tool will place all the VIs that are called directly from TestStand Sequence Files as seperate VI's (not in a LLB) into the target folder. It will then create a support LLB containing all the subVI's used by the directly called VI's. If you have VI's that are called directly from TestStand and are also used as subVI's you will again have problems because the same VI can be loaded from two different locations.
2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
No Teststand will not beable to find your VI's in the EXE. If you need to use the same VI's in both your OI and TestStand sequence file then create a DLL.
But I would recommend you keep the OI code seperate from your Test Code.
3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
Install your drivers first. The IO should be installed as part of the TestStand deployment as this will register the various components correctly.
Regards
Ray Farmer
Message Edited by Ray Farmer on 08-06-2008 01:02 PM
Regards
Ray Farmer

Getting Error Code:26282 when trying to deploy TestStand Application?

Getting Error Code:26282 TestStand - Deployment Utility Splash Screen.vi >> TestStand - Distribution Wizard GUI.vi >> TestStand - Build.vi >> TestStand - Create Installer.vi >> TestStand - Set NI Paths Entries.vi >> MSI DK Add Entry to NIPaths Requested.vi

My problem is that when I installed TS on this computer, The redistributable Engine Components part failed and I selectected to continue. I have uninstalled all of the NI software and deleted the c:\Program Files\National Instruments\ folder. Re-installed LAbview 7.0 and then re-installed Testand 3.0 in that order. The same error occurred "corrupt or damaged Cabs.w1.cab file" during part 4 of install. The error was #1335. I looked in the redist folder and 24 msm files had been installed at the time of the error. When the program continued it reported that error #2350 had occurred. Yesterday I tried to add the redist files from a Demo CD and got the same results.
Thanks
Steve

Deployment teststand error (labview test - sequence context)

Hello,
I need help by deploying my workspace to the deployment(target)computer. That is what I have done:
- i create a workspace, in this workspace are different sequence files and the vi´s which i have created.
- then i use the deployment tool (teststand) and deploy the workspace to a directory in the network.
- after that i copy the modified SequentialModel.seq to the target maschine.
- now if i want start the sequence file an error occured. Teststand can`t start my vi´s because it can`t find files like LabVIEW Test - Sequence Context, TestStand - Set Property Value (Boolean Array). Choosing the path of the file in the search directory doesn`t help.
Maybe i have made an error with the deployment tool?! How is the right way to deploy in a network without using an installer. Iám using teststand 3.0.
thankyou
Schwede

Hi Schwede
If you want to deploy your Sequence File and the Processmodell you have to copy first your original Processmodell from the NI folder to the user folder.
Than open the deploy-tool and load your workspacefile. Mark the point "deploy files in Teststand user directories" and define the image path. Don't mark the "create installer" field.
You will get and image folder with several subfolder.
In the target subfolder you can find your sequencefile. In the Teststand subfolder you can find your customized Processmodell or Operator Interfaces. Attention, please use relative paths when you create your workspacefile.
hope this helps
Manuel Wielander
National Instruments

Deploying TestStand app on TestStand-less target

I want to deploy a TestStand app on a target that doesn't have TestStand installed on it. I ran into this before on a different target, and the only way I could get around the ActiveX error messages I saw was to install TestStand on the target. Now we're going to send this deployment out, and I remembered my previous troubles. Will I again have to install TestStand at the target. If not, what specific files should I look for in my LabWindows/CVI and TestStand projects that will tell me that I have what I need.

As I understand it, TestStand "apps" require the TestStand engine at a
minimum. You can create a distribution kit from within TestStand
that just distributes the engine. The sequence files have a
separate installer. This is how I've done my test systems in the
past. You will need to provide a serial number and activate the
engine when you deploy it. Otherwise it will run in demo mode
only.
If you want to make it easy for the people installing your app, you
could build a distribution kit in TestStand that distributes the engine
along with your application. I don't think it's easy to do this
in CVI.
I am the founder of CnCSoftwareSolutions. When not cleaning up baby drool, I write about test data or work on Vision, a tool for understanding your test data. Visit me at www.cncsoftwaresolutions.com

Deploying teststand V3 - mdac98 error on target machine

Thank you in advance.
I have two PXI computer that I'll like to deploy sequence file to, from a development machine, I have successfully create the installer using tool>>deploy test stand system but I get error message "mdac98" required when I attempt to install it to win98 target machine. I have been to the windows website to download and install "mdac98.exe" but I still get the error.
I have read some literature on this issue but got no where. Out of curiosity what is the different between "disturbing test stand" and "deploying test stand". anyone?

Rash,
I just answered a question you posted on DCOM that was nearly identical. Are you also having problems with mdac or was this question supposed to be on DCOM?

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

TestStand Deployment Query

Hi,
I have TestStand 3.0 development licence and once my development is finished i need to deploy my software to client machine. Do i need to purchase TestStand Base Deployment Utility,TestStand Debug Deployment Utility or can i can deploy by suing the option present in Tools->Deploy TestStand System.
If i need to buy Base or Debug Deployment utility then what is the purpose of this option Tools->Deploy TestStand System ??
Thanks in advance,
-Anil
Anil-B'lore

Hi Anil,
The Deploy TestStand System is very good at organizing every code module and component that you need for a deployed system. It will find all of your VIs (if you use LabVIEW), and all of your other code modules. It will create a single installer that will include the TestStand Engine. However, you will still need to a license to run TestStand on the deployment machine. So you will use both the Tools >> Deploy TestStand System along with purchasing a deployment license for using TestStand on another machine.
Allen P.
NI

Deploying TestStand

Similar Messages

Maybe you are looking for