writing data from shared variable to hard disk

[faustina]

but if it was a bad data type wouldn't I have seen a broken wire or coercian dot?

[NAKeel]

Usually, but queues can use almost any data type, so the change might have been enough to make the VI run improperly, but not cause an error.  Again, that is just speculation. 

[faustina]

I wrote another VI using the identical looping structure.  I got the same problem with the indicators, so I rewired the connection between the shared variable and the queue.  But a buffer was still not allocated.  Is there a way to make sure this happens?

[NAKeel]

Can you post a screen shot of the code that is giving you problems?  I think I will need to see the problem to give you a proper answer. 

Nick Keel 

Applications Engineering 

National Instruments

[faustina]

here is the code

[Smootastic]

What values are available at the shared variable when you queue the element?  Have you considered using the Dequeue element function instead of the Flush Queue?  I can't immediately think of a way to ensure the allocation, I'll have to continue to take a look and try my own example VI.

Just to make sure, this VI runs on the Host PC correct?  If it's on the real-time side, you may want to try an RT FIFO.

What options did you select when you opt to show buffer allocations? 

[faustina]

I checked the shared variable everytime I was enqueueing and sure enough, everytime I was sending a 'zero' and the array was empty.  That's when I used the Show Buffer Allocations window to examine the arrays.  This VI is suppose to run on my Host PC.  I only selected arrays in the Show Buffer Allocations window.

[OliviaC]

Have you tried using the Dequeue VI instead? The Flush queue VI is really only meant to be used at the end to remove the remaining items in the queue.