Run project without labview

[Raydem]

Hello,

I have the base version of Labview and I need to run the project on another computer without Labview. How can I do it? I remember that in old versions of labview I had the possibility of creating an .exe, but I read that this option is only available with the application builder. Is there another way to execute the project? I installed the Labview runtime on the other computer but it doesn't work.

Thanks

[ZYOng]

Unfortunately no. You would need to purchase a license for the Application Builder or a separate LabVIEW Base license.

[altenbach]

It depends on your license and your purpose of running it on another computer. For example if you have a "named user license", you are allowed to install LabVIEW on up to 3 computers as long as you are the only one using it.

In this case it is not an "exe". You would be running it in the development environment and would need to install LabVIEW on the other machine. I assume that since you only have "LabVIEW base", the installation would be relatively simple.

Details from here:

Named User License. If you have obtained a named user License, you may install the Software on up to
three (3) computers in a single workplace of one (1) individual you designate and register with NI ("Named
User").

So carefully check what kind of license you have and then read the relevant sections of the license agreement.

[WNM]

It can be done if you have a code-version compatible version of the runtime engine (RTE) installed on the target machine along with a complete set of all the VIs, controls & whatever that are used by the top-level VI. This includes everything that is pulled from LabVIEW libraries as well as any DLLs that those modules reference.  Assuming that you can pull this collection of files off, you'll still need to build (or acquire from some system where it can be built) a code-version compatible of a "launcher" VI executable.  This "launcher" executable is a small EXE, that when run, will prompt you for a path to the top-level VI to be run. If you give it a good path and if you have managed to collect together all its necessary supporting files into a common folder or LLB, then the top-level VI will start running just as if you had created an EXE from it.  This allows you to have one "launcher" EXE that can run any number of ordinary VIs on a target system.

 The launcher EXE can be built to remember (through an INI) the path last used to the target VI so it does not ask for it but once.  If launcher is setup to look for/use/create an INI file which shares the same name as the launcher, you can create multiple copies of the launcher EXE with different names and different VI targets that individually will run.

[Raydem]

OMG!!! Is there any tutorial for this?

[WNM · Accepted solution]

I don't know what version of LabVIEW it is that you are trying to use but here (attached) is a an example for LabVIEW 2014. 

[billko]

---

@WNM wrote:

It can be done if you have a code-version compatible version of the runtime engine (RTE) installed on the target machine along with a complete set of all the VIs, controls & whatever that are used by the top-level VI. This includes everything that is pulled from LabVIEW libraries as well as any DLLs that those modules reference.  Assuming that you can pull this collection of files off, you'll still need to build (or acquire from some system where it can be built) a code-version compatible of a "launcher" VI executable.  This "launcher" executable is a small EXE, that when run, will prompt you for a path to the top-level VI to be run. If you give it a good path and if you have managed to collect together all its necessary supporting files into a common folder or LLB, then the top-level VI will start running just as if you had created an EXE from it.  This allows you to have one "launcher" EXE that can run any number of ordinary VIs on a target system.

 The launcher EXE can be built to remember (through an INI) the path last used to the target VI so it does not ask for it but once.  If launcher is setup to look for/use/create an INI file which shares the same name as the launcher, you can create multiple copies of the launcher EXE with different names and different VI targets that individually will run.

---

While you showed that it is possible to do, I don't know what the legal ramifications are.

[Kyle97330 · Accepted solution]

What sort of project is this?

Is it for work?  School?  Personal use?

If it's for work\research\teaching then you can try the advice given but you probably ought to try convincing your management to buy a proper license.

If it's for personal use, or if it's for a school outside of a classroom setting and not for research/teaching, then look into the Community Edition of LabVIEW.  It's free for personal use and includes the application builder (it's basically the Professional edition with a different license).

[Raydem]

Thanks for your information.