Difference: ECSmanual (1 vs. 8)

Revision 82008-08-09 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 26 to 26
 VeloFSM.gif
Added:
>
>

How to start the Velo ECS FSM

  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
  3. Double click on VEECS1_UI_DEN. The following panel will pop up:
    VeloTopDEN.JPG

  4. Select the FSM tab.
    VeloTopDEN_FSM.JPG

  5. Click on the STOP ALL button.
  6. Click on Start/Restart ALL.
 

Procedure to operate the VELO ECS

  1. Operating the main VELO ECS control
  2. Operating the VELO DAQ
Line: 33 to 44
 
  1. Operating the VELO HV
Changed:
<
<
-- StefanoDeCapua - 06 Mar 2008
>
>
-- StefanoDeCapua - 06 Aug 2008

 
META FILEATTACHMENT attachment="VeloFSM.gif" attr="" comment="" date="1214209907" name="VeloFSM.gif" path="VeloFSM.gif" size="45332" stream="VeloFSM.gif" user="Main.StefanoDeCapua" version="1"
Added:
>
>
META FILEATTACHMENT attachment="VeloTopDEN.JPG" attr="" comment="" date="1218296459" name="VeloTopDEN.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopDEN.JPG" size="37517" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopDEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTopDEN_FSM.JPG" attr="" comment="" date="1218296475" name="VeloTopDEN_FSM.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopDEN_FSM.JPG" size="26848" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopDEN_FSM.JPG" user="Main.StefanoDeCapua" version="1"

Revision 72008-08-09 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 11 to 11
 
<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->
Added:
>
>
 

Introduction

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]

Line: 26 to 29
 

Procedure to operate the VELO ECS

  1. Operating the main VELO ECS control
  2. Operating the VELO DAQ
Changed:
<
<
  1. Operating the VELO DCS
>
>
  1. Operating the VELO DCS
 
  1. Operating the VELO HV

Revision 62008-08-08 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 25 to 25
 

Procedure to operate the VELO ECS

  1. Operating the main VELO ECS control
Changed:
<
<
  1. Operating the VELO DAQ
>
>
  1. Operating the VELO DAQ
 
  1. Operating the VELO DCS
  2. Operating the VELO HV

Revision 52008-08-07 - BarinjakaRakotomiaramanana

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 27 to 27
 
  1. Operating the main VELO ECS control
  2. Operating the VELO DAQ
  3. Operating the VELO DCS
Changed:
<
<
  1. Operating the VELO HV
>
>
  1. Operating the VELO HV
 

-- StefanoDeCapua - 06 Mar 2008

Revision 42008-06-23 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 20 to 20
 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:

Changed:
<
<

VeloFSM_v0.pdf
>
>
VeloFSM.gif
 

Procedure to operate the VELO ECS

  1. Operating the main VELO ECS control
  2. Operating the VELO DAQ
Changed:
<
<
  1. Operating the VELO DCS
  2. Operating the VELO HV
>
>
  1. Operating the VELO DCS
  2. Operating the VELO HV
 

-- StefanoDeCapua - 06 Mar 2008

Changed:
<
<
META FILEATTACHMENT attachment="VeloFSM.pdf" attr="" comment="" date="1204839137" name="VeloFSM.pdf" path="C:\Documents and Settings\stefano\Desktop\VeloFSM.pdf" size="25284" stream="C:\Documents and Settings\stefano\Desktop\VeloFSM.pdf" user="Main.StefanoDeCapua" version="2"
META FILEATTACHMENT attachment="VeloFSM_v0.pdf" attr="" comment="" date="1204839288" name="VeloFSM_v0.pdf" path="C:\Documents and Settings\stefano\Desktop\VeloFSM_v0.pdf" size="25284" stream="C:\Documents and Settings\stefano\Desktop\VeloFSM_v0.pdf" user="Main.StefanoDeCapua" version="1"
>
>
META FILEATTACHMENT attachment="VeloFSM.gif" attr="" comment="" date="1214209907" name="VeloFSM.gif" path="VeloFSM.gif" size="45332" stream="VeloFSM.gif" user="Main.StefanoDeCapua" version="1"

Revision 32008-05-06 - EddyJans

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 19 to 19
  1) VELO_DAQ (Data acquisition)
2) VELO_DAI (DAQ Infrastructures)
3) VELO_DCS (Detector Control System)
4) VELO_HV (High Voltage)
Changed:
<
<
You can view the general layout of the VELO ECS hierarchy here: VeloFSM_v0.pdf.
>
>
You can view the general layout of the VELO ECS hierarchy here:
VeloFSM_v0.pdf
 

Procedure to operate the VELO ECS

  1. Operating the main VELO ECS control

Revision 22008-04-23 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->
Line: 22 to 22
 You can view the general layout of the VELO ECS hierarchy here: VeloFSM_v0.pdf.

Procedure to operate the VELO ECS

Changed:
<
<
  1. Starting the VELO ECS
>
>
  1. Operating the main VELO ECS control
 
  1. Operating the VELO DAQ
  2. Operating the VELO DCS
  3. Operating the VELO HV

Revision 12008-03-06 - StefanoDeCapua

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="VELOCommissioning"
<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

Introduction

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: VeloFSM_v0.pdf.

Procedure to operate the VELO ECS

  1. Starting the VELO ECS
  2. Operating the VELO DAQ
  3. Operating the VELO DCS
  4. Operating the VELO HV

-- StefanoDeCapua - 06 Mar 2008

META FILEATTACHMENT attachment="VeloFSM.pdf" attr="" comment="" date="1204839137" name="VeloFSM.pdf" path="C:\Documents and Settings\stefano\Desktop\VeloFSM.pdf" size="25284" stream="C:\Documents and Settings\stefano\Desktop\VeloFSM.pdf" user="Main.StefanoDeCapua" version="2"
META FILEATTACHMENT attachment="VeloFSM_v0.pdf" attr="" comment="" date="1204839288" name="VeloFSM_v0.pdf" path="C:\Documents and Settings\stefano\Desktop\VeloFSM_v0.pdf" size="25284" stream="C:\Documents and Settings\stefano\Desktop\VeloFSM_v0.pdf" user="Main.StefanoDeCapua" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback