Construction of an executable

Similar Questions

• Difference between VI and executable execution.

  I have a dynamic number of buttons in a cluster that I position by program on my front screen based on the upper-left position of the bunch.  When running in development mode, everything is fine and the cluster remained in this post after the execution.  However, when the application is built, the buttons and the cluster flowing to the left in a phased manner.  I have attached the source zip file.

  I think the solution is very simple and it would have been more obvious except for the fact that you 'hid' the offending code using a stacked sequence (please, never use a stacked sequence).

  In the box "invisible" 0 and 2 cases of the sequence stacked, you write to the scripting property AutoSize.  Run mode, this property is a read-only property.  In general, any property node with the light blue colour which designates a property Scripting, are (probably) not in the code that is planned for the construction as an executable file.

  Bob Schor

• Executable file do not write in tdm/PDM files.

  Hello

  I wrote a wrapper around a VI that controls the entries to designed the hardware and monitors the outputs for the prolonged lifetime of testing purposes.  We use compact DAQ for control and data acquisition.  We do not wish to moor a LabVIEW license for six months to run the desired test, I compiled an executable and built an installation program.  Everything worked without problems on a PC with LabVIEW and everything seemed to work well on a PC without LabVIEW with the executable... until I decided it was time to start analyzing the outputs recorded (tdms files).  The application is able to not control my material, no problem, I could see it passes through different States and key measures that I display on the user interface are valid, but the log files are simply cannot be created, not even an empty file.  At the lowest level, the open storage VI [TDM] is called to open or create the file (filename is entered by the user or created with timestamp if he did not) and each 'bit' of data is written by writing data [group of channels] and write data [channel] live on the PC with LabVIEW, the output files are created without problem.

  Did not work with executables before.  How can I start to debug (without installing LabVIEW on the PC in question - and when all goes well when run on a computer with LabVIEW installed)?  Have tried to build the executable with active debugging, but do not know how to "enable" debugging or a walk through as in LabVIEW... or if it's even possible...  I don't get warnings or errors during the race.  Is there something special I need to do in the construction of my executable or installer, particularly writing executables TDMS files?

  Thanks in advance

  -Andy

  
  

• Why an asynchronous call would lead to "the VI is not executable. The full development version... »

  I built a labview moderately complex program to connect with a new parser that I build.  To briefly describe the application, the main VI is a user interface which, in an initialization step, asynchronously calls a dozen other screws each called VI is a state machine that handles communication with a component specific for my parser, whether heat controllers, regulators debit, NI DAQmx channels, a SQL database, etc..  I use the VFG and/or EI to communicate information between the main VI and each component. The system works well when it passes through NI Labview 2012 SP1 (full development Version).  I build the project successfully, but when I run the construction (on the same development machine), I encounter the "the VI is not executable.  The full development of LabVIEW version is needed to correct errors"message.

  My first troubleshooting step that was supposed to isolate the problem.  I removed all the asynchronous calls, rebuilt and the program works without errors (granted, no State machines that handle I/O bundles are running). This gave me the impression that my UI screws are not the problem.

  The next step that I took was to create a test project with a simplified user interface to call asynchronously, and control a single component.  The first part, I tried to control a heating unit, and it works perfectly.  I have build it and run without errors or problems.

  Thinking that the component should not be a problem, I add the async call for this component in my main VI, to test it.  This works well in the built environment of Labview development, without errors, but alas, I get the same message as the "VI is not executable' when I try to run the build.

  I am at a loss on how to make trouble, or it could be the cause of the problem.  Why an asynchronous call to the VI even break the construction of an executable project, but don't cause problems in an executable of side projects?

  
  

• Messed up because of the LVOOP project

  It began in the construction of an executable file with 3 error (could not load front), I uncheck 'remove FP', but I get error 2208. Now I changed the paths of certain controls and live in some classes due to name conflicts. And get a lot of errors "VI is locked by the owner. In two days I should make acceptance of the factory to test my project, and I think that I will be lost my job, because this grand and expencive project will not work.

  Sorry, I would say that LVOOP has the bigs, then don't use it.

  
  

• XP embedded causing my screen buttons on lock?

  Hello

  I work ona Labview applications. Basically, I'm ordering a device through RS232, also I have a Labjack U3, used for a series of keys that are duplicates of buttons that I have on the screen. The main interface is a touch screen of Advantech running XP Embedded. I'm using Labview 8.6 for the development of the construction of my executable.

  I have no problems on my desktop computer or a laptop, but when I install the application on the touch screen, sometimes my buttons on screen lock and I have to force quit the program. My program uses a structure of tab to switch between the screens and all the buttons are connected to the event structures. When I switch to another screen in my program, all buttons on this screen will be frozen... I can't click on them with a mouse or by using the touch screen. Curiously, if I use my 'manual' buttons related my labjack, these work very well, even if they trigger essentially the same code by clicking on the buttons on the screen (although these are onlu some command buttons on the main screen of execution).

  Anyone who has ever seen anything like that? This sounds like a problem XP Embedded or is it possible that I have a code bug that comes only in XP embedded as I'm taxing the system rather than my normal computers?

  Thanks for any idea!

  Garrett

  Hey Marti,

  I think you're right. I did some checking and I did have my buttons that attach to the event anyway (mechanical action) structures, and I had even forgotten to disable some immediately after being pressed. The places where I seemed to lock up that all had the same mechanical action, so it must have been see the pressed button twice in quick succession. Once I have it cleaned, things seem to work well. Application tax the processor much more on the XP integrated office it seems I must be much more careful about the fine details of programming.

  The event structures are great, but be very careful!

  I've never built a debuggable executable... I look at how to do this. I did a lot of programming on 7.1 and have been away from him for a few years, a lot has changed with 8.6.

  Thanks for the help!

  Garrett

• Build is unsuccessful - not sure why

  Hello

  I have worked on my application and have done several (over a dozen) builds (create an executable installer and make) in recent weeks.

  This morning, I made some minor changes (format of input data for the Subvi) and suddenly I get this error on the construction of an executable file. I can't imagine all the changes I did that could have caused this.

  OK, I just solved this problem...

  I deleted the files created by the construction (in windows)

  Then run the build, it generated new files rather than crush them, and it worked.

• LabVIEW 8.6.1 - message builder vi is password protected

  I am new to Labview 8.6.1 and I get a few messages I can't explain why. Labview is the construction of an executable, I have a few messages such as the one displayed in attachment. The messages are associated with the screws that are part of the Labview library and are protected by Word. Usually I ignore messages. I wonder why I see these messages.

  Another question: you can see the entire hierarchy of the project to generate an executable from just in Report Designer by exploring the table of parameters VI in Labview 7.1.1. Is it possible to see a similar thing in Labview 8.6? Or Labview 8.6 builds any project no meter if I put the generator in a certain way, with only a few screws of the whole project?

  Hi Virginia,...

  have you checked the field to change/remove the password?

  The manufacturer includes only the vi of always included and all dependencies of this as well as all dynamically vi with also all dependencies.

  Mike

• Error 6 in construction of Apllication of the executable

  
  

  Hi Ather.lq,

  An error 6 is usually generated when you create a distribution and the path of a file in the project extends beyond the limit of 255 characters allowed by Windows. Here are a few troubleshooting steps that may help:

  1. Use a shorter path, such asc:\
  2. Make sure that your file path does not point to a wrong drive, such as a CD or DVD drive.
  3. Application (EXE) or shared library (DLL) of construction, check the box use LabVIEW 8.x file available in the advanced build specification Properties dialog box page.

• How to find the path to an executable of construction labview

  After generating an executable file with Labview and the installer, users install on some PCs. During the installation process, they have the option to install to a directory of choice here. How can I know this way of installation with a non-labview, for example script method.

  Jorn

  Hello Jörn,

  According to my experience, you have two options:

  (A) search all possible installation locations and find the location of the executable file.

  (B) for the installation that your script can do refers to the value afflicted a permanent Pavilion.  It is usually a registry key, but you can also use a text file that installs in the user of an application data directory or data in the same place no matter where the user places the exe itself.  System variables are also an option, but I see no good reason to use those unless you need run your script remotely.  Be aware that intervention antivirus or the user can snaffle these methods if you are relying on them, so if something essential is based on your script following that you'll either want to leave the user in the documentation or through a prompt orders or check/recreate this indicator in the exe itself, perhaps as part of the launch process (or both).

  For (B), you do not want this as an action of post-installation (available as an option in the tab 'Advanced' of the Installer Application Builder Properties window) and write the installation to the location/file/variable you chose.

  Kind regards

• Create an executable by mathscript or from the Windows command window

  Hello

  I have a lot of screws that must be built into executables. So, I think to write a script to save time.

  Windows MathScript looks a lot like the command window in MATLAB, so I wonder if there is a way to create executable files using mathscript?

  Or is it possible to build from the windows command window?

  Thanks for your reply and have a nice day.

  Kind regards

  Yan

  You can use the tools in the palette of constructor calls write a LabVIEW program to automate the construction of applications.

  (Somehow I don't understand not what you want. Building is usually negligible compared to write the program or the configuration of the build).

• Error 7 only during the executable to call the library node function

  Hello

  I'm having some trouble with LabVIEW, creating an executable work of my application. The program communicates with a sensor of moving laser Keyence LK-G5000 series with drivers provided by Keyence. When you run the program in the development environment, the program runs without any problem. However, when the construction program and run the program with an executable file, the program generates error 7 as shown below:

  

  After looking through the previous posts on error 7 and executable environment on the forums AND I found that a lot of people mentioned that the development environment and runtime environment use different path structures. I also found a guide of NOR to solve this problem here:

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

  However, after following these instructions, I always get error 7 only when executing the program in an executable environment.

  I've never used any .lvlib library in the past before, so I don't know if this may have been the issue (it was provided by Keyence.) The library includes 2 private screws that can only be called within the library, so I don't think I can go without using the library. There are screws in the library that use the DLL files (which are also included in this same library) through the node library function call in LabVIEW that appear not to be included when I create an executable file. Adding even manually the DLL files to the folder where the executable generates the same error 7.

  Is this what I remember in my code to allow the program to function within the executable?

  Fasteners are drivers for Keyence, my top level VI (GeoREF-Keyence controller.vi) and all my sub live

  Best regards

  Victor

  Executables are taking a different path, as a start to debug the path as an indicator and see which path is being planned in executable mode?

• Executable test sequence TestStand deployment

  Hello

  I would like to automate my test using TS environment and the BT.

  My goal is to have one machine with the development of TS (Inc. LV) for construction of test software that is compiled in one .exe file to run on the tested machine that does not have TS or LV

  Can I use the software for this task?

  It is for the main development computer:

  
  
  
  
  
  
  
  
  
  
  
  
  
  

  779601 35	NEITHER Developer Suite, English, include 3 years SSP	1
  779602 35	NEITHER Developer Suite Automated Test Option, include 3 years SSP	1

  It is for the machines to run the tests on:

  777774-3505 NI TestStand Base Deployment Engine License 5 unit Bundle

  I would like to have an option to monitor the performance of the tests on each machine and if necessary to perform debugging on the tested machine operations.

  If the package above will provide this capability so where can I find the documentation to create .exe files to run on test computers?

  If not, what software will provide this capability?

  Thank you

  His Lev

  Lev,

  These are the correct packages for TS development and deployment.  The only thing is that you have little debugging with the deployment license features.  If you want to debug, so instead of the deployment license they have licensed TestStand Debug.

  http://www.NI.com/TestStand/deploy-compare/

  More about licenses: http://digital.ni.com/public.nsf/allkb/B4B7C4ADB9B21B3F86256D360061891F

  One thing you should realize is that TestStand creates no executables.  Because TS is essentially a scripting language, you deploy the raw files.  These raw files feeding the TestStand engine and execute the steps in order.

  TestStand comes with 10 different (fully customizable) User Interfaces.  What are executables and run above the TestStand engine.  They allow you to run your sequence files (mostly scripts).  You will only need to use 1 of them.  The User Interface is so technically the executable for a deployment machine.

  More information on automation TestStand deployment:

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

  Chapter 14 of the reference manual: http://www.ni.com/pdf/manuals/373435e.pdf

  Interfaces user is in Chapter 1 to chapter of the major components:

  http://www.NI.com/PDF/manuals/373435e.PDF

  I hope this helps.

• "Lack of function external lvanlys.dll ' when executing EXE

  Windows 7 x 32, LV2009SP1 / LVRuntime 2009

  I am trying to build an EXE from a customer code.  They use the analysis library (NI_AALBase.lvlib).

  It works well on my dev machine.  When I create the EXE file and place him on a target with LVRuntime on that machine, I get the error:

  Lack of function external lvanlys.dll: Mean_head:C NI_AALBase.lvlib:Mean.vi.

  I explicitly added the lvanlys library to the project.  I added the library as a source file in the build.  Finally, I added the DLL itself to the project and as a source for the build.

  Still the same error.  The DLL is located in the folder data after construction.  I tried to move it in the same folder as the EXE file and in the system32 folder.  Nope.

  I just changed the extension of the DLL to dllx and tried again, and I get the same error, so it looks that it can't find it.

  Do I need to register this DLL or something?  Is there a file?

  You are an installer of construction or simply transfer the executable file?

  If you are just transferring the executable file, make sure to include the folder "data" beside him.

  (You can also check if the target computer has the engine execution of std (~ 170 MB) and not only the minimum (38MO).)

• Other Include directories in the construction or the installer

  The engineer so I have to write this program hates digging around for files if the software specification call for several configuration files outside the root directory.

  C:/program name/System_Config

  C:/program name/Instrument_Config

  C:/program name/Test_Scripts

  How can I include these files in a generation or the installer so that they are created during installation and placed in the appropriate default directories of config files?

  Look in the category Destinations in the dialog box to create a new installer.  The construction specifications for an installer by default puts the executables in [Program Files] \YourProjectName, where [Program Files] is a token that specifies what the Program files for the PC, you are installing.  There are many other chips for other paths such as Windows, office...

  I would first try to put in a new folder under the direction of [Volume Windows] tree.  (There is a new icon of folder at the bottom of the tree).  I'm leaving the Windows volume is going to be at the root of any drive you have installed Windows on, which should be C:\

  You could also add a new directory such as c:\YourProjectName which would put an absolute path for the installation of the executable at.