DAQ Integration

Europe/Zurich

KPiX, TPC and DESY test beam DAQ integration meeting
24 Nov 16

Participants: Marty, Leif, Ulf, David, Ryan, Dieter, Dimitra

The purpose of the meeting was to discuss and agree on a strategy
on how to synchronise the different detectors in order to have combined Si tracker + TPC test beams at DESY.

 

** KPiX
Info: KPiX can accept an external clock.
If KPiX is externally triggered, it can accept 4 events per frame. If KPiX is self-triggered, it can accept 4 events per channel.
KPiX timing procedure: It receives start of frame, then it requires 2ms to fully switch on and to be able to take data, and then it is able to take data for up to 8K cycles.

What will KPiX need?
1. KPiX will need to receive the 20MHz clock from the TLU.
2. KPiX will need a start of run information.
3. KPiX will need to accept a start of frame by the TLU.
Making KPiX accept this information from the TLU will be done by Ryan.

What will KPiX do?
KPiX stores timing information as #frame and #cycle. Cycle timing is defined in 8x50ns intervals (20MHz clock).

 

** TLU

What will the TLU do?
TLU will help synchronise both systems.
1. It will provide a clock (20 MHz) to KPiX,
2. it will send a switch-on signal to KPiX at the start of frame,
3. it will provide trigger stamps (using a scintillator setup. this information will be stored offline), and
4. it will send the trigger to the TPC.
These implementations to the TLU will be done by David.

What does the TLU need?
DESY can provide a signal when the DESYII cycle is at minimum. Dimitra will find out
what type of signal is provided by DESY and will monitor the cycle to determine how long after this signal kpix should switch on.
The TLU then will be programmed accordingly (by David) to send a switch on signal to KPiX (start of frame) after XX intervals of 50ns (20MHz clock).

 

** TPC

What will TPC do?
TPC will accept a trigger signal from the TLU. It will then start taking data and send a busy signal to the TLU. The TLU will not time stamp new triggers until the TPC busy signal is lifte
d.
The TPC will not store the timing information but it will store the actual event. The TLU will store the timing information of the trigger (according to the 20MHz clock).
TPC accepting the TLU signal will be implemented by Ulf.

 


** How will the data be matched offline?
TLU timing for sending a trigger to the TPC is available in terms of 50ns intervals.
TPC timing not available.
TPC events and TLU triggers will be a 1:1 match.
KPiX will probably be on self-trigger mode. KPiX will store timing information as #frame and #cycle. The #frame is in terms of 50ns (in accordance with the TLU 20 MHz clock)
and #cycle time resolution is in 8x50ns.
This timing resolution is fast enough for the DESY test beam.

Schematics to be attached.

 

There are minutes attached to this event. Show them.