Status of KEKB accelerator control system

KEKB control group
Noboru Yamamoto


  • Overview
  • Status of Development

  • Overview

  • KEKB control system will use EPICS toolkit as a base of system. It provides an,
  • "OPEN",
  • Flexible,
  • and Extensible
  • framework for a control system.

  • Presentation Layer
    X-terminals are used as operator's console. Multi-screen X-terminal is being tested.

  • Application Layer
    UNIX server is chosen as an application server. It also works as a database server for static/archive database.

  • Database Layer
  • EPICS uses a distributed run time database for equipment control. Link-persons in hardware groups are responsible to design EPICS database templates.
  • A (relational) database provides,
  • Information of devices in the accelerators, such as interface address, calibration data etc,
  • Information on archived data.
  • Equipment Control Layer
  • Field buses
  • GP-IB
  • Serial
  • Modbus+
  • Reflective memory(?)
    VME CPU based on MC68060 is used at the first stage.
    PowerPC based board was tested with EPICS R3.12 software. EPICS was ported to the new platform without much difficulty. Our measurement shows that PowerPC based board runs EPICS 5 times faster than MC68040 based board.
  • Network
    Switched FDDI is used as a backbone of KEKB control system network. The backbone network is connected to a switched Ethernet HUB at each control stations.

  • Timing System
  • RF reference signal
  • Fast timing system
    Beam revolution signal and trigger signals will be distributed through fiber optics cables. Time delay module used in TRISTAN, TD2, is redesigned as VME board.
  • Synchronization based on EVENT.
  • Safety
    Safety alarm/interlock system used in TRISTAN will also be used in KEKB with necessary modification.

  • CATV
    We use the existing infrastructure for Lab-wide distribution of the KEKB status. The KEKB status can be accessed through a network.

  • Status of Development