Embed Size (px)
Citation preview
January 2005
SLAC Controls EvolutionIncorporating the LCLS
Ron Chestnut, January 2005(borrowed heavily from P. Krejcik and B. Dalesio)
OutlineThe original SLC control systemThe PEP-II upgradeEPICS at SLACThe LCLS projectLCLS Controls IntegrationConclusions
January 2005
The SLC Control SystemStarted in 1982VAX/VMS-basedBroadband network (pre-ethernet)Multibus-1 homed front end computersRich set of applicationsMixture of Fortran, PLM, Assembler, CVery complex timing, beam control system
January 2005
The SLC ApplicationsModel basedAdaptive feedbacksBeam pulse coordinated data acquisitionComplex “correlation plots”MultiknobsButton Macros
Monolithic application
January 2005
Why the VMS apps are so goodVMS data are kept fresh (asynchronously)DB Access takes about one microsecond4-deep in-memory hierarchical DB
VMS AlphaDB
Micro withPart of Db
January 2005
The PEP-II UpgradeProject started about 1995Blue ribbon commission looked at EPICSDecided to stay with SLC system
Attachment to applications on VMSLack of experience with EPICSNeed to ensure CS availability
RF systems done in VXI – EPICS a naturalInjection control also EPICS
January 2005
EPICS – an international collaborationStarted at LANLIn the US: APS, TJNAF, SNS, LBL, ORNLWorldwide: KEK, BESSY, DESY, DIAMONDSLS, Frascatti, BEPC, Pohang, Shanghai
Toolkit for building control systemsDistributed, OSI
vxWorks, Linux, RTEMS, XP, ….
January 2005
EPICS in PEP-II12 RF stations
Most VXI modules are SLAC-builtAllen Bradley for status and slow control
4 IOCs for injection control2 VXI crates for Bunch Current MonitorsVME crate for injection controlGPIB controller
BaBar (detector) slow control (many IOCs)Tune Tracker applicationLongitudinal feedback system (by Fox et al.)
January 2005
What is NOT in EPICS for PEP-IIStandard analog and digital supportMagnet controlBeam Position Monitors
All “standard” devices on which the rich set of VMS applications are dependent
January 2005
SLAC EPICS Now PEP-II supportDamping ring RF (Allen Bradley)NLCTA/8-Pack (pre ILC)“Soft IOCs”
General intermediate comutational support“Scratch” areas for display/printing supportEthernet GPIB applications
Interface 3rd Party SW (e.g. Labview-based)
Comfort level much higher across the lab
January 2005
Current EPICS Integration
EPICS has access to SLC databaseMany SLC applications have EPICS Channel Access capabilityMost ad-hoc additions (Gated cameras, Tune measurements) supported via EPICS
Each SLC application must be modified to access EPICS data
January 2005
Disparate Architectures
VMS
RMX RMXRMX
RMX
RMXRMX
Host Host Host
Client Client Client
Client & HostEPICS Supportfor VMS
SLC Central Architecture EPICS Distributed Architecture
January 2005
Linac Coherent Light Source
Project Description
Near Hall
Far Hall
FEL Center
January 2005 Linac CenterLine
Sector 20 Linacs
Straight AheadTune-Up Dump
Sector 21-1B
5 metersScale:
L0-1
L0-2
RF TransverseDeflector
EmittanceWire Scanners Energy Wire
Scanner & OTR
Matching Section
Quadrupole,typ.
RFGun
Cathode LoadLock
DL1 Bend
Linac Solenoid
Gun Solenoid
Gun-to-Linac
L0 Linacs
Linac Coherent Light Source
Uses:a new injector andthe last 1 km of the SLAC linac
SLAC Linac
Two Chicanes for bunch compression
FFTB Tunnel
Near Hall
Far Hall
FEL Center
Undulator Hall
January 2005
The World’s First Hard XThe World’s First Hard X--ray ray LaserLaser
January 2005
Capabilities
Upgrade – more bunches/pulse
Spectral coverage: 0.15-1.5 nm
Peak Brightness: 1033
Average Brightness: 3 x 1022
Pulse duration: <230 fs
Pulse repetition rate: 120 Hz
Photons/pulse: 1012
To 0.5 Å in 3rd harmonic
January 2005
Ti:Sa laserRG Gun
Laser HeaterLaser HeaterUpstream linacL0
Linac1
RF PhotoInjector 135 MeVεx,y = 1mm mrad, q=1 nCσz = 3ps, σδ ≈ 0.05 %
RF PhotoInjector 135 MeVεx,y = 1mm mrad, q=1 nCσz = 3ps, σσδδ ≈≈ 0.05 %0.05 %
Linac2
Linac3
BC1 chicane 250 MeVσz = 0.63 psBC1 chicane 250 MeVσz = 0.63 ps
Existing SLAC structurewarm, copper linacS-band 2856 MHz120 Hz
Existing SLAC structurewarm, copper linacS-band 2856 MHz120 Hz
X-band harmonic cavityX-band harmonic cavity
BC2 4.5 GeVσz = 0.07 ps
BC2 4.5 GeVσz = 0.07 ps
UndulatorL =130 mUndulatorL =130 m
X-rays1.5 Å
LTU 14.1 GeVσz = 0.07 ps, σδ ≈ 0.01 %
LTU 14.1 GeVσz = 0.07 ps, σσδδ ≈≈ 0.01 %0.01 %
1 km1 kmLoLa transverse cavityLoLa transverse cavity
January 2005
LCLS - Estimated Cost, ScheduleLCLS - Estimated Cost, Schedule$273M Total Estimated Cost$315M Total Project Cost
FY2005 Long-lead purchases for injector, undulatorFY2006 Construction beginsFY2007 FEL Commissioning beginsSeptember 2008 Construction complete – operations begins
2002 2003 2004 2005 2006 FY2008 FY2009
Construction Operation
FY2001 FY2002 FY2003 FY2004 FY2005 FY2006 FY2007
CD-1 CD-2a CD-2b
CD-3a
CD-3bCD-0Title IDesignComplete
XFELCommissioning
CD-4
Project Engineering Design Long-LeadProcurement
January 2005
Personnel – Resources20042.42.56.07
1.94.42.81
200510.373.44
.601.39
.8610.18
20068.122.662.20.32.31
10.29
20076.071.904.63.51.72
6.32
20083.26.77.62.10.05
6.56
Total30.249.338.124.262.37
34.17
Ctl. Elec. EngineerCtl. Sr. Elec. Tech.Ctl. Elec Tech.Pwr. Elec. EngineerPwr. Sr. Elec. Tech.Control Prog.
January 2005
LCLS contributing labsInjector and linac – SLACUndulator – ArgonneX-ray transport and diagnostics – LivermoreSmaller contributions from other labs too
January 2005
LCLS Team – new to SLACDivision head from ArgonneMuch in common with SPEARDevelopment core from EPICS community
SNS (itself a 5 lab collaboration)ArgonneLANLSPEARSLAC Controls (ESD)
January 2005
LCLS Control System GoalsProvide a fully integrated control system to support the construction, test, installation, integration, operation and automation of the LCLS AcceleratorStandardize all devices and components across all subsystems.Identify all data either by pulse id, beam pulse related time stamp, or 500 msec rough time stamp.Full integration with the SLC – timing, use of LCLS data in SLC high level applications, and use of SLC data in LCLS
January 2005
Difference to PEP-II decisionPEP-II needed to use fabulous suite ofapplications on VMS as isAt that time we had very little EPICS experienceLCLS will add two pieces to EPICS IOCs
Timing interface to SLAC system“Spoofing” context in IOC which responds just like an SLC micro (SLC-Aware IOC)
January 2005
Global Hardware - Timing Boards
SLC micro
476 MHz RF Reference
Master PatternGenerator 128 bit beam codes at 360 Hz
CPU
EVG
Event Generator(PIOP)
Beam Code + EPICS Time + EPICS Events
LLRF
16 triggers
CPU
EVR
Event Receivers(PDU)
Diag
16 triggers
IOC IOCEVR
HPRFI/O
Boards
FIDO119 MHz w/ 360 Hz fiducial
January 2005
Scientific timing requirementsMaintaining saturation in the FELProvide femtosecond timing for pump-probe experiments
Time stamp arrival of FEL pulse w.r.t. an optical laser pulsei.e. synchronize user laser with linac RF reference
Coarse timing of RF bucketAnd jitter at subpicosecond level
January 2005
Functional RequirementsMaximum Link Length 2 KilometersTiming Stability (Long Term) < 5 picosecondsTiming Jitter RMS < 0.5 picosecondsRF Phase Stability (1 second) < 0.07 deg. S-band RF Phase Stability (Long Term) < 5 picosecondsRF Phase Jitter RMS < 0.07 degree S-bandPhase Transmission Frequency 2856 MHzTiming Resolution (Normal) 350 ps (S-band bucket)Timing Resolution (with vernier) 1 psRequired Frequency Stability 3x10e-9
January 2005
Integration with the SLC Control System
SLCAlpha
All HighLevelApps
PNet (Pulse ID / User ID)
MPG
SLC Net over Ethernet (Data Transfer)
micro
CamacI/O
RF reference clock
XtermXtermXtermXtermEPICSW/S
DistributedApplications
EPICSW/S
DistributedApplications
EPICSW/S
DistributedApplications
EPICSW/S
DistributedApplications
EPICS WSDistributedHigh Level
Applications
CA over Ethernet (EPICS Protocol)
I/OC(SLC-aware)
EVG
Microemulator
PNET
CAS
I/OC(SLC-aware)
Microemulator
Fast Feedback
CA Gateway
EVR
Timing
January 2005
Three kinds of front-end supportTraditional SLAC Micros
Old equipment onlyNo new additions
Traditional EPICS IOCsTotally new itemsNo existing SLAC support
SLC-Aware IOCsNew equipment of old typeWorks also as traditional EPICS IOC
January 2005
EnvironmentEPICS Release 3.14.nR/T OS RTEMSWorkstation OS LINUXEPICS ADE (CVS) Simple??Compilers GNUBug Report / Tracking ArtemisNaming Standard PEP IIName Service Name Server JLABDocumentation Web AreaTest stations FFTB
January 2005
Client ToolsDisplay Manager EDMArchiver Channel ArchiverAlarm Handler ALHMessage Logger CMLogElectronic Log Book DESY, Babar, JLAB?Stripchart StripToolWeb based viewing SPEAR, A-Beans, JoiMint,AIDA??Image Analysis Matlab format?Save / Restore ?RDB SNS (leaning)Gateway 3.14.6 Gateway
January 2005
High Level ApplicationsMatlab Available for PhysicistsPython Available for PhysicistsHigh Level Apps
SLC Available in existing systemXAL New directionMatlab based Growing group of users
Top priorities to move into EPICSWhich ones make the SLC-aware IOC easierWhich are the most usefulWhich are the easiest to pick off
January 2005
Hardware Direction – Buy/Steal/MakeIn-House VME version of the PNETCommercial BPM - Echotek and Libera ElectronicsCommunity Timing System (Diamond/SLS/APS)Community Digital Power Supply Controller (SLS)Commercial LLRF - DigitizersCommercial Machine Protection System in PLC? 8msecCommercial Video – evaluate several options (30 Hz)Commercial Conventional Facilities through AB PLCCommunity Wire Scanners ??Commercial Fast feedback in shared memory?
January 2005
Summary
We hope to base all of our hardware on developments from the community or those commercially available.Integration with the existing SLC system is a critical step to allow SLAC operators to use the existing tools while we are adopting and modifying replacements.We are using standard EPICS tools for core development and engineering interfaces.We are adopting all we can from the community and we will use our resources to extend them as we can.
January 2005
LCLS Software Tasks – Standardize/AcquireData Archiving to support all phases of the projectOperator Display Tools / Synoptic, Plots, Waveform, ImageAlarm ManagementElectronic LogHigh Level Application Support: Matlab, XAL, PythonControl System Configuration ToolsRelational Database Management in all project aspects
January 2005
Organizational IssuesControls Department (SW and HW) had always asked for requirements and provided solutions (PEP-I, SLC, PEP-II, NLCTA)LCLS is using Controls as one possible service providerMixture of SPEAR, SLAC, and outside cultureSNS model of project oversight is being used
One engineer for each subsystem for whole machineAll responsible engineers work directly for the LCLS
January 2005
ConclusionLCLS is providing the opportunity to move away from a two decade old solution.The SLC-Aware IOC solution provides a long-needed migration path.Old dogs can learn new tricks.Alte Baeume koennen doch umgepflanzt werden.
