1 / 15

Finite State Machines (FSM) for the ALICE DCS: a common project

Finite State Machines (FSM) for the ALICE DCS: a common project. Why FSM? How do we do it? The method and a given example ALICE DCS: the Project Presentation Conclusions. Why FSM?. For both ALICE and the sub-detector’s C.S. the FSM approach allows for:

dinh
Download Presentation

Finite State Machines (FSM) for the ALICE DCS: a common project

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. Finite State Machines (FSM) for theALICE DCS: a common project • Why FSM? • How do we do it? • The method and a given example • ALICE DCS: the Project Presentation • Conclusions G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  2. Why FSM? • For both ALICE and the sub-detector’s C.S. the FSM approach allows for: • to develop the the Sub-Detector controls in a standard way; • to reduce the number of parameters to be managed at the Supervisory layer. • to integrate in the ALICE DCS the sub-detector C.S. with related hierarchy and partitioning features. G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  3. PVSS & SMI++ toolkit in the JCOP framework http://clara.home.cern.ch/clara/fw/FSMConfig.pdf How do we do it ? SMI++ provides tools to buildDevice Units,Control Units, Domainsall behaving as finite state machine; to define the Partitioning mode:Included, Excluded,StandAlone, Command Disabled, ManualandIgnored; to define the Hierarchy rules:Exclusive or Shared mode. ALICE DCS TPC DCS HMPID DCS TPC HV ss TPC FEE ss HMPID HV ss G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  4. The method and the HMPID as a given example: State and Action lists STATES The State diagram of the HV Subsys. Transition or Action LIST OFF : The HV HMPID is OFF and the PS’s are OFF too Standby : Itloads the module configuration and it brings the system on the STANDBY status CONFIG: The relevant parameters are loaded and set in the PVSS Data points, the enabled module goes in STANDBY else in the DISABLED state HVon : It switch ON all the configured HV channels HVoff : It switch OFF all the configured HV channels STANDBY : The system is ready to power on the enabled HMPID HV segments Reset : To exit from the Error Status Off : go to the OFF status. RAMPUP : TheHV segments are switched ON READY : The HV sub system is ready for Physics RAMPDOWN : The HV segments are switched OFF • Set up the requirement list of the HV sub-system; • Define the functional states of the system; • Then provided a graphical representation of the States and Transitions: the bubble chart. G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  5. Hierarchy: Exclusive or Shared mode MainUser Expert Hierarchical representation of the HMPID C.S. This representation and functionality comes once the SMI++toolkit is adopted to build the C.S.. Included, Excluded, StandAlone, Command Disabled, ManualandIgnored; HMPID Control Unit Domain Cooling C.U.Domain Low voltage C.U Domain. Gas Distrib. C.U.Domain C6F14 rec. C.U. Domain High Voltage C.U. Domain (c.prg SMI++) ? ? LCMain LCModul HVPS 1 ? HVm 1 HVm 2 Device Units HVm 3 HVm 4 7 HMPID Modules HVm 5 HVm 6 hardware HVm 7 G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  6. FSM Device Units FSM Device Units FSM Device Units FSM DP FSM DP FSM DP HVm2 HVm1 HVm2 HV Channels The HVm.. Device Unit : a tailored interface to the hardware HV SubSystem Control Unit Domain • All the parameters and variable of the CAEN SY1527 Crate are linked, by OPC server technology, to a set of PVSS DataPoint by means of the Framework configuration facilities • Some DataPoint are defined as Logical Device, one for the HV Power Supply Station and 7 for the HV Modules, they will became the interface point for the FSM Device Unit • For each Device Unit an associated FSM has been defined using the FSM-Framework tools • An High Voltage Control Unit Domain and the relative SMI++ control program has been created • A devoted Interface Control Scripts Program is requested to convert, all the information coming from the SY1527 (board included), in logical objects (Device Unit) behaving as FSM’s …  Interface Program Framework device DPs DCOM/OPC connection CAEN SY1527 G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  7. The Interface Control Script Program • When the Domain Control Program send an action (command) to a FSM Device Unit, the related DataPoint values changes. • This results in the execution of a subroutine that according to the command received modify all the related DataPoint configuration. Physical Devices FSM Device Units Event fired by Request Action Command to Devices Jasd j i= 0 If(kjsad) asd asda Jkd askd aksd kaksd as Asdas asd 1 CAEN SY1527 crate Primo [FwSy1527] HVpa1 [hmpidHVPS] HV Power Supply 5 CAEN A1821 boards Primo_board01 [FwCaen1527Board] HV Module 1 Primo_board01 [FwCaen1527Board] Primo_board01 [FwCaen1527Board] Primo_board01 [FwCaen1527Board] Primo_board01 [FwCaen1527Board] HV Module 2 Jasd j i= 0 If(kjsad) asd asda Jkd askd aksd kaksd as Asdas asd 49 CAEN HV channels Primo_board01_ch01 [FwCaenChannel] Primo_board01_ch01 [FwCaenChannel] Primo_board01_ch01 [FwCaenChannel] Primo_board01_ch01 [FwCaenChannel] HVm1 [hmpidHVM] HV Module 3 Primo_board01_ch01 [FwCaenChannel] HVm1 [hmpidHVM] Primo_board01_ch01 [FwCaenChannel] HVm1 [hmpidHVM] Primo_board01_ch01 [FwCaenChannel] HVm1 [hmpidHVM] HVm1 [hmpidHVM] HVm1 [hmpidHVM] HVm1 [hmpidHVM] HV Module 4 Change of Device Status Event fired by values changes HV Module 5 HV Module 6 • When a parameter value of the Physical Device undergo changing, then the corresponding DataPoint config value changes. • This starts a subroutine that according to new value may bring the related FSM D.U. in the new state. HV Module 7 G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  8. HV Control Unit: session snapshot An example of HV Sub System RAMPUP phase: The control panel  opened from the Device Editor & Navigator  has taken the control of the HV sub-system, as shown in the FSM-Framework panel . The intermediate RAMPUP state is reached just after the HVon command is send to the Control Unit. The telnet section  on the SY1527 crate gives a real time feedback. The Power Supply Unit is in READY state during all the operations. The modules from 2 to 7 are disabled  2 1 3 5 4 G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  9. HMPID Control Panel: the Graphic User Interface G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  10. Configuring Hierarchy of FSM High Voltage C.U. Domain HVPS 1 HVm 1 HVm 2 HVm 3 HVm 4 HVm 5 HVm 6 hardware HVm 7 Working with the SMI++ toolkit Configuring FSM Domains. It is relevant for Patitioning purposes Control Unit definition Config. Panel for Device Type Config. Panel for Logical Object type G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  11. External Data Base for the HMPID Configuration 1 In order to have a centralized repository of the Detector Configurations a D.B. , external to the PVSS environment, has been created. Store a Configuration: the HMPID config. parameters are stored in the external DB as a list of doublets (Name,Value) where the name is the symbolic name of a parameter given by the user. Load a Configuration:according to a Dictionary, each doublet (Name,Value) in the Config. D.B. is converted in the corresponding doublet (DataPoint, Value) in the PVSS environment (DP  Value). Configuration DB PVSS DB Experiment parameters set #1 Experiment parameters set #1 Experiment parameters set #1 Name1Value Name2Value Dictionary Name1 DP1 DP1 Value Control Script 3 2 Control Script • Symbolic NameDefinition : a custom panel in the FW allows the definition of the Symbolic Name into the Dictionary. • Store a configuration: a control script program is able to record, in the Configuration DB, the actual HMPID configuration parameters present in the PVSS Data Base. This is a “detector snapshot”. • Load a configuration: a control script program reads from the config. DB all the parameter values requested for the “detector configuration” and according to the Dictionary writes them in the PVSS Data Point Elements. G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  12. Dictionary and Management of the External D.B. Configuration panel to create the Dictionary entries. Definition of a complex symbolic name. The Load/Store Configuration Setting panel. G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  13. What About the ALICE DCS ? Taking profit of the expertise developed so far while implementing the HMPID C.S.(PVSS, SMI++ toolkit and external config. D.B.),we are going to start the designing and implementation of the first prototype of ALICE DCS. ALICE DCS ITS DCS TRD DCS TPC DCS TOF DCS HMPID DCS G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  14. ALICE DCS:Project Presentation • Integration of all the HMPID Subsystem Controls as FSM; • Access extension (PostgreeSQL and MySQL) and improving of the external Data Base for the HMPID configurations; • Integration of the HMPID C.S. in the first prototype of the ALICE DCS; • Subsequently, integration in the ALICE DCS of a new sub-detector C.S.. G. De Cataldo CERN-CH, A. Franco INFN Bari, I

  15. Conclusions • At level of HMPID C.S. the PVSS+SMI++ toolkit (avail. In the JCOP F.W.) has proven to be effective, then we intend to extended this approach to the implementation of the ALICE DCS (http://clara.home.cern.ch/clara/fw/FSMConfig.pdf), • To be homogeneous, all the subdetector C.S should adopt the same FSM approach: the common project; • Development activities for the first ALICE DCS prototype are now on the way; • The Alice Control Co-ordination Team and HMPID expertise are available to provide information G. De Cataldo CERN-CH, A. Franco INFN Bari, I

More Related