1. Pierluigi Paolucci & Giovanni Polese
RPC DCS INTEGRATION
STATUS
Pierluigi Paolucci & Giovanni Polese
I.N.F.N. of Naples
cms.na.infn.it
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

2. P. Paolucci & G. Polese - INFN di Napoli
INTEGRATION STATUS
First, create a hardware and a logical views of your detector system using the framework device editor & navigator.
Design a hierarchical structure that allows detector logical partitions and hardware partitions.
Identify your partitions and the smallest unit you want to model as a supervisor control unit. This unit should have meaning in terms of your different subsystems.
Follow the naming conventions from the very begin.
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

3. P. Paolucci & G. Polese - INFN di Napoli
INTEGRATION STATUS
Define the states and commands of your devices trying to reduce the as much as possible the number of them. ON, OFF, ERROR, STANDBY, RAMPING UP, RAMPING DOWN… If exists, use the framework standard for your device.
Summarize the states of your device units with the control units. At the level of the supervisor control tree the list should be small, typically: ON, OFF, STANDBY ,ERROR
When you start creating the fsm nodes and fsm node types, use the naming convention from the very beginning. Renaming sometimes is very painful
Create a ‘cms_detector’ folder inside the panels folder to store ALL your panels (same for pictures). “project_folder/panels/cms_detector/”
DISCUSS
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

4. P. Paolucci & G. Polese - INFN di Napoli
INTEGRATION STATUS
Place a global variable in front of all your dp references in panel, libs or scripts. This variable will be filled with the appropriate system name. This way all the fsm panel will be accessible from the whole pvss systems.
Use the configuration DB tool to store your different running modes and device parameters.
Create your project as an installable component. The new framework installation tool provides functionality for this purpose.
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

5. P. Paolucci & G. Polese - INFN di Napoli
FSM TOPNODE
RESET ON
OFF
CONFIGURE
CONFIGURE
GOTO_STB
STANDBY
GOTO_STB
RESET
ERROR
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

6. STANDBY STATUS ONLY TOP NODE HAVE A STANDBY STATUS
USE A INVISIBLE DEVICE TO LOAD DIFFERENT CONFIGURATION FROM DATABASE
DCS Node
(Root)
STATES:ON,OFF,ERROR,STANDBY
ACTIONS:CONFIGURE,RESET,GOTO_STB,RECOVER
Device standBy
IF (TOPNODE->CONFIGURE)
LOAD FROM DB CONFIGURE RECIPE
ELSE IF (TOPNODE ->RESET)
LOAD FROM DB RESET RECIPE
ELSE IF (TOPNODE->GOTO_STB)
LOAD FROM DB STANDBY RECIPE
Wheel P2
Wheel P2
STATES:ON,OFF,ERROR
ACTIONS:CONFIGURE,RESET,RECOVER
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

7. P. Paolucci & G. Polese - INFN di Napoli
MAJORITY
USE MAJORITY FOR SECTOR AND WHEEL FSM.
IF 2 CHAMBERS ARE IN STATE ERROR=>
MAJORITY ERROR-> SECTOR STATUS =NOT_READY
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli

8. P. Paolucci & G. Polese - INFN di Napoli
SECTOR ALARM
WE ARE INTESTING THE POSSIBILITY TO USE A SUMMARY ALARM FOR SECTORS TO INTEGRATE INTO TOPNODE. THIS ALARMS IS AN OR CONDITION OF ALL SECTOR’S CHAMBERS.
FOR THIS AIM WE NEED A DATAPOINT STRUCTURED AS FSM TREE, FOR THIS REASON WE HAVE USED AN INTERNAL DATAPOINT
SECTOR SUMMARY ALARM
SECTOR FSM STATUS
1/17/2019
P. Paolucci & G. Polese - INFN di Napoli