EPICS

EPICS
EPICS · Public domain · source
Name	EPICS
Developer	Los Alamos National Laboratory, Argonne National Laboratory, Oak Ridge National Laboratory
Released	1980s
Programming language	C, C++, Python (programming language), Java (programming language)
Operating system	Linux, Windows, macOS, VxWorks
License	Open-source

EPICS

EPICS is a set of open-source software tools, libraries, and applications for building distributed control systems used in scientific and industrial facilities. It enables instrumentation orchestration, real-time device control, data acquisition, and operator interfaces across large-scale projects such as particle accelerators, synchrotron light sources, and fusion reactors. EPICS is widely adopted at institutions including CERN, SLAC National Accelerator Laboratory, European Organization for Nuclear Research, Fermilab, and Brookhaven National Laboratory.

Overview

EPICS provides an architecture for linking input/output controllers, operator consoles, and data archiving systems into a coherent control system. The toolkit centers on a database-driven model using networked process variables to represent hardware and software state, facilitating integration with hardware from vendors such as National Instruments, Siemens, Schneider Electric, ABB, and Yokogawa. Operator interfaces and higher-level applications are often implemented using frameworks and tools from projects like Control System Studio, MEDM, Java (programming language), Python (programming language), and Qt (software), enabling visualization and automation across facilities such as Diamond Light Source, European XFEL, ISIS Neutron and Muon Source, SOLEIL, and MAX IV.

History and Development

EPICS originated in the 1980s from collaborations among US national laboratories including Los Alamos National Laboratory, Argonne National Laboratory, and Oak Ridge National Laboratory to solve scaling problems encountered at projects like Los Alamos Meson Physics Facility and later at accelerator projects including Advanced Photon Source and Spallation Neutron Source. Development continued through academic and research partnerships with organizations such as University of Chicago, University of Oxford, MIT, and Caltech. Over decades EPICS evolved through major milestones influenced by events and projects like Project X, International Linear Collider, Large Hadron Collider, and upgrades at Stanford Linear Accelerator Center.

Architecture and Components

Core components include the Input/Output Controller (IOC), Channel Access and pvAccess network protocols, records and databases, and client-side tools. IOCs run on real-time platforms often built with VxWorks, Linux, or Windows, interfacing to hardware through device support for controllers such as Programmable Logic Controller vendors and real-time processors like PXI and VMEbus. Channel Access and pvAccess provide pub/sub mechanisms comparable to architectures in OPC UA and MQTT, while archiving solutions interface with databases like MySQL, PostgreSQL, and InfluxDB. GUI and scripting integrations leverage EPICS Base, Area Detector, Control System Studio, Matlab, Python (programming language), and LabVIEW.

Applications and Use Cases

EPICS is deployed in accelerator complexes including CERN, Fermilab, Diamond Light Source, European XFEL, Brookhaven National Laboratory, DESY, and KEK, and in large experimental facilities like ITER, JET (tokamak), National Ignition Facility, and neutron sources such as Oak Ridge National Laboratory's Spallation Neutron Source. Use cases cover beamline control, vacuum systems, cryogenics, magnet power supplies, radiofrequency control, detector readout, and robotics integration. EPICS supports experiments and instruments at institutions like Los Alamos National Laboratory, Lawrence Berkeley National Laboratory, Argonne National Laboratory, SLAC National Accelerator Laboratory, and research infrastructure projects funded by agencies such as U.S. Department of Energy, European Commission, and Japan Society for the Promotion of Science.

Community and Governance

EPICS development and governance involve collaborations among national laboratories, universities, and facilities organized through workshops, collaboration meetings, and mailing lists. Key contributors and institutions include Argonne National Laboratory, Oak Ridge National Laboratory, Los Alamos National Laboratory, SLAC National Accelerator Laboratory, Brookhaven National Laboratory, Diamond Light Source, DESY, and CERN. Community coordination occurs via working groups, international workshops (for example events hosted at Argonne National Laboratory and CERN), and repositories hosted on platforms similar to GitHub and GitLab where projects such as EPICS Base and Area Detector are maintained. Collaborations extend to standards bodies and projects like EPICS Extension, Control System Studio, and industrial partners including National Instruments.

Implementation and Integration

Implementations typically begin with IOC deployment, device driver development, and record configuration using tools from EPICS Base and modules such as synApps, Area Detector, and pvAccess. Integration often requires interfacing with hardware standards and buses like VMEbus, PXI, EtherCAT, Modbus, and PROFINET, and with enterprise services including MySQL, PostgreSQL, Active Directory, and Docker. Scripting, automation, and higher-level control are commonly implemented using languages and environments such as Python (programming language), Matlab, Java (programming language), LabVIEW, and Qt (software), while CI/CD and packaging use tools inspired by Jenkins, Ansible, and Docker.

Security and Maintenance

Security and maintenance practices for EPICS deployments include network segmentation, authentication and authorization layers compatible with Kerberos, TLS/SSL, access control via host-based firewalls and VPNs, and patch management procedures coordinated by facility IT groups at sites like SLAC National Accelerator Laboratory, Fermilab, CERN, and Oak Ridge National Laboratory. Regular maintenance uses version control workflows and testing practices from communities using GitHub, Jenkins, and automated testing frameworks, with long-term support provided by collaborating laboratories, university groups, and industry partners such as National Instruments and Siemens.

Category:Control systems