You do not understand the purpose of the Producer/Consumer Design, nor understand how Queues work.
The Producer Loop (for your example) should consist of the DAQmx Read and an Enqueue function. It should not include any data processing, and especially should not include a Plot (which is the entire reason you are using Producer/Consumer in the first place!).
When you dequeue something, you remove it from the Queue. So if you take "smooth data" and send it to two dequeuing "Consumer" Loops, then when one loop removes data from the Queue to process, that data will not be present in the second Queue, so your two "Consumers" will each show some subset of the data, but neither will have the entire data set.
If you (for some strange reason) to send the same data to two Consumers, you need two Queues. You can either have the Producer enqueue the data into two separate Queues, or (a method I've used) you can use Q1 to send the data from Producer to Consumer 1, dequeue in Consumer 1 and send the data to, say, a Plot and also enqueue it in a second Queue, Q2, which goes to your second Consumer. Note that this makes Consumer 1 become a second Producer 2.
Model 1: P1 puts data on Q1 (to C1) and Q2 (to C2). C1 processes Data, and C2 processes Data.
Model 2: P1 puts data on Q1 (to C1). C1 puts data on Q2 (to C2). C1 processes Data, and C2 processes Data.
In my case of one Producer and two Consumers, the Producer was a DAQ system, C1 (and P2) was a plotting routine, and C2 was a Data Streaming routine to save the data to disk.
Bob Schor
