Stephanie Allison LCLS Integration with SLC October 12, 2004 Integration with SLC LCLS Facility Advisory Committee Oct 12, 2004 Introduction PNET Timing VME Module SLC-Aware IOC Upgrades to Existing SLC Applications Progress Plans for Next 12 Months

Stephanie Allison LCLS Integration with SLC October 12, 2004 Integration with the SLC Control System SLC Alpha All High Level Apps PNet (Pulse ID / User ID) MPG SLC Net over Ethernet (Data Transfer) micro Camac I/O RF reference clock Xterm EPICS W/S Distributed Applications EPICS W/S Distributed Applications EPICS W/S Distributed Applications EPICS W/S Distributed Applications EPICS WS Distributed High Level Applications CA over Ethernet (EPICS Protocol) I/OC (SLC-aware) EVGEVG Micro emulator PNETPNET CAS I/OC (SLC-aware) Micro emulator Fast Feedback over Ethernet CA Gateway

Stephanie Allison LCLS Integration with SLC October 12, 2004 Timing Beam Code + EPICS Time + EPICS Events CPUCPU EVREVR Diag 16 triggers IOC CPUCPU EVREVR Power Supply Ctrl IOC CPUCPU Vacuum Ctrl Machine Protection Drive Laser Off SLC micro 476 MHz RF Reference 128 bit beam 360 Hz FIDO 119 MHz w/ 360 Hz fiducial Nsec resolution on the timing gates produced from the Event Receiver 50 psec jitter pulse to pulse PNET module gets beam code data from Master Pattern Generator Beam code data transferred to Event Generator Event generator sends events to receivers including: 360 Hz, 120 Hz, 10 Hz and 1 Hz fiducials 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 CPUCPU EVGEVG LLRFLLRF 16 triggers IOC EVREVR PNETPNET MPG

Stephanie Allison LCLS Integration with SLC October 12, 2004 Introduction: SLC-Aware IOC CPUCPU EVGEVG LLRF CPUCPU EVREVR Diag IOC EVREVR HPRF I/O Boards CPUCPU EVREVR Pwr Supply Ctrl IOC SLC Alpha Apps Xterm CPUCPU Vacuum Ctrl SLC-Net over Ethernet Provides data to SLC Apps from EPICS on demand and periodically Performs requests by SLC Apps by updating EPICS Messages over Ethernet no greater than 10 Hz Requires significant development in the IOC to emulate SLC “micro” in the IOC Used by non-LCLS projects too

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC IOC – What it Will Do Receive SLC messages and act on them in the same way as existing SLC micros for the following functions: BPM-Like Data Acquisition (Gated ADCs) – beam synchronous Magnet-Like Control and Readback (All Controlled Devices) Timing System (?) Maintain its part of the VMS SLC database: Receive the entire SLC database at initialization time Receive new setpoints at any time from the Alpha Send readbacks back to the Alpha on request and periodically Send setpoint changes made by external EPICS applications to the Alpha Goal – same amount of network traffic as SLC micros

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC IOC – What it Won’t Do MPS BITBUS Power Supply Control KISNET Communication Micro-to-Micro Communication via Alpha SLC-style Analog Signal Monitoring SLC-style Digital Input/Output SLC-style Error Logging (use CMLOG instead) SLC-style Klystron Interface SLC-style Video Interface SLC-style Timing Interface (?) Direct Hardware Access from VMS Debugging from VMS SLC-Style Fast Feedback Interface

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC IOC Software Architecture SLC Alpha DBEX Server SLC Database DB Recv IOC n Micro n SCP SLC Linux Proxy TCP/IP Micro n SCP MSG Recv DBMain Msg Q Msg Q1 MSGMain MAGMain DB MsgsRequestsReplies Data Users MSG Send IOC n Data Base Sequences Event z Callback y Scan x CA Client CA Server EPICS World EPICS Tasks … DB Send BPMMain Msg Q1 SLC “Micro” n

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC IOC SW Architecture – Errors SLC Alpha SCP Error Server errlog Users SLC Tasks IOC Tasks CMLOG Daemon CMLOG Listener IOC n Unix Workstation Errors CMLOG Server cmlog Forward Browser SLC “Micro” n

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC IOC Issues So Far Endian and padding – VMS to/from any possible EPICS platform Restart SLC tasks without restarting the IOC Too much time on prototyping, not enough time on functional requirements

Stephanie Allison LCLS Integration with SLC October 12, 2004 Upgrades to Existing SLC/PEPII Apps SLC database work to define all devices on each SLC IOC, tool needed to generate consistent EPICS and SLC Databases Possible SLC database VMS channel access server upgrades. Minor changes to SLC CMLOG interface programs. Minor upgrades to VMS SLC applications (“SCP”) and other VMS programs (example: SCP micro IPL logic, Database Executor). When a little change to a VMS application saves significant effort on the SLC IOC or an EPICS client.

Stephanie Allison LCLS Integration with SLC October 12, 2004 Progress: May 2004 – Oct 2004 PNET Timing Module Design finished Board is in, parts are being populated First board ready for integration testing in one month

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC-Aware IOC Progress Team in place: LCLS Controls: Stephanie Allison, Dayle Kotturi, Linda Hendrickson ESD Software: Ron Chestnut, Diane Farley, Debbie Rogind, Consultants Weekly meetings, working web page and task list in place Prototype by ESD (2 people part-time): SCP message transfer with IOC Database downloaded Runs on Solaris and VxWorks Identification of issues Begin defining functional requirements by reading existing (old) documents, examining source, and talking with SLC micro SW experts (4 people part-time). Some basic high-level design decisions have been made.

Stephanie Allison LCLS Integration with SLC October 12, 2004 SLC Application Upgrade Progress ESD Software Engineers: Tony Gromme, Ken Underwood, Ron MacKenzie New “type” of SLC micro – minor changes made to SCP, DBEX, and error processing Test database implemented for 2 SLC IOCs Forward CMLOG browser changed for new tags

Stephanie Allison LCLS Integration with SLC October 12, 2004 Plans for Next 12 months PNET driver software by Feb, 2005 Define how the PNET data is used by the event generator and receiver SLC IOC functional requirements review by Nov 3 Continue SLC IOC prototyping throughout Detail SLC IOC design by December SLC IOC implementation begins soon after First: Message service, DB interface, shared utilities (2 people part-time) In parallel: Miscellaneous SLC app changes (1 person part-time) Second: Magnet control and BPM acquisition interface (2 people full-time) In parallel: Define IOC application requirements needed for the SLC IOC. Fully operational prototype by Oct 2005 Ready for first beam in LINAC by May 2007