1. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari1 Common FSM’s updates An exercise to design the standard FSMs for the DCS, the HV and the LV for a generic sub-detector in ALICE playing with: 1. the DCS hierarchy, 2. the state summary tables and 3. the state diagrams. Contribution: A. Franco, INFN Bari U. Frankenfeld (TPC DCS),

2. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari2 An example of sub-detector DCS hierarchy for the exercise SMI Control Unit SMI Device Unit Hardware Device Work in progress Testing HVPS1 HV PS GAS Phis. Param. LV PS LVPS14FEEMod 1 LVPS1 HVLV/FEE GAS PLC P,T sensors SBD DCS PLC LCS & FSM LCS COOL Cooling System BEAM? SCRIPT INTERF. CONFIG HVMod 1 HV chsLV chs CF DB

3. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari3 The summary table for the DCS-HV states Warnings Keeping in mind the DCS hierarchy the table has to be read from right to left ( propagation of the STATE changing ); The corresponding command list is reported in the followings HV state diagrams (see later); If the cell of the empty column between DCS and HV system is white then the HV system STATE must not be propagated at the DCS level; In case of automatic recovering the MIXED state in the HV SYSTEM resolve the HV MODULE OFF ambiguity jumping in STANDBY. MIXED is active when not all the controlled channels are in same stable state ; In this hierarchy the HV Module can control many HV channels and the HV SYSTEM can control many HV Modules; The state naming is not yet final (the blue NOT_READY in the yellow MIXED ? STBY_CONFIGURED in CONFIGURED?) and the table may not be exhaustive: working in progress!

4. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari4 READY GO_STANDBY CONFIGURE (key) BEAM_FILLING GO_READY STBY_CONFIGURED INTERMEDIATE PROGRESSING_DW_INTER PROGRESSING_DW PROGRESSING_ PROGRESSING_UP CONFIGURE (key) STOP GO_READY STOP BEAM_FILLING STANDBY OFF DOWNLOADING GO_OFF CONFIGURE (keys) DOWNLOADING State diagram for the Detector DCS GO_STANDBY Additional diagrams: B,C,D. (see later)

5. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari5 ON GO_STANDBY CONFIGURE (key) GO_INTERMETIATE GO_ON STBY_CONFIGURED INTERMEDIATE RAMP_DOWN RAMP_DOWN_LOW RAMP_UP RAMP_UP_LOW CONFIGURE (key) STOP GO_ON STOP GO_INTERMEDIATE STANDBY OFF DOWNLOADING GO_OFF CONFIGURE (keys) DOWNLOADING State diagram for the HV system and channel group GO_STANDBY Additional diagrams: A,B,C,D,E,F. (see later)

6. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari6 ON GO_INTERMETIATE GO_ON OFF INTERMEDIATE RAMP_DOWN RAMP_DOWN_LOW RAMP_UP RAMP_UP_LOW GO_OFF GO_ON GO_OFF GO_INTERMEDIATE State diagram for the single HV channel (special DU) Additional diagrams: A,B,C. (see later) On the GO_ON, GO_INTERMEDIATE and GO_OFF commands the DU provides the downloading in the hardware of the corresponding set of recipes value.

7. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari7 OFF GO_OFF RESET GO_READY ON Network connection lost INTERLOCK_WENT Active lines on External Interlock and External disable RECOVER_INTERLOCK State diagram for the HV(LV) power supply NO_CONTROL Power Crate unsafe Conditions, Kill command RECOVER ERROR INTERLOCK The connection between NO_CONTROL and OFF is valid if the remote control of the power supply is on also when the PS is switched off. Additional diagrams: A,B,C,D. (see later)

8. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari8 The summary tables for the DCS-LV states Warnings: as for the HV table

9. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari9 ON GO_STANDBY CONFIGURE (key) GO_ON STBY_CONFIGURED RAMP_DOWN RAMP_UP STOP STANDBY OFF DOWNLOADING GO_OFF CONFIGURE (keys) State diagram for the LV system and channel group GO_STANDBY Additional diagrams: A,B,C,D,E,F. (see later) In order to take into account the delays in swapping the different recipes sets in the channel, the RAMP_UP and RAMP_DOWN states are needed.

10. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari10 ON GO_INTERMETIATE GO_ON OFF RAMP_DOWNRAMP_UP GO_OFF GO_INTERMEDIATE State diagram for the single LV channel Additional diagrams: A,B,C. (see later)

11. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari11 One or several tripped channels in a channel group Recovering actions WA_REPAIR NO_CONTROL When the communication is established #trips ≥ Max? A Go to the appropriate state From any state if the communication with the hardware is lost Go to the appropriate state When several modules in ER_REPAIR, or External Interlock, or power crate failure, un-calibrated board. ERROR RECOVER Go to OFF ER_REPAIR Go to the appropriate state Recovering actions Yes No BC RECOVER_INTERLOCK INTERLOCK_WENT D It is the propagation of the interlock condition in HVPS1 INTERLOCK Go to OFF The ‘ADDITIONAL diagrams ’: ERROR HANDLING (E,F in the next page!) In the state diagram of the power supply the ADDITIONAL A refers to a failure of a certain number of fans or AC modules in the crate that do not prevent the HV power supply to work properly;

12. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari12 When all channels are in the same stable state MIXED E From any state when not all the channels or systems are in the same state Go to the appropriate state When all the systems are in a stable state PROGRESSING_UP (DOWN) F From any state when not all the channels or systems are in a stable state Go to the appropriate state The ‘ADDITIONAL diagrams II’: the COMPLEMENTARY STATE

13. DCS workshop 13-14/6/2005G. De Cataldo, CERN-CH and INFN bari13Conclusion 1.For the DCS, the HV, and the LV systems the ACC is trying to provide reference FSM hierarchies along with their standard state diagrams. All the sub-detector control expert are kindly requested to verify if these state diagrams fits with the sub-detector operation and give feedback to the ACC. 2.In order to integrate in the DCS any different system with a synchronized FSM, each control expert could do the same exercise: Starting from the system operation design the corresponding FSM hierarchy using the Device and Control Unit (SMI++ object that can be implemented in the PVSS FW); Starting from the DU interfacing the hardware, try to synchronize the state list up to the DCS level using the state summary table; Draw the corresponding state diagram with a detailed command list. 3.For any question please do not hesitate to contact me