1 / 22

LCLS Controls and Data Acquisition September 23, 2004

LCLS Controls and Data Acquisition September 23, 2004. Outline. Control System Architecture Control System Delivery Schedule for commissioning High level applications (including data acquisition) Areas of concern. Introduction. Control system will evolve with machine needs

valiant
Download Presentation

LCLS Controls and Data Acquisition September 23, 2004

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LCLS Controls and Data AcquisitionSeptember 23, 2004 • Outline • Control System Architecture • Control SystemDelivery Schedule for commissioning • High level applications (including data acquisition) • Areas of concern

  2. Introduction • Control system will evolve with machine needs • Control system commissioning needs to be incorporated in the schedule • Need to prioritize control system needs • Which devices need to be read/controlled • Which application packages • How much automation needed in a measurement • Flexibility to adopt applications from SLC and other labs

  3. Integration with the SLC Control System EPICS W/S Distributed Applications SLC Alpha All High Level Apps EPICS W/S Distributed Applications EPICS W/S Distributed Applications Xterm Xterm Xterm EPICS W/S Distributed Applications Xterm EPICS WS Distributed High Level Applications SLC Net (Data Communication) KISNet (fast closed loop control data) PNet (Pulse ID / User ID) MPG Ethernet (EPICS Protocol) micro Design Provides: SLC Data available to EPICS EPICS data available to SLC PNET timing info into EPICS P N E T R C V R EVG I/OC (SLC-aware) Micro emulator Camac I/O RF reference clock

  4. Global Buses Meet LCLS Requirements EPICS W/S Distributed Applications EPICS W/S Distributed Applications SLC Alpha Apps EPICS W/S Distributed Applications Xterm Xterm EPICS W/S Distributed Applications Xterm EPICS WS Distributed High Level Applications Xterm Fast Feedback SLC-Net over Ethernet Channel Access over Ethernet HPRF I/O Boards EVR Power Supply Ctrl PNETRCVR E VG EVR LLRF EVR Diag Vacuum Ctrl C P U C P U C P U C P U IOC IOC IOC IOC 16 triggers 16 triggers Single Bunch Beam Dumper Drive Laser Off Machine Protection Beam Code + EPICS Time + EPICS Events

  5. Delivery Schedule 2006 May RF Conditioning start – injector Timing LLRF Vacuum Gateway operational from SLC to EPICS Data Archiving RF Automatic Conditioning of Cavities? Personnel Protection – Injector Area August First UV on cathode Power Supply Control BPMs and Profile Monitors Machine Protection System (To laser)

  6. Delivery Schedule 2007 May First Beam on Linac Axis SLC high level applications (SLC-aware IOC) Wire Scanners

  7. Delivery Schedule 2008 June Start Undulator Commissioning Fast Feedback Personnel Protection – LTU and Undulator Area Machine Protection System (To kicker and laser) What tools are needed for X-ray Transport?

  8. High Level Applications • The controls software used by physicists and accelerator operators to: • will be EPICS control panels (edm) • keep the beam running stably in the optimized state • tune or optimize the beam • monitor performance for long-term optimization • diagnose problems with machine performance • detect, prioritize and notify of fault conditions

  9. High Level Applications • Generic diagnostic packages • Beam orbit display • Wire scanner user interface • Profile monitor user interface • Generic tuning packages • Multiknob facility • Deterministic correlation plot package • Buffered data acquisition • Specialist tuning packages • Transverse emittance reconstruction • Beta matching • Bunch length measurement • Slice emittance measurement • Beam line online modeling • Power steering • Linac energy management

  10. High Level Applications • Related software • Fast feedback system • Configuration control (needs RDB) • Data archiver – enhanced version of the history plot package • Archive data viewer – 1 access to data from any archive • Error logging • Alarm handling - watchdog facility to scan and determine severity of out-of-tolerance devices. • Image analysis and fitting package

  11. Closer look at data archiver • 3 types of data to archive • signals from BPM and other gated devices (N scalers with timestamp). N=160 BPMs*3 + 9 toroids + 19 wire scanner readout devices + other devices (beam loss monitors and ion chambers) • video data (15 frames/sec of 1 Mpixel data), 1 camera at a time • machine parameters and ambient conditions (10K channels with timestamp, once a minute) • What is needed here? • 160 BPMs synchronously at some rate? Forever. 1Hz, 10Hz, 20 Hz? • What about archive viewing? • Any need to keep circular buffers and trigger them on some event? Like an MPS trip?

  12. Areas of Concern 1 • Matlab vs XAL • Matlab is needed for physicists to create on-the-fly applications. Direct access to control system parameters with time stamps will be provided. • Which operator applications might be done in Matlab or XAL? Who should participate in the decision? When do we need to decide? • Chris Allen (LANL) giving presentation “Automated Charged Particle Beam Steering” (XAL) Thurs. Sept.30, 2-4 p.m. SSRL 3rd floor

  13. Areas of Concern 2 • What are we using for a relational database (RDB)? • Needed for configuration control and online modeling • We are late getting started on this • There is still no money to start it

  14. Areas of Concern 3 • The Control System needs time for Commissioning!! • Make subsystem schedules with time for this • Provide support for operating the equipment to ensure proper operation through the control system.

  15. Conclusions • The control system architecture supports the requirements. • Information is needed from the project regarding the dates the equipment is required. • To support commissioning tools, we must get some resources to support RDB and determine a platform for these tools. • Information is needed to ensure that data acquisition system supports the requirements • Subsystem engineers must include time to commission the control system. • Information is needed from the physicists regarding what tuning scenarios they will need so that the appropriate application software is avail (e.g slice emittance msmt).

  16. Timing Nsec resolution on the timing gates produced from the Event Rcvr 20 psec jitter pulse to pulse Event generator passes along beam code data from SLC Event generator sends events to receivers including: 360 Hz, 120 Hz, 10 Hz and 1 Hz fiducials (per subsys) last beam pulse OK Machine mode EPICS time stamp Event receivers produce to the IOC interrupts on events data from the event generator in registers 16 triggers with configurable delay and width 476 MHz RF Reference SLC micro Master Pattern Generator 128 bit beam code @ 360 Hz FIDO 119 MHz w/ 360 Hz fiducial Vacuum Ctrl P N E T RCVR EVR Power Supply Ctrl C P U E VG EVR LLRF EVR Diag C P U HPRF I/O Boards C P U C P U IOC IOC IOC 16 triggers 16 triggers Single Bunch Beam Dumper Drive Laser Off Machine Protection Beam Code + EPICS Time + EPICS Events

  17. SLC Net “Micro” Communication Provides data to SLC Applications from EPICS Operates at 10 Hz (not beam synched) Requires significant development in the IOC to emulate SLC “micro” in the IOC On an application by application basis we will evaluate what functions to provide LIST HERE WHAT IS ON?NOT ON THE LIST? SLC Alpha Apps Xterm Xterm Xterm Xterm SLC-Net over Ethernet Vacuum Ctrl C P U PNETRCVR E VG HPRF I/O Boards EVR Power Supply Ctrl EVR LLRF EVR Diag C P U C P U C P U IOC IOC IOC IOC

  18. Channel Access EPICS W/S Distributed Applications SLC Alpha Apps EPICS W/S Distributed Applications Xterm Xterm EPICS W/S Distributed Applications Xterm EPICS WS Distributed High Level Applications Xterm Channel Access Vacuum Ctrl C P U PNETRCVR HPRF I/O Boards EVR Power Supply Ctrl E VG EVR LLRF EVR Diag C P U C P U C P U IOC IOC IOC IOC A channel access server in SLC provides data from existing SLC micros to EPICS applications All IOCs have both a channel access server to allow access and a client to have access Channel access provides read/write by all clients to all data with a server. All EPICS high level applications are channel access clients that may or may not have a server.

  19. Global Communication Fast feedback is required to run at 120 Hz Values will be transmitted from RF and selected diagnostics to Power Supply and RF IOCs The communication needs to be reliable, verifiable, and have a well thought out degradation The entire time budget to read, transmit, commute, control, and settle is 8.3 msec First estimates are that the control system can use 2 msecs to transmit and receive the data Can this be done over a common Ethernet with adequate bandwidth – or is a dedicated one needed? Fast Feedback Vacuum Ctrl EVR Power Supply Ctrl C P U PNETRCVR E VG EVR LLRF EVR Diag HPRF I/O Boards C P U C P U C P U IOC IOC IOC

  20. Machine Protection Machine protection is used here to define faults requiring global mitigation Response time is under 8 msec There are two mitigation devices: Single Beam Dumper - which prohibits the beam from entering the undulator Drive Laser Off – which prohibits beam from entering the cavity Action must also be taken to reduce the repetition rate of the beam This new design is required to interrupt the beam before the next beam pulse. Vacuum Ctrl HPRF I/O Boards EVR Par Supply Ctrl C P U PNETRCVR E VG EVR LLRF EVR Diag C P U C P U C P U IOC IOC IOC IOC Single Beam Dumper Drive Laser Off Machine Protection

  21. Controls Commissioning in WBS

  22. SLC Micro Software Architecture SLC Alpha Users SLC Database Micro n Errlog SCP SCP SCP Error Server DBEX Server TCP/IP SLC Linux Proxy Replies Requests TCP/IP DB Msgs SLC Micro n MSG Main DB Main Msg Q Msg Q Msg Q1 Error Hndlr Micro n … Func1 Main Func* Main Func* Main CAMAC Modules

More Related