(r2) Draft_DCS < Sandbox

You are here: PANDA Wiki>Sandbox Web>Draft_DCS (revision 2) (raw view)~~EditAttach~~

-- Main.MarioBragadireanu - 12 Oct 2014

Welcome to the home of *PANDA DCS wiki.*
---+ PANDA Detector Control System
   * [[#PANDA%20DCS%20Technical%20Design][%BLUE%P<span style="background-color: transparent;">ANDA DCS Technical Design</span>%ENDCOLOR%]]
   * <p> [[#Contacts][%BLUE%<span style="background-color: transparent;">Contacts</span>%ENDCOLOR%]]</p>
---+++ <span style="color: #2f4f4f; line-height: 1.1em; background-color: transparent;">PANDA DCS Technical Design</span>

The present structure of PANDA experiment involves several sub-detectors and sub-systems (Fig.1). The Slow Controls (SC) of each PANDA sub-detector and sub-system are planned to be monitored and controlled from a supervisory software application.

<img align="top" alt="PandaCentralDCS.png" height="361" src="%ATTACHURL%/PandaCentralDCS.png" title="Fig. 1: PANDA DCS -centralized view" width="640" />

In the past, an evaluation of several [[http://en.wikipedia.org/wiki/SCADA][SCADA]] development packages, [[http://www.etm.at/index_e.asp][PVSS]], [[http://www.ni.com/LabView][LabView]], [[http://www.aps.anl.gov/epics/][EPICS]], was performed by a PANDA slow controls subgroup and the EPICS package was selected to be the main SC software development tool.

Due to the anticipated complexity of the whole PANDA DCS and the expected staged assembly of PANDA detector, the DCS is highly needed to be modular and scalable. In order to accomplish this, each PANDA sub-detector or sub-system is envisaged to be basically autonomous but manageable from a supervisory layer.

<img align="top" alt="PandaDCSPartition.png" height="367" src="%ATTACHURL%/PandaDCSPartition.png" title="Fig. 2: PANDA DCS Partition" width="640" />

The autonomy of each PANDA DCS partition (Fig. 2) implies that the partition should be self-controllable. This means that, specific slow control software, tailored to configure, monitor and control the hardware devices belonging to the partition, is required. Moreover, the partition specific software must be capable to share data with the supervisory layer.

<span style="background-color: transparent;">In order to ensure compatible data sharing between the SC supervisory layer and SC partition, an EPICS Process Variable [[http://www.aps.anl.gov/epics/extensions/gateway/][Gateway]] is required to be implemented by each PANDA SC partition. Additionally, thePV Gateway will provide access rights administration and subnet interface.</span>

The SC operation of each partition will be performed from a dedicated graphical user interface (GUI). The interface should ensure the accurate and safe operation of the partition hardware. The complete interface, or part of it, will be embedded in the PANDA supervisory software.

At the moment, the state of the art user interface to EPICS is supported by the Control System Studio (CSS) framework. The technical design of PANDA SC system is planned to provide a set of guidelines for naming conventions, and graphical interface look and feel, in order to guarantee the similarity of the independent developed modules and to simplify the integration.

The outcome of putting all the above requirements together is a PANDA DCS architecture based on a three-layer design – Supervisory, Control and Field layers. The highest level is the Supervisory one. The Control Layer is in the middle and it is the level where all the PANDA DCS partitions are connected. The Field Layer is embedded in each PANDA DCS Partition, and is made of all the devices and sensors used to monitor and control the sub-sytem.

<img alt="PandaDCSLayers.png" height="311" src="%ATTACHURL%/PandaDCSLayers.png" title="Fig. 3: PANDA DCS Layers" width="640" />

Because the device driver software support in EPICS is limited, the software development tools used to control the lowermost layer (Field Layer) are at the free choice of the developer. The only constrain here is that the software must be integrated in the control layer with the EPICS system. However, the recommendation is that the developer, in the early stages of design, should try implement, were is possible, the same hardware and software, with EPICS support, realized by other PANDA sub-systems.
---+++ <span style="color: #2f4f4f;">Contacts</span>

Topic attachments
I	Attachment	Action	Size	Date	Who
png	PandaCentralDCS.png	manage	70.0 K	12 Oct 2014 - 07:39	MarioBragadireanu
png	PandaDCSPartition.png	manage	66.7 K	12 Oct 2014 - 08:14	MarioBragadireanu
png	PandaDCSLayers.png	manage	110.6 K	12 Oct 2014 - 09:15	MarioBragadireanu

Topic revision: r2 - 12 Oct 2014, MarioBragadireanu

Sandbox

Sandbox Web
Sandbox Web Home
Changes
Index
Search

Webs
- Cerenkov
- Cerenkov.Pandacerenkov
- DCS
- Daq
- Daq.Pandadaq
- Detector
- EMC
- EMPAnalysis
- Forwardstraws
- GEM
- MC
- Magnet
- Main
- Mvd
- PANDAMainz
- PWA
- Pbook
- Personalpages
- Physics
- Physics.Baryons
- Physics.CharmoniumAndExotics
- Physics.HadronsInNuclei
- Physics.OpenCharm
- PhysicsCmt
- SPC
- STT
- Sandbox
- ScrutinyGroup
- System
- Tagpid
- Tagpid.Pandatagpid
- Tagtrk
- Tagtrk.Pandatagtrk
- Target
- Target.ClusterJetTarget
- Tof
- WebServices
- YoungScientists
- ZArchives

Create personal sidebar

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PANDA Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)