1. 5 March 2002 - DCS Final Design Review: RPC detector The DCS system of the Atlas RPC detector V.Bocci, G.Chiodi, E. Petrolo, R.Vari, S.Veneziano INFN Roma

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

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

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

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

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

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

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

9. 5 March 2002 - DCS Final Design Review: RPC detector 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

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

11. 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 Hardware and SoftwareTools used

12. 5 March 2002 - DCS Final Design Review: RPC detector 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

13. 5 March 2002 - DCS Final Design Review: RPC detector 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

14. 5 March 2002 - DCS Final Design Review: RPC detector 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)?

15. 5 March 2002 - DCS Final Design Review: RPC detector 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).

16. 5 March 2002 - DCS Final Design Review: RPC detector 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