Run LabVIEW executable in Windows 7

Similar Questions

• Error Code 37 running labview 6 with windows XP

  I checked most of the posts about this generic error code 37. Here's my dilemma... Labview 6 running on a windows NT system. This computer is on its last breath, and we want to switch to XP... I installed labview 6 on a XP machine and the program works very well... and I actually get my external device data unless I get the ERROR 37... the great thing is I can not launch a Subvi, which creates a linear between because once I get error 37, stops the Subvi. I don't understand how can I read data from my external device, still get the device not found msg. I even tried to install 7 LV and LV 8 still get the same results.

  To close the Communication port, you could create a new white vi, ask a close visa on the block diagram, he points to the port to close and run the vi.

• You use HP 4156 instrument with Labview 2010 in Windows 7

  We recently bought Labview 2010 for Windows 7 and some software porting, we had on Labview 6.  These programs of control of two instruments: HP (Agilent) 4156A parameter Analyzer and the Keithley 7001 switch system.  When I looked for the drivers of instruments for these two systems, they were no longer available for Labview 2009 and associated NI-VISA 3.2 driver is not compatible with Windows 7.  You have any suggestions on how we can run Labview 2010 on Windows 7 with the ch (Agilent) 4156 A and Keithley 7001?

  A pilot in 2009 can be loaded in 2010 and this is the minimum VISA version, you can use. You need not even the driver of instruments most recent. Just run your existing code.

• Is it possible to run an executable on a Windows Phone 8 Labview?

  If I create an executable of Labview, it will be possible to run it on a Windows 8 phone?

  No, as Mike has already said.

  The reason is that an executable of LabVIEW contains a binary code that is compiled for the x 86 architecture CPU, and access to the Win32 API. Windows Phone general works on the ARM or RISC processors and provided only a subset of Win32 very limited in the past. With the new Windows RT technology that he actually moved even further the Win32 compatibility as it is all architecture is based on .net technology.

  So even if you happen to get a processor Intel Atom based device Windows Phone that would be compatible x 86 it couldn't work, because a LabVIEW executable is an executable format portable Win32 is not a picture of .net bytecode.

• executable files may only work running labview

  Dear all,

  I simply create an executable file that calls several functions of a DLL (also written in LabVIEW), the LabVIEW DLL will call a DLL acquisition card written in c ++ to capture images from my camera. Everything worked fine until I have copy my entire program to a pc with the only run LabVIEW and installed vision. While the program no longer works. The LabVIEW DLL I call keep will return null string that it's not supposed to be. The DLL is supposed to return 0 for any mistake or any number which is the error code.

  Help, please... Thank you very much!!

  Hi GerdW,

  Thanks for the reply.

  I just thought of it.

  It was because I only installed runtime of vision but has not installed the device IMAQ driver.

  My program works fine after installing the device IMAW driver.

• How can question I run an executable file in the background?

  Hello

  I'm trying to run an executable in the context of LabVIEw, but none of the methods described in the forum and on ni.com seems to work. I use LV 2011 on a 64-bit Windows 7 machine where it is important.

  I tried the method described in "How to make an executable in the background as a marketing app?" (http://digital.ni.com/public.nsf/websearch/4A8B626B55B96C248625796000569FA9?opendocument&Submitted&&... but I always see a fragment of a window at the bottom near the start (Exhibit 1) key.) Table 2 shows that it consists only of the title bar. (I customized the appearance of the window as described and added the two points

  HideRootWindow = True

  UseTaskBar = FALSE

  in the *.ini file.)

  I also tried to disable all other items in the menu customize appearance of window with the same result.

  Then I tried the method described in "Ongoing execution of an executable of LabVIEW as a background process" (http://digital.ni.com/public.nsf/allkb/EFEAE56A94A007D586256EF3006E258B) addition of the FP. Open the VI method and affecting the hidden state. I got the same result (table 1).

  Should I do more or different for my version of windows? I appreciate your help. Thank you.

  I found the problem. It was a wrong directory for the build name. I continued under an older version of the executable with the default window settings. The method that is described in how to run an executable file in the background as a startup Application? "(Works... http://digital.ni.com/public.nsf/websearch/4A8B626B55B96C248625796000569FA9?opendocument&Submitted&& .

  Sorry, for wasting your time. Mea culpa.

  Peter

• Running Labview embedded Office - MinnowBoard or raspberry pi 2

  It is possible to run the executable LabView in the embedded Board?

  as a raspberry pi 2, minnowBoard, BeableBone?

  Thank you

  It's the one - http://www.tsxperts.com/labviewforraspberrypi/

  Looks really cool, but still some time away.

  Edit - you should know that they do not already have the version of Arduino out. I did have the opportunity to use it, but the IP is obviously a more promising target because of its benefits.

  http://www.tsxperts.com/Arduino-compatible-compiler-for-LabVIEW/

• (My Labview executable built) has encountered a problem and needs to close.

  All,

  I built a labview executable that interacts with the GPIB and the Texas Instruments EV2300 via USB.

  The VI works beautifully on the development computer and I built the VI in an executable file and it works fine on the development computer.  So, I built a Setup program that installs running Labview 2010 on the target computer.  I ran the Setup program on a computer on the production line I know can run GPIB and the EV2300, but when I try to run the executable I get an error that says: ""(votre demande) has encountered an error and needs to close.""

  I can get labview executables that do not speak of GPIB or USB to run on the target computer, then it is not the execution environment.  And I VB6 applications that can run EV2300 and GPIB interfaces smoothly.

  I don't do anything weird with the paths to files in my program, only the creation of the railways using the VI canned to convert strings into paths.  Under the program, I've read some text files and write a.

  Is there anything that I need to know how to build an application with an installer?  I need to get up and running so the test program can work on a production line.

  
  

• There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  Hi, I m a bit new in LabVIEW and I'd like to ask a few questions...

  -There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  -One API PI or raspberry beaglebone exists for LabVIEW?

  -Power supply Wich can recommend you control with LabVIEW? (some chip solution witn 0 - 30v / 0 - 3A DC)

  Thank you very much for your advice!

  Best regards

  Elena

  Elena,

  I know raspberry, so no comment on that.

  For the rest:

  -Do you want to create tools for developers? If so, we must look in the API of project VI and VI server. If this isn't the case, please compile your application LV as executable and call this one using a batch file.

  -LV prefer specific supplies. LV is a programming language. There are several power supply providers (including OR) which provide directly the LV API for their power supplies. So, essentially, the approach is:

  1. choose food that serves your needs.

  2. check if the power supply has a standard interface for programming (such as Ethernet, GPIB, or if the power supply is PXI, is already providing a programming interface!)

  3. check if the LV API (so-called "instrument driver") is available for the device. In the case of a PXI system, get you a device driver (for example NI DCPower).

  4. check if the LV samples are available (for example in the Finder for example LV once you have installed the driver).

  Norbert

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• where labview.ini in Windows 7

  I just started w / win7. Of course, things are different. where labview.ini in Windows 7?

  Chuck Lippmeier

  In the same place it was before - right next to the LabVIEW application. You running 64-bit Windows, but have 32-bit LabVIEW? If so, look in C:\Program Files (x 86).

• Problem in opening and running LabVIEW in separate user account

  Hello

  I would like to create a 2nd user account on my computer in the laboratory that has LabVIEW 2011 installed on it. However, when I try to open LabVIEW in the 2nd user account there is an error code 1 and another message complaining about some dialogue 3 button VI.

  I found that I can still continue by clicking OK, except that now I can't start my VI, where I copied over my 1 user account. I get attached errors, including one that seems to be complaining of Simple error handler in my VI which runs at the end of my program error messages. Does anyone have an idea on how to fix the errors?

  Help, please!

  Thank you!!!

  Hi Vrinkle,

  LabVIEW is usually installed in "C:\Program files (x 86) \National Instruments\LabVIEW xxx ', where"(x 86) "is the version of LabVIEW application for a 32-bit version of LabVIEW on a Windows 64-bit and"xxx"brand (year)." In this folder you will find subfolders "vi.lib", "instr.lib" and "user.lib" - all the rights granted to your new user account need to access these files (like all the others those of LabVIEW file)!

  BTW. display your serial number on a public forum is not the best idea...

• Software to install to run redistributable LabWindows on Window XP?

  Hi all

  I wrote a sort of Hello World of GUI in LabWindows. I need to run his reditributable on Windows XP OS that is not any LabWindows software installed on it. I tried to launch its redistributable on Windows XP; However, I have some errors. How should I proceed? The library files must be installed?

  Thank you

  Kanu

  Hi, Kanu, you cannot simply copy a CVI executable on a new machine to run: the minimum required is to install the runtime engine CVI on the system target; After thet, your software may require some additional component or driver to correctly executed.

  This knowledge base article addresses this issue in detail and explains how to create a distribution kit that installs all the necessary software on the target computer. See also the other links on this page and the sections of online Help article.

• error 1 when running standalone executable

  Hey everybody,

  I'm having some trouble with an app that I'm building in an executable file. Now, it seems that everything is build without errors, but when I go to run the executable file I get a weird 1 error from one of LabVIEW built in libraries. I tried to do remote debugging, but I do not see the error pop up in my code anywhere, so I'm a bit confused as to what is happening.

  The error does not collect until after I click on a button that loads a VI in a secondary school (high school even load the correct VI). Also, I don't get any errors when I run the VI in the development environment.

  I have attached a picture of what the error said.

  Thanks in advance for the help.

  Ryan

  Your error message indicates that the error is from the VI who writes in a configuration file and has nothing to do with the sub-panels or the reset of values. You're probably update a configuration file with certain values or something. You show your real code makes it, but if I had hazad a guess I would ask are you aware of this: why my executable not working when using the VI Constant current path?

  As for your question on the application path: http://zone.ni.com/reference/en-XX/help/371361H-01/lvprop/app_appdir_path/

• Run the executable from the folder that is being synchronized

  We run a view environment 5.0, Windows 7 and Persona.  The folder on the desktop is one of the folders that is redirected.  If a user copy an executable file on the desktop, the permissions of the server where the folder is redirected resident take previous.  He cannot run the executable file on his desk and gets an error Windows cannot access it.

  Thank you

  When you say that the the desktop folder is redirected, which is part of the Folder Redirection GPO folder, or is it just part of the character which is managed by the Directorate of Persona? If it is redirected to a network location using the Folder Redirection settings, then the permissions associated with this network location would come into play. If you examine the properties of the executable file, is there an option to unlock the file to the bottom of the dialog box? Who could be there if you try to run an executable file from a network location.

  If it's just being roamed by using the Persona management, perhaps you must set the desktop folder to preload? It is possible that the icon is on the desktop, but the file itself has not finished downloading yet.

  Dave