Controls ENICE FSM for dummies w all my
- Slides: 18
Controls EN-ICE FSM for dummies (…w/ all my respects) 24 th Nov 09
Controls Typical DCS application EN-ICE User knowledge of the system Heterogeneity/Complexity - + Ø More than 3 M IOs Ø Large variety of technologies Ø 150 computers ØDeveloped by: ØCollaborations CERN-Universities ØMany temporary stuff Ø Operated by a non-experience shifter F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 FSM for dummies - 2
What is a FSM? Controls n . . . as it is used in the JCOP Framework ? n a tool to model controls systems • …by breaking it into smaller and simpler units n with several states each with several associated actions n all is implemented in the State Machine Interface n SMI++ F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 FSM for dummies - 3
Controls Why FSM? The DCS of the LHC experiments consists of a large variety of complex devices and technologies 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 F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 FSM for dummies - 4
Controls An example system CU/LU DU DCS Muon HV LV Cooling HV Gas Cooling HV LV Gas Commands Tracker States & Alarms Vertex § 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. F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 FSM for dummies - 5
Controls Partitioning DCS Vertex Tracker Muon HV LV Cooling HV Gas Cooling HV LV Gas
Controls Partitioning Modes Included child fully controlled by parent states Parent Manual parent does not send commands states Child child not controlled by parent states commands Child Excluded Parent commands Child Ignored parent ignores the child’s states Child Parent commands
Controls Formal Methods Real life FSM hierarchies account with several tens of nodes with a set of well defined states and possible transitions among them The challenge: how to make sure that all state and transitions are reachable, how to avoid infinite loops, etc. Preliminary work done in CMS proved the validity of Formal Methods for this kind of analysis Goal: Integrate this analysis and tools into the FSM toolkit
Controls Backup slides
Controls Implementation EN-ICE What do we have? What are we lacking? Ø Panels and control procedures that require a deep understanding of the detectors/systems Ø 150 peers with no hierarchical organization Ø Hierarchical organization Ø Knowledge encapsulation Ø Sequencing and synchronization across (and within) PVSS systems Ø Partitioning management Ø Ownership FSM PVSS Middleware (OPC, DIM, DIP, drivers, etc) Front-End (CAEN/Wiener/Iseg, ELMB, etc. ) F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 PVSS x 150 Middleware (OPC, DIM, DIP, drivers, etc) Front-End (CAEN/Wiener/Iseg, ELMB, etc. ) FSM for dummies - 10
Controls JCOP FSM The JCOP FSM toolkit consists of: § PVSS • UI, archiving, configuration persistency, Alarm Handling, Access Control, proxies § DIM • for inter process communication § SMI++ • FSM behaviour F. Varela – EN/ICE – Section Meeting – 24 th Nov 09 FSM for dummies - 11
Controls Control Unit Overview Parent Operator Configuration Commands/States Database Commands/States Configuration data Specific Behavior FSM Logging & Archiving Ownership & Partitioning FSM Alarm Handling PVSS II Commands/States Child
Controls Logical Unit Overview Parent Operator Configuration Commands/States Database Commands/States Configuration data Specific Behavior FSM Logging & Archiving Alarm Handling PVSS II Commands/States Child
Controls Device Unit Overview Parent Operator Configuration Database Commands/States Configuration data Logging & Archiving PVSS II FSM Interface Alarm Handling Device Driver Settings & Readings HW/SW Device
Controls JCOP Framework Names Control Unit Logical Unit instance of a logical unit type running as a SMI domain instance of a logical unit type running inside a SMI domain Logical Unit Type modelling of behaviour for an abstract object Device Unit instance of a device unit type based on a device Device instance of a device type Device Unit Type modelling of a behaviour based on a device type Device Type modelling of a hardware or logical device with PVSS datapoints
Controls PVSS Integration PVSS UIM Ctrl UIM SMI++ (Real FSM Machinery) SML Files Ctrl DU Handler fw. Fsm. Srvr DB DM API EV PVSS 00 smi D D D SML parallel and asynchronous execution 1. User defines FSM hierarchy and node behaviour in PVSS 2. fw. FSMSrvr create SML files containing this knowledge 3. SMI++ procs read SML files at start-up and implements the FSM behaviour In other words, PVSS acts as UI to configure and operate the SMI++ procs
Controls Sending a command Machine 1 UIM DB UIM API EV DM PVSS 00 smi D Dist UIM Ctrl DU Handler DB DM API EV PVSS 00 smi D D Machine 2
Controls A device changes state Machine 1 UIM DB UIM API EV DM PVSS 00 smi D Dist UIM Ctrl DU Handler DB DM API EV PVSS 00 smi D D Machine 2
- Gravity for dummies and dummies for gravity equations
- He who controls the past controls the future
- General controls vs application controls
- Netgear gsm/fsm fully managed switches
- Rdt3.0 receiver
- "tremendousness design"
- Fsm tutorial
- State diagram
- Spring fsm
- Refurbished netgear gsm/fsm fully managed switches
- Finite state machine elevator
- Selective repeat dilemma
- Verilog fsm example
- Tap state machine
- Ifs fsm
- Louise voden
- Fsm counter
- Fsm & fpp
- Fsm