DC DAQ Shift Instruction
DC DAQ Shift Instruction
Version 1.5
23/10/2001
G. Eckerlin
This Document is valid for :
Branch 4 (Central Tracking)
Branch 5 (Forward Tracking)
Branch 6 (Forward Muon)
1. Error during running (mainly L2keep, L3Keep, FER timeouts) :
If you get a run stop or a Central Trigger error caused by one of the branches
mentioned above usually you just have to abort the run if it does not stop itself
and reset the failing branch on the RESET Panel in room 301 (Rack A2 left).
The name of the branch is written on the panel.
! Note Do not reset the Forward Muon Trigger instead of the Forward Muon !
To reset the branch you press the button 2 seconds and wait 20 seconds for the
downloading to finish.
This should be done ONCE only !
You do NOT have to do a WARMSTART. Just start the next run. If it fails starting the run with
"No Run Prepare Acknowledge" reset the system again as soon as the run has
If this fails -> call the EXPERT.
2. Errors during RUN START :
If the system detects a hardware problem it reports it by a yellow message like
"Normal Mode ** Crates OFF ? **" instead of the green "No Error".
In this case see section 5. Hardware problems.
If the system fails during RUN START (eg No Run Prepare Acknowledge)
it restarts itself automatically. This takes 20 seconds, so in case the run stopped
with "No Run Prepare Acknowledge" please wait for the reboot to be completed
(20sec) then try starting again.
If the run start fails again with "No Run Prepare Acknowledge" reset the system
on the RESET Panel (Rack A2 left in room 301) and wait 20 seconds then try
starting a run. If this fails -> call the EXPERT.
3. Errors during WARMSTART :
If the system does a WARMSTART you may see a black message like
"BRANCH 4 restart (20sec)" for each of the 3 systems. If the system finishes the
WARMSTART you should see a message like "BRANCH 4 ready" and the red
flushing WARMSTART signe will change to the green NO ERROR message.
If the systems fails during WARMSTART (eg Calo finishes before any of the above
branches) keep the WARMSTART going (do not abort it) and press the RESET
button as described in (1.) The WARMSTART should finish after 20 second as
normal. If this does not happen try a second RESET during the same WARMSTART
and if this fails the system has either a hardware failure or the software is not
properly loaded anymore. In both cases you have to abort the WARMSTART and go
to the Tracker MACs or Terminals in room 307 :
Branch 4 (CTD): MAC in rack B17 right
The CTD_Supervisor should be seen on the screen (Pic. 4-6).
Branch 5 (FTD): MAC in rack B17 left
The FTD_Supervisor should be seen on the screen (Pic. 4-6).
Branch 6 (FMu): MAC on top of rack B19 left (on top of the shelf)
The Fmu_Supervisor should be seen on the screen (Pic. 4-6).
To see if the Master has crashed you have to look at the terminal output. The program
VersaTerm PRO is running on the MAC in the background and is connected to the
Master CPU. To see the screen of VersaTerm you have to move the mouse to the symbol
shown in right upper corner of the MAC screen and push the mouse button. A menu list
will appear that includes VersaTerm, which you have to select before you release the
mouse button. After that you should see the VersaTerm on the screen (see Picture 1)
Picture 1
If the system crashed you see a register dump like the one before the prompt :
H1monA>
If the software is corrupted you will see in addition above the '----' line :
Error loading Master Code !! reload BOOT RAM !!
or a line staring with :
Exception ....
In both cases you may reload the software to get the system alive again.
(see Chapter 4)
If the last action was a failing WARMSTART you may see one line starting with
BERR/AERR...
Then try again a Reset. If it still is in this state call the EXPERT.
4. Downloading the Tracker DAQ software :
If the system is not able to run after several resets or in the cases mentioned in
Chaper 3 above you may reload the system from the corresponding MAC
(see Chapter 3)
Note ! In case the terminal output does not show any change after a reset or
WARMSTART the connection of the terminal to the master may be lost. For example
in case the trailer had a complete power down this is the case. Then you have to
reestablish the connection before taking any further action (see chapter 10).
For each system there is one Supervisor application running on the MAC. If not
you will find the applications icon on the desktop (see picture 3), it is called
CTD_Supervisor , FTD_Supervisor or FMu_Supervisor respectively.
You start it as usual by double klicking on them and you will see after some time
what is shown on picture 4.
If the application is already running you may have another window active.
To get the BOOT Window you choose the Menu Item BOOT in the Menu Control
on the top of the screen.
Note ! Only if the terminal shows the prompt 'H1monA>' it is possible to download
the software ! If this is not the case you may abort the CPU by selecting the menu item
'Abort CPU' from the 'Experts' Panel. This will cause a current run to crash !
Therefore it should ONLY be done if the system is not properly running !
You first load the software again by klicking on the Load button in the right lower
corner. You will be asked to confirm the load by pressing OK on a small window
showing up. The download will take some time and you will see on the small
textfield left to the load button (where 'Initialisaton done' is written first) the
value 00000000. If you see the value 00000006 or 00000004 or the application
quits with an error then call the EXPERT.
If no error occures then you go on by choosing the Menu item FADC Params
on the Menu Parameters on the top of the screen. You should see what is shown
in picture 5 except that the vaules might be '25' or '30'. Then you hit Download
and the parameters are downloaded. ! Note DO NOT change any of these Values !
Again you will be asked to confirm the load by pressing OK on a small window
showing up. The downloading is then done quickly and you will not realise it.
You then have to set the system back into a proper operations mode this you do by
choosing Configuration in the Menu Control. The picture 6 should be seen on the
screen with the bits set as shown in the picture. You just hit the Download.
After you did the usual confirmation, it will tell you on the left lower side
(where progress is seen first) that the loading was successfull.
Now you have to restart the system by pressing the RESET button in 301 and wait
the 20 second.
You do not need a WARMSTART after this procedure. Just start the next run.
If this fails try resetting as described in Chapers 1 and 2. If you do not succeed
call the EXPERT.
5. Hardware problems :
If the system detects a hardware problem it will report it on the system supervisor
console during Run Start with a yellow message like :
"Normal Mode ** Crates OFF ? **"
The system will automatically switch the crate out of the readout and run with
what remains active. You should nevertheless inform the expert IMMEDIATELY!
You may check the Master output after a WARMSTART or a RESET.
If there is a branch not working correctly it will be seen in the Master output like
the one seen in Picture 2.
Picture 2
The example shows a crate been offline indicated by the line :
WARNING -- Branch x (y:z) not active.
you may also see a message like :
WARNING -- Branch x Acc failure.
Table 1 gives the location of the crate indicated by x or the (y:z) number pair.
First thing you should do is to check if the corresponding crate has it's AC and DC
power ON. If not try to switch it back on reset the branch and start a run.
If you can't get to FADC crate back on the power supply has to be exchanged. -> call expert !!!.
If the crate is on check that the power indicating lights on the FADCs, the Scanner and
the Accelerator (see pictures 7 and 8 ) are on.
If not the corresponding fuse has to be exchanged -> call expert !!!.
If the crate is on and all lights are ok switch the crate off and wait 30 seconds
before you switch it back on again. Then reset the branch and try to start a run.
If after power off/on the branch does not start do a warmstart.
If you still have troubles --> call expert !!!.
6. Test pulse runs :
6.1 Central and Forward Tracker (branch 4 and 5 )
Go to the Readout and Logging Panel :
Select Central Trigger (branch 1) and
Central Tracker (branch 4) or Forward Tracker (branch 5)
(Only one of the tracking branches at a time please !)
Select Permanent Logging and Farm ON in the Readout options.
Turn OFF Level2 and Level4 and select Full reconstructions for the
Filtering+Farm options
Verify the modifications !
Go to the General Trigger Settings Panel :
Set the word to 0 first, then select the NIM1 trigger bit for the Central
Tracker run or the NIM3 trigger bit for the Forward Tracker run.
Verify the modifications !
Set all other Trigger Masks explicitely to 00000000 ! (Verify!)
Go to the Branch Parameters Panel for Central Tracker or Forward Tracker :
Select in the DAQ Mode panel 'TP On' and check that
'Enable Subsystem Control' is active (which is default).
Verify the modifications !
Do a Warmstart to down load the modified parameters for the selected branch.
A successful Warmstart will give a black message 'Branch 4 (or5) restart ...'
in the System Messages window and run stopped after 20 seconds.
(sometimes the message 'branch 4 (or 5) ready' is printed).
If the Warmstart takes longer then 30 seconds see chapter 3.
Start the run.
The event rate should be of the order 2 - 6 Hz and a yellow message "Test
Pulse Mode" is displayed if everything is setup correctly.
A higher rate may indicate other triggers been selected (Check on the
Central Trigger Mac with the Window 'Monitor Trigger Rates')
- The Event size is 10 - 25 kBytes. If it is much less :
1. NIM1 or NIM3 trigger is not selected, additional triggers are selected.
2. The branch is not in the TP mode. (No Warmstart/Verify/Control Enable ?)
Stop the run after 200 events unless there is a request for an extended run.
Important !
The selected tracking branch will NOT be in normal running mode until you do the following :
Go back to the relevant Branch Parameter Panel (Central or Forward):
Select 'Standard Settings' and Verify !
Do a Wamrstart again to download the standard settings for the branch.
(Check that it was successful - see above)
This will set this branch back to LUMI operation.
If you do not contiunue with special runs you also have to set the Trigger and
Readout+Logging to 'Standard Settings' before the next run.
(You do not need a warmstart for that)
Test pulse runs (cont.)
6.2 Forward Muon Detector (branch 6) :
Go to the Readout and Logging Panel :
Select Forward Muon (branch 6) ONLY !
(No other branch in the readout not even branch 1)
Select Permanent Logging and Farm ON in the Readout options.
Turn OFF Level2 and Level4 and select Full reconstructions for the
Filtering+Farm options
Verify the modifications !
No changes for the Trigger Settings Panel :
This run uses a local trigger, the Trigger Settings Panal is ignored.
Go to the Branch Parameters Panel for Forward Muon:
Select in the DAQ Mode panel 'TP On' and check that
'Enable Subsystem Control' is active (which is default).
Verify the modifications !
Do a Warmstart to down load the modified parameters for the selected branch.
A successful Warmstart will give a black message 'Branch 6 restart ...'
in the System Messages window and run stopped after 20 seconds.
(sometimes the message 'branch 6 ready' is printed).
If the Warmstart takes longer then 30 seconds see chapter 3.
Start the run.
The event rate should be of the order 3 - 5 Hz.
- If you get no Events at all the branch is not in TP mode .
(No Warmstart/Verify/Control Enable ?)
Stop the run after 200 events unless there is a request for an extended run.
The run stop may not finish in this mode then you have to abort the run finally.
Important !
The Forward Muon branch will NOT be in normal running mode until you do the following :
(The run will NOT start or at least a lot of error messages will show up!)
Go back to the Branch Parameter Panel for Forward Muon:
Select 'Standard Settings' and Verify !
Do a Wamrstart again to download the standard settings for the Forward Muon.
(Check that it was successful - see above)
This will set the Forward Muon branch back to LUMI operation.
If you do not contiunue with special runs you also have to set the
Readout+Logging to 'Standard Settings' before the next run.
(You do not need a warmstart for that)
7. List of crates :
| Central Tracker |
Forward Tracker |
Forward Muon |
|---|
| Branch | Crate | Location | Crate | Location | Crate | Location |
|---|
| Master | A5M | Master | B3M | Master | M3T |
| 1 | STC | A4M | STC | B3M | STC | M1T |
| 2 | 3:1 | A7B | 1:4 | B4T | 1:1 | M1M |
| 3 | 3:2 | A7M | 1:5 | B5T | 1: | M1B |
| 4 | 2:8 | A5M | 2:4 | B4M | 1:3 | M2M |
| 5 | 1:7 | A5T | 2:5 | B5M | 1:4 | M2B |
| 6 | 2:2 | A4B | 3:4 | B4B | 1:5 | N1B |
<>| 7 | 2:7 | A4M | 3:5 | B5B | 1:6 | N1M |
| 8 | 1:6 | A4T | 1:1 | B6T | | |
| 9 | 3:5 | A9B | 1:2 | B7T | | |
| 10 | 3:6 | A9M | 1:3 | B8T | | |
| 11 | 3:7 | A9T | 2:1 | B6M | | |
| 12 | 3:4 | A8B | 2:2 | B7M | | |
| 13 | 3:3 | A8M | 2:3 | B8M | | |
| 14 | 3:8 | A8T | 3:1 | B6B | | |
| 15 | 2:1 | A5B | 3:2 | B7B | | |
| 16 | 1:8 | A6T | 3:3 | B8B | | |
| 17 | 3:9 | A7T | | | | |
| 18 | 1:1 | A1B | | | | |
| 19 | 1:2 | A1M | | | | |
| 20 | 1:3 | A1T | | | | |
| 21 | 2:4 | A2B | | | | |
| 22 | 2:5 | A2M | | | | |
| 23 | 1:4 | A2T | | | | |
| 24 | 2:3 | A3B | | | | |
| 25 | 2:6 | A3M | | | | |
| 26 | 1:5 | A3T | | | | |
| 27 | 2:9 | A6B | | | | |
Table 1
8. Expert on call :
In case of problems that cannot be solved by the shift call the CJC Expert on call.
If the expert on call is not reachable you may try to get one of the 2 permanent
expert in the list below.
| name | home | phoneMobile/ City phone |
|---|
| CJC On Call | - | -4356495 |
| Guenter Eckerlin | 83293661 | 0175/5837469 |
| Claus Kleinwort | 4802969 | 0175/5837468 |
Table 2
9. DC DAQ Supervisor :
9.1 Starting the Supervisor
Picture 3
If you see the above picture on the MAC the Supervisor is not active or is in the background.
To start the supervisor double klick the icon called CTD_Supervisor97 (or FTD_Supervisor97
or Fmu_Supervisor) seen on the right top of the MAC screen.
You should see after some seconds a screen similar to the one shown in Picture 4.
You might see the VersaTerm window on top of the supervisor, in this case you have to klick
with the mouse in the supervisor window to get it active.
If for any reason you can not get the supervisor running, reboote the MAC and wait for the
reboot to finish, it should automatically start the programs for you.
9.2 Loading the DC DAQ Software from the Supervisor :
Picture 4
If the Supervisor is running correctly on the MAC you will see the above screen.
There might be a different window on the bottom, then you have to select the
Menu item 'boot' under the Menu 'Control' to get the above screen.
As an example the CTD_Supervisor is shown (see name on top in the middle).
Check that you see FTD_Supervisor or FMu_Supervisor respectively if dealing
with the corresponding branch.
NOTE ! Make sure you have read chapter 4 before you go any further !!
The defaults are set properly at startup of the program and should look like the
above except the version number at the end may have changed.
NOTE ! DO NOT CHANGE the values in any of the fields !!
To download the software klick on the load button at the lower right.
A window will pop up asking you for confirmation, if you want to download klick
on the OK button, else Cancel.
The text field will change from 'initialisation done' to '00000000' if everthing is ok.
If you see a value of '00000004' or '00000006' or the program stops with an error
reported by the MAC -> CALL an EXPERT.
9.3 Loading the Parameters from the Supervisor :
Picture 5
If you choose the Menu item 'FADC Params' on the Menu 'Parameter' you will
see the above window.
The defaults are set properly at startup of the program they differ for CTD, FTD and
Fmu Supervisor (The CTD example is shown).
NOTE ! DO NOT CHANGE the values in any of the fields !!
To download the parameters klick on the Download button at the lower right.
A window will pop up asking you for confirmation, if you want to download klick
on the OK button, else Cancel.
9.4 Loading the Configuration from the Supervisor :
Picture 6
If you choose the Menu item 'Configuration' on the Menu 'Control' you will
see the above window.
The defaults are set properly at startup of the program they should look like the
above shown example.
NOTE ! DO NOT CHANGE the values in any of the fields !!
To download the parameters klick on the Download button at the lower right.
A window will pop up asking you for confirmation, if you want to download klick
on the OK button, else Cancel.
10. How to Connect VersaTerm to the Master CPU :
For branch 6 (Forward muon) the MAC is connected via a normal cable to the
Master CPU and there is no action needed to establish a connection.
For branch 4 and 5 (Central and Forward Tracker) follow this instruction.
The connection of the MAC to the Master CPU is done via the F58 terminal switch.
It is connected even if the MAC had to be rebooted. Only in case of a power down in
the trailer or in the 3rd floor the conneciton is lost.
If the system is running correctly and the connection is still ok, you should see a
message on the terminal for each run start or stop with the correct run number.
In case you have problems with the system and you are not sure if the connection
is ok you may reset the branch. In this case you must see something printed on the
screen, if not the connection has to be reestablished.
First press <ð><enter> ! Both keys together and not <shift><return>!
You will see "Welcome to the H1 terminal switch" followed by a list of options
labeled by characters. If not restart the MAC and try again.
If it fails again call the expert , else follow the instruction below.
NOTE ! If you do not type anything, a timeout will occure and you have to start
from the beginning (<shift><enter>). In case you selected a wrong option you may
also start from scratch by just hitting <shift><enter>.
In the following you have to type the character listed for the option you want to
choose without return unless explicitely stated.
To establish the connection to the corresponding master do the following after the
"welcome" message of the F58 switch :
Hit <n> (to establish a new link)
-> A list of available groups will appear.
Enter 13<return> (to select the Tracker_F58 switch)
-> A list of terminals will be listed, some of them are used. You just
hit <return> to select any unused terminal.
-> A new message for the Tracker_F58 will show up with a list of options.
hit <n> (to establish a new link)
-> A list of available groups will appear again.
Enter 1<return> (to select Central Tracker Main links)
or enter 3<return> (to select Forward Tracker Main links)
-> A list of available terminals will be shown.
Select the terminal labeled "CTD Master" or "FTD Master" respectively by entering
the corresponding number (1) and hit <return>.
A message will be displayed like :
"Link established with : CTD Main CTD Master" (Central Tracker example)
Now the VersaTerm should be properly connected and after a reset of the branch
you should see the Master printout.
Check it to see if it reports any error. If not, try to start a run.
11. DC DAQ Hardware :
11.1 FADC crates
Picture 7
This pictuer shows a typical Tracker DAQ FADC crate with the Accelerator, the
Scanner and 15 FADCs. Left to the Accelerator there are 2 more boards in the crate
which are not shown here.
If for any reason The crate is of you may switch it on by pressing first AC ON/OFF
then DC ON/OFF. If the LOCAL CONTROL light is off the control is disabled for the
panel, then you have to press the LOCAL CONTROL ON/OFF first, and then switch the
crate ON.
If the crate is ok you should see the power indicators of all cards been ON (see picture 8).
Blinking lights on the right side labeled Voltage/Current Monitors, indicate a fault in the
system, but usually this fault is not vital and if the crate stays on you still can take data.
The experts will deal with this errors if needed.
11.2 FADC and scanner Fuses
Picture 8
This picture shows were the power indicator lights are located on the different
boards. If one of them is off an expert has to change the fuses before the system
can go back to operation. DO NOT change the fuses of Accelerator or Scanner
yourself, because there is a high risk do damage the boards if you take them out of
the crate. You may exchange the FADC fuses, if you know how to take a board out
and back in to a VME crate. (Spare fuses you find in a small plasitc bag attached to
RACK B4)
11.3 Power Supplies
Picture 9
This picture shows the back of a FADC crate. If you have to exchange a power supply
make sure you have a second person to help you, because the power supplies are realy
heavy. To exchange the PS switch the crate off first, (AC and DC) then disconnect the
mains cable at the back. The PS is fixed with 2 clips, one on each side at the bottom.
If you opened the clips you may slide the PS back out of the crate.
! WARNING! The Signal cables run on top of the PS and some control cables run on
the side of the crate down or up the rack, they are fragile and you may easily cut or
damage them by moving a PS out or in ! Please be very carefull.
THIS is an EXPERT action and is is not ment to be done by a normal shift person!
12. Crate Address Maps (NOT BDC!!)
12.1 Master crate
| from | to Adress | Crate | Module | Purpose |
|---|
| 0xC0000000 | 0xC0FFFFFF | Master crate | 16 MB DPM | old MEB |
| 0xC1200000 | 0xC12FFFFF | STC crate | VIC | Eventbuffer |
| 0xC2100000 | 0xC2xFFFFF | FADC crates 1:x | VIC | Eventbuffer |
| 0xC3100000 | 0xC3xFFFFF | FADC crates 2:x | VIC | Eventbuffer |
| 0xC4100000 | 0xC4xFFFFF | FADC crates 3:x | VIC | Eventbuffer |
| 0xC5200000 | 0xC52FFFFF | STC crate | CPU | Triggerproc. |
| 0xC6100000 | 0xC6xFFFFF | FADC crates 1:x | CPU | FADCprocessor |
| 0xC7100000 | 0xC7xFFFFF | FADC crates 2:x | CPU | FADCprocessor |
| 0xC8100000 | 0xC8xFFFFF | FADC crates 3:x | CPU | FADCprocessor |
| 0xD0000000 | 0xD01FFFFF | Master crate | Taxi (2MB) | MEB |
| 0xD0200000 | 0xD03FFFFF | Master crate | DPM (2MB) | Monitor DPM |
|
| 0xD0800000 | 0xD08FFFFF | Master crate | VIC | Chain 0 |
| 0xD0900000 | 0xD09FFFFF | Master crate | VIC | Chain 1 |
| 0xD0A00000 | 0xD0AFFFFF | Master crate | VIC | Chain 2 |
| 0xD0B00000 | 0xD0BFFFFF | Master crate | VIC | Chain 3 |
| 0xD0E00000 | 0xD0FFFFFF | Master crate | DPM (2MB) | Boot DPM |
| 0xD6000000 | 0xD6FFFFFF | Master crate | RTPC | Qtproc Chain1 |
| 0xD7000000 | 0xD6FFFFFF | Master crate | RTPC | Qtproc Chain2 |
| 0xD8000000 | 0xD6FFFFFF | Master crate | RTPC | Qtproc Chain3 |
12.2 STC crate
| from | to Address | Crate | Module | Purpose |
|---|
| 0xD0900000 | 0xD09FFFFF | STC crate | VIC | Event buffer |
| 0xDF000000 | 0xDF0000FF | STC crate | FASTCard | Trigger |
| 0xDF003000 | 0xDF0030FF | STC crate | SLOWCard | Trigger |
| 0xDF004000 | 0xDF004FFF | STC crate | TbitsCard | Trigger |
| 0xDF101000 | 0xDF1010FF | STC crate | LOGICCard | Trigger |
| 0xDF001000 | 0xDF001FFF | STC crate | FANOUTCard1 | Trigger Type1 |
| 0xDF002000 | 0xDF002FFF | STC crate | FANOUTCard2 | Trigger Type2 |
12.3 FADC crate
| from | to Address | Crate | Module | Purpose |
|---|
| 0x48000000 | 0x483FFFFF | FADC crates | Accelerator | Data buffer |
| 0x40280000 | 0x4028FFFF | FADC crates | VIC | Event buffer |
| 0xD0900000 | 0xD09FFFFF | FADC crates | VIC | Event buffer |
| 0xD0C00000 | 0xD0CFFFFF | FADC crates | Scanner | Data processor |
| 0xD0E00000 | 0xD0E0xFFF | FADC crates | FADC (x=0-F) | Data pipeline |