90 likes | 170 Views
DAQ-SALTRO16 activities in Lund & developments in Brussels/DESY. Lund University Ulf Mjörnmark. EUDET/LCTPC setup in september 2010. Low voltage. Front End Electronics. Kapton cables. TPC. Magnet. ALTRO based Front End Electronics & DAQ.
E N D
DAQ-SALTRO16 activities in Lund&developments in Brussels/DESY Lund University Ulf Mjörnmark
EUDET/LCTPC setup in september 2010 Low voltage Front End Electronics Kapton cables TPC Magnet
ALTRO based Front End Electronics & DAQ Hardware is based on ALICE TPC readout electronics Standalone DAQ with ALICE drivers/libraries Operated reliable when taking data in test beams at DESY: 2009: February – March, July, September 2010: September, December In September 2010 the system operated with: 7680 channels (60 Front End cards) 3 RCUs, 2 DRORCs Problem: broken amplifiers on FEC, caused by discharges in GEM? Next testbeam: june 2011, with test of input protection on amplifiers
Front End Card Backplane New design LV LV CONTROL LV LV Pad plane SALTRO16 MCM Multi Chip Module 16 ch ALTRO PCA16 Kapton cable PAD plane
Multi Chip Module with 2 SALTRO RCU Bus card (Backplane) LV&ctrl MCM SALTRO16 Padplane
Development in Lund DAQ-SALTRO16 Same as for EUDET/LCTPC Which has: no common DAQ interface no common TLU/DBOX trigger Modifications needed for New ”Front End Card” New backplanes MCM instead of FEC Time scale: h/w & s/w september 2013
COMMON DAQ INTERFACE? COMBINED RUNNING? DAQ CORE LUND PART COMMON PART 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.
Trigger system DBOX – TLU trigger?to be fully implemented if any combined running (DBOX = local distribution of trigger/busy/reset/clock) Common DAQ EUDAQ:?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 commands Data: address/port/format/handshake (library routine?) to send data over network Local DAQ: Should be possible to easily swap to local running and setup.
Development in Brussel/DESY Implement DRORC in microTCA: Advanced Mezzanine Card (AMC) connect ed to RCU/MCM/FEC system Development steps: Learn microTCA Make simple AMC as test New DRORC Two streams to/from DRORC: *Setup/Control *Data -> DAQ system: existing or new? Common DAQ? Time scale of microTCA?