LabVIEW Subvi executable

Similar Questions

• LabVIEW 2009 executable will not manually load screws

  Before LabVIEW 2009 I was able to create an executable file containing a main VI which was empty. When this executable has been launched, I could open the other screws on the system through file-> open from the empty main VI. I used this to check distributions of llb for missing/bad behavior screws on systems with just running LabVIEW. Now in LV2009 when I load a VI through this method... nothing. No charge. No error. NOTHING.

  'Function' or a bug?

  I have not tried to reproduce this, but a valid solution would be to add a couple of features to the stub executable to do the following?

  • Dialog box file to find a VI
  • Reference open VI
  • FP. Open method

• LabVIEW 2010 executable runs under windows xp, but not in windows 7

  Hi all.  Here's the situation.  We have Labview 2010 professional development on a computer running Windows XP.  I designed all my programs with this PC.  We have another PC which has Windows 7 with no Labview.  I'm trying to make the executable files and put them on the Windows 7 PC.  I have been here three executable files and move the Windows 7 PC.  One of the executables work correctly, the other two interrupt immediately.

  Executables that stop have temperature limits and the program is apparently seen a low temperature and so stop the program.  Yet, these same executables work fine on the PC under Windows XP.  What seems to be the case, is that the program is expelled before allowing himself read the temperatures.  I use the modules of the series C 9213 and 9211 with 9188 Chassis.   My programs are showing 0 for temperatures.  Well, it's certainly in the low temp limit, so the program stops.  However, she should not do this.  I know there is little delay with the playback of all thermcouples in 9213 and 9211 modules, but this was not a problem with Windows XP.  Even if the program starts from scratch on the XP PC, temperatures immediately appear, or appear after a second or two.  Yes, I've rarely seen a temp 0 on the XP PC, but the program doesn't stop; Give it a second or two and the time appear.  Why is it that happens in Windows 7?

  An executable that works has no measure of temperature.  It uses only 9481 modules and run the solenoids at a rate of about 0.2 seconds.  This executable works fine on both computers.

  So what - this on the modules of temperature reading that is causing a problem in Windows 7?

  Other installation data :

  -The XP PC has the updates Labview 2010 is compatible with

  -The PC Win 7 not the latest updates of Labview 2010 there are has compatibility problems.  National Instruments has given me the compatible components, and they has several levels down by the most recent (for example MAX vs MAX 5.6 v14.0)

  
  

• LabVIEW 2011 executable does not close

  Hello

  I created a very simple piece of demo code to try to discover Labviews Plugin architecture (please see attached).

  For some reason when I create my demo code in an executable file and click the button stop the façade that closes, but the program continues to run in the taskbar.

  I built, run and compiled my code in Labview 2011 SP1.

  My final actions for the main vi are to close the front panel and then call the function "Quit Labview".

  Failure to close occurs intermittently (it will close with success after 3 out of 4).

  I have attached my code.  Does anyone have an idea why it doesn't work?

  Thank you!

  
  

• LabVIEW 2013 executable only works on the development machine?

  Hi all

  I created an executable to distribute my test software, but it only works on the development computer. With success, I gave my front executables with labview 2012 on the target computers by simply creating the .exe in the project and then Explorer in installing labview nessary drivers and run the engine of time without problems. Now, I created a new test with Labview 2013 program and I can not get my new test .exe application to run on the target computer. Has anyone seen this kind of problem before?  Any help will be appreciated.

  Thank you

  
  

• Creation of example Labview Subvi

  Hello

  I am using a Labview VI example as a Subvi in my projects. (Image/Vision/examples of treatment/Image Treshold.vi)

  I've wired the trajectory control and displays two images to the terminals at the top right of VI.

  Then, I created my main VI with a control path & two views of the image and add this example VI in my block diagram.

  Trajectory control works properly but I do not see the images loaded into my main VI.

  What I'm missing here?

  Thanks in advance.

  

  Problem solved.

  Just forgotten to remove IMAQ dispose screws

  Thank you for your interest and sorry for taking your time.

• Should I use Visa 5.0 if I do a labview 2009 executable?

  We want to make an installer for an executable created in Labview 2009. I installed LV 2010, but I opened the project (which has been done in 2009 LV) in 2009 from LV.

  DURATION VISA 5.0 is the only option for the VISA duration under the "additional installers".

  Will this work with an executable file LV 2009?

  The Readme for VISA indicates what versions of LabVIEW, it supports. Haven't you read? NI-VISA 5.0 supports versions of LabVIEW 8.5 front, so it does not work with 2009.

• Deploying a LabVIEW Windows executable on a Unix machine

  Hello everyone,

  Can someone tell me if it is possible to deploy an executable file created in Windows Labview 8.5 on a Unix machine. We would launch an executable and also to display a Web page on the UNIX-based computer to view the currently running program. And if it is possible, you have some tips?

  Thank you!

  Rocio

  I don't know anything about these older UNIX systems. If it is possible I don't know how to do it.

  Is it possible to get another machine and install Windows on it and then connect to the Tru64 on the network by using web services?

• Manufacturing of Panel of labwindows CVI as Labview Subvi

  Dear all,

  Does he know how to use LWCVI in Labview.

  I had developed LWCVI according to program GUI. Now, I want to use in labview, where I also want to use the value of some digital commands to the CVI group.

  Is it possible to call and use the LWCVI program in LABVIEW.

  -Vishnu

  
  

• LabVIEW Subvi VI icons changing crash - hierarchy

  Hello

  My LabVIEW hangs then close the icon editor that has been opened from within the hierarchy of the VI. Im running LabVIEW 2015f3 (32-bit) on Windows 10 (64-bit).

  Since this has been reported as a bug fixed (CAR ID 519216) in 2015 LabVIEW I was wondering if someone with the same configuration could check that this problem has indeed been fixed?

  Thank you.

  This happens on my installation of LabVIEW 2015 as well. Specifically, it seems that LabVIEW will break if you try to change the icon of a VI that is not open.

  Good taken, I'll see if I can open the CAR up Monday.

• How to declare the size of the array in a labview subvi

  
  

  Hi, I posted a response and documentation in the CVI hereforum: hope, he can help you.

• Reminders does not work in the executable LabVIEW front panel

  I have a couple of reminders in the process template that trigger an event in the event structure to update of the lights on the front panel for the user. Everything works fine until I have create an executable file. This can also be an indication of the other points, I have not discovered yet.

  Any ideas?

  Thanks for all the help.

  Found!

  Not unlike most of LabVIEW developers, I have a range of utility screws that I use over and over again. Such vi is vi uses a property node to find out what environment the application is running in, i.e. .llb, exe, development, publishing student, etc.. This vi is used because SEO screws in an executable file have a way different than when their listing in the development environment. Using this vi allows your code to reference the screws properly when developing and when the executable is built. The code still works because it automatically adjusts the referenced path of the vi. See attachment 'Path Finder.vi environment'.

  Now for the fun part! For some reason, perhaps because of the friendly character of NOR and the relationship it is with its developers :-), AND decided to change the path of the executables in LabVIEW 2009. After hours of troubleshooting and countless rebuilt, I came to the conclusion that the ' paths of the band of "work magically stopped working. It was at this time one of my friends happened to walk and ask why I had everything in my monitor across the room (figuratively speaking of course, I'm sure we've all been there). I explained what could be the only conclusion, band paths do not work!

  My friend immediately began laughing, having recently had the same problem. He explained that in LabVIEW 2009 executable paths are different and our 'find the path vi' would not work. He added that NOR, after finding this funny, however gave the developers a way to solve this problem with a check box within the app Builder. The box is called "Layout using LabVIEW 8.x file." See attached photo named "App Builder."

  The only thing I could say to my friend was, ' silly me, I should have know what that.»

  Laughing out loud

  Thank you for trying to help, it launched my butt.

• TestStand can't find subVIs with Labview RTE

  I read the user manual on how config map if I want to call a VI with RTE labivew, but I'm still, puzzle on TestSatnd can not find the subVIs.

  Here's what I have:

  1. a development PC teststand with the right version of Labview RTE installed.

  2 another PC installed labview development system

  3. I created a VI in labview, PC using features of Report Builder. Of course, she calls a few vi.lib of labview subVIs.

  4 then I copy this VI to Teststand PC and try to load the sequence VI, he transforms a cannot find the subVIs.

  I wonder if Labview RTE includes all vi.lib, instr.lib. What should I do if I want to call this VI without installing the development system in the machine of teststand?

  
  

• What I need to install in another pc without LabView and wants use executable Vi

  Hi, everyone, please, help me

  I want to use another VI without LabVIEW PC executable, what I have to do to run the VI.exe?

  Thank you

  At a minimum, you will need to install the LabVIEW runtime engine.

  You may need to install more depending on what your program does.  Maybe the drivers DAQmx or the VISA run-time.

• Why my executables LabVIEW losing features GPIB after update to 488,2 drivers

  A year ago on a remote test unit, I had put in place for a production line, a worker had decided to launch National Service update of the Instruments on the test PC and update all available programs. After this update, none of the GPIB functions worked on test executable for the test of LabVIEW software. After the execution of Automation Explorer, I was able to confirm that all of the GPIB instruments were still present, operation and alias still correct. The only way I could solve this problem was by erasing all National Instruments software and put it back into place, again.

  Yesterday on a local test machine is the same thing. This time 488.2 full driver package has been installed from a USB stick to update the 488,2 drivers on the machine and subsequently, none of the GPIB functions worked, causing all LabVIEW test executables to lock up. Once again, Automation Explorer shows that the GPIB instruments are installed and functioning and all aliases are always accurate. I erased all the software of NOR and reinstalled but now I stil can't get LabVIEW programs to work properly.

  Someone at - it of another expereinced this problem?

  What is the solution?

  After thinking the problem to the remote installation, it appeared that after a year of operation, the problem occurred after update 488,2 pilots to the new version 14.0

  The cure is to install the drivers of v3.1.2 previous back on the system.

  I uninstalled all the software version 14 of OR out of my test PC set-up and installed the package v3.1.2 OR-488. 2 and all the executables started working again.

  The Readme for VISA DURATION v14.0 says is comaptible with LabVIEW versions 2011-2014, but apparently there is a problem at least 2013 that touched me.