Contents:

0. Power Up Procedure
1. Download and Monitoring
2. Take Data to L3
3. Take a SDAQ Calibration Run
4. Start the SDAQ Monitoring
5. Run SMT Examine
6. Power Down Procedure
7. Trouble Shooting
 

Online version: http://www-d0.fnal.gov/~d0run/SMT/doc/ShiftInfo.html

For this instructions it is assumed that data taking is done with crate 0x69, whereas the SDAQ calibration run is done with crate 0x63.

0. Power Up Procedure

1. Switch on the sequencer crate on MCH2 rack M204.
2. Power up VRB crates 0x63 (M206), 0x67 (M208), 0x69 (M210), and 0x6b (M211):
1. Make sure all fault LEDs are lid (no fault). If one is lid:
1. Go to the back of the rack.
2. Push and hold the `Smoke Det. Reset' button.
3. Push and hold the `Fault Reset' button (Fan should start, all LEDs should be lid).
4. Push the PS on button.
2. Use the right lever to switch the power for the bottom crate on.
3. Wait until the 2 blue light on the VRBC front panel go off (~3 sec).
4. Push the reset button on the VBD (the only button). Make sure the `BUSERR' light on the VBD goes off (keep hitting reset).
3. Download the emulators (see below).

WARNING: This might work only from the account smt10p. Contact Fritz or Geoff if you need this. Normal D0 shifts don't need this at the moment.
If you are running the real Detector (H-Disk, or Barrel):
Change the direcotry : cd /online/config/smt/
setup onl_apps
./SmtIbDab

The following window should pop up:

The Status before download might be different.
 
 

Do the following from your teminal to do the download:

setup onl_smtcalib
dbgui

This pops up the main menu shown below:

Once after power up the emulators need to be initialized: Click the `emulators' button to open the following window:

Initialize all by clicking on the `init all' button. Alternatively you can initialize a single sequencer (SVXE-3002 is connected to crates 0x69 and 0x6b) the following way:

• left click on `SVXE-300x', a menu pops up
• subsequently click on `reset', `load FiFo', `set enable'
• close the pop up menu by right clicking on one of the items
• you may close the emulator window now

Use the scroll bar in the lower part of the window to check the complete data output.

If the result does not look like this,  try to take a couple of cal inject events (hit the `next' button or the `cal inj' button again).  If that doesn't help the download went wrong. Check the trouble shooting item.
 

2.  Take Data to L3

Make sure that the download (Step 1.) is done.
Go to the Taker window. Select the menu item `modify/change trigger'.
Select the file pulser-smt-0x69-3.0 from the tracking sub-directory.
Hit the start button.
You should see events coming in from L3 now. If not, look at the Trouble Shooting Section.
 

3. Take a SDAQ Calibration Run

Make sure that the download (Step 1.) is done.
Go to the Taker window. Select the menu item `modify/change trigger'.
Select the file calib-smt-0x63-1.0 from the tracking sub-directory.
Hit the start button:

1. Check that the "download" from taker is performed correctly
2. Don't expect the taker window to show you any progress information (0 Hz, 0 events)

1. Select the SMT page
2. The crate selected by the configuration file is marked blue

1. Abort the run in the Calib_Manager_GUI window
2. Reset the front end processor
3. Wait 2 minutes
4. Download the crate again (`download' button on main window)
5. Try the calibration run again
6. If the error persists: call the expert

4. Start the SDAQ Monitoring

setup onl_smtcalib devel
ssdaq
account: smt_calib@d0onprd1
password:

The following window pops up:

Choose the correct crate, `VRBCR-63' , the VRB that you want to monitor (`VRB-6301'),  an HDI in that channel (`SVXE-6903_C'), or a chip of that HDI (`SVXE-6903_C_00). You can monitor complete Crates, VRBs, HDIs, or single chips. Note that some choices are disabled. If the calibration run is already over, click on `continuous mode' to get to `single mode'. While the calibration is ongoing, choose a different update time. The resulting histogram will be updated every n minutes. After you made your selections, click on the `Start!' button.

In the Histoscope selection window you get the following choices:

Select what you want to look at: `Pedestal@/VRBCR-63.....':

5. Run SMT Examine
 
 

6. Power Down Procedure

1. Switch off the sequencer crate in rack M204.
2. Switch off VRB crates 0x61 (M205) ,  0x63 (M206),  0x65 (M207).
3. If nobody else on MCH2 is running any more, power off VRB crates 0x67 (M208), 0x69 (M210), and 0x6b (M211).  Powering them off slows down the L3 VRC on this floor.  If especially CFT is running leave these crates on.
4. Make sure that also the empty top crates in these racks are powered off.
5. Switch off the scope in rack M204 and the 2 movable power supllies in rack M206.

General Information

The SMT read out is situated in MCH2. Rack M201 contains the sequencer crate: from left to right Sequencer Controller (SEQC), 3 Sequencer (SEQ), 3 Emulators.
 

We can use 6 VRB crates, named after their Geographic Sectors GS:0x61, 0x63, 0x65, 0x67, 0x69, and 0x6B. The Geographic Sector is marked above the crate and at the side. It contains from left to right: the front end processor (Power PC, PPC), VBD, VBD repeater, VRBs, VRBC:

Download failed
 
 

1. The download button turns red.
 
 

Go to the main window and hit the `details'  button of the crate where the download failed. The following window should pop up:

Color Codes:

grey: condition unknown
yellow: disabled
green: download OK
sea green: download OK, simulated data selected
red: ERROR status
• HDI download failed:

• Download the emulators again (SVXE-3001 for crate 0x63, SVXE-3002 for crate 0x69).
• Repeat the download.
• Ensure that the HDI and the emulator channel have the same number of chips configured. (For experts only.  Right click on the appropriate item.)
• Does the sequencer show the correct number (71 or 7C) on the front panel? If not most likely a cable connection is not right. Check the 50 conductors on the front panel of the emulators and the back plane of the sequencers.

• SEQ download failed:

1. check that the SEQ crate is switched on (MCH2,  rack M204, lower crate)

1. When the VRB crate is powered up the VBD tries to read the crate id from the VRBC. As the VRBC is not up at that time, the VBD shows a bus error. At the end of the boot up procedure the PPC checks all the VME addresses in its EPICS database. If the VBD is in bus error during this procedure the corresponding VME address is disabled. The symptom is that the event length read from the VBD is 0. This can be checked by selecting the `read evt len' of the VBD button of the detailed view. This  behaviour can be avoided following the proper power up sequence. To solve the problem reboot the frontend (push the RST button of e.g. D0OLSMT03). Make sure that the VBD is not in bus error during boot up (press the reset button on the VBD (the only button on that module) if it initially is in bus error).
2. Does the sequencer show the correct number (71 or 7C) on the front panel? If not most likely a cable connection is not right. Check the 50 conductors on the front panel of the emulators and the back plane of the sequencers.
3. Make sure that only the VRB that is read out is plugged into the VRB crate. Remove additional VRBs that are not used.

Make sure that the front end processors are switched on:

• The crate that is downloaded must be switched on. Check CPU lights on the VRBs and power light on the  VBD and VRBC. Probably reset the front end.
• The sequencer crate (SEQC, SEQ, Emulators) is connected to d0olctl39 on MCH3, rack M305 (behind the door). Make sure the PPC is on and correctly loaded (reset if in doubt).

No events coming to L3

1. Issue a `SCL init' from Coormon
2. Check the Front End Busy status on the DAQ Monitor display (start_daq_monitor_display, choose L1, Geo Sector). Check whether a GS assiciated to an SMT crate sends (too many) FEBusy. If not, bug someone else. In the unlikely case it is SMT:
1. Redownload and make sure that cal inject shows the correct pattern. Corrupted data (missing 0xc0c0 end marker) can cause the problem.
2. Was the trigger configured correctly? Free and reload the trigger configuration from the taker window.
3. Sometimes reinitializing the L1 Trigger Frameword (L1TFW)  helps (quite rare).
4. Last instance: remove the feedback cable from the VRBC (blue 10? conductor)
3. If there are no events coming to the VBD (ETG shows incomplete events for SMT crate 0x69,  the VRBC is getting no triggers: the 2 blue lights on the VRBC front panel are not lid), initialize the VRBC. Click on the `details' button of the main SMT GUI window for the right crate and left click on the VRBC (top row).  Click on the `init' field.
4. If the VRBC is getting triggers (both blue lights are flashing on the VRBC front panel), but the event number on the VBD front panel is not increasing:
1. Redownload
2. Power cycle the VRB crate
3. Remove additional VRBs that are not used in the readout (download again)
5. The VBD shows that it receives events, the event number is increasing: This is almost cerainly a L3 problem. Look into trouble shooting there (reset from WWW, reset button, reb....)

This is usually due to a problem on the front end.  To get the error message log on to the correct frontend (telnet d0olsmt07, login: ioc, password:                 ).
Abort the ongoing run and try again.  You will get some information for the new run from the frontend.

1. `Permission denied' when trying to read the configuration file: check the file /online/ioc/ppc/mv2304/d0olsmt07/run.conf   If the permissions are set correctly, reboot the front end.
2. According to the front end the run has finished normally, but the calibration manager shows `Run in Progress': This is usually a problem within the calibration manager or the SDAQ. Check the corresponding  directories in /online/log
3. Make sure the SDAQ configuration is set correctly: choose `global parameter' from the main window and select SDAQ Parameter. Only the buttons `Calibration' and `Itc' should be checked. De-select additional buttons and download again.