1 / 17

Status of the TOF-RPC Readout Chain

Status of the TOF-RPC Readout Chain. Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010. Outline. Status PADI PCBs Readout System FEET-PADI & CAEN HPTDC Active LVDS Splitter Results Readout System FEET-PADI/FEET-GET4 & ROC Overview Status Outlook. FEET-PADI Production Status.

duncan-white
Download Presentation

Status of the TOF-RPC Readout Chain

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. Status of the TOF-RPC Readout Chain Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  2. Outline • Status PADI PCBs • Readout System FEET-PADI & CAEN HPTDC • Active LVDS Splitter • Results • Readout System FEET-PADI/FEET-GET4 & ROC • Overview • Status • Outlook Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  3. FEET-PADI Production Status • PADI II • 4 PCBs @ China • 2 PCBs @ India • 1 PCBs @ Heidelberg (Sebastian Manz / ROC Setup) • 3 PCBs @ GSI (3 PCBs not fully equipped) • PADI III • 2 PCBs @ Rossendorf (CAEN Setup) • 2 PCBs @ Heidelberg (Ingo Deppner / CAEN Setup) • 9 PCBs @ GSI (6 PCBs not fully equipped) • 30 PADI II & 30 PADI III are here @ GSI • PCBs are not available at the moment (one PCB is equipped with 2 PADIs => 8 Channel) Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  4. CAEN HPTDC Setup • 2 CAEN HPTDCs V1290 • one TDC for leading edge and one TDC for trailing edge =>it is necessary to split the output signals of PADI • problems with passive splitting leaded to an active solution • tests with 1:10 LVDS-Splitter (Clock Distributor 2, Karsten Koch) Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  5. CAEN HPTDC Test Setup Pulse Generator Reference Signal TDC A TDC B LVDS LVTTL 1:10 LVDS Splitter VME-Readout Dead Time lock Attenuator FEET-PADI 1:10 LVDS Splitter Trigger Trigger Logic Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  6. Results for CAEN TDC Setup From reference signal split into two channels of TDC 35 ps typical from HPTDC manual =>developed PCB with 8x1:2 splitter for Feet-PADI Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  7. LVDS Splitter for FEET-PADI(FEET-PADI-LVDS-AD1) Output for TDC A 70mm Input PADI Signals Output for TDC B Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010 • 8 x 1:2 LVDS Splitter (MAX9174) • 100ΩimpedancecontrolledPCB • 1 PCB for 1 FEET-PADI • 30 PCBs are ordered • delivery date 16.04.2010 (not equipped!)

  8. Outlook FEET-PADI CAEN Setup • system tests in Heidelberg with HD-RPC (Ingo Deppner) • will be used next Beam time • possible that all “Test-RPCs” will have the same readout system • => good for comparison of the different RPCs • LVDS splitter for FEET-PADI will be available soon Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  9. Readout System FEET-PADI / FEET-GET4 & ROC Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  10. Components • CLOSY2 (Karsten Koch) • Clock Generator (250MHz, 156.5MHz, Sync Pulse) • 3x Clock Distribution2 (Karsten Koch) • FEET-PADI (Mircea Ciobanu) • FEET-GET4 (Holger Flemming/Harald Deppe) • R2F (Holger Flemming) • (Adapter between FEET-GET4 & ROC) • ROC (KIP Heidelberg) JochenFrühauf CBM-Collaboration Meeting 12.-16.04.2010

  11. Status • 2 full systems are available for tests • 1x @ GSI • 1x @ KIP Heidelberg • only a few communication tests are done Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  12. Data • no Input – Signals for FEET-PADI • Msg:5 Roc:0 Epoch2:01000000Msg:5 Roc:0 Epoch2:00000000Msg:5 Roc:0 Epoch2:01000000Msg:5 Roc:0 Epoch2:00000000Msg:5 Roc:0 Epoch2:01000000Msg:5 Roc:0 Epoch2:01000000Msg:5 Roc:0 Epoch2:00000000Msg:5 Roc:0 Epoch2:01000001Msg:5 Roc:0 Epoch2:00000001Msg:5 Roc:0 Epoch2:01000000Msg:5 Roc:0 Epoch2:00000000Msg:5 Roc:0 Epoch2:00000000…….. Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  13. Results • 24 times • Msg:5 Roc:0 Epoch2:01000000 • Msg:5 Roc:0 Epoch2:00000000 • followed by 1 time • Msg:5 Roc:0 Epoch2:01000001Msg:5 Roc:0 Epoch2:00000001 • Bit for “CLOSY SYNC PULSE” • Data GET4 Nr.:0 and Nr.:1 • amount of Epoch messages & Sync Pulse message are consistent Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  14. First Data • with 50mV / 10ns Input Signals for FEET-PADI CH1/CH8 • Msg:6 Roc:0 Get4:01 Chn:3 Edge:1 Ts:7c43aMsg:6 Roc:0 Get4:00 Chn:0 Edge:0 Ts:784c0Msg:6 Roc:0 Get4:01 Chn:3 Edge:1 Ts:7c47cMsg:6 Roc:0 Get4:00 Chn:0 Edge:1 Ts:7c438Msg:5 Roc:0 Epoch2:01000000Msg:6 Roc:0 Get4:00 Chn:0 Edge:1 Ts:7c47aMsg:6 Roc:0 Get4:01 Chn:3 Edge:0 Ts:0851eMsg:5 Roc:0 Epoch2:00000000Msg:6 Roc:0 Get4:01 Chn:3 Edge:0 Ts:08560Msg:6 Roc:0 Get4:00 Chn:0 Edge:0 Ts:08511Msg:6 Roc:0 Get4:01 Chn:3 Edge:1 Ts:084fc………… Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  15. Results • data shows hits in the used channel • timestamp counters of GET4 are increasing up to the next “Epoch Message” and afterwards these counters are reseted • different error messages and external sync events in the data stream • only for input signals in the 2nd GET4 chip • no error or ext. sync messages for the 1st chip • crosstalk in the 2nd GET4 Chip • only from Channel 0,1,2 to Channel 3 Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  16. Outlook FEET-PADI / FEET-GET4 & ROC • modification in the FPGA code of the ROC • include timestamp counters, system messages • GO4 analysis • testing setup • test Or-Output of PADI • test I2C Interface of FEET-PADI for threshold adjustment Jochen Frühauf CBM-Collaboration Meeting 12.-16.04.2010

  17. Thank you for your attention

More Related