ICALEPCS2019 - List of Authors (Andreassen, O.O.)

Paper	Title	Page
WEPHA026	Integrating COTS Equipment in the CERN Accelerator Domain	1136
	O.Ø. Andreassen, C. Charrondière, K. Develle, A. Rijllart, R.E. Rossel, J. Steen, J. Tagg, T. Zilliox CERN, Geneva, Switzerland
	Successful integration of industrial equipment in the CERN accelerator complex relies mainly on 3 key components. The first part is the Controls Middleware (CMW). That provides a common communication infrastructure for the accelerator controls at CERN. The second part is timing. To orchestrate and align electronic and electrical equipment across the 27 km Large Hadron Collider (LHC) at sub nanosecond precision, an elaborate timing scheme is needed. Every component has to be configured and aligned within milliseconds and then trigger in perfect harmony with each other. The third and last bit is configuration management. The COTS devices have to be kept up to date, remotely managed and compatible with each other at all times. This is done through a combination of networked Pre eXecution Environments (PXE) mounting network accessible storage on the front ends, where operating systems and packages can be maintained across systems. In this article we demonstrate how COTS based National Instruments PXI and cRIO systems can be integrated in the CERN accelerator domain for measurement and monitoring systems.
	Poster WEPHA026 [4.690 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA026
About •	paper received ※ 27 September 2019 paper accepted ※ 19 October 2019 issue date ※ 30 August 2020
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPHA027	Evaluation of Timing and Synchronization Techniques on NI CompactRIO Platforms	1141
	O.Ø. Andreassen, C. Charrondière, K. Develle, R.E. Rossel, T. Zilliox CERN, Geneva, Switzerland
	For distributed data acquisition and control system, clock synchronization between devices is key. The internal CPU clock of a CompactRIO has an accuracy of 40 ppm at 25 degree Celsius, which can cause up to 3 sec of drift per day. To compensate for this drift, common practice is to use a central clock (such as NTP) to synchronize the systems. In addition, the cRIO has an onboard FPGA which has its own 40 MHz clock. This clock is not synchronized with the CPU, and will also cause time drift. For short measurements, this drift is usually negligible, but for continuous data acquisition systems, running 24/7, the accumulated error has to be compensated. This article will show how we synchronized all clocks across multiple systems used for monitoring seismic activities in the LHC underground and surface areas. It will also describe the mechanism used to cross check synchronization by using the CERN developed White Rabbit timing system.
	Poster WEPHA027 [0.567 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA027
About •	paper received ※ 26 September 2019 paper accepted ※ 19 October 2019 issue date ※ 30 August 2020
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPHA129	Synchronizing LabVIEW Development and Deployment Environment	1394
	O.Ø. Andreassen, C. Charrondière, M.K. Miskowiec, H. Reymond, A. Rijllart CERN, Geneva, Switzerland
	LabVIEW with its graphical approach is suited for engineers used to design and implement systems based on schematics and designs. Being a graphical language, it can be challenging to keep track of drivers, runtime engines, deployments and configurations since most of the tools on the market aimed towards this are implemented for textual languages. Configuration management is possible in the development environment via version control systems such as perforce, however at CERN and in the open source software development community in general, the tendency is moving towards Git. In this paper we demonstrate how the combination of automated builds, packaging, versioning and consistent deployment can further ease and speed up development, while ensure robustness and coherency across systems. We also show how an in-house built tool called "RADE Installer" synchronizes both development environments and drivers across workstations, empowering graphical development at CERN, by merging the open source toolchains with the workflow of LabVIEW. RADE installer represents definitively a solution for LabVIEW to keep track of drivers, runtime engines, deployments and configurations.
	Poster WEPHA129 [2.789 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA129
About •	paper received ※ 27 September 2019 paper accepted ※ 09 October 2019 issue date ※ 30 August 2020
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

Paper

Title

Page

Integrating COTS Equipment in the CERN Accelerator Domain

1136

O.Ø. Andreassen, C. Charrondière, K. Develle, A. Rijllart, R.E. Rossel, J. Steen, J. Tagg, T. Zilliox
CERN, Geneva, Switzerland

Successful integration of industrial equipment in the CERN accelerator complex relies mainly on 3 key components. The first part is the Controls Middleware (CMW). That provides a common communication infrastructure for the accelerator controls at CERN. The second part is timing. To orchestrate and align electronic and electrical equipment across the 27 km Large Hadron Collider (LHC) at sub nanosecond precision, an elaborate timing scheme is needed. Every component has to be configured and aligned within milliseconds and then trigger in perfect harmony with each other. The third and last bit is configuration management. The COTS devices have to be kept up to date, remotely managed and compatible with each other at all times. This is done through a combination of networked Pre eXecution Environments (PXE) mounting network accessible storage on the front ends, where operating systems and packages can be maintained across systems. In this article we demonstrate how COTS based National Instruments PXI and cRIO systems can be integrated in the CERN accelerator domain for measurement and monitoring systems.

Poster WEPHA026 [4.690 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA026

About •

paper received ※ 27 September 2019 paper accepted ※ 19 October 2019 issue date ※ 30 August 2020

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPHA027

Evaluation of Timing and Synchronization Techniques on NI CompactRIO Platforms

1141

O.Ø. Andreassen, C. Charrondière, K. Develle, R.E. Rossel, T. Zilliox
CERN, Geneva, Switzerland

For distributed data acquisition and control system, clock synchronization between devices is key. The internal CPU clock of a CompactRIO has an accuracy of 40 ppm at 25 degree Celsius, which can cause up to 3 sec of drift per day. To compensate for this drift, common practice is to use a central clock (such as NTP) to synchronize the systems. In addition, the cRIO has an onboard FPGA which has its own 40 MHz clock. This clock is not synchronized with the CPU, and will also cause time drift. For short measurements, this drift is usually negligible, but for continuous data acquisition systems, running 24/7, the accumulated error has to be compensated. This article will show how we synchronized all clocks across multiple systems used for monitoring seismic activities in the LHC underground and surface areas. It will also describe the mechanism used to cross check synchronization by using the CERN developed White Rabbit timing system.

Poster WEPHA027 [0.567 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA027

About •

paper received ※ 26 September 2019 paper accepted ※ 19 October 2019 issue date ※ 30 August 2020

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPHA129

Synchronizing LabVIEW Development and Deployment Environment

1394

O.Ø. Andreassen, C. Charrondière, M.K. Miskowiec, H. Reymond, A. Rijllart
CERN, Geneva, Switzerland

LabVIEW with its graphical approach is suited for engineers used to design and implement systems based on schematics and designs. Being a graphical language, it can be challenging to keep track of drivers, runtime engines, deployments and configurations since most of the tools on the market aimed towards this are implemented for textual languages. Configuration management is possible in the development environment via version control systems such as perforce, however at CERN and in the open source software development community in general, the tendency is moving towards Git. In this paper we demonstrate how the combination of automated builds, packaging, versioning and consistent deployment can further ease and speed up development, while ensure robustness and coherency across systems. We also show how an in-house built tool called "RADE Installer" synchronizes both development environments and drivers across workstations, empowering graphical development at CERN, by merging the open source toolchains with the workflow of LabVIEW. RADE installer represents definitively a solution for LabVIEW to keep track of drivers, runtime engines, deployments and configurations.

Poster WEPHA129 [2.789 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2019-WEPHA129

About •

paper received ※ 27 September 2019 paper accepted ※ 09 October 2019 issue date ※ 30 August 2020

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)