Window 7 using LabVIEW Runtime 8.6

Has anyone tried RTE 8.6 run time engine on Windows 7 ?

LabVIEW 8.6 is not officially supported on Windows 7. It might work, it might not. That's assuming you can actually get it installed. Search the forum and you will see this issue has come up many times over the past few months.
LabVIEW 2009 is officially supported for Windows 7.

Similar Messages

[HELP] Teststand error when using labView runtime engine...

I have an extensive TestStand 3.5 project which I am working on. This project uses a large number of LabVIEW 2012 VI’s. (Note: The version of TestStand cannot be changed). When TestStand 3.5 LabVIEW Adaptor is configured to “Development System (Active Version: 12.0)” all the sequence run and perform as expected.
When I change the TestStand 3.5 LabVIEW Adaptor is configured to “LabVIEW Run-Time Engine 12.0” then I get an -18002 error in the first VI called by the sequence and nothing runs. Now this sequence contains a standard library VI in it “Check if File or Folder Exists.vi”.
From research I realised that I needed to deploy the software properly. So created a LabVIEW project with all the sequences and VI’s in it and a “Source Distribution”. I also unchecked “Exclude files from vi.lib”, “Exclude files from instr.lib”, and, “Exclude files from user.lib”. After building the project I get a “data” folder full of VI’s and control files (273 of them).
Next I created an “Installer” and added build to the correct place. I can see the “data” folder in the source files section.
When I install this distribution kit on a PC, which happens to have full LabVIEW 2012 development on it, all the files install but the “data” folder is missed out!!!
If I then attempt to run the installed top level sequence I get the same -18002 broken VI error as before. If I manually copy the “data” folder into the same place as it was built it makes no difference.
Anyone got any suggestions?
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

Bit of additional information:
I created a blank LabVIEW 2012 project. To this I added one VI which included a call to "Check if File or Folder Exists.vi". Then added one TestStand 3.5 Sequence which contained a call to the VI above.
I then added a build to the project and built the project. This resulted in a folder with the sequence file, my VI and a Data folder containing the "Check if File or Folder Exists.vi". When I tried to run the TestStand sequence with LabVIEW Run-Time Engine selected it failed as before.
Next I added another LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" from the "Data" folder. It then worked!
I then modified my VI and added the MD5 checker VI (forget the exact name). It added some files to the dependences in the LabVIEW project. I rebuilt it and ran it again and again it worked. I did not need to add the additional VI's in the "Data" folder to the sequence file.
If I remove the LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" though it breaks again.
This is not ideal though as it is a bit chicken and egg. In order for the project to work I need to add one of the VI's from the generated "Data" folder into a sequence in the project, but I can't do that until I build the project to create the "Data" folder!
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

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.

Can I use labview 7.1 run time in windows 98?

I am going on update a too old test system. I use labview 7.1,but I find I can't install labview 7.1 runtime in windows 98.
so should I use labview 6.1 instead of it?
Sonic
Diffrent Strokes for Different Folks

Why cnt you update both ?!
- Partha
LabVIEW - Wires that catch bugs!

Transferring data from a DOS 5.0 (Win 3.1) Computer to a Windows XP Computer - Using Labview

In 1992 my lab purchased a Particle Size Analyzer (Microtrac series 9200) that came with a Compaq computer (DOS 5.0, Win3.1) and a printer. Due to proprietary software restrictions I currently need to keep the analyzer software operating on the DOS computer (to calculate the particle size distribution according to Microtrac's evaluation), although everything else about the system is out-dated. In fact the printer just died last week.
I have been asked to figure out a way to still be able to use the old analyzer software on the DOS computer, but retrieve the data so that it can more quickly (and reliably) be analyzed using current platforms. At the back of the DOS computer the only available port is a parallel port - what Im wondering is how I can transfer data using a parallel port from a DOS computer to another computer with Windows XP? I'd like to use Labview on the 2nd computer (with Windows XP) to retrieve the data - is this possible? And, how do I do this?
Other related questions which you may be able to help with:
(1) What equipment/ type of cord do I need to connect parallel ports?
(2) How do I get a DOS to send signal from the parallel port to the other computer? Do I just need to push "print screen"?
(3) What program do I need on the DOS computer to interface with the parallel port and send signals to the newer computer? Is there a labview program that will run on a DOS computer (Win 3.1)?
Thanks very much in advance for any assistance in this. I do not have a huge amount of computer knowledge so I apologize if any of my terminology is not completely accurate.

In dos you can use the copy or print command. More about it here. http://www.computerhope.com/issues/ch000199.htm I have also used a memory stick on dos system. I have USB memstick driver. This works fine. However This will require that your host computer do have a USB port.
Most computers from that time do have one or more serial ports. If you have a free serial port I would have used this and hyperterm on the XP computer. In order to transfer the output file. But before you do this you must set the serial ports on both computers to the same setting. In DOS this is done with the mode coomand http://www.computerhope.com/modehlp.htm
I do not know if this is supported in dos 5.0. But try to type the command msd in dos. MSD is a diagnostic utility to view diagnostic information relating to your computer's hardware setup
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

How do you make third party application window backmost using labview

Hi Guys
I know i can do whatever i want on labview windows.i can make third party application window frontmost.
But How to make third party applicaiton window backmost using labview.
Thanks

Hi wenjie1wang,
I have attached an example that uses the "Call Library Function Node" that accesses the "user32.dll" file that is responsible for manipulating with the windows such as minimising it.
After opening the VI you have to enter the name of the window you want to minimise, you can hard code that as a constant. Also on the front panel the control "nCmdShow" can be changed to dictate the action you want to do with the window.
Furthermore, please look at the Microsoft Developers Network to find more useful ways to use the property node in your project.
http://msdn.microsoft.com/en-US/
Let me know if this works.
Regards
Art
Applications Engineer
National Instruments
Attachments:
Minimise Window in Win7.vi ‏14 KB

Windows error 998 by installing labview runtime 8.2.1 on windows xp

Hello,
I got Windows Error 998 during installation of the labview runtime engine 8.2.1 on windows xp system. The installation with the same package worked on serveral other systems with the same os.
Any ideas?
Thanks a lot and best regards,
Michael
Attachments:
Error_998.png ‏14 KB

Based on the message it appears it's having problems reading the file. Did you copy the files from a CD? From a network? The file itself may be corrupt. Try recopying the files to your hard drive. You may also want to check your hard drive for errors.

Using Labview VIs without runtime

Hi all,
here we have a quite heavy Labview 2012 application. It consists of several dozens of VIs. One of them is a firmware updater for devices we produce.
The task is to create a standalone firmware updater which shouldn't rely on an installed Labview runtime. So our idea was to create a DLL from this VI which provides the corresponding functions. Then these DLL functions may be called from another application.
The problem is that the produced DLLs rely on an installed Labview runtime. Is there any other way to access VIs (or Labview functions in general) without a dependency on the runtime? I mean besides using Cameyo.

ABachmann wrote:
The problem is that it isn't possible to download a 200+ MB runtime everywhere around the world. If a farmer in the Australian bush only has a 19k modem connection, it is hardly a solution to have him download the hundreds of MB for the runtime for a small updater which is only some hundred KB of size. This is a real world scenario, we had this.
So we had the idea to create a DLL of some VIs and put around some glue code. This would be the fastest solution. But without a way to do this, we have to reimplement these VIs in another language. It is like reinventing the wheel.
I understand your problems but other languages will require specific libraries to exist on the system in order to run. They will be no different in that regard. They may benefit from using the libraries that are included with the OS installation but they are still using those items and if not there, such as the DotNET example listed above they will need to be downloaded as well. NI has made some improvements in LV 2011 that can trim back some of the RTE elements that get installed. As suggested though you can always create two installers. The RTE does not need to be included once they are already on the system.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Changing windows 7 display options using LabVIEW

I would like to use LabVIEW to change the display settings I'm using in Windows 7. To change the displays settings in Windows I have to right click on the desktop and click screen resolution. Then I have four options under multiple displays (Duplicate these displays, Extend these displays, Show Desktop only on 1, Show Desktop only on 2). I would like to be able to pragmatically select these. I believe I have use user32.dll to achieve this but am not sure which function to use. Any help would be appreciated. Thanks

Have you seen/tried this thread?
http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/7c9fd6d4-cee7-490a-8507-afb9512b3...
Charles Chickering
Architecture is art with rules.
...and the rules are more like guidelines

Now I am using Windows Xp Labview program now i want control the Sun Solaris OS Board.Is it Possible in Windows XP Labview?

Now I am using Windows Xp Labview program now i want control the Sun Solaris OS Board.Is it Possible in Windows XP Labview?

You better should post your question in the LabVIEW forum - this one here is dedicated to LabWindows/CVI...

Hoe I can convert a word or sentence into audio output using LabVIEW like the windows narrator?

I am converting Braille script to audio output using LabVIEW. So, I need to convert the script to english and then to audio. How can I do it?

Amaravian wrote:
I am converting Braille script to audio output using LabVIEW. So, I need to convert the script to english and then to audio. How can I do it?
From what I've seen in my brief search, you need to go the ActiveX route.

Error while using LabVIEW 8.2.1 Dll from Visual C++ 6.0

I am getting an error while using a LabVIEW 8.2.1 dll from Visual C++ 6.0 application. This is what I am doing:
1) Created a dll using LabVIEW 8.2.1 (I used a tutorial from NI knowledge base: "Creating DLLs from 6.0i". It is a temperature conversion VI; input DegreeF and get DegreeC out). Instead of LabVIEW 6.0i, I used 8.2.1. It created the dll Convert_Temp.dll successfully.
2) Then I created a Visual C++ 6.0 application (used a tutorial from NI knowledge base: "Calling a DLL from Microsoft Visual C++ that was Generated by LabVIEW 6i). I could build the project and create an executable application F_To_C.exe.
3) Then copied the LabVIEW dll Convert_Temp.dll into the folder where F_To_C.exe resides. Using windows explorer, went into that folder, and executed the application. I got the following error:
System Error 998 while loading the LabVIEW run-time engine (C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\8.2\lvrt.dll).
Convert_Temp requires a version 8.2.1 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of Convert_Temp to correct this problem.
I checked the folder: C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\8.2\. It has the file lvrt.dll.
So why am I getting this error?
GKB

sounds like you need to install the LabVIEW 8.2.1 runtime. Not the 8.2 runtime engine.
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC

I have a dll built using LabVIEW 6i. I am calling the dll from a VC++ application. When the application loads I get an error pop-up 'cannot find LabVIEW runtime'. If I change the VC++ code to dynamically load MFC (using the loadlibrary function) or dynamically load the LabVIEW dll I created then the problem goes away. Only when both are loaded statically do I get the error message.
The target machine is running Win2K pro and has the LabVIEW runtime installed.
I do not want do dynamic loads as I need to call the dll from a legacy application. Are there any options to change the way LV links to MFC or to force the dll to find the LV runtime?
Alan Widmer

Ben,
I have attached a ZIP of the files required to test a DLL from an MFC application. Or you can build the same application by following the instructions below. I used the numtest dll that you previously sent to me so there is no 'magic' in the LabVIEW or dll.
In VC++ select NEW. Pick the MFC AppWizard (MFC) to build an MFC application. In the wizard select
Project Name: MFCNumtest
Single Document
No database support
No Compound document support
Support for ActiveX
Default settings on the Features page
MFC Standard
MFC as a shared DLL
From the ResourceView of the project explorer, add an item Test to the IDR_MAINFRAME menu then add an item Go as a submenu item (with an ID of ID_TEST_GO)
Right click the new menu item and run the Class
Wizard. Click Add Function.. button to make a function OnTestGo()
Open MainFrm.cpp and scroll to the end of the file to see the skeleton for the OnTestGo function. In this function add a call to the LabVIEW dll. You will also need to add a reference to the .lib file and the usual extcode.h.
When you run the app you will see a window with the Test menu item. Select it and click Go to run the call to LabVIEW.
This all works great. If you now go to Project | Settings and on the general tab change the Microsoft Foundation Classes: item from 'Use MFC in a shared DLL' to 'Use MFC in a static library' rebuild ALL files in the project and run the app you get the error message:
System error 998 while loading the LabVIEW Run-Time Engine (C:\Program Files\National Instruments\shared\LabVIEW Run-Time\6.0\\lvrt.dll).
numtest requires a version 6.0 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of numtest to correct this problem.
I apologies for my slow response, g
ot distracted by some other issues.
Thanks for your help,
Alan Widmer.
Attachments:
mfcnumtest.zip ‏44 KB

Communicate with LabVIEW RunTime Application

Hi all.
I have an application created in LabVIEW, and I built an executable file from it (Let's call it App1.exe).
While App1 is running it sometimes generates an exception and is aborted. The problem is that the Run-Time APP1.exe GUI remains open (Which is undesirable). I need a way to close it somehow. I realized that the only way to close it is from another application (Let's call it App2).This solution can be realized in 2 different ways:
1) App2 communicates with App1 and closes it if App1 is not alive. The problem is that sometimes App1 is simply working slowly because of system problems and I might shut it down even though It's still running
2) To somehow obtain from the Run-Time engine what's the state of App1. I think that this way is preferable but i don't know how to communicate with the Run Time Engine.
I'll appreciate any suggestions (Preferably with some kind of example code)
Thanks, Nadav
P.S. I'm using LabVIEW 8.2.1.

What do you mean that it is "causing an exception"? Typically, an exception is a pretty serious failure that would kill the runtime engine too (thus closing all windows associated with it). What sort of error is stopping your application, but not the runtime engine executing it? It sounds like you possible have an internal error state that you haven't handled adequately. Part of the handling for a non-recoverable error should be orchestrating an orderly shut down of the application.
For what it's worth, if the runtime engine is still alive you can connect to it using VI Server and ask the execution state of the top-level VI. If it comes back "Idle" your code has stopped.
Mike...
Message Edited by mikeporter on 05-21-2007 12:43 AM
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

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

Window 7 using LabVIEW Runtime 8.6

Similar Messages

Maybe you are looking for