Working through your questions from the last...
If you remove the inner while loop, then you do not need to worry about the stop condition.
I made some changes. Six hundred thanks are enough as long as you promise to study this until you understand the changes.
Again, removing the inner loop and letting the outer loop do all the work simplifies things and eliminates questions about stopping and continuous acquisition.
Using the timeout on the Wait on Notification takes care of having a wait and setting the timing on the consumer loop. If the user changes the scale, the change is processed immediately and then the timing restarts. Note that this may or may not conflict with the timing in the DAQ Assistant which I cannot see.
You do not need any Wait or timeout in the Producer loop because the event structure will wait, quite patiently, until you push a button.
The shift register in the Consumer loop carries the Density Offset and Divisor from one iteration to the next. It is only updated when a notification is received. Similarly the Scale on the Flux density gauge is updated only when a scale change has occurred. By using labelled constants in the initializing cluster, I have named the values in the cluster so that Bundle by Name and Unbundle by Name can be used inside the loop. These provide a form of self-documenting code.
Lynn
