EPICS at KEKB Injector EPICSness at KEKB Injector

EPICS at KEKB Injector EPICS-ness at KEKB Injector Kazuro Furukawa, KEK. < kazuro. furukawa @ kek. Jp > KEKB Injector and Legacy Controls Network Controllers EPICS Gateways Timing System K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Control Systems at KEK u There are several Control systems in KEK, Some of them employ EPICS recently e+ /e – Linac PF-AR J-PARC EPICS Group PS ATF KEKB PF K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Linac in KEKB Collider Complex v 8 Ge. V Electron + 3. 5 Ge. V Positron for KEKB v 2. 5 Ge. V Electron for PF v 3. 0 Ge. V Electron for PF-AR v 600 m Linac with 59 S-band rf Stations with SLED v Double Sub-Harmonic Bunchers for 10 ps & 10 n. C v 2 -bunch in a Pulse and Continuous (Top-up) Injection K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Performance of KEKB Staffs in Linac are always Interested in performances in KEKB/Belle Here is the KEKB daily Performance Page updated Every minute K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Linac Controls u. KEKB = Factory Machine => Reliable Operation u. Controls should be Robust and Flexible u~1000 devices and ~10000 signals u. Frequent Beam Mode Switches; Four very Different Beam Modes, 300 times/day u. Precise Controls of Beam Parameters, Energy, Orbit, Emittance, Charge, Energy spread, Timing, etc. K. Furukawa, Apr. 2005.

EPICS at KEKB Injector History and Design Concept u History v 1978 -1982: Construction of First Computer-controlled System with 8 mini-computers, >200 micro-computers, >30 optical loop networks v 1989 -1992: Design of the next system v 1993 -1997: Installation and expansion for KEKB u Design Concept v Use of International and/or de-facto Standards v Use of Optical IP Networks for every Device controllers ³ No new field Networks, only IP Network (to be inherited by J-PARC) v Both of above should make future upgrade easier v (EPICS was not available widely at that time) K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Physical Structure u. Multi-tier, Multi-hardware, Multi-client, … K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Multi-tier Logical Structure K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Software Architecture u Base control software structure for Multi-platform v any Unix, OS 9, Lynx. OS (Realtime), VMS, DOS, Windows, Mac. OS v TCP - UDP General Communication Library v Shared-Memory, Semaphore Library v Simple How-grown RPC (Remote Procedure Call) Library v Memory-resident Hash Database Library u Control Server software v Lower-layer servers (UDP-RPC) for control hardware v Upper-layer server (TCP-RPC) for accelerator equipment v Read-only Information on Distributed Shared Memory v Works redundantly on multiple servers u Client Applications v Established applications in C language with RPC v Many of the beam operation software in scripting language, ³ Tcl/Tk and SADscript/Tk K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Recent Development u. Application software for Two-bunch in a Pulse u. Application software for Continuous Injection u. C-band Acceleration Project (for future Super. KEKB) u. More PLC adaptation, mainly by hardware groups u. Many slow feedback loops, including energy spread u. Slow Positron Facility inside Linac (60 Me. V e-) v. Intel-Linux-VME with Linac software and EPICS IOCcore v. CC/Net (embeded Linux CAMAC CC) for possible replace of Hytec (sorry) u. Evaluation of fast Waveform Digitizers v. Especially for 50 Hz data acquisition u. Network connected RAS module, etc. u. Upgrade of EPICS gateway K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Simple Ethernet Interface - 50 Hz Monitor u Timing signals of ~150 TD 4/TD 4 V/TD 4 R used in linac u If a signal is missing beam loss and possible damage to devices v There was a problem in comparators in TD 4/TD 4 V u A monitor module was built to monitor specific timing requirement u PIC processors and a X-Port from Lantronics u Monitored over Ethernet u Now two other kinds of modules were developed K. Furukawa, Apr. 2005.

EPICS at KEKB Injector VME RAS Module with Ethernet Interface v For reliability of VME crates (~25) v Currently Hardwired modules are used: wiring issues v Ethernet/IP connectivity is preferable ³ ³ ³ Power voltage, temperature, fan Watchdog timers Four RS 232 C ports for CPU, Network, etc TTL inputs/outputs VME reset v Firmware environment ³ Micro-i. TRON, or Linux ³ SH 4, 16 MB RAM ³ peripherals over I 2 C v Interface to EPICS ³ TCP communication with IOCs ³ Possible Embedded EPICS on i. TRON or Linux K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Why EPICS in my case u We made too much effort on duplicate development on many control systems u Our goal is to achieve high performance in the accelerator and the physics experiments u Reuse of available resources is preferable u Devices in Linac have been modernized, and development of EPICS device supports became possible u Anyway we need interface to down-stream accelerators esp. KEKB u Want to merge several archive formants in Linac u May expect (? ) man-power from other groups u May contribute to world-wide EPICS collaboration K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Building EPICS Gateway u Common Control System at the Top (of Linac and Ring) v Needs too much resources u Port EPICS onto our VME/OS 9 -Lynx. OS v Failed to get support/budget for Lynx. OS at Linac v (EPICS Maintenance with an unsupported Platform ? ) u Special Gateway Software, which interfaces to both the Linac Controls and EPICS IOCs as a Client v Built to ensure the feasibility at 1995 u Portable Channel Access Server v Implemented with EPICS 3. 12 and being used on HP-UX since 1996 v It is being used for several application software including Alarm display u Software IOC v Being used and being extended on Linux since 2003 K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Use of Existing EPICS IOC (Gateway IOC) u Software availability v Portable Channel Access Server was not available at around 1995 u Channel Access Server Emulation with Available Software Components v New gateway software which is clients to the both Linac and EPICS, and group of EPICS soft records v Real-time Operation is possible both ways using Monitors u Tested for Magnet Controls v MEDM panels were written Gateway K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Portable Channel Access Server (PCAS) u. Protocol Conversion v. Client to Linac Controls with Home-grown RPC and Cache Memory, Interface to Upper-level Servers (not directly to Lowerlevel Hardware Servers) v. Server to EPICS environment, with some Name wrapping u. Implemented for Linac in 1996 vfor Magnets, RF, Beam Instrumentations v>4000 Records are available v. Write-access Possible, normally Read-only v. Still used for CA Server KEKB Unified Alarm, Operation Status, etc. K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Soft IOC u IOCcore is available on Unix in EPICS 3. 14 v We have Tru 64 unix, Linux, HP-UX u Simple v IOCcore hides the complexity of Channel Access, etc v We design the device support to Upper-level Linac Servers, as we access to hardware in normal IOC u All standard EPICS facilities are available v Alarms, Operation Limits, Links, Periodic processing, Monitors, etc. u Implemented for Linac on Linux since 2003 v For RF, Beam Instrumentation, Vacuum, etc. v >2200 Records are available and extending u All the records are archived in Channel Archiver and KBlog v KBlog is used to analyze correlations between Linac/Ring v Developing Java viewer of the archive K. Furukawa, Apr. 2005.

EPICS at KEKB Injector General Comparisons u Symmetry v Gateway IOC is Symmetric between outside and inside of EPICS ³ Accessing from/to EPICS goes thru the same Gateway v Others are (somewhat) asymmetric u Name Resolution v PCAS can resolve names dynamically (at run-time) ³ Consumes less memory (? ) v Soft. IOC has to be prepared with static database ³ May be expected to give better response ³ Can be impossible for a large installations u Database processing and associate fields v Soft. IOC provides EPICS database Facilities like Limits, Alarms, Links, etc. ³ If we archive them, Archive Deadband is most necessary u Implementation of Gateway v Soft. IOC is relatively straight forward ³ Simply adding device supports K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Application software u. All the records from the Linac Soft IOC are archived both in Channel Archiver and in KBlog v. KBlog is used to analyze correlations between Linac/Ring v(Developing Java viewer of the archive) u. KEKB Alarm is connected to Linac PCAS v. May migrate to Linac Soft. IOC at Summer Shutdown (Linac PCAS is currently based on EPICS 3. 12) u. Some other applications utilize PCAS as well v(Many others access Linac Controls directly now) u. Small number of Records are going thru Gateway IOC, historically K. Furukawa, Apr. 2005.

EPICS at KEKB Injector KEKB Alarm Panel u Below is the KEKB Alarm Main Panel, which covers Linac Alarms as well. Detailed alarm information/history is available in a separate panel Linac Ring K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Beam Optics Panels in SAD u Beam Optics Matching and Optimization Panels in SADscript u Some Parameters goes thru EPICS Gateways, others directly to Linac K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Performance u. EPICS Gateway and Channel Archiver vare Running on Linux 2. 4. 20 (Redhat) with Intel Xeon 2. 4 GHz and Memory of 2 GB ³ About 10% of CPU usage ³ Monitors/Archives all of ~2200 Channels (partial in Kblog) ³ Can process 5400~6600 Channel Access Requests over Network v. Archive size is about 400 MB/day (300 MB/day in Kblog) ³ Both Channel Archiver and KBlog collect Data K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Timing u Beam timing, 2 locations 4 signals v loosely synchlonized to power line within 500 micro seconds v Possible pulse-to-pulse interlace between clients v for KEKB, 2 signals ³ synchronized to 10. 384 MHz (common frequency for 2856, 571, 114, 509) ³ < 3 ps jitter now, < 1 ps near future ³ 1 Hz to 50 Hz, any pattern v for PF, 1 signal ³ synchronized to bunch selected 500 MHz ³ 1 Hz to 25 Hz, any pattern v for PF-AR, 1 signal ³ synchronized to bunch selected 508 MHz ³ 1 Hz to 25 Hz, any pattern K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Timing u Streak camera at 3 locations, 3 signal v synchronized to beam timing within < 1 pico seconds v beam pulse selection u Most Beam monitors (90 bpm, 14 ws, 31 rf) 27 locations 27 signals 40 m each v synchronized to beam timing within 1 nano seconds v 1 Hz, 50 Hz, and selected beam pulse timing, etc. u rf (69 Klystron) stations 14 locations 101 signals 10 m each v synchronized to beam timing within 5 ns v always 50 Hz u Septum/Kicker v for KEKB, PF-AR v synchronized to beam timing within 1 ns v Beam pulse or 25 Hz fixed K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Timing u. Pulse-to-pulse changes vrf system (phase and timing), pulse magnet (on/off) switching vshould send beam type just after previous beam timing to switch those equipment parameters upattern decision can be static upre-program only for now, no dynamic change at the beginning K. Furukawa, Apr. 2005.

EPICS at KEKB Injector Summary u. Slow transition towards EPICS u. At Top u. At Bottom K. Furukawa, Apr. 2005.

EPICS at KEKB Injector K. Furukawa, Apr. 2005.