Runtime engine 8.6.1 on Labview 11
Hello,
I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it?
And if I downgrade to Labview 10, will i solve this issue??
Thanks in advance!!
This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
Sergey Kolbunov
CLA, CTD
Similar Messages
-
I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
"Installation aborted. Newer version already installed."
Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.
-
LV 6.0 runtime engine not found with labview 6.1
I recently upgraded to LabView 6.1.
Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
Shouldnt the 6.1 RTE be able to run older exe's?
I could find no solution searching this web site.
Thanks
Larry Junek, Certified LabVIEW DeveloperDid you install 6.1 wheer 6.0 was?
You may have lost the 6.0 RTE you did not realize you where using.
Yes you need the version of RTE that matches the app.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction -
Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment? I am using LabView 8.5.
I have a menu item, File/Exit, and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected. However, in development, I don't want to shut down LabVIEW when I select that menu item.
Maybe there is a more appropriate way to exit the program. However, I am looking for something elegant. I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
ThanksHere is a small VI with this exact function.
Attachments:
Is EXE.vi 9 KB -
Several question s about runtime Engine, application builder and labview player
I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferryferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png 24 KB -
Installing LabView 8.2 runtime engine on Windows 7 64-bit
We have a product built on LabView 8.2
For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
Our verification team has confirmed this to be true.
Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
How is this possible?
Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
Any thoughts would be extremely appreciated.
Attachments:
lv_install_error.jpg 22 KBNo, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV -
LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?
Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done. -
Labview 8 Application Builder and VISA Runtime Engine
Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
KenHi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer -
I am trying to run an exectutable on a computer that has the labview v8.2 runtime engine. The error I am getting is: Cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What is the easiest solution?
the matrix,
I would try reinstalling the LabVIEW 8.2 Run-Time Engine. You may also want to try creating a very simple project in your development environment that has a VI with just the Mean.vi, try building an executable and then running it on the machine that just has the 8.2 RTE.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me -
Unable to determine the install root path for the LabVIEW Runtime Engine
Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip 75 KBThis may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community. -
Profibus-Connection with NI LabVIEW Runtime-engine
Hi,
I have a Profibus network running in our porduction lane.
Now we want to report several states of this production continously.
Therefore I want to connect a desktop-pc via profibus to the PLC. But I want to run the VI on the PC as an application(exe) with the NI LabVIEW runtime engine because I won´t install LabVIEW on this PC. (on my development computer I have LabVIEW 2011)
My question is:
Does the Profibus communication work if I run the VI that way if I add the needed "additional installer" to my installer file?
I´m quite sure that it will work but I want to check this point before ordering a Profibus-Board.
I hope you understand my question and give me a positive answer so I can order an new Profibus-PCI-Board
best regards
MartinHi Martin,
the scenario you are describing sounds reasonable and that should work.
But in general, if you buy something at NI you can always call and describe your situation. Either the sales person can help you with your decision or in more complicated cases the sales person redirects you to a support engineer.
Best regards,
Christoph -
Running Datasocket in labview 2013 open labview runtime engine 7.0
Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.
Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments -
LabView Runtime Engine 7.0 trys to install at start up
This just started happening, every thing was fine a few days ago. Now when I click on the LabVIEW desktop ICON it says it wants to install the 7.0 Runtime Engine. And asks for disk#3 Do I need this? Eventually after canceling prompts for a few minutes it loads my lab view and my VIs seem to work fine.
I,m using the 8.6 student edition,
Any Ideas?
Thanks
Alan Martin
Solved!
Go to Solution.Alan,
The lvruntimeeng.msi that you said your program is looking usually resides in your drivers installer folder with a path like this:
C:\National Instruments Downloads\NI-DAQmx\<Your Version>\NIDAQ<Version>-1\Products\LabVIEW_Runtime_Engine_71\LV711RTE
Mine is exactly this path:
C:\National Instruments Downloads\NI-DAQmx\9.0.2\NIDAQ902-1\Products\LabVIEW_Runtime_Engine_71\LV711RTE
The 7.1 Runtime Engine is uniquely named "lvruntimeeng.msi". The 8.0 is named "lv80runtime.msi" and 8.2 is "lv82runtime.msi" and so on. Since we cannot install this 7.1 RTE because you have a more recent version installed, please check the path name described above to see if your 7.1 Run-time Engine MSI is in there. Maybe even run a search to see if it is present anywhere on the system.
If not, we can uninstall and reinstall your DAQmx drivers and reinstall them since they will have each Run-time Engine MSI.
Clearly there has been a file structure mishap and these can typically only be remedied by completely reinstalling the program(s) that initially installed the file(s).
Logan H
National Instruments
Applications Engineer -
Hi,
I have a problem opening an Excel spreadsheet by a LabVIEW application that is using Runtime Engine 7.0 in a Windows 98 OS environment .
I tried LabVIEW 7.1, it will not install on Win98. Meanwhile, I installed Excel 97 and 2000 (Excel 2003 does not install on Win98) and tried to open the spreadsheet, no luck with any combination.
Same code can open the spreadsheet in a WinXP OS, RTE 7.0, Excel 2000/2003 environment.
What can I do? Any advise?
Regards,
LVLVHi,
I did some experiment, I found out that Run-Time Engine 7.0 running executable generated at LabVIEW 7.0 environment (code written in LabVIEW 7.1 but save as 7.0) cannot open Excel 2000 files. If I replace Excel 2000 with Excel 2003 application on my pc, the executable code will open the Excel file (Run-Time Engine 7.0 works with Excel 2003).
Is the Excel 2003 and higher versions will only work with Run-Time Engine 7.0 and higher code?
How can I make executables using Run-Time Engine 7.0 work with Excel 2000 (Windows 98 operating system)??? (I cannot change Excel and Run-Time Engine and OS versions due to limitations, how can I work with what I have?).
Thanks for your help.
Regards,
LVLV -
Runtime Engine 7.1.1 Disk 2 when starting Labview
I have labview version 8.2.1 installed on my computer.
The other day I installed some application by another company that must have installed Labview Runtime Engine 7.1.1 on my computer. I didn't need that program anymore, so I uninstalled it.
Now anytime I try to run any labview programs on my computer, I get several dialog boxes wanting me to put NI Labview Runtime Disk #2 in my CD drive.
How can I get rid of these dialog boxes?
Please help!!!Hi bkundework,
This issue seems very strange but I do have a few suggestions. The first idea that comes to mind is to repair LabVIEW 8.2.1 from Add/Remove Programs. If you no longer have the 8.2.1 disks or if a repair does not work, you should install the LabVIEW Run-Time Engine 8.2.1. This download is available on NI’s website.
These two ideas are the easiest ways to possibly fix things. If they don’t, a list of all the NI Software you have installed would be helpful for going forward.
Charlie M. CLD
Maybe you are looking for
-
What is (ParamErr: error in user parameter list)
I get the following error message when I try to send my imovie '11 project to iDvd: Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred. (ParamErr: error in user parameter list) Anybody
-
Display Integrated Oracle Report in New Browser Window
Hi All, I am using APEX 3.0.1 and Reports Builder 10g and have integrated my Oracle Reports (.rdf) successfully with APEX. The trouble is that the report output (in PDF format) is opening in the same browser window as my APEX application and I would
-
WebDav using https fails with network name cannot be found.
When I attempt to connect to a Webdav server from a Windows 8.1 box it fails with System Error 67 has occurred. The network name cannot be found. I am using the net.exe USE command with the following syntax: net.exe use Z: https://dav.DomainYaya.com/
-
Why is the pay script showing up as script and not the link
I am trying to put the pay pal script into my form and its not showing as the link but as the original script
-
ORA-13044: the specified tile size is smaller than the tolerance
Hi, I get the oracle error ORA-13044: the specified tile size is smaller than the tolerance when I do the following point cloud clip: 8 sdo_geometry(2003,29903, null, 9 mdsys.sdo_elem_info_array(1,1003,3), 10 mdsys.sdo_ordinate_array(316504,316510,23