DAQmonitor

For synchronous data access you can use a DAQ middle layer server called the DAQmonitor. The DAQMonitor usually is used to check that the data revived by the DAQ is correct.  

But it is also  possible to pass the trainID (historically called macropulse) in pydoocs read methode and ensure related data. For this purpose the DAQmonitor (to be updated !) provides a ring buffer. An example how to read the data from the ring buffer can be found in the repository.

In addition the data from the DAQ monitor can be seen in the DAQ control to crosscheck that the data that should be saved reaches the DAQ correctly (long enough ADC traces ...)

Configuring the DAQ monitor:

After taken a DAQ run with the actual DAQ configuration which will be used during the beamtime, you could configure the DAQmonitor by using the taken DAQ run via the DAQdataGUI.

Currently it is the recommendation to configure the DAQmonitor as vuvfuser from flashlxuser1 or flashlxuser2.

Extra stuff

For experts: if a run is active (like in PBD) and the DAQmonitor is not reacting and can not be configured one can set the monitor ( in the status panel) to INITIALIZED and send the configuration and set to RUN again ...

MCS4 documentation

Link to the DAQmonitor Docu from MCS4