Pixel Standalone Test Beam: Status and Plans

M. Cobal, University of UdinePixel Week, TB meeting, CERN June 14th,

2004

- Plans for June 2004- Status of the area- Setup mounting

Goals for 2004: test something like ~ 12 non-irradiated and 7 irradiated production modules Need to clarify some not well understood measurements of last year. Need to have “benchmark measurements” to characterize the production modules.

Require ~ 4 weeks of beam (a commitment not much different from last year)

Standalone runs in 2004

Number of features observed in 2003 data showing a consistent disagreement with previous results.

•Not clear why the irradiated I2 turn out to be worst than I1•Not clear why significant fraction of events arriving at early times

Plus several problems spotted…

•In some runs the trigger delay was not properly set..•The beam spot shape made quite difficult to normalize from the H8 to the LHC situation….•The trigger we used for the high intensity run was certainly not the best suited..

This year data taking is extremely important as no further test beam are foreseen before LHC start-up

Apart clarifying the open issues, the production modules to be tested in H8, should pass a number of defined “benchmark” measurements, to be fully characterized:

Tests of functionality: inefficient or noisy pixels, noise, thresholds.

Operative tests: efficiency, timewalk, resolution, test of functionality to recover late hits,

depletion voltage measure of efficiency after irradiation in realistic conditions of ToT

and incident angle.

SPS schedule

I period: 26 June- 2 JulyII period: 12-26 AugustIII period: 14-20 October

We moved already to NA45.The barrack has been completely cleaned up.

The DAQ PCs have been already transported there.All the material who was around in H8 has been brought there

On 9th June the rails (already in the zone) have been fixed and the pixel table and box have been moved as well. People from Marseille will take care of the alignment

Once installed, we can stay in NA45 for all the period (until October).

This time all the space (3 rooms) is available for us.

Status of the area

Concerning the hardware,  and assuming we want to have 4 modules under test plus the pixel telescope, here is what is needed: - BAT telescope- Pixel telescope (single chip boards, MCC mother board, trigger diode, 2 Dual Channel power supplies) ->Genova- 1 regulator board (working for up to 6 modules) -> Milano- Cables from regulator board to PP0 (1 per module)-> Milano- 4 type0 small cables -> Bonn- 5TPCC, 5TPLL + corresponding cables -> LBL- 4 Power supplies Dual Channel  (AGILENT) for the 4 modules - 1 power supply 5Vx10 A (for the TPCCs). - ISEG module for the high voltage - For the DCS I assume Wuppertal will provide all is needed, and Udine is going to furnish the heat-exchanger- Single board computer-> Genova

Hardware needed (showed at the last PDSG)

Material available in H8

VME material ============ 1 TDC 1 CORBO 1 VME spy 1 BAT control box (probably old: A2015)

NIM material ============ 1 coincidence (4 channels) 4 FAN-OUT (3 with 4x4 channels, 1 with 8 channels) 2 Double Time Units 3 Discrimanators (1 with 8 channels, 2 with 4 channels) 1 FAN-IN (with 16 channels in and 2 channels out) 1 SIMULATION SYNCHRO (random trigger generator) 1 TTL Timing Repeater

Material available in H8 (2nd)

Others ====== 3 Motor Drivers SI3450 1 Gossen power supply Konstanter (2 channels 20V-1A, 1 channel 7V-5A) 2 Power supplies (2 channels 20V-1A, 1 channel 8V-5A) 1 Power supply (2 channels 20V-1A, 1 channel 7V-5A) with sense in the rear panel

Material available in the pixel lab

NIM material: ========= 2 Octal Discriminator 1 HV Power Supply 1 Counter 1 Time Unit

Others ======= 1 Keitley (HV Power supply GPIB) 1 Power Supply 1 ch. 30V/4A 1 Oscilloscope

Trigger

People from Marseille will start the installation during the pixel week: the trigger has to be completely rebuilt and they will provide a drawing of the whole scheme.

We requested a high intensity run, which means ~ 108

particles/spill. From 2003 data we learned that the intensity we can obtain is high enough not to focuss the beam up to 2mm size (intensity in the spot was by far higher than the one in the B-layer)

- We were running with the pixel telescope, triggering with the telescope diode and the 1st scintillator. - There were saturation problems with the scintillators

The plan is to try to put the discriminator in the test beam area ( with or without additional amplifiers).

DAQ

All DAQ and monitoring PCs have been reinstalled No particular problems, apart from formats in the DAQ (IS) database which have been changed (this requires a couple of day of work)

DCS

Jojo and Tobias are coming to CERN for the pixel week and will prepare the DCS installation. Jojo is going to stay till June 23, while Tobias will be available till the end of the testbeam period

Pixel telescope

Works will start during the pixel week

BAT telescope

Bonn people arrived to CERN on the 9th of June. Four BAT-modules are installed, cabled, and powered (they chose four of five perfect modules, one is as spare in the control room).

After installation, all four modules have been tested stand- alone with their PCI-based system and they all seem alive: pedestal and noise are OK (apart from one strip on one module that needs to be masked), the electronics tests all work fine.

Everything has been left powered, so ready for operation.

Read-out and trigger cabling was connected and pulled into the control room.

Bat telescope

The trigger cabling is as agreed with Paolo but obviously untested.

The BAT-part of the VME system was still in place; it has to be set up with a SBC and the general trigger logic. So the final testing with triggering and the creation of config/mask files on the SBC will be done by Markus starting next Tuesday.

These means they won't need further access to the beam area (unless new problems are found when testing with the SBC), except for taking the lids off the BAT module sensor area. Those were left on to keep the modules protected during further installation work.

Changes since last test beam:• Use “Dynalene HC-50” coolant: good to about -50°C• Coolant flows to the four pixel modules in parallel• Valve for each module, so that flow rate can be individually adjusted• New heat exchanger [uses return flow of coolant to cool down dry air]

Pixel test beam box

Chiller Manifold

Heat exchangerDry air / N2

coolant

Gas/dry N2

(Aldo Saavedra, Sven Vahsen, Tom Weber)

Every module is connected in parallel to the cooling. Every inlet to the module has a valve to adjust the flow for each individual plate/module. The cooling liquid can go down to -50C and there is a heatexchanger for the dry nitrogen.

Cooling system

Cooling system

A quick lab test has been done, where all four cooling plates have been connected, and the manifold's valves have been opened completely for all four modules.

The heat exchanger has been connected to the return flow ofthe chiller, and a chiller has been used that should have a flow rate similar to the one at CERN. When the module has been powered (IDD=1.2A, IDDA=1.0A), the NTC temperature went up 3.3 degrees.

CoolantFlow

Manifold distributes coolant to each module

Cooling plate with module installed. Use quick-connectors for coolant hoses to avoid spills inside box when disconnecting hoses.

Heat Exchanger

Coolantout

Coolant in

Air in

Air out

Quick & dirty test in the lab: ΔT (module power_on – power_off) = ~3°C

Cooling system

The flow conditions in this little test should be pretty realistic

The important differences with respect to the test beam will be the heat exchange with the surroundings, and the viscosity of the coolant at low temperatures.

They are going to bring a lot of insulation to deal with the former, and the new coolant should help with the latter. Tom is going to send everything that's in the pictures, plus spare parts and a lot of insulation via federal express on Monday. So the package should arrive during next week.

The start of the installation is previewed on Monday the 21st.

It is necessary to improve the on-line monitoring and to speed up the offline one, to have a prompt feed-back in case things are going wrong.

Indications from expert on how to improve the online monitoring are expected: from the previous experiences some additional plots/ distributions which should be checked immediately, can be identified. And shifters could be given some "good" examples of how they should look like..

An electronic logbook will be available to be tested (see talkof Magdalena). There will be strict rules for shifters on how to fill the logbook (electronic or paper one)!!

The goal  is to arrive as close as possible to some kind of "a regime" situation

Data and data quality control

1) Modules which are supposed to go under test, should arrive here already mounted on the proper metallic support (Aldo should have sent a drawings to all the relevant parts). In this way, mounting or dismounting a module would be an easyoperation of 2 minutes

2) Modules should be protected by their plastic cover not to be damaged during manipulation. They should just have the two needed connectors and not additional cables, scotch tape etc..

3) Modules should arrive already calibrated and the files should be made available in time.

4) People who want to test a module should try to have here a responsible for the module to work properly (or ask explicitely to somebody here)

Reminder: rules settled in June 2003!!