Display message pop up stops independent loop

[FrankHS]

I have two independent loops, a DAQ loop and a UI loop. The DAQ loop is dynamically launched using Open vi reference with option Ox80 (Call and forget) and a start asynchronous call node. No inputs or outputs are passed to the vi. Communication to and from the DAQ loop is done with LV2 style globals. The DAQ loop is a while loop that executes once per second.

If I open a One Button Dialog in the UI, the DAQ loop is not interrupted (it continues to iterate). However, if I open Display message to user the DAQ loop stops iterating until the popup is acknowledged.

 Why is this? Either pop up will stop the UI loop, as expected.

My goal is that the DAQ loop should have one core to itself. The UI and any windows processes should share the other available cores.

I would appreciate any thoughts on this. Is this the best way to launch the DAQ loop.

[James.M]

The Display Message subVI actually uses the One Button Dialog at its core and the subVIS above that use Same as Caller execution.

Can you simplify your code and share something that replicates this issue? I wouldn't expect a parallel loop to be stopped by a dialog in a separate loop.

[PalanivelThiruvenkadam]

The pop which you are referring is implemented in dynamically launched vi's or in main loop.
It's better to share the code for clear understanding.

[Hooovahh]

Ohh ohh I know this one, root loop.

http://www.labviewcraftsmen.com/blog/the-root-loop

There are several work arounds, and an idea exchange to change this behavior

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Change-one-and-two-button-dialog-windows-do-they-do-no...

[FrankHS]

I took all the UI and DAQ stuff out of the program so that I could upload it. I left the state machine, event structure and replaced the DAQ routines with a wait. Then I ran it and couldnt replicate the behaviour I described.

If that wasnt enough, I ran the program (very slightly modified) and couldn't replicate the behaviour that I saw before! I will keep checking into it.

[FrankHS]

Does this launch program guarantee me a core, assuming one is available? Or do I need to use a timed loop to do that?

[Hooovahh]

You can't dedicate a VI to run on a particular core or thread, the compiler work together with the CPU (and OS) to try to run it as best as possible.