Client view vi webpage without needing run time engine

I am trying to create a environmental webpage attached to a Labview vi where end user can browse the web page from their home computer internet. Problem is I read that the end user need to have the Run Time Engine installed in their computers, now this sucks. If the end users need to remember to install run time engine to every computer their visit, there will no business. Is there someway to bypass this?
http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_html_documents_an/
"If you want clients who do not have LabVIEW installed to view and control a front panel remotely, they must install the LabVIEW Run-Time Engine, then view the front panel remotely."
Solved!
Go to Solution.

Hi sunflower2772,
if you want to use the NI function of webserver, then you have to install the runtime engine (there is also a smaller one), the same as using some JAVA code.
If you don't want to do this, then you have to write your own webserver.
Mike

Similar Messages

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

Can labview export shared libaray use in C++ without run-time engine?

Hi, everyone
Now, I write a VI for a algorithm and export it as a dll. I use the dll in my C++ apps. It is good. But I want to know how my apps can run without labview run-time engine or I must install run-time engine?

you can install run time engine or include dll which will be used by your application.

How can I uninstall Labview run time engine from the machine?

I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
Can anyone suggest solution to my problem?
Thanks,
Chander

J-Tek,
I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

You may not need to install the Run Time Engine...

I know this has been mentioned before, but after a long search of the archives, I couldn't find the right person to give credit to - sorry!
If you have a simple exe, you may not need to install the runtime engine on the target machine at all - all you need to do is include some of the engine's files with the exe for it to work. Try it out: copy the following files & folders into the folder containing your exe:
..\National Instruments\shared\nicontdt.dll
..\National Instruments\shared\nicont.dll
..\National Instruments\shared\LabVIEW Run-Time\your_version\everything (including all sub-directories)
so, using 6.1 as an example, you exe's directory would like something like:
..\AppDirectory\MyApp.exe
..\AppDirectory\MyApp.ini
..\AppDirectory\My_Apps_DLLs,if_any
..\AppDirectory\nicontdt.dll
..\AppDirectory\nicont.dll
..\AppDirectory\lvapp.rsc
..\AppDirectory\lvjpeg.dll
..\AppDirectory\lvpng.dll
..\AppDirectory\lvrt.dll
..\AppDirectory\mesa.dll
..\AppDirectory\serpdrv
..\AppDirectory\models\heaps_of_stuff_in_here
..\AppDirectory\errors\more_stuff_in_here
..\AppDirectory\script\and_some_bits_in_here_too
Take all of this data to a machine without LabVIEW or the runtime installed, and try to run the exe - all going well, it will execute without any problems. This exe distribution method can be really useful, especially when distributing autorun presentations on CD-ROMs.
* DISCLAIMER: as far as I am aware, this method is NOT authorised or supported by NI - use it at your own risk!
cheers,
Christopher
PS: I'd like your feedback: please give this posting a rating
Christopher G. Relf
[email protected]
Int'l Voicemail & Fax: +61 2 8080 8132
Aust Voicemail & Fax: (02) 8080 8132
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but
not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Yes, this method is not supported. However, this method is good if you wish to write your own installer for a LabVIEW Application. (Note: The method above does not install DataSocket, NI-Reports, or any of the 3D Graph controls.)
I would still suggest running the LabVIEW Run-time Engine installer so that more than one application can use it.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Is there a way to install exe of a vi on an XP machine without LV run-time and not have to restart?

Hi,
I need to deploy an application that reads channels from a FP module for testing purposes. The problem is, I cannot restart the system I need to install this on because it is running critical control software which cannot be interrupted. The system does not have the labview run-time engine and I know installing this requires a restart of XP probably due to registering DLLs or something.
I'm using "Fieldpoint Network Read" to read from the module. The simple answer would be to simply install this on a machine on the same network that I can restart. However, I have no such luxury because I am connecting to the system in question over a long distance VPN connection and I need to be able to poll the data from the FP every 250ms which may be too much for the connection.
So basically, I need to find a way to read data from this FP in a manner similar to "FP Network Read" without restarting the system. Is there any way to do this with labview? Alternatively, I may be able to write this app using LabWindows since I know some software is already running on that machine programmed with that.
Solved!
Go to Solution.

The first thing I'd say is that a restart may not be necessary. I have in the past installed LabVIEW development environment and when asked I said I would restart later. Then I opened LabVIEW and started coding. I'm not sure what it thinks it needs to restart for but it may not be required.
The other thing I'd like to mention is that LabVIEW 7.1 and older can run EXEs without needing to install a run time engine. So it is possible to build a EXE in 7.1, then include some files and DLLs in the same directory as the EXE, and when it is ran it will use them. There's probably issues with talking to DAQ devices without MAX and I have no idea how you address this but it is another possibility.
Of course you already know the best answer and that is to reboot the system when most convenient.
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.

Does Vision Development Module obviate the need for the Vision Run Time Engine?

I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated. In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons). Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs. I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers. I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine). Does this mean the engine is already installed and ready to run compiled applications? Or do we need to pay for the engine on each computer?

The Development module includes the RTE for that machine.
For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Unable to locate labview run time engine (lab view 8.5)

Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe I have the following error message:
Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
What I'm missing??
Thanks
Maurizio

are there one other reasons why it would not work. I have asimilar problem.
I intsalled version 8 of run time engine and acrtivated software. Now I am trying to run compiled application provided to me by third party.
When I click on application it says
Unable to locate LV run time engine
Test server requires a version 6.0 or compatible LV engine.
How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

LV8 without run-time engine?

I am using a LabVIEW 8.0 development system. I built a project and want to build a installation build to install the application. However, when I tried to add Labview 8.0 run-time engine to the installation build (In BuildSpecification->Additional Installers), Labview prompts me that my machine does NOT have a Labview 8.0 run-time enine, and the selection for NI Labview 8.0 run-time engine is RED!
How could this be possible? I have a Labview 8.0 development system, and labview tells me that I don't have Labview 8.0 run-time engine? What's the reason for that?

Hi Lylee,
This can occur when the project and build spec are created on a different machine with a slightly different version of the runtime. You should have another 8.0 runtime listed under the additional installers that is not red. You can then uncheck the "red" 8.0 runtime and check the normal one. The reason the one you have checked now if red is because that is the version the build spec is looking for but it does not exist on the system.
For example, if I make a project and build spec that had DAQmx checked as an additional installer, then opened the project on a machine that did not have DAQmx installed, DAQmx would still be checked and listed under additional installers but it would be red.
If you do discover that somehow your system does not have the Run-Time Engine installed, you can download those here.
David_B
Applications Engineer
National Instruments

Necessity of a run time engine

Can anyone tell me whats the detailed concept behind the necessity of installing the labview run time engine along with a labview application to make it work?
veena.

"Veena" wrote in message
news:[email protected]..
> What i wanted to know was what does a run time engine exactly does and
> whats its necessity? I havent explored the versions compatibility
> parts...am new to labview and exploring various things theoretically
> and practically, since I cant find a particular place or book that
> gives a overall view, and theres only manuals available for now...
> Veena
I'm taking a guess here, Labview is an interpreted language and that means
it needs something to convert the labview code into machine instructions,
the converter is the Labview runtime engine.
I think even if you create a *.exe file you need the runtime engine to run
it. I don't have the full d
evelopment version though so don't quote me on
that.
If you look in the help index for run-time engine you will find this answer
"Using the LabVIEW Run-Time Engine
If you create a system using LabVIEW that runs applications or shared
libraries, then you must install the LabVIEW Run-Time Engine. The LabVIEW
Run-Time Engine includes the libraries and other files necessary to execute
LabVIEW-built applications and shared libraries. All client computers
running LabVIEW-built applications and shared libraries must also have the
LabVIEW Run-Time Engine installed.
The LabVIEW Run-Time Engine also includes a browser plug-in that allows
clients to view and control VI front panels remotely using a browser.
All applications and shared libraries built with a particular version of
LabVIEW will share the same LabVIEW Run-Time Engine installation, so only
one installation is required. If you use applications or shared libraries
that you create with different versions of LabVIEW (for example, 5.1,
6.0,
and so on), you must have the Run-Time Engine for each version of LabVIEW
installed on the system.
You can find an installer for the LabVIEW Run-Time Engine on your LabVIEW
CD. "

NI LabVIEW Run-Time Engine + TCP/IP

Hello, Anybody knows how to activate TCP/IP service on PC with standard NI LabView Run-Time Engine installed. If I trying communicate with server from my PC (LVRTE) its works correctly. However, when I am trying interchange client and server applications it appears with error 1. Probably I need to add some settings to *.ini files on PC with LVRTE? --- Alex

<Alex> wrote:
Client/Server applications are communicate via standard TCP/IP VIs. I have tried to add 3 line as you wrote to server.ini, but it's didn't help
As I indicated, the lines are only applicable to using the VI Server. You had not indicated whether you were using the VI Server or just the TCP/IP VIs. At this point we need a better explanation of what you're doing. Specifically:
What does this: "If I trying communicate with server from my PC (LVRTE) its works correctly." mean? What is the "server"? What's it running? What do you mean by your "PC (LVRTE)"?
What does this: "However, when I am trying interchange client and server applications it appears with error 1" mean? What is the "interchange client" and the "server applications". Reading this implies you have more than one application running on the "server", whatever that is.
Seeing some code wouldn't hurt either.

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Is it possible to choose the serial port if only the run time engine is installed

I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
the different ports. Any suggestions?

Hi Daniel,
Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
I have attached a Small VI to Illustrate this.
Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
I hope this Answers your Q!
Good Luck
Mache
Good Luck!
Mache
Attachments:
Serial_Port_Select.vi ‏36 KB

Why does my LabVIEW 2010 Program ask for the LabVIEW 8.5.1 run-time engine every time it is launched after being installed?

It is a simple timer program that shows the elapsed time (see attached pics). I can't think of a single thing that should be causing this ... It started happening right after I selected scale objects with front panel resizes and recompiled, and re-installed the app. It was not happening before that when installed without the selection of resizing, but then I removed the selection and it still happens. Any Ideas would be appreciated.
Solved!
Go to Solution.
Attachments:
Timer Block Diagram.JPG ‏100 KB
Timer Front Panel.JPG ‏34 KB

A bit more info:
If I cancel through all of the dialog boxes (see attached) when trying to launch my little app, it runs normally. Looks like it really doesn't need the 8.5.1 engine after all.
Attachments:
Run-time Engine 8.5.1 dialog box.JPG ‏25 KB
Run-time Engine 8.5.1 dialog box - 1.JPG ‏15 KB

Client view vi webpage without needing run time engine

Similar Messages

Maybe you are looking for