1 / 19

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

The 1 st Beam Test of TGC electronics at H8 in May/June ‘03. Chikara Fukunaga on behalf of TGC electronics group*. *in particular, with help from H.Kurashige, Y.Kataoka , D.Lellouch, L.Levinson, G.Mikenberg , O.Sasaki, S.Tarem, T.Wengler,. TGC electronics at H8.

eliza
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The 1st Beam Test of TGC electronics at H8 in May/June ‘03 Chikara Fukunaga on behalf of TGC electronics group* *in particular, with help from H.Kurashige, Y.Kataoka,D.Lellouch, L.Levinson, G.Mikenberg, O.Sasaki,S.Tarem, T.Wengler, CF 8/June/2003 ATLAS muon week in Gallipoli

  2. 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 + others • With real signals of TGC 7 layers using 3 T8 units • Integrate the system with MuCTPI and CTP • Take data from TGCs together with ones from MDTs CF 8/June/2003 ATLAS muon week in Gallipoli

  3. Hi-pT Trigger 3-let and 2-let R-f coincidence Low pT trigger 3-let or 2-let Level1 buffer and Derandomizer Trigger Electronics CF 8/June/2003 ATLAS muon week in Gallipoli

  4. Beam Test Setup at H8 CF 8/June/2003 ATLAS muon week in Gallipoli

  5. Beam Test Setup at H8 (2) TGC Triplet 2 TGC doublets PS pack Hi-pT crate CF 8/June/2003 ATLAS muon week in Gallipoli

  6. Electronics used • Chamber (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 crate • High pT module (4 Hi-pT ASIC) x1 • Star Switch (SSW) module x2 • HSC • ROD crate(s) • Sector Logic for r-f coincidence • RODs (ROD and Test-ROD alternatively) • TTCvi • CCI • Cable • Individually shielded TP Category-5 cable from PS board to Hi-pT crate 10m (ATLAS:15m) for LVDS • Optical fiber from Hi-pT crate to Sector Logic/ROD in the hut 50m (ATLAS:150m) for G-link. CF 8/June/2003 ATLAS muon week in Gallipoli

  7. Achievements • 1st 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:45Normal 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. CF 8/June/2003 ATLAS muon week in Gallipoli

  8. Bunch Crossing ID in PP ASIC worked. 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. The Sector Logic worked fine for r-f coincidence, and integration with MuCTPI OK. But if synchronization failure at Hi-pT output occured, r-f coincidence could not be achieved (related to I). Test summary - Trigger I. II. III. CF 8/June/2003 ATLAS muon week in Gallipoli

  9. Trigger Data could not be read out. Hit Data could be stored in a readout buffer but not in the correct buffer. Data could be stored in “the next buffer”. SSW for Sector Logic could not send data to ROD. Handling of TTC signals could not be done efficiently. A treatment forgotten made system behaviour very strange. Test summary - Readout I. III. II. IV. CF 8/June/2003 ATLAS muon week in Gallipoli

  10. Preliminary Results - Control • TGC-DCS worked very well during 25 ns at H8 • Most functions already functional and tested • ASIC configuration • Thresholds setting/monitoring, LV monitoring • Basic HV control • DAQ and DB communications • User Manual • Some functions still to be tested • TTCrx configuration via I2C • DCS-HSC • Unique ID • Charge monitoring proved extremely useful diagnostic CF 8/June/2003 ATLAS muon week in Gallipoli

  11. HV • CAEN 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 CF 8/June/2003 ATLAS muon week in Gallipoli

  12. Histogram of analog chamber charge -H8 • One wire analog channel per chamber is read, integrated on DCS-PS and histogrammed on the ELMB CF 8/June/2003 ATLAS muon week in Gallipoli

  13. 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. CF 8/June/2003 ATLAS muon week in Gallipoli

  14. Readout Results Hit-pattern Doublets Multiplicity Beam Profile Wire Test ROD data Strip TGC ROD data CF 8/June/2003 ATLAS muon week in Gallipoli

  15. Readout Results: Hit pattern Triplet Multiplicity Beam Profile Wire Test ROD data Strip TGC ROD data CF 8/June/2003 ATLAS muon week in Gallipoli

  16. Readout results: Track pattern Doublets Triplet Strip Wire CF 8/June/2003 ATLAS muon week in Gallipoli

  17. Readout integration with MuCTPI • TGC-ROD has been integrated to run with MuCTPI and ROS This implies consistent L1IDs from both systems ! CF 8/June/2003 ATLAS muon week in Gallipoli

  18. MuCTPI Summaryfrom 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. CF 8/June/2003 ATLAS muon week in Gallipoli

  19. Summary • TGC 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. CF 8/June/2003 ATLAS muon week in Gallipoli

More Related