Normal text - click to edit RCU – DCS system in ALICE RCU design, prototyping and test results (TPC & PHOS) Johan Alme

Normal text - click to edit RCU – DCS system in ALICE

RCU design, prototyping and test results (TPC & PHOS)

Johan Alme

Normal text - click to edit

Content

• Overview• RCU - Read Out Control Unit• DCS – Detector Control System• Event Readout • Test results• Ongoing Work


Overview


RCU – Read Out Control Unit

• Hardware entirely developed by Bergen.

• Firmware a collaboration between Bergen and CERN

• Tasks– Shipping event data from the Front End Cards to the DAQ

(Data Aquisition)

– Distributing Triggers

– Communication with the Front End Electronics


RCU

RCU Architecture

Trigger IF

StatusRegister Slow Control

Active FEC list

ALTRO IFInstuction Mem

Result MemActive Ch. List

DataAssembler

SIU interface

CommandInterpreter

& Bus Switch

FE

C

Altro Bus

I2C Bus

FE

C

RCU bus

DCS

SIU

Trigger information

DATA PATH

RCU Bus has been tested in a 12h stress-test with approximate 200 billion transactions without any error


DCS - Detector Control System

• Collaboration between Bergen and Heidelberg • Tasks

– Configuring the RCU FPGA– Configuring the Frond End Electronics Cards (FEE)– Monitoring/Controlling of the FEEs– Configuration of the Trigger system.


DCS Architecture

ARM Processor

Ethernet IF

JTAG master

ADC readout

RCU Bus IF

RCU FPGA Config

Dim

connector (RC

U)

TTCRX

RCU bus

Triggerinfo

ADCs

JTAG

Ethernet


Firmware/Software on DCS

DIM client

Shell DIM server

Linux Kernel

Driver

Module Interfaces

Intercom layerDirect login (SSH)

Software

Firmware (FPGA)

• Direct Login via SSH used in TPC and PHOS beamtests.

• DIM server and DIM client development is ongoing.


FEC

LinuxshellsendRCUcommand

Event Readout example

DCS

RCU

FECFECAltro IF

Trigger IF

DataAssembler

SIU IF

FECsDaq

1. Configure system to wait for trigger

2. FEC collects data when L1 trigger. 3. RCU reads event when L2a trigger and

ships it through the datapath to the

DAQ. 4. When done, RCU again waits for new

trigger.

w 0x7000 0x64000aw 0x7001 0x700125w 0x7002 0x64000bw 0x7003 0x700000w 0x7004 0x64000cw 0x7005 0x70000fw 0x7006 0x3b0000w 0x7007 0x360000w 0x7008 0x300005w 0x7009 0x390000wait 1 usr 0x0

w 0x8800 0x00080000w 0x6400 256 0x0000w 0x6498 0xffffw 0x649A 0xffffw 0x649B 0xffffw 0x649C 0xffffw 0x7802 0x10bb8wait 1 us

Trigger info

L1 Trigger

Buffering event...

L2 acceptTrigger

Important: Only RCU FPGA is directly in the datapath.


Configuration & Readout

Transporter to DCS scripts

RCU

buffer

FE

CF

EC

• 3200 active channels• 1000 samples/channel

< 1 s 0.7 s 3 s

Overall configuration data: 7MB/RCU – Worst case scenario

Max 4,7 s for configurationReadout: 3 ms


TPC Beamtest results


Test results

• Successfully used in the TPC beamtest.

• Successfully used in the PHOS beamtest.

• More systems are running smoothly in a lab environment.


Ongoing work

• Change the FPGA on the RCU board from Altera to Xilinx for better handling of radiation– Test-card– New RCU board prototype ( Mass production late 2005)– Hardware & Firmware for automatic reconfiguring of RCU – Extensive testing of radiation harness

• Firmware for voltage and temperature measurements• Firmware for trigger interface module.

Documents

Normal text - click to edit RCU – DCS system in ALICE RCU design, prototyping and test results (TPC & PHOS) Johan Alme