LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

executable problem

Hi,
We have a main VI that runs specific tests that the users want. The main VI works fine in the development environment, but when we made it into an executable file, all the tests work fine except for one. This test will run continuously for some reason, it finishes and then restarts by itself.
Basically, the sub-VI sends an indicator to the main VI that it has finished executing, so the main VI then allows the next test to run. We ran the main in the development environment with this test and it works fine, but in the executable file, the done signal never becomes true, so this sub-VI runs continuously in the main VI. Do you know what's wrong?
Thanks.
0 Kudos
Message 1 of 4
(2,768 Views)
Just a guess, but... One of the biggest problems with building executables is the path to other VIs. In the development environment, an example path might be
C:\this path\my vi.vi
While in the executable, the path changes to:
C:\this path\executable.exe\my vi.vi
I'm sure you can see the problems this can cause is the program does not take this into consideration. I ran into this a while ago. This almost sounds like that type of problem.

Rob
0 Kudos
Message 2 of 4
(2,768 Views)
I included the sub-VI dynamically when I built the executable program. All the other VI's that were included work.
0 Kudos
Message 3 of 4
(2,768 Views)
....
0 Kudos
Message 4 of 4
(2,768 Views)