Presentation is loading. Please wait.

Presentation is loading. Please wait.

ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review.

Similar presentations


Presentation on theme: "ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review."— Presentation transcript:

1 ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review

2 Connections RUN1: VME RUN2: VME, USB RUN3: VME (TTCmi crate), USB (PM/SPI), IPbus USB: PM/SPI bus on new board s Lab: connected to Wxx PC with USB cable P2: Anywhere USB-Ethernet-USB adapter allowing longer distance VME, replaced by IPbus in run3: Board’s FPGA programming (not clear yet, if IPbus can be used) Boards control Counters reading SSM reading possibly CTP readout using IPbus in run3 2

3 Run2 layout NFS/BOOTP server serving VME CPUs NFS/BOOTP server serving VME CPUs Application server (SMAQ, IR processing) Application server (SMAQ, IR processing) Diskless VME CPU CTPCTP CTPCTP LTULTU LTULTU RF2TTCRF2TTC RF2TTCRF2TTC LTULTU LTULTU 9 VME CPUs controlling 9 VME crates VME bus 3 Alice experimental network cavern

4 Run3 layout NFS/BOOTP server serving VME CPU IPbus Controlhub NFS/BOOTP server serving VME CPU IPbus Controlhub Application server Diskless VME CPU CTPCTP CTPCTP LTULTU LTULTU RF2TTCRF2TTC RF2TTCRF2TTC LTULTU LTULTU Alice experimental network 1 VME CPU VME bus 4 1Gb switch 1Gb private Ethernet, for IPbus cavern

5 IPbus Based on UDP protocol over 1Gb Ethernet Reliable TCP connection when used with Control hub –part of IPbus software Data word: 32bits Typical latency: 250 – 450 usecs Typical throughput: 50 – 500 Mb/s, depends on the length of data block Software API: Available for C++ and python Allows single atomic operations: Read, Write Read+Modify bits: (X= (X&A) | B Read+Modify sum: X= X+A Block R/W operations Future plans: Streaming DAQ port (aka DDL in run2) 10Gb ethernet http://dx.doi.org/10.1088/1748-0221/10/02/C02019 (2014 TWEPP paper) https://svnweb.cern.ch/trac/cactus/wiki 5

6 IPbus example address_table.xml: describing firmware connection_file.xml: specifies particular IPbus endpoint <connection id="board.1" uri="chtcp-2.0://localhost:10203?Control hub target=137.138.201.240:50001" IPbus endpoint address_table="file://address_table.xml "/> 6

7 C++ #include "uhal/uhal.hpp" #include "uhal/tests/tools.hpp" //open connection ConnectionManager manager ( "file://../connection_file.xml" ); HwInterface hw=manager.getDevice ( "board.1" ); // Request for block and simple register read ValWord reg; ValVector ram(1000); ram= hw.getNode( "ram" ).readBlock(1000); reg= hw.getNode( "reg" ).read(); // data transfer starts/finishes with following line hw.dispatch(); cout << "reg:" << reg.value() << " ram[0]:" << ram.at(0) << std::endl; 7

8 Summary Latency: VME (~1us) much faster, but is not an issue for CTP/LTU control Throughput SSM (=4MB) read: VME using word access 28Mb/s, IPBUS: ~ 500Mb/s is meaningful IPbus used for CTP readout: possible, with rates given in an example below, using 4kB data blocks (50Mb/s IPbus data rate ) IRs stream: 64bits/interaction, as used in run2/DDL2, IR rate 500kHz corresponds to 32Mb/s IPbus data rate Trigger messages: 144 bits/message, 100 kHz event rate corresponds to 14.4 Mb/s in IPbus data rate 8


Download ppt "ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review."

Similar presentations


Ads by Google