Labview generates an exe file

You have a lot of calls to vi, and when you generate an exe program, you should be placed in a relative path and saved to the exe installation directory for exe to call.

You just start the vi to generate the exe and the vi that is called is not all called can not be called Of course the error is reported!

Let's re-edit the generation rules.

Addendum: I just didn't see the diagram clearly.

You are not using what toolkit is not installed.

For example, if you use Visa, then you should add Visa to your installation package, and you seem to lack a toolkit here. There is a big picture of wood, and I can't see it clearly.

Supplement 2: I'll take a look.

Did you put the ' in when the exe was generated? It feels like if there is a function that calls this library in the subvi you called, it must be because it is referenced, but the default location of the reference is not found, and the reference content will be prompted like this, and the reference content is missing.

You will find the difference when you display the path with the control.,The relative path is relative to that sub-vi.,After generating the exe, the path will become relative to the exe.。

In addition, there are products on the stationmaster's group **, cheap ***.

When using serial port communication functions, you may need to choose Visa, and when it comes to hardware such as data acquisition cards, you may need to choose DAQMX drivers, etc.

See if you use some of the vi in the kit, and add the kit when packing.

Take a closer look at which drivers you need to select in the build installation file with the attached installer. For example, if you use serial communication functions, you may need to choose Visa, and when it comes to hardware such as data acquisition cards, you may need to choose DAQMX drivers, etc.

It is better to generate the "installation file", because this is the case when the exe file is generated (if you are not very clear about the inside of Labview), it is normal, and it is recommended to generate the "installation file".

The installation file will do the trick.

1. First, click Run Labview program to enter the LabView startup window.

2. There are two ways to create VI programs, first of all, you can directly click VI in the startup window to create.

3. Another way is to click Create Project in the startup window, and then select Create a new blank VI in the Create Project window.

4. After the creation is completed, two windows will appear, one of which is the front panel with a darker interface color, which is used to place various controls, and the two windows can use shortcut keys.

CTRL+E toggle.

5. Another interface is a block diagram with a light color of the color chain.

It is used to write**,Click the right mouse button on the front panel,You can bring up the control palette,You can add the required controls。

6. Finally, after placing various controls in the two windows, you can call up the tool selection board in the view manuscript menu key to connect and other operations.

We said for a long time, not in detail, go to the ni official website to see, it is very detailed. Portals.

1."The exe file is also generated, but it is still displayed. vi?This problem can be solved by setting the property of the vi.

In the programming environment, select the menu 'File', 'VI Properties'. In the dialog box that pops up, select 'Window Appearance' and tick off the 'Same as VI name' option. Then fill in the window title with the title you want to display.

2."But when you open it, you have to click the continuous run button to run", this problem is that your program does not use a loop mechanism, but a simple program algorithm. LabVIEW's exe runs automatically.

In fact, it's not that your program is not executed, but that it is only executed once and then it is over. So you need to put the whole program into a while loop box in the back panel, so that it will be executed in a loop. As shown in the figure, the time of the scheduled loop should be added to the while loop, which is at least 1ms, otherwise the CPU usage will be very high.

Alternatively, you can use the Timed Loop structure box directly.

3.The question "How to cancel these three buttons and menu bars" is the same as the first question, select the menu 'File', 'VI Properties'. In the pop-up dialog box, select 'Window Appearance', select 'Custom', and then you will be able to understand and set it up however you want.

Show Menu Bar', 'Show Runtime Toolbar' are ticked.

4.Redo your own menu bar, select Menu, Runtime Menu, and select Custom in the dialog box. Then it should be on the line, as for how to use the menu and program association, just look at the help that comes with LabView.

The generated exe cannot be modified in the vi attribute, you need to go back to the original vi program to modify the relevant settings in the process of regenerating the exe, and do not choose to generate between modes! In the default state, the generated exe is opened and run directly! It's inconvenient.

In addition, the name is also directly changed during the generation process!

One way is to create an application (exe), generate an installer, include your generated application in the installer, and include the labview run-time engine, so that the generated installer only needs to install it on the target machine, and it can be used!

It should be noted that if your program contains components such as visa, you should also include the components when generating the installer, and include what you need, so that it is complete!

The alternative is that you don't need to generate an installer!

How to use: Package your own files as exes, and then copy all these files to the generated exe folder, which can be run on computers without LabView installed.

This is the 2011 version of the Labview run-time file, and the same goes for the others. Just find the appropriate version of these files.

In this file, there is Chinese in the language, that is, in the process of packaging the exe, the runtime language should be set to Chinese, and the others should be canceled.

No, at least the computer must have the Labview Runtime Engine, and if you use other components, such as Visa, you need to have Visa on your computer

Refer to the practice of other programs, generally exe, with dynamic library dll.

Labview also turns to guess the spike can be generated. .NET's dynamic library. However, when replacing, the interface name must be the same and the parameter type must be the same. There is a certain flexibility in this practice.

A1: On the function palette, find the "Programming" Dialog & User Interface menu, which contains functions such as "Insert Menu Item" and "Delete Menu Item". Usage, see its help files and examples, which are simple and easy to use.

Note that the menu bar of the block diagram above is the same as in the block diagram before the deletion, and an item has been added as you said, and then the "window" and "help" have been deleted

In addition, vi, there is a runtime menu in the menu bar in the "" ". The following dialog box is summoned. What you see is what you get.

I copied the "Default" menu to the "Custom" menu, and then made the same additions and deletions

To put it bluntly, I don't understand what you mean.

Let's be clear! Or upload your program.

Use the packaging function (if there is no project before packaging, you will be prompted to build a project point to confirm) In fact, the configuration inside does not need to be changed.