1. CONFIGURATION OF FERO IN ALICE Peter Chochula 7 th DCS Workshop, June 16, 2003

2. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 2 Outline  Alice Online System architecture  Configuration classes and assignment of detectors to them  FERO Architectures of detectors which will be configured via DCS  Example of SPD developments  TRD/TPC developments  Next steps…

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

4. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 4 Partitioning of ALICE Online systems DAQ/R C PCA DCSTRG ECA (Source: S. Vascotto, TB presentation, October 2002) Partition A DAQ/R C PCA DCSTRG Partition A ECA: Experiment Control Agent PCA: Partition Control Agent

5. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 5 Summary: Alice FERO Architectures FERO Class A FERO Class B Class C FERO Class D FERO Configuration Monitoring DDL is used to configure FERO Monitoring is based on different technology There are 2 options to configure FERO: DDL based ( same as Class A) Non-DDL (Ethernet, etc.) DDL is not involved in configuration Configuration and monitoring are sharing the access path to FERO Configuration Monitoring Configuration DDL

6. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 6 Concept of the Front-end Device (FED) PCA DAQ/RC DCS FED CPU FERO Hardware DIM Server DIM Client PLC LVPS Profibus, JTAG, etc. Additional monitoring path DAQ Workstation (LDC) DDL Sw DDL FED

7. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 7 Detectors assignment to FERO Classes Class AClass B Class CClass D PMD SSD SDD HMPID Muon Tracker Muon Trigger PHOS CPV SPD PHOS – Spectrometer TOF T0 TPC FMD TRD V0 EMC

8. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 8 FERO Configuration for devices belonging to Class “A”  DAQ/RC is in charge of the configuration  DCS action might be needed prior to configuration Detectors should document their needs in URD

9. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 9 Detectors configured via Ethernet  6 detectors in Alice will be probably configured via Ethernet: Class “C”  TRD Class “B”  TPC  PHOS (Spectrometer)  FMD  TOF  T0

10. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 10 TOF and V0 FERO Architectures  TOF Architecture relies on 2 independent Ethernet paths for FERO configuration/debugging At the lowest level CAN and TOFwire links are implemented Additional Ethernet connection enables debugging, SEE recovery, etc.)  DDL can be used to configure FERO  TOF is a member of “CLASS B”  T0 FERO architecture is based on TOF developments

11. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 11 TOF Architecture TOF FEE CRATE TOF Module TRM DRM (Linux PPC) LTU PTB Clock, L1-L2, BUSY, L0-T0 RORC DDL MDT SCM TOFWire ETHERNET CAN Inside L3 Magnet Reference: F. Cindolo Overall TOF: 18 Barrel Sectors 36 Ethernet Connections

12. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 12 TPC, TRD, FMD, PHOS-Spectrometer Architectures  TPC FECs (Front-End Cards) are controlled by RCUs DCS connection to DCS board (placed on RCU) is implemented via Ethernet (Profibus) DDL option for configuring FERO is preserved Modified versions of RCU will be implemented in FMD and PHOS  TRD FERO is controlled by readout boards DCS connection to DCS board is implemented via Ethernet DDL will not be used to configure FERO All systems behave identically from the point of view of DCS system (DCS boards are compatible)

13. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 13 Overall TPC: 4356 Front End Cards 216 Readout Control Units TPC FEE Architecture CONF. & R/O MON. & CTRL BOARD CONTROLLER DATA PROC. DATA MEMORY DAQ INT (DDL-SIU) DCS INT (PROFIB, ETHER,...) TRIGGER INT (TTC-RX) CONFIG. & READOUT NETWORK (100 MB / s) DCS NETWORK 1 2 25 RCU CRXUX LOW VOLTAGE POWER SUPPLY FEC COOLING FEC 128 ch Ref: L. Musa, U. Frankenfeld DCS Board

14. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 14 TRD FERO Architecture MCM, Vreg, …. Configured via DCS board TRD consist of 540 chambers Slides: M.R. Stockmeier Identical DCS board will be used in TPC Overall TRD: 540 Chambers

15. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 15  TPC and TRD started their developments of configuration software  Efforts focused on DCS board access  Developments can be reused by other detectors based on the same DCS board

16. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 16 V0 FERO Architecture FEE is accessed via VME modules Ref: B Nielsen

17. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 17 EMC FERO Architecture FEE is accessed via VME modules Ref: M Cherney

18. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 18 SPD FERO Model Configuration Mode Operation Mode JTAG Pixel Chip MCM

19. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 19 SPD FERO Access Architecture (2).. VME Crate Router VME Master (MXI)

20. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 20 SPD FERO Access Architecture (2) Router(s) MXI-2 1 router services 6 halfstaves SPD contains 20 routers PCI-MXI DC S DAQ MXI-VME Trig

21. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 21 Architecture of SPD’s FED JTAG MXI-2 MCM AgentT Agent Configuration VISA MXIVME DetectorVME CrateFED WS Hardware Software

22. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 22 Architecture of SPD Control Software PVSS DIM Client CA1 CA2MA1 SPD Halfstave MCM Router VISA PCI-MXI-VME Database DIM server Commands Data, flags Monitoring Agents (MA) are implemented as separate thread Control Agents (CA) react to commands received by the server Monitoring Agents (MA) publish data as DIM services Commands recognized by SPD Software: Start/Stop Agent Modify Agent parameters (refresh rate, deadband) Set Debugging level Configure SPD

23. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 23 Implementation of Control Software in SPD HW Interface Control Agent 1 Control Agent 2 Monitoring Agent 1 Monitoring Agent 2 Control & Monitoring Application Control Agents receive and execute commands Monitoring Agents Read information from hardware

24. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 24 Implementation of Control Software in SPD DIM Services DIM Commands HW Interface FED ONLINE Systems Control Agent 1 Control Agent 2 Monitoring Agent 1 Monitoring Agent 2 DIM Server Control & Monitoring Application DIM Server enables communication between Agents and control Application

25. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 25 Implementation of Control Software in SPD DIM Services DIM Commands T V,I Flags Get/Set Server Parameters Start/Stop Agents Configure HW Interface FED ONLINE Systems Control Agent 1 Control Agent 2 Monitoring Agent 1 Monitoring Agent 2 DIM Server Control & Monitoring Application Commands need Bidirectional Data Flow (acknowledge) Monitoring Agents do not receive data – Unidirectional Data flow

26. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 26 Implementation of Control Software in SPD DIM Services DIM Commands T V,I Flags Get/Set Server Parameters Start/Stop Agents Configure Monitoring Client 1Monitoring Client 2 Control Client HW Interface FED ONLINE Systems Control Agent 1 Control Agent 2 Monitoring Agent 1 Monitoring Agent 2 DIM Server Control & Monitoring Application

27. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 27 SPD Control Software Prototype SPD DIM Server DID (Dim Client) DimTree (Dim Client) Service Data

28. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 28 SPD Prototype Dim Client (PVSS Version)

29. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 29 SPD Software – configuration database access  SPD Configuration Database prototype is based on MySQL  First implementation relies on ADO technology  Data is retrieved by the FED software, PVSS sends only configuration request

30. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 30 SPD FERO Configuration Database Prototype

31. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 31 SPD FERO Configuration Database Prototype  Data compression based on a fact that most chips within a detector contain the same settings  DAC Template Table – stores typical chip settings  DAC Corrections Table – stores deviations from the Template for every chip Compression factor ~40

32. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 32 SPD Software Developments  First prototype of vertical Slice ready  Connection exists between PVSS and SPD hardware  Updated version of URD is available Please see this document “for inspiration”  Next steps – integration with ECS First prototype expected by the beginning of July 2003

33. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 33 FEE Server (DIM - Server on RCU - Card) PVSS Server (DIM - Server) FEE Client (DIM - Client) InterCom Layer (Application layer) Database Access PVSS Client (DIM - Client) TPC/TRD Software Architecture 2003-06-03, http://www.ztt.fh-worms.de V 1.0 (Darmstadt / Worms)

34. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 34 PVSS DIM Client Comparison of SPD and TPC/TRD Approaches (1) PVSS DIM Client CA1 CA2MA1 SPD Halfstave MCM Router VISA PCI-MXI-VME Database TCP/IP Ethernet RCU master High Level API DIM client DIM server DCS Interface module DDL configuration interface module DDL ? DIM server Aplication Layer Database Data, flags Commands DIM server Commands Data, flags

35. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 35 Comparison of SPD and TPC/TRD Approaches  Both models are very similar  TPC/TRD developments are presently focused on the interface to RCU  SPD software uses VISA to access the hardware  Working meeting preliminary scheduled for July Coordination of developments between SPD and TPC/TRD Integration with ECS

36. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 36 Integration of FED with ECS – FSM Prototype  The aim is to extend the vertical slide up to ECS  Implementation will follow the existing example of HMPID  In the beginning a very simplified model will be used  Detectors are kindly invited to participate in the developments Your feedback is essential

37. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 37 Integration of FED with ECS – FSM Prototype OFF VERY PRELIMINARY !

38. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 38 Integration of FED with ECS – FSM Prototype OFF Not Ready Power is On VERY PRELIMINARY !

39. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 39 Integration of FED with ECS – FSM Prototype OFF Not Ready Ready Configuring Configure Re-Configure Power is On VERY PRELIMINARY !

40. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 40 Integration of FED with ECS – FSM Prototype OFF Not Ready Ready Configuring Calibrating Configure Calibrate Re-Configure Power is On Calibrate VERY PRELIMINARY !

41. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 41 Conclusions (1)  Front-end architectures of all Alice subdetectors can be divided into four categories  Detectors belonging to configuration class “A” might need actions from DCS prior to their configuration These requirements should be documented in URD  Developments of FED software started for SPD and TPC/TRD  Prototype software exists for SPD, next step is its integration with ECS

42. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 42 Conclusions (2)  Big progress has been made towards understanding of detector requirements We wish to thank you all for collaboration  It’s time to update your URD ALICE ACC is happy to provide you with help

43. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 43  In this presentation we mentioned some technologies  Next slides provide a brief overview of VISA and DIM technologies

44. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 44 Virtual Instruments Software Architecture - VISA  VISA is an industrial standard  package for configuring, programming and troubleshoting of instrumentation systems based on GPIB, VXI, PXI, serial (RS232/485), Ethernet, and/or USB interfaces  Provides unified program access to all interfaces  LabWindows, LabView, C, C++, Visual basic interfaces  set of libraries, interactive tools and configuration utilities  Available for Win 9x/Me/NT/2k/XP and Linux Application Code VISA VME PXI VXI GPIB Serial USB Parallel Ethernet

45. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 45 Bundled VISA Tools Test and Measurement Explorer VXI Interactive control VIC - Visa Interactive Control VISA provides Interactive control utilities for ease of development and debugging

46. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 46 DIM – Distributed Information Manager  Communication Package developed at CERN  Based on Client-Server Paradigm  Provides access to information in distributed systems across different platforms  Existing interfaces to several programming languages including C, C++ and Java  Integrated with PVSS

47. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 47 DIM Architecture 1.DIM Server registers its Services and Commands with the Name Server 2.DIM Client requests the list of services from the Name Server 3.Client receives list of services from the Name Server 4.Client subscribes to a service 5.DIM Server updates all subscribed clients (on change or time basis) 6.Client can send commands to server  Name Server provides transparency in distributed environment  Error recovery – all connected processes get information as soon as the crashed process comes back Name Server DIM ServerDIM Client 132 4 5 6

48. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 48 DIM Availability  The package is available at CERN for both Linux and Windows operating systems  For more information see: http://dim.cern.ch/dim

49. ﴀ Peter Chochula 7th ALICE DCS Workshop, June 16, 2003 49 Applications of DIM in ALICE DCS  DIM is preferred method for accessing the FERO  DIM provides an powerful method for interfacing of DCS with “non-standard” devices such as: Home made power supplies Calibration systems, etc.