A   B   C   D   E   F   G   H   I   K   L   M   P   Q   R   S   T   U   V  


Paper Title Other Keywords Page
TUX01 Interfacing EPICS IOC and LabVIEW for FPGA Enabled COTS Hardware controls, background 43
  • A. Veeramani, K. E. Tetmeyer
    National Instruments, Austin
  • R. Šabjan, A. Žagar
    Cosylab, Ljubljana
  Several attempts have been made to integrate EPICS functionality with National Instruments LabVIEW. With existing EPICS code, labs want to reuse the code while still being able to use LabVIEW to interface with FPGA enabled embedded controllers and other COTS hardware. In this paper, we will show how we can run EPICS IOC simultaneously with LabVIEW on VxWorks based hardware. We will go into the implementation details and the benchmarks that will be obtained from the LANSCE-R project at Los Alamos National Labs. We will also examine ways to implement a Channel Access(CA) server natively in LabVIEW. This will open up the opportunity to use a variety of IO and different operating systems that LabVIEW can interface with. The native LabVIEW CA server will implement all Channel Access functionality exposed by a standard EPICS IOC such as synchronous and asynchronous publishing of data, alarm processing, and response to connection requests by CA clients. We will finally cover the programming of FPGA allowing for custom solutions.  
slides icon Slides  
TUP001 Generic VME Interface for Linux 2.6 Kernels controls, instrumentation, fibre-optics 77
  • A. Homs, F. Sever
    ESRF, Grenoble
  From the beginning of the ESRF both the machine and beamline control instrumentations were based on VME diskless crates equipped with Motorola CPU boards running OS-9. The TACO client-server architecture was used for distributed control. Several modernization steps were performed to migrate from OS-9 to Linux running either on the VME CPU, or on a remote industrial PC connected to the crate using a PCI/VME bus coupler. An initial implementation of a generic VME driver interface was developed for Linux 2.4 which allowed the same VME driver code to work on the different platforms. This work presents the complete re-writing of the above VME layer to fully conform to the abstract bus/device interface provided in Linux 2.6. The new subsystem clearly separates the rolls of VME hosts, controlling the target VME bus, and VME devices, using generic bus functionality exported by the hosts. This structure supports safe hot-plug operations in multi CPU systems and IRQ handling, among other features. The existing VME host drivers (SBS Bit3 bus coupler and Tundra Universe II chip) and VME device drivers (for ESRF, Compcontrol and ADAS cards) were successfully ported to this new structure.  
poster icon Poster  
TUP009 Control System Studio (CSS) Data Browser controls, site, background 99
  • K.-U. Kasemir
    ORNL, Oak Ridge, Tennessee
  The “Data Browser” is an interactive strip-charting and plotting program for both live and archived control system data. Implemented within the Eclipse-based Control System Studio (CSS) environment, it interfaces nicely with other CSS tools. Users can seamlessly access samples from various data sources. We describe the current features and discuss the benefits as well as difficulties that result from CSS/Eclipse.  
slides icon Slides  
WEX03 Development of Embedded EPICS on F3RP61-2L controls, power-supply, extraction, linac 145
  • A. Uchiyama
    SHI Accelerator Service ltd., Tokyo
  • K. Furukawa, N. Kamikubota, H. Nakagawa, T. T. Nakamura, J.-I. Odagiri, M. Tomizawa, N. Yamamoto
    KEK, Ibaraki
  • K. Kameda, T. Natsui, H. Shiratsu
    Yokogawa, Tokyo
  • M. Komiyama
    RIKEN Nishina Center, Wako, Saitama
  • T. Nakamura
    MELCO SC, Tsukuba
  • M. Takagi
    Kanto Information Service (KIS), Accelerator Group, Ibaraki
  Control systems of modern accelerators, such as RIBF, KEKB and J-PARC, adopt many programmable Logic controllers (PLCs). They are supervised by Input/Output controllers (IOCs) of Experimental and Industrial Control System (EPICS) with being controlled and monitored through Ethernet connections. In this type of control system, the adoption of Ethernet as a field-bus reduces the work load for the development of device/driver support modules of EPICS. On the other hand, having controllers (PLCs) under yet another controllers (IOCs) doubles the work load for the implementation of the front-end software. In order to solve the problem, we developed an embedded EPICS on F3RP61-2L, a CPU module running Linux that can work with a base module and I/O modules for FA-M3 PLC. We found that the IOC program can run without any modifications on the CPU module. This paper describes the details of the embedded EPICS system and the application of the new type of IOC for the control systems in operation and under construction.  
slides icon Slides  
WEP011 Experience Using Credit-Card Size Boards Based on Coldfire Processors and Running Under ucLinux controls, linac, feedback 189
  • G. Bassato
    INFN/LNL, Legnaro, Padova
  • W. Zou
    CIAE, Beijing
  Coldfire processors find an ideal application as compact, low-cost controllers thanks to the extremely low power dissipation and the wide range of embedded peripherals. We report some experiences using commercially available credit-card size boards based on the Coldfire MCF5329 processor and running under Emlix ucLinux.  
poster icon Poster  
WEP021 Status of the Control System for the Therapy Facility HIT ion, controls, diagnostics, power-supply 215
  • T. Fleck, R. Bär
    GSI, Darmstadt
  • J. M. Mosthaf
    HIT, Heidelberg
  Shortly before first tumour patients will be treated with high-energy ions at the facility in Heidelberg we give an overview of the control systems special characteristics, current status and remaining functionality to completion. The control system was designed by GSI but has been developed by an all-industrial partner. At each of the three therapy rooms more than 20000 combinations of beam energy, intensity and focus can be requested by the therapy control system. The commissioning for carbon and proton ion beams has already been conducted by GSI. We show how different operating conditions are implemented to ensure at the same time the possibility for experimental research while beam properties already verified within medical test procedures must not be altered without following predefined workflows. Therefore all system and device parameters as well as all set values that possibly change beam properties for patient treatment have to be securely locked or e.g. integrated into checksums. We will also focus on several minor and a few major changes in functionality that had to be implemented to conform to the requirements that originated by the risk assessment of the control system.  
poster icon Poster