Access a queue within a labview application .exe built

Similar Questions

• Stand-alone labview application (.exe file) does not run correctly

  Hi all

  I'm doing a labview application only to run on another computer (I never did this before).

  I went through the tools-> build application prompts and was able to build an exe file.

  the program is supposed to control a power meter and measures of power, then save them in a text file.

  When I run the exe, on the same computer, I compiled the exe, the program generates a text file to save data to, but he cannot communicate with the electricity meter.

  There are a few screws Sub and a dll file that are used to communicate with the electricity meter. Would it be possible that I am not say labview to correctly

  include these files when I create an executable?

  What are some common problems that arise when building stand alone applications that could be cause of my problems?

  And no one knows of any good tutorials on building applications stand alone in labview, other than the help files OR?

  Thanks for your help,

  Also, if you used the VISA, include the runtime with your Installer.

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

• How to develop the final application exe file that will work on PC not installed labview

  Hello

  I developed a labview application (I request manufacturers/builders and professional license).

  I generate the final exe file by the tools of-> built Application exe of VI-> fact file

  But this the application exe file runs only on machines installed labview. His works do not on the other PC.

  For the execution of the other PC I have to do.

  Hello Ramji,

  As you said, EXE is created by you and its nning ruou fine on the PC where you created such as LabVIEW is present there.

  So for LV CE, please create an installer and Add Installer/additional software required by your EXE.

  Look at the link for reference.

  http://www.NI.com/white-paper/5406/en

  Kind regards

  Leila

  CLD

• Can place my labview application on a public website .exe

  Hello

  If I created a labview application only .exe and want to publish it on a public Web site so anyone can run it.

  Is this feasible? If yes how?

  Please, step by step.

  Yes, the computer that hosts the application requires the LabVIEW run-time engine. Panel will also require a licence for each connection. This is explained in the article I linked to.

• debugging a standalone application (EXE)

  Hello

  I have an application that uses ActiveX controls to communicate with two different cameras at the same time.

  I have a simulation environment in a computer where I got installed Labview 2014. Here, I built my program, and it works well.

  I created an application (EXE) and then tried in another computer that is isolated from all the networks, but it is the computer that manages the two devices directly.

  The program works very well, with the exception of a few minor errors. I want to debug the program on this computer, but I can't do it remotely, and it has no installed labview or.

  Do you know if there are any tools or ways to see my block diagram of the application or to see some of its settings while running?

  I find that this article

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

  but it does not apply to my case because I have access to no distance to the computer that is running.

  Thank you

  A method proven (and very old!) who will work with an executable is to build in logging functions.  I got a program in real time which seemed to lose of ticks.  He was already streaming status information for the PC, but something to 'lose '.  I added code to write to a local log file some 'Debug' information, including the State of some of my digital and found lines where my 'assumptions' on my code were false (i.e. my stupid mistake).

  Depending on your situation, which can involve a lot of text to read, but that's why we have with matching text editors...

  Bob Schor

• Creation of LV8.5 application EXE, Error 1502

  Hello

  I am building an application .exe of my code of LabView8.5. This is my first time doing so.

  My VI program works very well and has no errors.

  However, when I try to compile the application, I get the error

  Error 1502 to the node invoke in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

  Possible reasons:

  LabVIEW: Cannot save a bad VI without its schema.

  Method name: Save target: Instrument

  To my knowledge, there is no bad VI, like the VI to run ok in LabVIEW!

  Thanks for your help,

  David

  Construction of an exe does not actually include the dependencies, so you will be required to ensure that the dll is present on your target computer or build an installer that automatically places the dll on the computer.

• . Misfortunes of ICO in the Windows registry for my LabVIEW Application

  Wow, adding that last bit of spit-and-shine in a LabVIEW program can turn into any process.

  I defined a type of file with a .tpml (XML file of the temperature profile).  When my user double clicks on a file of this type, it launches my LabVIEW application.  All this is worked and works well.  I even setup for my program add entries to Windows registry key so that the .tpml file type is associated with my program executable.  This is related to my previous post here.

  The problem I have is that I did a fantasy for my LabVIEW program icon and these well DOCUMENTED files.  The problem is that the key of Windows registry entry that associates this file in my program, causing the ATTESTED to the 16 icon file icon x 16 my program executable.  If I remove the association in the register, it goes back to the .ico file I made.

  I don't know if I can add my ATTESTED to my .exe file icon so that an association between the two causes the correct icon to be displayed in Windows, or if there is some other entry registry key that I need to do to replace Windows and requires to use my DOCUMENTED file. ICO for the icon.  Anyone know?

  These are the registry keys that makes my Installer:

  HKEY_CLASSES_ROOT\

  .tpml = "tpmlfile".

  . tpml\DefaultIcon = [INSTALLDIR] data\TPMLFile.ico

  tpmlfile = temperature profile XML file

  tpmlfile\shell\open\command = [INSTALLDIR] Profile Editor.exe '%1 '.

  I have all of the isthmus and the brightness I want in this program with the exception of this problem with the icons (less a few problems the keyboard TAB).  As I said, if I remove the entry "tpml\shell\open\command" in the registry, the DefaultIcon works OK.  With this registry in place entry, it uses by default the icon 16 x 16 for "Profile Editor.exe".

  Any ideas?

  Thank you very much for your time and input!

  -Nic

  The solution was that I needed the DefaultIcon key as a child of tpmlfile entry NOT .tpml.  Here is my final registry keys that work like a champ!

  HKEY_CLASSES_ROOT\

  .tpml = "tpmlfile".

  tpmlfile = temperature profile XML file

  tpmlfile\DefaultIcon = [INSTALLDIR] data\TPMLFile.ico

  tpmlfile\shell\open\command = [INSTALLDIR] Profile Editor.exe '%1 '.

  -Nic

• Building an application (Exe)

  Hey guys I'm building an application of my VI in labview 2012 but there is no application (exe) option when I right click the specifications of construction even if I saved the project. Please check the attached snapshot.

  If you purchase and install, professional LabVIEW or LabVIEW Development Suite, Application Builder is included otherwise you need to install it as a separate add-on.

  Refer to:

  http://www.NI.com/LabVIEW/buy/

• How should I treat the files that have been opened by using my LabVIEW application?

  Hello!

  I want to put the code in my LabVIEW program that she will handle a file opened with.  Let's say I have create my app as an .exe.  I have my .exe associated with a particular file type in Windows.  If the user double clicks on the file, it will launch my labview application.

  How can I get the information in path of file of the file that the user has clicked on in my code so I can handle?

  Thanks for your time!

  -nic

  @Ravens-

  If you put:

  SuperSecretPrivateSpecialStuff = True

   

  In your file LabVIEW.ini, it will unlock an "OS Open Document" event to use in a block Structure of the event with a 'File Path' node on the left side.  Whenever the application is launched via a file of the operating system, this event fires (even if your application is already up to-and-operational).

   

  Works like a champ and is enough would apply us!

   

  This method was published in the forums JKI.

• LabVIEW application developed on windows can be installed under linux?

  Hi all

  I use suite developer LabVIEW 2009 on windows 7 PC. I was wondering if the application created with labview on PC can be deployed on the linux platform? If not, is it possible to develop the LabVIEW application on windows to deploy on linux platform?

  I was also wondering if computers single-board as Beagleboard, Raspberry Pi are loaded with linux, labview application can be deployed on these computers?

  (in simpler words, I wonder, with existing suite of Labview 2009 developer on windows, can I develop a data acquisition application and deploy it on single-board computers that have linux installed on them.)

  Thank you!

  Nilesh-

  To create an exe on a Linux platform, you need LabVIEW for Linux with its application builder. You can open the source on the Linux machine.

• Application exe missing vi sub

  Hello

  Hello

  I did based on PCI 6221 DAQ card applications.

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Kind regards

  Hari

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Kind regards

  Hari

  Hello

  Sorry for the post above.

  Here clearly displayed.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Hello

  Sorry for the post above.

  Here clearly displayed.

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Kind regards

  Hari

• VI in Application.exe missing Sub

  Hello

  I did based on PCI 6221 DAQ card applications.

  I build application.exe.

  I build Installer 1) 2010 runtime engine) 2 DaqMX drivers included.

  When I installed and run the application on the client computer.

  It gives the error code 3.

  No source files were found. Missing Sub Vi.

  Are all the missing Sub vi associated DAQmx.

  I found that all the Vi Sub required file Exists in the installation folder.

  One please solve the problem.

  Kind regards

  Hari

  I got it it works fine now.

• Installation of construction LabVIEW application disables the Windows Device Manager? Help on how to diagnose the problem?

  Please can anyone shed light on this, or suggest where to look?

  I built an application using the Application Builder of LV2014 (32 bit).

  On a Win7 X 64 PC at work, it installs and runs ok.

  On Win7 X 64 PC at the customer, it installs ok, but then after Windows restarts on demand 'device manager' no longer works and there are some unchangeable registry entries associated with nipalu. The client runs Symantec security software. A client COMPUTER technician is suggesting that LabVIEW is interacting with device drivers and this is the origin of the problem, but we do not know how to go further. It is not really acceptable to deploy computers where the Windows Device Manager no longer works. Surprisingly, the application itself works always - it's just Windows which messed up.

  Thank you

  Thanks for the suggestions. The company IT guy has not been able to talk to a person in NI UK support (no one was available), but he managed to keep it down to a problem with Dell Data Protection encryption Enterprise Edition. Delete first, then install the LabVIEW application, then reinsert DDPE gave a system where everything worked.

  We have built apps that used progressively more labview drivers (vision, labview base; digital i/o)

• I'm not able to install both on the same PC LabVIEW applications. I have uninstall the first application in order to install the second. Is there a way to avoid this?

  I wrote two LabVIEW applications. The first acquires data from three different devices, displays the data and writes it to a file. The second application reads the data and displays it on the screen.

  Can I install the first application and run it, but I can only install the second application if I uninstall the first application.

  Any ideas as to why this is happening?

  You install applications by using a Setup program created with the application builder to LV?

  What LV version do you use?

  You have a dedicated for each installer build script, or do you still want to change the settings of a single build script (which would be a reason for this behavior!)?

  hope this helps,

  Norbert