Autonomy with application builder?

Hello.
I have tried to compile an application with the "application builder" I find in the menu. (see picture below).
My problem is that the .exe file created needs labview to run.
Is it because the version of Labview I have (V 7.1) doesn't include the real "application builder" or because the .exe built with this application builder aren't autonomous but needs Labview to run?
(I want to run the program built on a computer without Labview).
regards.
Vincent.
Attachments:
application_builder.jpg ‏48 KB
labview_menu.jpg ‏39 KB

The resulting exe does not need the complete LabView installed: it is satisified with the LabView run-time engine.
There is an option to include it in the distribution if you create an installer (see the Advanced button).
Otherwise, you can download the Runtime Engine Installer from ni.com:
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C130D?opendocument&node=1...
Paolo
Paolo
LV 7.0, 7.1, 8.0.1, 2011

Similar Messages

Problem with Application build in JDeveloper 11.1.5 to WLS 10.3.5

Hi to everyone, I have a problem with a application build in JDeveloper 11.1.5 and deployed to a standalone WLS 10.3.5 ( with the JRF template appliied , to run adf applications )
When I try access to the page : localhost:7001/myApp , it show me :
"Error 403 Fordbbiben ".
but when I put :
localhost:7001/myApp/index.jspx, it show me :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 8, 2012 9:06:22 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
What can I do to fix the problem ??
Thanks

Analyzing the problem, I created a new ADF application with only a web page (index.jspx) , and deploy it to the WLS, and I access to URL of page and it runs !! ( http:localhost:7001/myApp/faces/index.jspx ).
But, when I ADD A TASK FLOW to the application and deploy to the WLS newly , and try to access to the URL application's ( http:localhost:7001/myApp/faces/index.jspx ) . It show me again :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 10, 2012 19:02:57 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
Why it show me that error when I ADD a Task Flow to the Application ???
Can Anyone help me please ?? I m varios days with this problem. Thanks

Error 7 occurred at Open VI Reference with Application Builder

Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
"Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

Dear Sir;
There are two things that are good to try:
First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
.llb file to compile.
Regards

Error message "VI is not executable"! Need help with Application Builder

Hello,
I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
To get a better idea from my project, here a little description of it:
In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
So, i hope to get an answer soon (the deadline for the project is not soooo far away )
If you need more information, please let it know...
I would be very grateful if there is someone with a working solution...
Kind regards from the Netherlands,
Sebastian

Sebastian,
Your architecture makes it very difficult to debug this and other problems. Does the error message mention which VI is causing the problem? It is very important to wire your error clusters everywhere. In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute. At the end, place an error cluster indicator that you can see on your front panel. When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
This is a start, but you really need to push this into a queued-state machine before this gets any more complicated. As it were, if anything in your loop hangs, your whole application hangs. See attached for a queued-message handler (not advisable for actual applications, but you get the point. You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
-Jason
Message Edited by LabBEAN on 01-20-2009 08:36 AM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
State Machine.vi ‏18 KB

Using dynamic VI referencing in combination with Application Builder

Hi.
In this thread (http://forums.ni.com/t5/LabVIEW/How-to-access-a-known-control-in-a-VI-reference/td-p/1255244) I attempted to modify our under development test system, so that we didn't have to change the same main VI for every test that we are adding, since we are several persons who'll be adding tests (i.e. conflicts would arise, that we would have to iron out manually every time). The solution in the thread above works very well, by opening a reference to the test sub VI and calling the reference. I then can pass data to the sub VI, and can get the test results from the sub VI. Great!
The problem came when running the program through the Application Builder. The test system starts up fine, but the above method fails miserably, since the sub VI files are no longer there. It seems that the sub VI's are not a part of the exe binary file coming from the Application Builder.
So I'm drawing a blank here. Does anyone have a suggestion on how to to this? I'm only seeing the two options. Either adding the sub VI's in the same main VI file, but then we have to be very careful on not getting conflicts (or fix the conflicts manually when they arise). Or use the dynamic VI referencing, but then the system doesn't work with the Application Builder (which means that this method is out). Is there a third method of doing this?

Hi Mike.
I use LabVIEW 2009.
Well, I actually *can* use the dynamic call solution now. The problem was that (1) the files weren't included in the exe file (fixed by adjusting the Application Builder settings), and (2) the Check if File or Folder Exist VI doesn't work if I try to check if the sub VI is present inside the exe file. The solution here was basically to ommit the whole Check if File or Folder Exist VI, and just do an error check on the Open VI Reference VI. The Open VI Reference VI will fail if trying to open a reference to a file that doesn't exist, so I just wired that to a case loop around the Call By Reference VI.

Problems with Application Builder and NI-DAQmx drivers in Labview 8.2 Professional

Hello everyone,
I am trying to use the application builder to create an executable so that someone without labview is capable of a remote panel connection to connect to our test laboratory. our test laboratory uses the USB Compact DAQ 9172. I did find some other forums that ran into a similar problem where a computer that didnt have labview installed on it looked for a particular driver (nilvaiu.dll). The common solution appeared to be when building the installer, include the current NI-DAQmx (8.3 in our case) option and then the clients worked fine. My question is when i use the application builder to create an installation file for this application, i get a prompt to:
Locate the "National Instruments Device Drivers - February 2006 Disk 1" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
What is confusing is that the installation cd's in our laboratory are from August 2006 (501165N-03). It didnt make sense to me that i would need to downgrade the drivers from a few months ago, but i've been wrong before. We just upgraded from the full development to the professional version about 2 weeks ago to utilize the application builder function. Has anyone else ran into this problem and could this be a limitation because we purchased the software with the academic discount?
thanks in advance
Chris

Chris,
My "fix" is brute force. Backup everything. Removing all the NI software takes a while. Be sure to remove leftover directories and files.
Altering the windows registry takes seconds and is not hard if you know what you are looking for. I've attached a screen shot with the NI entry selected. This is what I deleted on by machine. The thing to remember is that the registry controls all the software on your pc. Delete/alter the wrong entry and you have problems. Worst case scenario is that you could end up formating the hard drive and starting over from scratch. I'm not trying to scare you, but I want to make sure you understand the potential for harm.
One thing you might try first. NI-DAQmx 8.5 is now available for download from NI. You might try unloading 8.3 and installing 8.5.
Attachments:
regedit pic.JPG ‏102 KB

Error 10 occurred When createing an executable with application Builder?

Problem: I am using the LabVIEW Application Builder to create an executable from my VI. When I run the Application Builder, I receive the following error:
Error 10 occurred at Copy in Win Install Copy Redistribution Files.vi->Win Install Create.vi->Dist Call Create Installer.vi->Builder Application.vi
Possible Reason(s)
Labview : Duplicate Path
or
NI-488 : New I/O attempted with old I/O in progress
Why do i receive this error and how can i resolv this issue?

Jiang,
It sounds like this could be an overwrite issue. From the file path you specified, I can tell you that the error is occurring in creating the installer for your executable. Are you specifying an installer directory where you have already created an installer of the same name? If so, is that directory read only? Make sure that write privileges are enabled for you installer directory, and if that doesn't fix anything, try specifying a different installer directory.
If none of these suggestions take care of the problem, please post a simple example that illustrates the problem (i.e. a simple VI and a copy of the build file). We can then try to replicate the problem and troubleshoot it. What version of LabVIEW are you using?
Regards,
E. Sulzer
Applications Engineer
National Instruments

Installer built with Application Builder gives error "Cannot install, higher version already installed"

I am having an issue with an installer which I created with the Application Builder. I have a project that I have successfully deployed. Subsequently I created another project (and vi) which is based on a copy of the originals, both with new file names. In the renamed project file, I changed all file names, paths, and all resources, to reflect the new names. I also changed the installer’s destination and install folders, of course. I reset the executable’s version number (in the Build Specification properties) to 1.0 (the original was 1.3). I then successfully built an executable and the application installer. However, when I run the installer (setup.exe), it gives a dialog (after the license screen) that it “Cannot install” because a “higher version already installed”.
I’ve done exactly the same thing with other vi’s and projects of mine, and never had this issue. The installer correctly installs the newly created (and renamed) version where it is told to in the project file. Also, I’ve never had a problem deploying (installing) on my development PC either.
I have carefully checked and rechecked to make sure there is no reference to the original executable or paths. What could be causing this behavior? I want to keep the two projects completely separate, so simply changing the version to higher than 1.3 is not an acceptable solution.
Thanks to anyone in advance for any help and suggestions.
Ed

Yes, LV 8.5 does NOT give me control over the GUID. In the project file there are three such strings:
"App_applicationGUID"
"App_INI_aliasGUID"
"App_INI_GUID"
They all have different numbers and none of them match the GUID or PackageGUID in setup.ini. I don't know if they are related or not, but usually it's not a good idea to mess with (manually edit) files like these (project, ini, etc.) unless you know what you are doing. (For example, I do edit the setup.ini file to change some of the [Dialogs] parameters, but that is based on direction from NI support.)
Anyway, like I said, I've made copies of projects before and never ran into this problem. At least I have a solution, however laborious, in creating a new project file from scratch.
Let me know if anyone has more thoughts on this.
Ed

Queues in application made with application builder don't work?

(Labview 2011) I have a medium sized application that runs just fine within the Labview environment. It uses event trapping for most things and passes longer tasks off to a consumer loop using a queue. Having gotten it to run the way I want, I want to use the application builder to turn it into a stand alone exe that can be distributed. It compiles without any errors or warnings and starts up fine. However, anything that happens via a queue doesn't work. The very first thing that should happen within any of the queues is that it should disable and grey out certain buttons to prevent unwanted behaviour. They don't get disabled and greyed out. So it's pretty clear nothing gets started. The queues also all have error handlers and there's no peep from them. Everything that doesn't use a queue works OK. Is there some kind of option in the application builder I need to activate to get the queues to work properly? The consumer loop does use an enum to figure out what it should do. On the off chance that the queue was mistakenly running the default (blank) case, I stuck a message box in there to warn it was being accessed. No message comes up so there is no indication that it is running the queues at all. The program doesn't hang when it should be running a queue. It just doesn't do what it should. ANy help would be greatly appreciated.

rossu wrote:
Thanks for the replies. The answer is a bit bizarre, but might be useful to know. Apparently, in some of the cases in the event structure (producer loop), the Boolean value that gets wired to the stop control in the surrounding while loop was missing. In the Labview environment,this didn't cause a problem (default value?), but in the application it did. Making sure they were all fixed made the issue go away. Interestingly, which events were missing the Boolean and what didn't function were not correlated. The program never got hung in the event loop I.e. the interface didn't freeze.
This does not make any sense either. There should be no difference between development and build. Most of my output tunnels of event structures are only wired in the non-default situations. I suspect there was maybe some corruption and changing the tunnels forced a recompile, clearing things up. No way to really tell.
LabVIEW Champion . Do more with less code and in less time .

Create uninstaller exe with application builder

Hi!
Im using LabVIEW 8.5. I have created an application with the app. builder, it works fine, also an installer.
But I need an UNINSTALLER, like Uninstall.exe to be created also.
I have found a NI doc, which says:
"The Create Uninstaller option was removed from the
Advanced Installer Settings dialog box because the Application
Builder always creates an uninstaller"
But where can I find it?
im able to uninstall my app, using the Windows add/remove softwares option, but i need an exe.
Can you help me?
Thanks:
Waszil

Since the installer is based on Microsoft technology and the Microsoft standard is to only have the Add/Remove option, you cannot create an uninstall.exe with LabVIEW. I'm not even sure why would would need to if everything works with Add/Remove Programs and that is what everyone is used to now. In any case, there are probably some commercial installer packages available that still support the old technology.

Problem with "Application Builder"

Hello!
I have problem when I am using application builder to convert my program to exe files. MY PROGRAM: I use a main program to copy a template VI in to other VI´s, and then I can execute the copied VI´s from main. When I have tried to convert my program to a EXE file, everything works but not executing the copied VI. The following error messages apperies when I try to execute the copied VI. What does this mean???
BR
Kristian K
Attachments:
error.jpg ‏152 KB

Hello!
Information for users on this discussion forum: the problem was due to 'Build Text' function and when that function was removed the program worked fine. The functionality in the 'Build Text' function could easily be replaced by the 'Format Into String' function.
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

Exe with Application Builder

"Can Application Builder build *one executable* which consists of a constantly
running instrument VI and a VI which is periodically executed from a remote host
through the Labview HTTP Server. Both of which normally share data through a global variable VI".

I believe so. What you will need to do is build just one application. The deal is that you cannot share data across different applications but different VIs within the same application is fine.

VIs from LabView libraries not found in .exe built with Application Builder

I have added VIs that are called by reference to the dynamic vi list in the App Builder, but some of them fail to run because of sub VIs that aren't found at runtime.
These sub VIs are from the standard LabView libraries. For example: "Open/Create/Replace file.vi", "Write Key (I32).vi", "Open File+.vi" and "Read File+ (string).vi". Also, a typedef "ADC.flx.ctl" can't be found(from the Motion CustomControls library).
Even if I have those VIs open when I compile all of my VIs (using Ctrl-Shift-Run), they can't be found when I run the executable.
Brian Smith
Advanced Light Source
Lawrence Berkeley National Laboratory

Are you running the executable on the development machine? If not, make sure that all the required drivers are installed on the target machine (i.e. NI-MOTION etc.).
The version of the LabVIEW Runtime Engine also has to be the same as the LabVIEW development version.
Under �Application Builder >> Target >> Build Options� make sure to choose �Single target file...�. This way all sub VIs will be compiled into the executable.
In LabVIEW 7.1 you can choose to �Disconnect type definitions�� under the �Application Settings� in Application Builder. Does it help to remove the checkmark?
Best regards,
Philip C.
Applications Engineer
National Instruments
www.ni.com/ask
- Philip Courtois, Thinkbot Solutions

How to build a DLL that has Pascal calling conventions with application builder?

Hi,
I'm researching for possible solution to one of our problems.
In one case, solution would be to build a DLL from LabView
code. This should be simple task, but the application that
is going to load the DLL requires that the functions in the
library are exported using Pascal calling conventions,
similar to the C/C++ example code below.
DWORD APPEXPORT far APPPASCAL function(char hexr[])
Could this be possible with LabView somehow? Or is it best just
to write the DLL with C/C++?
Thanks.

Thanks Wiebe.
I don't know whether I need pass string pointers or not. The example
I posted was from the manual of the program that will be using the DLL
I build with LabView. I only wanted to show with it the exported calling
convention needed. It seems that it actually confused my question rather
than clearing it.
Anyway, now I know that it's possible to declare the calling convention
when building the DLL. And it's always good to know that I might encounter
different pointer types on the way, this may actually save me from a lot of
debugging some day.

Problems with application builder

Hi,
I have a little problem to distribute my application.
When you install the program, a direct link to the program appears in Start
Button, but not the link with the "uninstall" program. To uninstall the
program is neccesary to go to Start->Settings->Control Panel->Add/Remove
programs, but this is a little inconvenient for a not-advanced user.
Thanks in advance,
Miguel.

This is where I would expect to see uninstall. All of MS Office, LabVIEW,
CVI, Acrobat, AutoCad, Visio, Internet Explorer, Visual Basic, etc., etc.,
are all uninstalled from the Add/Remove Programs. I think having uninstall
as a shortcut from the Start menu is a little dangerous as it's too easy
to select.
"Miguel" wrote:
>Hi,>>I have a little problem to distribute my application.>>When you install
the program, a direct link to the program appears in Start>Button, but not
the link with the "uninstall" program. To uninstall the>program is neccesary
to go to Start->Settings->Control Panel->Add/Remove>programs, but this is
a little inconvenient for a not-advanced user.>>Thanks in advance,>>Miguel.>>

Autonomy with application builder?

Similar Messages

Maybe you are looking for