\item There were boards added to the system for which there is no calibration data available
\end{itemize*}
-It is suggested to run a calibration cycle about once a day (less is fine if temperatures are stable) and when there is a time window available (e.g. when the parasitic user takes over). As temperature is an important factor, the calibration should not be done immediately after power was switched on.
+It is suggested to run a calibration cycle about once a day (less is fine if temperatures are stable) and when there is a time window available (e.g. before we take beam back from the parasitic user). As temperature is an important factor, the calibration should not be done immediately after power was switched on.
There is an icon in the Tactical Overview checking the status of calibration near the lower left corner - it automatically checks the reasons for re-calibration as listed above.
-To do a calibration, use the "TDC Calibration" buttons in the DAQ control window. After clicking "Start TDC Cal", the Tactical Overview will show the (approximate) progress of the process in the lowest row. Once it is completed, use "Stop TDC Cal" to return to the normal data taking mode.
+To do a calibration, use the "TDC Calibration" buttons in the DAQ control window. First, make sure that all boards are running and no front-ends (especially from RICH, ECAL, Start) are missing. If some are missing, follow the usual procedures to recover them.
+
+After clicking "Start TDC Cal", the Tactical Overview will show the (approximate) progress of the process in the lowest row. Once it is completed, use "Stop TDC Cal" to return to the normal data taking mode.
Make sure that the Tactical Overview now shows the new time of the last calibration. If there was a DAQ failure (either restart or failing boards\footnote{Only from ECAL, RICH and Start. MDC is not affected by this run} while the calibration took place, the process has to be repeated.
\section{DAQ control window}
\label{section:daqcontrolgui}
+Most control tasks can be done using the DAQ Control GUI, only few things need access to other tools.
+
\begin{figure}[htp]
\centering
\includegraphics[width=\textwidth]{figures/DaqControl.png}
-\section{Eventbuilder Operator Guide}
+% \section{Eventbuilder Operator Guide}
\label{sec:eboperatorguide}
\subsection{Regular beamtime control}
\section{Power Switches and Supply control}
+\label{powersupplies}
\begin{description}
\item[Start Detector TRB3] ~\\odroid1, \verb!/dev/HAMEG_HAMEG_HO720_020546031!, \url{http://odroid1:1234} \\
Linear power supply for start detector.
\clearpage
\tableofcontents
+\part{General Advice}
+
\cleardoublepage
\part{Control}
\input{daqcontrol}
\section{Eventbuilder restart}
\input{ebstartup}
-\clearpage
-\part{Eventbuilder}
-\input{eboperatorguide}
-
\clearpage
\part{QA}
\section{QA Control}
\input{expertknowledge}
+\clearpage
+\section{Eventbuilder}
+\input{eboperatorguide}
+
-The main power supplies can be controlled
+The main power supplies can be controlled. A full list for the experts can be found in section \ref{powersupplies}.
+
+
\begin{figure}[htp]
\centering
\label{fig:powersupplycontrol}
\end{figure}
\subsection{MDC Chamber}
-\subsection{Full MDC}
-All MDC front-ends (addresses 2xxx) can be power cycled from the DAQ control window.
-In the DAQ Control, use the button "MDC LV Powercycle" in the "Expert Tools" column for this.
-
+If a few MDC boards fail (with a "FEE error" or "MBO w/o data") and a DAQ restart doesn't help (or is needed frequently), a power cycle of one MDC chamber can be performed: Read the address of the failing board (e.g. 2045) from the Tactical Overview. Use the Icon "MDC LV Powercycle" and select the corresponding button (here 204x).
Afterwards, the correct FPGA design needs to be loaded to the OEP. Click the ``RebootOEP'' button. After 10 seconds all OEP are rebooted and DAQ can be started again. If rebooting of the OEP fails, first run a DAQ start-up until the script complains ``OEP design too old''. Close the window and try rebooting OEP again.
+\subsection{Full MDC}
+If it's unclear which part of MDC causes an error, or if there is a larger number of boards failing, you can do a complete MDC power cycle using "EPICS Power" and "MDC Group" instead of using the "MDC LV Powercycle".
+
\subsection{RICH}
All boards of the RICH subsystem (addresses 7xxx and 82xx) are powered by the supplies in the "RICH Group". Use the button "RICH Group ON | OFF" to first switch them off (takes about 10 seconds), wait a few seconds and switch them on again. When all 9 power supplies are active again, do a DAQ restart.
\subsection{ECal / RPC}
+There are two separate power supplies for ECal: The front-ends (Padiwa) can be power cycled using "ECAL 5V Powercycle". After that a DAQ restart is needed to load the correct settings again. The TRB boards share a common power supply with RPC (available in EPICS), so that a "Reprogram FPGA" is needed afterwards.
\subsection{Full Powercycle}
-A full power cycle should only be done after contact to an expert. Use the EPICS window to switch off the RICH and MDC groups, as well as the "MDC/TOF/Central", "RPC/ECAL" and "HUBS" power supplies. Not available in EPICS are the power supplies for Start and Forward Wall and those for ECal frontends. These need to be switched in their respective interfaces.
-
-Then, switch them on again.
-
-Now use "Reprogram FPGA" from DAQ Control to load design files to all FPGAs. Then do a DAQ restart until you see the message ``OEP design too old''. Close the window and use ``RebootOEP'' as described in the "Full MDC" power cycle description.
+A full power cycle should only be done after contact to an expert. A list of necessary steps is found in the Expert Section of this manual.
jspc29 / daqdocu.git / commitdiff