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 [2016/02/29 11:51] pereira [Controls tab] |
s800_daq_tools [2016/02/29 13:26] pereira [Troubleshooting] |
||
---|---|---|---|
Line 2: | Line 2: | ||
* [[#Running the S800 DAQ]] | * [[#Running the S800 DAQ]] | ||
- | * [[#Run Control Window]] | + | * [[#Readout GUI]] |
- | * [[# | + | |
* [[#Mesytec CFD GUI]] | * [[#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 92: | Line 87: | ||
- | ==== 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. | ||
+ | |||
+ | * [[No data sources defined]] | ||
+ | ==== No data sources defined ==== | ||
+ | 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 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: | ||
+ | - 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 " | In the rare case that the RunControl GUI gets " | ||
- | ===== S800 DAQ status tool ===== | ||
- | In order to remotely monitor the status of the S800 DAQ, a tool has been created which can show statistics and current information about the present running instances of the Readout GUI and eventbuilder programs. This is accessed by the following: | ||
- | 1. On spdaq48 do: | ||
- | **/ | ||
- | which will open the status GUI. | + | ===== How to run combined S800 + GRETINA ===== |
+ | OBSOLETE. Documentation is currently under development. | ||
- | There are tabs for connections to the Readout GUI, the eventbuilder and a controls tab. | ||
- | |||
- | |||
- | ==== Readout GUI tab ==== | ||
- | The communications port to the Readout GUI is tcp:7999 and it runs by default on spdaq48. These options are selected by default in the server and port drop down boxes, but other values can be entered here by hand. Clicking "Get Status" | ||
- | |||
- | {{: | ||
- | |||
- | |||
- | ==== Eventbuilder tab ==== | ||
- | 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/ | ||
- | |||
- | {{: | ||
- | |||
- | 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/ | ||
- | |||
- | |||
- | |||
- | ===== 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: |