Detector Control System: Difference between revisions
(Add device driver links) |
(Add something about ControlSystemStudio-Phoebus and OTSDAQ) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
* [https://groups.nscl.msu.edu/controls/files/devSnmp.html SNMP] (supported by NSCL/FRIB) specifically for SNMP devices, including many networked power supplies (Wiener/ISEG), many uninterruptible power supplies and power distribution units, and others; | * [https://groups.nscl.msu.edu/controls/files/devSnmp.html SNMP] (supported by NSCL/FRIB) specifically for SNMP devices, including many networked power supplies (Wiener/ISEG), many uninterruptible power supplies and power distribution units, and others; | ||
* [https://epics.anl.gov/modules/soft/asyn/ asynDriver] (supported by ANL) for general access to serial devices, GPIB, TCP/IP, etc. | * [https://epics.anl.gov/modules/soft/asyn/ asynDriver] (supported by ANL) for general access to serial devices, GPIB, TCP/IP, etc. | ||
A number of programs and libraries are available that work with EPICS. We use the [https://control-system-studio.readthedocs.io/en/latest/services/archive-engine/doc/index.html Control System Studio] toolset for its [https://control-system-studio.readthedocs.io/en/latest/services/archive-engine/doc/index.html data archiving] and display building features. Regular shifter displays and alarm notifications are provided through the OTS DAQ user interface. (Details in Mu2e-doc-[https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=32256 32256] and -[https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=32426 32426].) | |||
This page is currently a stub. Here are some links for more information: | This page is currently a stub. Here are some links for more information: | ||
| Line 17: | Line 19: | ||
* The DCS source code is being migrated from Redmine to https://github.com/Mu2e/DCS. | * The DCS source code is being migrated from Redmine to https://github.com/Mu2e/DCS. | ||
* Constantly reviewed and updated developer and user documentation will be available at https://mu2e.github.io/DCS, which is automatically generated from files maintained in the Mu2e DCS GitHub project. | * Constantly reviewed and updated developer and user documentation will be available at https://mu2e.github.io/DCS, which is automatically generated from files maintained in the Mu2e DCS GitHub project. | ||
[[Category:Experiment]] | |||
Latest revision as of 17:05, 7 May 2020
The detector control system (DCS), provides operational control and monitoring of all Mu2e subsystems. The DCS is also referred to as the "slow controls."
The backbone of the DCS is EPICS. We are using the 3.15 Stable release of EPICS.
EPICS base defines a large number of record types, and extension modules support a multitude of additional devices and record types. These are documented on the EPICS Resources and Support page. Important modules for Mu2e include
- StreamDevice (supported by PSI) for any device with a byte stream based communication protocol;
- SNMP (supported by NSCL/FRIB) specifically for SNMP devices, including many networked power supplies (Wiener/ISEG), many uninterruptible power supplies and power distribution units, and others;
- asynDriver (supported by ANL) for general access to serial devices, GPIB, TCP/IP, etc.
A number of programs and libraries are available that work with EPICS. We use the Control System Studio toolset for its data archiving and display building features. Regular shifter displays and alarm notifications are provided through the OTS DAQ user interface. (Details in Mu2e-doc-32256 and -32426.)
This page is currently a stub. Here are some links for more information:
- Mu2e-doc-33080 is an overview presentation for Mu2e collaborators.
- Mu2e-doc-31778 describes how Mu2e devices connect to EPICS directly, and Mu2e-doc-31727 describes how Mu2e subdetector DAQ electronics connect to the DCS through the TriggerDAQ.
More resources coming soon:
- The DCS source code is being migrated from Redmine to https://github.com/Mu2e/DCS.
- Constantly reviewed and updated developer and user documentation will be available at https://mu2e.github.io/DCS, which is automatically generated from files maintained in the Mu2e DCS GitHub project.