SLAC Controls Evolution - DESY - MPY-Group
SLAC Controls Evolution - DESY - MPY-Group
SLAC Controls Evolution - DESY - MPY-Group
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Outline<br />
January 2005<br />
<strong>SLAC</strong> <strong>Controls</strong> <strong>Evolution</strong><br />
Incorporating the LCLS<br />
Ron Chestnut, January 2005<br />
(borrowed heavily from P. Krejcik and B. Dalesio)<br />
The original SLC control system<br />
The PEP-II upgrade<br />
EPICS at <strong>SLAC</strong><br />
The LCLS project<br />
LCLS <strong>Controls</strong> Integration<br />
Conclusions<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
The SLC Control System<br />
Started in 1982<br />
VAX/VMS-based<br />
Broadband network (pre-ethernet)<br />
Multibus-1 homed front end computers<br />
Rich set of applications<br />
Mixture of Fortran, PLM, Assembler, C<br />
Very complex timing, beam control system<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
The SLC Applications<br />
Model based<br />
Adaptive feedbacks<br />
Beam pulse coordinated data acquisition<br />
Complex “correlation plots”<br />
Multiknobs<br />
Button Macros<br />
Monolithic application<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Why the VMS apps are so good<br />
VMS data are kept fresh (asynchronously)<br />
DB Access takes about one microsecond<br />
4-deep in-memory hierarchical DB<br />
VMS Alpha<br />
DB<br />
Micro with<br />
Part of Db<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
The PEP-II Upgrade<br />
Project started about 1995<br />
Blue ribbon commission looked at EPICS<br />
Decided to stay with SLC system<br />
Attachment to applications on VMS<br />
Lack of experience with EPICS<br />
Need to ensure CS availability<br />
RF systems done in VXI – EPICS a natural<br />
Injection control also EPICS<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
EPICS – an international collaboration<br />
Started at LANL<br />
In the US: APS, TJNAF, SNS, LBL, ORNL<br />
Worldwide: KEK, BESSY, <strong>DESY</strong>, DIAMOND<br />
SLS, Frascatti, BEPC, Pohang, Shanghai<br />
Toolkit for building control systems<br />
Distributed, OSI<br />
vxWorks, Linux, RTEMS, XP, ….<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
PEP-II e + e - Collider<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
EPICS in PEP-II<br />
12 RF stations<br />
Most VXI modules are <strong>SLAC</strong>-built<br />
Allen Bradley for status and slow control<br />
4 IOCs for injection control<br />
2 VXI crates for Bunch Current Monitors<br />
VME crate for injection control<br />
GPIB controller<br />
BaBar (detector) slow control (many IOCs)<br />
Tune Tracker application<br />
Longitudinal feedback system (by Fox et al.)<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
What is NOT in EPICS for PEP-II<br />
Standard analog and digital support<br />
Magnet control<br />
Beam Position Monitors<br />
All “standard” devices on which the rich set<br />
of VMS applications are dependent<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
<strong>SLAC</strong> EPICS Now<br />
PEP-II support<br />
Damping ring RF (Allen Bradley)<br />
NLCTA/8-Pack (pre ILC)<br />
“Soft IOCs”<br />
General intermediate comutational support<br />
“Scratch” areas for display/printing support<br />
Ethernet GPIB applications<br />
Interface 3 rd Party SW (e.g. Labview-based)<br />
Comfort level much higher across the lab<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Current EPICS Integration<br />
EPICS has access to SLC database<br />
Many SLC applications have EPICS<br />
Channel Access capability<br />
Most ad-hoc additions (Gated cameras,<br />
Tune measurements) supported via EPICS<br />
Each SLC application must be modified to<br />
access EPICS data<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Disparate Architectures<br />
RMX<br />
RMX<br />
RMX<br />
Host Host Host<br />
RMX<br />
VMS<br />
Client & Host<br />
EPICS Support<br />
for VMS<br />
RMX<br />
Client Client Client<br />
RMX<br />
SLC Central Architecture<br />
January 2005<br />
EPICS Distributed Architecture<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Linac Coherent Light Source<br />
Project Description<br />
Near Hall<br />
FEL Center<br />
Far Hall<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Linac Coherent Light Source<br />
Uses:<br />
a new injector and<br />
the last 1 km of the <strong>SLAC</strong> linac<br />
Undulator FFTB Tunnel <strong>SLAC</strong> HallLinac<br />
Near Hall<br />
FEL Center<br />
Cathode Load<br />
Lock<br />
RF<br />
Gun<br />
Gun-to-Linac<br />
Two Chicanes for bunch compression<br />
L0-1<br />
L0 Linacs<br />
Far Hall<br />
Gun Solenoid<br />
Linac Solenoid<br />
L0-2<br />
Matching Section<br />
Scale:<br />
5 meters<br />
Quadrupole,<br />
typ.<br />
RF Transverse<br />
Deflector<br />
January 2005<br />
Linac Center<br />
Line<br />
Ron Chestnut<br />
Sector 20 Linacs<br />
Emittance<br />
ronc@slac.stanford.edu<br />
Wire Scanners<br />
Energy Wire<br />
Scanner & OTR<br />
DL1 Bend<br />
Sector 21-1B<br />
Straight Ahead<br />
Tune-Up Dump
The World’s First Hard X-ray X<br />
Laser<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Capabilities<br />
Spectral coverage: 0.15-1.5 nm<br />
To 0.5 Å in 3 rd harmonic<br />
Peak Brightness: 10 33<br />
Photons/pulse: 10 12<br />
Average Brightness: 3 x 10 22<br />
Pulse duration:
Upstream linac<br />
RG Gun<br />
L0<br />
Ti:Sa laser<br />
Laser Heater<br />
RF PhotoInjector 135 MeV<br />
ε x,y = 1mm mrad, q=1 nC<br />
σ z = 3ps, σ δ ≈ 0.05 %<br />
Linac1<br />
X-band harmonic cavity<br />
BC1 chicane 250 MeV<br />
σ z = 0.63 ps<br />
BC2 4.5 GeV<br />
Linac2<br />
σ z = 0.07 ps<br />
Existing <strong>SLAC</strong> structure<br />
warm, copper linac<br />
S-band 2856 MHz<br />
120 Hz<br />
1 km<br />
Linac3<br />
LoLa transverse cavity<br />
LTU 14.1 GeV<br />
σ z = 0.07 ps, σ δ ≈ 0.01 %<br />
Undulator<br />
L =130 m<br />
X-rays<br />
1.5 Å<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
LCLS - Estimated Cost, Schedule<br />
$273M Total Estimated Cost<br />
$315M Total Project Cost<br />
FY2005 Long-lead purchases for injector, undulator<br />
FY2006 Construction begins<br />
FY2007 FEL Commissioning begins<br />
September 2008 Construction complete – operations begins<br />
CD-0<br />
CD-1 CD-2a<br />
CD-2b<br />
Title I<br />
Design<br />
Complete<br />
CD-3b<br />
XFEL<br />
Commissioning<br />
FY2001 FY2002 FY2003 2002 2003 FY2004 2004 FY2005 2005 FY2006 2006 FY2007 FY2008 FY2009<br />
Project Engineering Design<br />
Long-Lead<br />
Procurement<br />
CD-3a<br />
Construction<br />
Operation<br />
CD-4<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Personnel – Resources<br />
Ctl. Elec. Engineer<br />
Ctl. Sr. Elec. Tech.<br />
Ctl. Elec Tech.<br />
Pwr. Elec. Engineer<br />
Pwr. Sr. Elec. Tech.<br />
Control Prog.<br />
2004<br />
2.42<br />
.56<br />
.07<br />
1.94<br />
.42<br />
.81<br />
2005<br />
10.37<br />
3.44<br />
.60<br />
1.39<br />
.86<br />
10.18<br />
2006<br />
8.12<br />
2.66<br />
2.20<br />
.32<br />
.31<br />
10.29<br />
2007<br />
6.07<br />
1.90<br />
4.63<br />
.51<br />
.72<br />
6.32<br />
2008<br />
3.26<br />
.77<br />
.62<br />
.10<br />
.05<br />
6.56<br />
Total<br />
30.24<br />
9.33<br />
8.12<br />
4.26<br />
2.37<br />
34.17<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
LCLS contributing labs<br />
Injector and linac – <strong>SLAC</strong><br />
Undulator – Argonne<br />
X-ray transport and diagnostics – Livermore<br />
Smaller contributions from other labs too<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
LCLS Team – new to <strong>SLAC</strong><br />
Division head from Argonne<br />
Much in common with SPEAR<br />
Development core from EPICS community<br />
SNS (itself a 5 lab collaboration)<br />
Argonne<br />
LANL<br />
SPEAR<br />
<strong>SLAC</strong> <strong>Controls</strong> (ESD)<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
LCLS Control System Goals<br />
Provide a fully integrated control system to support the<br />
construction, test, installation, integration, operation and<br />
automation of the LCLS Accelerator<br />
Standardize all devices and components across all<br />
subsystems.<br />
Identify all data either by pulse id, beam pulse related<br />
time stamp, or 500 msec rough time stamp.<br />
Full integration with the SLC – timing, use of LCLS<br />
data in SLC high level applications, and use of SLC data<br />
in LCLS<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Difference to PEP-II decision<br />
PEP-II needed to use fabulous suite of<br />
applications on VMS as is<br />
At that time we had very little EPICS<br />
experience<br />
LCLS will add two pieces to EPICS IOCs<br />
Timing interface to <strong>SLAC</strong> system<br />
“Spoofing” context in IOC which responds just<br />
like an SLC micro (SLC-Aware IOC)<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Global Hardware - Timing Boards<br />
476 MHz RF Reference<br />
SLC micro<br />
Master<br />
Pattern<br />
Generator<br />
FIDO<br />
119 MHz w/<br />
360 Hz fiducial<br />
128 bit beam codes at 360 Hz<br />
IOC<br />
C<br />
P<br />
U<br />
E<br />
V<br />
G<br />
E<br />
V<br />
R<br />
LLRF<br />
HPRF<br />
I/O<br />
Boards<br />
IOC<br />
C<br />
P<br />
U<br />
E<br />
V<br />
R<br />
Diag<br />
Event<br />
Generator<br />
(PIOP)<br />
16 triggers<br />
Event<br />
Receivers<br />
(PDU)<br />
16 triggers<br />
January 2005<br />
Beam Code + EPICS Time + EPICS Events<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Scientific timing requirements<br />
Maintaining saturation in the FEL<br />
Provide femtosecond timing for pumpprobe<br />
experiments<br />
Time stamp arrival of FEL pulse w.r.t. an optical<br />
laser pulse<br />
i.e. synchronize user laser with linac RF<br />
reference<br />
Coarse timing of RF bucket<br />
And jitter at subpicosecond level<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Functional Requirements<br />
Maximum Link Length<br />
2 Kilometers<br />
Timing Stability (Long Term) < 5 picoseconds<br />
Timing Jitter RMS<br />
< 0.5 picoseconds<br />
RF Phase Stability (1 second)<br />
< 0.07 deg. S-band<br />
RF Phase Stability (Long Term) < 5 picoseconds<br />
RF Phase Jitter RMS<br />
< 0.07 degree S-band<br />
Phase Transmission Frequency 2856 MHz<br />
Timing Resolution (Normal) 350 ps (S-band bucket)<br />
Timing Resolution (with vernier) 1 ps<br />
Required Frequency Stability 3x10e-9<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Integration with the SLC Control System<br />
MPG<br />
SLC<br />
Alpha<br />
All High<br />
Level<br />
Apps<br />
micro<br />
Camac<br />
I/O<br />
RF reference clock<br />
CAS<br />
Xterm Xterm<br />
Xterm<br />
Xterm<br />
SLC Net over Ethernet (Data Transfer)<br />
PNet (Pulse ID / User ID)<br />
E<br />
V<br />
G<br />
P<br />
N<br />
E<br />
T<br />
Timing<br />
Micro<br />
emulator<br />
CA Gateway<br />
I/OC<br />
(SLC-aware)<br />
Fast Feedback<br />
EPICS<br />
EPICS<br />
W/S EPICS<br />
W/S<br />
Distributed EPICS<br />
EPICS<br />
W/S WS<br />
Distributed W/S<br />
Applications<br />
Distributed<br />
Applications Distributed<br />
Applications High Level<br />
Applications<br />
Applications<br />
CA over Ethernet<br />
(EPICS Protocol)<br />
E<br />
V<br />
R<br />
Micro<br />
emulator<br />
I/OC<br />
(SLC-aware)<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Three kinds of front-end support<br />
Traditional <strong>SLAC</strong> Micros<br />
Old equipment only<br />
No new additions<br />
Traditional EPICS IOCs<br />
Totally new items<br />
No existing <strong>SLAC</strong> support<br />
SLC-Aware IOCs<br />
New equipment of old type<br />
Works also as traditional EPICS IOC<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Environment<br />
EPICS Release<br />
R/T OS<br />
Workstation OS<br />
EPICS ADE (CVS)<br />
Compilers<br />
Bug Report / Tracking<br />
Naming Standard<br />
Name Service<br />
Documentation<br />
Test stations<br />
3.14.n<br />
RTEMS<br />
LINUX<br />
Simple??<br />
GNU<br />
Artemis<br />
PEP II<br />
Name Server JLAB<br />
Web Area<br />
FFTB<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Client Tools<br />
Display Manager EDM<br />
Archiver<br />
Channel Archiver<br />
Alarm Handler ALH<br />
Message Logger CMLog<br />
Electronic Log Book <strong>DESY</strong>, Babar, JLAB?<br />
Stripchart<br />
StripTool<br />
Web based viewing SPEAR, A-Beans, JoiMint,AIDA??<br />
Image Analysis Matlab format?<br />
Save / Restore ?<br />
RDB<br />
SNS (leaning)<br />
Gateway<br />
3.14.6 Gateway<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
High Level Applications<br />
Matlab<br />
Available for Physicists<br />
Python<br />
Available for Physicists<br />
High Level Apps<br />
SLC<br />
Available in existing system<br />
XAL<br />
New direction<br />
Matlab based Growing group of users<br />
Top priorities to move into EPICS<br />
Which ones make the SLC-aware IOC easier<br />
Which are the most useful<br />
Which are the easiest to pick off<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Hardware Direction – Buy/Steal/Make<br />
In-House VME version of the PNET<br />
Commercial BPM - Echotek and Libera Electronics<br />
Community Timing System (Diamond/SLS/APS)<br />
Community Digital Power Supply Controller (SLS)<br />
Commercial LLRF - Digitizers<br />
Commercial Machine Protection System in PLC? 8msec<br />
Commercial Video – evaluate several options (30 Hz)<br />
Commercial Conventional Facilities through AB PLC<br />
Community Wire Scanners ??<br />
Commercial Fast feedback in shared memory?<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Summary<br />
We hope to base all of our hardware on developments<br />
from the community or those commercially available.<br />
Integration with the existing SLC system is a critical<br />
step to allow <strong>SLAC</strong> operators to use the existing tools<br />
while we are adopting and modifying replacements.<br />
We are using standard EPICS tools for core<br />
development and engineering interfaces.<br />
We are adopting all we can from the community and we<br />
will use our resources to extend them as we can.<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
LCLS Software Tasks – Standardize/Acquire<br />
Data Archiving to support all phases of the project<br />
Operator Display Tools / Synoptic, Plots, Waveform,<br />
Image<br />
Alarm Management<br />
Electronic Log<br />
High Level Application Support: Matlab, XAL, Python<br />
Control System Configuration Tools<br />
Relational Database Management in all project<br />
aspects<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Organizational Issues<br />
<strong>Controls</strong> Department (SW and HW) had always<br />
asked for requirements and provided solutions<br />
(PEP-I, SLC, PEP-II, NLCTA)<br />
LCLS is using <strong>Controls</strong> as one possible service<br />
provider<br />
Mixture of SPEAR, <strong>SLAC</strong>, and outside culture<br />
SNS model of project oversight is being used<br />
One engineer for each subsystem for whole machine<br />
All responsible engineers work directly for the LCLS<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Conclusion<br />
LCLS is providing the opportunity to move<br />
away from a two decade old solution.<br />
The SLC-Aware IOC solution provides a<br />
long-needed migration path.<br />
Old dogs can learn new tricks.<br />
Alte Baeume koennen doch umgepflanzt werden.<br />
January 2005<br />
Ron Chestnut<br />
ronc@slac.stanford.edu
Change language