03-21-2006 01:46 PM
03-21-2006 06:27 PM
03-22-2006 08:39 AM
03-22-2006 11:28 AM
03-22-2006 02:10 PM
The vi works great. I am currently using it for testing. Everything works great. but after I make an exe file then the two booleans gives error out of four.
I am attaching the error.
Thanks
03-22-2006 02:11 PM
03-22-2006
02:36 PM
- last edited on
06-30-2025
09:57 AM
by
Content Cleaner
Have you installed the patches for LabVIEW 6.0? The latest patch is LabVIEW 6.0.2 and is available free for download. You should definitely have the latested patch installed.
Also, can you check your Application Builder settings to make sure that the front panels for your 2 subVIs that cause the crash aren't being removed? LabVIEW 6.0 would sometimes mistakenly remove the panel, which would of course cause the crash if you tried to call the subVI and view its front panel. Also, VIs that Property Nodes or Invoke Nodes shouldn't have their front panels removed, since these rely on front panel data.
You can check these settings from the VI Settings tab of the Application Builder as seen below:
To modify these settings, click the Edit Build Settings button to see the following dialog:
Message Edited by Jarrod S. on 03-22-2006 02:37 PM
03-23-2006 07:46 AM
Hi Jarrod,
I looked into the setting and all that you have suggested. Everything seems to be okay. All the front panels that needs to be opened have yes in the respective columns. And I tried to make an exe file again. I run into the same problem. Out of four booleans in my program,two of them runs fine but when I click on either of the other two booleans that dont work, I get this error message and the program terminates.
I have absolutely no idea what is going on.
Thanks
SAL
03-23-2006 11:59 AM
HI Sal,
I noticed that from the error message you posted, it looks like you are (or were using) 6.0. I just wanted to make sure that you got the upgrade to 6.0.2 like Jarrod suggested. If you're using 6.0.2 and all of your front panels are included in the executable, then it may be just time to dig into debugging.
I think you said that each of the four buttons launched a different subVI. What is happening in these subVIs? Are you calling a DLL or using a particular instrument driver? Are you doing any File I/O? Frequently paths are the problem when a VI works fine but an executable has problems. Is there any difference between the subVIs which work in an executable and subVIs that don't? What happens if you try making each of the four buttons launch the same subVI? Try one of the ones that work, AND one of the ones that doesn't? Also, if you take out the subVIs and simply put message pop-ups for each of the buttons, do you still get the error in the executable?
I know this is a lot of questions, but hopefully they will help us pin down the problem.
Let us know what happens!
Megan B.
National Instruments
03-24-2006 01:20 PM
Hi Megan,
Yes I think I need to start debuggin in the software to see what exactly is causing the error. As far as my sub vis', Yes the four buttons launch four individual vis. And inside are some formulas, dll and serial/channel read in and out. That shouldnt be causing any problem, shouldit? Each of individual subvis runs fine. The two button that doesnt work has one thing in common, I am not sure if its causing the problem. It reads the serial port. I will try to do some more things and lets see if I can get around with it.
Thanks
SAL