Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
Dan

Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
LabVIEW, C'est LabVIEW

Similar Messages

Labview Executable with VISA functions in Run Time Engine

Hi Everybody
I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
Thank you
Jackie

I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

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

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

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 I use the labview run-time engine 2010 with my LV 2012 program?

Hi all,
I will receive the new Labview Developer Suite 2012 DS2 in a few days and
I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
Stay Hungry, Stay Foolish
Solved!
Go to Solution.

Hi Benjamin,
You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications. Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
The following links direct you to our download pages for the run-time engine:
The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
Hope this helps.
Marshall B
Applications Engineer
National Instruments UK & Ireland

What's the cost of Labwindows run time engine

Dear Sir,
I have some questions about CVI and hope you can help me figure it out as usual.
1st, what's the advantage of labwindows against Labview? I know one is C programing environment and the other graphical environment. But the Labview seems more user-friendly.
2nd, What is run-time engine according to your definition? I know Matlab has similar component and is free of charge. Does the run time engine in Labwindows charge? If so, how much?
3rd, Previously, I thought labwindows is used to convert Labview program into C source code which is faster (how fast, compared with labview) and very popular in the industries, so companies do not have to buy labview and run it for just simple application in the field. But if the run time engine costs a lot, I can find no reason to use labwindows.
Thank you very much!

1) LabVIEW is a graphical based programming environment and
LabWindows/CVI is a C based programming environment. Both can be used
for similar tasks. Users familiar with C may prefer CVI. LabVIEW is
typically easier to learn if you are unfamiliar with both.
2)
The Run-Time Engine is a separate component that can be installed to
execute LabWindows/CVI programs and LabVIEW programs. It is free of
charge for both LabVIEW and LabWindows/CVI.
3)
LabWindows/CVI does not convert any LabVIEW programs into C code.
LabVIEW programs are already compiled as you write them, so you won't
need to convert them to C to use them. You should see similar
performance in similar LabVIEW and CVI code.
Allen P.
NI

Can Run-Time Engine 6.0 runs on Window XP?

I have a 6i LabView application and I did build Run-Time Engine 6.0 for that! My boss asked me that if our customer has Window XP and does not have LabView 6i whatsoever, with Run-Time Engine 6.0 install, will have any problem?

As this Compatibility article states, you won't have to worry about.
Good Luck

LabWindows/CVI 2009 Run-Time Engine update

I wanted to let everyone know that NI has released an udpated CVI 2009 Run-Time Engine. Information on what bug(s) this update fixes can be found here. If you are currently not using the CVI 2009 Run-Time Engine, you do not need to install this update.
This is an updated installation of the CVI Run-Time Engine, not a patch. If you download and install this update it will upgrade whichever version of the CVI Run-Time Engine you currently have to version 9.1.0.428 (CVI 2009 released with version 9.1.0.427). One way to find out which version of the CVI Run-Time Engine you have installed is to view the version number of c:\windows\system32\cvirte.dll. If you install version 9.1.0.428, any installer distributions that you create from any version of the CVI ADE will include version 9.1.0.428.
If you have not yet installed LabWindows/CVI 2009, it's recommended that you install this update, either before or after you install CVI 2009.
Luis

To be clear, the original problem that you reported ("Attempt to free pointer to memory not allocated by malloc() or calloc()") might very have been the problem that this patch fixed, which was in fact new to 2009. But that problem only happens if there were actual plots in the graph.
However, after looking at the "dynamic memory is corrupt" isse some more, it turns out that it is actually expected behavior, believe it or not. This is a limitation of easytab controls, caused by how they use callback chaining in their implementation. Whenever a panel or a control has its callback chained, you cannot change the callback, or make a copy of it after the chaining takes place. This is described in the EasyTab_ConvertFromCanvas function help ("...For the same reasons, do not call DuplicatePanel or DuplicateCtrl on any of these panels or controls after the Easy Tab control has been created.").
As you probably have read elsewhere, easytab controls are quite obsolete. They were a stopgap "solution" to the problem of there not being a native tab control in the CVI user interface library. Native tab controls were finally added in CVI 8.0, and so we recommend that, if possible, users update their code to use these instead.
Luis

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Will Labview VIs developed on a MacIntosh run on a Windows PC? How about visa versa?

Will Labview VIs developed on a MacIntosh run on a Windows PC? How about visa versa?
Thanks,
Dennis U

As long as you don't use platform specific tools (such as IMAQ vision, ActiveX...), or advanced DAQmx functions, LabVIEW portability between platforms is excellent.
On MacIntosh, LabVIEW works fine with virtual PC, but is very slow (5-10 times...). Try it and see if it suits you needs.
Message Edité par chilly charly le 01-09-2006 09:19 AM
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

Does labview run time engine 8.6 LVRTE86std.exe supports DAQ?

Due to the LONG TIME required to build an installer with exe, and this kind of DAQ issues http://forums.ni.com/ni/board/message?board.id=170&message.id=324343&query.id=1071542#M324343
I want to just give the user the Labview run time engine 8.6 LVRTE86std.exe http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en , and ask them to copy paste the exe.
But does the LVRTE86std.exe contains all the necessary dependency for DAQ? Including the Sound and Vibration dependencies required for DAQ? Is there some document I can look up to see whether LVRTE86std.exe supports DAQ and I dont have to build an installer of my own?
Solved!
Go to Solution.

No, the runtime does not include DAQmx. It does not include any hardware drivers. That is discussed in numerous posts.

Can LabVIEW Run-Time Engine 7.0 control LabVIEW 6.1 VIs?

I'm attempting to remotely control a LabVIEW 6.1 example VI through the browser plugin on another system. On that other system, can I use LabVIEW Run-Time Engine 7.0? Or do I need 6.1?

Never mind, I should have read the RTE 7.0 information first. I need LabVIEW Run-Time Engine 6.1 to run LabVIEW 6.1 VIs.

Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

Similar Messages

Maybe you are looking for