Legnaro Muon Data Acquisition

1. Legnaro Muon Data Acquisition CPT Week 16 April 2002 M. Bellato, M. Gulmini, G. Maron, N. Toniolo, S. Ventura and L. Zangrando INFN – Laboratori Nazionali di Legnaro INFN – Sezione di Padova CERN

2. Aims of the Legnaro muon DAQ system * • Provide system for the Drift Tube (DT) production centers: • Aachen • Legnaro • Madrid • Torino • Provide a system for Bari RPC production center • Provide a system for the CERN DT validation center (at ISR) • Provide a system for test beams of RPC and DT chambers (coupled or standalone) * * * * * Sites already provided with our DAQ systems based on pre-XML XDAQ framework

3. Legnaro Muon DAQ System I Detector Frontend Level 1 Trigger Readout Units JRCS FastEthernet Switch Event Manager Builder Units Computing Services PC based EVM (OS vxWorks, Linux) Builder Unit ORCA BU Requests TTL/NIM Ethernet Lv-1 TrgID Broadcast PIII EVM VME Readout Unit (OS vxWorks, Linux) Lv-1 TTL/NIM P M C P P C VME TDCs TrgID P M C Events Ethernet Software Framework = preXML-XDAQ PC based Builder Unit (OS Linux) OODB, Flat IDE

4. Legnaro Muon DAQ System II Detector Frontend Level 1 Trigger Triggers Vetos, etc. Readout Units RC Electronics FastEthernet Switch (RCN, BCN, BDN) JRCS Event Manager RU Spy RCN Builder Units BDN BCN Computing Services BCN BDN PMC I/O RC Trigger BU Spy RC Spill ON/OFF Triggers Vetos, etc. EVM RCN OUT BCN DB

5. Next Step • Use of fully pipelined electronics • Use of final (or prototype of) electronics boards • TTC synchronized • Update XDAQ version • Integration with the Run Control and Monitor System (RCMS)

6. DAQ Layout for next step DT Chamber 128 Ch 128 Ch 128 Ch 128 Ch Max 128 x 7 (896) ch 128 Ch LVDS data output Serial links ROB – 128 TDC ch Readout Board MiniCrate CCB TRG BSY • TTC link: • CLK • TRG • BCRST • EVRST To Minicrate Control Board CCB Ctrl RS232 VME TTCvi PCI-VME SBS-620 TTCex • ROS – 8 • Readout Server • Collects up to 4 Minicrates • Output to DDU (missing here) • DDU emulation via VME PC EVM - RU TRG BSY PC - BU To storage Fast Ethernet PC – C&M XDAQ Software Framework RCMS Services

7. Configurations Production Centers Next September Test Beam MiniCrate CCB DT Chamber DT Chamber 2 DT Chamber 1 MiniCrate CCB TRG BSY MiniCrate CCB TRG BSY TTCvi TTCex VME TTCvi TTCex VME PC EVM – RU - BU TRG BSY PC EVM - RU PC – C&M TRG BSY PC - BU Fast Ethernet PC – C&M

8. Operational Modes • Event Builder • It is needed when multiple RUs (i.e. with multiple ROSs or with other detectors – like RPC) are used • 1 trigger = 1 EVM interrupt = 1 event readout • Stream mode • Useful when a single RU and BU are used • Data are continuously readout from the output Fifo of the ROS • For instance • a fifo “almost full flag” is used to interrupt the RU CPU • a DMA is started to readout the filled part of the fifo and write it into the RU buffer memory • etc.

9. XDAQ Customization • Event Builder • Spill/Trigger/Interrupt handling/ to XDAQ framework • Electronics CPU/DMA readout • Multiple output data stream • Stream mode • consumer/producer model (no evm) • Run Control • RCMS Integration

10. XDAQ Customization: Event Builder Lv 1 2 3 Readout front end electronics Bsy RUI 6 Use of the new RUM primitives RUM Spill On/off Readout Bsy Lv 1 • Interrupt (Lv 1) syncronization OK • More signals (readout, spill, Lv1 trigger (interrupt) need to invoke the same class. • DMA synchronization. Understood, to be done • Multiple output streams. To be investigated • Stop command wants to flush all the events are in daq memories. Implemented in the RU. BU in progress. Moreover also the event Ids queues (in BM and RM) should be flushed. New flushing algorithm implemented. To be discussed. • Readout based on the new RUM primitives RUO Veto 1 RM Send 5 Cache BM Confirm BU Request 4 Multiple Output Streams

11. Trigger Handling “Interrupt” RM Appl. (Trigger) 1 CPU for EVM and 1 CPU for RU. RCN via Ethernet, Lv1 also in RU Lv 1 Trigger ISR Ethernet RUI Appl. (readout) Trigger EVM Lv 1 Trigger “Interrupt” ISR RUI Appl. Ethernet Readout TCP RUO Appl. BU Send/Cache RU

12. Run Control xdaq adapter command-engine cmd + RS object cmd + xdaq DOM node Security Service UserDB ConfDB Resource Service XML RS Protocol Xdaq protocol UI Info&Mon Service LogDB UI Session Manager Services Connection UI Run Bkkpng Job Ctrl Problem Solver Sub-System Controller RCMS Sub-System (Daq)Resources SOAP message XDAQ Appl

13. XDAQ + RCMS test bed • waiting for minicrate delivery (expected for April, problems found in TTCrx, patches, etc.). Probably a tested pre-production end of May • Then a XDAQ test bed has been set up based on the “old” electronics, no real chambers available Lv-1 P M C Bsy P P C VME RU TDCs TrgID Lv-1 P M C P M C Bsy P P C VME EVM Events TrgID P M C PC - RU FastEth PC - RU PC - BU PC - RCMS

14. Status • Event Builder Mode • Most of the customizations implemented in our running systems have been moved in the new XDAQ framework (Interrupt, DMA, buffer flushing, etc.) and work. • BU customization is just in progress. • problems found with December XDAQ version + customization when trigger rate > 200 Hz. Now moved to March XDAQ • Start up problems with the March release (documentation for the new configuration XML schema is really needed) • Stream mode • Not yet clear if really useful in the production centers. We need to gain experience with the new electronics first. • Run Control Integration • First prototype running with XDAQ (December release) nodes. No yet compliant with the March XDAQ release (configuration XML schema changed) • Session, Partition, Resource handling provided • Basic GUI provided • IMS in progress