1 / 10

FED update

FED update. Peter Chochula. Workshop on Radiation Hard Electronics for ALICE (CERN, August 30). FED architecture has been (again) presented at Workshop on radiation hard electronics for ALICE (CERN, August 30) Slides are available on ALICE Electronics coordination pages

gaura
Download Presentation

FED update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FED update Peter Chochula

  2. Workshop on Radiation Hard Electronics for ALICE (CERN, August 30) • FED architecture has been (again) presented at Workshop on radiation hard electronics for ALICE (CERN, August 30) • Slides are available on ALICE Electronics coordination pages • Almost all ALICE sub-detectors were present to the workshop • The talk was well received P. Chochula DCS Workshop, CERN , September 2004

  3. Workshop on Radiation Hard Electronics for ALICE (CERN, August 30) • From following discussion it has been clear that so far the software developments for FED and its integration with ALICE online systems are not advancing very well • designers are partly unaware of FED concepts • Big progress for CLASS “A” devices (HMPID), TPC and TRD and SPD • It has been agreed that it would be useful to organize a workshop dedicated to FED operation (December 2004?). Most detectors did not perform a detailed study of the FED operation yet P. Chochula DCS Workshop, CERN , September 2004

  4. Present FED developments • Thanks to Worms group and excellent feedback from TPC and TRD, FED has progressed for RCU based architectures • Developments are re-usable for TPC, TRD, PHOS and FMD • Marc kindly agreed to provide latest news P. Chochula DCS Workshop, CERN , September 2004

  5. SPD developments • SPD is entering a new phase • Final readout module (router) becomes available • Software used for its testing will be based on FED architecture • SPD FED prototype used a software emulator which replaced the hardware • Present work (I.A.Cali) is focused on replacing this with real hardware drivers. P. Chochula DCS Workshop, CERN , September 2004

  6. SPD FED preparations for combined ITS testbeam (October 2004) • The router module will be tested in combined ITS testbeam in October • FED Server will be used to access the FERO • Three steps of FED development • All FERO related commands (configure, calibrate, …) are implemented as standalone code • Once debugged, the code will be included into the FED framework • Database access for FERO will replace plain ASCII files P. Chochula DCS Workshop, CERN , September 2004

  7. FED related questions • FE1: How often are the FERO parameters (specified in DB2) loaded? • This question is related both to database and to FED • Frequency of FERO re-configurations has impact on many topics • Data caching • ECS interface • Network throughput, performance • What are the reasons (besides the SEU) for re-configuring FERO • Do we need to stop the run? P. Chochula DCS Workshop, CERN , September 2004

  8. FED related questions • FE2: how are the SEU monitored and what recovery actions are expected from DCS? (Indicate also expected frequency of these events) • How does the DCS detect automatic re-boot of FERO? • What do you need to record in database? • How does the DCS know that the electronics is re-booted as a consequence of SEU and not due to e.g. a network problem P. Chochula DCS Workshop, CERN , September 2004

  9. FED related questions • FE3: provide a complete list of FERO parameters to be monitored, including also status flags etc. Indicate also required actions from DCS if some of these parameters are out of range. • these numbers are needed in order to estimate the impact on network bandwidth • What other flags are monitored, what is the expected DCS actions once these are out of range P. Chochula DCS Workshop, CERN , September 2004

  10. FED related questions • FE4: describe the detector calibration procedure and interaction between online systems • How often do you need to calibrate and how long does it take? • How much data is collected and what is its destination? • What is the communication between online systems • Do you perform standalone calibration? • Do you need to synchronize DCS, DAQ and TRG? P. Chochula DCS Workshop, CERN , September 2004

More Related