NI VISA 14.0 runtime engine

Hello Everyone,
I started with LabView full development system 2011 and updated to 2014 recently. Now I was trying to build my vi. When i was trying to create runtime engine when I select NI VISA 14.0 it is giving error saying " NI visa 14.0 media path not found". So i just tried to install runtime engine by downloading from ni.com, downloading was successful, but not able to install it. Am I doing anything wrong?
Thanking you,
Sushmith

sushmith_ks wrote: When i was trying to create runtime engine when I select NI VISA 14.0 it is giving error saying " NI visa 14.0 media path not found".
The installer build spec just needs a copy of the VISA 14.0 installer in order to add it to the installer for your application. You do not need to reinstall it. It should ask you where the distribution is.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

I give up where are they hiding the LabView runtime engine downloads?

When I deploy en EXE I find it much easier to just plug the target machine into the network and download VISA and the Runtime Engine.
VISA is easy to find but I always end up spending 45 minutes to an hour looking around for the LV runtime download.
It's been 45 minutes now and the closest I have come is finding the Web Browser runtime plugin.

2012 32bit
2012 64bit
2012 SP1 32bit
2012 SP1 64bit
2011 32bit
2011 64bit
2011 SP1 32bit
2011 SP1 64bit
2010 32bit
2010 64bit
2010 SP1 32bit
2010 SP1 64bit
2009 32bit
2009 64bit
2009 SP1 32bit
2009 SP1 64bit

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?
Ken

Hi,
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

Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
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

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

Runtime Engine VISA Treiber in EINEM Installationsschritt - wie ?

Folgendes Problem:
Mein Programm benutzt den seriellen Anschluss. Damit das funktioniert müssen sowohl die Runtime Engine als auch der Visa-Treiber installiert werden. Beim Visa Treiber 3.01 soll man sogar noch eine fehlerhafte Datei per Hand austauschen - Wie bring ich das Ganze in die vom Application Builder erzeugte Installation ?
Man kann ja kaum dem Kunden zumuten, 2 Programminstallationen durchzuführen und dann noch eine Systemdatei manuell zu patchen..!

Just an idea for a workaround:
-Include the VISA Install files as support files into your main install package.
-In the installer options you can start a program after installion, so it should be possible to start the VISA installation
-For the patch... maybe that might work with a script (.bat) file that you start for the installation and replacement ? But then you shouldn't reboot after Visa installation and do this reboot in the script.
Henrik
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Can visa runtime engine be included in application build?

I just installed my program on a new machine and it wouldn't work. Turned
out I needed to also install the visa runtime engine. Is there any way to
automatically include that in the application build?

I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
/Brian
Attachments:
screenshot 13-08-2007 17.57.JPG ‏95 KB

An EXE under 8.5.1 runtime engine can't find VISA drivers

Apologies in advance for newbie question.
I built a simple app (EXE) that uses PC serial port, using VISA drivers.
Works OK on one Dell PC, not OK on another. Not exactly sure what to try.
The failure occurs when code hits the "Visa configure serial port" block.
See attached bitmaps for error message and offending block.
Do the Visa drivers need to be installed by me on the PC ?
Attachments:
error9.JPG ‏46 KB
diagram.JPG ‏11 KB

Hello Remerlin,
Did you just create an exe, or did you create a full installer. If you are going to deploy an application that uses functionality such as VISA, or LabView Runtime, you need to create an installer and include the additional installers such as VISA. The following is a link to a tutorial on how to do this.
http://zone.ni.com/devzone/cda/tut/p/id/5406
When creating the installer, go to additional installers under categories (in installer properties) and make shure VISA, and LabView Runtime are checked, as well as any other functionality you will be using.
Regards,
Ben Cook

Instrument I/O assistant in runtime engine

Hello,
I currently use the Instrument I/O assistant in some of my VIs to communicate with an Agilent network analyser using SCPI commands. This works fine, and I am able to do everything I want to do (on my desktop which has LabVIEW installed).
I would like to be able to run my VIs on a laptop which does not have LabVIEW installed, using the free runtime engine. I have successfully been able to do this with several VIs that do not contain the Instrument I/O assistant.
However, I can't get any VIs that contain the assistant to work on the laptop. I have verified that the connection between the laptop and the network analyser is OK in MAX, and all the device numbering and addressing is the same on the laptop as it is on the desktop. I have even been able to get individual blocks such as "GPIB Write" to work on the laptop.
Any ideas would be greatly appreciated.
Cheers,
Dan

What version of LabVIEW are you using? For quite a while, you have had the option of creating an installer. This is the recomended way to distribute an exe. Prior to 8.x, you could include the LabVIEW run-time. Since 8.x, you have had the option of creating an installer that included hardware drivers such as GPIB, DAQmx, NI-VISA, etc. You could also download the VISA run-time. The full version of VISA should also be included on the CD you got with the GPIB board. Some of the GPIB CDs did not automatically install VISA but you can always stick the CD in and manually select it for installation.

Runtime engine can't load vi with lvdatetimerec.ctl

Hello everybody,
i have trouble with TS 3.5 / LV 11.0
I programmed a small vi that calculates the time difference between now and a time stamp. To pass the timestamp from Teststand i use a Control (lvdatetimerec.ctl) and the matching VIs to do the task.
Unfortunally i can't load the vi into Teststand using the Runtime Engine. I get the message "Unable to load VI "xx.vi" with the Run-Time Engine. It is possible that the version of the VI or one of its subVIs is not the same as the ..."
It is certainly the same and there is no problem until i include a constant or control of that type.
Do anybody have an idea?
Best regards
Thomas
Attachments:
TimeDiff.vi ‏7 KB

Try to recompile your vi hierarchy in LabVIEW (hold Ctrl and click Run), then save it, then try again in TestStand with LabVIEW runtime.
Runtime engine does not support dynamic compiling, this vi may looks fine in LabVIEW, but TestStand will complain that it is broken.
Sergey Kolbunov
CLA, CTD

Cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported

Hi,
I am new to using third party labview drivers. I have a labview driver for Chroma 63600 loads that I want to use in TestStand 2012.
However when I load the vi. I get an error 'cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported'
I have Labview Runtime Engine version 7.0 Installed on my Windows 7 machine.
Could anyone please let me know, How I could resolve this issue?
Please see attached driver for Chroma Loads
Solved!
Go to Solution.
Attachments:
chr63600_LabView_V11.zip ‏866 KB

To avoid more confuison,Here is the scenario,
The version that was on the driver attached is from the driver manufacturer.
I do not have any version of labview INSTALLED on my system. I am using the driver in Test Stand 2012 using a labview adapter.
I make sure I match the VI version and the run time engine version on TestStand 2012 to load the VI.
But for this specific driver, I was not successful in loading the VI at all.
As I understood that only 8.0 OR LATER are supported on TS 2012, I have asked to upconvert the driver to work with 8.2.1 Labview runtime engine.
I have now got a.LLB file of the driver mass compiled in Labview 2012 from discussion boards( and also attached here). I have tried the mass compiled LLB file on TS2012 but still have issues loading the VI as it moans about different version of SUB VIs.
However I am still trying to fix this version incomaptibilies. Any help would be much appreciated

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 KB

This 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.

Can I extract the orginal VI's from an executable created by Runtime Engine?

I have an executable program created using the Labview Runtime engine and need to edit the subVI's contained within. Unfortunately, I don't have the original VI's the program was created with.
Is there any way I can extract those VI's?
Thanks,
Mike C.

First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
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

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

NI VISA 14.0 runtime engine

Similar Messages

Maybe you are looking for