1. Controls EN-ICE FSM for dummies (…w/ all my respects) 15 th Jan 09

2. Controls EN-ICE Typical DCS application FSM for dummies - 2F. Varela – EN/ICE – UNICOS Meeting – 15 th Jan 09  Developed by:  Collaborations CERN-Universities  Many temporary stuff  Operated by a non-experience shifter  Concurrent access by multiple users  More than 1M IOs  Large variety of technologies  150 computers User knowledge of the system Heterogeneity/Complexity - +

3. Controls EN-ICE Implementation Front-End (CAEN/Wiener/Iseg, ELMB, etc.) Front-End (CAEN/Wiener/Iseg, ELMB, etc.) Middleware (OPC, DIM, DIP, drivers, etc) Middleware (OPC, DIM, DIP, drivers, etc) PVSS Front-End (CAEN/Wiener/Iseg, ELMB, etc.) Front-End (CAEN/Wiener/Iseg, ELMB, etc.) Middleware (OPC, DIM, DIP, drivers, etc) Middleware (OPC, DIM, DIP, drivers, etc) PVSS x150 What do we have?  Panels and control procedures requiring a deep understanding of the detectors/systems  150 peers with no hierarchical organization What are we lacking?  Modelling of a abstract entities in the control system  Hierarchical organization: Tree!  Knowledge encapsulation  Sequencing and synchronization across (and within) PVSS systems  Partitioning management  Ownership FSM FSM for dummies - 3F. Varela – EN/ICE – UNICOS Meeting – 15 th Jan 09 JCOP Framework  Framework:  Brings homogenization to the system  Hides complexity of the HW

4. Controls EN-ICE A very simple example T1 HV1 FSM for dummies - 4F. Varela – EN/ICE – UNICOS Meeting – 15 th Jan 09 T2 Pump HV2 HV3 LV1 LV2 LHC Constraints for operation:  HV can be ramped up to a reduced value only if cooling is OK and LV is ON  HV can be ramped up to the nominal value only if LHC report stable beams, cooling is OK and LV is ON JCOP Framework fwExtApp s fwElmb fwCAEN So far, in the application one only knows about individual devices LHCCooling LVHV Tracker Temperatures: OKNOT_OK UNK Pump: RUNNINGSTOPPED ERROR STDBY Cooling: READYN_READY ERROR States based on states of the children according to rules

5. Controls... as it is used in the JCOP Framework ? a tool to model controls systems …by breaking it into smaller and simpler units with several states each with several associated actions SM I all is implemented in the State Machine Interface SMI++ What is a FSM? FSM for dummies - 5F. Varela – EN/ICE – UNICOS Meeting – 15 th Jan 09

6. Controls The FSM is the tool that:  summarizes the conditions of the many devices in the DCS into a single overall state  allows the shifter to operate the detector with a few mouse-clicks Forces developers to hide the complexity of the system The DCS of the LHC experiments consists of a large variety of complex devices and technologies Why FSM? FSM for dummies - 6F. Varela – EN/ICE – Section Meeting – 24 th Nov 09

7. Controls  PVSS UI, archiving, configuration persistency, Alarm Handling, Access Control, proxies  DIM for inter process communication  SMI++ FSM behaviour The JCOP FSM toolkit consists of: JCOP FSM FSM for dummies - 7F. Varela – EN/ICE – Section Meeting – 24 th Nov 09

8. Controls Gas LV HV Cooling Gas DCS Tracker Vertex Muon LV Gas LV HV Gas Cooling Commands States & Alarms CU/LU DU  Control and Logical Units abstract entities. Logical decision units.  Only CU allow for partitioning  LU are lighter weight  Device Units model real and concrete devices/entities, e.g. a HV channel, a crate, a temp sensor. An example system FSM for dummies - 8F. Varela – EN/ICE – Section Meeting – 24 th Nov 09

9. Controls Control Unit Overview PVSS II Parent Commands/States Configuration Database Operator Child Commands/States Configuration data Specific Behavior FSM Logging & Archiving Alarm Handling Ownership & Partitioning FSM

10. Controls Logical Unit Overview PVSS II Parent Commands/States Configuration Database Operator Child Commands/States Configuration data Specific Behavior FSM Logging & Archiving Alarm Handling

11. Controls Device Unit Overview PVSS II Parent Commands/States Configuration Database Operator HW/SW Device Commands/States Settings & Readings Configuration data Logging & Archiving Alarm Handling FSM Interface Device Driver

12. Controls JCOP Framework Names Device Type modelling of a hardware or logical device with PVSS datapoints Device instance of a device type Device Unit Type modelling of a behaviour based on a device type Device Unit instance of a device unit type based on a device Logical Unit Type modelling of behaviour for an abstract object Control Unit instance of a logical unit type running as a SMI domain Logical Unit instance of a logical unit type running inside a SMI domain

13. Controls Partitioning DCS TrackerVertexMuon GasLV HV Cooling Gas LVGasLV HV GasCooling

14. Controls Partitioning Modes Parent Child commands states Included child fully controlled by parent Parent Child commands statesIgnored parent ignores the child’s states Parent Child commands statesManual parent does not send commands Parent Child commands statesExcluded child not controlled by parent

15. Controls PVSS IntegrationCtrl API EV D D D UIMUIMUIM DM DB PVSS00smi fwFsmSrvr Ctrl DU Handler In other words, PVSS acts as UI to configure and operate the SMI++ procs SMI++ (Real FSM Machinery) PVSS SML Files 1.User defines FSM hierarchy and node behaviour in PVSS 2.fwFSMSrvr create SML files containing this knowledge 3.SMI++ procs read SML files at start-up and implements the FSM behaviour SML parallel and asynchronous execution

16. Controls Sending a commandAPI EV D Dist UIMUIM DM DB PVSS00smi Ctrl API EV DD UIM DM DB DU Handler Dist Machine 1 Machine 2

17. Controls A device changes stateAPI EV D Dist UIMUIM DM DB PVSS00smi Ctrl API EV DD UIM DM DB DU Handler Dist Machine 1 Machine 2