Data acquisition stops

[BillyM]

Why does my data acquisition stop when I have a user input box pop up?

It doesn't happen on a quad core pc, just a dual core I'm attempting to run the program on.

I didn't think I really needed a core per while loop/subvi....

- Billy

[Arham-H]

Hi,

What device are you using for data acquisition? What timing are you doing using hardware or software?

I would appreciate it if you can provide more details on your setup.

Regards 

[BillyM]

I use a cDAQ, NI-9174. There are presently three modules in there as follows:

1x NI-9229

1x NI-9211

1x NI-9236

The general architecture used is a producer-consumer loop. However, I have a simultaneous third loop for continuous DAQ measurement. A snip of the code is seen below:

The DAQ is allowed to be turned ON/OFF dynamically for manual measurements. When the DAQ is running, the sampling rates are matched.

The 9229 and 9236 are in the same continuous loop with equivalent samplings.

The 9229 is at a rate 50k, and 5000 samples per channel. (10 averaged samples per second)

The 9236 is at a rate of 5k, and 500 samples per channel. (10 averaged samples per second)

The 9211 will be a single point measurement at the end of a test. It is a separate task.

During the subvi state machine, a pop up will cause the DAQ measurememnts to just stop, and it errors out.

So far, my workaround has been to use a functional global as a flag for "Testing in progress".

If the test is in progress, then an error will be ignored, and the configuration and measurements are started over again.

If the test is not in progress (waiting for user input/SUBMIT) then the user will be notified of a configuration error, and allowed to change the settings file dynamically.

It has no problems in LabVIEW Developer, but when it's compiled for run-time use - it will freeze when a user input box (custom or not) is loaded.

Best Regards,

Billy Murphy

[Arham-H]

Hi Billy,

Thanks for the information and screen capture of your program. Can you also let me know what error you get when the data acquisition stops? I am guessing that your development machine is quad core and the target machine is a dual core. If that is the case do you get the same issues when running the executable on the development machine (quad core)? I am also curious to know the LabVIEW version you are developing in.

Best Regards