Test beam preparations Florian Lütticke, Mikhail Lemarenko, Carlos Marinas University of Bonn (Prof. Norbert Wermes) DEPFET workshop Ringberg (June 12-15, 2013, Ringberg)

Goal: Test beam in May at DESY System Integration test Primary goal: –Complete data flow: DEPFET -> DCD -> DHP -> DHH -> ONSEN -> PC –Slow Control over DHH –Task force: Gießen, TUM, Bonn Backup plan: –Zero suppressed readout: DEPFET -> DCD -> DHP -> DHHe(mulator) -> PC –Slow control over DHHe –Lab test system PC means: –Producer -> Bonn-EVB -> Bonn-EUDAQ-Producer -> EUDAQ-EVB –Producer -> Bonn-EVB -> Online Monitor –Producer -> Bonn-EVB -> Bonn-EUDAQ-Producer -> EUDAQ-EVB -> EUDAQ-Monitor 2

Tasks: get that system working! Develop Hardware platform and get the DHP working Testing Develop Software necessary Testing. Update existing DAQ Software Testing.. Correct mapping from matrix to DHP Testing… Optimize System components, including the DEPFET and DCD Implement additional features (for testing) Testing…. 3

DHHe Control, MATLAB scripts & DHHe Development of Config_GUI software to configure DCD and DHP over JTAG, configure DHHe, upload Pedestals, mask Pixels etc. Development of MATLAB scripts to generate test frames and calculate pedestals Development of fileReader class and MATLAB plugin for “easy” access to DEPFET data files Development of automated routines for testing the DHP –Using Softcore inside DHHe –Fast upload of pedestals –Fast scan of all DCD channels Implemented and tested trigger engine for communication with EUDAQ TLU –Variable Trigger length, settable delays 4

DHP Functionality tests & Optimizations Functionality tests –High speed link –Communication with different clock speeds –Data processing (transmission losses with pre-programmed test frames) –Configuration of DCD via JTAG Switcher output sequences Optimized timings for Signals between DHP and DCD, same for DHHe to DHP Optimized timings to trigger the Systems with the TLU –Triggered laser and readout at the same time –Optimized timings to get all laser pulses 5 Data loss, % Occupancy, %

Development of a new generic producer plugin for our DAQ software –Multithreaded approach –Control thread and connection to/from the DAQ are handled in generic way. –Only data receiving thread needs to be rewritten for different devices Development of DHHe producer plugin Development of DHHe random generator plugin for testing the data flow ONSEN producer and ONSEN generator (Gießen) Implemented and tested DHHe and ONSEN data handling into the DAQ Software and into EUDAQ DHHe Producer plugin and our DAQ are able to write about 100k frames/sec to disc, if frames are small (1-5 pix firing) And much more, including incredible many bug fixes Development of DAQ Software 6

Development of Online Monitor Implemented DHHe and ONSEN data interpreter into our OnlineMonitor Implemented DHHe and ONSEN data interpreter into EUDAQ together with Benjamin 7

Mapping (I) – DCD-DHP Synchronization DHP Coordinates received Mapping DHP-> DCD (synchronize Data!) Mapping DCD-> BondPads BondPads->MatrixPads MatrixPads->Drains->Pixel location Delay Setting Row2_sync_DCD_Delay Steers point where DHP expects first byte from DCD Byte D has to be at the beginning 8 Points to direction of matrix, is located at the switcher side Switcher DEPFET DCD/DHP Straight digital data path -> no Mapping, only synchronization

Mapping (II) – DCDB Adapter Fanout Inner MappingOuter Mapping 9

Mapping (III) – Mapping at wirebonds A2 0 A2 16 A3 0 A3 16 A2 1 A2 17 A3 1 A3 17 A2 3 A2 19 A3 3 A3 19 A2 6 A2 22 A3 6 A3 22 A2 7 A2 23 A3 7 A3 23 A2 15 A2 13 A2 11 A2 9 A2 8 A2 10 A2 12 A2 14 A2 31 A2 29 A2 27 A2 25 A2 24 A2 26 A2 28 A2 30 P0 0 P2 0 P1 0 P3 0 P0 1 P2 1 P1 1 P3 1 P0 30 P2 30 P1 30 P3 30 P0 31 P2 31 P1 31 P3 31 A5 15 A5 13 A5 11 A5 9 A5 8 A5 10 A5 12 A5 14 A5 31 A5 29 A5 27 A5 25 A5 24 A5 26 A5 28 A5 30 A4 0 A4 16 A5 0 A5 16 A4 1 A4 17 A5 1 A5 17 A4 6 A4 22 A5 6 A5 22 A4 7 A4 23 A5 7 A5 23 A4 24 A3 15 Wirebonds to the DEPFET Matrix Lines to DCD 10

Mapping (IV) – Drain lines to Pixels Wirebond adaptor 11

Mapping (V) – Results 12 DHPDCDBondPadMatrix ColRowTotalBlCh.RowColDrainColRow DHPDCDBondPadMatrix ColRowTotalBlCh.RowColDrainColRow DHPDCDBondPadMatrix ColRowTotalBlCh.RowColDrainColRow DHPDCDBondPadMatrix ColRowTotalBlCh.RowColDrainColRow You got 30 seconds to remember everything. There will be a test!

Move Laser spot over Matrix. At every position take measurements, which pixel was hit. Plot reconstructed position vs. real laser Position. Mapping (VI) – Test with Laser 13 Laser position vs. row Laser position vs. column

DCD Optimization Bias Voltages + DACs Timing between DHP and DCD Optimal sampling point –Same procedure as every year. 14

Dry test and DHP hands on Session DHP Hands on Session in Bonn –Two weeks before test beam, 2-3 days –Topics: Setup of Bonn DAQ Software & important commands Data Formats & how to read them Powering Hybrid 5 & configuring it Running Hybrid 5 –Participants: Benjamin, Paola, Felix, Tadeas, Marca, Ulf Dry test –One week before test beam, 2-3 days, 2 other dry runs even before that. –Topics: Connection between ONSEN and DHH Connection between ONSEN and readout PC Data flow from ONSEN data generator to Bonn DAQ and to EUDAQ Connection between DHP and DHH Configuring DHP over DHH JTAG. –Participants: Sören, David, Thomas, Björn, Dima, Igor 15

And much more… Mechanics Hybrid Design Cooling Logistics –Planning –Packing –Setup Checked pedestal stability Result: Stable on hour scale Sensor Characterization 16 Cooling block on the back side of the PCB and thermal vias DCDBv2 DHP0.2

Thank you for your attention 17