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 [2015/10/25 16:48] pereira [Delay Window] |
s800_daq_tools [2017/04/08 13:26] pereira [Delay Window] |
||
---|---|---|---|
Line 2: | Line 2: | ||
* [[#Running the S800 DAQ]] | * [[#Running the S800 DAQ]] | ||
- | * [[#Run Control Window]] | + | * [[#Readout GUI]] |
- | * [[#EventBuilder Window]] | + | * [[#Mesytec CFD GUI]] |
* [[#Delay Window]] | * [[#Delay Window]] | ||
* [[#Trigger GUI]] | * [[#Trigger GUI]] | ||
* [[#Scaler Display]] | * [[#Scaler Display]] | ||
- | | + | |
- | * [[#S800 DAQ status tool]] | + | |
- | * [[#Readout GUI tab]] | + | |
- | * [[# | + | |
- | * [[#Controls tab]] | + | |
- | * [[#How to run combined S800 + GRETINA]] | + | |
Line 21: | Line 17: | ||
- | ==== Run Control Window | + | ==== Readout GUI ==== |
- | The Run Control | + | The S800 Readout |
- | Before beginning taking data is necessary to initialize the VME and CAMAC USB controllers. This is done by selecting the crate (either VM0079 for VME or CM0105 for CAMAC) and selecting the corresponding initialization file by clicking | + | Before beginning taking data is necessary to initialize the system. This is done by clicking '' |
- | {{: | + | After initializing the contollers, the ReadoutGUI window will show the '' |
+ | The figure below shows the Readout GUI window after initializing the system. After clicking '' | ||
- | ==== EventBuilder Window ==== | ||
- | {{:wiki:Eventbuilder.png|EventBuilder | + | {{:wiki:readoutgui2.png|Readout GUI Window}} |
- | The EventBuilder window will appear as part of starting the [[s800 daq tools#run control window|Run Control]]. This window will communicate statistics such as number of buffers read and number of events broadcast, and will also show error messages, should they occur. | ||
+ | |||
+ | |||
+ | ==== Mesytec CFD GUI ==== | ||
+ | The S800 electronics includes a Mesytec CFD (MCFD), used to " | ||
+ | |||
+ | The MCFD GUI can be started in three different ways: 1) by clicking the button '' | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/ | ||
+ | * 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** | ||
+ | * 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 | ||
+ | |||
+ | |||
==== Delay Window ==== | ==== Delay Window ==== | ||
+ | {{: | ||
- | {{: | ||
- | 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 [[ReadoutGUI|Readout GUI]]. 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. | ||
Some important things to remember: | Some important things to remember: | ||
Line 49: | Line 72: | ||
* 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 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 " | ||
* 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 | ||
- | * The “S800” trigger used as reference to calculate the ToF is from E1 up signal | + | * The S800 trigger used as reference to calculate the ToF is from E1 up signal |
* The signal delays controlled by the GUI (and not by cable delays) are not “pipelined” -- i.e., any new signals that arrive during the delay time of a previous signal are lost and thus deadtime is introduced into the system. | * The signal delays controlled by the GUI (and not by cable delays) are not “pipelined” -- i.e., any new signals that arrive during the delay time of a previous signal are lost and thus deadtime is introduced into the system. | ||
Line 64: | Line 88: | ||
==== 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 " | ||
A list of scaler channels can be found [[Scaler Channel Description|here]]. | A list of scaler channels can be found [[Scaler Channel Description|here]]. | ||
Line 71: | Line 97: | ||
- | ==== Troubleshooting ==== | + | ===== Troubleshooting |
- | In the rare case that the RunControl GUI gets " | + | There are several common reasons why the S800 DAQ may fails to start. The list below describes what to do to fix these problems. |
- | ===== S800 DAQ status tool ===== | + | * [[#Old processes still running]] |
- | In order to remotely monitor the status of the S800 DAQ, a tool has been created which can show statistics | + | * [[#No data sources defined]] |
+ | * [[# | ||
+ | * [[#Manual rebooting]] | ||
- | 1. On spdaq48 do: | ||
- | **/ | ||
- | which will open the status | + | ==== Old processes still running ==== |
+ | Sometimes, particularly if the previous S800 DAQ session ended in an uncontrolled way, there may be old processes running (CCUSB and/or VMUSB and/or S800 event builder) that will prevent Readout GUI to begin a run. Whenever this happens (typically after clicking '' | ||
+ | - Exit your Readout | ||
+ | - On a Linux session, connect to spdaq19 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 | ||
- | There are tabs for connections to the Readout GUI, the eventbuilder and a controls tab. | ||
+ | {{: | ||
- | ==== Readout GUI tab ==== | + | ==== No data sources defined |
- | The communications port to the Readout GUI is tcp:7999 and it runs by default on spdaq48. These options | + | When clicking '' |
- | + | - Go to **/ | |
- | {{: | + | - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing |
- | + | - If you cannot find that file, there is an old version | |
- | + | - You should now be able to run ReadoutGUI without problem | |
- | ==== Eventbuilder tab ==== | + | ==== CCUSB and/or VMUSB claimed by existing programs |
- | The communications port to the eventbuilder | + | One of the most common reasons why the S800 DAQ fails to start is because |
- | + | - Log on to S800 spdaq (spdaq19 as of October 2015) | |
- | {{: | + | - Type '' |
- | + | - Use '' | |
- | This is the only information available to the tcp protocol, but the pid of the processes responsible for these connections can be investigated by using the following | + | - Use '' |
- | + | - Try '' | |
- | 1. For each remote host, log in as each user which may be connected | + | - If this didn't help try rebooting the S800 DAQ manually (see below) |
- | + | ==== Manual rebooting ==== | |
- | 2. Do **lsof -i | grep port** (where port is replaced by the local port information obtained from the status gui. This will look similar to: | + | In the rare case that the RunControl GUI gets " |
- | + | ||
- | < | + | |
- | netcat.tc 2498 e11007 | + | |
- | </ | + | |
- | + | ||
- | where the second column shows the PID of the connecting process. In this case the pid is 2498. | + | |
- | + | ||
- | 3. Do **ps -aux | grep PID**. This will look similar | + | |
- | + | ||
- | + | ||
- | < | + | |
- | e11007 | + | |
- | </ | + | |
- | + | ||
- | which gives the program name associated with the PID that is connecting to the eventbuilder. | + | |
- | + | ||
- | If the eventbuilder is hanging, which is evidenced by non-increasing statistics and no data/ | + | |
- | + | ||
- | + | ||
- | ==== Controls tab ==== | + | |
- | This tab allows forced control | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | + | ||
- | ===== How to run combined S800 + GRETINA ===== | + | |
- | + | ||
- | In order to run the combined S800 + Gretina daq, the following steps need to be taken: | + | |
- | + | ||
- | 1. On spdaq48 in /user/ | + | |
- | + | ||
- | **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 | + | |
- | + | ||
- | **godaq** | + | |
- | + | ||
- | 3. On spdaq44 do: | + | |
- | + | ||
- | **/ | + | |
- | + | ||
- | < | + | |
- | | + | |
- | | + | |
- | +----------------+------------+-------+-------------+--------+---------+---------+------+-------------+ | + | |
- | | + | |
- | |s800 |8195 |8195 | + | |
- | |- | + | |
- | |segatest | + | |
- | |spdaq48.0400x | + | |
- | | + | |
- | +----------------+------------+-------+-------------+--------+---------+---------+------+-------------+ | + | |
- | </ | + | |
- | + | ||
- | 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. | ||