ESS Timing System Plans Timo Korhonen Chief Engineer, Integrated Control System Division www.europeanspallationsource.se Nov.27, 2014.

Slides:



Advertisements
Similar presentations
01/11/2002SNS Software Final Design Review1 V123S Event Link Encoder, Transmission System and PLL Receiver Thomas M. Kerner (BNL) SNS Global Controls.
Advertisements

Stephanie Allison LCLS Event System 14 June LCLS Event System Outline HW Block Diagram Timing Requirements Time Lines EVG.
ESS Timing System Plans and Requirements Timo Korhonen Chief Engineer, Integrated Control System Division May 19, 2014.
Status of the European Spallation Source Timo Korhonen Chief Engineer, Integrated Control System Division October 21, 2014.
Dirk Zimoch, EPICS Collaboration Meeting, Vancouver 2009 Real-Time Data Transfer using the Timing System (Original slides and driver code by Babak Kalantari)
Dayle Kotturi and Stephanie Allison Facility Advisory Committee Meeting April 20-21,
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
V4 – Executive Summary 1.Provide online add/delete of I/O to support continuous operation. 2.Provide redundant control of remote I/O to support improved.
Ion source RF system Andy Butterworth BE/RF Mauro Paoluzzi BE/RF 14/11/2013Linac4 ion source review.
SNS Integrated Control System EPICS Collaboration Meeting SNS Machine Protection System SNS Timing System Coles Sibley xxxx/vlb.
LHC Beam Dump System Technical Audit Trigger Synchronisation Unit.
ESS Controls Infrastructure Timo Korhonen ICS Feb.. 4, 2015.
Wir schaffen Wissen – heute für morgen Babak Kalantari, PSI EPICS Meeting, Saclay Paul Scherrer Institut SwissFEL Timing System Babak Kalantari.
SNS Integrated Control System SNS Timing Master LA-UR Eric Bjorklund.
Distribution of machine parameters over GMT in the PS, SPS and future machines J. Serrano, AB-CO-HT TC 6 December 2006.
LCLS Timing Software and Plan 1 Controls Timing Workshop EPICS Collaboration Meeting SLAC LCLS Timing Software and Plan April Kukhee Kim.
Micro-Research Finland Oy Timing System Modules Jukka Pietarinen EPICS Collaboration Meeting, Argonne, June 2006.
Micro-Research Finland Oy MRF Timing System Jukka Pietarinen Timing Workshop CERN February 2008.
RF voltage and frequency interlocks A. Butterworth MP review 17/6/2010.
TE-MPE-EP, RD, 06-Dec QPS Data Transmission after LS1 R. Denz, TE-MPE-EP TIMBER PM WinCC OA Tsunami warning:
General Time Update David Thompson Epics Collaboration Meeting June 14, 2006.
1 Timo Korhonen PSI 1. Concepts revisited…again 3. New (Diamond) cards features and status 4. EPICS interface 5. Conclusions SLS & Diamond Timing System.
SNS Integrated Control System Timing Clients at SNS DH Thompson Epics Spring 2003.
Issues in Accelerator Control Bob Dalesio, December 23, 2002.
EPICS Collaboration Meeting Fall PAL October 22 ~ 26, 2012 LCLS Timing System (pattern design, evGUI, and high level) Mike Zelazny for LCLS Timing.
Timing Requirements for Spallation Neutron Sources Timing system clock synchronized to the storage ring’s revolution frequency. –LANSCE: MHz.
Fast Fault Finder A Machine Protection Component.
BEPC II TIMING SYSTEM EPICS Seminar Presented by Ma zhenhan IHEP 20.August 2002.
ESS Timing System Prototype 2012 Miha Reščič, ICS
Page Beam Instrumentation mini- workshop Conclusions from the Hardware, Timing and MPS mini-workshop Lund, Miha Reščič Deputy Head of
ESS (vacuum) control system Daniel Piso Controls Division February 20, 2013.
Daniel Piso Fernández Some Ideas about Integration Support Cases and PLC Activities at Controls Division.
ICS interfaces Timo Korhonen ICS Apr 22, 2015.
Control System Tools for Beam Commissioning Timo Korhonen Controls Division Chief Engineer April 8, 2014.
ESS LLRF and Beam Interaction
INTRODUCTION TO WIRELESS SENSOR NETWORKS
Giovanna Lehmann Miotto CERN EP/DT-DI On behalf of the DAQ team
RF acceleration and transverse damper systems
SLAC I&C Division / EE Department
Data providers Volume & Type of Analysis Kickers
SNS Status Report Karen S. White 10/15/08.
Beam-Synchronous Data Acquisition (BS-DAQ)
SLC-Aware IOC LCLS Collaboration Jan 26, 2005
SLS Timing Master Timo Korhonen, PSI.
LCLS Timing Software and Plan
Timing and Event System S. Allison, M. Browne, B. Dalesio, J
WP02 PRR: Master Oscillator and RF Reference Distribution
Commissioning and Testing the LHC Beam Interlock System
Shanshui Yang1, Li Liu1, Xi Jiang1, Li Wang1, Weifang Liu2
Development of built-in diagnostics in the RADE framework (EN2746)
Event Displays for EVR IOCs
SNS Timing System EPICS Workshop April 28, 2005 Coles Sibley
LCLS Event System - Software
Timing System GSI R. Bär / U. Krause 15. Feb. 2008
LHCCWG Meeting R. Alemany, M. Lamont, S. Page
Interlocking of CNGS (and other high intensity beams) at the SPS
Timing and Event System for the LCLS Electron Accelerator
Next Linear Collider Test Accelerator and EPICS
A Virtual Implementation of VELA (CLARA)
ICS update 7th Experiment Control Workshop
The CMS Tracking Readout and Front End Driver Testing
SLS & Diamond Timing System update
Timing and Event System S. Allison, M. Browne, B. Dalesio, J
Towards final BCM firmware and interface to MPS Hooman Hassanzadegan BI forum, Nov 2018, Lund
Control Systems for the APTM and GRID
Operation of Target Safety System (TSS)
Breakout Session: Controls
LCLS Machine Protection System
Timing and Event System Status DOE Review of the LCLS Project SC5 - Controls Systems Breakout Session S. Allison, M. Browne, B. Dalesio, J. Dusatko,
Rack installation and local tests for the MEBT Chopper Rack
Presentation transcript:

ESS Timing System Plans Timo Korhonen Chief Engineer, Integrated Control System Division Nov.27, 2014

Timing system requirements Accelerator parameters for timing – Front end frequency is 352 MHz (CERN Standard) – High energy section is at 704 MHz – Master oscillator at 88 MHz (btw: we could also divide from 352 MHz – or even 704 MHz, for that matter) – Repetition rate 14 Hz Dictated by neutron choppers No need to do AC sync (I have been told) – Repetition rate must be programmable No RF pulsing when no beam (power consumption) But “some” devices need still 14 Hz triggers (TBC) 2

Timing system requirements Typical requirements for a pulsed accelerator – Triggering of devices – Synchronous acquisition and data handling Long pulses mean a lot of data per pulse! – Distributing beam parameters Machine mode: where will the beam go (target, tuning dump) Beam mode: pulse intensity, length – Repetition rate control Possibly even single pulses – if possible – Timestamping of data ESS challenge: – Interfacing with the machine protection system – Ensuring that machine and beam modes are propagated correctly to all receivers – Synchronization with the target wheel (not as big an issue as it might seem, though) 3

Timing system requirements The typical requirements are “easy” – 14 Hz (vs 100 Hz or higher) repetition rate – Long pulses create some issues in data handling For control system in general, not too much for timing More work in software side – Ramping up the beam power; intensity and pulse length – Beam mode handling – Beam synchronous data handling Interfacing to MPS is critical – Or, find a way to make MPS totally independent But I cannot yet imagine how that could be done in a reasonable way 4

Functions 5 The ESS timing system (aka event system) can: Distribute synchronous triggers to a (very) large number of devices Triggers can be pulses, electrical or optical, with different properties that can be programmed at the receiving end Triggers can also be software, triggering some action in the IOC (Control Box) By “processing” EPICS channels that read out data, write values, calculate, whatever the IOC is able to do. Can also be non-EPICS actions. Distribute (limited amounts of) data to many receivers synchronously and simultaneously This happens in parallel to the trigger distribution, no effect on accuracy. Limited amount = 2 kilobytes in one transmission. The raw speed depends on setup but can be up to 125 MB/sec (even faster in the ESS generation hardware) A single transmission takes some microseconds (~2 us for the raw transmission) Distribute synchronous timestamps (long story to explain how this works) Generate (programmable) sequences of triggers (events), RF synchronized Accept asynchronous inputs to generate events Synchronize to an external input trigger with optional phase adjustment And many more things…(distribute clock signals, take in interlock inputs,…)

Structure of the system Fan-out system can (and will) have many levels. Synchronization accuracy will not be affected by how many levels there are The (accelerator) synchronization frequency (of 88 MHz) will be fed into the master event generator and used as the system clock. Downstream will be synchronized to that. The 14 Hz operating frequency will be generated by a method (TBD, e.g., target wheel rotation) and also fed into the event generator Events and (limited amounts of) data can also flow upstream (optionally) Master Event Generator RF Generator fanout Event receiver Event receiver 88 MHz fanout Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Triggers Software synch (IRQ) Timestamps Data Control & setup

Synchronous data collection 7 Master Event Generator RF Generator fanout Event receiver Event receiver 88 MHz fanout Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver Event receiver I/O CPU Event receiver Event receiver I/O CPU Event receiver Event receiver I/O CPU Each IOC (control box) receives the same events Event triggers reading out a piece of data (detector, AD converter, status bit/word) Data is timestamped and put into a “silo” (possibly with pulse numbering, TBD) Data can be streamed out (continuous recording) or read out as chunks (finite length)

Issues to be considered Synchronizing with “slow” devices with no EVR – PLCs, etc. – We need to be able to correlate data – NTP server in EVG IOC? Is it sufficient? Handling user’s devices – Oscilloscopes, etc. (known issue) Access to API & hardware interfaces? – Purpose-built devices: detectors, etc. No standard interfaces There is still time to think about this, though. – Integrate EVR directly into user hardware is one possibility. 8

Summary ESS timing requirements are not too different from other pulsed accelerators Machine protection is a big issue, though – One single mis-steered pulse will break the machine Platform (form factor) is pending final decision – Lots of push for microTCA, though – How to integrate other devices? Project timespan is an issue – We are building now something that will be in full use after 10 years, and have an expected lifetime of 40 years – Roadmap for upgrades and technology refresh Collaboration is very much appreciated! – Sharing of knowledge, applications, ideas… 9