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 [2016/02/29 15:00] pereira [Old processes still running] |
||
---|---|---|---|
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]] | * [[#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 '' |
+ | The figure below shows the Readout GUI window after initializing the system. After clicking '' | ||
- | {{: | ||
+ | {{: | ||
- | ==== EventBuilder 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 is invoked by either clicking the icon **MCFD GUI** in the desktop of [[Software# | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | * 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** | ||
+ | * 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 " | This window appears when the " | ||
Line 49: | Line 62: | ||
* 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 78: | ||
==== 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 87: | ||
- | ==== 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 ===== | + | * [[#No data sources defined]] |
- | In order to remotely monitor the status of the S800 DAQ, a tool has been created which can show statistics | + | * [[# |
+ | * [[#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 | ||
+ | - 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 to the new experiment 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 | ||
+ | ==== CCUSB and/or VMUSB claimed | ||
+ | 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 as of October 2015) | ||
+ | - Type '' | ||
+ | - Use '' | ||
+ | - Use '' | ||
+ | - Try '' | ||
+ | - If this didn't help try rebooting the S800 DAQ manually (see below) | ||
+ | ==== Manual rebooting ==== | ||
+ | In the rare case that the RunControl GUI gets "frozen", it is possible | ||
- | {{: | ||
- | ==== Eventbuilder tab ==== | + | ===== How to run combined S800 + GRETINA ===== |
- | The communications port to the eventbuilder is tcp:8100 and it runs by default on spdaq48. These options can be changed in a manner identical to the Readout GUI tab. Information about the current statistics (input/ | + | OBSOLETE. Documentation |
- | {{: | ||
- | |||
- | 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 commands: | ||
- | |||
- | 1. For each remote host, log in as each user which may be connected to the DAQ (ie e11007, s800). Unfortunately, | ||
- | |||
- | 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: | ||
- | |||
- | < | ||
- | 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 to: | ||
- | |||
- | |||
- | < | ||
- | 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 of the Readout GUI, and is for advanced users only. In the event that the run must be stopped, or the DAQ software exited without access to the Readout GUI itself these buttons may be used to perform these actions. The run MUST be ended before using the Force Exit button, or it is likely that the USB crate controllers will become stuck in DAQ mode and the crates will have to be reset. | ||
- | |||
- | {{: | ||
- | |||
- | |||
- | |||
- | ===== How to run combined S800 + GRETINA ===== | ||
In order to run the combined S800 + Gretina daq, the following steps need to be taken: | In order to run the combined S800 + Gretina daq, the following steps need to be taken: |