d etector c ontrol s ystem alice dcs workshop 16-9-2002 g. de cataldo cern-ch, a. franco infn bari,...

ALICE DCS workshop 16-9-2002

G. De Cataldo CERN-CH, A. Franco INFN Bari, I

1

Detector

Control

System

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

• Why FSM?• How do we do it?• The method and a given example• ALICE DCS: the Project

Presentation• Conclusions



2

Detector

Control

System

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 to reduce the number of parameters to be managed

at the Supervisory layer.at the Supervisory layer.

• to integrate in the ALICE DCS the sub-detector C.S. with related hierarchy and partitioning features.

• 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 to reduce the number of parameters to be managed

at the Supervisory layer.at the Supervisory layer.

• to integrate in the ALICE DCS the sub-detector C.S. with related hierarchy and partitioning features.



3

Detector

Control

System

How do we do it ?

TPC DCS

TPC FEE ssTPC HV ss

HMPID DCS

HMPID HV ss

ALICE DCSSMI++ provides tools

to build Device Units,, Control Units, Control Units, DomainsDomains all all behaving as finite state behaving as finite state machinemachine;;

to defineto define the Partitioning the Partitioning mode:mode: IncludedIncluded, ExcludedExcluded,,StandAlone, StandAlone, Command Disabled, , ManualManual andand Ignored;Ignored;

to defineto define the Hierarchy the Hierarchy rules:rules: Exclusive or Shared Exclusive or Shared mode.mode.

http://clara.home.cern.ch/clara/fw/FSMConfig.pdf

PVSS & SMI++ toolkitin the JCOP frameworkPVSS & SMI++ toolkitin the JCOP framework



4

Detector

Control

System

OFF : The HV HMPID is OFF and the PS’s are OFF too

STATES

CONFIG : The relevant parameters are loaded and set in the PVSS Data points, the enabled module goes in STANDBY else in the DISABLED state

STANDBY : The system is ready to power on the enabled HMPID HV segments

RAMPUP : The HV segments are switched ON

READY : The HV sub system is ready for Physics

RAMPDOWN : The HV segments are switched OFF

Standby : It loads the module configuration and it brings the system on the STANDBY status

Transition or Action LIST

HVon : It switch ON all the configured HV channels

HVoff : It switch OFF all the configured HV channels

Off : go to the OFF status.

Reset : To exit from the Error Status

The method and the HMPID as a given example: State and Action

lists

• Set up the requirement list of the HV sub-system;Set up the requirement list of the HV sub-system;• Define the functional states of the system;Define the functional states of the system;• Then provided a graphical representation of the States Then provided a graphical representation of the States

and Transitions: the bubble chart. and Transitions: the bubble chart.

• Set up the requirement list of the HV sub-system;Set up the requirement list of the HV sub-system;• Define the functional states of the system;Define the functional states of the system;• Then provided a graphical representation of the States Then provided a graphical representation of the States

and Transitions: the bubble chart. and Transitions: the bubble chart.

The State diagram of the HV Subsys.



5

Detector

Control

System

HVPS 1HVPS 1

HVm 7HVm 7HVm 6HVm 6



HVm 1HVm 1

High VoltageC.U. Domain

(c.prg SMI++)

High VoltageC.U. Domain

(c.prg SMI++)

Low voltageC.U Domain. Low voltageC.U Domain.

Gas Distrib.C.U.DomainGas Distrib.C.U.Domain

C6F14 rec.C.U. DomainC6F14 rec.

C.U. DomainCooling

C.U. DomainCooling

C.U. Domain

Device Units LCModulLCModulLCMainLCMain?? ?? ??

HMPID Control Unit

Domain

HMPID Control Unit

Domain

Hierarchy: Exclusive or Shared mode

MainUser

hardwareExpert

Hierarchical representation of the HMPID C.S.

This representation and functionality comes once the SMI++toolkit is adopted to build the C.S..

IncludedIncluded, ExcludedExcluded,,StandAloneStandAlone, , Command Disabled, , ManualManual andand Ignored;Ignored;

7 HMPID Modules



6

Detector

Control

System

FSM DP

FSM Device Units

HVm2FSM DP

FSM Device Units

HVm2

CAEN SY1527HV Channels

Frameworkdevice DPs

DCOM/OPCconnection

HV SubSystemControl Unit

Domain

HV SubSystemControl Unit

Domain

FSM DP

FSM Device Units

HVm1

InterfaceProgram

The HVm.. Device Unit : a tailored The HVm.. Device Unit : a tailored interface to the hardwareinterface to the hardware

• All the parameters and variable of the CAEN All the parameters and variable of the CAEN SY1527 Crate are linked, by OPC server SY1527 Crate are linked, by OPC server technology, to a set of PVSS DataPoint by technology, to a set of PVSS DataPoint by means of the Framework configuration means of the Framework configuration facilitiesfacilities

• Some DataPoint are defined as Logical Some DataPoint are defined as Logical Device, one for the HV Power Supply Station Device, one for the HV Power Supply Station and 7 for the HV Modules, they will became and 7 for the HV Modules, they will became the interface point for the FSM Device Unitthe interface point for the FSM Device Unit

• For each Device Unit an associated FSM has For each Device Unit an associated FSM has been defined using the FSM-Framework toolsbeen defined using the FSM-Framework tools

• An High Voltage Control Unit Domain and the An High Voltage Control Unit Domain and the relative SMI++ control program has been relative SMI++ control program has been createdcreated

A devoted Interface Control Scripts Program A devoted Interface Control Scripts Program is requested to convert, all the information is requested to convert, all the information coming from the SY1527 (board included), in coming from the SY1527 (board included), in logical objects (Device Unit) behaving as logical objects (Device Unit) behaving as FSM’s … FSM’s …

• All the parameters and variable of the CAEN All the parameters and variable of the CAEN SY1527 Crate are linked, by OPC server SY1527 Crate are linked, by OPC server technology, to a set of PVSS DataPoint by technology, to a set of PVSS DataPoint by means of the Framework configuration means of the Framework configuration facilitiesfacilities

• Some DataPoint are defined as Logical Some DataPoint are defined as Logical Device, one for the HV Power Supply Station Device, one for the HV Power Supply Station and 7 for the HV Modules, they will became and 7 for the HV Modules, they will became the interface point for the FSM Device Unitthe interface point for the FSM Device Unit

• For each Device Unit an associated FSM has For each Device Unit an associated FSM has been defined using the FSM-Framework toolsbeen defined using the FSM-Framework tools

• An High Voltage Control Unit Domain and the An High Voltage Control Unit Domain and the relative SMI++ control program has been relative SMI++ control program has been createdcreated

A devoted Interface Control Scripts Program A devoted Interface Control Scripts Program is requested to convert, all the information is requested to convert, all the information coming from the SY1527 (board included), in coming from the SY1527 (board included), in logical objects (Device Unit) behaving as logical objects (Device Unit) behaving as FSM’s … FSM’s …



7

Detector

Control

System

HVm1 [hmpidHVM]

HVm1 [hmpidHVM]

HVm1 [hmpidHVM]

HVm1 [hmpidHVM]

HVm1 [hmpidHVM]

HVm1 [hmpidHVM]

Primo_board01_ch01 [FwCaenChannel]






Primo_board01 [FwCaen1527Board]




1 CAEN SY1527 crate

1 CAEN SY1527 crate

5 CAEN A1821 boards

5 CAEN A1821 boards

49 CAEN HV channels

49 CAEN HV channels

HV Power Supply

HV Power Supply

HV Module 3HV Module 3







PhysicalDevices

FSMDevice Units

Primo [FwSy1527]



HVpa1 [hmpidHVPS]

HVm1 [hmpidHVM]

Jasd j i= 0If(kjsad) asd asdaJkd askd aksd kaksd asAsdas asd

Jasd j i= 0If(kjsad) asd asdaJkd askd aksd kaksd asAsdas asd

Event firedby values changes

Change of Device Status

Event fired by Request Action Command

to Devices

The Interface Control Script The Interface Control Script ProgramProgram1.1. When the Domain Control Program send an action (command) to a FSM When the Domain Control Program send an action (command) to a FSM

Device Unit, the related DataPoint values changes.Device Unit, the related DataPoint values changes.

2.2. This results in the execution of a subroutine that according to the This results in the execution of a subroutine that according to the command received modify all the related DataPoint configuration.command received modify all the related DataPoint configuration.

1.1. When the Domain Control Program send an action (command) to a FSM When the Domain Control Program send an action (command) to a FSM Device Unit, the related DataPoint values changes.Device Unit, the related DataPoint values changes.

2.2. This results in the execution of a subroutine that according to the This results in the execution of a subroutine that according to the command received modify all the related DataPoint configuration.command received modify all the related DataPoint configuration.

1.1. When a parameter value of the Physical Device undergo changing, then When a parameter value of the Physical Device undergo changing, then the corresponding DataPoint config value changes.the corresponding DataPoint config value changes.

2.2. This starts a subroutine that according to new value may bring the This starts a subroutine that according to new value may bring the related FSM D.U. in the new related FSM D.U. in the new state.state.

1.1. When a parameter value of the Physical Device undergo changing, then When a parameter value of the Physical Device undergo changing, then the corresponding DataPoint config value changes.the corresponding DataPoint config value changes.

2.2. This starts a subroutine that according to new value may bring the This starts a subroutine that according to new value may bring the related FSM D.U. in the new related FSM D.U. in the new state.state.



8

Detector

Control

System

HV Control Unit: session snapshotHV Control Unit: session snapshot

An example of HV Sub An example of HV Sub System RAMPUP phase:System RAMPUP phase:

The control panel The control panel opened opened from the Device Editor & from the Device Editor & Navigator Navigator has taken the has taken the control of the HV sub-control of the HV sub-system, as shown in the system, as shown in the FSM-Framework panel FSM-Framework panel .

The intermediate RAMPUP The intermediate RAMPUP statestate is reached just after is reached just after the the HVonHVon command is send command is send to the Control Unit.to the Control Unit.

The telnet section The telnet section on the on the SY1527 crate gives a real SY1527 crate gives a real time feedback.time feedback.

The Power Supply Unit is in The Power Supply Unit is in READY READY statestate during all the during all the operations. The modules operations. The modules from 2 to 7 are disabled from 2 to 7 are disabled

An example of HV Sub An example of HV Sub System RAMPUP phase:System RAMPUP phase:

The control panel The control panel opened opened from the Device Editor & from the Device Editor & Navigator Navigator has taken the has taken the control of the HV sub-control of the HV sub-system, as shown in the system, as shown in the FSM-Framework panel FSM-Framework panel .

The intermediate RAMPUP The intermediate RAMPUP statestate is reached just after is reached just after the the HVonHVon command is send command is send to the Control Unit.to the Control Unit.

The telnet section The telnet section on the on the SY1527 crate gives a real SY1527 crate gives a real time feedback.time feedback.

The Power Supply Unit is in The Power Supply Unit is in READY READY statestate during all the during all the operations. The modules operations. The modules from 2 to 7 are disabled from 2 to 7 are disabled

13

22

4

5



9

Detector

Control

System

HMPID Control Panel: HMPID Control Panel: the Graphic User Interfacethe Graphic User Interface



10

Detector

Control

System

Working with the SMI++ toolkit

HVPS 1HVPS 1




HVm 1HVm 1

High VoltageC.U. DomainHigh VoltageC.U. Domain

hardware Config. Panel for Device Type

Config. Panel for Device Type

Configuring Hierarchy of FSMConfiguring Hierarchy of FSM

Configuring FSM Domains. Configuring FSM Domains. It is relevant for Patitioning purposesIt is relevant for Patitioning purposes

Config. Panel for Logical Object type

Config. Panel for Logical Object type

Control Unit definitionControl Unit definition



11

Detector

Control

System

Experimentparameters

set #1


set #1

External Data Base for theExternal Data Base for theHMPID ConfigurationHMPID Configuration

Configuration DBConfiguration DB


set #1 Name1 ValueName2 Value

DictionaryName1 DP1

In order to have a centralized In order to have a centralized repository of the Detector repository of the Detector Configurations a D.B. , external to Configurations a D.B. , external to the PVSS environment, has been the PVSS environment, has been created.created.

Store a ConfigurationStore a Configuration: the HMPID : the HMPID config. parameters are stored in the config. parameters are stored in the external DB as a list of doublets external DB as a list of doublets (Name,Value) where the name is the (Name,Value) where the name is the symbolic name of a parameter given by symbolic name of a parameter given by the user.the user.

Load a ConfigurationLoad a Configuration:according to a :according to a Dictionary, each doublet (Name,Value) Dictionary, each doublet (Name,Value) in the Config. D.B. is converted in the in the Config. D.B. is converted in the corresponding doublet (DataPoint, corresponding doublet (DataPoint, Value) in the PVSS environment (Value) in the PVSS environment (DP Value)..

In order to have a centralized In order to have a centralized repository of the Detector repository of the Detector Configurations a D.B. , external to Configurations a D.B. , external to the PVSS environment, has been the PVSS environment, has been created.created.

Store a ConfigurationStore a Configuration: the HMPID : the HMPID config. parameters are stored in the config. parameters are stored in the external DB as a list of doublets external DB as a list of doublets (Name,Value) where the name is the (Name,Value) where the name is the symbolic name of a parameter given by symbolic name of a parameter given by the user.the user.

Load a ConfigurationLoad a Configuration:according to a :according to a Dictionary, each doublet (Name,Value) Dictionary, each doublet (Name,Value) in the Config. D.B. is converted in the in the Config. D.B. is converted in the corresponding doublet (DataPoint, corresponding doublet (DataPoint, Value) in the PVSS environment (Value) in the PVSS environment (DP Value)..

PVSS DBPVSS DB

DP1 Value

- Symbolic NameSymbolic Name DefinitionDefinition : a custom panel in the FW allows the definition of the Symbolic Name into : a custom panel in the FW allows the definition of the Symbolic Name into the Dictionary.the Dictionary.

- Store a configurationStore a configuration: a control script program is able to record, in the Configuration DB, the actual : 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”.HMPID configuration parameters present in the PVSS Data Base. This is a “detector snapshot”.

- Load a configurationLoad a configuration: a control script program reads from the config. DB all the parameter values : 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 requested for the “detector configuration” and according to the Dictionary writes them in the PVSS Data Point Elements.Point Elements.

- Symbolic NameSymbolic Name DefinitionDefinition : a custom panel in the FW allows the definition of the Symbolic Name into : a custom panel in the FW allows the definition of the Symbolic Name into the Dictionary.the Dictionary.

- Store a configurationStore a configuration: a control script program is able to record, in the Configuration DB, the actual : 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”.HMPID configuration parameters present in the PVSS Data Base. This is a “detector snapshot”.

- Load a configurationLoad a configuration: a control script program reads from the config. DB all the parameter values : 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 requested for the “detector configuration” and according to the Dictionary writes them in the PVSS Data Point Elements.Point Elements.

322

1

Control Script

Control Script



12

Detector

Control

System

Dictionary and Management of the Dictionary and Management of the External D.B. External D.B.

Configuration panel to create the Dictionary entries. Definition of a complex symbolic name..

Configuration panel to create the Dictionary entries. Definition of a complex symbolic name..

The Load/Store Configuration Setting panel.

The Load/Store Configuration Setting panel.



13

Detector

Control

System What About the ALICE DCS ?Taking profit of the expertise developed Taking profit of the expertise developed so far while implementing the HMPID C.S.so far while implementing the HMPID C.S. (PVSS, SMI++ toolkit and external config. D.B.),(PVSS, SMI++ toolkit and external config. D.B.), we we are going to start the designing and are going to start the designing and implementation of the first prototype of implementation of the first prototype of ALICE DCS.ALICE DCS.

Taking profit of the expertise developed Taking profit of the expertise developed so far while implementing the HMPID C.S.so far while implementing the HMPID C.S. (PVSS, SMI++ toolkit and external config. D.B.),(PVSS, SMI++ toolkit and external config. D.B.), we we are going to start the designing and are going to start the designing and implementation of the first prototype of implementation of the first prototype of ALICE DCS.ALICE DCS.

TRD DCSTRD DCSITS DCSITS DCSTPC DCSTPC DCSHMPID DCSHMPID DCS

ALICE DCSALICE DCS

TOF DCSTOF DCS



14

Detector

Control

System

ALICE DCS:Project Presentation

•Integration of all the HMPID Subsystem Controls as FSM;

•Access extension Access extension ((PostgreeSQL and MySQL) and improving of the external Data Base for the proving of the external Data Base for the HMPID configurations;HMPID configurations;

•Integration of the HMPID C.S. in the first Integration of the HMPID C.S. in the first prototype of the ALICE DCS;prototype of the ALICE DCS;

•Subsequently, integration in the ALICE DCS Subsequently, integration in the ALICE DCS of a new sub-detector C.S..of a new sub-detector C.S..

•Integration of all the HMPID Subsystem Controls as FSM;

•Access extension Access extension ((PostgreeSQL and MySQL) and improving of the external Data Base for the proving of the external Data Base for the HMPID configurations;HMPID configurations;

•Integration of the HMPID C.S. in the first Integration of the HMPID C.S. in the first prototype of the ALICE DCS;prototype of the ALICE DCS;

•Subsequently, integration in the ALICE DCS Subsequently, integration in the ALICE DCS of a new sub-detector C.S..of a new sub-detector C.S..



15

Detector

Control

System

Conclusions

• At level of HMPID C.S. the PVSS+SMI++ toolkit At level of HMPID C.S. the PVSS+SMI++ toolkit (avail. In the JCOP F.W.)(avail. In the JCOP F.W.) has proven to be effective, then has proven to be effective, then we intend to extended this approach to the we intend to extended this approach to the implementation of the ALICE DCS implementation of the ALICE DCS (http://clara.home.cern.ch/clara/fw/FSMConfig.pdf) ,

• To be homogeneous, all the subdetector C.S To be homogeneous, all the subdetector C.S should adopt the same FSM approach: the should adopt the same FSM approach: the common project; common project;

• Development activities for the first ALICE DCS Development activities for the first ALICE DCS prototype are now on the way;prototype are now on the way;

• The Alice Control Co-ordination Team and HMPID The Alice Control Co-ordination Team and HMPID expertise are available to provide informationexpertise are available to provide information

• At level of HMPID C.S. the PVSS+SMI++ toolkit At level of HMPID C.S. the PVSS+SMI++ toolkit (avail. In the JCOP F.W.)(avail. In the JCOP F.W.) has proven to be effective, then has proven to be effective, then we intend to extended this approach to the we intend to extended this approach to the implementation of the ALICE DCS implementation of the ALICE DCS (http://clara.home.cern.ch/clara/fw/FSMConfig.pdf) ,

• To be homogeneous, all the subdetector C.S To be homogeneous, all the subdetector C.S should adopt the same FSM approach: the should adopt the same FSM approach: the common project; common project;

• Development activities for the first ALICE DCS Development activities for the first ALICE DCS prototype are now on the way;prototype are now on the way;

• The Alice Control Co-ordination Team and HMPID The Alice Control Co-ordination Team and HMPID expertise are available to provide informationexpertise are available to provide information

d etector c ontrol s ystem alice dcs workshop 16-9-2002 g. de cataldo cern-ch, a. franco infn bari,...

Documents