Deployment Utility and Labview Modules

Hi,
I am fairly new to TestStand. I have created a TestStand Sequence that calls a number of Labivew modules. Everything works fine on my development machine.
I am trying to deploy this to another machine running a base development license. I ran the development utility and created a setup.exe which I have just installed on the 2nd machine.
When I go to run my test sequence on the 2nd machine it cannot locate the labview modules called in the test sequence.
So my questions are:
Can TestStand deploy these files for me, or should I do it manually?
If it can, is there a specific folder I should store all labview moduels on my development machine so the deployment utility picks them up?
Is there any option in the Deployment Utility that I need to set for TestSTand to pick up these modules?
Is there any special option I should set in the sequence file? Search area???
Thanks & Regards,
Don1.
Solved!
Go to Solution.

Hi,
You should be able to see the LabVIEW VI's in your deployment tool. If you can't then that is why you can't see them on the target system.
Are you using a TestStand WorkSpace/Project files?
Regards
Ray Farmer
Message Edited by Ray Farmer on 02-11-2009 06:30 AM
Regards
Ray Farmer
Attachments:
deployment.JPG ‏70 KB

Similar Messages

Deployment Utility can't find files

One of the standard search directories is “Current workspace directory”.
I’ve discovered that the Deployment Utility may or may not look there (regardless of whether it is checked), and it may or may not look in its subdirectories (regardless of whether “Search Subdirectories” is checked.
It works OK on some of our computers, but not on others.
In order to insure that the build always finds the files, I have to explicitly include in the search directories the folder that contains the .tsw file.
Is there a way to force the Deployment Utility to really look in the “Current workspace directory”?

The deployment utility will create a list of top-level files to deploy from a workspace, a directory or both. The distribution sources (workspace and directory) will only point to the root element which we will use to create the tree of files to include, these files will be specified with an absolute path to the file and we will not use the search directories to find them.
During the analysis phase the deployment utility will find all the required top-level files for the deployment. If you selected to deploy files from a workspace, the deployment utility will iterate over every worskpace object in the workspace and call GetAbsolutePath to get its path. If the problem you are seeing is with top-level files, then I would recommend calling into this method to verify that the files are found in the correct location.
Once we get all the absolute paths for the workspace objects we search those files, depending on their type. At this point things start getting a bit more complicated because of the large number of file types. If your workspace contains a sequence (we will find the path of the sequence by calling GetAbsolutePath on the workspace object, see the previous step), then we will analyze the sequence and for every step we will call the public API of its adapter to get the path; for example, for the LabVIEW adapter we will use VIPath and ProjectPath (in general, there are some special cases where we call other methods) to figure out which VI to deploy. If the problem is with one of your code modules I would recommend calling into the public path methods in the adapter that is calling into your code and making sure that the files are found in the correct location.
Without more information about your problem it is hard to give you a good answer, because the deployment utility (and test systems in general) are complicated pieces of code that deal with a great deal of complexity. Some of the things that might help us give you a more specific answer to your problem are:
What version of TestStand are you using?
What kind of deployment are you creating (VIs, DLLs, .Net assemblies? Creating Packed Libraries? Sending to multiple destinations?)?
Can you simplify the test case so that we can reproduce with relatively few files? Could you provide a sample that shows the error?
Are there any differences that you can think of between the computers where the deployment works and the computers where it doesn't?
When is the error happening? What is happening exactly? For example: Are you getting an error in TSDU that says that files couldn't be found? Are you building the deployment and the files don't show up in the image directory?
I hope this helps.
- Francisco

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

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.

Internal and external distribution models utilizing the SD Module and tcode

gurus,
Did anyone have an experience with internal and external distribution models utilizing the SD Module and transactions.
Please explain the model with tcodes.
Thanks in advance
Regards,
Andy

Can you pen down your requirement !

Mismatched versions of Labview and PDA Module

Last spring we received the update of labview 8.2 to 8.2.1 and we bought labview PDA 8.2.1. We installed the whole this week. When I try to run\build the VI, the error "Mismatched versions of Labview and PDA Module" appears.
I looked on the forum and found a similar case but it updated Labview and LV PDA. I never had LV PDA 8.2. I try to install LV PDA 8.2.1 with LV 8.2 but it is impossible because it is not the same version.
Do you have an idea of the cause of the problem?
Thanks you!

You will have to install LV 8.2 first then update it to 8.2.1.
Reboot your PC.
Install the LV 8.2.1 PDA toolkit (know that the toolkit also requires some other programs, mainly MS ones).
This should work.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

LabVIEW Control Design and Simulation Module version 2013

I have had Labview downloaded for quite some time now. Downloaded control design and simulation module. Installed it. When i go to use it in the
functions menu, only the window appears. Opening it shows an empty window. I have attached a screenshot of the issue. Could someone please explain to me what the problem is and how I can go about fixing it?
Attachments:
Labview screenshot.docx ‏998 KB

As Altenback said, It is very possible it expired or it needs activation. To see for sure, go to your "NI License Manager" and expand the Modules. you should see:
If not green then you have to fix the license.
Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

Could I use two regular computer to achieve realtime communication using the Ethercat and Labview Real Time Module?

Could I use two regular computers (one acts master , another one acts as slave using the Ethercat Internet Card) to achieve realtime communication using the Ethercat and Labview Real Time Module? if it could, what hardware should I purchase from the NI ?
Thank you!

Hi Xiaolin,
NI doesn't offer Windows based Ethercat master or slave software. Only LabVIEW RT can run the Ethercat driver.
However, you could use a LabVIEW RT target as an Ethercat master and use the Ethercat Internet Card with a slave PC (note: I think this will work from the Beckhoff description of the card you are describing. The card should integrate like any other non-NI slave. However I haven't tested the setup and don't advise saying it will work until you have tried).
You can use any NI RT target with two ethernet ports as the Ethercat master. This could be a cRIO, PXI or RT Desktop.
Jesse Dennis
Design Engineer
Erdos Miller

Differences between LabVIEW Education Edition and LabVIEW 2009 + NXT Module

Recently saw the announcement regarding LabVIEW Education Edition.
From the information available at this time it's hard to tell the difference between this product and just adding the NXT module to standard LabVIEW 2009 if your only interest in LabVIEW is for NXT programming. Anymore details about this new product would be appreciated as well as info on how it's different from the alternative. Are there some unique VIs not present in the standard NXT module? Obviously the pricing is very different, but for a student the academic version of LabVIEW is actually lower cost than this new Education Edition.

Inh-
LabVIEW Education Edition (LVEE) includes the NXT Module and the API to interface with Vernier products. LVEE is geared towards middle school and high school classrooms to get students interested in math and science. It includes curriculum for teachers that may not be familiar with programming and LabVIEW in general to use the NXT bricks and the LabVIEW environment.
LabVIEW with the NXT module only has the NXT API and not the Vernier API. It will not include the course work and as extensive example programming useful for teaching.
For additional information on LVEE, please take a look at the Getting Started with LabVIEW Education Edition or go to ni.com and search for “labview education edition”.
Regards,
Mike S
NI AE

LabVIEW module use DLL

In a teststand sequence file, it uses LabVIEW modules that call .NET DLL. The DLL cannot be linked to the program. If I were using LabVIEW only, I know that I can insert the DLL into a LabVIEW project and the VI in the project will know where the DLL are. However, I am not sure about teststand. Can someone help? Thanks!
Kudos and Accepted as Solution are welcome!

Are you asking because you want to deploy the system? If yes, you should create a workspace and add the .NET DLL to your project as additional file. You can use the Deployment Utility to include the DLL in a MSI (Microsoft Installer).
If you are NOT asking in the context of a deployment, please elaborate your question....
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

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

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

NI-Fieldpoint support in Windows 7 and LabView 8.6

We have a "classic" FieldPoint system with an ethernet controller. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Window 7. Is NI-FieldPoint supported in LabView 8.6 and Windows 7?
Regards,
nate
Solved!
Go to Solution.

Hi natewkidd,
I feel like there is some confusion between the operating systems running on a development machine (like Windows 7) and the real-time operating systems that run on our real-time controllers (like the FP-2000). I will do my best to clear up this confusion by first answering your questions.
1) What is the difference between LabView Real-Time 2009 and LabView 2009?
LabVIEW Real-Time 2009 is actually a software package officially known as the LabVIEW 2009 Real-Time Module that is installed after the LabVIEW 2009 development software to allow the user to develop and deploy real-time applications to real-time targets such as your FP-2000. You can think of the LabVIEW 2009 Real-Time Module almost as a plug-in for LabVIEW 2009 to allow for real-time application development and deployment.
2) If I have a FP-2000 on the ethernet network and want to use a computer running Windows 7 and LabView 2009 to record and display data, will I still be able to communicate with the FieldPoint network using the FieldPoint Read/Write VIs from my Windows 7 machine?
If you were just going to use the FP-2000 as a network module (NOT deploying a real-time application to run on the FP-2000 itself), you should be able to communicate with it using just the FieldPoint Read/Write VIs from your Windows 7 machine with LabVIEW 2009 and the NI-FieldPoint 6.0.5 driver. In this situation, you actually do not need the Real-Time Module since you are not deploying the application to the real-time target.
Regarding the FP-2000 not being supported beyond LabVIEW 8.5.1, this is because the memory on the controller is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Real-Time Module and the LabVIEW 2009 Real-Time Module. For more information on this please check out this KnowledgeBase article.
I hope this is helpful! Let me know if you have any further questions.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

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

Erreur -19050 lors de la compilation avec Deployment Utility/TestStand

Bonjour à tous,
Je souhaite créer un exécutable incluant des séquences TestStand avec des VIs Labview. Je suis tombé sur l'outil Deployment Utility qui a l'air de correspondre à ce que je souhaite faire.
J'ai donc essayer de construire un installateur avec cet outils qui inclut mes séquences et mes Vis etc..
Le problème arrive lors de la construction, une erreur apparait mais ne me donne pas plus de détails que ceci:
"error -19050: The bitness of LabVIEW does not match the bitness of the deployment utility."
J'ai essayé de chercher d'où vient le problème mais je suis au point mort la, je ne sais pas du tout où je dois regarder pour régler ce problème.
J'utilise les versions 2014 de LabVIEW et TestStand. Mes séquences fonctionnent correctement.
Merci de votre aide
Mehdi

Bonjour,
Je pense que tu risques d'avoir queslques difficultés pour exécuter ton application de test en distribution. Pour la distribution, il te faut effectivement au moins une licence Run-Time de TestStand et je pense que tu veux te passer de la licence LabVIEW.
Si j'ai bien compris, tu veux une distribution avec un installer de ton application TestStand. Tu as des séquences en TS2014 64 bits et tes codes modules LabVIEW sont en LabVIEW 32 bits pour le développement. J'imagine que ton adapter LabVIEW est configuré pour fonctionner avec LabVIEW en développement.
Première étape, as tu essayé de passer ton adapter LabVIEW en run-time ? A mon avis,ca ne va pas fonctionner d'parès cette KB .
Il faudrait que tes modules LabVIEW soient en LabVIEW 64 bits.
Le Run-Time TestStand n'est pas l'éditeur de Séquence. TestStand est un serveur ActiveX, et si tu as créé une interface opérateur spécifique, tu n'as pas besoin d'avoir l'éditrru de séquence pour exécuter ton application. SI tu veux les éditer ou l'exécuter depuis la même interface que celle que tu as en développement, il faut installer au moins le séquence Editor qui est disponible dans les "Optional TestStand Features..." lorsque tu coches Install testStand Run-Time. Pour l'acitvation de la licence, au pire, lors du premier lancement de ton application, il proposera de l'activer. Pense a ajouter le run-Time LabVIEW dans ton installeur si tu veux que ca installe tout d'un seul coup.
Mais je pense qu'avant de réussir tout ca, il faudrait vraiment vérifier l'exécution en Run-Time LabVIEW au niveau de l'adapter.
Petite question de curiosité, pourquoi tu chsoisis d'utiliser TestStand 64 bits ?
Cordialement

Deployment Utility and Labview Modules

Similar Messages

Maybe you are looking for