A query on the LabVIEW runtime engine.

Similar Questions

• System error 31 during the loading of the LabVIEW runtime engine

  I get the following error message.  I've attached a screenshot of him as well.

  System error 31 during the loading of the LabVIEW runtime engine (\\lvrt.dll)

  I'm trying to update an instrument running Windows 95.  What is system 31 error?  I can't find anything on this topic using Google or the search function of the forum.

  The instrument is a Romulus-IIIA of the Quad.  Chasing the assistance on their part as well.

  Hi Szandstra,

  See the knowledge base article describing what you see.  Follow the steps there to correct the problem.  Have a great day and let me know if this solution does not work for you!

• What are the requirements of the system for the labview runtime engine 2011

  Hello

  I'm looking for (ideally 2011 release) LabVIEW runtime engine requirements. The only information I can find a few States what operating systems it supports. I am eager to check the specifications of a target (Touch Panel computer - probably running Windows XP Embedded), to allow this execution. More precisely the amount of non-volatile storage system required - because we will need to specify a CompactFlash card. Clearly the application exe take little space like XPe will, but I'm eager to know the needs of the TENS.

  Andy

  Not sure about flash complact...  I can't remember seeing it in the relase notes, but follow the link below for the Manual:

  It should support the touch screen (I don't remember if you still need an additional plugin for this... I'll check).

  http://www.NI.com/PDF/manuals/371778g.PDF

  Look at page 2, the middle column

  or below the basic requirements:

  

• Can I use the labview runtime engine 2010 with my LV 2012 program?

  Hi all

  I get the new Labview Developer Suite 2012 DS2 in a few days and

  I wonder if it is possible to run LV2012 programs on the LV 2010 runtime or is it necessary to update all my customers to the 2010 to 2012 runtime?

  It is essential to have the runtime for the LV version in which the code is developed.

  If you plan to distribute the new code stored in LV2012, you must also LV2012 engine run.

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

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

• 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).

• 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 7.0 trys to install at the start

  This just started happening, everything was fine a few days ago. Now when I click on the ICON of the LabVIEW office he says he wants to install the runtime of 7.0. And application of disc #3 do I need this?  Finally after the cancellation of the guests for a few minutes, that it loads my opinion lab and my screws appear to work well.

  I, m using the edition of the 8.6 students,.

  Any ideas?

  Thank you

  Alan Martin

  Alan,

  The lvruntimeeng.msi that you said that your program is to research usually resides in your folder to install drivers with a path like this:

  Downloads\NI-DAQmx\\NIDAQC:\National instruments - 1\Products\LabVIEW_Runtime_Engine_71\LV711RTE

  Mine is exactly this way:

  C:\National Instruments Downloads\NI-DAQmx\9.0.2\NIDAQ902-1\Products\LabVIEW_Runtime_Engine_71\LV711RTE

  The 7.1 that runtime is particularly well named "lvruntimeeng.msi". The 8.0 is named "lv80runtime.msi" and 8.2 is "lv82runtime.msi" and so on. Since we can not install this RTE 7.1 because you have a more recent version installed, please check the name of the path described above to see if your 7.1 MSI runtime is there. Maybe even search to see if it is present everywhere on the system.

  Otherwise, we can uninstall and reinstall your DAQmx drivers and reinstall them because they will each Run - time Engine MSI.

  Clearly, there was an accident of file structure and these can generally only be remedied by reinstalling completely the programs installed initially the files.

  Logan H

• Call a VI that uses the 'exec.vi system' with the LabVIEW runtime as adapter

  Hello

  My TestStand sequence called a VI that includes a call to 'exec.vi system '. When I try to load it in TestStand and if LabVIEW adapter is set to the runtime, I get an error message «Unable to load Vi...» ». If I change the map to the 'development system', then it works fine.

  Is it possible to use the 'exec.vi system' in a VI that is called by TestStand with LabVIEW run-time?

  Thank you

  Alex

  Hi Alex,

  In case you, you get an error-18002.

  The reason is explained in the following link:

  -18002 errors in TestStand

  http://digital.NI.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument

  Please take a look at # 2. This is your case.

  It will be useful,

  Regrads

• & quot; incorrect function & quot; error on PostUIMessageEx in Labview with the Labview runtime

  Hello

  I have a TestStand GUI developed in c#. Now, TestStand has some modules Labview which must send the UIMessages to the interface graphic (it is too deep in Labview code to bring back to TestStand to send the UIMessage).

  When I use the complete edition LabVIEW 8.6.1 development version, all right, I can see my messages. Now, when I go to run Labview 8.6.1, the node to invoke PostUIMessageEx gives me an error: incorrect function (error 1).

  I have tried restarting PC/TestStand/Labview without success. Is that all that I'm missing?

  Thank you

  Alex

  
  

• LabVIEW run engine time included in the application exe

  Hi all

  Back in LabVIEW 5, we could create a single LabVIEW application exe file that included the execution engine (all in a single exe file). Now, we must install the runtime engine in its own right + the LabVIEW application exe. I don't think that someone knows a way to create LabVIEW application exe files which include the execution engine in new versions of LabVIEW.

  I know that we can install the runtime automatically during the installation of the LabVIEW application.

  I know also it makes more sense to have the execution time separate from the application of updates etc, but in some cases its nice just have a program obviously installed on the system - the application of interest.

  Any soloutions neat known?

  -Martin

  The time of applications from a single file is long gone. The current LabVIEW runtime engine is a great combination of many files, including DLLs, interface model files user etc. It is not always necessary, but even the most trivial LabVIEW application today takes several tens of these files at startup even. That's how things have changed, and although there are indeed efforts to get apps to run from one place to put them on a USB key for example, LabVIEW is not really a system that lends itself to this. In LabVIEW 7.1 and 8.0, you could include virtually all of the files that make up the runtime system in the same folder as your executable file, no NOR never argued that neither they will probably move to make. With some trial and error, you can start deleting files and see if your app still worked then, but it's a tricky procedure since the application could often start very well, but suddenly encounter display problems if you have opened a subscreen or something with this subject-specific objects.

  You can probably try to simply copy all the files from the LabVIEW Runtime folder in your executable file and there is a chance that it still works, but what for? The size of the facility remains basically the same and if you happen to install both applications on the same computer, each contains a copy of all of the runtime system, so there is no gain more but in fact a setback.

  The interdependencies of these modules are complicated and some need additional components and registry settings to work properly. By offering a way to configure individually that you want to include, and what would be a total pita for the end user that nobody would really understand what is needed for what and why. Experience would be so especially try it doesn't work once, and never use it again.

  I never thought to look into this latest version of LabVIEW. Time to figure it all out is simply average too much punishment for the small gains you get. Installers are the norm these days.

  Another issue that followed, is that you need to monitor all the Security Advisory reports NOR and other bugfixes and act on them yourself whenever a component that you have added in your application must be updated. As it is now, the NI Updater can and will update the plant installed according to enforcement system and all is well.

• NEITHER 9481 relay are not locked when running the labview compiled exe on a computer with only installed labview execution?

  I recently bought a cDAQ-9172 with several modules.  One of the modules is a NI 9481 relay module.  I created an application using Labview and built an exe file.  If I run the exe on the computer, it was developed on the relays work properly, that is, they remain locked up until their status is changed.  If I run the same exe on a computer with only the Labview runtime installed (no software installed), the pulse relay contacts and not locked.  I'm using Labview version 7.1 for my development and execution.  Everyone knows about this problem?

  Ignore this announcement, the error stems from a difference between each computer ini-files and has nothing to do with the Labview Labview runtime vs, my bad developer.

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

  Hello, I am curious to know if anyone knew if it is possible to install and use the two separate versions of the LabVIEW Run-Time Engine on a PC?  I have currently 2009 runtime engine installed on a machine, and I wanted to install the runtime for 2011 as well. I know that you can run two separate versions of the LabVIEW program on the same machine, but what about the Run-Time Engine?

  Thank you!

  No problem at all. I currently have the engines of execution for 8.2, 8.6, 2009, 2010 and 2011 on my computer. Multiples are no problem at all. Go ahead and load.

  Rob

• Installation of the LabVIEW 8.5.1 runtime error: "this application has requested execution to terminate in an unusual way.

  Hello

  a colleague in India can not install runtime LabVIEW 8.5.1 on Windows XP. On try installing, an error box appears, which says:

  (window title)

  Microsoft Visual C++ Runtime library:

  (text of message box)

  Runtime error!

  Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe

  This application has requested the execution to terminate in an unusual way.

  For more information, contact the application support team.

  http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg

  I found no relevant clues for that in the forums of NOR. A Google search led me to http://support.microsoft.com/kb/884538/en-us, offering a fix for the problem. Unfortunately, the installation of this hotfix does not solve the problem.

  You know this problem and you have any ideas, how can the problem be solved?

  Thanks in advance.

  Best regards

  Manual

  Hello

  Thanks for your replies. It seems that our colleague-IT solves the problem. Installing Windows XP for the India via the network of the company was defective.

  Best regards

  Manuel Haderle