A Trigger/Timing Logic Unit (TLU) for AIDA-Innova
Abstract
A new Trigger/Timing Logic Unit has been designed as part of the AIDAinnova project. It digitizes analogue pulses from multiple particle detectors in a test beamline, forms a trigger based on the input signals, records the time of incoming signals and the outgoing trigger and interfaces with devices under test (DUTs) in the beamline. The new TLU is an advance on previous TLUs developed for the EUDET, AIDA and AIDA-2020 projects by providing more input channels, more DUT interfaces and more accurate timestamping.
Full text
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 101004761. Advancement and Innovation for Detectors at Accelerators A Trigger/Timing Logic Unit (TLU) for AIDA-Innova David Cussans BTTB12, April 2024
Outline ⚫What is a TLU? ⚫(Why do I need one?) ⚫What exists now ⚫(What are all those blue boxes?) ⚫Why it needs to be improved ⚫(Why do I need a new blue box) ⚫Implementation ⚫(Front end , back end).
A Digression ⚫Without Particles …. ⚫Particle Physics is Philosophy, not Physics By user:shakko - Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=5535206 Greek Philosopher Democritus c. 460-370 BCE The universe is made of particles and the void
A Digression ⚫Developing detectors is at the heart of Particle Physics. ⚫“It was as if, suddenly, we had broken into a walled orchard, where protected trees had flourished and all kinds of exotic fruits had ripened in great profusion.” ⚫Cecil Powell, 1950 Nobel Prize for “Emulsion Technique” of particle detection. e
Back to the TLU ⚫… Returning to the AIDA-Innova TLU ⚫Aiming to make Beam Tests Better.
Why a TLU? ⚫May have entirely selfcontained system. ⚫In which case all you need is the beam. ⚫But often want to use existing beamline infrastructure.
Why a TLU? ⚫May want a signal to trigger read-out of detector ⚫In which case you need a beam trigger ⚫Can be helpful to have preinstalled scintillators etc. ⚫And trigger logic (AND, OR, VETO, etc.)
Why a TLU? ⚫May want to know where each particle hit your detector ⚫In which case you need a beam telescope ⚫Need a way of matching tracks in telescope with hits in your detector ⚫→ Hardware correlation through TLU
Why a TLU? ⚫May want particle ID ⚫In which case you need beam instrumentation (e.g. Cherenkov detector) ⚫Want to tag events with PID information (e.g. p/pi/K from threshold Cherenkov) ⚫→ Hardware correlation through TLU
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. AIDA-2020 TLU Asynchronous Interface ⚫Asynchronous “EUDET mode” ⚫No common clock between TLU and DUT. ⚫Trigger/Busy handshake ⚫(Trigger is only released when DUT acknowledges)
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. AIDA-2020 TLU Asynchronous Interface ⚫Asynchronous “EUDET mode” ⚫No common clock between TLU and DUT. ⚫Trigger/Busy handshake (configurable) ⚫DUT can clock out trigger number from TLU ⚫Output on trigger line ⚫Provides event-by-event cross-check
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. Trigger Logic ⚫Inputs clocked at 160MHz (nominal) ⚫Input signals can be delayed and/or stretched in units of 1/160MHz ⚫Signals from the 6 inputs fed into a look-up table ⚫Trigger output synchronized to clock fed to DUT (40MHz nominal) ⚫State of all inputs recorded at point that trigger “fires” −Can be used to tag events – e.g. Cherenkov information.
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. Documentation ⚫https://doi.org/10.1088/1748-0221/14/09/p09019 “The AIDA-2020 TLU: a flexible trigger logic unit for test beam facilities” , JINST ⚫Open Hardware project “AIDA-2020 TLU” −https://ohwr.org/project/fmc-mtlu −Hardware design files https://ohwr.org/project/fmc-mtlu-hw/ −Firmware source code https://ohwr.org/project/fmc-mtlu-fw/ ⚫User manual https://ohwr.org/project/fmcmtlu/blob/master/Documentation/Main_TLU.pdf
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. Firmware ⚫Control and readout of time-stamps with UDP/IP 1 Gbit/s Ethernet −IPBus: https://ipbus.web.cern.ch/ ⚫Ipbb build system −Scriptable build. Working on CI ⚫Open Source −https://ohwr.org/project/fmc-mtlu-fw/
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. Software ⚫All versions of TLU integrated with EUDAQ DAQ software. −Run control ⚫Configuration ⚫Monitoring −Readout of trigger timestamps −https://eudaq.github.io/
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654168. Existing - AIDA-2020 ⚫Current production version ⚫6 trigger inputs ⚫4 DUT connections −LVDS on HDMI ⚫But direction of each line can be swapped in hardware to allow different firmware mapping ⚫Low jitter clock ⚫Hardware permits optical distribution of clock/trigger ⚫In small desktop case or rackmount case
Why a New TLU? ⚫Increasing need for more precise timing ⚫(AIDA-2020 TLU has ~ 1ns time-stamping accuracy) ⚫User requests for more trigger inputs ⚫(Number of DUT interfaces can be increased in common clock mode using external fanout – up to 30 DUTs) ⚫A “PicoSecond TLU” being developed as part of the AIDAInnova programme.
Picosecond TLU ⚫Timing specification: −Clock jitter < 10ps RMS −Timing-stamping of input signals O(10ps) RMS ⚫Backwards compatible with AIDA-2020 TLU −Same signals on DUT connections ⚫trigger/busy/DUT-clk in EUDET-mode ⚫Global-clk, trigger, busy, shutter, T0 in common-clock mode AIDA-2020 TLU connected to beam telescope
Picosecond TLU - I/O ⚫Trigger inputs −Probably 8 ⚫(c.f. 6 for AIDA-2020 TLU) −ADC for time-walk correction ⚫(c.f. threshold discriminator in AIDA-2020 TLU) −TDC with O(10ps) bins ⚫Either implemented in FPGA or external PicoTDC (3ps bins) −Aim to contribute less to timing uncertainly than detector.
Trigger Inputs Level Comparator (same as AIDA TLU)
Trigger Inputs Variable Gain
Trigger Inputs Pulse Comparator
Trigger Inputs ADC for Time-Walk Correction
Trigger Inputs Rising Edge Pulse Stretching
Trigger Inputs Falling Edge Pulse Stretching
Trigger Inputs TDC
AIDA-Innova TLU Schedule ⚫Test board for trigger inputs being produced ⚫Ready June ‘24 ⚫Will be tested with MCP-PMT ⚫Prototype of full hardware ~ October ⚫Initial firmware and integration ~ Jan ‘25
Summary ⚫The AIDA(-2020/Innova) TLU provides a common hardware and software interface to beamlines ⚫AIDA-Innova TLU backwards compatible at the hardware signal level with EUDET / AIDA-2020 / AIDA TLU ⚫Data format different – will be “hidden” by EUDAQ ⚫Pico-second detectors need pico-second infrastructure ⚫Aiming for < 100ps timing
Backup