| Paper |
Title |
Other Keywords |
Page |
| MOAA01 |
Accelerators: The Final Frontier?
|
collider, electron, linac, proton |
1 |
| |
|
|
| MOPA01 |
Summary of the Control System Cyber-Security (CS)2/HEP Workshop
|
controls, synchrotron, monitoring, photon |
18 |
| |
- S. Lueders
CERN, Geneva
| |
Over the last few years modern accelerator and experiment control systems have increasingly been based on commercial-off-the-shelf products (VME crates, PLCs, SCADA systems, etc.), on Windows or Linux PCs, and on communication infrastructures using Ethernet and TCP/IP. Despite the benefits coming with this (r)evolution, new vulnerabilities are inherited, too: Worms and viruses spread within seconds via the Ethernet cable, and attackers are becoming interested in control systems. Unfortunately, control PCs cannot be patched as fast as office PCs. Even worse, vulnerability scans at CERN using standard IT tools have shown that commercial automation systems lack fundamental security precautions: Some systems crashed during the scan, others could easily be stopped or their process data be altered. The (CS)2/HEP workshop held the week-end before ICALEPCS2007 was intended to present, share, and discuss countermeasures deployed in HEP laboratories in order to secure control systems. This presentation will give a summary overview of the solution planned, deployed and the experience gained.
|
|
|
Slides
|
|
|
|
| MOPB03 |
Control System Studio (CSS)
|
controls, site, diagnostics |
37 |
| |
- M. R. Clausen, C. H. Gerke, M. Moeller, H. R. Rickens, J. Hatje
DESY, Hamburg
| |
Most applications for the control system EPICS are developed for UNIX and X-Windows. They are independent from each other, have a different look and feel, and it is difficult to exchange data. To solve these problems the Control System Studio (CSS) is under development. CSS is a common platform for new control system applications and provides developers with management infrastructure and a centralised connection to external data sources like JDBC-databases, JMS-, LDAP-servers, etc. CSS defines interfaces to avoid dependencies on special implementations. This design makes sure that an application can easily be integrated or exchanged. Another important feature is the accessibility of data through all applications via CSS-data types defined in CSS. The Data Access Layer (DAL) assures the transparent access to any control system protocol. Thus CSS is not only a platform for EPICS but for any control system that implements the DAL. The intension to modularise CSS and run it on any operating system lead to the decision to use the Eclipse RCP based on the OSGi technology. Technically CSS is a set of essential core-plugins and application plugins selected by the user.
|
|
|
|
Slides
|
|
|
|
| MOPB04 |
JavaIOC
|
controls, power-supply, monitoring |
40 |
| |
- M. R. Kraimer
Private Address, Osseo
| |
EPICS is a set of Open Source software tools, libraries, and applications developed collaboratively and used worldwide to create distributed soft real-time control systems for scientific instruments such as particle accelerators, telescopes, and other large scientific experiments. An IOC (Input/Output Controller) is a network node that controls and/or monitors a collection of devices. An IOC contains a memory resident real-time database. The real-time database has a set of "smart" records. Each record is an instance on a record of a particular type. JavaIOC is a JAVA implementation of an EPICS IOC. It has many similarities to a Version 3 EPICS IOC, but extends the data types to support structures and arrays.
|
|
|
|
Slides
|
|
|
|
| TOPA03 |
The IRMIS Universal Component-Type Model
|
controls, insertion, site, power-supply |
82 |
| |
- D. Dohan
ANL, Argonne, Illinois
| |
The IRMIS toolkit provides a relational description of the accelerator/facility hardware and how it is assembled. To create this relational model, the APS site infrastructure was successively partitioned until a set of familiar, "unit-replaceable" components was reached. These items were grouped into a set of component types, each characterized by the type's function, form factor, etc. No accelerator "role" was assigned to the components, resulting in a universal set of component types applicable to any laboratory or facility. This paper discusses the development of the universal component-type model. Extension of the component types to include port definitions and signal-handling capabilities will be discussed. This signal-handling aspect provides the primary mechanism for relating control system software to accelerator hardware. The schema is being extended to include references to the device support for EPICS-supported component types. This suggests a new approach to EPICS database configuration in which the user, after selecting a particular hardware component, is provided with links to the support software to be used in building the EPICS application.
|
|
|
|
Slides
|
|
|
|
| TPPA01 |
Control System Design Using LabVIEW Object Oriented Programming
|
controls |
84 |
| |
- H. Brand, D. B. Beck
GSI, Darmstadt
| |
Starting with version 8.20, the graphical programming language LabVIEW has been extended to object-oriented programming (LVOOP). This paper comprises a design study investigating the helpfulness of LVOOP for developing LabVIEW-based control systems. Moreover, the possible integration of such a control system into a mixed environment is demonstrated. Conventional object-oriented programs with text-based languages, as C++ or Java, typically declare an object as a pointer in the heap. Later on, objects are addressed "by reference." However, LabVIEW is using the paradigm of dataflow, and LVOOP follows this line. Consequently, objects can only be addressed "by value." This has fundamental consequences, since many existing object-oriented design patterns cannot be used. Within this work, a couple of dataflow design patterns that are useful for programming with LVOOP have been invented. A prototype system has been set up, demonstrating the advantages and disadvantages of this approach. Furthermore, it is easily possible to integrate a control system based on LVOOP into a mixed environment using DIM (www.cern.ch/dim) as a communication layer.
|
|
|
|
| TPPA03 |
Software Factory Techniques Applied to Process Control at CERN
|
controls, target, monitoring, collider |
87 |
| |
- M. D. Dutour
CERN, Geneva
| |
The LHC requires constant monitoring and control of large quantities of parameters to guarantee operational conditions. For this purpose a methodology called UNICOS was implemented to standardize the design of process control applications. To further accelerate the development of these applications, we migrated our existing UNICOS tooling suite toward a software factory in charge of assembling project, domain, and technical information seamlessly into deployable PLC–SCADA systems. This software factory delivers consistently high quality by reducing human error and repetitive tasks and adapts to user specifications in a cost-efficient way. Hence, this production tool is designed to hide the PLC and SCADA platforms, enabling the experts to focus on the business model rather than specific syntax. Based on industry standards, this production tool along with the UNICOS methodology provides a modular environment meant to support process control experts to develop their solutions quickly. This article presents the user requirements and chosen approach. Then the focus moves to the benefits of the selected architecture and finishes with the results and a vision for the future.
LHC:Large Hadron ColliderUNICOS:UNified Industrial COntrol SystemsPLC:Programmable Logic ControllerSCADA:Supervisory Control And Data AcquisitionTerms:Process control, software engineering
|
|
|
|
| TOPB04 |
Control System of the KEKB Accelerator Complex
|
controls, linac, injection, positron |
268 |
| |
- A. Akiyama, N. Kamikubota, T. T. Nakamura, J.-I. Odagiri, M. Satoh, T. Suwada, N. Yamamoto, K. Furukawa
KEK, Ibaraki
| |
The KEKB asymmetric electron-positron collider complex consists of 8-GeV Linac, high-energy and low-energy rings. Some of the resources were inherited from the previous TRISTAN project, and also they are shared with Photon Factory and PF-AR light sources. In order to realize the long lifespan of the system de-facto and international standard technologies were employed since the early stage, which have been efficiently operated. Several gateway methods were implemented to integrate heterogeneous sub-systems, which are gradually converted into EPICS. Scripting languages are employed for higher-level applications. The ever-evolving control system has enabled flexible and reliable beam operations at KEKB throughout the long period.
|
|
|
|
Slides
|
|
|
|
| WPPB37 |
Fast BPM DAQ System Using Windows Oscilloscope-based EPICS IOC
|
linac, controls, feedback, photon |
469 |
| |
- K. Furukawa, T. Suwada, M. Satoh
KEK, Ibaraki
- T. Kudou, S. Kusano
MELCO SC, Tsukuba
- J. W. Wang
USTC, Hefei, Anhui
| |
The non-destructive beam position monitor (BPM) is an indispensable diagnostic tool for the stable beam operation. In the KEK linac, approximately nineteen BPMs with the strip-line type electrodes are used for the beam orbit measurement and orbit feedback. In addition, some of them are also used for the beam energy feedback loops. The current DAQ system consists of the digital oscilloscopes and the VME computers. They are connected with the GPIB, and a signal from each electrode is analyzed with a predetermined response function once per second by a VME computer that is connected to the upper-layer control servers via Ethernet. The KEKB injector linac is planned to be upgraded to perform the simultaneous injection for 4-rings. In this operation mode, a fast DAQ system is strongly required. In the current system, maximum DAQ rate is strictly limited by the oscilloscope performance, and it should be improved for the 50-Hz measurement. For these reasons, we made the decision to replace the current DAQ system with the fast digital oscilloscope. In this paper, we will present the system description of the new DAQ system, and the detailed result of the performance test will be presented.
|
|
|
|
| WPPB38 |
Update on the CERN Computing and Network Infrastructure for Controls (CNIC)
|
controls, collider, hadron |
472 |
| |
- S. Lueders
CERN, Geneva
| |
Over the last few years modern accelerator and experiment control systems have increasingly been based on commercial-off-the-shelf products (VME crates, PLCs, SCADA, etc.), on Windows or Linux PCs, and on communication infrastructures using Ethernet and TCP/IP. Despite the benefits coming with this (r)evolution, new vulnerabilities are inherited too: Worms and viruses spread within seconds via the Ethernet cable, and attackers are becoming interested in control systems. Unfortunately, control PCs cannot be patched as fast as office PCs. Even worse, vulnerability scans at CERN using standard IT tools have shown that commercial automation systems lack fundamental security precautions: Some systems crashed during the scan, others could easily be stopped or their process data be altered. During the two years following the presentation of the CNIC Security Policy at ICALEPCS2005, a “Defense-in-Depth” approach has been applied to protect CERN's control systems. This presentation will give a review of its thorough implementation and its deployment. Particularly, measures to secure the controls network and tools for user-driven management of Windows and Linux control PCs will be discussed.
|
|
|
|
| WPPB39 |
130-MHz, 16-Bit Four-Channel Digitizer
|
target, controls, feedback, impedance |
475 |
| |
- R. Akre, T. Straumann, K. D. Kotturi
SLAC, Menlo Park, California
| |
The PAD (Phase and Amplitude Detector) was designed to digitize high-speed analog input data with large dynamic range. Because of its high speed and high resolution processing capability, it has been useful to applications beyond measuring phase and amplitude of RF signals and klystron beam voltages. These applications include beam-position monitors, bunch-length monitors, and beam-charge monitors. The digitizer used is the Linear Technologies LTC2208. It was the first 16-bit digitizer chip on the market capable of running at 119MHz; it is specified to run up to 130MHz. For each channel, the 16-bit digitized signal from the LTC2208 is clocked into a 64k sample FIFO. Commercial FIFOs are available that store up to 256k samples in the same package. The data are then read from the FIFO into the Arcturus Coldfire uCDIMM. A CPLD is used to handle triggering, resetting the FIFO, interfacing the Coldfire processor to the 4 FIFOs, and interrupting the Coldfire processor. The processor runs RTEMS version 4.7 and EPICS 3.14.8.2. There is an optional add-on available that attaches to the QSPI port on the PAD for reading 8 slow, 24-bit analog signals.
|
|
|
|
| ROAA01 |
Status of the ITER CODAC Conceptual Design
|
controls, plasma, site, monitoring |
481 |
| |
- J. W. Farthing
UKAEA Culham, Culham, Abingdon, Oxon
- M. Greenwald
MIT/PSFC, Cambridge, Massachusetts
- I. Yonekawa
JAEA/NAKA, Ibaraki-ken
- J. B. Lister
ITER, St Paul lez Durance
| |
Since the last ICALEPCS conference, a number of issues have been studied in the conceptual design of the ITER Control, Data Access, and Communication Systems. Almost all of the technical challenges have seen workable approaches selected. The conceptual design will be reviewed in 2007, before starting the preliminary engineering design. One software component that does not have a clear solution is the execution of data-driven schedules to operate the installation at multiple levels, from daily program management to plasma feedback control. Recent developments in workflow products might be useful. The present conceptual weakness is not having found a satisfactory "universal" description of the I&C design process for the "self-description" of the 100 procured Plant Systems. A vital CODAC design feature is to operate the full plant on the basis of imported “self-description” data, which necessarily includes the process description in each Plant System. The targeted formal link between 3-D design, process design, and process control has not yet been created. Some of the strawman designs meeting the technical requirements will be mentioned in detail.
|
|
|
|
Slides
|
|
|
|