The VIs you found would be used, but when you select New from the file menu one of the options is to open one of several design pattern templates.,
When you select New, a dialog box opens where you can select what you want to open. In the hierarchical menu on the left, expand the "VI" section and the section under it titled "From Template". Continue drilling down by expanding "Frameworks" and finally "Design Patterns".
Inside that last section you will find a template called "Producer/Consumer Design Pattern (Events)". Select it and then click OK.
This pattern uses an event (in this case a value change event on a button) to do something (cause a value to be put into a queue). This basic idea would be expanded by first flipping it "upside down" and then using a user-defined event to pass state-change information between loops.
In this scenario, the bottom loop (which is where your DAQ logic would be) becomes the producer loop while the top loop (the one with the event structure in it) serves as the consumer loop.
Basically, the counter in your code would generate a user-defined event whenever the counter value changes. The event would pass this state-change information to the consumer loop (instead of a queue).
I make this change because one of the issue that you have to address with using queues and notifiers to perform synchronization is that only one consumer will see any given notification or queue item. This is the way they are designed to work and it can be a very helpful trait, but if you have more than one consumer needing to be notified of a state change, this is also a problem.
By contrast, an event will be seen at the same time by all the consumers that are registered to receive it. Likewise, an event can pass as little or as much data as you like.
Mike...
