EMU Alignment DAQ Endcap Alignment Muon Alignment EDR Feb. 28, 2002 Outline: Components to be read-out or controlled (See D. Eartly’s talk for details of the front end hardware) General layout of FE and DAQ hardware Software Issues: Current Status plans and summary

Devices to be Readout DCOPS sensors: Analog sensors: 36 per layer (6 x 1/2-SLM lines, each with 6 sensors including both on the transfer plate) 6 sensors on each MAB daisy chained and communicate with 2 serial lines daisy chained and communicate with 2 serial lines Analog sensors: 60 ADC channels (for ME2, 3, and 4) > 144 ADC channels for ME1 area (12 more) One Agilent DAU handles 60 ADC channels. Each DAU communicates with 1 serial line Switching lasers (Agilent DAU) : 12 channels (SLM) per layer, 12 (possibly 24) axial ch.

Number of Serial lines 2 (RS-422) 3 (RS-232) 1 (RS-232) 5 3 2 Layer 1 MAB # Serial lines for DCOPS 2 (RS-422) # Serial lines for Agilent DAU 3 (RS-232) 1 (RS-232) Total # of serial lines 5 3 2

General Layout

Characteristics All the components above the serial hub (device specific below) are generic standard plug-ins. Device specific readout system is designed to be modular (equal vertical slices) and easily expandable. This allows developing software, testing and commissioning of the detector much simpler. Use of commercially available hardware (serial hub, Aligent DAU, ethernet hub, router/gateway, etc…) Data path in the low level should be protected from the outside network traffic, however, the DAQ operation system must be easily accessible. Relatively inexpensive.

Serial Hub & Agilent DAU

Software Issues Operating System: Linux Language: c with gnu compiler network protocol: TCPIP DCS interface: DIM socket connection rawdata: input to COCOA for the fast alignment reconstruction of chambers. Rawdata Exchange: Most of the rawdata are totally internal to the EMU system and no need for data exchange between the subsystems. Only a very small amount of MAB DCOPS sensor rawdata for the barrel system are possibly being read out by the EMU DAQ.

Software Issues (Cont.) Input to EMU Chamber Reconstruction (COCOA): Input to the EMU reconstruction program requires some information from the link system (link COCOA output) together with EMU raw data. Output of COCOA: Most of the data needed to be exchanged between the subsystem are not raw data but COCOA output. The output of the alignment reconstruction program must be easily interface to: Trigger alignment input Offline muon track reconstruction (ORCA) (see P. Ace’s Reconstruction Software talk for more details)

Expected Raw Data Size DCOPS sensors (8 words per sensor): 36 sensors per layer (4 layers in each side) 6 sensors on each MAB (36+6)*2*8*2 = 672*2 B Analog sensors: 60 ADC channels (for ME2, 3, and 4) 144 ADC channels (for ME1) (60*3+144)*2*2= 648*2 B approx. 5kB/event one event/min (over estimate) approx. 6 MB/day (very small)

Current Status Basic DAQ design is finished and tested We have, currently, a set of necessary hardware elements to test/develop a modular and expandable DAQ system. Router/Gateway (1) Rocketport Serial Hub (2) Agilent DAU (2) DCOPS readout electronics (multiple number of DSP cards, Interface cards). We have made and successfully tested a simple C program to readout both DCOPS and Agilent DAU. It works under Linux OS using a setup with all the basic readout hardware components listed above. We have been using above setup to test/debug our FE.

Near Future Plans for DAQ Continue to develop the DAQ software to add more functionalities. Modify RS232 to RS422 readout at the serial hub (at a moment, using RS232). We need to look into more on: making sure this DAQ configuration works with the nominal cms operating conditions, such as magnetic field and radiation. Get ready for the 2004 magnet test. (see more on next page) Implement DCS connection.

DAQ Magnet Test Plan Should be able to read out the full EMU alignment system using the hardware and software components for EMU DAQ described above. Some of the ‘nice’ functionalities of DAQ (GUI, DCS connections, Database access, etc.) may not be ready, yet. But that should be ok for this test. The software must be developed enough that during the magnet test we can have fast feed- back from the data taken. This means that the interface between raw data and COCOA, and COCOA software must be well established enough that we can get fast feed-back from COCOA output (results of muon alignment reconstruction).

EMU DAQ Summary We have completed and tested the basic DAQ design with a modular expandable unit successfully. We have been using the setup to test/debug FE. We are in a good shape to carry on developing our readout system.