1. Ervin DÉNES Collab Meeting, 23 – 26 2008 1 Emulating TOTEM Front-End Driver for trackerDAQ sw

2. Ervin DÉNES Collab Meeting, 23 – 26 2008 2 TOTFED TOTFED has: INPUT - 3 x OptoRX OUTPUTS- 4 x S_Link64 - 4 x USB2.0 - 1 x VME64x

3. Ervin DÉNES Collab Meeting, 23 – 26 2008 3 Data flow from VFATs to VME trough TOTFED GOH 0 VFAT1 VFAT16 GOH 11 VFAT1 VFAT16 TOTFED OptoRx 1 OptoRx 2 OptoRx 3 MAIN 1 SPY mem 1 MAIN 2 SPY mem 2 MAIN 3 SPY mem 3 VME 192 1 1 32

4. Ervin DÉNES Collab Meeting, 23 – 26 2008 4 16 1211 43 0 1010Bunch Counter 1100Event CounterFLAGS 1110Chip ID Channel data (128 bits) CRC 16 bits checksum Data at VFAT output (OptoRX input)

5. Ervin DÉNES Collab Meeting, 23 – 26 2008 5 12 bits VFAT chip ID is not unique! For identifying VFAT chip we has to find out the VFAT data comes from: –position number of VFAT for the given GOH –position number of GOH for the given OptoRx –position number of OptoRx for the given FED –FED board ID What info is needed?

6. Ervin DÉNES Collab Meeting, 23 – 26 2008 6 VFAT to GOH Data Format 0….…………………………..…15 176.………………….………..192 15.. …………. …….. …………….. … 0 VFAT 0 0….…………………………..…15 176.………………….………..192 VFAT 15............... 192……………………………………………………………………………………………………...…..……………….………..0 first wordlast word One Packet 0….…………………………..…15 176.………………….………..192 15.. …………. …….. …………….. … 0 VFAT 0 0….…………………………..…15 176.………………….………..192 VFAT 15............... 192……………………………………………………………………………………………………...…..……………….………..0 first wordlast word One Packet 0….…………………………..…15 176.………………….………..192 15.. …………. …….. …………….. … 0 VFAT 0 0….…………………………..…15 176.………………….………..192 VFAT 15............... 192……………………………………………………………………………………………………...…..……………….………..0 first wordlast word One Packet VFAT Data: - 192 bits serial; - 16 VFATs per GOH; - 12 GOHs per “OptoRX” 192 x 16 x 12 = 36864 (~4kBytes) packet Gueorgui, June 2007

7. Ervin DÉNES Collab Meeting, 23 – 26 2008 7 Data Format in buffer memory 32 bits VME words read from a Spy memory GOH 11 10GOH 9 8GOH 7 6GOH 5 4GOH 3 2GOH 1 0       Bit 0 of VFATs 16 … 1 of GOH 11 ….. 0 Bit 1 of VFATs 16 … 1 of GOH 11 ….. 0 Bit 191 of VFATs 16 … 1 of GOH 11 ….. 0

8. Ervin DÉNES Collab Meeting, 23 – 26 2008 8 Using CAEN controller read the 6 x 192 VME (32 bits) words Re-map the data Add header containing –position number of VFAT for the given GOH –position number of GOH for the given OptoRx –position number of OptoRx for the given FED –FED board ID To be discussed –header for each OptoRx and/or each GOH? What to do with VME data?

9. Ervin DÉNES Collab Meeting, 23 – 26 2008 9 Timing considerations Gigabit Optical INPUT 640Mb/s/fiber x 12 = 7.68Gb/s VME64x OUTPUT 40MB/s BLT Data Bandwidth – by definition S-Link64 OUTPUT 480MB/s 64bit@60MHz USB2.0 OUTPUT 480Mb/s – high 12Mb/s – full 320Mb/s – effective Real Example: CAEN Contr. + Tracker FED 6.6MB/s BLT read TOTFED has: INPUT - 3 x OptoRX -> 3 x 7.68Gb/s OUTPUTS- 4 x S_Link64 -> 4 x 480MB/s - 4 x USB2.0 -> 4 x 320Mb/s - 1 x VME64x -> 40MB/s TOTEM Experiment Trigger Rate- 1 kHz Event Size- 40 kBytes S_Link64 OUTPUT 480MB/s 64bit@60MHz Gueorgui, June 2007