From b327ecb967e960d648317ecba96e3b954ab5f410 Mon Sep 17 00:00:00 2001 From: hadeshyp Date: Thu, 29 Mar 2012 14:49:19 +0000 Subject: [PATCH] *** empty log message *** --- daqop_short.txt | 76 ++++++++++++++++++++++++++++++++++--------------- epics.tex | 36 +++++++++++++++++++++++ main.tex | 3 +- 3 files changed, 91 insertions(+), 24 deletions(-) diff --git a/daqop_short.txt b/daqop_short.txt index bd3add3..c53bc17 100644 --- a/daqop_short.txt +++ b/daqop_short.txt @@ -2,7 +2,8 @@ What is the starting point? --------------------------- Open the DAQ-Control GUI (HadesControl Icon), click on "Hmon". A firefox window will -appear. Click on "Tactical Overview". +appear. Click on "Tactical Overview". If firefox fails to start from the button, start +it manually and direct it to http://hades33/mon DAQ-Operation: -------------- @@ -11,7 +12,9 @@ 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" offers a description of typical situations during data +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. @@ -26,28 +29,45 @@ DAQ problems. The "HadesControl" Icon starts DAQ-Control. describes the use of these buttons. "Monitor Tools" contain all observation windows. - "CTS Mon": Opens the CTS Monitor. - "Hmon": Click on "Tatical Overview" in the new Firefox window to get - "Epics":Opens the Epics Monitor. - "Epics FB": Shows a status window containing Eventbuilder - information. - -"Eventbuilder Tools" are necessary for an Eventbuilder restart. Details are -described in the "Eventbuilder-Stop" guide. - - - + - "CTS Mon": Opens the CTS Monitor. + - "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 + - "Epics":Opens the Epics Monitor. + - "Epics FB": Shows a status window containing Eventbuilder + information. + - "Daq VNC" Opens the VNC window for DAQ control used during preparation + - "Chat" The DAQ users chat window + + +"Eventbuilder Tools" are necessary for the control of Eventbuilders. + - "Stop EB" stops all EB. + - "Restart EB" starts the EB with the last settings again + - "Prefix XX" restarts the EB and sets the file prefix to a new one + +"Expert Tools" + - "CTS Scope" Opens the window oscilloscope connected to the CTS for + signal adjustment + - "Reload RPC Thresholds" Loads the settings for trigger boards of RPC + in case the count rates on the CTS monitor are wrong + - "Restart EB IOC" If some of the entries in the Epics Eventbuilder Monitor + are white, use this button to restart them + - "Restart Hmon" Restarts the browser-based monitoring tools + - "Start / Stop Speech Output" Temporarily stops the speech output for errors + 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). +system is still running - in general, writing test files is better +than stopping EB!). 1. ) 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. 2.) To restart the EB with the current prefix, click on "Restart EB" in the DAQ-Control @@ -56,31 +76,41 @@ EB" in the DAQ-Control buttons "Prefix ...". N.B., that the "Prefix NoFile" button starts the event builder in dummy mode, i.e. no file is written. + + 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. -1. ) Press "Start DAQ" to restart DAQ. An orange window appears and +1) 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. -2. ) In the case of an unsuccessful DAQ restart a MDC Power Cycle +2) 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. )". +has to be restarted. Follow the instructions given in step "1)". -3. ) In the Case "2. )" failed, the "RebootMDCHub" icon should be used. -After pressing "RebootMDCHub" the DAQ has to be restarted which is described in -"1. )". +3) 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)". -4. ) In the case step "3. )" was not successful, a "Full Power Cycle" has to be +4) 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.)" . +Restart DAQ following the steps in "1)" . + +5) The DAQ expert has to be called if the DAQ is still not working. + + + + -5. ) The DAQ expert has to be called if the DAQ is still not working. +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. diff --git a/epics.tex b/epics.tex index e88a4e0..2ac10e6 100644 --- a/epics.tex +++ b/epics.tex @@ -37,5 +37,41 @@ dbl ==> gives you list of PVs. then quit +\end{verbatim} + +\subsection{DreamPlug} + +In the case of a failure of the DreamPlug, please reboot several times. +If this is not successful, then attach then please attach the +``GuruPlug JTAG board'', only the smaller connector (``UART''). +Then you can start on a laptop + + + +\begin{verbatim} + +picocom -b 115200 /dev/ttyUSB0 +(picocom: exit via: ctrl-a + ctrl-x + +# to boot from the internal SD-card +setenv x_bootcmd_kernel fatload usb 0 0x6400000 uImage +setenv x_bootargs_root root=/dev/sda2 rootdelay=10 +saveenv +reset + +# to set the device to boot from an external USB-stick +setenv x_bootcmd_kernel fatload usb 2 0x6400000 uImage_2.6.33.7 +setenv x_bootargs_root root=/dev/sdc2 rootdelay=10 +saveenv +reset + + +#USB stick root password: nosoup4u + +# if everything fails: +# overwrite the internal SD-card with an image (the one on the stick) +gzip -cdv /backup_ee_dev007_sda.raw.gz | dd of=/dev/sda bs=1M + \end{verbatim} + diff --git a/main.tex b/main.tex index 2c23c23..2300557 100755 --- a/main.tex +++ b/main.tex @@ -52,7 +52,8 @@ \title{A Users Guide\\to the\\HADES DAQ System} \date{\today ~-~\thistime} -\author{Jan Michel, J\"orn Adamczewski-Musch, Michael B\"ohmer, Grzegorz Korcyl, \\Marek Palka, Sergey Yurevich} +\author{Jan Michel, J\"orn Adamczewski-Musch, Michael B\"ohmer, Grzegorz + Korcyl, \\Marek Palka, Sergey Yurevich, Michael Traxler} \newcommand{\filename}[1]{\textit{#1}} -- 2.43.0