Mobile DAQ Testbench Mobi DAQ

1
Mobile DAQ TestbenchMobi DAQ
Matteo Volpi
2
Introduction
Slide 1
MobiDAQ is currently the DAQ system being used to
read the front end electronics and run
diagnostics tools to check the functionality and
stability of the superdrawers inside the module.
The Read Out Driver (ROD) is the intermediate
link of the chain between the front-end
electronics and the general data acquisition
system of the ATLAS detector (TDAQ) The ROD
system will be used in parallel with MobiDAQ and
will become the primary DAQ system as soon as
full redundancy is verified.

• Mobile DAQ test bench for commissioning of
  Tilecal in the pit
• Test up to 8 drawers simultaneously
• 2 main functionalities
• Test package using DVS (Diagnostics and
  Verification System)
• Data taking using TDAQ
• Weekly status report in Commissioning Meetings
• Dedicated homepage link on commissioning page
  (http//atlas.web.cern.ch/Atlas/SUB_DETECTORS/TILE
  /Commissioning/mobidaq/index.htm)

3
Hardware Overview
Slide 2

• Hardware
• 5 VP110 (CCT)
• 8 SSP ODIN cards
• 1 TTCvi
• 1 TTCex
• 1 Readout Buffer
• 4 CAEN ADC
• 1 116 optical splitter
• 1 moveable VME rack (old version, now is in
  USA15)
• Many cables

4
Setup in pit
Slide 4
Finally cables (TTC, G-Link, CAN, Trigger, HV,)
Mobi DAQ
Tilecal racks
FLPS
USA15
UX15
5
Commissioning Procedure
Slide 5
Turn on FLVPS ADC-CANbus communication test
(DVS) ADC functionality test (DVS) TTC
communication test (DVS) Triggers test (DVS)
Pedestals 1KHz (DVS) Pedestals at 100KHz (BCID
error) (DVS) Integrator linearity test (DVS)
Integrator pedestal run (DVS) CIS low gain
(DVS) CIS high gain (DVS)
Turn on HV Integrator pedestals (light leak
test) (DVS) LED (DVS)
Pedestal run (TDAQ bytestream) HV On Off CIS
mono run (TDAQ bytestream) HV On Off CIS scan
run (TDAQ bytestream) HV On Off LED run (TDAQ
bytestream) HV On
6
DVS
Slide 6
Diagnostics and Verification System (DVS) is
used to verify functionality of any TDAQ system
or a single component and to diagnose found
problems. DVS can examine any component of the
system (hardware or software) at different
levels of detail in order to determine as
accurately as possible the functional state of
components or the entire system.
7
TDAQ
Slide 7
The TDAQ is the data acquisition system of the
ATLAS detector .
The left part of the TDAQ gui (yellowish)
contains the run control. The right part
contains configuration and monitoring
applications. Important in the Commissioning
phase hopefully not in ATLAS is the Segment
Resource application which allows for
enabling/disabling readout segments. A tipe of
run is configured with the Run Parameter
application
8
Run types, diagnostics
Slide 8

• BCID Bunch Crossing ID Should be the same for
  each event on each digitizer board. Error
  indicates malfunction of digitizer board.
• Noise check that no channel, group of channels
  is too noisy
• Pulse shapes/stuck bits problem with signal
  digitization

• Team 5 is in charge of analyzing the data,
  comparing with Team 4, and reporting back
• to Team 2 (MobiDick) when it has found problems
  with the hardware

9
LED Dead channel test
Slide 9
Verifies the functionality of the PMTs after HV
is turned ON

• Dont expect response to be constant over
  channels
• -different fibers
• -different LEDs for even odd PMT.
• Low signal because of damage HVOPTOCARDS,

TDAQ runs
10
Pedestal runs
Slide 10
For the DVS runs Pedestals 1KHz/100KHz Check
the pedestals and their RMS for each PMT channel
Produces .ps file with pedestal RMS perchannel.
DVS RUN for LBC47
TDAQ RUN for LBC47
11
Cis
Verifies the charge injection procedure
Produces .ps files with sampled signals
Slide 11
Example of damaged digitizer by the FLVPS!!
12
HV Control Program
Slide 12
The level of the voltage can be set and checked
by the HV control system. This system also
measures the temperature in different parts of
the drawer.
A fast interactive software that operates the HV
control system is the hvlibtest A command
menu is shown. The input of 2 starts a list of
all accesible channels, increasing channel
numbers corresponding to increasing module
numbers. Upon input of 3 the channel is reset,
input 6 starts the temperature readout etc.
13
My experience
Slide 13
The commissioning was stopped because the Finger
Low Voltage Supplies damaged 6 modules. After
the module had been repaired by MobiDick (team 2)
we checked again the functionality with the
external Linear Low Voltage Power Supply.
We have run modules of Sector 13 with the HV on
-Sector 13 C Side. LBC46 and LBC49 have been
tested with HV On and Off (without cooling) We
have checked LED system We have checked pedestal
and CIS for digital and integrator read out. We
have taken TDAQ runs (LED,MonoCIS, CISScan,
Pedestal also with HV on) No problems
detected. -Sector 13 A Side LBA46, LBA49 and
LBA51 have been tested with HV On and Off
(without cooling) We have checked LED system.
We have checked pedestal and CIS for digital and
integrator read out. We have taken TDAQ runs
(LED,MonoCIS, CISScan, Pedestal also with HV
on) No problem detected All the modules reaper
(without LBA45) are tested and we dont see any
problems.
14
Conclusion
Slide 14
After two months at CERN I have learned a lot.
Many thanks to all the staff and in particular
Ulla, she spent a lot of time to teach me about
Mobidaq. Now I know -The setup and the test of
the optical fibers. -The DVS test and TDAQ
system, in addition I know the database of data
acquisition (is the same of final ATLAS ) -The
temporary Cooling system. -The laser (LED)
system. -The trigger system (from Mobidaq).
-The HV and LVPS system. 1-Firsty I was in
charge of optical fibers commissioning, whe I had
defined the commissioning procedure. 2-For second
month I was mobiDAQ run coordinator My
experience is very positive, because we check
many final components of TileCal.