From: hadeshyp Date: Tue, 16 Nov 2010 12:53:37 +0000 (+0000) Subject: *** empty log message *** X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=a6fa9a19c46b4d331de0ea9fdb76d5083ba20e95;p=daqdocu.git *** empty log message *** --- diff --git a/daqcontrol.tex b/daqcontrol.tex new file mode 100644 index 0000000..92ba90b --- /dev/null +++ b/daqcontrol.tex @@ -0,0 +1,55 @@ +\section{DAQ Control Scripts} +All main scripts to control DAQ are available on the desktop of all DAQ computers. They are grouped as shown below: +\subsection{DAQ Main Tools} +\begin{description} + \item[DaqManual] Downloads the current version of the DAQ manual from the web server and opens it. + \item[DaqVNC] Opens the normal DAQ control VNC on \verb!lxhadesdaq:1!. During beam-times, this VNC should only be used + to run small monitoring scripts. No DAQ control should be done from this screen. In case of problems, this screen will be + used by DAQ experts. + \item[DaqMonitorVNC] A small VNC screen that is forseen to show the basic monitoring tools. This VNC can only be controlled + from one of the two DAQ computers in the counting house, from everywhere else access is read-only. +\end{description} + +\subsection{DAQ Control Tools} +\begin{description} + \item[ReprogramFPGA] Programs all FPGAs in the system which are accessible via JTAG from TRBs. Other FPGAs can be rebooted by + sending the \verb!daqop reboot all! command from a console. N.B. the CTS always needs to be programmed by hand due to conflicts + with rw\_trbv2 scripts. To do this, please call an expert. + \item[StartDAQ] Starts the DAQ with default settings as defined in \\\verb!~/trbsoft/daq/main/start_briccolage.sh! \\In case of + problems, the scripts will ask the operator whether to proceed or not. In most cases, answer "no". Answering "yes" might be useful + in case of certain errors, but DAQ will not work afterwards in general. + \item[StartEbBeam] (Re-)Starts the eventbuilders in default configuration, writing files with prefix be. + \item[StartEbCosmics] (Re-)Starts the eventbuilders in default configuration, writing files with prefix co. + \item[StartEbTest] (Re-)Starts the eventbuilders in default configuration, writing files with prefix te. + \item[StartEbNoFile] (Re-)Starts the eventbuilders in default configuration, but writing no files to disk. Small files for QA are + produced nevertheless. + \item[StopEb] Stops the eventbuilders. +\end{description} + +\subsection{DAQ Monitor Tools} +\begin{description} + \item[CtsMonitor] Starts the CTS monitor (perl edition) - the Epics interface can be found on the main Epics screen. + \item[EbEpics] Starts the Epics monitoring tools for Evenbuilders. Screens are described in section \ref{sec:ebmonguide}. + \item[EbLogWatch] Starts the Logfile monitor for the Eventbuilders. The blue window contains a list with all messages from eventbuilders. + The green screen always shows the latest hld-file written to disk on each of the servers. + \item[Epics] Starts the main Epics interface + \item[GbeMonitor] Starts the monitoring tools for Gbe Links on FPGAs + \item[GlobalMonitor] The global monitor shows an overview of busy times, error flags and missing TRB (not correctly working at the moment) + \item[HadplotBeam] Shows plots of the beam structure - settings can be done using the Epics->CTS->Beam Structure interface + \item[HadplotMain] Shows the main plots with event rate, data rate and busy times + \item[HadplotError] Shows some error plots to see issues with timing triggers and transmission errors on the optical links + \item[HubMonitor] The Hub monitor shows the status of all optical links in the system, whether they are running or not connected. Additionally + the busytime of each link (LVL1 busy only) is shown in multiples of 10 per cent. + \item[LoggerWatch] Start monitor of logfile for DAQ and Eventbuilder starts and stops generated with logger +\end{description} + +\subsection{DAQ Expert Tools} +\begin{description} + \item[EbCpuMonitor] Opens gkrellm on all eventbuilding servers to monitor CPU, memory, disk and network load. + \item[StartDaqVnc] Starts the DAQ monitor VNC server - only to be used after machine has been rebooted + \item[StartEbRich] (Re-)Starts the eventbuilders in default configuration, writing files with prefix ri. + \item[StartEbShower](Re-)Starts the eventbuilders in default configuration, writing files with prefix sh. + \item[StartEbStart](Re-)Starts the eventbuilders in default configuration, writing files with prefix st. + \item[RichLoadPedestals] Loads RICH pedestals + \item[RichInitADCM] Reinitializes the RICH ADC modules +\end{description} diff --git a/ebmissingmbo.png b/ebmissingmbo.png new file mode 100644 index 0000000..18afc3b Binary files /dev/null and b/ebmissingmbo.png differ diff --git a/ebmonitorguide.tex b/ebmonitorguide.tex index 9660efc..0253ce8 100644 --- a/ebmonitorguide.tex +++ b/ebmonitorguide.tex @@ -1,3 +1,4 @@ +\label{sec:ebmonguide} \begin{figure}[hp] \centering \includegraphics[width=.9\textheight,page=1,angle=90]{ebmonitordescription.pdf} diff --git a/main.tex b/main.tex index cfe799b..ffbfb42 100755 --- a/main.tex +++ b/main.tex @@ -175,10 +175,13 @@ \part{Operator Guide} \section{Eventbuilder Monitor Guide} \input{ebmonitorguide} +\clearpage \part{Instructions} -\section{MDC Maintanance} +\input{daqcontrol} \input{mdcinstructions} +\input{showerinstructions} +\input{richinstructions} \clearpage \bibliography{biblio} diff --git a/mdcinstructions.tex b/mdcinstructions.tex index accde0c..96d57c1 100644 --- a/mdcinstructions.tex +++ b/mdcinstructions.tex @@ -1,6 +1,36 @@ -\begin{figure}[hp] +\section{MDC DAQ} +\subsection{Missing Motherboards} +\begin{figure}[htb] \centering - \includegraphics[width=.9\textwidth]{mdcpowercycle.png} + \includegraphics[width=.8\textwidth]{ebmissingmbo.png} + \caption[MDC Missing MBO]{MDC Missing MBOs} + \label{fig:mdcmissingmbo} +\end{figure} + +Missing Motherboards (i.e. MBO not sending data) can be found in the QA-Plot, window ``MDC'', tab ``Mb'' as shown in figure~\ref{fig:mdcmissingmbo}. +If the board is not sending data, but still available in the DAQ-network, a reinit of the MBO might help. + +To see if the board is still reacting on network accesses, one needs to have its address. The address is 0x2PSM where P is the plane (starting from 0), +S is the sector (0 -- 5), and M is the motherboard number (0 -- F) as seen in the QA plot. To test the connection, run +\\\verb!trbcmd r 0x2PSM 0! +\\If this gives back a number, the board is there and a reinit can be done. To do this, run the following command from any console on the DAQ computers: +\\\verb!trbcmd w 0xfffd 0x20 0x200! +\\This will force all OEP to reinitialize the Motherboards after the next trigger from CTS. If this procedure does not work or the board is not visible in +the network at all, do a MDC power cycle. + +\subsection{MDC Power Cycle} +If the MBO does not send data afterwards or was not accessible in the DAQ, one needs to to a power cycle. Go to the main EPICS screen, select ``Crates'', +then ``Group ON | OFF'' on the left side as shown in figure \ref{fig:mdcpowercycle}. Switch power off, wait 5 seconds, switch it on again and wait another 10 seconds. + +\begin{figure}[htb] + \centering + \includegraphics[width=.8\textwidth]{mdcpowercycle.png} \caption[MDC Power Cycle]{MDC Power Cycle} \label{fig:mdcpowercycle} -\end{figure} \ No newline at end of file +\end{figure} + +Afterwards, the correct FPGA design needs to be loaded to the OEP. This is done with the commands +\\\verb!daqop set flash 1 oep; daqop reboot oep! +\\After 10 seconds all OEP are rebooted and DAQ might be started again. If rebooting of the OEP fails, +first run a DAQ start-up until the script complains ``OEP design too old''. Answer with ``No'' and start again +with the command above. \ No newline at end of file diff --git a/richinstructions.tex b/richinstructions.tex new file mode 100644 index 0000000..70936ad --- /dev/null +++ b/richinstructions.tex @@ -0,0 +1,6 @@ +\section{RICH DAQ} +\paragraph*{Reinitialize APVs / Load new pedestals} +There is a script to reload pedestals: +\\\verb!cd /home/hadaq/trbsoft/dat/rich/; ./wr_peds.sh! + +Another script diff --git a/showerinstructions.tex b/showerinstructions.tex new file mode 100644 index 0000000..ccd2663 --- /dev/null +++ b/showerinstructions.tex @@ -0,0 +1,4 @@ +\section{Shower DAQ} +\paragraph*{Shower Thresholds} +Set shower thresholds - the last hex digit (0x4) is setting the thresholds to the given value. +\\\verb!trbcmd loadbit 0xfff7 0xc0 0xF 0x4!