This page describe the procedure of bringing a single HBU to operation. Some very basic component specification is summarized by Mathias Operation and Instruction Manual

here. Further commissioning steps are described as well. 2 manuals have been written in the past: Operation manual written by Oskar in 2013 written for the USB labview control and commissioning procedure written by Eldwan.

Interface modules

The HBU needs 3 modules for the operation: The Power board (POWER), Calibration board (CALIB) and Detector interface (DIF). These 3 modules are inserted in the Central Interface Board (CIB), which has 3 pairs of flexlead connectors, through which it connects to HBU (1 pair connects to each slab)

Mechanics

POWER, CALIB and DIF modules can be replaced by careful pulling of the module out without tilting.

There are 2 different flexleads: signal and power and they are not interchangeable. The flexleads should be both oriented with the printed label towards the CIB, as shown at the picture <!> TODO.

Flexlead installation: connector and flexlead has to be aligned and then pressed. A click might be heard during pressing on each corner of the connector. The most common reason for fail is CIB vs. HBU misalignment. If the flexlead is connected / disconnected too many time, the contacts in the connector might get loose and the flexlead needs to be replaced.

power connection

The power suppies adn typical currents: +6V (0.6 ~ 1.4 A), +12V (0.1 A), High Voltage (Power supply must be set to 3 V above the configured voltage, +90 V max)

DIF test

Boot LED blinks for ~1 s when the power sitches on. The LED indicates a phase where the firmware is downloaded from the flash to FPGA. If the light stays on, something is wrong.

Firmware can be update via Xilinx impact tool. <!> TODO Jiri picture

Easiest test if the DIF is working: Run the USB labview and check, if the "USB Open" indicator and "RESET_PROBE_REGx" indicators go green. The first connection after the first power on is not successful (the "RESET_PROBE_REGx" goes red). The Labview program needs to be stopped by the blue square stop button "Program Exit" and started again.

POWER test

It is a good idea to test the POWER board first before connecting to the HBU. This only applies when the power board is replaced or reinserted.

Voltages generated by the POWER board can be measured on the CIB board on dedicated test points: <!> TODO The power board by default doesn't generate all power. Only the DIF is powered after first power-on. Volages at test points <!> TODO ....... must be 0V

Therefore the DIF communication has to be established and power has to be enabled (as described here) in order to measure generated voltages:

  1. <!> TODO button enables <!> TODO voltages

  2. <!> TODO button enables <!> TODO voltages

  3. <!> TODO button enables <!> TODO voltages

POWER board provide 3 independent high voltages. The selection of which will be used in each ASIC is given by the resistor configuration on the HBU (each ASIC can have different HV). The high voltage is never completely switched of: a pre-bias of ~10V is always present. The high voltage is enabled by Pre_Bias 2 switch confirmed by the enable! set button in the Calibration tab of the labview, as shown at figure <!> TODO.

Slowcontrol files

Slowcontrol files are text files, which contain text decimal representation of the binary configuration of each asic. Each SPIROC needs a separate file. The modification of slowcontrol files is performed via a labview program SC_SP2B.vi.

(click to enlarge) alt slowcontrol tab 1 alt slowcontrol tab 2 alt slowcontrol tab 3

Careful! This programs overwrites the slowcontrol file without warning. It should be always used in a sequence: Set_file -> Read -> Modify -> write. It is not a god idea to change the filename between read and write.

common settings for all modes

DIF ID SPIROC2B_slowcontrol_DIFID.png must be unique among all SPIROCs connected to single DIF! Otherwise data will get mixed up. It is represented in binary form with LSB on left and MSB on right. The DIF ID on the picture would be 1*02 + 1*62 + 1*72 = 1+64+128 = 193

Hold value SPIROC2B_slowcontrol_hold.png defines how long will the trigger circuit wait until the memory cell is stores the data. /!\ 3 fields have to be set together: Trigger, ValidHold and RstColumn.

Switch TDC: When this field is ON, then the TDC memory cells are used for conversion. When OFF, ADC_LowGain is used instead of TDC. This is useful for intercalibration between HG and LG

Auto Gain: When ON: automatically decides which memory cell will be converted (HG or LG).

Autogain threshold: Threshold for the autogain selection. The level needs to be set safely below the non-linear region of HG ADC.

Trig Ext (OR36) enables a forced trigger generated by internal LED calibration system

Trigger threshold defines the minimum signal size, which is needed for the trigger to be generated and signal to be stored. Typical value is around 230.

Lab mode (forced trigger)

The Trig Ext (OR36) should be on and DAC1 : Trigger should be at some high level (>500 is usually sufficient)

Testbeam mode (autotrigger)

The Trig Ext (OR36) should be off, DAC1 : Trigger should be set to some value obtained by the autotrigger threshold scan.

Intercalibration HG/LG

/!\ TODO

USB Labview control

alt usb control tab 1

Communication

3 indicators should green if communication through the USB is established properly: USB Open, USB Init and RESET_PROBE_REGx. The USB Open can fail in following conditions: HBU doesn't have power, USB cable was not plugged properly, previous connection was interrupted and the power is still open or windows driver failed. If the RESET_PROBE_REGx fails for the first time, labview program needs to be restarted. If it keeps failing, the DIF probably 'crashed' and HBU needs a power cycle .

power on/off

There are 3 stages of power control: HBU2, 3.3V and SPIROC.

Power ON sequence: click on ON buttons in following following order HBU2, 3.3V and SPIROC

Power OFF sequence: click on ON buttons in following following order SPIROC, 3.3V and HBU2

load slowcontrol

alt usb control tab 2

Slow control files have to be prepared before and should be place in a dedicated folder. The expected filenames are: {SC_SP2b_ASIC01.txt SC_SP2b_ASIC02.txt SC_SP2b_ASIC03.txt SC_SP2b_ASIC04.txt. The folder path has to be copied into the SlowControl Folder Path. The path should end with "\".

Check if the High voltage is switched off before slowcontrol loading!. The High voltage can be controlled from the calibration tab.

For single HBU should be the configuration left in defaults (as shown at the screenshot). Then press buttons in order:

Each button should be pressed exactly once.

configuration

alt usb control tab 7

Following buttons should be pressed or (sequence order is not important):

Lab mode specific

LAB mode means to do measurements without particles. Just with internal LED system. Following settings are needed for LED measurements

Testbeam mode specific

data taking

alt usb control tab 4 alt usb control tab 5

There are 2 modes, in which the data can be taken. These modes differ in the run parameters. Filenams are given with the full path and without extension. If the filename remains the same, the data is appended to an existing file, not overwritten. Data and Time is added to the filename in the Testbeam mode.

The LAB mode configures just the number of external triggers (No. Ext. Trig) and the distance among them (Distance_Trigger 2).

The Testbeam mode sets 1 dummy trigger only and the distance is set to minimum or to the value of (Distance_Trigger 2) in the LAB tab (depends on the labview version used). The Meas.-Length defines the maximum time, for which the acquisition is allowed. The resulting length is calculated and transfered to the HBU when Def_Meas NOW is pressed. If the duration is longer than 16 ms, Bunch-X will start counting from 0 each 16 ms.

Validation should be switched on in the Testbeam mode only when there is an external lemo signal connected, or when the LED light is recorded in the autotrigger mode. Internally generated LED triggers are validated automatically.

InfoCycle defines how many readout cycles will there be among the temperature readout. The temperature is saved in the text files.

Commissioning

Gain

The gain is defined as a distance between 2 photopeaks in the single pixel spectrum. The gain is an individual property of each channel and each gain mode (high gain and Low gain). We assume, that the gain is same for all memory cells belonging to a single channel (and gain mode). However the pedestal depends not only on the channel and gain mode, but also depends on the memory cells, therefore data from all memory cells can not be simply merged together. We also assume, that the signal in memory cells does not deteriorate too much during the acquisition time.

hold scan

SPIROC waits fixed amount of time from the moment, when a trigger from fast shaper is detected and sampling moment. This time is called hold value. This value needs to be set experimentally. To do so, a set of slow control files needs to be prepared. There is actually a generator in the slowcontrol editor, which creates the set automatically.

There might be a difference between a hold value in autotrigger mode and a hold value in forced trigger mode (LED Lab mode), therefore the data have be taken in appropriate mode.

The default hold value is 011000(binary) = 24.

intercalibration

The ratio between high gain and low gain values need to be properly calibrated, if data from both gain modes need to be combined (operation in autogain mode). The gain can not be usually extracted directly from the low gain mode, because the resulting Single Pixel Spectrum does not see the individual peaks. Therefore we calculate the gain only for the high gain mode.

The SPIROC allow operation in a special mode, where it converts and sends data from both memory cells, from high gain and low gain. This mode can be configured by the slowcontrol Switch TDC option set to off.

This way we record exactly the same events in high gain and low gain memory cells and we can determine the slope from the ADC[high gain] vs. ADC[low gain] plot.

Autotrigger threshold scan

Autotrigger threshold is set for each ASIC individually and is common for all 36 channels. Channel-wise trimming is possible, but it affects the global threshold and never been tested in beamtest. The autotrigger threshold can be measured in 2 modes: in forced External trigger mode and in autotrigger mode. Both modes should be used.

The threshold typically lies between 200 and 240.

Analysis

Described here


CategoryHCAL

AHCALHBU2ElectronicBringupGuide (last edited 2016-12-20 10:35:59 by EldwanBrianne)