Deployment of TestStand 5-7 hours?

Similar Questions

• Deployment of TestStand asking Veristand

  Hello

  I'm trying to deploy a Teststand system. Usually, I try to install with all the necessary drivers test computers before hand, but this time I need to create a full installation package.

  The components that I need to install are:

  TestStand TERM 2014

  Runtime LabVIEW 2015 (32 bit)

  DAQmx run-time engine

  VISA run-time engine

  When I select the addiational components a few ones are selected as well.

  Some modules of LabWindows/CVI runtime (Teststand seems to need them)

  Performance of PXI Platform Services (DAQmx seems to need)

  NEITHER engine VAriable 2015 (Teststand seems to need)

  A couple of them seems a little weird but of course, no problem.

  I plugged my USB with the software bundle 2015 he asks.

  But now he also asks me for multimedia path NI Veristand 2015. It is not included on my USB drive apparently have, but even if that were the case, why a deployment using standard drivers and LabView Teststand should Veristand installation media?

  TestStand deployment is a little tricky with even with the new versions, but that's all just ridiculous.

  Someone at - it had the same problem and if so, how do solve you?

  Best regards

  Nimgaard

  Hi Nimgaard,

  It is possible that on your development system, one of the required common components was originally installed in the media Veristand.  for this reason, the framework of the installation program will ask you the mdeia where the product has been installed from.  Part of the Setup program does include that which is indicated on the installation in TestStand Deployment Utility dialog box, i.e. the products you select and all dependencies of these products.  If you do not have media veristand, you can download it from the Web site of OR here:

  http://www.NI.com/download/NI-VeriStand-2015/5542/en/

• The deployment of TestStand-19049 utility error

  I'm running an error when you try to create a new deployment of TestStand (process model, UI, etc.).  Specifically, I want to install the user interface and to transform the model in an absolute path, and that's where I'm running into the issue.  When I install to program files, the work of deployment without problem, however, I have run into issues trying to find files in things like property charger and other.

  To reproduce the problem:

  On the Installation Options tab, ' default Installation Base Directory: ' the absolute path value.  And the default installation directory is basically what whether (I tried my desired just C:\ directory and all the rest, but does not seem to make a difference)

  During construction, the status tab to build indicates the number of error-19049 with the message 'Destination not taken in charge under the current number of bits' and the message ' Base Directory default Installation: using the destination following WOW64 Directory System.

  I use TestStand 2014 32 bit with Labview 2015 32 bit on a 64-bit OS to Windows 7.  I can't change the number of bits of the TS or LV due to the dll I'm referencing that cannot be changed.

  Can anyone help?

  Seth_K salvation,

  It is a known bug that has been fixed in SP1 of TestStand from 2014; See ID 529404 number in the list of correction of a Bug in SP1 2014:

  http://www.NI.com/product-documentation/52845/en/

  The only known outside the upgrade to SP1 2014 TestStand solution is to use a relative destination instead of the absolute. If the upgrade to SP1 2014 TestStand isn't an option, let me know and we can look into other options.

• How to include LabView Instr.llb in a deployment of TestStand?

  I want to deploy my sequenze of testbed. When I install the deployment and you want to let it run it shows that it can t find all the sub whitch screws I used directly from LabView. For example: .vi VISA set up a Serial Port (Instr) or by check if file or folder Exists.vi. How to include this VI s to the installer?

  He s solved. This screw is located in the folder: Support screw whitch is createt automatically by the installation.  Thank you

• I can deploy from a folder AND a workspace in TestStand

  Hello

  Back in the old days of TestStand 2010 sp1, I was able to deploy the TestStand Public and a workspace.  After reviewing the files, you can find as well in the distributed file and configure the destination of all, file-by-file.

  In 2014 TestStand, I can't understand how to do this same thing.  Whenever I includes a directory or a TestStand audience in addition to the workspace, the workspace files do not appear in the distributed files.  (They appear in the workspace view, but I can not configure the destination from there... it is grayed out).  Further regarding me, when I have only a selected workspace, I see these files in the file distriibuted display after reviewing.

  Everyone knows this?  Is my only option now to include all the workspace?

  Hi GarryG,

  At the end of the analysis, check if there are errors present in the status tab to build. In some cases, an error can prevent analysis ended.  We intend to improve this behavior in a future version of TestStand to stop the scan only critical errors and ensure that we clearly indicate the user of any errors that occur.

  If there are errors in your case, please record the logs and tie them so we can take a look.  Meanwhile, resolve all errors will probably prevent the issue you see.

• deployment issues

  Hi all

  I'm new to Teststand and tried to deploy my Teststand applicatino on computer target for the last 2 days and have some questions about the deployment process.

  1. I developed my TestStand application on the D drive on my development computer. My computer has only the C drive. In this case, (note: TestExec.ini is also being rolled out) I would still need to:

  (a) change target the path search on the computer configuration after deployment, for example, adding/changing of all relevant paths in the configuration of the research to start with drive c. or

  (b) I can also do a few tricks, by setting configuration C: research in computer development, just for the sake of deployment. In this way, the deployment on the target computer will be the right search path (and the files output because directory report I specify a directory output fix reports). Then I have to change the configuration of the search on drive D for the continuation of the focus on the computer of deveopment.

  The question is: if I choose one) as deployment strategy, in order to add/change the configuration of the computer search target, I need a teststand development license. If I download a teststand development (evaluation) on the target computer, after the add/change the configuration of the search on the target computer, I disable the Teststand development and move the license to the license of deployment on the computer base target, this will do, right?

  2. shared variable deployment published network is not so straightforward. My target computer will communicate with a compactRIO with shared variables. The compactRIO controller is AES. I added a "deploy Labview Utility LIbrary step" in a sequence step and deploy this sequence on the target computer. I ran this sequence in order to deploy the variable shared on the target computer. However, I got an error saying that the shared variable library can not be deployed and to ensure that it has only shared variables in the library. I checked and you can see that there are only shared in the lilbrary variables. What could be the possible reasons? Can someone give me advice on this problem? Y at - it a tool that can scan the library and tell me if there is a 'hidden' in this library vi because I see nothing wrong with the library even with my big glasses.

  I think other shared, for example variable deployment options: a) maybe I need to download a system assessment deveopment LabView on the target and the copy on the Labview project and deploy the variable shared across the labview project. or (b) I can create a vi that uses the variable shared and using labview generation process for deploying the vi as exe. Check the option "deploy the shared variable" appropriate in the build process, run the exe on the target computer. This way I can deploy the shared variable. After deployment, disable the deveopment LabView evaluation license so there is only LVRTE on the target computer.

  (Not the one above) and b) sensible options such as shared variable deployment strategies?

  At this point, I realize that the TestStand deployment is a skill. There is no systematic deployment for TestStand approach. The experts out there agree? I just need a few entries so that I'm not on the wrong track. Thanks in advance for your comments.

  Yours,

  chati

  Hello chati,.

  version of the software you use?

  There is a known issue with the variables related to a shared library in old versions of LabVIEW.

• The call of the TestStand of LabView modules

  Hello

  I have some dllmodules developed to be launched from TestStand and so the methods require a context of sequence as in param.

  But now I would call these modules on a computer without TestStand. I thought the call of LabView but is it possible? I do not have access to change the modules.

  You can use the TestStand Deployment Utility, located in the TestStand menu under Tools-> deploy the TestStand system

  In the TSDU, you can create an installer to deploy a workspace TestStand and tab of Setup options, you can even choose to include the TestStand engine in the installation program.

• labview deployment project has conflicts

  I'm having a problem with a deployment of teststand (2013 Teststand, LabVIEW 2013)

  I have a deployment that deploys my project LabVIEW that contains all of the drivers (classes and lvlibs) for use in my sequences.

  During deployment (LabVIEW options), I uncheck "exclude vi.lib", "exclude user.lib" and "exclude instr.lib" because the deployment should also work on a PC that has only some runtimes and an operator interface.

  The build is complete without errors, but I can't open the deployed project...

  --> not on a development PC because it detects conflicts (XNodeSupport and some in vi.lib picture.llb of the vi)

  --> not on lifetime PC (file not found)

  Else you have noticed the same behavior?

  He works with LabVIEW and TestStand 2010.

  Thanks in advance for your help, advice and tips :-)

  (Cross post, also on Lavag.org: here )

  NEITHER of the spirit together, we have identified the problem.

  The GDS (suite Goop development) causes conflicts.

  The problem is identified, the solution is underway.

  See you soon,.

  Wim

• Why Search beginning of Labview VI?

  Hello

  Given that I deleted a «...» VI \Support directory", originally created during deployment of Teststand, whenever I start

  LabVIEW 8.6 as a search for several VI is executed.

  These VI is NOT planned and was initially located in the Support directory above.

  My questions are:

  1 why Labview seeks these VI at startup, even if no VI is loaded in the editor?

  2. why the search path is not updated according to the original source directory has been deleted?

  (why not use the new location for subsequent Labview start up?)

  Thank you

  Gary.

  Propably is one of the cases, where a massive compilation might help.

  I guess some vi is loaded at startup of LV that are still linked to this directory. As fix you, they are not saved, so that you get them correct every time. If you know who has vi who might be, you can also find them in LV directory and manually open them and save the changes.

  Felix

• Error loading DLL Vista

  Hello

  I'm deploying a TestStand system developed on XP to a target system using Vista.  Part of the package uses LabVIEW screws that call functions in a dll created in Visual Studio 2005.  Everything works on the development system and a system of deployment under XP.  When I run on the Vista machine, the VI will not load in TestStand.  If I try to load the VI in the LabVIEW on the Vista system, I see the error in the attached JPG.

  Any suggestions?

  Thank you

  Mike

  

  It can be associated .NET, but I guess that the code was done in Visual C++? You try to deploy a debug version of the Assembly? If so, the debugging DLLs will not be on the Vista machine. You must deploy the version of the DLL.  Alternatively, you can try to install the Visual C++ (downloadable from Microsoft) runtime on the Vista machine.

• TestStand Debug Deployment License Question

  I'm a little confused by the licensing OR and need advice...

  I have a PC that I use with a contract manufacturer that is set up to run LABView and Teststand
  applications.

  It was working fine until recently, I've updated this PC and receive the following backup TestStand license
  screen every time I run the TestStand on this PC application:

  

  When I try to activate this product online, I get the following screen:

  

  On this PC I have not loaded development system but I buy and had installed on this PC, a copy

  of the TestStand Base Deployment Engine. I don't know what is the debug deployment environment or how

  He got on this PC.

  If these are the same package, where can I find the serial number for the TestStand Base Deployment Engine on my

  2013 developer Suite CD?

  If these are not the same, How can I remove this backup reminder now so I can make sure I can run again TestStand

  applications on this PC (that I need to send it back to a remote site before 5 days)?

  Thank you

  Just delete the license files according to the link I mentioned earlier.  Then you should be able to activate correctly again.

• Why my TestStand deployment installation appear under my Windows will not start menu of my target machine?

  Why my TestStand deployment installation appear under my Windows will not start menu of my target machine?

  I managed to install the deployments of work to the target machines. However, I expected to see the classified facility "My TestStand system" in my Start menu, but it is not. Am I misunderstanding something here?

  Also, if I do another target second deployment to the station as "My TestStand system B", all LabVIEW files in my previous installation for "My system TestStand" disappear from the directory (c:\Program Files\My TestStand system) target.

  I use TestStand Professional 4.2.1 on Windows XP and LabVIEW 2009 development station.

  Thank you Paul,.

  That solved my second problem and inspired me to look deeper for the response to my first problem. The answer lies in the tab 'distributed file","Installer properties' box 'create a program item:

  

  Wouldn't be nice if it is automatically checked by default for main sequence files? Wouldn't also nice if "Upgrade Code" was regenerated automatically by default whenever we have saved the file *.tsd under another name?

  Thanks again,

  Eugene

• Report TestStand deployment

  In the report of TestStand how can I make sure that the report options are not changed after deployment. In addition, the deployment from one station to the other, will I be able to transfer the report such as filepath macros with parameters.

  If you have added a custom report and you want not deleted, I would add it in the ModelPlugins\Addons folder instead of just ModelPlugins.  Any sequence of plugin file that is located in this folder is automatically executed.

  Another option is CRC file TSConfiguration\ModelPlugins\ResultProcessing.cfg to check changes of the elements changing (or even your movie file extension).

• TestStand-19000 deployment error

  Hello

  I am trying to build my app TestStand deployment but I get an error:

  -19000-the library created in the source distribution is not valid. Contact National Instruments support. The file created is:

  It does NOT specify the file after the ': '.

  I've tried several fixes by browsing the log generated by the deployment engine, but now he gives me all the relevant information.

  If you want to check, the log is attached (this is an .xml file).

  Any help is really appreciated.

  Thank you!

  
  

• TestStand deployment error - error: unable to locate all the screws saved subVIs because it lacks a Subvi

  Hello

  I am a systems and software engineer based in Vancouver. I developed a test system automated using 2013 LabVIEW and TestStand 2013 with custom operator interface.
  I encountered problem 'lack screw' which is kind of weird because I went to analyze the sequence for the TestStand Deployment Utility and TestStand sequence editor > files broadcast tab.
  But when I tried to build the installer and reach the point ' called distribution screw, it always throws an error saying "an error occurred trying to read the error of the screw, possible because the screws are not saved in the latest version of LabVIEW. Do you want to save any changes now? ". I tried both (that is to say Yes and no) for this option, but it has not solved the problem.

  This is part of the original error message displayed in the TestStand deployment utility:
  " ***************************
  Then the treatment live...
  Error: Cannot locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.
  The chain of calls to missing screws:
  1 - ATE_AccelerometerTest.vi
  2 - CreateAndMergeErrors.vi (missing)
  3 - LogControl_CheckForErrorSendUpdates.vi (missing)"

  All screw missing come from userlib.

  Actions performed:
  -File of sequence analyzed by using the TestStand Deployment Utility and TestStand sequence editor
  -Checked "search directories" include all the necessary files/dependencies.
  -Mass to compile the directory of the missing screws
  -Added all the necessary files and folders in the workspace file.

  The result is always the same function according to the actions performed.

  Debugging last I did earlier, is that I tried to find the sequence and steps missing screws as shown above (for example ATE_AccelerometerTest.vi)
  and I discovered that the measure appears to be an empty action step. This would be possible even if it has already passed the analysis?

  Other considerations include:

  I'm using sp1 2013 LabVIEW and TestStand 2013. We tried the building three 3 computers and we only managed once to a freshly installed comptuer.

  Hoping to hear from you soon.

  Kind regards

  Michael Panganiban
  Engineering systems and software
  www.Synovus.ca
  [email protected]

  Hi all

  We were able to solve the problem. First of all to note is that the release notes in 2013 TestStand is obsolete and we confirmed engineer OR Austin TestStand 2013 works very well with LabVIEW 2013 SP1.

  Second, we played option deployment TestStand that solved the problem. Attached are the pictures.

  We have activated just the 'delete unused Components VI'. It could be one of the libraries (lvlib) we have included in the compilation, but we've not thought of it again because we have checked that all the screws are working. It could also be something else that I think is very hard to find from information. However, if someone had the same problem, this could be useful.

  Again, we return to using 2013 TestStand and LabVIEW 2013 SP1.

  I appreciate all comments and feedbacks. Otherwise, you can close this request for assistance.

  Thank you.

  Kind regards

  Michael Panganiban

  Engineering systems and software