Presentation is loading. Please wait.

Presentation is loading. Please wait.

Slow Control LHCf Catania Meeting - July 04-06, 2009 Lorenzo Bonechi.

Similar presentations


Presentation on theme: "Slow Control LHCf Catania Meeting - July 04-06, 2009 Lorenzo Bonechi."— Presentation transcript:

1 Slow Control LHCf Catania Meeting - July 04-06, 2009 Lorenzo Bonechi

2 Summary of status Main part is already prepared Everything is stored in the Catania Subversion repository and accessible with a very complicated username and password… Text based server C/C++ classes for management of devices: – Agilent LV: Lorenzo – CAEN LV/HV and ADCs – Encoders/Manipulator – TRHX and Silicon FEC: Andrea Text based client and monitor Graphical client and monitor DIP handshake

3 LHCf Slow Control Server (SCS) Main implemented tasks Defines the directory and files where SC data and information are stored – Three files: textual data file (only for fast check), binary data file, log file Call initialization routines for all managed devices Creates two timers for repeating some actions regularly in time – T1: read parameters from devices and check their status – T2: write data on files Creates the socket for managing client connections: – Able to allow multiple clients to connect – For each client starts a thread where translation of client’s commands is performed and instructions are sent to the devices Defines the mutexes, variables to access resources in a safe way Basic DIP handshake

4 LHCf Slow Control: THREADS Why threads!?!? Threads are not processes, but parts of the same process: the same routine is replicated and all copies run independently They can share some resources while different processes don’t (in particular they share the same allocated memory and therefore they can access to the same variables) What do they do for the LHCf SCS? One thread is used to communicate only with the client that triggered it. It receive client’s commands through the network, decode and execute them (commands to be sent to devices / requests of help by users / safety rules etc.) They share the memory where data and variables are stored

5 LHCf SCS: screenshot

6 SCS – Things still to be done A tentative summary Understand if/how to take some automatic decision if a subsystem fails Automatic installation method: definition of directories and files Define trusted PCs for client connections (to avoid unwanted accesses) Correct the TRHX class (for temperature monitoring) Maybe correct also the ENCODER classes in such a way not to freeze a client when running the “move” command (actually we can bypass this problem by opening another client and sending the “stop” command) Check and complete the help file with some parts and maybe modify the help behavior to be more efficient Define all the necessary “procedures” (safe sequences of commands to be launched by the standard user)

7 Text-based Slow Control Client (SCC) Main implemented tasks Manage getting commands by the users and sending them to the SCS through a shell-like textual interface which integrate command history, shell command execution and other beautiful things Return to the user some output produced by the SCS Manage password definition for expert users on the PC where it run and the identification of standard or expert users Can enter monitoring mode where: – Monitor for each sub-system can be enabled/disabled pressing a key – Information is updated every second and shown with simple formatting – A color map helps checking for problems (maybe sound could be also useful, but I tried and I was not so happy, so I removed; we can add again).

8 Some SCC screenshots

9 The SCC help

10 Help: list of commands

11 Help: list of procedures

12 Detailed help on commands and procedures NAME DESCRIPTION

13 Some SCC screenshots

14 Text-based monitor

15 Graphical Client Can perform the same operations of text- based client(obvious) Include beautiful graphical monitor for all relevant parameters (voltages and temperatures) Sorry, I had no time to prepare some nice figure

16 Connection to the DIP system Exchange of information between the LHC machine and all the experiments We need to know the status of the beams and machine operations before going into the data taking configuration  handshake with the DIP (read beam status and answer with appropriate answers) LHC need also to know the centre of the particle distribution detected by LHCf and the intensity to optimize the machine parameters and maximize the interaction between the beams  this part is included in the online analysis

17 Slow Control scheme Slow Control Server S.C. CLIENT THREAD request connection accept read/set send cmd and read data Silicon Front End Slow Control Server send cmd Devices: 1)CPWS1 LV/HV 2)CPWS2 LV/HV 3)AGILENT LV 4)ADCs 5)MANIPULATORS 6)TRHX (t-sensors) DIP Client DIP Server Online Analysis lhcfmon1.cern.ch request connection LHC Files read/set


Download ppt "Slow Control LHCf Catania Meeting - July 04-06, 2009 Lorenzo Bonechi."

Similar presentations


Ads by Google