MICE CM25 Nov 2009Jean-Sebastien GraulichSlide 1 Detector DAQ Issues o Achievements Since CM24 o Trigger o Event Building o Online Software o Front End

MICE CM25 Nov 2009 Jean-Sebastien Graulich Slide 1

Detector DAQ IssuesDetector DAQ Issues

o Achievements Since CM24

o Trigger

o Event Building

o Online Software

o Front End Electronics

o CAM-DAQ Interface

o Schedule Milestones

o Summary

Jean-Sebastien Graulich, Geneva


Achievements since Achievements since CM24CM24

DAQ and Controls ReviewDAQ and Controls Review Factor of 5 increase in # of particle Factor of 5 increase in # of particle

triggers per spilltriggers per spill FADC Firmware upgradedFADC Firmware upgraded

Factor of 4 reduction in data size

Trigger DebuggedTrigger Debugged Problem with Event building under Problem with Event building under

controlcontrol

-------------------------------------------------------------------------------- Target DAQ des-integratedTarget DAQ des-integrated

DAQ ReviewDAQ Review

Details presented at VC 121Details presented at VC 121

The DAQ Review is Done ! The DAQ Review is Done ! Very useful comments have been receivedVery useful comments have been received Detector DAQ appears to be in shape and Detector DAQ appears to be in shape and

should allow data taking for Step III and should allow data taking for Step III and beyondbeyond

Unified Controls, Data Flow and Online Unified Controls, Data Flow and Online Database are more recent projects and the Database are more recent projects and the committee has noticed it’s not yet maturecommittee has noticed it’s not yet mature

Need better integration DAQ/Controls More thinking on Online Data Buffer Disk Access

Serious concern about the man power Serious concern about the man power available for Controlsavailable for Controls

MICE VC June 2009 Jean-Sébastien Graulich Slide 3

ReminderReminder

The DAQ Spill Gate has to be checked The DAQ Spill Gate has to be checked before data takingbefore data taking

Documentation available Adjust Width And log !!!


TOF1

Accepted Particle Trigger

GVA1 = Part. Trg Request

Spill Gate

Trigger debuggingTrigger debugging

Trigger signal generation was in “update” Trigger signal generation was in “update” modemode

Went unnoticed at low rate Introduced variable dead time difficult to control Caused saturation

SolvedSolved


Particle Trigger request

Accepted Particle Trigger

Event BuildingEvent Building

Synchronization can be lost because ofSynchronization can be lost because of Unstable electronics in DAQ trigger distribution Unstable behavior of the VME/Pci Interface

The DAQ software release the busy The DAQ software release the busy and enables the DAQ trigger receiver and enables the DAQ trigger receiver channel after readoutchannel after readout

Must go through the VME/Pci Interface It happens that one of the two commands is not

executed properly… Unpredictable Cured only by a power cycle

Has to be monitoredHas to be monitored


DAQ Trigger MonitorDAQ Trigger Monitor


Number of LDC receiving a DAQ Trigger per DAQ event

LDC Number

cou

nts

# o

f D

AQ

Tri

gg

ers

Particle Trigger Particle Trigger monitormonitor


Equipment number

LDC Number

Co

un

ts#

of

Pa

rt T

rig

ger

s

V1724FADCsScalar ch0

TDCs

V1731FADC


Front End ElectronicsFront End Electronics

TOF2TOF2 1 TDC and 5 FADC to be

installed Will require upgrade of the

rack layout in Control Room

EMR: Electron Muon EMR: Electron Muon Ranger (aka SW)Ranger (aka SW)

Prototype of Front End Board exists BUT :

We consider going for another ASIC (Amplifier-Shaper-Discriminator)

Buffer Card will be developed in Geneva

More details in Daniela Lietti’s talk


CAM/DAQ Interface

Double link EPICS should know the DATE status A summary of EPICS data should be inserted

in the online data stream Date Status Monitoring

James Leaver has provided EPICS Server EPICS Client Test Software Status Display

Next step: A small piece of code reading real status from DATE


CAM/DAQ Special Case:

Target DAQ Target data is really both CAM and

DAQ Double flow is implemented Based on a single I/O software -> No issue

with format change

Waiting for the target to be online for final tests

But in the meanwhile the code vanished…

Will require dedicated testing runs


Schedule Schedule MilestonesMilestones

From CM23From CM23 TOF2 Shaper/Splitter ProductionTOF2 Shaper/Splitter Production mid Marchmid March need need

testingtesting DAQ reviewDAQ review June 09June 09 Upgrade of fADC firmwareUpgrade of fADC firmware July 09July 09 CAM data in Online Data StreamCAM data in Online Data Stream June 09 June 09 -> Nov -> Nov

0909 Tracker integrated in DAQ and OLMTracker integrated in DAQ and OLM July 09 July 09 ->-> Jan 10Jan 10 TOF TDC Clock SynchronizationTOF TDC Clock Synchronization July 09 July 09 -> March 10-> March 10

More complicated than first thought. Need a dedicated board Burst Gate Signal in the Trigger SystemBurst Gate Signal in the Trigger SystemNeed aupport hereNeed aupport here

Approval of SW/EMR Front End ElectronicsApproval of SW/EMR Front End Electronics In Proto phaseIn Proto phase Production of SW/EMR Front End ElectronicsProduction of SW/EMR Front End Electronics Sept 2009 Sept 2009 -> Jan -> Jan

1010--------------------------------------------------------------------------

TOF2 DAQ InstallationTOF2 DAQ Installation Dec 09Dec 09

SummarySummary

DAQ review passedDAQ review passed Data rate increased by a factor of Data rate increased by a factor of

Mainly due to FADC upgrade

Trigger system upgraded to handle Trigger system upgraded to handle this ratethis rate

Event building problem understood Event building problem understood and under monitoringand under monitoring

Next stepsNext steps Interface with CAM Integration of TOF2


Documents

MICE CM25 Nov 2009Jean-Sebastien GraulichSlide 1 Detector DAQ Issues o Achievements Since CM24 o Trigger o Event Building o Online Software o Front End