+\section{Error Messages During Start-Up}
+
+\paragraph*{Found Fifo not empty in \$logFile. Problem with TRB-Net?\\
+ Found TX Busy in \$logFile. Problem with TRB-Net?\\
+ ERROR: data2ora(): 'daqop read ids' failed!\\
+ ERROR: when reading compile times of \$sys: \$line} ~\\
+The DAQ restart did not work due to a problem in the TrbNet. Try start-up again. In case of repeated failes, try a complete power
+cycle.
+
+\paragraph*{Found Verification Failure in \$logFile. Problem with jam-programming?}~\\
+Programming the FPGA did not work properly. Try to program FPGAs again. A power cycle / reboot of
+the board in question can help. Also, try to properly fix the connection between TRB and AddOn.
+
+\paragraph*{Unused macro names: \$names }~\\
+There is a problem in the call of the start-up script, one of the macro names given with -m is not
+found in the configuration files. Check the spelling of makro names in \verb!startup_briccolage!.
+
+\paragraph*{ERROR: \$trbname, TDCx: mode\_rc\_compression is not defined \\
+ ERROR: \$trbname, resolution modes must be identical for all four TDCs!\\
+ ERROR: \$trbname, resolution modes have wrong values!}~\\
+Check the configuration files for TDC configuration on TRBs.
+
+
+\paragraph*{ERROR: addr2serial(): unknown serial number for address \$addr \\
+ ERROR: serial2addr(): unknown address for serial number \$serial}~\\
+A problem with a combination of serial numbers and network addresses - no matching pair could be found. Check configuration files.
+
+
+
+\paragraph*{ERROR: serial2addr(): unknown board system type for serial number \$serial\\
+ ERROR: boardSysType(): unknown board system type for address \$addr\\
+ TRB-Net address \$addr is outside of the known address ranges}~\\
+The addresses of the boards must be in the ranges defined in \verb!daq/main/address_range.db!, so that the script can identify
+the type of the subsystem (CTS, TOF, etc). Check configuration files for network addresses and serial numbers.
+
+
+\paragraph*{ERROR: boardSysType(): unknown board type for address \$addr\\
+ ERROR: boardType(): unknown board type for address \$addr }~\\
+The addresses of the boards must be in the ranges defined in \verb!daq/main/address_range.db!, so that the script can identify
+the type of the board (TRB, Hub2, etc). Check the configuration files for network addresses and serial numbers.
+
+\paragraph*{ping \$host returned unknown status}~\\
+This message could appear if something goes wrong with the ping call. Never happened...
+
+\paragraph*{Cannot connect to the following hosts}~\\
+A network connection to a specific board failed. Check configuration files and current set-up in the cave, if the mentioned board is
+really supposed to be available. Try to connect / ping board by hand. Try a power cycle.
+
+\paragraph*{Try to start command\_server -p 4712 \& on these hosts by hand}~\\
+The network deamon that is used to execute commands on the boards mentioned above is not running and could not be started.
+Log in to the board in question and run the command mentioned. Try to kill all running command\_server processes on this board.
+Try a reboot of this board.
+
+\paragraph*{Compile time for \$sys \$local\_addr is too old!}~\\
+The listed OEP are not booted with the correct FPGA design. Reboot OEP with correct design:
+\\\verb!daqop set flash 1 oep; daqop reboot oep!
+\\Then start DAQ again.
+
+\paragraph*{Error: Board type '\$type' specified in 'Value table' in \$register is most likely not defined in 'Register table'}~\\
+There is an error in a \verb!register*.db! file. Correct the error, then start DAQ again.
+
+
+\paragraph*{Encapsulated ifdef/ifndef are not supported.\\
+ The sequence of directives looks fishy}~\\
+Syntax error in the configuration scripts regarding macro ifdef constructs.
+
+\paragraph*{Something wrong with a format of \$filename.db}~\\
+Syntax error in the given configuration file.
+
+
\section{General DAQ Issues}
\subsection{Full Power Cycle}
A full power cycle of all power supplies for the DAQ system is a straight-forward process with several steps.
\item Re-plug up-link
\end{itemize}
+\subsection{Switch off a board that causes errors}
+In some cases it is necessary to switch off one front-end board because of errors.
+
+
+\begin{figure}[htb]
+ \centering
+ \includegraphics[width=.6\textwidth]{HubMonitorBusy.png}
+ \caption[Hub Monitor - Busy]{Part of the Hub Monitor showing one busy front-end}
+ \label{fig:hubmonitorbusy}
+\end{figure}
+
+\paragraph*{Given: Busy Board in Hub Monitor}
+Usually, a broken board causes a busy in the DAQ and shows up in the Hub Monitor with a purple hash as shown in figure~\ref{fig:hubmonitorbusy}.
+
+In most cases, several purple hashes are shown, one for each network link that connects the front-end to the central network hub.
+You have to find the link that connects a hub to the problematic front-end itself.
+
+In the example shown, hub 0x1003 reports a busy link on port 3.
+If you are unsure if this is the front-end connection, test all links reported by hashes with \verb!whatis.pl! until you
+end up with a board address that neither starts with 1 nor 8 and is not of the form 0x32-0 (all these addresses
+are hubs and no front-ends). \verb!whatis.pl 1003 3! reports, that board 0x2122 is connected to this port. This is a
+front-end and can be switched off.
+
+
+\paragraph*{Given: Board Address} If you already know the front-end address (e.g. 1234), use
+\\\verb!whatis.pl 1234! to find the port this front-end is connected to.
+
+\paragraph*{Switch Off} Given the hub address and the port number you can switch off the port:
+\\\verb!daqop switch hub ax1003 port 3 off!
+
+Running this command switches off the port until the next DAQ restart. For a permanent switch-off, the command has to be added
+to the \verb!startup_briccolage.sh!. Put the command in before the call of the \verb!startup.pl!.
+
+
jspc29 / daqdocu.git / commitdiff