ICALEPCS2013 - List of Authors (Lange, R.)

Paper

Title

Page

Design and Implementation Aspects of the Control System at FHI FEL

324

H. Junkes, W. Schöllkopf, M. Wesemann
FHI, Berlin, Germany
R. Lange
HZB, Berlin, Germany
R. Lange
AES, Princeton, New Jersey, USA

A new mid-infrared FEL has been commissioned at the Fritz-Haber-Institut in Berlin. It will be used for spectroscopic investigations of molecules, clusters, nanoparticles and surfaces. The oscillator FEL is operated with 15 - 50 MeV electrons from a normal-conducting S-band linac equipped with a gridded thermionic gun and a chicane for controlled bunch compression. Construction of the facility building with the accelerator vault began in April 2010. First lasing was observed on Februar 15th, 2012. * The EPICS software framework was chosen to build the control system for this facility. The industrial utility control system is integrated using BACnet/IP. Graphical operator and user interfaces are based on the Control System Studio package. The EPICS channel archiver, an electronic logbook, a web based monitoring tool, and a gateway complete the installation. This paper presents design and implementation aspects of the control system, its capabilities, and lessons learned during local and remote commissioning.
* W. Schöllkopf et al., FIRST LASING OF THE IR FEL AT THE FRITZ-HABER-INSTITUT, BERLIN, Conference FEL12

Poster MOPPC096 [10.433 MB]

MOPPC124

Optimizing EPICS for Multi-Core Architectures

399

R. Lange, F. Di Maio
ITER Organization, St. Paul lez Durance, France
R. Lange
HZB, Berlin, Germany

Funding: Work supported by German Bundesministerium für Bildung und Forschung and Land Berlin.
EPICS is a widely used software framework for real-time controls in large facilities, accelerators and telescopes. Its multithreaded IOC (Input Output Controller) Core software has been developed on traditional single-core CPUs. The ITER project will use modern multi-core CPUs, running the RHEL Linux operating system in its MRG-R real-time variant. An analysis of the thread handling in IOC Core shows different options for improving the performance and real-time behavior, which are discussed and evaluated. The implementation is split between improvements inside EPICS Base, which have been merged back into the main distribution, and a support module that makes full use of these new features. This paper describes design and implementation aspects, and presents results as well as lessons learned.

Poster MOPPC124 [0.448 MB]

MOPPC148

Not Dead Yet: Recent Enhancements and Future Plans for EPICS Version 3

457

A.N. Johnson, J.B. Anderson
ANL, Argonne, USA
M.A. Davidsaver
BNL, Upton, New York, USA
R. Lange
HZB, Berlin, Germany

Funding: Work supported by U.S. Department of Energy, Office of Science, under Contract No. DE-AC02-06CH11357.
The EPICS Version 4 development effort* is not planning to replace the current Version 3 IOC Database or its use of the Channel Access network protocol in the near future. Interoperability is a key aim of the V4 development, which is building upon the older IOC implementation. EPICS V3 continues to gain new features and functionality on its Version 3.15 development branch, while the Version 3.14 stable branch has been accumulating minor tweaks, bug fixes, and support for new and updated operating systems. This paper describes the main enhancements provided by recent and upcoming releases of EPICS Version 3 for control system applications.
* Korhonen et al, "EPICS Version 4 Progress Report", this conference.

Poster MOPPC148 [5.067 MB]

TUCOCB04

EPICS Version 4 Progress Report

956

T. Korhonen
PSI, Villigen PSI, Switzerland
L.R. Dalesio, N. Malitsky, G. Shen
BNL, Upton, Long Island, New York, USA
D.G. Hickin, J. Rowland
Diamond, Oxfordshire, United Kingdom
M.R. Kraimer
Self Employment, Private address, USA
R. Lange
HZB, Berlin, Germany
M. Sekoranja
Cosylab, Ljubljana, Slovenia
G.R. White
SLAC, Menlo Park, California, USA

EPICS Version 4 is the next major revision of the Experimental Physics and Industrial Control System, a widely used software framework for controls in large facilities, accelerators and telescopes. The primary goal of Version 4 is to improve support for scientific applications by augmenting the control-centered EPICS Version 3 with an architecture that allows building scientific services on top of it. Version 4 provides a new standardized wire protocol, support of structured types, and parametrized queries. The long-term plans also include a revision of the IOC core layer. The first set of services like directory, archive retrieval, and save set services aim to improve the current EPICS architecture and enable interoperability. The first services and applications are now being deployed in running facilities. We present the current status of EPICS V4, the interoperation of EPICS V3 and V4, and how to create services such as accelerator modelling, large database access, etc. These enable operators and physicists to write thin and powerful clients to support commissioning, beam studies and operations, and opens up the possibility of sharing applications between different facilities.

Slides TUCOCB04 [1.937 MB]

TUCOCB05

Device Definition and Composite Device Views on Top of the Flat EPICS Namespace

L.R. Dalesio, K. Shroff, L. Yang
BNL, Upton, Long Island, New York, USA
R. Lange
HZB, Berlin, Germany

The EPICS (Experimental Physics and Industrial Control System) IOC (Input Output Controller) Core database represents a process on signal level, presenting a flat view of possibly complex devices. This signal level interface is an easily agreed upon common denominator, allowing drivers, signal records, and processes on these signals to be standardized across EPICS installations. However, it is also necessary to represent a device in its different aspects. Currently this requires a-priori knowledge of all individual channels that are included in a device by each client. This paper discusses device orientation based on the new EPICS Version 4 database and middle layer services along with the ecosystem to manage these views.

Slides TUCOCB05 [1.144 MB]

MOPPC124

Optimizing EPICS for Multi-Core Architectures

399

R. Lange, F. Di Maio
ITER Organization, St. Paul lez Durance, France
R. Lange
HZB, Berlin, Germany

Funding: Work supported by German Bundesministerium für Bildung und Forschung and Land Berlin.
EPICS is a widely used software framework for real-time controls in large facilities, accelerators and telescopes. Its multithreaded IOC (Input Output Controller) Core software has been developed on traditional single-core CPUs. The ITER project will use modern multi-core CPUs, running the RHEL Linux operating system in its MRG-R real-time variant. An analysis of the thread handling in IOC Core shows different options for improving the performance and real-time behavior, which are discussed and evaluated. The implementation is split between improvements inside EPICS Base, which have been merged back into the main distribution, and a support module that makes full use of these new features. This paper describes design and implementation aspects, and presents results as well as lessons learned.

Poster MOPPC124 [0.448 MB]

Paper	Title	Page
MOPPC096	Design and Implementation Aspects of the Control System at FHI FEL	324
	H. Junkes, W. Schöllkopf, M. Wesemann FHI, Berlin, Germany R. Lange HZB, Berlin, Germany R. Lange AES, Princeton, New Jersey, USA
	A new mid-infrared FEL has been commissioned at the Fritz-Haber-Institut in Berlin. It will be used for spectroscopic investigations of molecules, clusters, nanoparticles and surfaces. The oscillator FEL is operated with 15 - 50 MeV electrons from a normal-conducting S-band linac equipped with a gridded thermionic gun and a chicane for controlled bunch compression. Construction of the facility building with the accelerator vault began in April 2010. First lasing was observed on Februar 15th, 2012. * The EPICS software framework was chosen to build the control system for this facility. The industrial utility control system is integrated using BACnet/IP. Graphical operator and user interfaces are based on the Control System Studio package. The EPICS channel archiver, an electronic logbook, a web based monitoring tool, and a gateway complete the installation. This paper presents design and implementation aspects of the control system, its capabilities, and lessons learned during local and remote commissioning. * W. Schöllkopf et al., FIRST LASING OF THE IR FEL AT THE FRITZ-HABER-INSTITUT, BERLIN, Conference FEL12
	Poster MOPPC096 [10.433 MB]

MOPPC124	Optimizing EPICS for Multi-Core Architectures	399
	R. Lange, F. Di Maio ITER Organization, St. Paul lez Durance, France R. Lange HZB, Berlin, Germany
	Funding: Work supported by German Bundesministerium für Bildung und Forschung and Land Berlin. EPICS is a widely used software framework for real-time controls in large facilities, accelerators and telescopes. Its multithreaded IOC (Input Output Controller) Core software has been developed on traditional single-core CPUs. The ITER project will use modern multi-core CPUs, running the RHEL Linux operating system in its MRG-R real-time variant. An analysis of the thread handling in IOC Core shows different options for improving the performance and real-time behavior, which are discussed and evaluated. The implementation is split between improvements inside EPICS Base, which have been merged back into the main distribution, and a support module that makes full use of these new features. This paper describes design and implementation aspects, and presents results as well as lessons learned.
	Poster MOPPC124 [0.448 MB]

MOPPC148	Not Dead Yet: Recent Enhancements and Future Plans for EPICS Version 3	457
	A.N. Johnson, J.B. Anderson ANL, Argonne, USA M.A. Davidsaver BNL, Upton, New York, USA R. Lange HZB, Berlin, Germany
	Funding: Work supported by U.S. Department of Energy, Office of Science, under Contract No. DE-AC02-06CH11357. The EPICS Version 4 development effort* is not planning to replace the current Version 3 IOC Database or its use of the Channel Access network protocol in the near future. Interoperability is a key aim of the V4 development, which is building upon the older IOC implementation. EPICS V3 continues to gain new features and functionality on its Version 3.15 development branch, while the Version 3.14 stable branch has been accumulating minor tweaks, bug fixes, and support for new and updated operating systems. This paper describes the main enhancements provided by recent and upcoming releases of EPICS Version 3 for control system applications. * Korhonen et al, "EPICS Version 4 Progress Report", this conference.
	Poster MOPPC148 [5.067 MB]

TUCOCB04	EPICS Version 4 Progress Report	956
	T. Korhonen PSI, Villigen PSI, Switzerland L.R. Dalesio, N. Malitsky, G. Shen BNL, Upton, Long Island, New York, USA D.G. Hickin, J. Rowland Diamond, Oxfordshire, United Kingdom M.R. Kraimer Self Employment, Private address, USA R. Lange HZB, Berlin, Germany M. Sekoranja Cosylab, Ljubljana, Slovenia G.R. White SLAC, Menlo Park, California, USA
	EPICS Version 4 is the next major revision of the Experimental Physics and Industrial Control System, a widely used software framework for controls in large facilities, accelerators and telescopes. The primary goal of Version 4 is to improve support for scientific applications by augmenting the control-centered EPICS Version 3 with an architecture that allows building scientific services on top of it. Version 4 provides a new standardized wire protocol, support of structured types, and parametrized queries. The long-term plans also include a revision of the IOC core layer. The first set of services like directory, archive retrieval, and save set services aim to improve the current EPICS architecture and enable interoperability. The first services and applications are now being deployed in running facilities. We present the current status of EPICS V4, the interoperation of EPICS V3 and V4, and how to create services such as accelerator modelling, large database access, etc. These enable operators and physicists to write thin and powerful clients to support commissioning, beam studies and operations, and opens up the possibility of sharing applications between different facilities.
	Slides TUCOCB04 [1.937 MB]

TUCOCB05	Device Definition and Composite Device Views on Top of the Flat EPICS Namespace
	L.R. Dalesio, K. Shroff, L. Yang BNL, Upton, Long Island, New York, USA R. Lange HZB, Berlin, Germany
	The EPICS (Experimental Physics and Industrial Control System) IOC (Input Output Controller) Core database represents a process on signal level, presenting a flat view of possibly complex devices. This signal level interface is an easily agreed upon common denominator, allowing drivers, signal records, and processes on these signals to be standardized across EPICS installations. However, it is also necessary to represent a device in its different aspects. Currently this requires a-priori knowledge of all individual channels that are included in a device by each client. This paper discusses device orientation based on the new EPICS Version 4 database and middle layer services along with the ecosystem to manage these views.
	Slides TUCOCB05 [1.144 MB]

MOPPC124	Optimizing EPICS for Multi-Core Architectures	399
	R. Lange, F. Di Maio ITER Organization, St. Paul lez Durance, France R. Lange HZB, Berlin, Germany
	Funding: Work supported by German Bundesministerium für Bildung und Forschung and Land Berlin. EPICS is a widely used software framework for real-time controls in large facilities, accelerators and telescopes. Its multithreaded IOC (Input Output Controller) Core software has been developed on traditional single-core CPUs. The ITER project will use modern multi-core CPUs, running the RHEL Linux operating system in its MRG-R real-time variant. An analysis of the thread handling in IOC Core shows different options for improving the performance and real-time behavior, which are discussed and evaluated. The implementation is split between improvements inside EPICS Base, which have been merged back into the main distribution, and a support module that makes full use of these new features. This paper describes design and implementation aspects, and presents results as well as lessons learned.
	Poster MOPPC124 [0.448 MB]