Including a Pre-Built LLB in Application Builder 8.X

I have just recently updated some old code to 8.5.1. This code contains many dynamic calls to VIs located in pre-built LLBs (LLBs that were saved prior to application builder). This application is also compatible with a priority plug-in architecture. So when creating an application or installer in app builder 8.X, how does one include a LLB file? I do not wish to build it. I just want to include it the same way you may include a text file or someother type of source file. LLB files do not show up as individual files in the Project Manager.

AstroGlen wrote:
I would like to create an installer that uninstalls the previous version of software (which was written in 7.1.1). I am assuming it is necessary to make edits to the "registry" category in the installer properties. I am also assuming that I would need to enter the product code for my application. This is the code found in the 7.1.1 application builder \ installer settings \ Properties button. But i do not know the particulars of what needs to be done.
I think when you install an application created/built using a higher version of LV, it ll automatically overwrite any previous version(s) of that application installed in the target PC. We may not need it to be uninstalled manually. Did you try this?
- Partha
LabVIEW - Wires that catch bugs!

Similar Messages

Pre-built useful WDJ applications

Hi Everyone,
does SAP have any pre-built useful WDJ applications (SAP released many VC xApp Analytics applications)? If yes, how can I get my hands on these applications?
Thanks, Jin

Jin,
Follow [this link.|https://www.sdn.sap.com/irj/sdn/nw-ui]. Under Web Dynpro Java header, there are many Web Dynpro tutorials with pre-built projects available for download.
You can also follow [this link|Web Dynpro Java Tutorials and Samples NW 2004] to many Web Dynpro Java tutorials.
Hope this helps.
Vishwas.

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

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

Application Builder: Application closes after launcher

I'm trying to run the executable of my application that was built with the Application Builder. I am using actor framework and have a Launcher.vi that is set as the Startup VI and launches the parent actor. When I run the executable, I can see the Launcher.vi front panel open and close quickly, but the main front panel never opens. Where do I begin to debug my executable? Is there something obvious that I am forgetting to do? I have compared my application configuration to the Actor Framework example (which does produce a working executable) and can't find anything that is different.
Solved!
Go to Solution.

OK, I figured out it. I went back and looked closer at the launcher for the Actor Framework example and noticed that the Launch Actor VI block does not have "Open Actor Core front panel" set to true which I thought was strange because the front panel opens correctly for that application. I poked around in the VI properties for the example projects parent Actor Core.vi and saw that Window Appearance has a custom configuration. The options for Show front panel when called and Close afterwards if originally closed were checked in the example project but un-checked for my project. I also looked at the Execution settings and saw that the example is configured for Shared clone reentrant execution while my project is configured for Non-reentrant execution.
The Window Appearance change correctly launches my main front panel. I played with the Execution settings to see what those did and noticed that when my VI is configured for Non-reentrant execution, child actors don't seem to be getting launched. Additionally, the stop button on my front panel will close the front panel but the application is still running. Changing the mode to Shared clone launches child actors properly and completely closes the application when the stop button is pressed. I also tried Pre-allocated clone reentrancy to see what would happen; the launcher just errors out immediately saying the Call by Reference VI is not exectuable.
I guess that makes sense. Actor Framework expects that state is not maintained when an actor is destroyed, so shared clone ensures that each instance of a child actor is given its own memory pool to be cleared when the actor is stopped. http://zone.ni.com/reference/en-XX/help/371361J-01/lvconcepts/reentrancy/

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

Application builder error.llb

Hi all,
I'm using application builder to compile an executable of my VI. Compile runs without a hitch.
However, when I try to launch the .exe three subvis from error.llb are missing : Not Found Dialog.vi, Details Display Dialog.vi and Set String Value.vi
The compiled .exe seems to be looking for these VIs in instr.lib, which is nowhere to be found in the compile folder.
This happens even on my developpment machine, on which, of course, the VI runs fine from within LabView.
Did I miss something during the compiler setup ?
Thanks in advance for your help !
Nico
Solved!
Go to Solution.

I've had this before, and it was reported by NI as being a bug that comes from loading up a project that was built in an older version of LabVIEW and creating an application from it. For me it was loading a LV8.5 project into 8.6.
The only workaround was to add the three missing vi's to the project, and ensure they are added to the Always Included list within the application builder.
You will find these vi's in Program Files\National Instruments\LabVIEW 8.x\vi.lib\Utility\error.llb. Simply add them to your project somewhere, then in application builder made sure you select them as Always Included in the Source Files section, then rebuild your application.
Message Edited by Thoric on 03-13-2009 03:52 PM
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Can I include raw files into the installer folder with LV application builder?

Hello,
I have created a batch file that will run at the end of the installer, which will copy over some raw configuration files into the source destination so that the configuration files can be customized for each end user without rebuilding the installer with application builder. I also have an autorun.inf so the installer will automatically run when the user installs the CD.
However I would like to have some default configuration files and an autorun.inf file that will be automatically added to the installer "volume" folder using the application builder.
However I don't see a way to include raw files in the "volume" folder. It appears all source files in the application builder are embedded into the binary files.
Please let me know if this is possible with the current application builder.
Regards,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor

Russel,
i think this link might give you some good hints....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Do I have to build adapters to Oracle AIA for pre-built integrations?

Hello,
The way Oracle AIA provides pre-built integration packs for Siebel, SAP & other products - how do I develop such integrations for my application? Through AIA foundation packs or do I've to write an adapter to connect with Oracle AIA?
Thx, Amol.

There is a wizard in AIA that creates a few composites for you which follow the rules of the AIA-Specification. Then you can fill them with application-specific-code yourself.
Edited by: user10942884 on 25.06.2010 03:29

I w'd like to know if LabVIEW 6.0 Application Builder includes the daqdrv (for data acquisition) and serpdrv (for serial communication) support files by default.

Building an application to communicate to a device by serial port

Hi velou
The LabVIEW 6i Application Builder no longer requires daqdrv. Regardless of your Application Builder and LabVIEW version, you must always install the appropriate driver files on the target machine. For example, if your application communicates with a DAQ board and a GPIB board, then you must install NI-DAQ and NI-488.2 on your target machine. If you are using the VISA VI's for serial communication, than you have to install NI-VISA . If you are using the "old" serial VI's, than you have to include serpdrv separately.
Luca P.
Regards,
Luca

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

How to include another msi with LV application builder?

I can use LV application builder to create an installer for my application. But my application relies on a 3rd part msi, which should be run after my application is installed. So how to include this msi with LV app builder? Thanks in advance.

I would recommend executing a batch file that launches your other installers after your LabVIEW executable finishes installing. The process of doing this (in addition to other suggestions about including 3rd party installers) can be found in the Knowledgebase linked here.
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

Can visa runtime engine be included in application build?

I just installed my program on a new machine and it wouldn't work. Turned
out I needed to also install the visa runtime engine. Is there any way to
automatically include that in the application build?

I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
/Brian
Attachments:
screenshot 13-08-2007 17.57.JPG ‏95 KB

I would like to display the pause button in an executable built with the LabVIEW 6.0.2 application builder.

When we upgraded to LabVIEW 6.0.2 (Windows) the executables no longer had the pause button in them. This was a useful feature but I can't find an option to display this button in the Application Builder. Please let me know if this option has been removed and whether I need to allow for pauses to be built into the programming. Thanks.

A well designed application shouldn't need to be aborted the hard way but if you want this feature, you can enable it in the application builder settings.
Under the "VI Settings" tab, select your Top Level VI and press "Edit build settings...".
Change the item "User can abort VI" to "Yes".
LabVIEW, C'est LabVIEW

What information is included in .exe's built with App. Builder? e.g. PC name

I need to build an application (Windows XP executable) in LV 8.5.1 with Application Builder that is anonymous (not traceable).
Apart from the info entered in the Build spec dialog box, what potentially traceable information is contained within the executable?
I am thinking there might be LabView serial number(s), PC name, MAC address, processor serial number?
Thanks
MJC

Why would you think that information would be in there? Those items have nothing to do with an application.
What do you consider (besides what you've listed) to be non-anonymous?

Including a Pre-Built LLB in Application Builder 8.X

Similar Messages

Maybe you are looking for