Installing VISA run-time with distribution

Is there a way to seamlessly (transparent to the end-user) integrate the VISA run-time engine installation into an installation of a Labview app created with App Builder?
I am trying to avoid the user having to run two different install programs (the app install and the VISA install).
I am doing some serial port communications, using the VISA VI's in my app. Also, does VISA need to be configured beforehand, or can I just load a customized 'visaconf.ini' file with the serial ports aliases?
Thanks.

Hi,
There isn't a way to automatically include the VISA installer on the LabVIEW app installer. You can use some batch files to make the LabVIEW app installer execute other installers.
The following knowledge base gives some suggestions and points some of the problems you might encounter when using the LabVIEW 6.1 App Builder.
How Do I Distribute National Instruments Drivers with Applications Built in LabVIEW 6.1?
Hope this helps
DiegoF
National Instruments.

Similar Messages

Problems bundling visa run time with installer

I am trying to build an installer for an application that makes VISA read/writes through a serial port. I have tried to create an installer for this application but I keep getting a cryptic error that then terminates LV. I am experiencing the same problem as described in this thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=228510&query.id=494979#M228510
I am developing with LV8.2 on XP SP2. I would like to bundle the VISA Run Time so that I can communicate via VISA R/Ws. After reading the above mentioned thread it didn't seem like there was ever a real resolution to the problem. I am bundling the VISA Run Time engine just fine with other projects and I have deleted and started over several times with the installer inside this project, but I keep getting the same error, see attached document.
So are there any ideas short of me having to reinstall LV or VISA?
Thanks in advance!
Dave
Attachments:
LV Error.doc ‏32 KB

Thanks for the reply.
I would agree that the project is corrupted. I think I proved to myself that this was the case when I created a new project and magically everything worked just fine. The project was created under the exact same release of LV by the same PC so I am just trying to understand why the project was corrupted while trying to build the installer.
I guess I have my solution now I'm into the deep dark hole of trying to understand why the error occured. I know once I go down this path there is no returning.......
Thanks!

Where is VISA run time engine in new LV 7.1 from August?

Hello All
Can somebody help me locating run time engine to VISA in the new LV7.1 from August 2004?
Thanks in advance
Pawel

Hello Pawel
The Run-time engine is not related to the LabVIEW version you are using on your executable but the NI-VISA driver version you are using in LabVIEW on your executable. So if you are using the newest version of NI-VISA in LabVIEW 7.1 which is version 3.2 you would have to install VISA Run-time engine 3.2 on the target machine.
You can find all the VISA run-time engine version on the following site...
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BAC002C51FA?opendocument&node=132070_US
Regards
Mohadjer

How to Install crystal run time programs with out designer.

Can anyone suggest me how to install crystal run time program with out installing entire designer software.
Is it coming along with CR software package, which we have to do custom install or is it coming as a different package.
Currently my client is using only the run time programs to trigger crystal report from VB app but developers have installed entire software for development. We need to figure out how this install can be done, as it was done long time before and folks who have done it left the company.
Any suggestion on this would be of great help to me.

See this wiki:
https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsforVisualStudio.NETRuntimeDistribution-Versions9.1to12.0
Ludek

Visa run time installer in LV 8.2?

Hi again!
I need some help conerning adding Visa Run Time to an .exe that I'm trying to build. I recently built the .exe and found that the front panel and all sub Vi's were active, but the controls weren't communicating through the serial port like they had been when I was working with the project. From what I have read and observed, it looks like the appropriate action to take would be to include the VISA run time components with the exe. However, I'm unable to located the correct window in which to do this! I have seen screenshots on the forums, but am not able to locate it in the ".exe" builder! I'm running LV 8.2 and I downloaded the Visa - Runtime 4.0 zip, extracted, and ran it on my system but it wouldn't continue installation, telling me that no files would be removed or installed. I tried to modify what would be copied to the drive but I couldn't make any selections that changed the out come. I'm very green to labview and would appreciate any help or advice that can be given.
Thanks
Ryan

Hi Valcon,
To include the VISA Runtime Engine in your installer for your executable, you'll want to go to your Project Explorer and Right-click Build Specifications & select New Installer from the list. You can then add the VISA Runtime Engine under the "Additional Installers" section. Installers are made for executables that you would like to run on computers that don't have the full version of VISA, etc. installed (thus we need the Runtime Engines). If you run your executable on your development computer, you should already have the full version of VISA installed & you should be able to run your executable there without a problem. Hope this helps!
Regards,
Anna M.
National Instruments

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

How to include the visa run-time into the installer?

Dear All,
          I made an USB device whose driver is developed by "NI visa driver development wizard".
          In my program, the COM is also be used. When it is builded and creats the installer, I have checked the Serial Port Suport in Advanced settings in Installer which I thought the visa run-time engine is concluded. In fact, when it is installed, the COM can work correctly, but the USB device's driver can't be installed. To fix it, the visa run-time engine must be setupped again.
          I see that I can add it to "run executable after installation" but during the installaion of run-time engine, some pages will be displayed which need user to choose some option.
         Would you please give some suggestion that the process of installation is automatic. Certainly the part of visa run-time engine which the USB driver is needed can be integrated to the installer of vi(like COM) is best.
          Thank you!
Hugo
PS: I am using LabVIEW 7.1

First, you can install a VISA Runtime Engine in the target PC, to verify it is VISA Run Time Engine issue.
If so, you can add a VISA Run Time Engine in LabVIEW when creating an Installer. It is much easy in LabVIEW 8 and still possible in LabVIEW 7.1. Follow the link.
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E?OpenDocument

Installing LabVIEW Run-Time Engine 8.5.1

I want to run saved VI's from one computer with LabVIEW 8.5 Professional Development (8.5) on another computer using the Run-Time Software.
After installing LabVIEW Run-Time Engine 8.5 (LabVIEW85RuntimeEngineFull.exe from http://joule.ni.com/nidu/cds/view/p/id/861/lang/en), do I need to do anything else before running a saved VI created in LabVIEW 8.5 from another computer? I install the program, but the only options under programs-national instruments are:
-data socket
-License Manager
When I installed LabVIEW DSC Run-Time System 7.1 on the same computer there was an shortcut under "programs-national instruments-" to LabVIEW DSC Run-Time System 7.1, which is what I need but for the Run-Time Engine 8.5 instead.

Joseph is correct. The run-time engine is only for "stand-alone" executables created with the Application Builder (included in the Professional version or higher, or can be purchased separately if you have the Base package). To run a vi in the development environment, you need one of the LabView packages.
Message Edited by Edjsch on 05-12-2008 01:48 PM
Message Edited by Edjsch on 05-12-2008 01:48 PM

Installing only Run Time Components

We have recently purchased the Oracle IDS 6i suite. In the On Line Manual for Forms & Reports 6i,it is stated that to install the Run Time Components only one has to use the Custom Option and then select Runtime Components. However when we try this out we do find the Runtime Components option in the Software Asset Manager.
Could somebody tell me where these components are located are they in some other CD.
Thanks
R. Nair

Joseph is correct. The run-time engine is only for "stand-alone" executables created with the Application Builder (included in the Professional version or higher, or can be purchased separately if you have the Base package). To run a vi in the development environment, you need one of the LabView packages.
Message Edited by Edjsch on 05-12-2008 01:48 PM
Message Edited by Edjsch on 05-12-2008 01:48 PM

Able to install the .ipa signed with distribution certificate using iTunes on MacBook Pro. where as the when tried to install using iTune on PC is causing a problem

Able to install the .ipa signed with distribution certificate using iTunes on MacBook Pro. where as the when tried to install using iTune on PC is causing a problem

The sound input going to the mic is not going to pipe through the speakers like that. It doesn't do it because it would cause a feedback loop on itself. The mic input will take sound and output it to a program or to another pathway (like a VoIP or Facetime call, etc.) but it won't behave like a Karaoke machine if that's what you're thinking.

VISA run-time Engineがインストールできず困っています.

VISA run-time Engine　5.4　のインストールをこころみましたが、
”VISA Shared Components 64-Bit”のインストールに失敗しました。というポップアップ
が表示され、最終的にインストールに失敗します。
VISA run-time Engine　5.3　と　VISA run-time Engine　4.6.2　のインストールも試しましたが、
インストールに失敗します。
ウィルス対策ソフトを停止しても同様に失敗します。
どのバージョンもドライバーパッケージのインストール（中のデジタル著名？）がうまくいかないようです。
解決方法をご存知の方、ご回答のほどよろしくお願いします。
PCスペックは以下の通りです。
　　OS:　　　　　　Windows 7　64bit
　　実装メモリ：　8.00GB
　　空き容量：　　260G
添付:
VISA_RunTimeEngine_インストールエラー.png ‏236 KB

返信が遅くなりました。
申し訳ありません、表現が悪かったようです。結局解決できずじまいです。
幸いXPパソコンを用意できたので、XPパソコンにインストールし対応しました。
VISA run-time EngineはNF社の任意波形発生器を制御するために必要でした。
類似の事例等ご存知でしたら、アドバイスいただけませんでしょうか。

How to prevent prompt to install CVI Run-Time Engine?

The LabVIEW laptop for my client got messed up, so I spent several hours making it forget everything it ever knew about NI software. I started by uninstalling all NI applications, then manually deleted all the folders that the uninstaller leaves behind, then ran a couple of registry cleaners to sweep out as much NI as possible, and finally ran regedit to see what was left. In the end there were only some legacy drivers that regedit would not let me delete.
Then I installed 8.6.1 from DVD, carefully selecting only the options we needed; LabVIEW core, cRIO, FPGA, PID, and the minimum set of drivers the installer would let me get away with. Note that no Labwindows/CVI option boxes were checked. When the installation was complete, I rebooted the machine and launched LabVIEW, which immediately prompted me to install the LabWindows/CVI 8.5.1 (not 8.6.1) Run-Time Engine. I dutifully fed it my 8.6.1 DVD, which caused LabVIEW to crash. After 3 reboot/retry cycles with the same result, I decided to appeal to the forum for help.
What is causing LabVIEW to think I need the CVI Run-Time Engine (and a down-rev version, at that), and how do I convince LabVIEW that I do not?
Jeff

Thanks for the reply! OK, so LabVIEW needs the CVI RTE even though I'm not using any CVI features. I can live with that. I downloaded LabWindows/CVI Run-Time Engine 8.5 from the NI web site and tried to install it. After I confirmed that I accepted whatever that license agreement says, the installer told me that "No software will be installed or removed."
Then I opened LabVIEW, and it went through the same "The feature you are trying to use..." popup and tried to install the CVI RTE. The installation failed as usual, and LabVIEW crashed.
A few minutes ago I found and ran CVTRTE.msi on the 8.6.1 distribution DVD. I selected the "repair" option, which completed successfully. After rebooting, I launched LabVIEW only to be greeted with the now-hated NI LabWindows/CVI 8.5.1 Run-Time Engine installer.
The part of this that is so infuriating is that there appears to be no way for anyone to make a computer forget everything NI so you can start with a clean slate.
Jeff
Attachments:
NoCanDo.jpg ‏28 KB

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

Path where to install the run time engine (on Linux)

I have a cluster of Linux computers where I would like to run compiled LABview (8.20 at the moment) applications build
with the application builder.
Therefore I would like to install the LABview run time engine on a NFS mount file system seen from each computer. But
the installation procedure of the run time engine does not propose to
choise the installation directory, but force the installation
in /usr/local/lib.
I try to workaround this problem and have copied the /usr/local/lib/LABview.8.2 directory to my NFS filesystem and
made the 'necessary' links.
Unfortunatly it doesn't run and fails because the
liblvrt.so.8.2 library can not access patched versions of the
libOSMesa.so.4
and libGL.so.1 librairies but uses the standard ones in /usr/X11R6/lib.
Even by setting my LD_LIBRARY_PATH correctly to access the patched librairies versions it does not run because the
liblvrt8.2 library seems to be linked with the following
'rpath' (given by the command 'strings liblvrt.so.8.2 |
grep patchlib')
$ORIGIN/LabVIEW-8.2/patchlib:$ORIGIN/patchlib:/usr/X11R6/lib:/usr/lib:$ORIGIN:$ORIGIN/LabVIEW-8.2/linux:$ORIGIN/linux:$ORIGIN/resource
which prevents to access the patched librairies versions if the $ORIGIN is not set. Therefore I tried to set $ORIGIN as an
environment variable but it doesn't change anything.
Therefore my question is: Did somebody have already had this type of problem, what is $ORIGIN and how I can set it ?
Thanks in advance.

Sir,
Please could tell me the distribution you use ?
Cordially,
Pierre R...
Certified LabVIEW Developer

Installing the run-time engine as a non-administrator

I want to distribute a stand-alone application to end-users that are not administrator of their computer. When they try to install the RTE without administrator privileges, the installer cannot continue because it cannot write to the C:\ base directory. How can I fix the run-time engine installer to work without administrator privileges?

On the second screen of the installer, the user can choose an alternative target location. Have you tried that?
(sorry, I don't know how well this will work). What is the runtime version?
(For your reference, this document describes planned changes in the folder structure for future LabVIEW versions.)
LabVIEW Champion . Do more with less code and in less time .

Installing VISA run-time with distribution

Similar Messages

Maybe you are looking for