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

Similar Messages

  • 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

  • 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

  • Best way to distribute LabVIEW Instruments Drivers.

    Hello,
    I'm trying to stick to the standards described just there:
    Developing LabVIEW Plug and Play Instrument Drivers
    Instrument Driver Development Tools and Resources
    Instrument Driver Guidelines
    However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
    Here is a couple of questions I'm not really sure about their answers:
    Is it okay to use a .NET dll and to make some calls?
    Is it fine to hide the Block Diagram? With passwords in the Drivers
    Can we put prevent the modification
    In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
    May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
    What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
    How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
    Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
    Solved!
    Go to Solution.

    Ehouarn wrote:
    Hello,
    I'm trying to stick to the standards described just there:
    Developing LabVIEW Plug and Play Instrument Drivers
    Instrument Driver Development Tools and Resources
    Instrument Driver Guidelines
    However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
    Here is a couple of questions I'm not really sure about their answers:
    Is it okay to use a .NET dll and to make some calls?
    Is it fine to hide the Block Diagram? With passwords in the Drivers
    Can we put prevent the modification
    In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
    May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
    What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
    How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
    Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
    Not sure about 1) but 2) and 3) are definitely a no go if you want your library to be distributable through the ID network. The standard only allows for DLLs in that  are really developed in C but would require you to also distribute the C code as far as I understand.
    OOP may not be a problem.
    Packed Library is definitely not something you want to do. They only work in the LabVIEW version in which they were created. You will hate the moment you decided to go with packed libraries as requests come in for other LabVIEW versions and your drivers are bashed on all discussion forums as being a pain in the ass to use.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • 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

  • 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.

  • Need help in converting old LabVIEW instrument drivers to new version.

    Hello,
    I just rented a Tektronix DG2020A data generator. I did not find any instrument drivers for the DG2020A on the Instrument Driver Network, although there are drivers for DG2040 that could be used to some extent. With the instrument, I also received a floppy with example programs. This does include LabVIEW drivers for the DG2020A. However, when I tried to load the VIs, I received an error message that the VI version 3.1 is too old to be converted to 7.1. Can someone at NI help with the conversion? It would be very useful.
    Thanks.

    There is a driver available for the DG2020 on NI's site. Models supported are the DG2020, DG2030, and DG2040. Available in both 7.x and 8.x.

  • I am looking for LabVIEW instrument drivers for Audioprecision test equipment. It looks like you do not support any Audioprecision intruments?

    I also do not see any support for Keithley 2420 Sourcemeters.

    Hi Kristen,
    If you search www.Keithley.com you will find an instrument driver for the 2420 device. Go to the "downloads" section and search for 2400.
    I am not sure what you mean by Audioprecision instruments. If you had a specific driver in mind, I would check with the instrument manufacturer. Often times they develop and support the drivers since they know the instruments far better.
    If you do not see the driver on their website, please submit a request at http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer.
    We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driv
    er (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at:
    http://www.ni.com/devzone/idnet/development.htm
    Hope this helps out!
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • 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

  • What labview package do I need to develop third party labview instrument drivers?

    We have been asked develop labview 6.1 drivers for a third party data acquisition card. What Labview package do we need to buy, basic, pro etc?

    The only way to really program for a third party data acquisition card in LabVIEW would be through a "call library function node". You would have to call the dll that third party card developer provided. As far as I know all LabVIEW packages contain a "call library function node". I would recomend buying at least the full development environment because of some of the additional features in that package.

  • "I am looking for LabVIEW instrument drivers for a PTS 160 Frequency Synthesizer

    looking for instrument driver for PTS 160 Frequency Synthesizer

    "Unfortunately I was unable to find a driver for this instrument at http://ni.com/idnet. This leaves you with one of a couple options. It may be possible to modify an existing driver to work with this instrument. Otherwise, http://www.ni.com/devzone/idnet/other. htm states a few options to obtaining a driver. NI only writes drivers for standalone instruments in the eight IVI classes(DMMs, Scopes, Function Generators, Switches, Power Supplies, Power Meters, RF Signal Generators, and Spectral analyzers) that communicate via GPIB, Serial, or TCP/IP, so a driver cannot be written for your instrument. It would also be beneficial to notify the instrument manufacturer, they often have drivers for multiple programming languages. If they do not, you may want to hire an
    Alliance Member to write an driver for you.
    Alliance Member Directory
    http://www.ni.com/alliance/ alliance_member.htm"

  • Deploy TS system without uninstall

    How do I set "Deploy TS system" to just update a previous installation done with Deploy utility? Is it just to call it a different name under "Installer options/Advanced options/Keywords, Version, Subject or product code"? I have looked in the manual and cant find information about these fields.
    Many thanks

    Hello Dan!
    I believe the information you are requesting can be found in the TestStand help and in particular you should look at the following text:
    Quote:
    "Advanced Installer Options Dialog Box
    To launch the Advanced Installer Options dialog box, launch the Deploy TestStand System dialog box and click Advanced Options on the Installer Options tab.
    The Advanced Installer Options dialog box contains the following options:
    Manufacturer—Specifies the name of the company, which appears in the Currently Installed Programs list of the Add or Remove Programs dialog box in Windows. This option corresponds to the [Manufacturer] Microsoft Installer (MSI) property.
    Version—Specifies the current software version number. The installer uses this number to check for a current installation and to check for upgrades. You must increment the version number to create versions of the installer that are capable of overwriting previous installers. The version corresponds to the [ProductVersion] Microsoft Installer (MSI) property.  Note  This control is disabled if the Auto Increment option is enabled.
    Auto Increment—Specifies that the version is automatically increased when an installer is built. When you select this option, the Version control is disabled.  Note  You must save your deployment before closing the Deploy TestStand System dialog box to retain the new version number. 
    Upgrade Code—Displays a string that uniquely identifies a related set of installers in Windows. Only one system, with a specific upgrade code, can be installed on a computer at a given time. An installer that has the same upgrade code and a higher version updates an older installation. The upgrade code corresponds to the [UpgradeCode] Microsoft Installer (MSI) property."
    So the last one is the method I believe you should use!
    Regards,
    Jimmie A.
    Applications Engineer, National Instruments 
    Regards,
    Jimmie Adolph
    Systems Engineer Manager, National Instruments Northern Region
    Bring Me The Horizon - Sempiternal

  • Est ce qu'on peut utilisé les NI visa et instruments drivers dans un seul diagramme labview

    Bonjour,
    Est ce qu'on peut utilisé les NI visa et instruments drivers dans un seul diagramme labview c'est à dire pour communiquer avec un instrument de mesure il est ce que il faut la communication avec lui o utilisant visa ouvrier et/ou le VIs qui fait la reste de tel instrument

    Hi ghabri,
    I am not entirely certain that I understand your question as a whole, but I will do my best to answer your question in French.
    Oui tu peut utiliser les fonctions de NI-VISA et les instrument driver VIs dans un seul diagramme LabVIEW. Les instrument drivers sont seulement les subVIs qui contiennent les fonctions de NI-VISA. Les instrument drivers utilisent les fonctions de VISA dans leur VIs pour programmer quelques fonctions qui sont specifique pour cet instrument. Donc, tu peux utiliser les fonctions NI-VISA tant que tu n'utilise pas ces fonctions dans une maniere qui va faire un conflit avec les instrument driver subVIs.   
    I hope that this answers your question. I would recommend posting this in the French discussion forums for better support in French:
    http://forums.ni.com/t5/Discussions-de-produit-de-NI/bd-p/4170
    Regards,
    James D.
    Applications Engineer
    National Instruments

  • Why does visa write hang with Labview 2009 instrument drivers.

    I'm having an issue with a code package that I'm running. The pacakge is very complex and was written by someone other than me. It runs fine while using the labview 8.5 drivers, however, when the 2009 instrument drivers are install there is a visa write call to an instrument where the software will hang up at the VISA write VI. I tried setting the timeout attribute but that makes no difference. I would expect that if the visa write did not work, that it would time out with an error instead of hanging up.
    Some additional information. The instrument is an EPM which is on a GPIB bus with other instruments. When I place the EPM2000 on a serparate bus this problem goes away, but I want to be able to operate on the same GPIB bus.
    Has anyone experienced a similar problem? What can I try to help troubleshoot the problem. I tried opening NI Spy but that shows no activity going on.

    Hi Steve,
    My apologies, when you said instrument drivers I assumed you were refering to the individual drivers for your instrument.  Were you refering to the VISA drivers?  If so, the latest version of these is 5.1.1 which can be downloaded here: http://joule.ni.com/nidu/cds/view/p/id/2659/lang/en.
    Also are you able to communicate with this device using the test panels in Measurement & Automation Explorer?  There is also a tool called NI IO Trace (or it may still be called NI-SPY in 2009) that can be opened from MAX that monitors all GPIB commands sent and received on the machine.  Getting a log of the commands when the hang occurs may help to diagnose it.
    It is possible this issue could be caused by opening and closing the VISA reference frequently in the code such as in a loop iteration.  Is this is case in your code?
    Justin D
    Applications Engineer
    National Instruments
    http://www.ni.com/support/

  • 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)

Maybe you are looking for