How to implement multiple queues in one circular buffer?

[LawrenceChong]

Spoiler

Recently I have successfully shared data of 2D array among different vis in a project, using circular buffer.

However, there is only one circular buffer allowed in one project for one data type.

I want different vis, running and getting data from circular buffer in different speed, all getting data as a queue from circular buffer. Like the circular buffer's read continuous mode.

The problem is that after a vi reads in continuous mode, the read data is deleted from the circular buffer. Then other vis can not use them any more and can not keep track where they should begin to read again.

So if it is possible that there are multiple pointers or queues in circular buffer to keep track the progress of different vis, and data only update when it gets input from DAQ but not deleted when read?   

[crossrulz]

Sounds like what you really want is either a Notifier or a DVR (Data Value Reference).

[Ben]

---

@LawrenceChong wrote:

Spoiler

Recently I have successfully shared data of 2D array among different vis in a project, using circular buffer.

However, there is only one circular buffer allowed in one project for one data type.

I want different vis, running and getting data from circular buffer in different speed, all getting data as a queue from circular buffer. Like the circular buffer's read continuous mode.

The problem is that after a vi reads in continuous mode, the read data is deleted from the circular buffer. Then other vis can not use them any more and can not keep track where they should begin to read again.

So if it is possible that there are multiple pointers or queues in circular buffer to keep track the progress of different vis, and data only update when it gets input from DAQ but not deleted when read?   

---

THe last time I wrote a multi-subscriber cirular buffer was in LV 6. Since then I have found that polymorphic queues perform much better so I now use multiple queues. One queue for each subscriber of the data. The subscribers are then responsible for maintaining their own histories.

So just use multiple queues.

Ben