Question on Labview 8.2 Standalone executable

Hi Fellows,
I have a question, I have created a standalone executable labview file of a vi created to test a circuit board I am working on. Whenever I open the executable file, the labview panel opens up running. Is there a way to create the executable file so that when opened initially, it does not run until I hit run on the labview panel? I don't want any voltage going to my circuit board until I hit run. Is it possible to do this? Since this is the only vi, it is also my startup vi.
Patrick

There is a bug in 8.2, that will prevent from still standing applications. The workaround is to build the application as debuggable and force it to wait on the debugger (be aware that the exe will be bigger).
But such a thing should be programmed in the application, IMHO.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

How to create a standalone executable in LabVIEW 2009 Professional Development System?

How to create a standalone executable in LabVIEW 2009 Professional Development System?
Solved!
Go to Solution.

This should help you out http://zone.ni.com/devzone/cda/tut/p/id/3303
Also remember that quick search with Google in many cases will be quicker than asking in this forum. I always use Google before I ask for help in any forum. It is much quicker
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Return Code of a Labview Standalone Executable

Does a standalone executable built with Labview return a RETURN CODE?
If yes, is there any way control the value of this RETURN CODE?

Hi,
In general, I would agree, but executables (.exe) can contain functions. For
example, create a Call Library Function, and type LabVIEW.exe in the Library
name... This is an executable, and does have functions, that do return
values.
It's just one big mess, dll's ocx, tbl, exe, com etc. (e.g. try browsing to
a dll when selecting a ActiveX automation reference, or selecting a ocx in a
Call Library Function... To use a protocol, the file need to have several
required functions, e.g. DllRegisterService for dll's). In general, a return
value it the value of the eax register (on processor level), but this cannot
be controlled in labview. So creating a LV dll is good advice.
Regards,
Wiebe.
"chadevans" wrote in message
news:50650000000500
[email protected]..
> No. Executables don't return anything. I would look into returning a
> value from a LabVIEW DLL instead of using an executable. LabVIEW
> DLL's can be created from Tools>>Build Application of Shared
> Library(DLL) function in LabVIEW 6.0 or later.
>
> See also
>
href="http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a
100753500/f46e8f2ba898c...

Standalone executables and dependencies in the Java World

I'm a very seasoned C/C++ developer who's just learning Java. I have this gnawing question that's bugging me. It's rather elementary but it requires someone with experience to answer it.
If I'm delivering a standalone executable (C/C++) to a Windows or Linux customer, it is possible to deliver simply a "*.exe" file (windows) or a Linux Executable file (Linux) which can be installed and run immediately with no dependencies not included in a typical installation. (although, on linux, if there is a gui involved, a typical default Linux install may be missing some dependencies for the gui )
But in the Java world, since the JRE is not necessarily included in a Standard Windows or Linux default installation, my customer would always have to install the JRE on their machine before they can run any code that I produce in Java ...correct? And there is no way to execute a jarfile as a standalone; it always must be executed by the JRE ("java -jar <jarfilename.jar> ) ...right? And if I were to code a new GUI application in Java on the Linux platform, it would have to be run via "java -jar <gui_jarfilename.jar> ...correct?

R2me2 wrote:
"Your questions cause me to suggest that you look into Java Web Start;"
No, this is exactly what I'm not asking. I mean really standalone ....as in the executable runs by itself without user having to install anything else* (via CD, web or anywhere). So I suppose the answer to my question is that NO, there's no such thing in the Java World and that whenever a java program is installed, it always has the JRE as a dependency and that the installation of a java executable is not complete until the JRE is installed.Not to sound like a noob but what were you expecting. Java runs on the JRE and that is what makes it portable as the JRE can be installed almost anywhere o.O
This is not the inconvenience that you are making it out to be. No user is gonna beef with you if they came to you asking for a java application to be installed and I most certainly have played the client role, having to download the latest JRE to run my bank applets. No so long as you provide the user with all the info they need like a link to JRE download etc you will be fine.. :)

A question about LabVIEW's instinct.

Hello guys:
I have a question about LabVIEW's nature.
Is LabVIEW a language that can realize the operation system(OS) ?
I feel LabVIEW can express my idea intuitively in my mind.
So LabVIEW can help me develop some program rapidly.
I think LabVIEW can do it.
How about your opinion?

Do you mean can LabView read your mind?
Not by itself, external hardware is required.
Jeff
"´^¤j®ü" wrote in message
news:3b05a593@newsgroups....
> Hello guys:
>
> I have a question about LabVIEW's nature.
> Is LabVIEW a language that can realize the operation system(OS) ?
> I feel LabVIEW can express my idea intuitively in my mind.
> So LabVIEW can help me develop some program rapidly.
>
> I think LabVIEW can do it.
>
> How about your opinion?
>
>
>
>

Difference between the standalone executable and an interpreted commond

In the last of this aricle the author mentioned two commonds, I am not exactly sure the meaning ,can anyone give a interpretation?
the article:
[http://www.javaworld.com/javaworld/jw-12-2000/jw-1229-traps.html?page=4]

On Windows when you start a command prompt, you are running a program called cmd.exe
When you type "dir" in command prompt cmd.exe itself does something. This is it "interpreting" your command.
If, however, you type "myprogram.exe" then cmd.exe looks for another program in a file called "myprogram.exe". If it doesn't it issues an error message. This is it (still) interpreting your command. If it does find it, however, it runs your program. That program is a "standalone executable".
The distinction becomes relevant when you consider a more complicated command like this:
myprogram.exe > myfile.txt
This instructs cmd.exe to run your program but send any of its output to a file. Your program doesn't know how to do that second part. That's up to the interpreter.
So if you use Java to launch your program it would make no sense to tell it to redirect in this way; you would have to launch cmd.exe and tell that to in turn run your program and do the redirect.

Questions about LabVIEW

Dear support team,
Could someone please respond to Eric's questions? Eric works at Bonneville Power Administration and they are gearing up for another major LabVIEW and DSC project. He may have LabVIEW 7 beta. I am on my way out of town for two weeks and won't have access to phone or email. Thanks!!
Tricia Lee
DSM Inland Northwest
[email protected]
"Pierce, Eric - TNCB-TPP-2"
05/01/2003 08:05 AM
To: [email protected]
cc:
Subject: The list of question i never sent
Sorry for the long delay, things have been very busy here with this new project. I have questions / concerns about the DSC, OPC and LOGOS; first here is our architecture.
We will have two servers running windows 2000 server. Both servers will be live and need to have all DSC components installed. One server is to act as the primary server and the second is to act as a failover server. We have custom components that manage all of our custom services, if one of the custom services stops responding the failover service will shut down all custom services on the primary server and start all of the custom services on the secondary server, thus, the secondary server becomes our primary live server.
My understanding is that we will have to load a *.spf file on each HMI that tells the HMI where the server is, at the same time we need to initialize the DSC and OPC with *spf and *.lpd files. Now I might have the file extensions wrong but the idea is the same. We have all of our data in a SQL 2000 database, how do we make sure that all of the configuration files match the SQL 2000 db? We have several GUI's that can edit the SQL 2000 data, how do we update the DSC / OPC configuration files?
So in short here are my current questions:
How can we manage failover with two live servers
How can we ensure that DSC / OPC / Logos configuration files match the data in SQL 2000?
Does any of this make sense? This labview stuff is very new to me.
Eric Pierce
ACS Group, Inc.
Sr. Software Engineer
w. (360) 619-6284

Hi Eric,
You got it right that once the primary machine goes down, the standby machine detects this, and then loads the appropriate SCF file, etc. Caveat: This would mean however that the hardware in question is accessible by both the machines (it's on an Ethernet, for instance). Any hardware physically connected to the primary machine will obviously be not accessible by the secondary (unless there's a way to have a "Y" connection).
The logging part you mention is not very clear to me. Several questions come to mind: Isn't DSC the logger, logging to its Citadel database? Or, is SQL 2000 the main database? And DSC is logging to SQL 2000? If yes, how? Or is the SQL 2000 querying Citadel and hence getting the data into itself?
Regards,
Khalid

Vi works in LabVIEW, but not when executed by TestStand.

Hi everybody. I'm using LabVIEW 8 with the Sound and Vibration
Toolkit, and TestStand2. I am planning on using TestStand to
execute a series of performance tests on an audio processing
board. When run independently, the vi (which I have attached
here) runs correctly, and returns a value for the parameter being
tested. In this case it is SNR.
However, when executed by TestStand, the vi seems to run correctly, but
returns a value of "NaN". This causes TestStand to fail the test.
Does anybody know what is going on here? I've checked FAQs and
help files, etc... Why would the vi work on its own but not in
TestStand?
Thanks.
Brett Gildersleeve
Attachments:
SingleChannelSNR.vi ‏173 KB
Test Sequence.seq ‏15 KB

Hi Ray, Thanks for the reply.
Basically, when I run the VI on its own, I see the SNR value appearing
both in the SNR indicator and in the Test Data Out cluster under
Numeric Measurement. The rest of the indicators are empty
(string, report text, status, code, source). My waveform graph
shows an FFT of the signal.
However, when running the exact same VI through TestStand, I get NaN as
the output. The FFT of the signal is NOT displayed in the
waveform graph... strange. No errors are received.
In order to make it easier to debug, I replaced all of the analysis functions
with functions included in LabVIEW 8. Now everybody should be
able to run it. I do a simple THD test this time around. With the VI running
on its own, I get a value of 1.8 as the THD and the Numeric Measurement of Test Data
Out. However, whenever running the test with TestStand, I get a
value of NaN.
Same problem.
Any suggestions?
By the way, what exactly do you mean by "wiring
up the Error cluster and feed in to the Error Out."? I'd
like to try it out, but I'm not sure exactly what you mean. I
already have the Error out cluster wired up, I think.
Message Edited by TheSleeve on 05-22-2006 12:12 PM
Attachments:
SingleChannelTHD.vi ‏159 KB
Test Sequence2.seq ‏15 KB

Error in Calling a dll built in labview from Matlab standalone

hello,
The problem I encountered is in the use of the math interface toolkit. I
created a dll which performs data fitting using a labview vi which i converted into a dll using the
math interface toolkit.
This dll is then called from a standalone matlab program. It works fine in the computer where I
create the matlab standalone program and labview dll. Howerver when i export to another
computer the matlab part runs fine but an error is reported when it tries to
call the labview created dll.
"One or more output arguments not assigned during call Parfit.dll"
The files related to this problem in the math interface toolkit (the labview vi, the corresponding dll and the matlab .m and .fig files and the standalone exe are in the attachment and named MathITproblem.zip
The matlab run time engine(for matlab 7) and labview runtime engine(ver 7.1) must be installed for this matlab file to run. the run time engines are downloadable from the web.
Does any one know the source of this error or encountered it before?
thanks
Attachments:
MathITproblem.zip ‏1263 KB

Hi Srinivas,
Just another note, I noticed that the Math Interface Toolkit version (MIT) 1.0 is not compatible with LabVIEW 7.1. You’ll need version 1.0.1. of the MIT toolkit in order for it to work with LabVIEW 7.1.
The LabVIEW 7.0 lvanlys.dll is also attached. I had to rename it with a .txt extension, so you’ll want to delete the extension.
Kileen
Attachments:
lvanlys.dll.txt ‏516 KB

How to include LabVIEW Run-Time in executable file ?

Hello folks,
I have an application that need the user to simply calling executable file without setting up LabVIEW run-time because my executable file will be posted in LAN and anyone can run it remotely. What should I do? Any help very appreciate...
Thanks so much

You have to have labVIEW run-time installed on your computer in order to run a LabVIEW programs (vi or exe). What you can do when you distribute an exe file is to create an installer which lets you install LabVIEW run-time and create a menu item (in Windows) in the Start>>Programs menus. Then you can distribute the whole package and after running the installer, LabVIEW run time as well as the exe is installed.
You can do this in the installer settings of the Application builder (when you create the .exe file). Go to the "Advanced" section. There you can add the LabVIEW run-time Engine to the installer.
One other possibility you can do if several people want to use the programm over Lan is to use the LabVIEW webserver. You can run a programm somewhere on the
network and other people can open the front panel in their Webbrowser. But maybe that's not exactly what you want. ??

How to include external files when building installer for a standalone executable?

Hi,
I was trying to build a stand alone executable from my Labview project and I was able to do it successfully. Now I would like to include a few external .txt files in the installer. Those .txt files have parameters/constants that will be used by the program, and my program needs to load/read them when running. For now I have to manually copy/paste them into the target machine, but I really hope the installer can do it automatically. I see there is a "data" folder in the installer, and that's where I hope those .txt files can be added into.
How can I do it? Can anyone give me some suggestions? Thanks!
Rgds
Harry
Solved!
Go to Solution.

Norbert,
I could not find "Add file" when right clicking the project. See attached image please. Under "Project" I do have a "Add to project" but there is no option for external files. I did not find "Source" location either.
What did i do wrong? Is there any version requirement here? I have a 2010 base version. Thanks for your help.
Rgds,
Harry

Some questions on Labview under KDE4 and GNOME

I have some questions regarding KDE4 an GNOME with Labview for Linux. I'm trying to help a colleague get somethings working with regards to these desktop environments.
1. KDE4: When I try to open a VI directly through Dolphin (the default file manager under KDE4)..and the file (lets say ABCD.VI) is located in say /home/user/Test VI/ABCD.vi. When I double click, Labview starts and says that "/home/user/Test" is not a valid VI and it just errors out and refuses to open. It refuses to honor any whitespaces under KDE4 is what I've noticed. I haven't noticed this under KDE3.
2. GNOME: There are no icons for .vi files after installation, even though the desktop support for GNOME is installed during the install process.
Would appreciate some help!

Hi Anshul,
What version of Mandriva do you see this in? We only official test for and support a couple distributions (SUSE is only supported up to 10.3): http://digital.ni.com/public.nsf/websearch/35D2B5E483A001A18625716B005BE464?OpenDocument
Regards,
Jeremy_B
Applications Engineer
National Instruments

Another really easy one: Is there a way to compile a .vi and its dependencies into a standalone executable?

Hey, I'm using the Full Development System version 5.0.1, and I was wondering if I can take a VI and its dependencies and turn them into an executable which doesn't depend on Labview's being installed.
Or if not, what is the minimum amount of Labview that needs to be installed in order to run a .Vi?
Thanks,
-Dobbs

Use Application Builder to create an executable. I believe LV 5.0.1 is close to 5.1.1. You'd get a .exe file that you can distribute. Keep in mind that you need Run Time Engine installed in the machine that will run without the LabVIEW development system. I believe the run time engine is free. If you use the SQL toolkit, you'll need to get a run-time license for App Builder.
In LV 5.1.1, under Project menu, select "Build Application".
I'd generally build a single VI containing all the VIs but you can certainly link it to an external file. Both ways work.
Under "Top Level VI", you'd need to specify the Top Level VI if you want the VI to execute automatically. Otherwise, it'll prompt you to select a VI to run.
I hope that helps. Regards,
Shan Pin Koh
Systems Eng
ineer
Oakriver Technology

Questions on Labview 8.5 for Linux edition

Hi All,
I have some questions about LV 8.5 Linux edition:
1, Does it follow the GPL rules?
2, Which main distributions it supports?
3, Why I cannot download an evaluation edition?
Thanks.
David

DavidLee wrote:
Hi All,
I have some questions about LV 8.5 Linux edition:
1, Does it follow the GPL rules?
2, Which main distributions it supports?
3, Why I cannot download an evaluation edition?
Thanks.
David
1. LabVIEW is closed source and therefore the GPL does not apply to LabVIEW itself. It does make use of some external componanats that are under the GPL such as the kernel itself and the MESA library which is
2) look under www.ni.com/linux/support.htm#1. basically most recent RPM distributions should be fine but for non-RPM versions it installs reasonably well on recent systems. Got it to run on Ubuntu Feisty without real problems after installing RPM package support.
3) There isn't one. Since there is no license manager for non-Windows versions NI can not make an evaluation version that can be activated through a license key. This would require a separate build with reduced functionality to release as evaluation version, and the sales for LabVIEW for Linux do not justify that extra expense.
Rolf Kalbermatter
Message Edited by rolfk on 12-24-2007 10:01 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

OO question in LabVIEW example

Hello,
I am trying to learn OO and I have a question in the LabVIEW examples. See the attached image
What is the protected VI's? It looks like a collection of VIs with a type def. Isn't this a class? Why isn't it a class? What is going on?
Thanks

No image attached. Which example are you looking at?
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Question on Labview 8.2 Standalone executable

Similar Messages

Maybe you are looking for