This guideline describes the VELO ECS (Experiment Control System) which is in charge of supervising and controlling all the detector’s components.
The ECS control system is a hierarchical, reactive system built as a tree of interconnected control nodes. At the higher levels we have control nodes called control units (CU), to which an operator can connect to take the control of the associated sub tree of the system, and at the very lower level we have the control nodes called devices units (DU) connected to real hardware components that they supervise. It is hierarchical because each control node has only one master node from which it receives commands to execute and a limited set of direct children to which it can send commands. A control node implements the entry point to supervise a sub-part of the detector. The root node controls the full detector. It is reactive because the control nodes behaviour is to react to events. Two types of events exist: a command reception coming from the parent node or a state change in one of the children controllers. Event occurrences trigger two types of control flows. The command flow which propagates along the tree from the operator (or control program) connected to a CU down to the lower level nodes DU acting on hardware to have some real action executed. The state change flow which propagates along the tree from the hardware component that changes its status, up to the control node CUs that can take the necessary action to cope with this state change. All control nodes publish a unique state representing the state of the sub-detector part they control. The way this state is computed is different for CU and DU. [Extract from the the LHCb ECS guideline]
The VELO ECS is divided into 4 sub-domains:
1) VELO_DAQ (Data acquisition) 2) VELO_DAI (DAQ Infrastructures) 3) VELO_DCS (Detector Control System) 4) VELO_HV (High Voltage)
You can view the general layout of the VELO ECS hierarchy here: