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

Similar Messages

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.

Fatal Error in LV8.2 Run-Time Engine install

Hi,
We have a serious problem with installation of LV 8.2 Run-Time Engine (RTE).
When a Domain Administrator is trying to install the RTE, the installation stops with the following error (see RTEInstallFatalError.jpg):
In error message path 'mk' references to domain Administrator user name.
When a Local Administrator installs the RTE, there is no problem.
Any explanations or suggestions? It is a very heavy bug, if even the domain administrator cannot install the RTE and therefore use the application.
Thanks,
Wirer
Message Edited by Wirer on 04-04-2007 06:25 AM
Attachments:
RTEInstallFatalError.JPG ‏13 KB

Found a solution to the problem...
As the error indicates there is a problem with the user's profile folder 'My Documents'. Domain administrator did not have 'My Documents' in his profile. After creating such a folder there manually, RTE installation worked successfully.
So now the question rises: why RTE installation requires such a folder to exist? Nothing is installed there!
My opinion is that RTE installation needs to be much more reliable than it is currently. Professional developers who make commercial products using LabVIEW will have a lot of pain with the current solution.
1) Customization options for RTE are poor. I think that most of the companies that deploy their LV-made application want no extra stuff installed. If the developer knows that e.g. TDMS or NI-REPORTS are not used in his application, there should be an option to NOT install these with RTE!
2) There should be more documentation (by NI) on RTE installation and its error handling should be improved.
I hope more discussion on RTE.
Thanks,
Wirer
Message Edited by Wirer on 04-04-2007 08:48 AM

Run compiled application (LV 8.6) without run-time engine

Hi,
I just recently wrote a small 200KB program that performs simple calculations that I'd like to use on several different computers. The application works perfectly, but the problem is that I really don't want to go through the download/install/reboot process of installing the LabVIEW Run-time 8.6 software on every single computer (especially since downloading a 100MB file to run a 200KB program seems counter-intuitive). Is there a way to get the application to run without the engine? Previous searches resulted in old posts of people simply copying the engine files from the shared folder into the application directory, but that did not work when I tried it. Is this no longer possible on LV 8.6? I'll have no choice but to rewrite the application in a different programming language if LabVIEW isn't capable of running standalone compiled applications.
Thanks,
Anthony

I made the test with LV 8.6 on Windows.
I used a VI which does not need any drivers neither serial nor any other hardware execpt the graphics card.
I made an application from this VI on my normal development machine and checked that it will start and work as expected.
I setup a NI free partition with Win XP Prof. SP2. I have some non NI programs installed like a virus scanner, defragmentation tool, Adobe Reader, a drive imageing tool and WLAN drivers. The .NET Framework 2.0 is installed.
I copied the application and all files under National Instruments\shared\LabVIEW Run-Time\8.6 to the machine in a temporary folder.
I booted the machine into this partition. The application will start and work as expected. You do not need to make a complete runtime installation until you do not need any drivers.
The above mentioned folder has a size of about 64 MByte. Dependent on the application and desired languages you can remove parts of it.
Dennis,
during the various LV 8.x versions it was possible to do it as described above exepct one version, 8.2 I think, which needed an ini-File in the Windows folder.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

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

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

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

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

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

Building an Application in Windows to be used in Linux (with the Run-Time Engine)

Hi All,
I have an LabVIEW project I have developed in a Windows environment. I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment. The OS is openSUSE v10.3 (with GNOME). I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box? According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for Linux

The cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

I have trouble in building stand-alone application, "you must intall Labview run-time engine on any computer on which you want to run this application"

I have installed the LabVIEW 7.0 run time engine and checked all in the advanced setup on the installer setup slide. but I still get such a message saying that the target computer needs to have LabVIEW 7.0 run-time engine. What I want is a real stand-alone application even without having labview ... I used to think that's due to my program contains MATLAB nodes. But this is not true, since even without Matlab, it's still wrong. Please help, thanks!!!

As was stated elsewhere, you have the option of building the runtime engine into your application when you build it. However, you can also create a "runtime engine application" by simply opening the application builder and doing a build without adding any source code files. The result is a small program (named lvrt.exe) that can run any LabVIEW code--whether or not its built into an executable.
Such an application can be helpful if you are wanting to install several LV-based applications on the same computer in that it reduces the amount of redundant code on disk. All you have to do is make sure that Windows on the target computer associates the llb and vi file extensions with the runtime engine program.
It can also be helpful during testing to run test code that isn't built into an executable.
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

EXCEL Run Time Engine ?

I'm using one of the vi that ships w LV7.1. It basically reads in an EXCEL file. I'm also using the Report Generation ToolKit to write the final report data of the UUT. Do I need MS Excel installed on my target machine ?? Is there such a thing as a run time engine for Excel ?

As far as I know in the past excel is an activeX object which is installed with excel or office and is part of the licence, so I was under the impression that inorder to communicate with excel (ei through automation) you needed to install the application. HOWEVER, I was recently at a Microsoft developers event (included a session about office 2007 beta) which the speaker mentioned that this will nolonger be the case, you waill be able to automate both excel and work documents without having the application installed on the machine, but not powerpoint. This might have to do with the change in document formats from .doc and .xls to .docx and .xlsx. Essentially the new format will be a zipped XML marked up doccument with much more open format so the office suite in not as needed for automation (opening the way for much more programability and 3rd party software interactions). I could be wrong about needing to install office to get the office support to work for the report generation since I use LV 7.0 and OfficeXP.
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

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

LV8 without run-time engine?

Similar Messages

Maybe you are looking for