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

Similar Messages

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

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!

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.

LabVIEW Run-Time Installer

Hi,
Does anyone know if it is possible to run the LabVIEW Run-Time Installer
in silent mode?
Best regards
Magnus Nilsen

"Magnus Nilsen" wrote in message
news:[email protected]..
>
> Hi,
>
> Does anyone know if it is possible to run the LabVIEW Run-Time Installer
> in silent mode?
>
> Best regards
> Magnus Nilsen
It is simple!
Place in folder
C:\Program Files\National Instruments\shared\LabVIEW Run-Time\5.1\
lvrt.dll and ole_lv5container.dll
Do not install RT 5.1.1 because of bug in
Edit->Preferences: Tab [Front Panel]->Check box 1,2,3 or 4 -> Crash!!!

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社の任意波形発生器を制御するために必要でした。
類似の事例等ご存知でしたら、アドバイスいただけませんでしょうか。

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

LabView Run-Time Installation Failure

Hi
I am trying to install the LabVIEW Run-Time Engine 20112 under a Windows XP Professional 32-bit SP3 Versin 2002, but every time I open the executable file, the comand prompt returns the message "Program too big to fit in memory". The machine has 2Gb of RAM memory, with only 670Mb in use. The Hard disk has 17Gb of free space. I have also installed on the computer the LabVIEW Run-Time Engine 8.6.
Could you support me in the installation ?
Tanks
Download Link:
http://joule.ni.com/nidu/cds/view/p/id/2534/lang/en
Executable file name:
LVRTE2011f3std.exe

Recargable wrote:
Hello!
I tried installing the last version of the Windows Installer and the problem persisted.
First I was installing from a mounted ISO image as if it was a DVD inserted for the virtual Windows XP, so I tried installing from a copy of the ISO image in the virtual hard disk, which failed too. Then I tried installing the Windows Installer. Copy the installation files out of the ISO image didn't go well either. Finally, I copied the installation files to a usb flash memory, I installed the Virtual Machine Additions in the virtual Windows XP (because is necessary for reading usb flash memories) and I could perform the installation from the flash memory.
I can't yet understand why the OS recognises the executable files correctly in this last case and not in the others. They are the same files!!
Thanks!!
Totally strange. I have no ideas on that one, but glad you got it to work.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

System requirement for the LV and VISA run-time library

Dear
My application built from LV8.2.1 didn't run on the old-fashioned notebook, which was under XP and 256 RAM.
(The application was tested successfully in several times in other computer.)
In the only first running, there was no problem.
But after that, the application executed "twice" and one of two couldn't be removed even in Windows Task Manager.
(I had to switch off the computer for restarting PC)
However, I am not sure if this problem is a kind of the library's bug but suspect the out-of-fashioned notebook.
What's the minimum system requirement for the LV run-time library and VISA runtime library of version 8.2.1?
Or any other check points?
Lee
메시지가 08-07-2007 02:03 AM에 labmaster에 의해 편집되었음

Thank you, falkpl and smercurio_fc.
Of course, my application and the libraries have no problem in other computers.
There were no error messages but it seemed not to run normally.
My application had to show a status message prior to a VISA routine, but only a blank in the status control.
When I click the application one time, the application was not launched.
Then the two same applcations were appeared in the second click.
One of two applications could be removed by the Taskmanager. (malfunction of the program exit button.)
But the remained one can't be exited by the Taskmanager or Exit Windows.
Maybe, I had better remove the XP and then try again.
Anyway, I can't understand the reason why any NI Labview developer remained in silence for this kind of postings.
메시지가 08-07-2007 08:43 PM에 labmaster에 의해 편집되었음

Error when importing static files in run-time installation

Hello all,
I have a development environment running 3.2 and also a run-time test environment running 3.2. I'm trying to import an export of static files from the development environment into the test environment, and we're getting the following:
SQL> @static_file.sql
Set Credentials...
Check Compatibility...
API Last Extended:20090112
Your Current Version:20090112
This import is compatible with version: 20090112
COMPATIBLE (You should be able to run this import without issues.)
Set Application ID...
...static file repository
declare
ERROR at line 1:
ORA-00001: unique constraint (APEX_030200.WWV_FLOW_HTML_REPO_IDX1) violated
ORA-06512: at "APEX_030200.WWV_FLOW_HTML_API_PRIVATE", line 84
ORA-06512: at "APEX_030200.WWV_FLOW_HTML_API", line 45
ORA-06512: at line 6
We've exported and imported these same static files in the past with no issues, and we also exported and imported two applications and an image export without issues.
Any idea what is causing this?
Thanks!
John

Update:
I had two static files in my export - one was assigned to a specific application and one wasn't. When I ran into the issue importing, I had elected to export "all static files". I just tried it again, but exported and imported each of them individually, and it worked fine so I'm back in business.
But perhaps there is an issue when exporting all files, when they aren't all assigned the same way? Maybe something to be looked into...
John

Receive an immediate Run Time installation error

Hello,
I just formatted my machine, installed windows, installed the latest drivers, performed Windows Updates, installed Acronis, Installed Office 2007, performed Windows Updates.
I download the install_reader11_en_mssd_aaa_aih.exe file and run it.
I click Next on the Adobe Reader Update Preferences.
Just in Time Debugging: An exception 'Runtime Error' has occurred in script.
Script Editor says: Cannot create Application Data Folder.
Thank you.

Thank you Pat.
I tried your first suggestion of right clicking and "Run as Administrator" but that didn't help.
Installing from Adobe - Adobe Reader Distribution the link you provided worked. I successfully installed Adobe reader.
Thank you. Now I can go to sleep.

Visa Control grayed out when executable used with Run-time Engine

When I run an executable on a machine with only the Run-time Engine the Visa Control for Com Ports is grayed out. I'm guessing that I am missing a library, but do not know which one.

You need to install the VISA run-time. If you are just using VISA for serial communication, then there is an option on the app builder (Installer Settings>Advanced) for Serial Port Support. This will add a much smaller version of the VISA run-time engine to the installer you create. If you are using GPIB, etc., you have to install the hardware driver (i.e. NI-GPIB) and the full VISA run-time engine.

How to specify a different directory for the Run-Time Engine?

With LV 7.1 it's become even more difficult to create installation sets in third-party tools without having to include the full run-time engine separately.
If you use any of the advanced analysis VIs you have to install the run-time engine (no use in including files in the same directory as the built application) and if you do and you use the old serial VIs you get a problem because the application will load the run-time from the main run-time installation and then look for serpdrv in that directory, not in the application folder...
So - being forced to use the installer builder in the application builder and include the run-time engine in the installation kit I wonder whether it is possible to specify where the run-time should be installed?
By default it will go in a directory called National Instruments in the program files folder, however that is not ideal due to the fact that the users have no relation to the fact that our application needs something from NI...and may end up deleting the directory ("National Instruments? - what do I need that for...let me delete it...). We would like to be able to specify that the run-time is installed silently in a directory named with our company name instead.
MTO

When you create the stand alone, in options you can actually set the temp directory and default directory. You can change it there OR in goto options and check for libraries/directories. You can change it there too.
Kudos always welcome for helpful posts

Licence NI VISION Run-Time Engine

Bonjour,
Je vous envoie cette question parce que malgré le nombre de doc que j'ai pu trouver en relation avec ma question, je n'ai pas eu de réponse clair à mon pb :
Je possède une application qui a été développé avec LV 8.2.1 faisant appel à des fonctions issues de NI IMAQ 3.7. (Très brièvement le programme acquiert des images provenant d'une caméra, réalise des opérations simples sur les images et enregistre les resultats de ces opérations, donc d'autres images).
J'aimerai savoir quels sont les licences que je dois acheter pour installer la version compilée de mon prog sur pc client (qui ne possède pas LV). (Je sais deja que je devrai acheter pour chaque PC client une licence IMAQ 3.7 mais concernant le traitement de ces images puis-je me contenter de NI VISION Run-Time Engine 8.2.1 qui me semble-t-il est gratuit de la même façon que NI LABVIEW Run Time Engine 8.2.1)
Merci d'avance pour vos réponse qui je l'espère m'aideront à voir plus clair entre les IMAQ vision, vision run-time, VISA Run-time....
Solved!
Go to Solution.

Bonjour fabrice91,
Le NI-VISION Runtime est disponible au téléchargement et ce
gratuitement, cependant lors de l'installation
il te faudra l'activer. Lorsque tu crée un exécutable LabVIEW n'intègre pas
automatiquement de Run Time Engine, c'est pourquoi il te faut créer un
installeur qui contiendra le RTE de LabVIEW et de NI-VISION. Si tu lance l'exécutable
sur le poste de développement il est normal que ton application tourne car tu
as tous les Runtime nécessaires sur ce poste. Par contre si tu essaye de lancer
ton application sur une machine où il n'y a aucun logiciel NI ton exécutable ne
devrai pas fonctionner et c'est là que vient ton installeur. Pour connaitre les
programmes National Instruments installés sur un PC tu as plusieurs
possibilités soit de passer par Measurement & Automation Explorer soit
Démarrer >> Panneau de Configuration >> Ajouter/Supprimer des Programmes
>> Logiciels National Instruments.
Benjamin R.
R&D Software Development Manager
http://www.fluigent.com/

Run-Time Engine Installation ?

I currently have LabVIEW Developer Suite 6.0 for both PC (Windows NT/2000) and the Mac OS . We are developping a number of executables that will be run on Windows NT 4.0 hosts . I have a few questions.
1.) Is there an installer for the run-time engine that I can use to place the run-time engie on the image of the target machines. I have stumbled on the back-door method of including the run-time installation in the installer for an application. but I would prefer to install the run-time engine once on all of the target machines (there are about 60 of them).
2.) Are executables cross-platform ? Will an executable that is built on a PC/MAC run on a MAC/PC ?
3.) Does anything change when we get LabVIEW 6.1 ?

The installer for the LabVIEW run-time engine can be found at \..\National Instruments\LabVIEW 6\AppLibs\installs. You will need separate run-time engines for the PC and Mac as executables are not cross-platform. To run an executable on a PC, you will need to use the PC version of the application builder and to run an executable on a Mac, you will need the Mac application builder. When you get 6.1, if you build an application with it, you will need to install a 6.1 run-time engine.

Visa run time installer in LV 8.2?

Similar Messages

Maybe you are looking for