This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
s800_daq_tools [2017/04/08 13:33] pereira [Trigger GUI] |
s800_daq_tools [2017/07/17 18:03] pereira [Old processes still running] |
||
---|---|---|---|
Line 7: | Line 7: | ||
* [[#Trigger GUI]] | * [[#Trigger GUI]] | ||
* [[#Scaler Display]] | * [[#Scaler Display]] | ||
+ | * [[#Running in Slave mode with multilogger]] | ||
* [[# | * [[# | ||
Line 97: | Line 98: | ||
{{: | {{: | ||
+ | |||
+ | |||
+ | ==== Running in Slave mode with multilogger ==== | ||
+ | The S800 DAQ can be run in Standalone mode (as described above), or in Slave mode. The later means that the S800 DAQ is controlled by an external DAQ (e.g. GRETINA). In this mode, the S800 ULM receives external clock and external synchronization | ||
+ | |||
+ | |||
+ | By default, when running in Slave mode, data are recorded in the stagearea of the Master DAQ (experiment account). It is however possible to record simultaneously data from the S800 into the S800 stagearea, using the '' | ||
+ | |||
+ | When running XDT for an experiment with a Master DAQ (e.g. GRETINA), it is recommendable to run the S800 DAQ in Slave mode with the s800filter multilogger enabled. This can be done following the steps: | ||
+ | |||
+ | * Click to the tab '' | ||
+ | |||
+ | * Select the option " | ||
+ | |||
+ | * Click again on the tab '' | ||
+ | |||
+ | * Check out s800filter to enable recording data from this ring buffer | ||
+ | |||
+ | * After this, S800 data from every run recorded by the experimenters, | ||
+ | |||
+ | * After finishing XDT, it is better to disable the s800filter ring-buffer in the multilogger menu so the S800 stagearea doesn' | ||
+ | |||
+ | |||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
- | There are several common reasons why the S800 DAQ may fails to start. The list below describes what to do to fix these problems. | + | There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of these problems. |
- | * [[#Old processes still running]] | + | * [[#Old processes still running|Error message " |
- | * [[#No data sources defined]] | + | * [[#No data sources defined|Error message "No data sources are running so a run cannot be started" |
* [[#CCUSB and/or VMUSB claimed by existing programs]] | * [[#CCUSB and/or VMUSB claimed by existing programs]] | ||
* [[#Manual rebooting]] | * [[#Manual rebooting]] | ||
Line 109: | Line 133: | ||
==== Old processes still running ==== | ==== Old processes still running ==== | ||
- | Sometimes, particularly if the previous | + | Sometimes, particularly if the S800 DAQ session ended in an uncontrolled way (e.g. you tried to " |
- | - Exit your Readout GUI properly | + | - Exit your Readout GUI |
- | - On a Linux session, connect to spdaq19 | + | - On a Linux session, connect to the S800 spdaq by typing '' |
- | - Type '' | + | - Type '' |
- Type ''/ | - Type ''/ | ||
- You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column '' | - You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column '' |