the Central Muon Readout System
The program that is responsible for the control of the Central Muon Readout processors is called "Muon Data Aquisition". It can be started by double-clicking on the corresponding Icon on the Desktop of the Macintosh "Muon Daq Control". On startup, the program automatically goes into the "shift actions" Mode, where dangerous actions, as modifying the Setup etc. are disabled.
The Windows to be touched by the shift crew are
This window shows Information about the Events, which are currently treated by the Coordinators Monitoring- and Histogramming Routines. Since not all, but only a small fraction of events are subject to these routines, the display is not updated very fast. Especially in low rate runs the updating-times can be rather big, so do not worry, if the Event Number is not updated every second.
Also shown in this Window are the Messages, the processors deliver to the Mac. This Display can be scrolled, to check former Messages. Here, you can find error Messages, which can help to find the reason for a run crash.
This Window allows you to
There are several procedures to get readout program working again. All the procedures require a stopped or aborted run , and they should end with Messages coming up on the Muon Daq Mac :
13:59:Crd ->******************************************* 13:59:Crd ->* * 13:59:Crd ->* Central Myon System Data Aquisition * 13:59:Crd ->* * 13:59:Crd ->* bootstrap succesful * 13:59:Crd ->* * 13:59:Crd ->*******************************************
This Procedure is the normal way of starting the system, when there was a change in the Muon Setup Files, or after a power failure in one of the crates. When the run is stopped, just press on the button "reboot all" and wait for the Messages in the Message window to stop scrolling. If there is no "Buserror dump" and the FIC terminal above the Mac shows no cursor, the startup was successful. If the startup was not succesful, the go on with Procedure 3.
If you try this procedure, the normal startup did not work. Sometimes, because of pending interrupts, the Coordinator cannot reset properly all the ClusterProcessors. To solve the problem click on the button "reset all" on the window "CDAQ Commands" and afterwards, try Procedure 2. If the startup was now sucessful, be happy and restart the run. If it was not successful, see section trouble shooting.
This procedure is to call the DAQ expert.
If the readout program cannot be started correctly with one of the Procedures described above, there may be a hardware Problem. First look at the FIC terminal above the control Macintosh. If it shows a register dump, then look at the Entry "FAD" of this dump. If this entry is D0Dxxxxx where xxxxxx is a hexadecimal Number, go to the crate of Cluster D, switch it off for 30 sec. and then switch it on again. after that, try to restart the system with one of the procedures described above
If terminal shows a blinking cursor and above this, one of the last Messages is "stop at XXXXXXXX" where XXXXXXX is a Hex Number, look on the Message output on the Control Macintosh. There should then be messages of the form that are demonstrated in Table 1
01:38:Crd ->Buserror at Adress D0D03018, PC 20022E30 01:38:Crd ->Buserror at Adress D0D03020, PC 20022E30 01:38:Crd ->Buserror at Adress D0D03084, PC 20022E30 01:38:Crd ->######################## 01:38:Crd ->Buserror at Adress D0D03098 01:38:Crd ->StackPtr 801CF16 01:38:Crd ->Processor Status 2300 01:38:Crd ->Buserror at Program Counter 20022E30 01:38:Crd ->format LWd B008 01:38:Crd ->aborted after 3 retrys 01:38:Crd ->last retry BusErr at D0D03084 01:38:Crd -> at Routine $15E+startProcessors 01:38:Crd ->d0 26 d1 AB8 01:38:Crd ->d2 0 d3 9002308 01:38:Crd ->d4 800070C d5 70407 01:38:Crd ->d6 8C d7 0 01:38:Crd ->a0 2002EFF4 a1 D0D03098 01:38:Crd ->a2 10000000 a3 800070C 01:38:Crd ->a4 801CF16 a5 20030DE4 01:38:Crd ->a6 801CF12 a7 801CF16 01:38:Crd ->########################
Table 1: Messages that will appear, if one Processor detects a
Buserror. This mostly shows a problem on the communication with one of
the Cluster Processors
If that is the case, go and look for crates which are off, and if all are on, switch off and on Cluster D After that, reload the readout program with one of the Procedures described above.
If you receive only few such Messages on the Log Panel of the H1 supervisor
program ( one per 5 Minutes ), then write this into the Dig. Muon Logbook
and do not worry.
Otherwise :
You find a summary of the Problems, that occurred in the Message Window of the Daq Program, when the run was stopped. (See Table 2)
15:13:ClusE ->####Mapping Error Report 15:13:ClusE ->Cnt 3 Roc# 2D Bus# 10 Element# 7 Map 40 15:13:ClusE ->Cnt 1 Roc# 19 Bus# 14 Element# 8 Map 40 15:13:ClusE ->Cnt 1 Roc# 2A Bus# 10 Element# 7 Map 40 15:13:ClusE ->Cnt 1 Roc# 2A Bus# 14 Element# B Map 1
Table 2: Summary of the errors that occurred while mapping and
checking the data
The entries mean the following:
This document was generated using the LaTeX2HTML translator Version 96.1 (Feb 5, 1996) Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds.
The command line arguments were:
latex2html -split 0 -html_version 3 -dir shiftins ShiftInstructions.tex.
The translation was initiated by Claus Keuker on Thu Jan 30 21:06:46 MET 1997