90 likes | 261 Views
HOLA and FTK_IM tests in SR1. Duo-HOLA in Pixel & SCT RODs. New HOLA works as a drop-in replacement for the original HOLA in both Pixel and SCT RODs It took us a couple of days to get their software infrastructure working in SR1 A lot of problems running partitions
E N D
Duo-HOLA in Pixel & SCT RODs • New HOLA works as a drop-in replacement for the original HOLA in both Pixel and SCT RODs • It took us a couple of days to get their software infrastructure working in SR1 • A lot of problems running partitions • Solved with help from the experts • Small issue with dimensions: • HOLA front mounting panel has a hole through which the optical transceiver sticks out • But our HOLA has two such transceivers!
Single-output HOLA panel in a ROD-BOC motherboard The mounting panel provides enough space for only one transceiver
Duo-HOLA was installed without a mounting panel → YIKES! With slight pressure, our HOLA touches the grounded rim of ROD-BOC card. As a result, strong current burns a protective resistor on the ROD-BOC.
HOLA + FTK_IM setup XOFF (DAQ) ROD ROBIN I ROS (PC) Pattern generator DAQ link Duo-HOLA XOFF XOFF (FTK) FTK link XOFF (FTK) ROBIN 2 Attenuator FTK_IM replicates the data it receives from HOLA and sends it to a 2nd ROBIN. A PC reads out and validates data from both ROBINs. We control the speed of each readout to selectively exercise XOFF FTK_IM EDRO board
XOFF from FTK • Pixel: FTK can hold the data (XOFF) for an arbitrarily long period of time. • This is just a feature of their SR1 testbench • Once XOFF removed, data flow continues • SCT: at ~100 Hz even rate (maximum for their SR1 testbench), FTK can hold data for up to 10 seconds • Beyond that, ROS times out, and the corresponding ROD is completely taken out of data taking. • Need to be careful!
Fear of spurious XOFFs • During FTK commissioning, FTK fiber may be plugged/unplugged at will • Random noise on the FTK fiber may induce spurious XOFFs on HOLA side • XOFF status is sampled at 100 MHz • Significant probability to get it randomly • At 100 KHz event rate, spurious XOFFs may introduce enough downtime to take down the ROD (see previous slide)
Possible solutions • Initially, load a version of HOLA firmware without FTK XOFF • Replace firmware later (eg, technical stop) • Replace one HOLA LED with a jumper that enables/disables FTK XOFF • Have a programmable register in HOLA that enables/disables FTK XOFF • HOLA starts up without FTK XOFF • At any time, FTK XOFF can be enabled by sending a special set of programming signals through S-LINK return lines from FTK_IM • Already implemented and tested • We like solution #3. But should we also add a jumper (#2) – just to be on a safe side?
Thanks • Big thanks to Pixel and SCT experts (too many to list here) • Jinlong organized everything and provided invaluable help along the way • Alberto, Francesco, Marco, Andrea