From: hadeshyp Date: Mon, 2 Apr 2012 13:11:54 +0000 (+0000) Subject: *** empty log message *** X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=6e0f38f81531718ea51d12c1c7053823ecae6405;p=daqdocu.git *** empty log message *** --- diff --git a/main.tex b/main.tex index 2300557..055722f 100755 --- a/main.tex +++ b/main.tex @@ -174,7 +174,9 @@ \clearpage \part{Operator Guide} +\input{shortguide} \input{ebmonitorguide} +\clearpage \input{daqmonitorguide} \clearpage diff --git a/shortguide.tex b/shortguide.tex new file mode 100644 index 0000000..c0d559a --- /dev/null +++ b/shortguide.tex @@ -0,0 +1,119 @@ +\section{Short Manual} + +\subsection{What is the starting point?} + +Open the DAQ-Control GUI (HadesControl Icon), click on "Hmon". A firefox window will +appear. Click on "Tactical Overview". If firefox fails to start from the button, start +it manually and direct it to http://hades33/mon + +\subsection{DAQ-Operation} + + +The main task of the DAQ-Operator is to watch the +Tactical-Overview window and check that all buttons are green. +The essential numbers (like trigger rates) have to be in limits +given by the shift leader. +The "Operator Guide" gives further information about each entry in +the tactical overview. You can open it by clicking on an entry. +It also offers a description of typical situations during data +acquisition. It also contains instructions to solve typical +problems. Following guides point to relevant chapters if necessary. + + + +\subsection{DAQ-Control Window} + +The DAQ-Control Window provides functions solutions of ocurring +DAQ problems. The "HadesControl" Icon starts DAQ-Control. + +\begin{description} +\item[DAQ-Operator] Buttons are necessary for a DAQ restart. The "DAQ-restart" guide +describes the use of these buttons. + +\item[Monitor Tools] contain all observation windows. + \begin{description} + \item[CTS Mon] Opens the CTS Monitor + \item[Hmon] Click on "Tatical Overview" in the new Firefox window to get the mains screen. + If firefox fails to start from the button, start it manually + and direct it to \\http://hades33/mon + \item[Epics] Opens the Epics Monitor. + \item[Epics FB] Shows a status window containing Eventbuilder information. + \item[Daq VNC] Opens the VNC window for DAQ control used during preparation + \item[Chat] The DAQ users chat window + \end{description} + +\item[Eventbuilder Tools] are necessary for the control of Eventbuilders. + \begin{description} + \item[Stop EB] stops all EB. + \item[Restart EB] starts the EB with the last settings again + \item[Prefix XX] restarts the EB and sets the file prefix to a new one + \end{description} + +\item[Expert Tools] + \begin{description} + \item[CTS Scope] Opens the window oscilloscope connected to the CTS for + signal adjustment + \item[Reload RPC Thresholds] Loads the settings for trigger boards of RPC + in case the count rates on the CTS monitor are wrong + \item[Restart EB IOC] If some of the entries in the Epics Eventbuilder Monitor + are white, use this button to restart them + \item[Restart Hmon] Restarts the browser-based monitoring tools + \item[Start / Stop Speech Output] Temporarily stops the speech output for errors + \end{description} + +\end{description} + + + + + +\subsection{Eventbuilder-Stop} + +In the case of beam breaks etc. the shift leader decides to +change the mode of data taking or even stop data taking (DAQ +system is still running - in general, writing test files is better +than stopping EB!). + +\begin{itemize} + \item Stop the data taking press the "StopEB" button in the "DAQ +Control" window. In the tactical overview the first button in +the row "EB" the text will change from EB-running to EB-stopped. +Note that it is not necessary to stop before restarting or loading a new prefix. + \item To restart the EB with the current prefix, click on "Restart +EB" in the DAQ-Control + \item To start the EB with a different prefix, click on one of the +buttons "Prefix ...". N.B., that the "Prefix NoFile" button +starts the event builder in dummy mode, i.e. no file is written. +\end{itemize} + + + +\subsection{DAQ-Restart} + +In the case the DAQ is not working correctly, the DAQ has to be +restarted. DAQ-Control provides the necessary operations for +a DAQ restart. + +\begin{enumerate} + \item Press "Start DAQ" to restart DAQ. An orange window appears and +should disappear after 30s-40s if the restart was successful. +An unsuccessful attempt is indicated by an error message in +the orange window. Try a second DAQ restart, if the first +one failed. + \item In the case of an unsuccessful DAQ restart a MDC Power Cycle +has to be performed. The steps of a MDC Power Cycle are described +in the Operator Guide Chapter 34.2. After this operation the DAQ +has to be restarted. Follow the instructions given in step "1)". + \item In the Case "2)" failed, the "RebootMDCHub" icon should be used. +After pressing "RebootMDCHub" and waiting 30 seconds, the DAQ has to be +restarted which is described in "1)". + \item In the case step "3)" was not successful, a "Full Power Cycle" has to be +performed. This procedure is described in the "Operator Guide Chapter 33.1" +Restart DAQ following the steps in "1)" . + \item The DAQ expert has to be called if the DAQ is still not working. +\end{enumerate} + + +All DAQ-Control Tools will open a orange window with their output which disappears +after they finished. Make sure that no two orange windows are open at the same time. +