Why ?
- Modules are rare and precious
- Modules are finicky and fragile
- Modules usually aren't finished and working until
the last possible moment
=> Try to remove surprises and reduce "tuning" at beamtest
=> Keep guidelines minimal and unrestrictive as possible
=> Useful commonality with lab test systems
- Module technology and designs are now converging, so it makes sense to work towards beamtest standards.
Module Boxes
- H8 Environment Chamber ("Uppsala Box")
- Until the TSP eventuates, this environment chamber defines the conveniently available module support infrastructure.
- There is little room on our granite table for non-conforming boxes (our telescopes now occupy the overhanging space)
- It provides good cooling, cold dry air, mechanical stability, well-defined rotations, darkness
- ...but has a MAXIMUM of 10 MODULES
- Many different but compatible test boxes were used in 1998 ranging
from the QMW liquid cooled box to ad-hoc improvisations
- I suggest these minimal box guidelines:
- 25.0mm thick in beam direction (with cover plates removed)
- Cooling connections (if used) at TOP
- Electrical connections at one side (or top)
- Low-material beam window as per drawing defining active detector area
- In general, there is room ABOVE and to ONE SIDE of the module for paraphenalia, with the bottom and other side defining the position of the beam relative to the detector.
Readout and Cables
- Our traditional readout using the DSP with BC96 and SC97 remains
supported, with installed cables and RD13 software,
BUT users should bring their own DSP and BC96 - A new higher-density and faster readout using Mustard, Slog and Prague LV supplies is now available, with kit dedicated to H8.
- Older support cards using 5V repeater chips need to be exchanged or modified for use in this system - please contact Gareth
- A completely new barrel non-diagnostic (ABCD) support card design is also available allowing direct connection to Prague LV (DB25 connector) with a small signal connector to Mustard and Slog (DB15) - please contact Gareth for further information
Module Information from Lab tests
- We should aim for STANDARD SCANS, automated as possible, using
generic scan configuration files. This requires for each module:
- Nominal CALIBRATION (for standard threshold scans)
- Nominal FULL DEPLETION BIAS and HV LIMITS
- Bad channel lists
- We should aim to have for each module a default configuration file with a format common to the systemtest as defined by the SCTDAQ project
- Each module should be given a unique name to assist in book-keeping
... eg, mel6, pg1, cg3 ...
Advance warning
- Our system conveniently reads out 6 modules at present, though more can be accommodated given warning.
- The environment chamber has room for 10 modules at most.
- We also need some scheduled DAQ development time
- => Please let me know module plans in advance, even if not definite
- The SCT lab in building 186 at CERN is equiped with various readout test systems, including the systemtest kit: subject to coordination, modules can be checked out here in the several days prior to installation at H8, or of there are problems.
Module Requests
- The SCT operations group (systemtest, beamtest etc.) would like
a resource of REFERENCE MODULES
- Setting up (and studying) multi-module readout, control and power
- Reference planes at nominal efficiency during high-precision runs
- Multi-plane tracking studies, including high rate (=> No telescope)
- We would therefore appreciate knowing of modules that basically
behave and which are not required for other purposes which could
be made available on request
- Barrel planes (SS or DS) preferred for tracking