Building Application Without Distributing Polymorphic VIs

Hi all,
We're currently deploying several LabVIEW applications that use polymorphic VIs. I have no problem building these applications (apart from one known issue with LV8.6.1 and a bad dsoffset error - so we use LV2010 for that app).
My issue arises with the deployment of these systems. At present, the polymorhpic VIs are copied to relevant subdirectories and deployed as they stand. To my mind, this is messy. It would be better if they were packaged inside the executable.
I'm sure one of the Application Builder controls allows this, but it's not obvious how to do it. The manuals don't seem to tell me much more than the online help, either.
Any tips?
Regards,
Geoff
Geoff Field, BE, CLAD, MIEAust
Professional geek, amateur stage-levelling gauge
Solved!
Go to Solution.

Thanks Tst.
Of course! It was the compatibility mode flag.
Mike: The clue was that I was working mostly in LV8.6. When using Application Builder with LV 8.6, any polymorphic VIs are packaged separately to the EXE file, as extra files in subdirectories under the EXE's directory. Thus, you might have:
EXE
Module1
Polymorphic VI1
Polymorphic VI2
Module2
Polymorphic VI1
Polymorphic VI2
etc.
Under LV2010, of course, the EXE packaging deals with polymorphic VIs a lot more cleanly.
Regards,
Geoff
Geoff Field, BE, CLAD, MIEAust
Professional geek, amateur stage-levelling gauge

Similar Messages

Building application with microsoft agent

Can someone clarify if there is anything different that needs to be done while building a stand-alone application that includes VIs that use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI VIs? I have been able to build applications with only CGI VIs but failed while adding MS agent VI functionality. Any help is greatly appreciated.
-Sheela

"Belur" wrote in message
news:[email protected]..
> Can someone clarify if there is anything different that needs to be
> done while building a stand-alone application that includes VIs that
> use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI
> VIs? I have been able to build applications with only CGI VIs but
> failed while adding MS agent VI functionality. Any help is greatly
> appreciated.
>
You'll need to install the Microsoft Agent parts on the target computer.
They are:
MSAgent.exe - the core components
actcnc.exe - MS Speech Recognition Engine
tv_enua.exe - MS Text To Speech engine
Merlin.exe - or any of the available different voices
Theses are available for downl
oad from
http://www.microsoft.com/msagent/downloads.htm

How can i include Polymorphic VIs while building an executable?

Hi,
am trying include polymorphic Vis while building a stand alone application. It is giving me error. If i use instances of the polymorphic VI instead of using it as library, i am able to build application. is there any way to use the library directly in the process of building stand alone application. Am using LabVIEW 8.0
Thanks
Anil

What are the errors that you are getting? Polymorphic VIs should have no problem in a built application - it would be a major issue if they did because NI makes extensive use of polymorphic VIs in their driver code.
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

How build stand alone application without labview

I have main vi and contain the sub vi i need build stand alone application without labview
how build stand alone application without labview?
thank and regard

I assume that the poster means to run this on a computer without the development environment installed. That is what the app builder is for. Review Altenbach's post. This being said, there will need to be a runtime engine installed on the target PC. You can 'bundle' that with your build application and install it together, although I usually prefer Not to do that, and make that a seperate step because it is rather large, and if the target already has it, then it is wasted space. Speaking of run time engine, I have seen negative reactions to it by my customers, but after sitting down and explaining that, with few exceptions, every application requires a run time engine. It is just that some are bundled with windows, or installed through windows update. Once explained, it usually quiets the opposition. [Paul steps off soap box now]
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

Using two different VISA functions on build application

Hello
I have developed an application that communicates with instruments.
One instrument is GPIB, and my application communicates with this through a gateway, so Agilent VISA libraries are installed as primary, to perform this.
Another instrument is USB. When I build the application (.exe) the communication with this instrument is lost.
Does anybody know what is happening?
Thanks you all

Hi Ester,
When you build your executable, you may need to configure the serial port as part of yuor build.
Under "Build Application or Shared DLL", go into "Installer Settings", select "Advanced".
You may have to select "Serial Port Support" and /or "Port IO Support".
Then build.
Hope this helps.
-JLV-

Using external llb when building applications

I would like to be able to update the SubVI's that an executable uses, but am having problems editing them after installation of the build application.
I am using the option "Small target file with external file for SubVI's" in the application builder, but I don't seem to be able to open the VI's present in the external library ("data.llb") after installation. I get the error message "ressoruce not found", when trying to open the file in LabVIEW. Does anyone know what might be the problem.

Caveman wrote:
> I would like to be able to update the SubVI's that an executable uses,
> but am having problems editing them after installation of the build
> application.
>
> I am using the option "Small target file with external file for
> SubVI's" in the application builder, but I don't seem to be able to
> open the VI's present in the external library ("data.llb") after
> installation. I get the error message "ressoruce not found", when
> trying to open the file in LabVIEW. Does anyone know what might be the
> problem.
Those VIs get just as much stripped of their front panel and diagram
unless you specifiy not to do that in the VI settings in Application
Builder. Without front panel you can not load a VI in the LabVIEW
editor. It is only good for calling
by reference.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Cannot build application with labview 7.0

I had built application previously using labview 6.X while some of the V.I. are without block diagrams, but I couldn't do that any more with labview 7.0 as a error will be prompted, why is this happening & are there difference in application builder between labview 7.0 and previous version? Must I load those V.I. without block diagrams dynamically now ?

Unfortunately it is impossible to build application with newer version with VIs without block diagrams, which saved in oldest version.
from ni web site:
"National Instruments does not recommend saving VIs without block diagrams because LabVIEW needs the block diagram to recompile the VI after an upgrade. When you upgrade LabVIEW, you must find a version of the VI that includes its block diagram to recompile it. Such a version did exist before the block diagram was removed because it is impossible to create a new VI without a block diagram."
"Based on that information, it should be clear that once a VI is saved without diagrams:
You cannot open or run the VI on any other version of LabVIEW, older or newer."
More information:
http://digit
al.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/00a6bacda1c01a0786256b60006163e7?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/28c4cb0cf83e1a1d862566e2007a2a9c?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fee732f4b1541b9586256bf0006a78ca?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/0649a3350de20aa186256d91007b3d61?OpenDocument

Why does Build Application vi work in development environment but not in executable; error 1025

Hello,
I have an application ("A") that I am trying to build using another application ("BuildA").
I can create an application for A manually from its project using the Build Specification, and it works fine (A.exe).
Also, when I run BuildA.vi in the development environment it calls the "Build.vi" correctly and again builds application A.exe just fine.
Then, when I make BuildA an application (manually) and run BuildA.exe, I would expect it to also create A.exe just like BuildA.vi did in the development environment.
However, it fails with the error:
Code: 1025
Open VI Reference in NI_App_Builder_API.lvlib:Build (path).vi->BuildA.vi<APPEND>
VI Path: <b>C:\TEMP\AppBuild\BuildA\vi.lib\AppBuilder\BuildTarget.vi</b>
I noticed this thread , which looks like a similar problem, but no conclusion was reached.
Why does BuildA.vi work fine in the LabVIEW environment, but the application BuildA.exe does not work? All paths are hard-coded, so it shouldn't be a path issue.
Thanks,
-john
Solved!
Go to Solution.
Attachments:
AppBuild.zip ‏175 KB

Interesting code. I'm curious how you came to decide 324ms in your while loop, and 58 in the other, and then 5136ms at the end. In any case I suspect this has to do with this line of text in the help of the Build.vi.
If you plan to run a build specification on the LabVIEW Run-Time Engine, do not include the Build VI in any of the VIs for the build specification.
I don't fully know what this means but it might be why it isn't working.
The Build.vi opens all Context (application instances) and then looks for the one named "NI.LV.MxLvProvider". This I assume is a application instance NI uses to build applications. It then uses this and opens some other VIs in this instance for the building. The error you are getting is "Application Reference is invalid" meaning it couldn't find the NI.LV.MxLvProvider instance it needs to build. Again I believe this maybe because you are in a run-time environment and that instance doesn't exist there.
At the end of the day I'm guessing since Application Builder is not free, NI probably doesn't include it in the Run-Time engine, which is free. So you can't build the way you want. You could have and EXE running in the run-time open an instance in the development, then run your VI from there if you must make this an EXE. It maybe easier to just edit the BuildA.vi to have a "Run When Opened" so that you double click the VI and it runs which behaves like an EXE sorta.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Standalone application without labview ?

Hi
I am trying to build an .exe file using application builder in LabVIEW 7.0. Is it possible to build an application without labview dependency ? In short, I want something like an .exe file which will run on systems without labview. I know visual basic has this facility. Please let me know.
Thanks
Sridhar.
Kudos always welcome for helpful posts

"Maximus00" <[email protected]> wrote in message news:[email protected]..
> . . . I wanted an option where he can view my application without having
to install anything on his PC. Looks like that is not possible ? Am i right
?<br><br>Sridhar.
You are not right. It is possible. With LV 7.0 and previous versions (I
don't know if this still works for 7.1), the executable will run correctly
if lvrt.dll and the other support files are in the same directory. So you
could, for example, put your executable on a thumb drive. Copy all files
and folders in the C:\Program Files\National Instruments\shared\LabVIEW
Run-Time\7.0 directory to the thumb drive as well. Then your supervisor
could just run the program from the thumb drive without copying anything to
his computer. Or, if you want the drive back, he could copy the entire
contents to his drive without using an installer.
But this begs the question, if your supervisor is evaluating executables you
are creating in LabVIEW, what's the problem with installing LV Run-Time on
his computer?

Build application erroration Error 7

Could anyone kindly help me here, I have met "Error 7 occurred at Invoke Node in Dist Build App from LLB.vi->Dist Build App Image.vi->Build Application.vi" while I am using Labview 7.1 to build my exe installer for my customer. I encountered this error message twice during that process. The first time it when I launch build DLL and the second time is at build. After I press continue button, builder stops with no warning and error.
Thanks in advance
Willy

Hi Willy,
can you tell me if all of your VIs are made with the same LabVIEW Version 7.1 or is it possible that some were built in a previous version?
The Application Builder reads certain information from the VI in order to determine how to build the executable. Since there can be significant differences between two versions of LabVIEW, the build process may fail with an error similar to the one you mentioned.
You can convert your VIs to the most recent version by using the Mass Compile featurel. The Mass Compile feature will allow you to select either a directory or a LabVIEW .llb file to compile.
Hope that helps,
Stefan Henke
NIG

Build Application Error

I am consistently getting an Error 26071 when I try to build my application to make an .EXE. I am usling LV6.1, and Application Builder for it. The app. works just fine from within LV itself. There are no errors.
Specifically, the error message is "Error 26071 occurred at Build Application.vi >> Dist Call Create Installer.vi >> Win Install Create.vi >> Win Install Add Files.vi >> MSI DK Add Shortcut.vi", with possible reasons stated as "Windows GetCommError: The hex value if the code us x65D7".
This code used to build just fine before I added some code using the Winevent.llb library, retrieved from NI. I had done a mass recompile on it and my code, just in case there was LV version compatibility issues. I also copied the specific vi's from Winevent into my library and did another mass compile, to no avail. I am using VISA serial port vi's (the GetCommError made me think this might be related).
Any ideas on what I'm doing wrong or what I'm missing?
Jeff

Check out this knowledge base here and let me know if that helps solve your issue.
Tyler H.
National Instruments

Problem in build application

I build application (exe ) for my main VI but there is main problem if run my main VI in another PC without labview there is problem see figure for explain may problem
Attachments:
Mohammad 1.doc ‏552 KB
moh.doc ‏212 KB

Creation of an installer will only help you when the "hpe363xa,
nidmm ,niswitch" drivers are also included.
Beside an installer you could also install the drivers manually in the PC containing only the LV run-time.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Open a different vi than the startup vi from a build application in LV2009

When building an application (exe file), I have to select a vi as "statup vi" in the build specification. This vi opens its front panel and executes when I execute the application.
But I can still open the front panel of other vis by using a command line argument:
myapp.exe "myvi.vi
The startup vi still opens and runs, and the vi "myvi.vi" opens its front panel as well. That was before LV2009.
Since I upgraded from LV8.5 to LV2009, my shortcuts do not seem to work anymore. I also tried using a longer path with the new LV2009 exe structure:
myapp.exe "subdirectory\myvi.vi" since the vi is in a subdirectory. It does not work either.
1-How can I open a vi when launching a build application, like it was possible before LV2009
2-How can I (Why can I not) use the File/Open... menu item of a front panel window to open a vi that resides in side the build executable?
Thanks for any help.

Thanks Norbert for (incredibly) fast reply.
Well: in the advanced page of the build specification, we still see
the option "pass all command line arguments to application". If
disabled, only the arguments after "--" (two hyphen) are passed to the application
itself (according to the help for this dialog window). So I assume that the arguments before the two hyphens are interpreted by the runtime engine. In previous versions of LV putting a vi path (inside or outside of the exe) would open its front panel - even though doing a quick search I could not find documentation about this feature...
Is there any documentation about which arguments are
accepted by the runtime engine when the mentioned option is disabled?
Can we not give a vi that should open (anymore)?
Baptiste

How to build distribution package with Agilent VISA as primary

Hi everybody,
I build a distribution package under LW 8.0 in a PC(Agilent VISA is primary), then I install the distribution package in another PC.
But I found the distribution package install NI VISA as primary in another PC. So How could I make Agilent VISA as primary when I build Distribution Package?
Does anyone can help me?

TaoZ,
Does your application use both NI-VISA and Agilent VISA? NI-VISA is only functional as the primary VISA, so if you need to use both NI-VISA and Agilent VISA, Agilent VISA will need to be secondary. If you are using just Agilent VISA, then you should not need to install NI-VISA. If you already have NI-VISA installed on the system, then typically Agilent VISA will overwrite NI-VISA because they use higher version numbers than us, but this is not necessarily always the case. Which version of each driver are you working with?
National Instruments
Product Support Engineer

Building Application Without Distributing Polymorphic VIs

Similar Messages

Maybe you are looking for