desy test beam (daq integration, measurement plans, analysis) mathieu benoit
TRANSCRIPT
DESY test beam (DAQ integration, measurement plans, analysis)
Mathieu Benoit
Outline
• DAQ Integration– M-i-M TLU Interface testing– Timepix Producer Status
• TestBeam Measurement plans
M-i-M TLU• Man-in-the-Middle TLU Reader is a interface to the
trigger logic unit used by the EUDET Telescope– Handle the handshake on each trigger with the
telescope system , transmit Event Number and synchronize with Timepix Producer via standard ethernet connection
– Handle the FITPix readout trigering and BUSY– Provide full digital control of Timepix Trigerring
• Control through ethernet using a simple dependence free, open Library
• Compatible with mostly any PMOD equipped FPGA Developpement board – Reusable for CLICPix readout, Timepix3 readout– Low cost (~300 CHF)
• Possibility for other Use – TDC (see next slides)– Stand-Alone trigger interface to fitpix – Synchronisation studies (proposed by DESY) FPGA Board
LVDS Signal for TLU I/O
LEMO, TTL signal for spying TLU Signal and triggering TP
M-I-M TLU
TLU Timepix + FITPix
Microblaze (C code) PHY
Communication to PC
TLU Reader, TDC, etc
Trigger,Reset
Trigger Clock ,BUSY
Trigger
Busy
MIMTLU
MIMTLU to increase track rate (Method 1)
• MIMOSA26 only sensitive for 220 us, but is essentially dead time free• Timepix can readout out for arbitrary time, but long dead time (20-30
ms)
MIMTLU can to scale the trigger rate sent to Timepix to keep shutter open for longer periods ~O(ms). • The producer can then send data for many TLU trigger in one event, every
X event.• Telescope still send data every event• Chunk of X telescope event are merged offline to match Timepix events• Advantage -> Increase trackrate, disadvantage -> We loose online
monitoring Backup solution to increase trigger rate
Modification to telescope to increase track rate (Method 2)
• Mimosa26 actual readout actually read 100s of frame per trigger, throw most of them away and keep only two
• I am looking into modifying the MIMOSA26 Labview Readout to change the number of frame kept per readout– Experts say it should be possible.– To be tested in the next TB period
Preferred to increase trigger rate (until arrival of new TLU)
MIMTLU as TDC
• MIMTLU can handle trigger up to 3.2kHz
• Internal clock in FPGA MIMTLU running at 10 MHz– MIMTLU can be used to
provide coarse time stamping (~500ns over 10s) of trigger within Timepix Shutter
– A CERN Open-Hardware TDC compatible with Spartan6 FPGA claim accuracy down to ~50ps!!
2.5kHz High-Precision Pulser
Absolute Resolution (over 2ms)
Pulse-to-pulse timing (over 2ms)
Measurement plan for June 20131. Alignement Run, Telescope Only (1M Trigger, 1-2h)
2. Alignement Run, Telescope plus Timepix at 0 degree, TOT Mode (3h)
3. TOA Run with Various Shutter length/Clock (~ 1M Trigger, 0.5 day)
4. Optimization of Telescope plane distance (0.5 Day )
5. High Track rate run, method 1 & 2 (1 day)
6. MIMTLU TDC Run/ CLICPix Readout Synchronization tests (0.5,1 day)
7. Power Pulsing Run (If DSG available) ~(1M trigger, 0.5 day)
8. Arrhus Specific measurements (1-2 days)
Lab issues• There has been issue with material
disapearing from the Vertex lab • Euro/swiss adapters• Lemo, scalpels, soldering equipement• USB cables • Soldering Iron was broken and not
fixed • Etc …
• Would it make sense to ask for a wall to be built to control access ? It would also define better the protected zone (RP)
• With CLICPix/Timepix3 developpement coming, it would be useful to have a second setup table for precision measurement (for example with scintillator fingers from DT, IR Lasers)• Melles griot has affordable lab table
with BreadBoard for < 4500CHF