Re: DAQ+storage must happen independent of other screens OR user interaction

2004-02-13 Thread waldemar.hersacher
There are some examples how to use named queue. LV 6.0.2: Search Examples >> Advanced Examples >> Execution control Examples >> Synchronisation examples >> Named Queue LV 6.1 & LV 7.0: Find Examples >> Optimizing Applications >> Synchronizing Tasks >> Queue Message Loging.vi In this example they

Re: DAQ+storage must happen independent of other screens OR user interaction

2004-02-12 Thread Sandeep
Hi Waldemar, I didnot follow the 'named queue/notifier' part of your explaination. Would you mind putting it in a simplest example? (frame1/frame2/frame3). That will be clearer. thanks much. Sandeep

Re: DAQ+storage must happen independent of other screens OR user interaction

2004-02-10 Thread waldemar.hersacher
The best way to implement this is using a background VI for DAQ+storage. Load this VI from your main VI with Open VI Reference and start the VI with the Invoke node Run VI. Use a named queue to send data from your UI VI to the background VI. Use a strict typedef for the data to transfer over the qu

DAQ+storage must happen independent of other screens OR user interaction

2004-02-09 Thread Sandeep
I have a problem here. Program has 3 screens screen 1 To save user entered parameters. Example - acquisition period value, data storage location, averaging screen 2 -data acquisition(DAQ) takes place -graphs are displayed for user -additional user parameter selection (user selected momentary tem