Alexander Krieg (DESY-IT) - HEPiX Spring 2008 - Indico@DESY 8. May 2008 1 Indico@DESY.
DAQ-SALTRO16 activities in Lund & developments in Brussels/DESY
-
Upload
hakeem-ingram -
Category
Documents
-
view
22 -
download
1
description
Transcript of DAQ-SALTRO16 activities in Lund & developments in Brussels/DESY
1
DAQ-SALTRO16 activities in Lund&
developments in Brussels/DESY
Lund UniversityUlf Mjörnmark
2
EUDET/LCTPC setup in september 2010
Low voltage Front End Electronics Kapton cables TPC Magnet
3
Operated reliable when taking data in test beams at DESY:2009: February – March, July, September2010: September, DecemberIn September 2010 the system operated with:7680 channels (60 Front End cards)3 RCUs, 2 DRORCsProblem: broken amplifiers on FEC, caused by discharges in GEM?Next testbeam: june 2011, with test of input protection on amplifiers
ALTRO based Front End Electronics & DAQ
Hardware is based on ALICE TPC readout electronicsStandalone DAQ with ALICE drivers/libraries
4
16 ch ALTRO PCA16 Kapton cable
SALTRO16
PAD plane
Front End CardBackplane New design
MCMMulti Chip Module
Pad plane
LVLV
LV LVCONTROL
5
Multi Chip Module with 2 SALTRO
MCM
LV&ctrl
Bus card (Backplane)
Padplane
RCU
SALTRO16
6
Development in Lund
DAQ-SALTRO16Same as for EUDET/LCTPCWhich has:no common DAQ interfaceno common TLU/DBOX trigger
Modifications needed forNew ”Front End Card”New backplanesMCM instead of FEC
Time scale: h/w & s/w september 2013
7
Control? implement a common server that can communicate with the DAQ process on one side, as the local server do, and with a common control on the other side.Event data transfer? Currently as local storage and sending raw binary data over network.
COMMON DAQ INTERFACE? COMBINED RUNNING?
LUND PART COMMON PART
DAQ CORE
8
Trigger systemDBOX – TLU trigger? to be fully implemented if any combined running(DBOX = local distribution of trigger/busy/reset/clock)Common DAQEUDAQ:?Some work was done to integrate DAQ process with EUDAQ, but lack of time/manpower and problem with ALICE C-code together with EUDAQ C++ code interrupted it.
Interface to common DAQ:Should not need to intregrate common daq code into the standalone daq core, to avoid code ”incompatibility”, e.g.:Control:CommonServer to convert common commands to local commandsData: address/port/format/handshake (library routine?) to send data over networkLocal DAQ:Should be possible to easily swap to local running and setup.
9
Development in Brussel/DESY
Implement DRORC in microTCA:Advanced Mezzanine Card (AMC)connect ed to RCU/MCM/FEC system
Development steps:Learn microTCAMake simple AMC as testNew DRORC
Two streams to/from DRORC:*Setup/Control *Data -> DAQ system: existing or new?
Common DAQ?Time scale of microTCA?