Building an executable

Ive been trying to build an executable to run on a different computer, but I must be doing something wrong. I have read the NI tips on this subject and I also have the Labview for Everyone book that I have been trying to solve my problem with but I just can't seem to figure it out.
My program works on my computer, but on the computer I am installing it on (which also has the same version of labview installed) it runs but it doesn't do anything, it just hangs up. It does not give me any error messages and the program does not break, it just keeps running but doesn't do anything.
I have attached some screenshots to show how I am building the application in the project explorer.
One thing I notice is that my application has a bunch of sub.vis, but none of them appear in the project explorer. I was under the impression that it adds all sub.vis automatically, but maybe I am missing something.
Also I am confused as to the difference between "Startup VIs" and "Always Included" shown in the image called "Application Builder."

Adding a VI to a project does not automatically add all subVIs. It doesn't have to. You can add the subVIs yourself if you wish, but it's strictly not necessary. I typically like to see everything in the project file, but some folks don't. Startup VIs refers to the top-level VIs in the application. Normally you'd have just one, but you can have more than one. Always included refers to VIs that you load dynamically. Since they are not directly linked to a VI, in order to make sure they get included with the application you need to put them in that list. This is all explained in the LabVIEW manual. Did you read it?
As for your issue, your code screenshot implies that you are talking to an instrument. Have you installed the required drivers on the target machine? If your subVIs are using VISA then you should install NI-VISA and NI-488.2. If you're using the plain GPIB functions, then you only need NI-488.2.
Aside: your use of local variables like that is usually a red flag. Not in the sense that local variables are bad, but it's impossible to say from just the screenshot if you have some sort of race condition. Also, it's not clear what your intention is with error handling. If an error occurs on the first iteration of the loop, that will not prevent subsequent iterations from running, since the string of VIs are controlled from a tunnel, which means each iteration only ever sees the tunnel value at the start of the loop.

Similar Messages

Error while building an executable from vi

Hello,
I am trying to make a .exe file from the VI which includes Vision Aquisition Software also and while building it I get a error message--
Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass: Save.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Create_Build_Application.vi -> EBUIP_Global_OnCommand.vi -> EBUIP_Global_OnCommand.vi.ProxyCaller
Possible reason(s):
LabVIEW: Cannot save a bad VI without its block diagram.
Can anyone tell me how to solve this problem ?
Thanks in advance.

I had done that and did not work. I did not get rid of the old build defination, but started a brand new one via Tools>Build Application (EXE) from VI... I got the same error 1502. Inspecting the offending VI did not yield any obvious problem with the block diagram.
Upon searching for error 1502, I found this Know Issue link:
http://www.ni.com/white-paper/11869/en. Issue ID 255617 stated:
Error 1502 can occur if dependencies are placed in non executing case structures
In previous versions of LabVIEW you could place VIs in a case structure with a constant wired the the case selector. This would load the VIs at runtime. If you have this pattern and attempt to build an executable you could receive error 1502
Workaround: Don't use unreachable code
So the issue is I have an case structure with hard coded boolean, so the other case is unreachable.

Error when building an executable in BridgeVIEW

Hi,
Every time I try to build an executable in BridgeVIEW I get an error that I have to close all VIs before building an EXE, but I only have the top level VI open. I tried shutting down the PC and restarting but nothing works. I have seen this in LabVIEW, but LV closes them for you.
Any ideas?
Thanks.

Lupita wrote:
HI,
You are probably right. So here is what Ive tried:
1) Restarting my PC. Opening a blank new VI and trying to build an application by adding my "main.vi" as a top level VI. This way I make sure there are NO VIs opened.
The list that appears on the Build Application menu contains ALL VIs called by my main.vi.
Thanks again.
I can't really say that I remember a behaviour like this but considering that the latest BridgeVIEW version corresponds to LabVIEW 4.1 (which was never released) or so, I would say that this is so long ago that my memory might be flaky here.
And the application builder back then was also not the same as it is now. I'm afraid unless you are going to use a more recent version of LabVIEW together with the DSC Toolkit (which is basically what BridgeVIEW evolved into) there is little cahnge that anybody can help you with this here.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

STANDA MOTOR AND BUILDING AN EXECUTABLE APPLICATION

Hello,
I have some problem to build a executable file from the main labview program.
For other applications and devices i don't have any problems (i build
executable files and use them on other computer without any problems).
But with this stepper motor, the main program and the examples given by the
comapany in Labview works and the executable files don't (By not working i have
no particula error message but no remote control at all).
Has someone met this problem?
I think that there is something wrong during compilation (links are missing or
something like that?)
I would appreciate help on this point
Thanks a lot
Regards
Julien

the config file i rename it in *.txt in order to be able to send on the site
Julien
Attachments:
config_julien_V1.txt ‏1 KB

How do I build an executable w/o installing the runtime engine in the OS?

Hello everyone
I have developped an application with LabView 8.01 and build an executable for a customer, this works great, if I have administrator rights. But my customer don't have full administrator rights and they are not able to install the software (Runtime Engine). In LabView 6.0.1, to solve this problem we added the lvrt.dll and some support files directly to the application builder as support files and it worked without to install the runtime engine in the operating system.
How can this be done in LabView 8.0.1 and which files are needed?
I am thankfull for any advice.

hi,
you always need admin rights to install software.
I think it's not possible in labVIEW 8.01 to install the runtime without admin rights.
The costumer only has to the runtime one time, so he should try to contact his system administrator.
I've found no workaround for it.
Best regards.
Christoph Strasser
AE/NIG

When building an executable I get the error message var.lsb not found.

When building that executable with LV 5.0 it will work, but it will not work on a korean version of WinNT 4.0.

When exactly does the error message come up? When you're doing the build or when you attempt to run the executable?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Building an Executable - Not Enough Memory to complete this operation

I am trying to build an executable from my project, it is quite a large program. During the build, within the 'initializing build' phase, I get the error message 'not enough memory to complete this operation'. I have a decent PC running XP and 4GB ram. LabVIEW is using about 1.2GB of ram when the problem occurs.
This is an application that I've been working on for some time and I have experienced similiar problems before. To get round it I have added the /3GB switch to the boot.ini file. However that is no longer working, it complains of a problem loading a dll which seems to have only started happening since moving to LV2012.
Does anybody have any experience with solving this problem please? It is a bit of a showstopper for me at the moment.
Thank you,
Martin

Hi Martin,
Adding the 3GB switch is a solution which should still work on your system.
I'm a little confused, is the system still complaining about not having enough memory? Or is it just the dll problem?
And is the error message occuring during the build, or when trying to run the .exe?
The dll in question is associated with DAQmx.
If it is a runtime problem rather than a build problem, it may be that you haven't included the DAQmx driver on the target machine, in which case the answer lies in this document: http://www.ni.com/white-paper/5406/en
If I've misunderstood, please clarify the exact issue which is currently occuring, and we can continue to troubleshoot.
Ian S
Applications Engineer CLD
National Instruments UK&Ireland

Why might a VI break when building an executable on one machine versus another?

I have a large test application that is designed to work on several machines. In the process of testing I go to each machine and open the project on the machine I am testing. When I am satisfied the project is behaving as expected I build the executable and test that it is working as expected. This is where my problem occurs.
More Background: This software was originally meant to run one test at a time and was upgraded to run multiple tests at the same time(sharing resources and the like). To accomplish this, another VI was written that opened instances of the original VI (clone). I don't know if this is common, however this has been in use for a while and is known to work even after the migration to the network(probably not the problem).
My issue is that I can build the software on one machine and it will work on another machine, yet when I try to build the same exact project from the other machine it will no longer open the instance of the original VI. I probed the error wire and it indicates that the VI must be broken. So I open the VI and it has no errors.
I have no idea how to diagnose this any further. Anyone have any ideas?
-Nate
Solved!
Go to Solution.

Try mass compiling the entire project hierarchy prior to making a build. Also, if you are dynamically launching VI's, you must put them in the "Always Include" section of a Build Spec.
Do either of these things help?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

I need to build an executable which allows all the VIs to be viewed as if in LabView

I hope I am not being stupid but I need to build an executable which allows all the VIs to be viewed, opened - closed, as if being interpreted by LabView 8.5. The system is a simulator and I am required to allow the system to be inspected for correctness whilst running. Further, interactive panels exist at various locations throughout the structure and they must all work.
Can somebody tell me how to do this or provide me with some pointers?
Ideally I would like the navigation to be the same as if the code was being operated within LabView then the same idiots guide, I’ll need it in two years, will work for both the exe and the interpreted versions. The target machines will not run LabView and simply distributing the VI tree would be very bad news because it would allow erroneous edits to break the system.
Thanks in advance

Mike
Sorry I may not have expressed myself well.
I have developed the system in LabView 8.5 and I now want to release it to be installed on machines without LabView. I can do that, however I have a problem. I am required to allow the internals (the source) of the system to be visable; I don’t know how to do that without LabView on the machine. Yes, I know I could produce PDFs for all 1500+ VIs but I don’t want to do that and the customer does not want it eather; he wants to navigate the model and check what he finds.
I hope this makes my requirements clearer.
Thanks
Frank

Some problems while building tuxedo executables (OS/390 - Open MVS)

Hi,
I have a both strange and serious (at least it seems serious to me) problem
with building tuxedo executables.
I'd like to link the object files with a library I created (say libmylib.a),
and the only place I know about to pass some info to the tux builders is the
env var CFLAGS. In my case the CFLAGS looks as follows: "-L
/u/myhome/myproject/lib -lmylib", but the linker protests, saying that the
symbols from object files placed in my library can't be resolved ;(.
On the other hand if I just take the object files out from the library and
try to link the executable placing all of them explicitly in the command
line everything goes smoothly.
HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELP...
Regards
Chris
PS. I use Tuxedo release 6.5

Hello,
Welcome to MSDN forum.
I am afraid that the issue is out of support range of VS General Question forum which mainly discusses
the usage of Visual Studio IDE such as WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
Because your issue is about ASP.NET web application development, I suggest that you can consult your issue on ASP.NET forum:
http://forums.asp.net/
for better solution and support.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Help building an executable that uses a factory pattern

Hello,
I'm trying to build an .exe from a VI that uses the factory pattern. The VI gives me the error that it can't find the classes to load and is looking outside the .exe file to find them. The specific error is:
"Get LV Class Default Value.vi<APPEND>
<b>Complete call chain:</b>
Get LV Class Default Value.vi
Main.vi
<b>LabVIEW attempted to load the class at this path:</b>
C:\ATE\Experiments\Build Testing\Builds\Virtual Classes\High Class\High Class.lvclass"
I thought those classes were bundled into the .exe when it was built? I have included the class folders in the "Always Included" window of the build script.
Any help would be appreciated. I'm fairly new to classes and I haven't built an .exe with an app using the factory pattern.
Thanks,
Simon
Attachments:
Build Testing.zip ‏491 KB

This might be the answer. I found the following checklist on Building Executables. It really is referencing things other than Objects, but maybe Object folders also need to be properly located ...
Bob Schor [the stuff I found is below this line ...]
Ensure paths generate correctly.
Details
If a VI loads other VIs dynamically using VI Server or calls a dynamically loaded VI through a Call By Reference node, make sure the application or source distribution creates the paths for the VIs correctly. To ensure paths generate correctly, use relative paths to load the VIs. The following table depicts the relative paths for a top-level VI, foo.vi, which calls a.vi and b.vi. C:\..\Application.exe represents the path to the application.
Path to source files
Path to files in application
C:\Source\foo.vi
C:\..\Application.exe\foo.vi
C:\Source\xxx\a.vi
C:\..\Application.exe\xxx\a.vi
C:\Source\yyy\b.vi
C:\..\Application.exe\yyy\b.vi
If you use the LabVIEW 8.x file layout and you include dynamically loaded VIs in the application, the paths to the VIs change. For example, if you build b.vi into an application, its path is C:\..\Application.exe\b.vi whereC:\..\Application.exe represents the path to the application and its filename.

Error 8 occurred when building an executable due to file permission error?

I received this error on executable builds from two different .vis. Other .vis in the project build without incident and the message below doesn't seem to indicate the file that is causing the problem, unless it is the SPT-errors.txt file listed at the end of the error message.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files\National Instruments\LabVIEW 8.5\project\errors\Japanese\SPT-errors.txt

Hi DanielAllis,
Like mentioned earlier, there is most likely an application on the internet that you can find and use where you can see what processes are calling specific files or folders to see if that specific file is being used by anything else. It doesn't sound like this is the root of your problem, but it couldn't hurt to check. Also, I have seen a similar problem to this with someone who was using the software Subversion and Tortoise with their application. I am not familiar with this software in particular, but I have attached a link below that goes through the steps that this other person took to try and fix the same error when having this software on their computer. Let me know if any of this helps!
http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537
Regards
Noah R
Applications Engineering
National Instruments

Building java executable for windows

Well, actually I have two qestions:
1) how it is possible to build executable running under windows using usual Java tools, e. g. ant or something like this?
2) if I'm using VS.NET I can't compile files wich import javax. ... etc. classes, what I should to in order to import them?
Any suggestions welcome.

Well, actually I have two qestions:
1) how it is possible to build executable running
You want a .exe at a guess, search the forums.
All the regs. have answed this many many many times, and some very good answers exist on the forums.
Normally, when people ask this, they really need to read:
http://java.sun.com/docs/books/tutorial/jar/
http://java.sun.com/products/javawebstart/
But sometime (not very ofton) a ".exe" is needed:
http://gcc.gnu.org/java/
http://www.excelsior-usa.com/jet.html
under windows using usual Java tools, e. g. ant or
something like this?Sure, make a new task. For GCJ this would be very easy.
2) if I'm using VS.NET I can't compile files wich
import javax. ... etc. classes, what I should to in
order to import them?Are you compiling to .NET or to Java Byte Code.
If its Java Byte Code, I have no idea, if its .NET the below might work
http://classpath.org
http://www.ikvm.net/

How to build and executable which will include Advantech DAQ vi's. Have Advantech USB 4750

I'm using Advantech USB 4750 hardware and Advantech DAQ VIs. It is working perfectly on the developing machine. Now i'm trying to create an executable. cant get the executable to talk to the DAQ. I already installed the USB 4750 driver and runtime engine in the machine I will be running my executable. How do I incorporate the Advantech DAQ VIs to my executable. They are showing as dependancies on the Project exlporer. Need some help on this.

Hello DiracDeltaForce,
Besides Travis-E recommendations on this post, I wanted to show you these links:
Building an Installer (Windows) - LabVIEW 2012 Help
http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/build_installer/
Building a Stand-Alone Application - LabVIEW 2012 Help
http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/building_a_stand_alone_app/
Hope you find them useful.
Regards
Ernesto
Applications Engineer
National Instruments

Building an executable without configuring the Measurement & Automation Explorer

After building my FieldPoint executable I want to install the program on a target computer. There I need the FieldPoint Server and the LabVIEW runtime engine. Why do I have to manually configure the Measurement & Automation Explorer (attaching the .iak file), when my .iak file is included in the installer of my executable? And how could I solve it, that I would not have to configure it for every user of the computer again?
I would like to have an executable which is ready to run after the run of the installer...
Can somebody help me out?

I don't have the proper things in front of me at the moment, but here is a guess as to what your problem might be.
When you use a FP IO Address, the default root for the address is Fieldpoint, which is the last iak file that was saved\opened in MAX. I think that if you change this in your program to a different file (there is a second tab in the IO address window where you can do this), it should force the program to go to the specific iak file.
Try to take over the world!

Building an executable

Similar Messages

Maybe you are looking for