ACDC3 Data Flow Feedback: Testing Results & Control Software Overview
50 likes | 175 Vues
Explore the testing results and control software details for ACDC3, including issues and solutions. Learn about equipment compatibility, packet routing challenges, and software management with HP devices.
ACDC3 Data Flow Feedback: Testing Results & Control Software Overview
E N D
Presentation Transcript
Feedback from ACDC3 Kazu Akiba
Data Flow • 12 Tell1s plus Odin put together on the crate • NZS Data: 4~5kBx12 per event: • 2.0 kEvent/s max DAQ with 1 PC. • Tested with MEP factor up to 4 (NZS) and 15 (ZS) • Too many packets to route: • 1 switch is not enough for the Velo (HP 3400) • 2 HP3400 work! • 1 to funnel, the next one to route. • Works, but without Jumbo frames. • Artur brings the peacemaker: • HP5412 handles the job with no problems.
Controls Software • Velo Front-end, Tell1s, Odin, Hughin and Velo Temperatures controlled by PVSS • DIM_DNS_NODE was quite busy… • ISEG HV and CAEN LV software from the company • Conservative approach. • Cooling monitoring as stand alone application (LabView)
Issues • Tell1 individual FSM does not check if the CCPC is alive: configuration fails. • Network interface on lbh8lx02 started to give up (required a sudo service network restart from time to time towards the end of the test beam.) • EB has a small dead time when closing or opening a new file. • Optical failure leads to some asynchronization: dangerous with 1 DAQ PC. • Some aparent asynchronization between Odin and Tell1s… To be confirmed.
Before After 4000 86