02-06-2008 02:21 AM
02-06-2008 03:04 AM
You have not to destroy/release queue after each sending.
Open your queue and connect the reference on both loops. So the one loop enqueues the queue and the other one should dequeue them. After you exit both loops you can release the queue.
I use queues very very often (up to 20 queues), but I can't confirm that the memory usage increases.
Eugen
02-06-2008 03:28 AM
Hi Eugen,
Thanks for your answer.
You write "Open your queue and connect the reference on both loops". This will work fine if both threads are in the same VI, but I can't do so because they are both in separate VIs, called dynamically... Thats my main huge problem.
Any other suggestions about how communicate between VIs called dynamicaly ? What kind of structure should I use ?
Thanks
02-06-2008 03:41 AM
Queues work fine for communicating between different VIs - when you obtain a queue, you have the option of entering a name, which obtains the same queue.
There are two ways in which you can run out of memory:
The real solution depends on what it is you are actually trying to do, but I'm suspecting you might want a notifier - unlike queues, a notifier only maintains the most recent value and so will not grow unbounded.
I suggest you post more details about what it is you want to do exactly. Posting images of your code might also help.
02-06-2008 03:44 AM
02-06-2008 03:52 AM
02-06-2008 03:53 AM - edited 02-06-2008 03:54 AM
And here the screenshot of the Main.vi, which starts both loop-VIs.
.
02-06-2008 03:57 AM
02-07-2008 01:15 AM
Hi everybody,
Thanks for all of this answer. I will try those solutions and check for the memory size usage...
Thanks again.