Programatically determine if Vision Run-Time Engine Activated

I am working with an application that requires the Vision Run-Time Engine. After installation, if the Vision Run-Time Engine is not activated I get a pop-up (Vision Evaluation notice) that is behind my main application window. The pop-up is launched when I am running an analysis with the application (I assume the pop-up is invoked when I am calling a Vision Development VI). It appears to the user as if the application hangs. I can force the pop-up to be frontmost so the user will see the window. However, I'd like to be able to programatically determine if the Vision Run-Time Engine has been activated. This way I will not have to continue to poll for this window after it has been activated. Is there a way to do this?
Also, suggest that this pop-up window should be made front most so this work around isn't necessary. Please take a look into this NI R&D.
Thanks!
Brooks

Hi Brooks,
You should be able to probe the error wire and look at the error message to see if the RTE is activated or not. This is the standard way of programatically checking to see if a license exists.
-N
National Instruments
Applications Engineer

Similar Messages

Does Vision Development Module obviate the need for the Vision Run Time Engine?

I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated. In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons). Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs. I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers. I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine). Does this mean the engine is already installed and ready to run compiled applications? Or do we need to pay for the engine on each computer?

The Development module includes the RTE for that machine.
For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

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/

How to install Vision run-time engine to a desktop PC converted to real-time target

Hi, all
I don't know how can I install the vision run-time engine to a desktop PC which I converted to a real-time target. The same problem applies to installing real-time run-time engine and labview run-time engine to the real-time target. The only way to install software to real-time target is through "add/remove software" in MAX for remote system, but it is not for all types of run-time engine installation.
I am also confused about how to activate those run-time engines for the desktop PC as real-time target.
Please help and great thanks.
Wei

Hi turtle,
Here is a link that explains how to set up a desktop PC as a real-time target. The section for Formatting & Setup should help you the most.
NI Developer Zone Tutorial: Requirements for Desktop PCs as LabVIEW Real-Time Targets
Justin D.
Applications Engineer
National Instruments

NI Vision Run-Time Engine 8.2 - Error user is now getting when attempting install of built software

I've built an installer for an application using LabVIEW 8.2 and Vision8.2. I have sent this installer to someone for 6 months and they have had no problems completing the install.
Now the last time that I sent the installer, the user is getting the attached error during install.
"NI Vision Run-Time Engine 8.2
Error: Another installer or uninstaller is running.
Finish that installer or uninstaller and try again."
When the user clicks OK to this error, the user is then told to restart or finish uninstall. Since we do not know what uninstall is being asked for, the user restarted the computer and attempted running the software - to which he was prompted for LVWA.dll file and he did not know what to do from there.
I gave the installer to a second beta-tester - the same thing occurred.
The only thing 'of significance' that has changed in my software that I can think of that is Vision related is the inclusion in the software of the ability to read/write .TIF files. I have no clue whether that might have anything to do with the error.
Any help is appreciated. NI - I can post the installer ZIP to your ftp site if you want.
Sincerely,
Don
Attachments:
error.jpg ‏30 KB

Hello Don,
Have you tried uninstalling the previous Vision run-time
engine on the deployed computer before running the new installer? You
might also want to try running the Vision RTE separately from the installer to
see if you are able to manually run it on the target. Here is a document which explains the
procedure for both manually installing the RTE as well as how to include it in
the LabVIEW installer:How do I
Deploy LabVIEW 8.0 and 8.20 Applications with NI Vision 8.0 and 8.2?
I also found
a Knowledge Base that may be helpful addressing the error you mention in your
first post. I hope this helps.
How Do I
Correct the "Another Installer Is Already Running" Error Message?
Regards,
Vu D

Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Sir,
My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Hi,
Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1. I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported. Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later. The Vision RTE version should correspond to the version of Vision you are using. For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed. With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
Regards,
Ryan M.
Applications Engineer

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly). I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine. Is this a bug in the installer, or is there something else I need?

LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular). However, many people have had success installing to various flavors of Ubuntu. You can search these forums using the key Ubuntu and find the problems they had and how they solved them. If you cannot find an answer to your problem, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Unable to locate labview run time engine (lab view 8.5)

Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe I have the following error message:
Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
What I'm missing??
Thanks
Maurizio

are there one other reasons why it would not work. I have asimilar problem.
I intsalled version 8 of run time engine and acrtivated software. Now I am trying to run compiled application provided to me by third party.
When I click on application it says
Unable to locate LV run time engine
Test server requires a version 6.0 or compatible LV engine.
How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

I've created an application installer using LabVIEW's application builder and use it to install NI MAX. However, after running the installer, the VISA interactive control is disabled in NI MAX.
The installer installs the following NI components: NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX. But, the installer created with the application builder does not seem to install the necessary components.
What needs to be added to the installer to enable the VISA interactive control (VISAIC)?
Thanks.
Solved!
Go to Solution.

From Pedro Munoz, Applications Engineer, National Instruments
Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
Here is the download link:
http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
And in here you can find instructions on how to get started with it:
http://zone.ni.com/reference/en-XX/help/374206A-01/
Let me know if you have any question.
Regards
Pedro Munoz
Applications Engineer
National Instruments
http://www.ni.com/support

Installer Error of LabView Run Time Engine 6.0.2 "premature"

I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
Does anyone know what to do is ?
Thanks for Help

It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
J.R. Allen

EXCEL Run Time Engine ?

I'm using one of the vi that ships w LV7.1. It basically reads in an EXCEL file. I'm also using the Report Generation ToolKit to write the final report data of the UUT. Do I need MS Excel installed on my target machine ?? Is there such a thing as a run time engine for Excel ?

As far as I know in the past excel is an activeX object which is installed with excel or office and is part of the licence, so I was under the impression that inorder to communicate with excel (ei through automation) you needed to install the application. HOWEVER, I was recently at a Microsoft developers event (included a session about office 2007 beta) which the speaker mentioned that this will nolonger be the case, you waill be able to automate both excel and work documents without having the application installed on the machine, but not powerpoint. This might have to do with the change in document formats from .doc and .xls to .docx and .xlsx. Essentially the new format will be a zipped XML marked up doccument with much more open format so the office suite in not as needed for automation (opening the way for much more programability and 3rd party software interactions). I could be wrong about needing to install office to get the office support to work for the report generation since I use LV 7.0 and OfficeXP.
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation package for Run-Time Engine 7.0

I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit). The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading. I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013. Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0. If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected). How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0? Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
Solved!
Go to Solution.

Bob_Schor wrote:
Are you running your VI from a Project? If so, you can look at Dependencies and get an idea what "dependent" VIs you might have. There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it. If all of your relevant VIs are in a single folder, add the entire folder. Now look in Dependencies.
BS
Yes I am running the VI from within a LV Project. After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
1. Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
2. Restart the PC
3. Open the project, close the project choosing to "save all"
4. Restart the PC
5. Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
6. Restart the PC
7. Open the project, close the project choosing to "save all"
8. Open the project and run the VI. No more messages about LabVIEW trying to find Run-Time Engine 7.0.

When opening PT Assembler, Windows tries & fails to open NI Run-Time engine

I am using PT Assembler, a front-end for the Panorama Tools software bundle, to stitch microscope images taken by LabVIEW using the QCam Suite. Whenever I attempt to open PT Assembler, Windows informs me that it needs to configure the NI LabVIEW Run-Time Engine 7.1.1, which it cannot as it is not installed. After cancelling the configuration 4-5 times, my program opens and runs without errors.
PT Assembler has absolutely nothing to do with with NI or Labview as far as I can determine, so why does Windows try to open it with the run-time engine? I attempted to install the 7.1.1 engine from ni.com but was informed that it was unavailable. Is there any way I can keep Windows from attempting to use the engine? I could install a later version of the engine and hope it works, but I am a bit leery about how it might affect my program.

Hi rhazelton,
If this program hasn't been created in LabVIEW, then I'm not sure why it would be doing this.. However, you should be able to download the 7.1.1 run-time here. Give it a try and see what happens!
Regards,
Brian A.
National Instruments
Applications Engineer

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

Programatically determine if Vision Run-Time Engine Activated

Similar Messages

Maybe you are looking for