Search NASA⌕ Search

Engineering topics

Neswold, Richard

Publications and source records attributed to Neswold, Richard.

Controls at the Fermilab PIP-II Superconducting Linac

PIP-II is an 800 MeV superconducting RF linac under development at Fermilab. As the new first stage in our accelerator chain, it will deliver high-power beam to multiple experiments simultaneously and thus drive Fermilab’s particle physics program for years to come. In a pivot for Fermilab, controls for PIP-II are based on EPICS instead of ACNET, the legacy control system for accelerators at the lab. This paper discusses the status of the EPICS controls work for PIP-II. We describe the EPICS tools selected for our system and the experience of operators new to EPICS. We introduce our continuous integration / continuous development environment. We also describe some efforts at cooperation between EPICS and ACNET, or efforts to move towards a unified interface that can apply to both control systems.

43 PARTICLE ACCELERATORS↗

Beam Commissioning and Integrated Test of the PIP-II Injector Test Facility

The PIP-II Injector Test (PIP2IT) facility is a near-complete low energy portion of the Superconducting PIP-II linac driver. PIP2IT comprises the warm front end and the first two PIP-II superconducting cryomodules. PIP2IT is designed to accelerate a 2 mA H⁻ beam to an energy of 20 MeV. The facility serves as a testbed for a number of advanced technologies required to operate PIP-II and provides an opportunity to gain experience with commissioning of the superconducting linac, significantly reducing project technical risks. Some PIP2IT components are contributions from international partners, who also lend their expertise to the accelerator project. The project has been successfully commissioned with the beam in 2021, demonstrating the performance required for the LBNF/DUNE. In this paper, we describe the facility and its critical systems. We discuss our experience with the integrated testing and beam commissioning of PIP2IT, and present commissioning results. This important milestone ushers in a new era at Fermilab of proton beam delivery using superconducting radio-frequency accelerators.

43 PARTICLE ACCELERATORS↗

Machine Protection System Research and Development for the Fermilab PIP-II Proton Linac

PIP-II is a high intensity proton linac being design to support a world-leading physics program at Fermilab. Initially it will provide high intensity beams for Fermilab's neutrino program with a future extension to other applications requiring an upgrade to CW linac operation (e.g. muon experiments). The machine is conceived to be 2 mA CW, 800 MeV H⁻ linac capable of working initially in a pulse (0.55 ms, 20 Hz) mode for injection into the existing Booster. The planned upgrade to CW operation implies that the total beam current and damage potential will be greater than in any present HEP hadron linac. To mitigate the primary technical risk and challenges associated PIP-II an integrated system test for the PIP-II front-end technology is being developed. As part of the R&D a robust machine protection system (MPS) is being designed. This paper describes the progress and challenges associated with the MPS.

43 PARTICLE ACCELERATORS↗

Preventing Run-Time Bugs at Compile-Time Using Advanced C++

When writing software, we develop algorithms that tell the computer what to do at run-time. Our solutions are easier to understand and debug when they are properly modeled using class hierarchies, enumerations, and a well-factored API. Unfortunately, even with these design tools, we end up having to debug our programs at run-time. Worse still, debugging an embedded system changes its dynamics, making it tough to find and fix concurrency issues. This paper describes techniques using C++ to detect run-time bugs *at compile time*. A concurrency library, developed at Fermilab, is used for examples in illustrating these techniques.

43 PARTICLE ACCELERATORS↗

The Machine Protection System for the Fermilab Accelerator Science and Technology Facility

The Machine Protection System (MPS) for the Fermilab Accelerator Science and Technology Facility (FAST) has been implemented and tested. The system receives signals from several subsystems and devices which conveys the relevant status needed to the safely operate the accelerator. Logic decisions are made based on these inputs and some predefined user settings which in turn controls the gate signal to the laser of the photo injector. The inputs of the system have a wide variety of signal types, encoding methods and urgencies for which the system is designed to accommodate. The MPS receives fast shutdown (FSD) signals generated by the beam loss system and inhibits the beam or reduces the beam intensity within a macropulse when the beam losses at several places along the accelerator beam line are higher than acceptable values. TTL or relay contact signals from the vacuum system, toroids, magnet systems etc., are chosen with polarities that ensure safe operation of the accelerator from unintended events such as cable disconnection in the harsh industrial environment of the experimental hall. A RS422 serial communication scheme is used to interface the operation permit generator module and a large number of movable devices each reporting multi-bit status. The system also supports operations at user defined lower beam levels for system conunissioning. The machine protection system is implemented with two commercially available off-the-shelf VMEbus based modules with on board FPGA devices. The system is monitored and controlled via the VMEbus by a single board CPU

Wu, Jinyuan↗

Beam Trail Tracking at Fermilab

We present a system for acquiring and sorting data from select devices depending on the destination of each particular beam pulse in the Fermilab accelerator chain. The 15 Hz beam that begins in the Fermilab ion source can be directed to a variety of additional accelerators, beam lines, beam dumps, and experiments. We have implemented a data acquisition system that senses the destination of each pulse and reads the appropriate beam intensity devices so that profiles of the beam can be stored and analysed for each type of beam trail. We envision utilizing this data long term to identify trends in the performance of the accelerators

Nicklaus, Dennis J.↗

An Erlang-Based Front End Framework for Accelerator Controls

We have developed a new front-end framework for the ACNET control system in Erlang. Erlang is a functional programming language developed for real-time telecommunications applications. The primary task of the front-end software is to connect the control system with drivers collecting data from individual field bus devices. Erlang's concurrency and message passing support have proven well-suited for managing large numbers of independent ACNET client requests for front-end data. Other Erlang features which make it particularly well-suited for a front-end framework include fault-tolerance with process monitoring and restarting, real-time response,and the ability to change code in running systems. Erlang's interactive shell and dynamic typing make writing and running unit tests an easy part of the development process. Erlang includes mechanisms for distributing applications which we will use for deploying our framework to multiple front-ends, along with a configured s et of device drivers. We've developed Erlang code to use Fermilab's TCLK event distribution clock and Erlang's interface to C/C++ allows hardware-specific driver access.

43 PARTICLE ACCELERATORS↗