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/07/17 17:42] pereira [Old processes still running] |
s800_daq_tools [2020/03/04 17:54] pereira [Trigger GUI] |
||
---|---|---|---|
Line 82: | Line 82: | ||
==== Trigger GUI ==== | ==== Trigger GUI ==== | ||
- | {{:wiki:800px-TriggerGUI.png? | + | {{:wiki:ULM_updated.png? |
The Trigger GUI appears when the " | The Trigger GUI appears when the " | ||
+ | |||
+ | The trigger GUI allows the user to select the source of the S800 clock and clock-reset signals (internal, from the ULM module), or external from (e.g.) GRETINA. If you are using external clock and reset signals, make sure to check the boxes labeled "" | ||
+ | |||
+ | |||
The different signal going through the trigger scheme can be inspected in th Data-U6 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four " | The different signal going through the trigger scheme can be inspected in th Data-U6 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four " | ||
Line 125: | Line 129: | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of 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|Error message: " | + | * [[#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 133: | Line 137: | ||
==== Old processes still running ==== | ==== Old processes still running ==== | ||
- | Sometimes, particularly if the S800 DAQ session ended in an uncontrolled way (e.g. you tried to " | + | 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 '' | ||
Line 153: | Line 157: | ||
==== CCUSB and/or VMUSB claimed by existing programs ==== | ==== CCUSB and/or VMUSB claimed by existing programs ==== | ||
One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following: | One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following: | ||
- | - Log on to S800 spdaq (spdaq19 | + | - Log on to S800 spdaq (spdaqXX |
- Type '' | - Type '' | ||
- Use '' | - Use '' |