LabVIEW Application Builder

Similar Questions

• LabView Application Builder, FieldPoint-> Programmabsturz beim Aufstarten einer erzeugten EXE-Datei

  Hallo, habe folgendes problem:

  Fur einen Kunden wurde ein Programm zur Datenerfassung developed (2005).

  Die Daten werden über die Fieldpoint-Schnittstelle und einer CSV-Datei abgespeichert erfasst.

  Fur ein Folgeprojekt der Kunde einer Version dieses Programms eine möchte.

  Therefore, one wurde der Application Builder acquired um eine Exe-Datei zu ruler.

  Da ich sonst nichts mit mache LabView ist meine nicht mehr die latest LabView-Version

  Version of LabView 7.1

  Application Builder as LabView 7.1

  FieldPoint Version 4.1

  DAS create einer EXE-Datei war auch been, nur beim EXE der implement auf dem neuen Zielrechner, das Gingold

  Programm beim Aufstarten die application great mit einer Fehlermeldung ab (Fehlerbericht a Microsoft senden...) und one sharp.

  The Rechners green Ereignisanzeige der in diesem Falle immer die message ".NET Runtime 2.0 Error Reporting."

  Typ: Fehler

  Ereignisskennung: 1000

  Warum das Programm ist leider nicht auszumachen absturzt sometimes, der of mit of ich aber dass Schnittstelle schatze

  zu FieldPoint (Version 4.1) hat zu tun.

  Wenn ich das Programm aus meiner Entwicklungsumgebung aus Starte works are properly.

  Testweise habe ich auch schon die Entwickungsumgebung auf dem neuen Zielrechner installed, auch dann so mein Programm wenn ich're manuell von sleeps aus starte. Kann ich beim ruler der Exe-Datei noch was please gemacht haben? Aber warum die EXE-Datei dann ab und zu works?

  Hi ralfn,

  Thank you for the information on Hyperthreading.

  The new PC contains a CPU dualprocessor.

  After deactivation of the screening "will launch several threads" in the LabView software

  (Tools-> Options-> Performance and memory), my EXE file works fine.

  Thank you, best regards,.

  Schnetzi

• LabVIEW Application Builder Crash: ntdll.dll module failing

  Hello guys,.

  I am currently having problems during the construction of my project (LV2012 (32 bit), Windows 7). At the end of the application generation, LabVIEW crashes without explanation (screenshot in french, sorry)

  

  Following Windows errors logging:

  Event 1000 Application Error
  
  Faulting application name LabVIEW.exe, version : 12.0.0.4024, time stamp : 0x4fea600e
  Faulting module name : ntdll.dll, version : 6.1.7601.17725, time stamp : 0x4ec49b8f
  Exception code : 0xc0000374
  Fault offset : 0x000ce6c3
  Faulting process id : 0x16fc
  Faulting application start time : 0x01cda5350f41f87c
  Faulting application path : C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe
  Faulting module path: C:\Windows\SysWOW64\ntdll.dll
  Report Id : 8e5b1344-1128-11e2-97d8-c0f8dae81bad
  

  I had the same problem on LabVIEW 2011. I tried to create my application with another computer (also LV2012 32-bit) and Windows 7 64 bit and I have no error.

  What is the problem with my computer?

  For french, french subject people

  Thank you for your help,

  Kind regards

  Quentin

  Solution found:

  -Uninstall all products of OR

  -The keys to clear registry associated with LabVIEW

  -Remove the directory of National Instruments in Application Data

  -Reinstall LabVIEW

• LabVIEW Application Builder 2010 not approved w / professional?

  I am running LabVIEW 2010 x 64 with a disconnected "Professional Dev" license file, but my app Builder is not active and expired trial shows?

  Does anyone else have this problem?  Or suggestions how to solve this problem?

  I left a voice message with our rep OR, but I'm waiting to hear back.

  Solution found:

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

• Error 1722 to the deployment of Installation Windows 7 LabVIEW applications

  Hello

  I use version 8.5 of LabVIEW Application Builder to deploy my standalone executable. I have never had a problem on Windows XP and have been very successful on Windows 7 installation. But now I have a client who gets the following error in Windows 7 (but the same installation package works very well for him on XP machines):

  Installing NO-SUN 1.7.0f0, part 10 of 19 with error 1722.

  Error 1722.  There is a problem with this windows package install.  A program run as part of the Setup did not finish as expected.  Contact your provider to support personal or package.  Contiunue Y or N.

  (Engineers application OR in particular) anyone have any ideas? (My contract has expired. I think that there is a way to report bugs, but is there a way to contact support OR directly in addition to this forum?)

  Thanks for any help.

  Ed

  UPDATE:

  Good news! My client back to me and told me it was his anti-virus (Trend Micro) that caused the error. When he disabled as I suggested (which I have a base of knowledge OR "Error 1722" article), the installation was successful.

  Thank you all until next time...

  Ed

• Failure to build LabVIEW application on Linux using "Shared library".

  In order to create a LabVIEW application on linux without X display, I have respected the LabVIEW VI using the shared library for Linux. I did it by clicking with the right button on construction Specifications and selecting New > Shared Library, and in the section Advanced , check the box labeled embedded version using the runtime engine. At the end of the build process, a message to inform that the build failed with the following message:

  "Error 127 to the Exec System: sh: gcc: command not found".

  The error code is not set. No one has provided a description for this code, or you could have wired a number which is not an admission of error code error code. »

  I have had no compling the LabVIEW VI in normal mode, so am confused about which is the problem.

  Hi Julian,.

  GCC is a compiler C and C++ under Linux.  A simple way to check if it is installed is to open a terminal and type 'gcc', if the command is recognized then the package is already installed, and the problem must lie elsewhere.  If this slot of Linux has a package manager, then it must be posted in here also.  If not then it could point to him being not installed or missing a dependency makes not accessible from the command line.  Here is a link that should hopefully scroll you through installation of gcc with Redhat: http://www.cyberciti.biz/faq/centos-linux-install-gcc-c-c-compiler/ .

• Application Builder Question: How to get several .exe files in one version?

  I am trying to release a LV 2010 application composed of a high level VI (Main.vi), and a number of dynamically called live contacting one using functional global variables (and a few classic global variables).

  One of the dynamic subVIs (Second.vi) can in fact be used independently of Main.vi (and often will). I wish it were available as a .exe, but I would like to be able to communicate with Main.exe if is started after Second.exe. Is - it somehow possible?

  It seems to me that I must write two screws as independent applications (and release them as such, but in the same folder of the application) and find another way to enable the exchange of data between the two (which, I have no idea). Is there an easier way, I'm missing? The two screws as high level screws in the Build specification will do almost what I want, but not quite, since it in order to open the two screws little important if I want to run only the Main.vi or Second.vi only (and of course only show the single .exe file in the application folder).

  You could do this by using the arguments passed to the exe.  This document gives an example "past of Arguments to a LabVIEW executable".  I just think, you can create shortcuts in the Application Builder, but you will need to generate them buy a post running installation tool.

  Jason

• Application builder cannot build the exe. Error 8 has occurred in AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi

  I bought a new Dell laptop (Windows 10 Pro) and LV 2015 (32-bit) is installed. I copied my project files and tried to build the exe file and received the error 8. After much searching for an answer, I created a minimal test with just a single white vi project and an exe based build spec to reproduce the error with. Whenever I try to build, I get the same error 8:

  An error occurred during the generation of the application. You don't have the appropriate permissions to create the application at the specified location, or the application is in use.

  Invoke the node in AB_Engine_Build_Method_Wrapper.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller
  
  Method name: Build: Application

  Error 8 has occurred to AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi

  Possible reasons:

  LabVIEW: File permission error. You do not have the correct permissions for the file.

  I can't quite imagine I could have permissions issues. I of course have full admin on the machine privileges.

  I've seen other messages (like this one) who speak to have Windows Explorer opened the path of construction when it tries to go up and get this error. I made double sure that I don't have ANY Windows Open Windows Explorer, trying to build. There was a mention in one of the positions which perhaps of LabVIEW in current directory is defined in the file generation, but I'm not quite what that means, or why that might happen when there isn't usually prevents me to build on other machines.

  I tried the procedure described in the KB, but no help.

  Interestingly, I have created a virtual machine (Win 10) for a different project and installed LV 2015 32 bits in the virtual machine, and all my applications build very well in the virtual machine. But on OS from my physical machine, I get this error 8 for all construction applications.

  I tried to fix LabVIEW, and also I tried to uninstall reinstall LabVIEW. Nor was the error to go away completely. After the repair, the project has successfully generated once. But subsequent attempts to build fail with the same error.

  See the attached test project and the build log.

  Thank you

  Nathan Scharfe

  CLD

  My best guess is that some external process is the use of the folder and do not let you write here. The most likely candidates are anti-virus software or a service of indexation of a certain type. I'm guessing that he sometimes managed everything simply because it is a race condition and in these cases, the blocking part yet or is already done.

  You could try the building to a network drive, when these forces are less likely to be able to make the lock or you could try to find a software that shows you what software has handles opened in a folder and control for an offender. I seem to remember that the Process Explorer and SIW show this, but it's far from my area of expertise.

• 1 error in writing on a text - installer with Application Builder file

  I wrote an installer using the Application Builder to install the runtime engine that allows any computer without LabVIEW to run an .exe program. Setup runs and installs engine race and then as a .exe VI. When it is done installing, the .exe VI opens automatically.

  An error appears when the .exe opens and says "1 error in writing to a text file". If the user clicks on the error that it can run the program without problem, it converts file formats in a file .lvm. Automatically, it generates a new file name and saves the file in the same directory, but with a different name.

  Why did it only happen when opening first upward? The program tries to run when it automatically opens? Is there a file path residual left in the program that trys to run first, before that the user put his own file path in the program?

  I am semi new to labVIEW (a few months) and that nothing shows that would create this error at the beginning of the program.

  Thank you

  Hi Scott,.

  Well, you could model a little VI and turn on debugging highlighted to test your idea!

  THINK THE STREAM!

  How a Boolean entry should WAIT for the action of the user? It should be read according to the stream!

  What this small pseudo-code:

  REPEAT
  
    Wait (50ms)
  
  Until the button

  Or how about an event in the user queue structure?

• Application builder

  Hello

  I hope sombody can help me with my problem.

  I created an application with the Application Builder. The application works and communicates with the hardware, but only on the PC, on which is installed Labview. On other PCs, the application runs, but do not communicate with the hardware. I installed all the drivers and I can commuicate with the material using the Explorer Meassurement and automation. I installed the drivers with the NO-DVD.

  I tried different ways to install the runtime and drivers, but nothing has worked.

  Thanks a lot for your help.

  Best regards

  Florian

  Since you where able to control your devices with MAX, my first guess would be that the material / channel descriptors used in the request are not correct. I suggest using commands instead of constants for channel selection.

• application builder error.llb

  Hi all

  I use the application builder to compile an executable from my VI. Compilation works without a hitch.

  However, when I try to launch the .exe subvis are missing three of error.llb: not found Dialog.vi, Dialog.vi to view details and the value string Value.vi

  The compiled .exe seems to be looking for these screws in instr.lib, which is not found in the compilation folder.

  This occurs even on my machine for development, on which, of course, the VI works well since in LabView.

  I missed something during the configuration of the compiler?

  Thank you in advance for your help!

  Nico

  I had this before, and it was reported by OR as a bug that just load a project that was built in an old version of LabVIEW and creating an application thereof. For me it was to load a project LV8.5 in 8.6.

  The only solution was to add the three missing from vi to the project and make sure that they are added to the list always included in the application builder.

  You will find these vi NIUninstaller Instruments\LabVIEW 8.x\vi.lib\Utility\error.llb program. Simply add them to your project, somewhere, and then in the application Builder makes sure that select you them as always included in the source files section, and then rebuild your application.

• 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

• Application builder appears complete but does not create executable not

  I'm working on a major project (~ 5000 screws, LV2011 SP1, Win7 32 bit) and have recently from problems with the Application Builder. This is after 3-4 years of success is based on this project...

  When I try to build my application of following higher level occurs:

  1. "build status' window opens as usual and starts the processing of my file:

  

  2. Subsequently, the progress bar reaches about halfway and the message becomes "Compilation."... » :

  

  3. then the progress bar jumps sharply at the end and the message becomes "Save...". ». In addition, the 'Done' button becomes active, as if the build is completed. The window remains like this for always. Notes on this dialog box:

  • The 'Explorer' and 'Help' buttons work normally in this State.
  • If I press the 'Done' button (or close the window with the Red 'X') then the window closes but Labview is suspended. The only way out of here is to kill the process in Task Manager.

  

  4. If I sail in my generation folder so I see temporary build files are still sitting here, i.e. the manufacturer failed to create my exe...

  

  When I turn on logging, I see that all the files seem to be treated successfully (in comparison with a previous successful build log), but the paper stops before writing the article ' [output file Version]]... ".

  Anyway - I'm trying to restore a large number of small changes to see if I can isolate that my changes of code causing the problem.

  Someone out there knows what could cause request the manufacturer to get as much as he does, thinking it's done (even if this isn't the case)?

  Thanks for all the ideas...

  Well - I finally managed to isolate the problem... Corrupted code is attached!

  
  

  The attached code is a version of a dialog box that is used in my project. The question turned out to be associated with the order by radio inside the tab control:

  • If you open the library and then try to REMOVE the two controls private library (simultaneously), then you are greeted with the accident below report. NOTE: Remove the private items one-at-a-time does not cause the accident. (weird...)
  • The same happens if you try to rename the library

  

  The solution:

  • The inclusion of this library in my project was originally my application build will fail every time.
  • Given that the report mentions "RadioClust.cpp", I made the amazing jump that the question has been connected with the radio control... so I just unplugged all instances of this control their typedef. That seems to have fixed!

  ASIDE: I have not checked if including this library in a different application will cause his generation to not too... Something to try out a rainy day!

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