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.

Similar Messages

  • Unable to locate the LabVIEW Run-Time engine

    Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
    I can't go forward or backwards!
    Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
    In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
    At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
    What could be causing this problem, and how do I get past it??
    Thank you.

    One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
    The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
    I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
    Good luck.
    Dan

  • Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

    Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC?  I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
    Thanks!
    Solved!
    Go to Solution.

    I'm guessing this is a bug that NI needs to fix.  I see no reason you shouldn't be able to install the run-time engine of an older version.  I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine.  There are some command line switches for NI installers as mentioned here:
    http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
    I wonder if there is a force install option.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • 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

  • 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

  • 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

  • UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

    UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
    Uninstalled DAQ and reinstalled.  MAX still throws an error. 
    Any Isead besides uninstalling 3/4 of my software?
    Merry Christmas!
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

    To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility.  To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue.  Thank you!

  • Teststand error states that a vi failed to load in the Labview Run-Time Engine

    I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
    If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
    How do I get this VI to run on this system when it is called by test Stand?
    Thank you

    The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
    I do not have labview loaded on this system, only the run time engines from running my deployment.
    When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
    Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
    I have attached the teststand sequence if this helps.
    Thanks
    Attachments:
    QuantumDigitalBd.seq ‏13 KB

  • 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

  • Why do different versions of the LabVIEW Run-Time Engine not compatible?

    LabVIEW Run-Time Engine to become more and more big
    Why do different versions of the LabVIEW Run-Time Engine not compatible?
    " 一天到晚游泳的鱼"
    [email protected]
    我的个人网站:LabVIEW——北方客栈 http://www.labview365.com
    欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview
    Solved!
    Go to Solution.

    jwdz wrote:
    LabVIEW2020 ....... ,it look like?
    You need to express your ideas more clearly. We cannot fill in the blanks and read between the lines if the post has no substance.
    jwdz wrote:
    It will affect the future development of LabVIEW, right?
    What is "it"?
    There are many things that affect the future development of LabVIEW, starting with NI management, all the smart people in LabVIEW development, the economy, the LabVIEW users, etc.
    If you are worried about the increasing size of the distribution, the good news is that the cost of data storage and data transmission has dropped much more dramatically. Even though newer versions are bigger due to great and welcome new features, the improvements in infrastructure have actually made the distribution and storage significantly easier over the years and will continue to do so. Trust me!
    Nobody wants to go back to a LabVIEW version that fits on a floppy disk!
    LabVIEW Champion . Do more with less code and in less time .

  • System Error 998 While loading the Labview Run-Time Engine

    Hello.
    I have a DLL made with LV 7.1 I run the dll using a C compiler and works great in WINXP, but cannot run in Win2K. Error is:
    "System error 998 while loading the Labview Run-Time Engin(c:\program
    files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
    READVOLTAGE requires a version 7.1 (or compatible) Labview Runtime
    Engine. Please contact the vendor of READVOLTAGE to correct this
    problem"
    READVOLTAGE is my function inside the dll. The runtime is already
    installed. I tried it in another WINXP running machine and works fine.

    This is actually a Microsoft bug with statically loaded DLLs. There are a couple of workarounds for it, and I have included two links below to posts that address this issue:
    Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC
    I get error 998 when calling a LabVIEW buildt DLL from MSVC++
    Kind Regards,
    E. Sulzer
    Applications Engineer
    National Instruments

  • System error 999 while loading the Labview Run-Time Engin

    Bonjour à tous,
    J’ai un PC avec un Runtime LV71.1 qui me retourne l’erreur suivante. Je ne trouve pas d’info sur cette erreur. Une Idée sur la cause ?
    System error 999 while loading the Labview Run-Time Engin(c:\program files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW
    Résolu !
    Accéder à la solution.

    Bonjour Maxime, merci pour ta réponse qui est très intéressante. Le soft est en LV7.1.1 est fonctionne depuis plusieurs années. Le PC est chez un client, dans un pays très « hostile », je n’ai donc pas accès à ce dernier. Un superviseur local m’a fait le retour qu’après redémarrage du PC ce dernier indiquait un problème, avec photo pour descriptif. Je n’ai pas plus d’info pour le moment. Je viens donc de demander un CHKDSK c: /F
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

  • 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/

  • System Error 31 while loading the LabVIEW Run-Time Engine

    I'm getting the following error message.  I've attached a screen shot of it as well. 
    System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
    I'm trying to update an instrument running Windows95.  What is system error 31?  I can't find anything on it using Google or the forum's search function.
    The instrument is a Romulus-IIIA from Quad Group.  I'm pursuing assistance from them as well.
    Solved!
    Go to Solution.
    Attachments:
    Winzeta Error LabVIEW.JPG ‏17 KB

    Howdy Szandstra,
    Check out this KnowledgeBase article describing what you are seeing.  Follow the steps there to correct the problem.  Have a great day, and let me know if that solution doesn't work for you!
    Sincerely,
    Chris G in AE

  • Does CVI install the LabVIEW Run-Time Engine?

    Hello,
    running the NI Update Service suggests to download a 226 MB patch for the LabVIEW 2012 Run-Time Engine... (all I installed knowingly was CVI2012)
    --> How can I check if the computer has this engine installed, what is the file name to search for (and is it needed by CVI)?
    Thanks!
    Solved!
    Go to Solution.

    Hello,
    1) You can use Measurement And Automation Explorer (MAX) to see the National Instruments Softwares installed:
    2) Some CVI softwares use the Labview runtime.
    By example, when you use the CVI Menu: Help / Find Examples... , you launch NIExampleFinder.exe which uses the labview runtime:
    3) When you install the NI-VISA library, the software C:\VXIPNP\WinNT\NIvisa\NIvisaic.exe is also installed. This utility is a Labview Software.
    I think it's difficult to avoid the Labview runtime on a computer with NI softwares installed...

Maybe you are looking for

  • Eliminating 'the big white box ' on load

    In the second or two before my flash page appears with normal preloader etc, the size of the flash element is always shown a s a big white box over the surrounding black page...my background color is set to black on both the flash and html page conta

  • Inquiries vs. Customer Contacts

    I pulled a Inquiry report for the past 3 months and there were 104 inquiries. Our customers submit inquiries by filling out one form. I pulled a Customer report for the past 3 months which provides the Contact information for these inquiries and ther

  • Help for cellular data settings

    i purchased i phone 4 from duty free and it was working with MTN Rwanda, option of cellular data network was present. But when i shifted to airtel India that option disappered. will data work on my phone when i go to India or how can i manually insta

  • My history keeps deleting itself.

    The history from "today" is the only history that is saved. Every time I close my browser, the history is erased.

  • Is there a way to get ONLY UNREAD mail on my iphone and ipad and ALL mail into Outlook on my computer?

    When I'm out and about, I pick up my mail on my iPad and/or on my iPhone. I HATE having to sift through the duplicates. I know I can delete the emails from the server as they are being downloaded, and that would solve the problem between the iDevices