1 / 16

The DCS system of the Atlas RPC detector

The DCS system of the Atlas RPC detector. V.Bocci, G.Chiodi, E. Petrolo, R.Vari, S.Veneziano INFN Roma. Atlas RPC muon system location. follow ELMB tests done by DCS group. Location of the CAN nodes in the LVL1 muon Trigger. PAD Boards.

hagen
Télécharger la présentation

The DCS system of the Atlas RPC detector

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 DCS system of the Atlas RPC detector V.Bocci, G.Chiodi, E. Petrolo, R.Vari, S.Veneziano INFN Roma 5 March 2002 - DCS Final Design Review: RPC detector

  2. Atlas RPC muon system location • follow ELMB tests done by DCS group 5 March 2002 - DCS Final Design Review: RPC detector

  3. Location of the CAN nodes in the LVL1 muon Trigger PAD Boards There are about 900 PAD boards, each one with an ELMB CAN node. 5 March 2002 - DCS Final Design Review: RPC detector

  4. CAN node CAN branch Can branches in Atlas muon detector • 900 CAN NodesDivided in chain of about 16 nodes: • about 64 branches • or 32 if branches grouped in max 32 nodes. Branches are foreseen for HV, LV power supplies. Design is not yet final 5 March 2002 - DCS Final Design Review: RPC detector

  5. CANbus on-detector connectivity Trigger and readout logic sector 5 March 2002 - DCS Final Design Review: RPC detector

  6. PAD board layout Remote I2C ELMB CAN daisy chain PAD board with TTCrx ELMB XCV200 and Optical Link 5 March 2002 - DCS Final Design Review: RPC detector

  7. PAD ELMB signals Optical link fpga FPGA configuration mode select Prom Jtag Reset CM Jtag Chain FPGA power down System reset Temperature I2C Long distance I2C Configuration I2C TTC Controls SPI interface (SPI Flash) 5 March 2002 - DCS Final Design Review: RPC detector

  8. CAN node connections PAD Logic TTC CM ASIC PAD controls x4 I/O PRODE delay CAN node x4 I2C Remote I2C (splitter) Transceiver Logic 8/16 bit Microcontroller node controller CAN Controller Chip I2C LM75 Temperatures SPI x5 I2C AD7417 ADC JTAG PCF8575 16-bit IO SPI Flash prom JTAG FPGA FlashRom x7 Connectivity SCAN Board Test Chips with JTAG SCAN PAD Logic Optical Link CM 5 March 2002 - DCS Final Design Review: RPC detector

  9. Pad devices controlled by ELMB • Distrubuted on motherboard and remote or piggy CM, link, TTC boards: • I2c Temperature sensors • TTC • Delay chips • FPGA • Flash prom FPGA • Flash prom SPI • I2c I/O registers • Coincidence matrix ASIC (about 200 I2C registers) • Optical link controls 5 March 2002 - DCS Final Design Review: RPC detector

  10. 5 March 2002 - DCS Final Design Review: RPC detector

  11. Hardware and SoftwareTools used • ELMB board • IXXAT 165 PCI CANBUS board • IXXAT CAN Analyzer • IXXAT canopen Client • IXXAT Tincan interface PCMCIA • Virtual Can Interface Library (VCI) • CAN open Master API 5 March 2002 - DCS Final Design Review: RPC detector

  12. Software development: • We integrated a single bus I2C in the CAN node. A guideline has been the document from Henk, but (we use SDO and): • We need to multiple I2C buses (three), only one implemented so far • We need different ‘flavors’ of I2C. • (SDO block transfer could be used for large I2C registers). • Software for FPGA readback on JTAG/SPI written for AVR evaluation board. • Readback and diff with SPI flash memory data takes 15 s. • We wrote new ccan.c and ccan.h to interface ixxat board 5 March 2002 - DCS Final Design Review: RPC detector

  13. Software requirements • We need a lot of functionalities on our ELMB firmware, only some is covered so far by the CERN/Nikhef supported software: • Efficient ‘Low level’ I2C/JTAG/SPI instructions, as we have developped so far • ‘high level instructions’, like • Load FPGA with SPI flash data • Check FPGA firmware • Initialize ASIC (200 I2C registers) • Read all temperatures • Measure clock phases from delay chip outputs • Monitor remote splitter board voltages and temeperatures 5 March 2002 - DCS Final Design Review: RPC detector

  14. Software • Currently we have an MS windows PC and IXXAT board and one ELMB. Current aim is: • ‘high level’ commands developped on pc (Microsoft Visual c++), low level commands sent via CAN. • ELMB interprets only ‘atomic’ instructions. • Then we will ‘move’ the high level commands from the remote application to ELMB firmware • We still need to: • define the full set of CAN commands; • understand the final size of this firmware. • Integrate to PVSS/OPC • Current distribution of GNU gcc is now supporting AVR. Should we move from ICAV to gcc (from windows to a generic windows/linux platform)? 5 March 2002 - DCS Final Design Review: RPC detector

  15. PVSS II • We wait for collaboration decision about final PCI boards. • PVSS II and OPC is now working on PCs and NI boards, on a test case configuration different from what we need. • Is an OPC server capable of handling our requests (realtime)? • Once our control software is implemented on PC/ELMB, is it portable to PVSS/OPC ? (rules/regulations to follow?) • We may want to start with PVSS II now, to understand this issues (e.g. database access). 5 March 2002 - DCS Final Design Review: RPC detector

  16. ELMB in the final system • We need about 1000 boards including spares for the final system. • We have 10 boards for out prototype work • It is time to start to think about the structure of the final system: • How many CAN nodes per PC ? • How many PCs ? • Check on initialization time vs CAN nodes per PC has to be done • (also ethernet-CAN boxes, configured as OPC servers, exist, they are small) • Do we have an answer on space needs? We need to answer on rack allocation 5 March 2002 - DCS Final Design Review: RPC detector

More Related