CF 8/June/2003 ATLAS muon week in Gallipoli 1 The 1 st Beam Test of TGC electronics at H8 in May/June ‘03 Chikara Fukunaga on behalf of TGC electronics

CF 8/June/2003 ATLAS muon week in Gallipoli 1

The 1st Beam Test of TGC electronics at H8 in May/June ‘03

Chikara Fukunaga on behalf ofTGC electronics group*

*in particular, with help from H.Kurashig

e, Y.Kataoka, D.Lellouch, L.Levinson, G.Mikenberg, O.S

asaki, S.Tarem, T.Wengler,


TGC electronics at H8

Validate the design of Muon Endcap Trigger Electronics

With electronics and software, which have been used in the present slice test (s) of end-to-end full chain + LV + HV + DCS + othersWith real signals of TGC 7 layers using 3 T8 units

Integrate the system with MuCTPI and CTPTake data from TGCs together with ones from MDTs


Trigger ElectronicsLow pT trigger 3-let or 2-let

Hi-pT Trigger 3-let and 2-let

R- coincidence

Level1 buffer and Derandomizer


Beam Test Setup at H8


Beam Test Setup at H8 (2)

TGC TripletPS pack

Hi-pT crate

2 TGC doublets


Electronics usedChamber (Triplet 32(Strip) x 24(wire), Doublet both 32 chan.)

ASD board (16ch.) x 2 PS pack PS board {8 PP (32 ch.) ASICs, 2 SLB ASICs , 1 DCS } x2

Hi-pT crateHigh pT module (4 Hi-pT ASIC) x1Star Switch (SSW) module x2 HSC

ROD crate(s)Sector Logic for r- coincidenceRODs (ROD and Test-ROD alternatively)TTCvi CCI

CableIndividually shielded TP Category-5 cable from PS board to Hi-pT crate 10m (ATLAS:15m) for LVDSOptical fiber from Hi-pT crate to Sector Logic/ROD in the hut 50m (ATLAS:150m) for G-link.


Achievements1st time for TGC electronics to process chamber data with high energy muon beam.

Chamber were operated with HV 2.9KV and Threshold for Anode -55mV/Cathode Strip 70mV. Normal operation values.Switching noise in HV line could be excluded by low-pass filter.

CO2 :N-pentane = 55:45 Normal operation values.

Although we have found lots of bugs in the system, some of them has not been understood yet, we have generated trigger signals and read out data.ROD could be operated in a combined system of MuCTPI and ROS.


Test summary - TriggerI. Bunch Crossing ID in PP ASI

C worked.II. Low pT and High pT matrices

worked, but there are several problems. Synchronization failure has been observed at both input and output of Hi-pT ASIC. If synchronization failure occurred at Hi-pT input, Doublet and Triplet coincidence could not be achieved.

III. The Sector Logic worked fine for r- coincidence, and integration with MuCTPI OK. But if synchronization failure at Hi-pT output occured, r- coincidence could not be achieved (related to I).

II.

III.I.


Test summary - Readout

I. Trigger Data could not be read out.

II. Hit Data could be stored in a readout buffer but not in the correct buffer. Data could be stored in “the next buffer”.

III. SSW for Sector Logic could not send data to ROD.

IV. Handling of TTC signals could not be done efficiently. A treatment forgotten made system behaviour very strange.

I.

II.

III.

IV.


Preliminary Results - Control

TGC-DCS worked very well during 25 ns at H8 Most functions already functional and tested

ASIC configurationThresholds setting/monitoring, LV monitoringBasic HV controlDAQ and DB communicationsUser Manual

Some functions still to be testedTTCrx configuration via I2CDCS-HSCUnique ID

Charge monitoring proved extremely useful diagnostic


HVCAEN SY1527

Using A1832P board or SASY prototype developed by CAEN for MDT/TGC

Control via OPC server

Using JCOP framework

Integrated in TGC PVSS application


Histogram of analog chamber charge -H8One wire analog channel per chamber is read, integrated on DCS-PS and histogrammed on the ELMB

0

20

40

60

80

100

120

140

1 33 65 97 129 161 193 225 257 289 321 353 385

Threshold 180 mV

Thresholds 50 mV

Threshold 30 mV

CCMC CH0 2900 50

0

200

400

600

800

1000

0 100 200 300 400

Pulse height

CCMC CH1 2900 50

0

200

400

600

800

1000

1 25 49 73 97 121 145 169 193 217 241 265 289 313 337 361 385

Pulse height


Preliminary Results - ROD

TGC-ROD (Israeli) and Test-ROD (Japanese) both worked fine with own prepared software based on ATLAS Online DAQ-1 framework. Data have been sent to ROS via S-link and also to own ROD processor. We have made individual analyses, and got consistent results.

TGC-ROD was operated in a combined run with MuCTPI and ROS.

One DAQ partition (2 RODs, 2ROSs, and Event Builder)

Data from two sources were correctly recorded.


Readout Results Hit-pattern Doublets

TGC ROD data

Test ROD data

Multiplicity

Wire

Strip

Beam Profile


Readout Results: Hit pattern TripletMultiplicity Beam Profile

Wire

Strip

TGC ROD data

Test ROD data


Readout results: Track pattern

DoubletsTriplet

Wire

Strip


Readout integration with MuCTPITGC-ROD has been integrated to run with MuCTPI and ROS

This implies consistent L1IDs from both systems !


MuCTPI Summary 　　　　　　　　　　　 from Thorsten Wengler

Connection to Trigger (Sector Logic) system established.Data of several combined runs (TGC+MuCTPI) were taken into respective ROS PC’s and on Event Builder. The data content looks ok (full analysis still to be done).Although MuCTPI group identified several issues on hardware and software, the present beam test was thought as very useful to record ‘real’ data for the first time and to identify things to be improved.


SummaryTGC electronics has been tested using muon beam and TGC as signal source at H8 (May,27 to June,3)The trigger, readout and control parts have worked and got sensible results from each part.DCS part worked fine.Several bugs, which had not been recognized prevents detailed and quantitative data analysis yet. Some of them, especially bugs related to timing must be cured as soon as possible.In this situation we have achieved to take data in the combined system with MuCTPI for both the trigger and readout streams.We need some more time to consider if we can bring the system again on September.

Documents

CF 8/June/2003 ATLAS muon week in Gallipoli 1 The 1 st Beam Test of TGC electronics at H8 in May/June ‘03 Chikara Fukunaga on behalf of TGC electronics