ALICE Front-end and Readout Electronics Setup & Configuration Peter Chochula

1. ALICE Front-end and Readout ElectronicsSetup & ConfigurationPeter Chochula

2. Present structure of the online systems in Alice Peter Chochula

3. ALICE online software hierarchy ECS DCS DAQ/RC TRG HLT … SPD TPC … SPD TPC … SPD TPC LV LV HV HV FERO FERO (Source: S. Vascotto, TB presentation, October 2002) Gas Peter Chochula

4. Partitioning of ALICE Online systems ECA PCA PCA DCS DAQ/RC TRG DCS DAQ/RC TRG Partition A Partition A (Source: S. Vascotto, TB presentation, October 2002) Peter Chochula

5. Standard Model of Alice FERO Setup & Configuration • Systems read the configuration from DB • DAQ/RC configures FERO via DDL • DCS is involved in monitoring Config DAQ/RC DCS Config+Data Monitoring + Control JTAG, Profibus, Ethernet, etc. DDL Logging FERO Peter Chochula

6. But... Peter Chochula

7. X X Some detectors need additional processing of data Example: Pixels JTAG path may change, the software needs to detect it and format configuration data Peter Chochula

8. Synchronization of online systems • FERO can be configured only if the related detector parts are ON and well under control Peter Chochula

9. Synchronization of online systems • FERO can be configured only if the related detector parts are ON and well under control • DCS should be informed about the present configuration (monitoring limits etc.) Peter Chochula

10. Synchronization of online systems • FERO can be configured only if the related detector parts are ON and well under control • DCS should be informed about the present configuration (monitoring limits etc.) • DCS can ask for reconfiguration after recovery from failure – other systems must be notified Peter Chochula

11. Synchronization of online systems • FERO can be configured only if the related detector parts are ON and well under control • DCS should be informed about the present configuration (monitoring limits etc.) • DCS can ask for reconfiguration after recovery from failure – other systems must be notified • For some architectures DCS and DAQ/RC are sharing access path to FERO Peter Chochula

12. Alice FERO Architectures Peter Chochula

13. Example: The Design of HMPID PLC DCS (OPC) DCS (OPC) DCS (OPC) RO 1-3 Temp. LV (6) FEE Segments DDL 0 RO 1-3 (6) HV Segments DDL 1 Peter Chochula

14. Example: The Design of TPC Peter Chochula

15. Example: The Design of TPC • Both implemented networks can configure the FERO in TPC • Even if one of the access paths will be used only occasionally (e.g.. debugging) – the implementation must still follow the general rules. Peter Chochula

16. Example: The Design of SPD Pilot MCM Readout Chip Sensor Bus Peter Chochula

17. Summary: Alice FERO Architectures • There are 2 options to configure FERO: • DDL based ( same as Class A) • Non-DDL (Ethernet, etc.) • DDL is used to configure FERO • Monitoring is based on different • technology DDL Configuration DDL Configuration Configuration Monitoring Monitoring FERO FERO Class A Class B • DDL is not involved in configuration • Configuration and monitoring are sharing the access path to FERO Configuration Monitoring Configuration Monitoring FERO FERO Class C Class D Peter Chochula

18. The Front-end Device (FED) Peter Chochula

19. DCS interacts with devices via well defined interfaces Hardware details are usually transparent to upper layers (Example: CAEN, ISEG) Preferred communication technologies are OPC and DIM Controls Technologies Customization, FSM Supervision (SCADA) Communications (OPC,DIM) Process Management (PLC…) Device Hardware Peter Chochula

20. Concept of the Front-end Device (FED) Additional monitoring path PCA DCS DAQ/RC FED DDL Sw DIM Client DIM Client DDL Sw DIM Server DAQ Workstation (LDC) FED CPU LVPS PLC Profibus, JTAG, etc. DDL FERO Hardware Peter Chochula

21. Controls Hierarchy Example: DAQ/RC is in charge of configuration PCA Commands Trigger DAQ/RC DCS Configuration CU Monitoring CU Trigger status CU Configuration DU Monitoring DU Trigger status DU FERO Hardware Status FED see C. Gaspar: Hierarchical Controls Configuration & Operation, published as a CERN JCOP framework document http://clara.home.cern.ch/clara/fw/FSMConfig.pdf Peter Chochula

22. Synchronization of online systems using the FED Peter Chochula

23. Example: Configuration of a device belonging to “CLASS A” PCA 1 DAQ/RC DCS 2 FERO CPU LVPS FERO Hardware PLC 3 DAQ/RC PCA 4 Peter Chochula

24. Example: Configuration of a device belonging to “CLASS B, C or D” PCA 1 DCS DAQ/RC 2 FERO CPU FERO Hardware DCS 3 PCA DAQ/RC 3 Peter Chochula

25. Using our model, both DAQ/RC and DCS are equivalent in the terms of FERO configuration • Both systems can reuse the same software! Peter Chochula

26. FERO Configuration and Synchronization via PCA. (Classes A,B,C,D) DAQ/RC DCS DAQ/RC DCS PCA PCA FERO WS FERO WS BUSY BUSY FERO FERO DDL DDL PCA PCA Peter Chochula

27. Related questions and actions Peter Chochula

28. Related questions • We need a clear strategy for database implementation – see talk of F. Carminati, TB Dec 2002 • We need a description of detector components (numbering and naming conventions) • We need feedback from detectors on configuration and monitoring issues – FERO design, details on interactions between systems, definition of FSM etc. Peter Chochula

29. Prototyping • First prototypes will help us to define the software interface and solve the problems related to controls hierarchy • There are 2 candidates for prototyping: • HMPID (advanced in FERO and FSM) • Pixels (available test systems @ CERN) Peter Chochula

30. Conclusions • The FERO configuration in Alice depends on architecture of individual detectors • Present detector architectures can be divided into four categories • Concept of the Front-end Device allows to unify the access to FERO. Detector details will be encapsulated in the custom software Peter Chochula