LabVIEW application builder - Deep start menus

Hi, is it possible using the labVIEW application builder to create start
menu program groups that are more than one level deep, i.e.
Start\Programs\My App\Tools

Just for you to compare I have attached some screenshots of my setup. Maybe you find a difference.
Attachments:
App_Builder_Setup.gif ‏152 KB
App_Builder_Menu_example.gif ‏83 KB

Similar Messages

Is LabVIEW application builder needed for TS deployment?

Does the LabVIEW application builder need to be installed for TS deployment of a project containing LabVIEW VI's?

LabVIEW Application Builder is only necessary if you are deploying LabVIEW files, even then you can use the flag "Include without Processing Item or Dependencies" in all your LabVIEW files to create an image and optionally an installer without requiring LabVIEW (or app builder) at all; however, using this flag is not recommended becuase if you use it you would have to include all the files and their dependencies in your deployment manually (either by including the root directory of your test system or by adding all the files to your workspace) and you would have to make sure that they are not broken and can be called from the run-time engines you are including in your installer.

LabVIEW Application Builder Crash : ntdll.dll faulting module

Hello guys,
I'm currently experiencing problems while building my project (LV2012 (32 bits) , Windows 7). At the very end of application build, LabVIEW crashes with no explanation (Screenshot in french, sorry)
Windows error logging follows :
Event 1000 Application Error
Faulting application name LabVIEW.exe, version : 12.0.0.4024, time stamp : 0x4fea600e
Faulting module name : ntdll.dll, version : 6.1.7601.17725, time stamp : 0x4ec49b8f
Exception code : 0xc0000374
Fault offset : 0x000ce6c3
Faulting process id : 0x16fc
Faulting application start time : 0x01cda5350f41f87c
Faulting application path : C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id : 8e5b1344-1128-11e2-97d8-c0f8dae81bad
I had the same problem on LabVIEW 2011. I tried to build my application with another computer (also LV2012 32 bits and Windows 7 64 bits) and I do not have any error.
What is wrong with my computer?
For french people, topic in french
Thank you for your help,
Regards,
Quentin
Solved!
Go to Solution.

Solution found :
-Uninstall all NI products
-Clear registry keys related to LabVIEW
-Delete National Instruments directory into Application Data
-Reinstall LabVIEW

Using the LabView application builder

Hi.. I'm trying to build an application from my labview project and I want it to run it in a computer with no Labview installed. When I'm trying to run this Error shows up: Unable to locate the Labview Run-time engine. Is It possible to run my application in this computer? or definetily I have to install Labview on it in order to run it.
Thank you

You need to install the LV runtime engine corresponding to the LV version of the development environment.
This can be easily accomplished by creating an installer for the executable. Also an option in the project build menu.
Otherwise search the Ni website and download it.
Regards,
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Why does LabVIEW Application Builder 8.0.1 create an executable that will not run?

My VI runs perfectly. But when I generate the executable, it will not run. I get a "File Not Found" error. The file it can't find is "File Open+.VI" from vi.lib. I've tried copying File Open+.vi into my project. If still generates the same error.
Attachments:
OTS.zip ‏3105 KB

There error is coming out of FlowCal Server. You use the current VI path to build up the file paths. That works great in development but when you compile a VI into an exe, an extra layer is added. See this KB http://digital.ni.com/public.nsf/websearch/FD7DE8BC8FFC256C862565F4006BE363?OpenDocument
So when its an exe you need to strip the path one more time.

Where do I find the VISA installation drivers to add to my application builder for my LabVIEW app?

I need to add the VISA installation drivers to my LabVIEW application builder, but I don't know where to locate them. (I found the instructions on adding the drivers, but it didn't tell how to find them: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/e09ba0e2f31d304f86256a640070058e?OpenDoc ument)

The following webpage contains the NI VISA drivers that you can download:
http://digital.ni.com/softlib.nsf/display?ReadForm&lookup=NI-VISA&view=current&node=132060_US
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Application Builder and Corrupt VIs

Howdy All,
I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
(As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
All input is appreciated.
WG

Hi Robert,
For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
"Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
NI-488: Non-existent board."
As you can see, I meant "non-existent board". This error is very easy to reproduce - m
ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
Victrick

Application Builder is it faster?

Hello all.
I just finished doing the example "Building an Application" from the
Release Notes "LabVIEW Application Builder Version 5.1". After doing
the build procedure the application ran noticeably slower that when I
ran the demo program in labview. Did I miss doing something to the
app or a setting in the builder, I was hoping the app would run at
least as fast when run from LabView but not slower. The machine I am
running on is a Pentium 300 running NT.
Thanks in advance.
Regards,
Steve Drake

The Application Builder creates an executable program which is at least as
fast as the same program run in the programming environment, with a gain
speed ranging from 2% to 10% due to the removed debug code.
However, this is true if you use the same options (especially the ones below
the "Performance" tag) you used in the programming environment. To force
your program to use these options, you have to make a copy of your current
LabVIEW.ini file (from the LV installation directory), rename it like your
executable file (i.e. assuming your exe file is myprog.exe, rename the copy
as myprog.ini). Finally edit the file, that has the same structure as a
standard Windows INI file, and rename the section named [LabVIEW] as your
program (in our example [myprog]). Distr
ibute this file in the same
installation directory of the executable file. This will force your progam
to use the same settings you used when developing it.
Apart from this, the executable file is also a bit smaller in memory, since
it does not load the editor and the debugger. In low memory conditions, this
can provide an additional speed gain.
Regards,
Nicola Chiari
"Steve Drake" wrote in message
news:[email protected]..
> Hello all.
>
> I just finished doing the example "Building an Application" from the
> Release Notes "LabVIEW Application Builder Version 5.1". After doing
> the build procedure the application ran noticeably slower that when I
> ran the demo program in labview. Did I miss doing something to the
> app or a setting in the builder, I was hoping the app would run at
> least as fast when run from LabView but not slower. The machine I am
> running on is a Pentium 300 running NT.
>
> Thanks in advance.
>
> Regar
ds,
>
> Steve Drake

Problem modifying FPGA code in an Application Builder-based system

I've inherited a working test system which uses LabVIEW FPGA, LabVIEW, Application Builder, and third party tools. The FPGA module (a FlexRIO) is responsible for generating test signals to a DUT and acquiring DUT output data. The host LabVIEW code controls the FlexRIO and acquires the test data. Application Builder is used to convert the host LabVIEW code to a Windows DLL so that it can be in turn controlled by higher level data analysis software running on Windows.
All of this currently works, and we're using it on a daily basis to test production devices.
We need to modify the FPGA operation to change the way the tests operate. We've modified the the FPGA VI to operate as we need it to and rebuilt the FPGA code (resulting in a new bit file), but subsequent runs of the test stack do not show the change to the operation of the FPGA code (the signals it is generating look exactly the same as in the original, unmodified, VI). We've tried renaming, deleting, and moving the bit file, but operation of the system is always exactly the same, even when the bit file is named differently or not located in the expected directory. We can't seem to affect the behavior we get out of the FPGA. It seems like we're not rebuilding something correctly, or that the system somehow has a copy of the old bit file stored away some place that it's using instead of the desired bit file.
We've verified that the newly created bit file is different than the original bit file, so it appears that the FPGA build process is succeeeding. I see no errors from LabVIEW when I build the FPGA code.
Does a DLL-ized version of LabVIEW host code operate the same as the same VI run from within the LabVIEW environment? When the DLL loads the FlexRIO, does it do so from the same referenced file path (I have the "Open FPGA VI Reference" properties set to use the bitfile, and the "Run the FPGA VI" checkbox is checked). We've power-cycled the host PXIe chassis between software runs to make sure the configuration memory in the FlexRIO is cleared.
It seems highly suspicious that we see the FPGA come up and run even when the bit file has been renamed or moved from the directory indicated in the "Open FPGA VI Reference". I would think that the DLL would attempt to open that file, fail to find it, and trip some sort of error dialog. But this doesn't occur, the FPGA gets loaded normally, and the test system operates as if nothing had been touched.
Previous developers were able to make this build process work, but it seems we're missing some critical step needed to actually update the code that ends up running on the FPGA.
The system is LabVIEW 2012.

The FPGA build definition has the bitfile filename hardwired into it, so the name is constant across rebuilds of the FPGA code. So we always have the same bitfile name (and consequently if we're not careful about saving the old files, then the old bitfile will be overwritten by a new build).
I could try your suggestion about the alternate calling method, but I'm hesitant about changing a build process that was known to work. It seems to me that I'm somehow not building the software correctly, as if I don't understand something about the DLL build process that's keeping the new FPGA code from being used.
To reiterate, our build process is:
1) Modify the LabVIEW FPGA VI
2) "Run" the FPGA VI to compile it (by the way, last night we tried a "Rebuild" on the FPGA code from the right click menu off the VI in the LabVIEW project and that also has failed to change the results)
3) Build the host DLL code by right clicking the DLL build definition in the LabVIEW project and selecting Build
4) Copy the resulting host DLL over to the directory location where the higher level Windows software expects to find it
5) Run the higher level Windows software (at which point we view waveforms generated by the FlexRIO to see if the FPGA's behavior has changed).
We've verified that the LabVIEW DLL won't rebuild if we rename the bitfile (LabVIEW gives an error saying it can't find the bitfile). We've also verified that the higher level Windows software won't run if the LabVIEW DLL is renamed in its directory (so we know that that exact copy is being opened by the Windows software). Yet we can't seem to modify the FlexRIO's behavior through this process.

Run page with cleared cache after edit in application builder

When I am building a form and run into an error while submitting the page I get the following situation. After making some changes to the page I try to run it again but the values from the previous try are still in the cache. So I immediately run into the same error I had earlier. The only way around this, that I currently know of, is to select another page in the application builder and start this. Then I can navigate to the page I'm working on using the menu. I usually start pages from the menu with a cleared cache.
Is there an easier way to do this?
There are currently two "run" buttons in the application builder. There is the button that says "run" and there is the "traffic light". Maybe one of those can be used the run the page with a cleared cahche and the other one with the cache still intact.
Edited by: Rene W. on Dec 23, 2010 6:26 AM

Hi,
One of the parameters in the URL is for clearing cache:
f?p=App:Page:Session:Request:Debug:ClearCache:itemNames:itemValues:PrinterFriendly
so, you could just enter the page number into the 6th parameter to clear the cache for that page
Andy

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

Projects, application builder LV7/LV8

I realize that this is a general question so I'm hoping someone can just point me in the right direction.
I have been using LV8, but recently had to work on a cRIO application that was written in LV7. I was able to make the necessary changes and solve the problem but there were a few things that left me confused.
The LV7 application was as follows:
an FPGA program
a RT program
some windows .exe program that, when run, would download all the appropriate programs into the cRIO and run it.
In order to make changes to any of the programs, and have those changes "stick", I had to run the Application builder. Fortunately the previous developer left a profile that I could load, and everything worked, but before I found out about this, I struggled with getting the application builder to correctly assemble all the necessary files.
My question is, does there exist a tutorial on using the application builder? Does it include writing an application that will find the RT VI, the FPGA VI, and put them in correctly?
I am familiar with LV8 and I understand how to have the VIs loaded automatically (stored on the cRIO). I'm just not familiar with LV7.
Just looking for pointers and tips on using the application builder I guess.
Thanks
Jeff

Jeff,
Here are a few links that should help you out.
Creating Executables with the LabVIEW Application Builder - This is a general overview of the Application Builder (version 6.0 and 7.0)
http://zone.ni.com/devzone/conceptd.nsf/webmain/4ef810ee05bef63c86256bf30062ec31
Deploying and Launching a Real-Time Application - This is more specific to deploying a real time application
http://zone.ni.com/devzone/conceptd.nsf/webmain/9ac4955881bd7b4d86256d0b0061dd1c
Hope this helps,
Justin D.
National Instruments

Installer instal labview application as window service

Dear NI
I want to make an installer which installs labview application as windows service.
Currently i am using third party tool to do this. Is it possible with labview application builder.
regards

It should be possible also with installer builder. You should automate described steps (put some entries into the registry and call executable from MS ResKit). Resourse kit should be deployed with same installer (not sure if there "silent" install possible, otherwise read ResKit documentation and license agreement). Alternatively you can build installer with third party tool - in this case you will have more "freedom". In the past I have done this with Inno Setup - works without problems.
Andrey.

Application Builder are corrupted 4.1.1

Hi am having quite a few issues with users on Chrome AND IE has problem as well
I even had an issue.. this is an example
http://imgur.com/M3rjh6p
http://imgur.com/hTtZINd
Drop-downs seem to have text from other dropdowns?
Anyone have this issue?
maybe related to
APEX 4.1.1 patchset bug?
Not sure if its Chrome update.. or a recent patch to oracle database we did?
Dean
Edited by: Postie on Apr 26, 2013 12:35 PM
Edited by: Postie on Apr 26, 2013 4:22 PM

The NI ftp site contains a Application builder update for 4.0:
ftp://ftp.ni.com/support/labview/updates/windows/appbuild/lv4abud.zip with files dated 3-20-1996 (inside zip file).
From the README:
- File Descriptions -
lv4abud.zip:
LabVIEW Application Builder 4.0 update for LabVIEW 4.0
Windows 3.x/95/NT versions only
Disk 1 of 1
Copyright 1996 National Instruments Corporation
All rights reserved
Sorry, 4.0 is too old for me to remember much about such details, but I would just try to download and install this.
LabVIEW Champion . Do more with less code and in less time .

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

LabVIEW application builder - Deep start menus

Similar Messages

Maybe you are looking for