Labview 2011 compiled application crash

[FiddlersElbow]

I'm writing a fairly simple DAQ application for use in a freshman engineering lab that is written for the USB-6211. Since it will be used at more than one campus, I'm trying to make it a compiled application. The application, as built in LabVIEW 2011, works fine. The problem is that the compiled executable crashes in the same places without fail. I've included both the unmodified VI source, and a version with the DAQ code disabled, and some dialogs inserted to follow the progress of the application. Executables for both are also included.

I'm using a producer/consumer-events architecture to manage three different DAQ tasks. The consumer loop will fail after any of the three DAQ events are run. The consumer loop works fine for the exit event. I also reverted to LabVIEW 2010 and recompiled there, with the same failures.

Any help is greatly appreciated!

Stuart

[altenbach]

---

@FiddlersElbow wrote:

The problem is that the compiled executable crashes in the same places without fail.

---

I have not looked at your code (currenty on a PC with only LV2010), but could you be a bit more specific about the "crash".

I don't understant the term "same places" (plural). Does that mean it crashes on different places depending on what you do? How quickly does it crash? Does it operate normally up to a certain point? Do you have instructions on how to reproduce the crash? What kind of crash? Do you get an error or OS message?

[FiddlersElbow]

I've added a LabVIEW 2010 version of the project, along with a VI snippet of the main VI. The issue that I have is in the consumer loop. This loop dequeues the enum that determines which DAQ task to run, hides the main window, runs the DAQ task, then reopens the main window, then returns to wait for the next enum from the producer loop. I currently have the DAQ tasks disabled, and one button dialogs strewn about for monitoring.

What happens is that the consumer loop executes to the point of reopening the main VI front panel for each of the three DAQ tasks, then the window closes and the application exits, with no warning or dialog, and no OS message. The consumer loop never restarts. The only part that works properly is to run the exit event, in which case, I see the two dialogs that indicate that both loops have exited properly before the application exits normally.

I hope this is a little clearer.

Thanks again!

[altenbach · Accepted solution]

I think if you close the front panel of the startup VI, the built application will quit.

Replace the "FP.open" properies with "FP.State" and toggle between "Hidden" and "Normal". That seems to work in my limited testing.

[FiddlersElbow]

That worked. Definitely a case of "really obvious when told" but I'd never have gotten there on my own.

Thanks again!