This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
s800_daq_tools [2016/02/29 13:28] pereira [Troubleshooting] |
s800_daq_tools [2023/10/19 17:23] swartzj [Running in Slave mode with multilogger] |
||
---|---|---|---|
Line 7: | Line 7: | ||
* [[#Trigger GUI]] | * [[#Trigger GUI]] | ||
* [[#Scaler Display]] | * [[#Scaler Display]] | ||
+ | * [[#Running in Slave mode with multilogger]] | ||
* [[# | * [[# | ||
- | * [[#How to run combined S800 + GRETINA]] | + | |
Line 14: | Line 15: | ||
===== Running the S800 DAQ ===== | ===== Running the S800 DAQ ===== | ||
- | This page gives user-level instructions on how to run the S800 data acquisition (DAQ) system for an experiment. Presently this is run from the linux machine [[Software#u6pc5 (data U6)|u6pc5]] in data-U6. | + | This page gives user-level instructions on how to run the S800 data acquisition (DAQ) system for an experiment. Presently this is run from the linux machine [[Software#u4pc8 (data U4)|u4pc8]] in data-U4. |
==== Readout GUI ==== | ==== Readout GUI ==== | ||
- | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal to the directory **/ | + | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software#u4pc8 (data U6)|u4pc8]] or by navigating in a Linux terminal to the directory **/ |
+ | |||
+ | Before beginning data taking, it is necessary to initialize | ||
+ | |||
+ | |||
+ | After initializing the controllers, the ReadoutGUI window will show the '' | ||
+ | |||
+ | Before beginning a run, you have to make sure that the ULM trigger module is properly configured. This can be done by clicking the button [[#Trigger GUI|Launch ULM GUI]] in the ReadoutGUI window. | ||
- | Before beginning taking data is necessary to initialize the system. This is done by clicking '' | ||
- | The figure below shows the Readout GUI window after initializing the system. After clicking '' | + | The figure below shows the Readout GUI window after initializing the system. After clicking '' |
Line 34: | Line 41: | ||
The S800 electronics includes a Mesytec CFD (MCFD), used to " | The S800 electronics includes a Mesytec CFD (MCFD), used to " | ||
- | The MCFD GUI is invoked | + | The MCFD GUI can be started in three different ways: 1) by clicking the button '' |
Line 40: | Line 47: | ||
- | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/operations/daq/usb/Config**, and click **Load** | + | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/s800/s800daq/Configurations**, and click **Load** |
- | * Alternatively, | + | * Alternatively, |
- | * By default, the CFD parameters can be adjusted individually for each of the 16 channels. It is also possible use the module in a " | + | |
* After modifying any of the CFD parameters, click **Commit to Device** | * After modifying any of the CFD parameters, click **Commit to Device** | ||
+ | * Don't forget to save the new settings in file **MCF16.tcl**. | ||
+ | - Go to '' | ||
+ | - Click '' | ||
+ | - Select file **MCFD16tcl** and click '' | ||
+ | - A warning window will pop out to verify that you want to overwrite the existing file. Answer '' | ||
+ | - Click again '' | ||
+ | - Click '' | ||
* The MCFD module includes the possibility to send a periodic pulsing signal to all the channels. Two frequencies can be selected: 1.22 KHz, and 2.5 MHz | * The MCFD module includes the possibility to send a periodic pulsing signal to all the channels. Two frequencies can be selected: 1.22 KHz, and 2.5 MHz | ||
Line 55: | Line 69: | ||
- | This window appears when the "Init" button is pressed on the VME crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. It can also be accessed by pressing the "Show GUIs" button. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. | + | This window appears when the "Launch Gate Delay GUI" button is pressed on the [[#Readout GUI|Readout GUI]]. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. |
Some important things to remember: | Some important things to remember: | ||
- | * There are four "Delay Inspect" | + | * There are four "Delay Inspect" |
* These "Delay Inspect" | * These "Delay Inspect" | ||
- | * TDCs of last 4 listed signals (including XF and object scintillators) are bypassed with cable delays and thus their delays cannot be controlled with the GUI. They can be inspected, however using the GUI | + | * TDCs of last 4 listed signals (including XF (DB5) and object scintillators) are bypassed with cable delays and thus their delays cannot be controlled with the GUI. They can be inspected, however using the GUI |
* It is possible to bypass the delay of a given channel by checking the " | * It is possible to bypass the delay of a given channel by checking the " | ||
* The TDC delays can only be changed when the run control is stopped; must SAVE settings before starting run control not to overwrite adjustments being made | * The TDC delays can only be changed when the run control is stopped; must SAVE settings before starting run control not to overwrite adjustments being made | ||
Line 71: | Line 85: | ||
==== Trigger GUI ==== | ==== Trigger GUI ==== | ||
- | {{:wiki:800px-TriggerGUI.png? | + | {{:wiki:ULM_updated.png? |
- | The Trigger GUI appears when the "Init" button is pressed on the CAMAC crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the S800. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI by right clicking on any of the wires to put that signal onto one of the four " | + | The Trigger GUI appears when the "Launch ULM GUI" button is pressed on [[#Readout GUI]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the S800. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI |
+ | The different signal going through the trigger scheme can be inspected in the Data-U6 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four " | ||
+ | The Trigger (ULM) GUI allows the user to select the S800 timestamp clock: either the internally generated clock from the ULM, or an external clock from an ancillary system (e.g. GRETINA). In the latter case, you have to make sure to check the two boxes on the bottom of the Trigger GUI labeled " | ||
==== Scaler Display ==== | ==== Scaler Display ==== | ||
- | The GUI used to display scalers rates can be open from the icon **S800 Scalers** in the desktop of [[Software# | + | The GUI used to display scalers rates can be open from the icon **S800 Scalers** in the desktop of [[Software# |
The GUI includes two pages labeled " | The GUI includes two pages labeled " | ||
Line 85: | Line 101: | ||
{{: | {{: | ||
+ | |||
+ | |||
+ | ==== Running in Slave mode with multilogger ==== | ||
+ | The S800 DAQ can be run in Standalone mode (as described above), or in Slave mode. The latter 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. |
- | * [[#No data sources defined]] | + | * [[#Old processes still running|Error message " |
+ | * [[#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]] | ||
+ | * [[#For hodoscope runs, cannot read signal from hodoscope]] | ||
+ | |||
+ | |||
+ | |||
+ | ==== Old processes still running ==== | ||
+ | Sometimes, particularly if the S800 DAQ session ended in an uncontrolled way (e.g. you tried to " | ||
+ | - Exit your Readout GUI | ||
+ | - On a Linux session, connect to the S800 spdaq by typing '' | ||
+ | - 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 '' | ||
+ | - If the producer value of a ringbuffer is not -1, take note of the PID, and kill the process by typing '' | ||
+ | - You should now be able to run Readout GUI and begin a run without problem | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
==== No data sources defined ==== | ==== No data sources defined ==== | ||
When clicking '' | When clicking '' | ||
- | - Go to **/mnt/daqtesting/ | + | - Go to **/mnt/events/ |
- | - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/mnt/daqtesting/s800/exxxxnew** | + | - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/mnt/events/ |
- | - If you cannot find that file, there is an old version that can be copied from the directory **/ | + | - If you cannot find that file, there is an old version that can be copied from the directory **/ |
- You should now be able to run ReadoutGUI without problem | - You should now be able to run ReadoutGUI without problem | ||
==== 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 '' | ||
Line 109: | Line 166: | ||
In the rare case that the RunControl GUI gets " | In the rare case that the RunControl GUI gets " | ||
+ | ==== For hodoscope runs, cannot read signal from hodoscope ==== | ||
+ | If you see this kind error message when starting the DAQ with the hodoscope in the trigger (Ext. 1 in ULM gui), check the voltages on the crate which holds the hodoscope shaper modules. If they are not at the correct values, follow this procedure: | ||
+ | - Turn crate off | ||
+ | - Unplug both shapers (for both hodoscopes). Just pull them but don’t fully remove the cards. | ||
+ | - With shapers unplugged, turn crate on and check voltages | ||
+ | - With crate on, firmly push one of the shapers in. | ||
+ | - Push second shaper in | ||
+ | - Verify crate voltages | ||
+ | This procedure works for the electronic configuration with CAEN shaper modules. | ||
- | |||
- | ===== How to run combined S800 + GRETINA ===== | ||
- | OBSOLETE. Documentation is currently under development. | ||
- | |||
- | |||
- | In order to run the combined S800 + Gretina daq, the following steps need to be taken: | ||
- | |||
- | 1. On spdaq48 in / | ||
- | |||
- | **wish ./ | ||
- | |||
- | or, on devop2 (the S800 MAC machine) | ||
- | |||
- | click on the operations folder on the lower icon bar and select runcontrol.command | ||
- | |||
- | 2. On a dataU machine logged in as the experimental account (e11007 for the June 2012 testing period) do | ||
- | |||
- | **godaq** | ||
- | |||
- | 3. On spdaq44 do: | ||
- | |||
- | **/ | ||
- | |||
- | < | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | </ | ||
- | |||
- | Upon start of run there will be another client of the s800 ring, which is the pushToGEB process. This should die on end run. | ||
- | The S800 daq will now be in slave mode, and run control is done from the NSCL daq window. | ||