10-06-2010 06:01 AM
Solved! Go to Solution.
10-06-2010 06:17 AM - edited 10-06-2010 06:21 AM
You can consider master - slave architecture with 1 master and 2 slaves. One slave can carry out the control and other measurement.
For intercommunication between loops: you can use globals or queues. Queues are recommended than globals (freedom from racing )
Post back if any queries.
10-06-2010 02:57 PM
thanks,
after reading the introduction to the master slave model, I will consider using it for my project.
Would it be suitable to write a master VI that handles frontpanel changes and communicates with the slave-VIs (not sub-VIs) for control and measurement via queus (if thats possible) or would it rather be a master vi that contains slave-loops for control and measurement?
Also, unfortunately, the formating of my initial post got lost, sorry for that 😉
11-03-2010 05:25 PM
well, after some time spend on the project, it was blown out to an event-driven input loop, three queued-state-machines for control- and recording purposes and another queue
for measurement-data transfer. Also I´m getting close to the point of losing track.
Do you think the best way to transfer the measurement-data (6 channel waveform array) to the tdms-recording loop and the control loop via 2 queues?