NEITHER VISA version to install runtime engine?

Similar Questions

• [LabVIEW 2013] Update Service NOR recommend to install the update for the 2012 LabVIEW runtime engine

  Update service NOR recommend to install the patch f5 for the 2012 LabVIEW runtime engine. However, I have LabVIEW 2013 currently running on this computer and never had installed LabVIEW 2012.

  Is this expected behavior and it is actually recommended to install this update?

  Hi mest,.

  Details of the full patch for f5 patch are available in this knowledge base article. As a general statement, we encourage everyone to install the patches as soon as they are available through the Update Service, especially if they are marked as Urgent (it is not marked urgent). In this particular case, it is unlikely that you'll turn to all the problems solved by the f5 2012 SP1 hotfix since you use LabVIEW 2013.

  The reason why you see the update in the update service is LabVIEW 2013 installs several versions of the runtime LabVIEW, so Update Service sees that you have on 2012 Run-Time Engine installed and invites you to patch.

  Kind regards

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments

• NEITHER Measurement & Automation Explorer 5.0 (superior version already installed)

  I have downloaded the driver NOR-DAQmx 9.4, but when I try to install it I get the message:

  Cannot install

  o OR Measurement & Automation Explorer 5.0 (superior version already installed)

  What does that mean? I have LabVIEW 2012 (Windows), version 12.0, 64 bit.

  Thank you

  Neil

  I think what is happening is that DAQmx is installed correctly, but the installer also try to install an older version of Measurement & Automation Explorer (MAX), which is what causes the error.

  You can check that DAQmx has been properly installed by opening MAX and check if it is listed on the software tab on the left.

  One thing to keep in mind is that 9.4 DAQmx is not compatible with LabVIEW 2012, so you can just upgrade to the latest version of DAQmx, which is 9.6 and is compatible with LabVIEW 2012.

• LabVIEW Runtime engine

  A strange thing has happened here: we have an old PC installed with a full version of labview software. An engineer has developed a Labview GUI. We can use this GUI to connect with our controller card using the RS232 port.

  Now, we want to use this labview GUI on another PC. I think it is unnecessary to install labview in the new PC software, but a labview runtime engine. Okay, so I downloaded and installed the runtime of 8.5.

  However, the GUI doesn't have to establish communication with my controller card... MISTLETOE can still be opened but no communication with my Board. No error as well...

  Can someone give me some advice?

  Thank you very much!

  If your application uses the functions of NI-VISA, then you will need to install the runtime of VISA on the target computer as well.  Way the easiest way is to create an installer that includes the runtime of LV and the execution engine VISA.

• LabVIEW Runtime engine on Windows Embedded Standard 7 P 32 / 64-bit?

  Any who tried never to install and run the LabVIEW Runtime Engine (2011 or later version) on Windows Embedded Standard 7 P 32 / 64-bit?

  I'm trying to figure out if this will work, for example on a CX5120 PC Beckhoff embedded. I have to have some TCP/IP communication simple to exchange information with another PC, but nothing else, i.e. drivers, etc...

  I hope that someone tried to do already. I don't have the right equipment now to check it out.

  As NEITHER sells touchscreens with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume that they used the RTE on WES7.

  But yes, it is done.

• Last runtime engine does not support XP

  Hi all

  A few days ago I started to create a dll using LabWindows/CVI 2015 (Evaluation Version, Version 15.0.1 (239), 15.0.1.239 execution engine), installed on a Windows 7 Professional SP1 system.

  The dll will be used within an application running on the system CVI target as operating system with Windows XP Professional SP3. The runtime there is version 12.0.0.422 (CVI 2012).

  As the version of the runtime on the target system must meet or exceed those on the development system, I tried to install the runtime SP1 CVI 'NILWCVIRTE2015SP1.exe' on the target system. But I got the message "this installation requires Windows 7 SP1 or later", which ultimately is the requirement of system given to the OS (-> Windows 8.1; Windows 8; Windows 7; Windows Server 2012 R2 64-bit; Windows Server 2008 R2 64-bit).

  What can I do to get my dll run on XP-target system?

  Usable for XP 2015 runtime probably does not exist?

  Installation of the CVI 2012 dll on the system development and compilation/build there is probably a solution, but are there other possibilities?

  Thanks for your help,

  NewInCVI

  Meanwhile, I have a working solution that I can with my (small) project.

  As it is also recommended, I decided to install the CVI on the XP machine. I chose CVI 2012, not 2013. The reason is simple, other members of the team use CVI 2012 and have licenses and of course also the installation CD. Due to lack of license for me I install on XP (as my PC Win7 2015) as a trial version, which is enough for me for now, what about the time that I need.

  So currently I develop my application as part of the ICB 2015 (as it is a bit more at ease working in the office and not in the laboratory), "carry" her updated source/header/whatever - XP machine and compile/build there the project files new/still once, that's all. And who works for me (of course, the code created less than 2015 must be compatible toe 2012 coding).

  So, thank you much for the help.

  and maybe see you in another topic,

  NewInCVI

• Installation of LabVIEW Runtime Engine 2016 compatibility questions...?

  Hi, I have just a quick question...

  I just download LabVIEW Runtime Engine 2016 in a PC at work. I need to run a VI in this PC that has a few executables 2015 VI for the moment. My question is, if I install the runtime from 2016:

  • Will there be any problems with executable files that have been compiled with the version of LabVIEW 2015?
  • Or these VI is fully compatible with Runtime 2016?

  Thank you in advance to all!

  JLuna wrote:

  I just download LabVIEW Runtime Engine 2016 in a PC at work. I need to run a VI in this PC that has a few executables 2015 VI for the moment.

  I guess 'the PC' has already the LabVIEW 2015 engine run. It is still necessary to run the executables of 2015. You must install the engine LabVIEW 2016 run if you also want to run executables built with LabVIEW 2016. Both the run-time engine can be installed at the same time.

  In order to run screws, you need the LabVIEW Development System. LabVIEW 2016 can generally open, recompile, and run screws LabVIEW 2015 (and many old versions, Details).

• Difference between the version of the Runtime and Developer version of LabVIEW.

  What is the LabVIEW Version called the runtime?

  Is this only for the visualization of the screws built in developer version LabVIEW?

  Can't we develop or modify TENS of LabVIEW version screws?

  vaibhavinegi wrote:

  What is the LabVIEW Version called the runtime?

  There is a version of the separate Runtime for each version of LabVIEW.  You can open NI MAX and develop software to see what is installed on your computer.

  Is this only for the visualization of the screws built in developer version LabVIEW?

  Without the development environment, you cannot change screws LabVIEW.  The runtime engine is responsible for actually running the code in order to integrate LabVIEW executables and run them on other machines without the development environment.

  Can't we develop or modify TENS of LabVIEW version screws?

  NO.

• Including the old versions of the runtime of the CVI in one installation program after the upgrade of CVI

  Hello

  I have a computer with CVI 2010SP1 that I recently installed CVI 2012 on.  I've noticed now that every time that I create an installer with CVI 2010SP1 which includes the runtime of the ICB, it's now, including the 2012 CVI runtime engine.  My guess is that this is because the installation program of the ICB 2012 updated modules of fusion in C:\Program Files\Fichiers communs\Merge Modules that it seems like the two versions of the CVI go when building their installers.  My first thought is to some how get a copy of the merge 2010SP1 CVI modules and manually add those to the installer.  Would this work, or there at - it an easier way, I'm missing?  Thank you.

  Hi tstanley,

  Unfortunately for this case as CVI 2010 was made before the install side-by-side feature, it is recommended that if you want to create an application that uses only the CVI 2010 Run Time you will have to downgrade of the CVI Run-Time installation of the development machine (which has some aspects to know as mentioned in the article) or have a separate computer that can be used to create the 2010 CVI based distributions.

• standard record path with the version of the runtime

  Hallo!

  How can I change the standard economy path on a PC where only the version of the runtime is installed?

  Thank you and have a nice day

  Hilby

  
  

• A query on the LabVIEW runtime engine.

  Can I access front of LabVIEW through Internet Explorer even if I do not have LabVIEW installed in my computer?

  The LabVIEW runtime engine works in this situation without the help of LabVIEW software?

  > Can I access front of LabVIEW through Internet Explorer, even if I do not have LabVIEW installed in my computer?

  Yes

  Server must have the labview, labview Web Server runtime and should be run remotely front panels.

  > LabVIEW runtime engine works in this situation without the help of LabVIEW software?

  Does not understand the question.

  Engine run LabVIEW is a LabVIEW software, which is required to run files executable labview. In the case of remote façade panels screws (exe) running on the server that has the run-time engine. Page Web you are viewing in the browser (client) gives you a picture and monitors where you click on it. It passes those clicks to the server, it changes picture accordingly (going on those clicks for labview, gets the update of this photo). Customer does not screw, so should not be the runtime of LV.

• Setup using LV Runtime Engine 2010 build error

  I had an executable and installer work which was built in LV2009.  Since then, I changed my source code and registered as LV version 2010.  I have rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that it had LV Runtime Engine 2010.  So I tried to rebuild the installer using LV Runtime Engine 2010 as an extra Installer.  However, this version was missed and I got a long error msg that I don't understand (see attached).

  Thanks in advance.

  See this knowledge base article . There are a few possible solutions listed.  Let us know if these don't work.

  Error code - 12 creating an installer of LabVIEW or LabVIEW SDK installation.

  http://digital.NI.com/public.nsf/allkb/afc375154efbd6ae8625760b005fb723

• Install the engine 6.1 enforcement (or compatible) labview with the labview 2011

  I installed a Labveiw 2011 trial version in order to check for potential problems to upgrade, I get if I decide to spend labveiw 6.1. Well, needless to say, there has been a lot. This is as expected because I have not updated labview for many years. I'm still not under any pressure to update; However, I want to in order to get help and make sure that I have no problem of compatibility with new equipment purchases. I was able to solve most of my problems of compatibility with code simple and other corrections. However, twice now I ran into an error at the launch of labview executeables compiled by two different manufacturers. The equipment I use is not yet old... maybe a year or two. When I run labview executables for the device on a PC that has the trial period 2011 installed labview under control, I get an error message saying something like "this requires a motor enforcement 6.1 (or compatible) of Labview. I tried to download and install the labivew engine 6.1 but I can't install this engine on a PC that has labview installed 2011. Can someone explain how I run these executables under labview 2011. I can't imagine that these executables were developed using 6.1 as this equipment is not yet a year old now.

  You should be able to have a number any time installed and 2011. I have several versions back to 7.0. I asked what exactly happens when you try to install it.

  Have you tried 2011 withdrawal, execution 6.1 installation and then installation of 2011?

• HOW TO OBTAIN MICROSOFT WINDOWS NT VERSION 4 INSTALLED ON MY WORK OF WANY GAME STARTING WITHOUT HIM

  HOW TO GET MICROSOFT WINDOWS NT VERSION 4 INSTALLED ON MY WORK PLAY WITHOUY WANT TO COUNT

  Hello

  Older programs may or may not work in Windows 7. I suggest you to run the troubleshooting of Microsoft Compatibility utility to determine this.

  ·         Open the program compatibility problems by clicking on the Start button, then Control Panel. In the search box, type Troubleshooting, and then click Troubleshooting. Under programs, click run programs made for previous versions of Windows.

  ·         For more information, please visit the link below,

  http://Windows.Microsoft.com/en-us/Windows7/open-the-program-compatibility-Troubleshooter

  Hope this information helped!

  Kind regards

  Arona - Microsoft technical support engineer
  Visit our Microsoft answers feedback Forum and let us know what you think

• The module:c:\progra~1\common~1\instal~1\engine\6\intel3~1\ctor.dll deer is a module of windows xp

  When I try to uninstall DVD SUITE from my computer, I get this message:c:\progra~1\common~1\instal~1\engine\6\intel3~1\ctor.dll is not found, can not move forward the process.has a way to achieve this module? Thank you!

  Oh no! Not garbage InstallShield act again. I swear to you that it is must be the worst piece of software ever written. No way to uninstall it, etc.

  OK, rant over. :)

  Try Revo Uninstaller Portable (I prefer just portable versions ;)) to uninstall.