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?

Similar Messages

Standalone applications in labview evaluation version

Can I make Standalone applications in labview 8.6 evaluation version??
Can this application work on other computers which do not have labview installed??

You cannot because in the evaluation copy there is no application builder.
Harold Timmis
[email protected]
Orlando,Fl
*Kudos always welcome

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?

Distribute application without labview run-time engine

I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
Solved!
Go to Solution.

Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
Attachments:
NI software.jpg ‏98 KB
Installer.jpg ‏216 KB

Strange current VI`s path returned in standalone application

I know that there is a difference in the path returned when using the "Current VIs path" in the development environment and in a standalone application, but this is not what I had expected: This is the path returned from the Current VIs path in the standalone application:
C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\rad.exe\RADHAZ-programmer\RADHAZ\rad.vi. Why is this the correct path to the VI?
If I strip this path once, and build a new path with the name of my dynamically called VI I get: C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\rad.exe\RADHAZ-programmer\RADHAZ\instr.vi. It starts from this path, but It won`t load some text-files located at C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds\kal-data without making changes to the instr.vi.
I tried to used the App.Dir property to find the correct top level directory, and it returns C:\LabView-programmer\RADHAZ-programmer\RADHAZ\builds as expected. But this is not the path that the dynamically called VI need.
Any suggestions is appreciated..
I searched for a detailed tutorial for setting up the build specification, but didn`t find any that helped much.
Gunnar
Solved!
Go to Solution.

HI Gunnar,
have you tried the last point of the Advanced AppBuild settings as described in the help?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Building standalone applications?

Hi !
I am trying to build standalone applications in LabView, and I wonder is
this possible?
I have the application builder in LabView 5.1 with Imaq 4.01.
-- Sincerely
Roger Ohlund, Engineering Physics F95
Lovsele 83, 930 10 Lovanger
Sweden
Tel. +46 0913 410 41, +46 070 33 33 543
mailto:[email protected]
mailto:[email protected]
http://www.acc.umu.se/~angler/

Bing,
From your previous posts it looks like you would like to download your FPGA VI to your cRIO modules and then have the application run at start up without the need of a PC to initiate the start. If this is what you are intending it is possible to download an FPGA VI to the Flash Memory of an FPGA Device. Instructions for this can be found by launching the Embedded Project Manager and selecting Help >> VI, Function, How to Help >> FPGA Module >> Running FPGA VIs >> Downloading FPGA to Flash Memory. This should work well if you are intending to run application as completely stand alone. Since there will be no communication with the host there would be no need for a Host Vi and the you would only need the FPGA vi to run the application.
Are you intending to create an application that will not communicate with a host PC or were you wanting to create and executable that you could distribute?
Steven
Applications Engineering
National Instruments

Is there a driver for NI Digital I/O cards for Venturcom RTX without LabView?

I'm looking for Digital I/O cards (PCI) for use with Venturcom RTX app (without LabView) and, since LabView RTX is based on Venturcom's RTX, I was hoping that NI might provide RTX drivers for their cards.

Dear Martin,
I have looked for information for PCI DIO drivers for use with the Venturcom RTX application without LabVIEW, unfortunately NI does not produce any RTX drivers for NI cards.
I would advise you to use register level programming, below is a link (even though it is for a PCI 6036):
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=5065000000080000000A320000&ECategory=Measurement+Hardware.Real-Time
Unfortunatley this is limited information.
Kind Regards
Louis Price
Applications Engineer
|National Instruments

Standalone application for data acquisition using NI DAQ card

I have made a standalone application in labview GUI for data acquisition and signal processing. if i have to run this application in any other computer what all softwares should be installed other than labview runtime engine...NI DEVICE DRIVER CD alone is to be installed or do i have to install any other software for data acquisition using NI daq card??
thanks and regards
Solved!
Go to Solution.

You should only need the run time engine, The device drivers for the device, maybe need VISA drivers if you are doing serial or something of that nature, You may need the channels or tasks created in NI measurements and automation if you created them there.
There may be other things that you will need depending on what you include in your code and what tool kits that you have installed.
Tim
Johnson Controls
Holland Michigan

Deploy simple Labview applications without installing the Labview runtime?

[Labview 8.21 - Windows XP]
Hello and a happy new year to all !
I have coded very simple Labview applications that basically read text files (exported from Ms Excel), make some string operations, array sorting and at the end write another text file that is then imported in Ms Access. Now I would like other people from the School parents association to use this application on their own PC but ideally without having to install the Labview run-time; for various reasons one of them being that they are not administrator of their PC, another reason being that I feel bad to ask them to install 100Mb of programs on their PC to execute my <1Mb applications. All that I can assume is that they have Excel and Access installed on their PC.
I have read some postings on the Forum and in the Knowledge base from which I understand that the only way to use my application without the Labview runtime is to build a shared library that maybe I could then link via a VBA code from inside Excel or Access. But I cannot find any usable example on how to do that practically. And maybe it is not possible.
What is the easiest way to run such very simple Labview compiled applications on a PC that does not have Labview installed? Is Labview not at all built for such use?
Thanks a lot for your help and ideas.
Christophe

You will need to have the runtime installed. There is a lot of other languages that also have the need for there own runtime, but they are commonly installed with the OS, so you don't realize it. Just building a dll won't solve this.
There might be a hack possible, though. People have managed to strip down the required installation and been able to deploy the required parts of the runtime only. If you want to go this way, search on LAVA. But I'm not sure if it works with LV 8.20, and you will need to invest some time to figure out the minimum requirements. But be aware that it is a hack, so it's on your own risk.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Why does it report missing *.dll when running standalone programs on a separate PC without LabVIEW?

I wrote a LabVIEW code to control GPIB, DAQ and Serial port. Then I built an installer including runtime engine. Everything works fine at the PC with the LabVIEW. I copy this installer folder to another computer without LabVIEW. I had no problem to install the program. But after I run the program, it started to ask for nilvaiu.dll. After I copied it under C\Windows\System32\, it started to ask for nimdbgu.dll, then niorbu.dll. Then it reported "The procedure entry point_pkgModulePackageEventLog@20 could not be located in the dynamic link library NIPALU.dll"
I guess it missed some drivers. So I installed NI-488.2 for Windows on the PC. But it did not solve the issue.

hi there
i recommend to update to DAQ 7.4. the performance is much better.
best regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Vision 8.2.1 and standalone applications

I recently upgraded to Vision 8.2.1 (still running LabVIEW 8.2), and subsequently modified a vision acquisition VI to take advantage of some of the new IMAQdx calls. The modified VI works fine, and the executable built from it works fine. However, I have rebuilt a standalone installer for this application, and after installing the app, a co-worker is unable to run it. The machine we're attempting to run it on does not have Labview installed, but we have purchased the license for standalone Vision applications for this machine, and it activates successfully during installation. Also, I have built the installer using the the 8.2.1 Vision RTE, so I know that's up-to-date. We were previously able to run the earlier version of the application built using Vision 8.2 on this machine with no problems. On the first attempt to run the new app, we received an error message indicating that niimaqdx.dll couldn't be found. So I located that dll on my machine and copied it over. Now, when we try to run the installed executable, a dialog box reports that several IMAQdx subVIs are missing. The exact message is:
"Missing subVI IMAQdx Discover Ethernet Cameras.vi in (my VI name here).vi
Missing subVI IMAQdx Enumerate Cameras.vi in (my VI name here).vi
Missing subVI IMAQdx Open Camera.vi in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI IMAQdx Get Image.vi in (my VI name here).vi
Missing subVI IMAQdx Unconfigure Acquisition.vi in (my VI name here).vi
Missing subVI IMAQdx Close Camera.vi in (my VI name here).vi"
Also reported missing are a couple of subVIs that I developed myself --- but only ones that have been added to the top-level VI since updating to Vision 8.2.1!
The project is composed of several layers of subVIs, and I can't post the project here. So, as a test, I made a simple dummy VI and project, which simply has a call to Discover Ethernet Cameras and a call to Enumerate Cameras. I then built an executable. I then built an installer. After installing to a PC without Labview, the resulting application has the same error. I've double-checked all my project settings, and they all seem ok. In fact, the settings haven't changed since my working version, with the exception of the "Additional Installers". The only changes there are the selection of "NI Vision Run-Time Engine 8.2.1" instead of 8.2.
Attached are the test VI and images of the error dialogs. I believe anyone can recreate this error by simply starting a new project, adding the attached VI (or any VI using IMAQdx calls), building an installer, then installing the application on a machine without Labview (you will need a licensed Vision run-time).
Any clues? I desperately need to resolve this issue, because the application in question is an important tool used by my co-worker. Hopefully, it's something simple that I'm overlooking.
Attachments:
test imaq.vi ‏8 KB
errors.JPG ‏38 KB

Ceger--
    The question is really what type of acquisition system you have. What type of camera and how is it connected to your computer. Since you didn't mention having a 1394, or firewire, camera or license, I am going to assume that you are using a plug-in frambrabber. The reason that I ask is that if you are using our hardware (i.e. a frambrabber) the cost of the license is included in the purchase. So you do not need to purchase a lincense for the IMAQ software, it's free, since you need a framegrabber to use it.
      On the other hand, if you have a Firewire or GigE camera that can plug directly into the computer then you have to purchase a license for this driver software, named IMAQdx.
   I can think of two possible reasons why you are getting the error, the first being that you have a framegrabber and so do not have a license for IMAQdx for the deployment computer. If you have a framegrabber you shouldn't need to use IMAQdx for any reason. The next being, since it is saying that so many of those files are missing, that you have not included IMAQdx into the installer. IMAQdx is separate from IMAQ and if you need to use IMAQdx then you need to include this into the installer.
      Please, let me know if any of this sounds like it could be what is going on and please post back with any questions so that we can get this figured out and get you back up and running!
Regards,
John H
Applications Engineer
National Instruments

Running a LabVIEW app on a MAC yosemite without LabVIEW

Hello all !
When you compile LabVIEW codes on a Mac, you create a ".app" instead of a ".exe". I would like to run my ".app" on another Mac running with Yosemite (OSX 10.10) and without LabVIEW on it.
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work ...
Has anyone already done such a thing and would have a method to follow ? :-)
Thank you in advance !
Solved!
Go to Solution.

gvanhoeke wrote:
When you compile LabVIEW codes on a Mac....
LabVIEW VIs are always compiled. You are probably talking about building a standalone executable.
gvanhoeke wrote:
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work
Instead of the "latest", you need the runtime engine that matches the LabVIEW version used to develop the program.
(Sorry, I have no direct experience with Macs)
LabVIEW Champion . Do more with less code and in less time .

Standalone application questions

Hi,
Question 1:
I have a data acquisition application using Labview. Four analog channels are recorded on HDD and displayed on waveform chart continuously.
Development application runs fine but standalone application on DELL laptop has problems: waveform does not show proper Grids; sometimes vertical and horizontal grid lines are broken. There is no problem recording data but only problem is displaying waveform.
The same standalone application used to run without any problem but after some minor modification, it behaves strange.
Any suggestions to fix the waveform display problems will be greatly appreciated.
Question 2:
�VI Property > Customize Windows Appearance > Show abort button� unchecked will disappear ABORT
button from VI. .After standalone application compilation and installation, the ABORT button was visible. How hide the ABORT button on the standalone application.
Question 3:
Can I replace Labview default RUN button with custom button, I want to hide Labview default RUN button and want to make a separate RUN button. Can I access property node or local variable of that RUN button?
Thanks in advance,
Kishor

About question 1.
I had some strange behaviour with charts and transparent backgrounds.
Perhaps it's something like this...
About question 2.
Perhaps you have made a build script that has the properties set. After
changing the VI, loading the build script might overwrite the VI settings.
About question 3.
You should modify the VI to wait for a button to be pressed (a while, 10 MS
wait, and a button). Let the VI start automatically (run when opened). This
has the same effect.
Regards,
Wiebe.
"Jeremy Braden" wrote in message
news:[email protected]..
> 1. The VI may have been corrupted after your minor changes. Do you
> have an old copy of the good code. You can also copy the block
> diagram of th
e bad VI to a new VI and build an executable from the new
> VI. Also do you see the same behavior with the classic waveform
> chart? What happens if you build a new LV executable with dummy
> information going to the chart?
> 2. The tests I ran showed that you can make the abort button
> invisible with the steps you mentioned. Do you think that you may
> have not saved your changes?
> 3. You cannot replace the run arrow. Atleast not from a nice
> integrated published solution sort of way. There are no properties
> for the run arrow.

How does the Labview based program apply to computer which without Labview

How does the Labview based program apply to computer which without Labview
student number：1110340001

SInce you list your "student number", you are probably using the student edition.
You cannot build standalone executables with the student edition.
You need LabVIEW professional. If you only have LabVIEW full, you need to purchase the application builder seperately.
LabVIEW Champion . Do more with less code and in less time .

Create installer without labview

Hi,
Is it possible to create an installer without LabVIEW? I am supporting Windows 2000 through 7 and the versions of NI software varies with each OS, specifically when dealing with oscilloscopes running Windows due to VISA conflicts.
The two main problems I have with creating installers with LabVIEW (Application Builder):
1) Windows 2000 requires the Product Framework before 2.8.0. This makes it impossible for installers to run on Windows 2000 that require product installation newer than 2.8.0 which is basically every installation for Windows 7.
2) As far as I am aware, the required software has to be installed on a local machine first before creating an installer. Then you navigate to the Additional Installers section when creating an installer to add to the installation. The location path will point to the orignal CD drive or location it was installed from on the local drive. I don't see why this required. Why can the installer be created directly from the extracted files without it being installed on machine?
Thanks
Solved!
Go to Solution.

Wow guys, thanks for two blatent insults. If you don't have anything nice to say don't say it at all.
A little further explaination:
Supporting and maintaining Windows 2000 in 2014, I agree, is cumbersome. However, you have to realize these oscilloscopes that run Windows 2000 in 2014 still cost upwards of $8,000 to replace and the operating system cannot be upgraded. Why do they still cost so much? Because they are very useful tools. And new ones cost $20,000 to $30,000. I don't think that this effort is "los[ing] [the company's] ability to make a profit".
For those of you that are interested in the orignal question posted here is my solution.
I used SFX Builder (http://sourceforge.net/projects/s-zipsfxbuilder/) to bundle NI's software into a single executeable file. Heres the steps:
1) Download all necessary NI software
2) Download SFX Builder
3) Download 7-zip (http://www.7-zip.org/)
1) Extract all NI software into a single folder and use 7-zip to compress into a .7z archive
2) Open SFX Builder and add the .7z archive to the File tab
3) You can easily set the path of extraction to anywhere on the computer, the temp (%temp%) is the most useful
4) On the Tasks tab click the add/plus button and select Run Program, then enter the path where the extraction happened, here is an example
5) Easy peasy!

Standalone application without labview ?

Similar Messages

Maybe you are looking for