Differences

This shows you the differences between two versions of the page.

--- s800_daq_tools [2016/02/29 11:51]
pereira [Controls tab]
+++ s800_daq_tools [2016/02/29 11:52]
pereira [How to run combined S800 + GRETINA]
@@ Line 94: / Line 94: @@
 ==== Troubleshooting ====
 In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq.
-===== 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:
-. On spdaq48 do:
-**/user/s800/operations/daq/usb/s800status/comms**
-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" will connect to this server/port combination and attempt to fill in the Run Info section with the returned information. The status will also be updated.
-{{:wiki:comms.png?500|S800 Status GUI}}
-==== 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/output buffers, etc) will be updated, as will the connections information. In this scroll box any connection to which the eventbuilder must write data is listed in the form: remote host:local port.
-{{:wiki:evbuild.png?500|Eventbuilder tab}}
-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:
-. For each remote host, log in as each user which may be connected to the DAQ (ie e11007, s800). Unfortunately, root access is required to see this information for every user, so seperate logins must be made for each possible user.
-. Do **lsof -i | grep port** (where port is replaced by the local port information obtained from the status gui. This will look similar to:
-<code>
-netcat.tc 2498 e11007   10u  IPv4  11103      0t0  TCP spdaq44.nscl.msu.edu:58207->spdaq48.nscl.msu.edu:9002 (ESTABLISHED)
-</code>
-where the second column shows the PID of the connecting process. In this case the pid is 2498.
-. Do **ps -aux | grep PID**. This will look similar to:
-<code>
-e11007    2498  0.0  0.0  12052  2252 ?        Sl   12:31   0:20 /usr/bin/tclsh /soft/intel/lucid/daq/10.1/TclLibs/s800/../../bin/netcat.tcl spdaq48 9002
-</code>
-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/triggers, then it is possible that one of these processes has crashed in a manner that holds open the tcp connection to the eventbuilder. The process can be killed, which will return the DAQ to a normal running mode.
-===== How to run combined S800 + GRETINA =====
 In order to run the combined S800 + Gretina daq, the following steps need to be taken:

S800 Documentation

User Tools

Site Tools

Differences

Page Tools