Control System
June 13, 2016
Tatsuro NAKAMURA

Outline• Overview• Central Server Computers• Network• IOC (Input/Output Controller)• Field Buses• Other issues• Recent Topics• Beam Abort Trigger System• Alarm System• Tasks toward Phase-2• Timing system, Injection control → Next talk2

Overview of the Control System(Software)• EPICS based --- Distributed System– EPICS (Experimental Physics and Industrial Control System) is atoolkit to construct control systems– 2 layer model• OPI (Operation Interface) --- operation programs on central servers• IOC (I/O Controller) --- equipment controls on frontend computers– CA (Channel Access)• Communication protocol over network• Core technology of EPICS• Operation Programs in Scripting Languages• Quick and Flexible Development• With EPICS-CA, GUI (tk)

– SAD Script (developed at KEK)
– Python3

Overview of the Control System(Hardware)
Central Servers

ConsolesHigh Speed Network（10G/1G Ethernet）

Frontend Computers
IOC (I/O Controller)

Field Buses
4

Overview of the Control System
Upgrade KEKB → SuperKEKB• Network– 1G Ethernet → 10G/1G, Redundant, VLAN
– Introduce wireless LAN• EPICS system– R3.13 (VxWorks based) → R3.14 (multiplatform)• IOC– Single platform (VME/VxWorks) → Multiplatform (VME/VxWorks,PLC/Linux, PC/Linux, µTCA/Linux, Embedded system, etc.)• Abort Trigger System– Metal wire based (trunk lines were replaced with optical fibers)→ Full optical connection• High level application upgrade– Alarm System, Task launcher, etc.

• Renovation of the Control Room and Computing Room5

Central Server Computers•

Control Servers --- Managed by Control Group– Dedicated for KEKB Control / Operation– Currently consists of• Rack Mount Servers– 2 HP-UX (old system)– 3 Linux• Blade Servers– 14 Linux•SAD Computers (SAD Cluster) --- Managed by SAD Group– Originally for SAD Simulations– Later intensively used for KEKB Operation– Not only for KEKB but also for other Projects (Many user accounts !)– Currently consists of• 7 Free BSD Servers• SAD-NAS (main storage)

6

Network
Star Conﬁgura1on between
Central Control Building
and26 Local Control Rooms
New installa1on planned in 2016:
DR Local Control Room

• Backbone– 10G/1G bps Ethernet– Central core switch• Catalyst 6509E

Central ControlBuilding– Redundant Configuration– VLAN
7

Control Network and KEK Lab. Network
User’s PC

SAD Computers(Oﬄine Purpose)

PCPCPCAll Users can login.

KEK Laboratory Network

Separate each other

SAD-NAS(/users, /data, DB,etc)

Firewall

NAS can be accessed directly
through both Networks.

KEKB Control Network

EPICS IOCIOCIOCIOC

Control Servers
SAD Computers(Opera1on Purpose)

ConsolesOnly KEKB Users can login.

All of SAD Computers and Control Servers share same home directory.

8

IOC (Input/Output Controller)• We use 2 major types• VME/VxWorks IOC– CPU• MVME5500, MVME4100• Force PPC750 (old)ＣＰＵ• PLC/Linux IOC– Yokogawa FAM3 series PLC– CPU• F3RP61 (Linux CPU)CPU Module
F3RP61I/O Modules 9

F3RP61 (e-RT3 2.0)
Linux 2.6.24
PPC 533MHz
128Mbyte RAM
100BaseTx x 2USBIEEE1394
SerialKEKB Beam mask controller
PCI
I/O Bus for FAM3 Module Interface
can access to mature FAM3 I/O Modules
Can be combined with conventional ladder CPU
Software development environment (ELDK)

10

Field Buses• CAMAC --- Too old (∼30 years old), still used!
– For BTà Replacement to PLC (or other Embedded EPICS Systems)
are planned before Phase 2– For old LLRF

• Serial (Asynchronous)• GP-IB– Widely used

• Ethernet– Widely used

• VXI/MXI– For BPM

• ARCNET– For Magnet Power Supply

11

ARCNET and Magnet Power Supply
New version
synchronous start signal

ARCNET Interface board（4 ch. / boards）
PSICM

CPU

magnetpower
supplyIOC(VME)

max. 20 nodes
twisted pair cable
local control
room

power supplyroom

ARCNET（1 pair）
synchronous start signal（1 pair）

PSICM is “Power Supply Interface Controller Module”, developed at KEK.

Other Issues• Operation Consoles– Central console terminals– Replacement of the old terminals in the Local
Control Rooms are in progress• Data Archivers– KEKBLog (monitoring ∼100,000 channels, 4GB/day)– CSS Archiver is also running for R&D purpose• Operation Log– “Zlog” : Zope based web application

13

Beam Abort Trigger System

New VME module“VME-AM”
8 optical input
1 optical output
14

Improvement from the KEKB abort trigger system
1. Response time from the input to the beam abort
100us -> 20us. Previous system used low pass filters for the noise
reduction, which increased the response time.

2. Optical fiber connection
Three kinds of signals(TTL, RS422, Relay contact) convert to opticalsignals to avoid the electrical noise. Control group maintains thesignal transfer quality.

3. Time stamp
In the most of the case, the beam abort are not only one input signal
but also many dependent signals. To find out the source of thebeam abort, the time stamp function is added to the VME-AM, which
can store the time of the abort signal with 0.1us resolution.

4. System check
To increase the reliability of this system, the system check function is15
installed to the VME-AM.Abort Trigger System in Phase-1 Operation
Only half of 36 VME modules have been installed due to thelimited budget. → Full installation will start for Phase-2
old modules

new VME modules

w/o modules (no aggregation)

16

Time stamp of the abort trigger

17

Alarm System• KEKB Alarm System– SAD-based program– Unstable to handle large number of channels– Hard to maintain• SuperKEKB Alarm System– Using CSS Alarm (EPICS standard tool) +GUI panel written in Python and tk toolkit– Backend database : PostgreSQL– ∼ 14,000 channels are monitored in Phase-118

Structure of New Alarm System• the CSS-based alarm system.
IOCIOCIOC
Monitor EPICS records(monitor the severity)

XMLDefinition
setting fileIOCIOCIOC

Alarm Config Tool

Initial setting

Channel Access

Alarm Server
Alarm log

Alarm status

Alarm DB

Alarm status

JMS (ActiveMQ)
Alarm status

JMS2RDB

Alarm Client GUI
Alarm log

Log DBShow the Current
Alarm Status

Change the setting
parameters

Write Alarm Log

Alarmhistory

List of EPICS records
to be monitored
Alarm message/ Beep / etc..

UserOperator

Alarm Status Panel
Appearance of the old KEKB Alarm (SAD-based Alarm) is inherited.

20

Alarm History Panel21

Tasks toward Phase-2• Set up infrastructure (network, etc.) for DR• Deployment of IOC for DR and IR• IOC of the BT lines (except pulsedmagnets) are left behind. They should beupgraded (CPU, Interface and Software)• Full Installation of the new abort trigger
modules• DR and DR-BT magnet control system
22Summary•
•
•
•
•
•
•

Our control system is EPICS-based distributed system, which has
been inherited from KEKB control system.
Network has been reinforced and reconfigured. It works well inPhase-1 operation.
Upgrading EPICS R3.13 → R3.14, we can use multiplatform IOC,
which provides more flexible configuration.
We use several kinds of field busses. New PSICM has been
installed for magnet PS control. Some old devices such as CAMAC
should be replaced.
New Beam Abort Trigger Module “VME-AM” has been developedwith full optical connection and partially installed. It works well in the
Phase-1 operation.
New Alarm System has been developed with CSS Alarm andpython/tk GUI. It works well in Phse-1 operation.
We still have many tasks toward Phase-2, not only construction ofDR and IR part but also the upgrade of existing part such as BTcontrol system and so on.
23

24

backup25

F3RP61 in SuperKEKB••••

Vacuum Control
LLRF (used with MicroTCA system)
Interface to the Personnel Protection System
Embedded in Large Magnet Power Supply– Digital feed back control for high current stability••••

Beam Mask Control
Pulsed Magnet (Kicker, Septum) Control
RF Power Supply Control
Tilting Support (SX Magnet) Control

26

Version up of the PSICM(Power Supply Interface Controller Module)– Interface/Controller card plugged in power supply• Microprocessor is embedded• ARCNET controller and driver• Timing signal input to start synchronous ramping– New version of PSICM• Support high speed communication (10/5/2.5Mbps)• Support high resolution Power Supply (24/20/18/16bits DAC)
• Fully compatible to the current version for the Magnet PS• Redundant timing signals• More reliable connectors

Old VersionNew Version

System conﬁgura<on of the beam abort

200m(1us)max.

2km(10us)max.

Opticalfiber
The most of the response 1me is limited by the cable signaltransfer 1me.

28

VME-AbortModule(VME-AM)

29