1 / 19

COPPER Status

COPPER Status. T.Higuchi / KEK. Belle II Data Stream. On/in/at the detector. In the electronics hut. Signal Digitizer. Digital Signal TX. Signal RX. Readout Electronics. Readout PC. ~30m cable. Analog Signal TX. Signal Digitizer. Readout Electronics. Readout PC. Belle II detector.

nyx
Download Presentation

COPPER Status

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. COPPER Status T.Higuchi / KEK Jul.4th, 2009. B2GM Meeting.

  2. Belle II Data Stream On/in/at the detector In the electronics hut SignalDigitizer DigitalSignal TX Signal RX ReadoutElectronics ReadoutPC ~30mcable AnalogSignal TX SignalDigitizer ReadoutElectronics ReadoutPC Belle II detector ReadoutPC STOR ReadoutPC EventBuilder OnlinePC Farm StorageSystem ReadoutPC ReadoutPC

  3. R&D of the Readout Electronics • Present FASTBUS-based DAQ will fail around L1 rate~1 kHz with DAQ deadtime being 20%. And in Belle II, the L1 rate will be ~10kHz. • Call for a new readout electronicsthat works up to L1 rate ~30kHz. Equipped with pipeline(FIFO) Equipped with online CPU for data processing Keywordsof R&D Modularized structure for easier maintenance Usage of commercially available products Seamless switch from the present system

  4. COPPER-II Board Signal RX x 4 orSignal digitizer x 4 Add-on modulesto the COPPER called “FINESSE” Online CPU RadiSys EPC-6315 • Intel P3 800 MHz • 256 MB memory • Network boot • RedHat Linux 9 VME9U size Onboard FIFO1MB x 4 on the tailside Trigger module 100 BaseT port x 2 Data transfer and Control

  5. Signal Digitizer – AMT3 FINESSE • AMT-3 TDC chip 2 http://atlas.kek.jp/tdc • 24 LVDS inputs / chip. • 256-edge deep L1 FIFO (pipeline), 8-event deep trigger FIFO. • Only matching edges to the trigger are output. • 0.7ns timing resolution. • Linearity = 251.0±0.9 ns (RMS) for 250.0 ns width pulse. • Spartan3 FPGA2 • AMT3 register control. • Data format. • COPPER local bus interface,COPPER FIFO interface. “tandem”-structured FINESSE

  6. 100% Compliant w/ PCI Good for a high density applications Many commercial products Ethernet cards, CPUs, GbE cards, memory modules, etc. RadiSys EPC-6315 PMC sized CPU module. Equipped with Intel PentiumIII 800 MHz w/ 512 MB memory. RedHat Linux 7.3 or 9, or FedoraCore 1 Linux run on it. Price = ~\120,000 / module. PCI Mezzanine Card Standard PCI NIC PMC NIC Bootable from CF card or from network.

  7. Performance Review @ 416 bytes/ev/FINESSE Factor-10 datareduction 40 TDC FINESSEEmulator PMC CPU Required trigger rate 30 TDC FINESSEEmulator Clock/TriggerGenerator 20 Accepted trigger rate [kHz] TDC FINESSEEmulator Typical trigger rate 10 Ethernet TDC FINESSEEmulator 0 10 20 30 40 Input trigger rate [kHz] COPPER-II The COPPER works> 30 kHz input rate RX

  8. Performance Review • Crosscheck of the COPPER output and the FASTBUS output. • Signals from the Q-T converter of Belle CDC are branched to the FASTBUS and the COPPER. From CDC Residual distribution 4 2 AMT3 –FASTBUS(unt= AMT3LSB) Daisy-chain 0 COPPER FASTBUS Resolution0.61 LSB (RMS) -2 -4

  9. Performance Review S.Y.Suzuki Normal data size FASTBUS ～29.5 μs Deadtime duration (μs) We achieved 90%deadtime reductionwith pipelined DAQ. COPPER/AMT3 ～2.8 μs # of hits/TDC

  10. 2002-2003 Start of R&D from a scratch. COPPER prototype in hand. 2004 Revision to COPPER-II. Study of maximum acceptable L1 rate: OK up to 30kHz. 2005 Debug of AMT3 FINESSE. Replacement of the Belle EFC DAQ with 6 COPPERs. Crosscheck with FASTBUS DAQ. a 2006 Replacement of part of the Belle CDC DAQ with COPPERs. Crosscheck with FASTBUS DAQ. Deadtime performance study. 2007 Replacement of the Belle CDC DAQ totally with 89 COPPERs. Replacement of the Belle ACC DAQ with 24 COPPERs. 2008 Replacement of the Belle TRG DAQ with 26 COPPERs. 2009 Replacement of the Belle KLM DAQ with 34 COPPERs. ECL and TOF DAQ are kept untouched. COPPER History in Belle DAQ Ready to go

  11. COPPER-II COPPER-3 • Major motivation for the upgrade • Replacement of disappeared/disappearing parts from the market to the available ones. • Bug fix (replacement bug fixing patches to onboard patterns). • Minor modifications • Replacement of the onboard Ethernet to the Gbit-Ethernet. • Length normalization of CLK/TRG lines from TTRX to FINESSEs. • Easier access to a reset switch. • Easier access to VME base address configuration switches. • Change of PMC CPU interfacing connector. • Movement of VME J0receiver location closer to the J0. • RoHS compliant parts.

  12. COPPER-3 Board Looks quite compatible to the COPPER-II.(The board color is changed to turquoise blue)

  13. COPPER-3 Compatibility Study • Before the study: Tips to operate the COPPER-3 • Use specially created Linux image for COPPER-3 • A Linux image for the COPPER-II cannot be used for the COPPER-3. • The special Linux for COPPER-3 is ok for the COPPER-II.

  14. COPPER-3 Compatibility Study • Minor troubles in compatibility study • Swap of eth0eth1 configuration • A bug found in the AMT3 device driver • Compatibility study setup • Same setup as the system test forthe COPPER-II and AMT3-FINESSE AMT3 FINESSE PMC CPU AMT3 FINESSE Clock/TriggerGenerator • Compatible data as the COPPER-II system test are readout in this study. • Trivially, the COPPER-3 can be said OK. • The CPU is booted up properly. • The CPU,AMT3-FINESSEs and trigger timing system works fine on the COPPER-3. AMT3 FINESSE 1 to 96 signal fan-out AMT3 FINESSE Ethernet COPPER-3 RX

  15. COPPER-II/COPPER-3 in Belle II DAQ • The COPPER-3 is ready to use. • We use the COPPER-3 as the data RX in the electronics hut. • We also use existing COPPER-IIs (~250 boards) together with the COPPER-3s. • We will purchase ~250 COPPER-3s including spares in coming 2-3 years.

  16. R&D of Processor PMC (PrPMC) • Problems of EPC-6315 (existing PrPMC) • Future prospect of the product is unclear. • Market trend is switching to ComExpress from PrPMC. • Vendor (US RadiSys) may stop the product supply immediately. • Both vendor and Japanese HQ are quite unprofessional. • The first release of the product was with untested BIOS. • The product was revised with an incompatible network chip. • Japan  US communication is poor. • Call for a new PrPMC withconcrete future prospect and kind support. Now in bidding procedure. The company will be fixed on Jul.14th.

  17. Specification of New PrPMC • CPU • Intel Atom 1.6GHz or more. • Main memory • 256MB or more. • Mass storage • Onboard 4GB SSD or external media like CF. • Network I/F • GbE w/ Intel 82574. • 900Mbps or more. • OS • Redhat Enterprise Linux 3 or CentOS 3 or later. • OS bootup method • From mass storage • From USB device • From network • User I/F • Serial console or USB/PS2 keyboard+mouse + VGA. • Power consumption • < 15W (EPC-6315 … 18W)

  18. Schedule of PrPMC R&D • Jun.19th Announcement of bid • Jul.1stMeeting w/ companies • Jul.7th Deadline of technical report from companies • Block diagram • Layout proposal of major parts • Jul.14th Box open • Company will be fixed on the day • Feb.19th End of R&D. We have two PrPMCs in hand then.

  19. Summary • We are confident that the COPPER-based DAQ is in a “state of the art”. • A new COPPER board, COPPER-3, is compatible with the COPPER-II. We are to employ the COPPER-3s for Belle II readout electronics. • A new PrPMC, which replaces the EPC-6315 with several problems, is under bidding process. We have them by Feb.19th.

More Related