| Paper | Title | Other Keywords | Page |
|---|---|---|---|
| S02SRU07 | Upgrading the BEPC Control System | controls, software, power-supply, operation | 82 |
|
|||
| The BEPC control system has been put into operation and operated normally since the end of 1987. Three years’s experience shows this system can satisfy basically the operation requirements, also exhibits some disadvantages a raised from the original centralized system architecture based on the VAX-VCC-CAMAC, such as slow response, bottle neck of VCC, less CPU power for control etc. This paper describes the method and procedure for upgrading the BEPC control system which will be based on DECnet and DEC-WS, and thus intend to upgrade the control system architecture from the centralized to the distributed and improve the integral system performance. | |||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S02SRU07 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S05SRN03 | Control Software for the ESO VLT | controls, software, operation, database | 202 |
|
|||
| The Very Large Telescope (VLT) project of ESO consists of an array of four optical telescopes of 8 m diameter, to be installed at a new site in the Atacama desert in Chile starting in 1995. The control software is completely distributed, being based on LANs interconnecting microprocessors and workstations, where several users and operators will be active at the same time. Microprocessors are used in a variety of control functions, including the active control of the shape of the main mirror and compensation for atmospheric turbulence. Dedicated links and antennas are planned for direct communication and remote observation from various European centers. The main concepts and novelties of the software design are explained. | |||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S05SRN03 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S07IC03 | EPICS Architecture | controls, database, EPICS, network | 278 |
|
|||
|
Funding: Work at LANL supported and funded under the Department of Defense. US Army Strategic Defense Command. under the auspices of the Department of Energy.<br /> Work at ANL supported by U.S. Dept. of Energy, Office of Basic Energy Sciences, under Contract No W-31-109-ENG-38. The Experimental Physics and Industrial Control System (EPICS) provides control and data acquisition for the experimental physics community. Because the capabilities required by the experimental physics community for control were not available through industry, we began the design and implementation of EPICS. It is a distributed process control system built on a software communication bus. The functional subsystems, which provide data acquisition, supervisory control, closed loop control, archiving, and alarm management, greatly reduce the need for programming. Sequential control is provided through a sequential control language, allowing the implementer to express state diagrams easily. Data analysis of the archived data is provided through an interactive tool. The timing system provides distributed synchronization for control and time stamped data for data correlation across nodes in the network. The system is scalable from a single test station with a low channel count to a large distributed network with thousands of channels. The functions provided to the physics applications have proven helpful to the experiments while greatly reducing the time to deliver controls. |
|||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S07IC03 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S08NC02 | Multi-Processor Network Implementations in Multibus II and VME | network, software, controls, interface | 295 |
|
|||
|
ACNET (Fermilab Accelerator Controls Network), a proprietary network protocol, is implemented in a multi-processor configuration for both Multibus II and VME. The implementations are contrasted by the bus protocol and software design goals. The Multibus II implementation provides for multiple processors running a duplicate set of tasks on each processor. For a network connected task, messages are distributed by a network round-routed for each task by user-callable commands. The VME implementation provides for multiple processors running one task across all processors. The process can either be fixed to a particular processor or dynamically allocated to an available processor depending on the scheduling algorithm of the multi-processing operating system.
Operated by Universities Research Association for the Department of Energy. |
|||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S08NC02 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S08NC03 | A Distributed Design for Monitoring Logging and Replaying Device Readings at LAMPF | software, controls, network, interface | 299 |
|
|||
|
Funding: Work supported by the U.S. Department of Energy As control of the Los Alamos Meson Physics linear accelerator and Proton Storage Ring moves to a more distributed system, it has been necessary to redesign the software which monitors, logs, and replays device readings throughout the facility. The new design allows devices to be monitored and their readings logged locally on a network of computers. Control of the monitoring and logging process is available throughout the network from user interfaces which communicate via remote procedure calls with server processes running on each node which monitors and records device readings. Similarly, the logged data can be replayed from anywhere on the network. Two major requirements influencing the final design were the need to reduce the load on the CPU of the control machines, and the need for much faster replay of the logged device readings. |
|||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S08NC03 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S08NC04 | Synchronous Message-Based Communication for Distributed Heterogeneous Systems | network, controls, Ethernet, real-time | 302 |
|
|||
| The use of a synchronous, message-based real-time operating system (Unison) as the basis of transparent interprocess and inter-processor communication over VMEbus is described. The implementation of a synchronous, message-based protocol for network communication between heterogeneous systems is discussed. In particular, the design and implementation of a message-based session layer over a virtual circuit transport layer protocol using UDP /IP is described. Inter-process communication is achieved via a message-based semantic which is portable by virtue of its ease of implementation in other operating system environments. Protocol performance for network communication among heterogeneous architectures is presented, including VMS, Unix, Mach and Unison. | |||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S08NC04 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S14OOP06 | The State Manager: A Tool to Control Large Data-Acquisition Systems | controls, data-acquisition, interface, MMI | 524 |
|
|||
| The State Manager system (SM) is a set of tools, developed at CERN, for the control of large data-acquisition systems. A dedicated object-based language is used to describe the various components of the data-acquisition system. Each component is declared in terms of finite state machines and sequences of parametrized actions to be performed for operations such as the start and end of a run. The description, written by the user, is translated into Ada to produce a run-control program capable of controlling processes in a distributed environment A Motif-based graphical interface to the control program displays the current state of all the components and can be used to control the overall dataa-cquisition system. The SM has been used by several experiments both at CERN and other organizations. We present here the architecture of the SM, some design choices, and the experience acquired from its use. | |||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S14OOP06 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S16MS02 | Framework for Control System Development | controls, interface, network, software | 542 |
|
|||
|
Funding: This work was supported by the US DOE under Contract No. DE-AC03-76SF00098 Control systems being developed for the present generation of accelerators will need to adapt to changing machine and operating state conditions. Such systems must also be capable of evolving over the life of the accelerator operation. Several of the new generation of control systems hardware being developed today have the capability of fast, sophisticated control at all levels in the control hierarchy. These systems are typically hierarchical and highly distributed with extremely high I/O throughput. We have initiated the design of a framework for control system development which can accommodate the new architectures. This paper will present requirements, design decisions, and specifications that we have devised for this framework. |
|||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S16MS02 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||
| S16MS04 | Optimization of Accelerator Control | controls, operation, experiment, injection | 550 |
|
|||
| Expensive exploitation of charged particle accelerators is inevitably concerned with requirements of effectively obtaining of the best characteristics of accelerated beams for physical experiments. One of these characteristics is intensity. Increase of intensity is hindered by a number of effects, concerned with the influence of the volume charge field on a particle motion dynamics in accelerator’s chamber. However, ultimate intensity, determined by a volume charge, is almost not achieved for the most of the operating accelerators. This fact is caused by losses of particles during injection, at the initial stage of acceleration and during extraction. These losses are caused by deviations the optimal from real characteristics of the accelerating and magnetic system. This is due to a number of circumstances, including technological tolerances on structural elements of systems, influence of measuring and auxiliary equipment and beam consumers’ installations, placed in the closed proximity to magnets, and instability in operation of technological systems of accelerator. Control task consists in compensation of deviations of characteristics of magnetic and electric fields by optimal selection of control actions. As for technical means, automation of modem accelerators allows to solve optimal control problems in real time. Therefore, the report is devoted to optimal control methods and experimental results. | |||
| DOI • | reference for this paper ※ doi:10.18429/JACoW-ICALEPCS1991-S16MS04 | ||
| About • | Received ※ 11 November 1991 — Accepted ※ 20 November 1991 — Issued ※ 04 December 1992 | ||
| Cite • | reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml) | ||