Abe, I

Kishiro, J

Kitamura, M

Kosuge, T

Kurokawa, S

Mutoh, M

Nigorikawa, K

CERN Document Server

COACK-II PROJECT ON ACCELERATOR CONTROL KERNELDEVELOPMENTIsamu ABE, Junichi Kisiro, Kazuyuki Nigorikawa, Takashi Kosuge, Shin-ichi Kurokawa, **Masakatsu Mutoh, and**Masaharu KitamuraHigh Energy Accelerator Research Organization (KEK), 1-1 Oho, Tsukuba, Ibaraki 305-0801, Japan*Mitsubishi Electric System & Service Co., Ltd.**Tohoku Univ. Sendai, Miyagi, JapanAbstractA PC (personal computer) system[1] has been appliedpartially in each of the top (GUI), middle and lower(I/O, device) layers of the accelerator control system. Infiscal year 1999, further reinforcement and enhancementof the device controller PCs of the device layer wasscheduled. With the advancement of existing PCarchitecture, as well as hardware and software, researchinto an accelerator kernel that has wide applications hasbeen undertaken. It will be possible to apply this kernelto a wide variety of accelerators. The development ofCOACK-II[2] and the realization of this research ispresented in this paper.INTRODUCTIONFor analysis purposes, the requirements for all types ofaccelerator control systems have been standardized inthis study. The adaptable product is packaged usingCOM (Component Object Model) as a component-ware,and is characterized by its distributed operation(DCOM). A PC control system is achieved through theintegration of SCADA[3]. Accelerator operation hasbeen enhanced through the use of COACK (Component-ware Oriented Accelerator Control Kernel), which is themain subject of this paper. In fiscal 1999, Japan Science& Technology (JST) are supporting COACK-IIdevelopment as an intensive research program.1 BACKGROUND OF COACK-IIResearch on the PC management of the Linac (LinearAccelerator) operator's console at the High EnergyAccelerator Research Organization (KEK) has advancedsince 1987. Our project started with financial aid fromJST, to develop a practical common or standardaccelerator control kernel on Windows NT using COMtechnology. This new kernel is based on the conventionalconcept of the KEK PF Linac control PC system whichwas developed using procedural programming, and canbe applied to any accelerator or to industrial fields formeasurement and control. Comparable systems havebeen developed at accelerator facilities in a number ofcountries, where the same problems have beenencountered. In an analysis of the problem weexperienced led to the observation of a common controlkernel in various measurement and control systems,especially in the accelerator field. During our analysis,the common accelerator control kernel was a subject ofcontroversy. In addition to the recent appearance of anew operating system, Windows NT, and the remarkableprogress in the cost reduction of PC hardware,outstanding forms of technology have become availableand are enjoying practical applications in variousindustrial sectors. Taking advantage of these newfrontiers in technology enabled a next-generation controlsystem to be devised. A control system entirely differentfrom the type used in the UNIX era. The new features ofthe measurement and control systems can also findapplication outside of the accelerator domain.2 ACCELERATOR CONTROL KERNEL(COACK-II)Even though the functional requirements for allaccelerators are virtually the same, an individualprogram for each has been developed. Trying to clearlyunderstand the huge flowcharts and 'spaghetti-like'programs developed with procedural languages isoverwhelming. Since it demands a great deal of timeand effort to prepare programs, we felt that it might bebetter to pool this kind of software.The first goal of COACK-II was to standardize thecommon accelerator functions, especially for the middlelayer, by increasing the flexibility. The second was tocreate new characteristics, making use of the latesttechnology through the introduction of component-ware.The characteristics are obtained not only by defining thestandard functions, but also by using components thatallow experimentation on encapsulated objects.Standardization enables improved functions throughflexible support. For COACK-II, an accelerator controlkernel was developed (fig.1) from the viewpoint of abroad range of applications and the creation ofcomponents.3 FEATURES OF THE COACK-IIPROJECTWhat new characteristics were created by adoptingmeasuring and control functions that feature innovativeforms of technology?International Conference on Accelerator and Large Experimental Physics Control SystemsInternational Conference on Accelerator and Large Experimental Physics Control Systems107International Conference  Accel rator and L rge Experim ntal Physics Control Systems, 1999, Trieste, Italy(1) Many discussions have centered on making auniversally adaptable control kernel for accelerators,measurement and the control systems. At present, thereare many types of commercially available softwarepackages and jointly developed control system softwareavailable. But this marks the first attempt at makingaccelerator control kernel components in addition tostandardizing common functions on various accelerators,and it is expected to set a new course in the realm of thissoftware. This method differs completely fromconventional software supply. Setting up properties andmethods, that are unaffected by source level is extremelyeasy. By basing preparations on COM standards, it hasbecome possible for anyone to supply widely usablecomponents using Visual Basic 6.0.(2) This adaptable kernel for accelerator control basedon fully distributed objects, may be the world’s first,developed as a form of installation technology. Acustomized kernel can be created, simply by downloadingcomponents from a server. Much in the same manner ascollecting information from a homepage, an originalsystem can be built by extracting usable componentsfrom the server. Component-ware dynamically operatedby shifting from one place to another on a network with afully complete binary object level was installed anddemonstrated.(3) Push technology [4] to manage assorted versions ofclient components and applications has been developed.(4) A way to establish components at the GUI(Graphical User Interface) level has been developed andis being promoted in Europe. The concept has beenhighly evaluated. Its operation has become more flexiblethrough the incorporation of ACOP [5] (AcceleratorComponent Oriented Programming), and newlyintegrated acceleration control has become availablethrough a link with COACK-II. In this manner, a viablesoftware sharing system among research institutes isevolving.(5) Commercially available SCADA (SupervisoryControl and Data Acquisition) software is rapidlyimproving, especially with ActiveX connections and isavailable at reduced cost. We can choose among themand easily build a control system. In each GUI or I/O(Input/Output) layer, accelerator control can be realizedsimply by linking ActiveX with SCADA. Intelligent I/Ocontrol and the GUI using SCADA can also be readilyintegrated with the COACK-II system.4 SYSTEM COMPONENTSIn this COACK-II project, we focused on the middle andupper layers. From a structural point of view, the upperand lower layers are equal in the COACK-II. GUI andI/O clients are managed in the same way in COACK-II.4.1 Functions of COACKCOACK-II main functions are:- Client communication, message exchanger,- Command control, Buffer, logging,- Database (Dynamic DB, Static DB, Archiving)management,- Integrated management of accelerator operation,- Download server for component-ware,- Component-ware dynamic operaion,- Extraction and reuse of macro-operation command,- Command sequencer,- I/O control, Alarm system by DCOM,- SCADA management, ACOP attachment,- Download server for component-ware,- Application pushing. [4]Fig.1 COACK-II system4.2 SCADAA Basic idea of the COACK-II system is to apply asmuch SCADA software in the upper and lower layers aspossible. One might say that SCADA and COACK-IIwere meant for one another. COACK-II makesIntegrated SCADA operation possible either as a largerscale control system or as an intelligent control system.4.3 Upper layerIn the connecting pattern of MMI, the upper layer is easyto link using ActiveX, and various kinds of commercialsoftware are available on the market. Conceivably, theintroduction of many kinds of components is alsopossible. Apart from ActiveX or DCOM (DistributedComponent Object Model) communication, that is;clients who do not utilize Windows, COACK-II providessocket communication services. Further, for clients whoare not COM users, COACK-II also permits theapplication of almost equivalent functions. Assumingthat Windows NT is used, a wide variety of Windowscomponents can be loaded. Also, COACK-II makes itpossible to introduce not only a VB (Visual Basic)container, but also SCADA software packages, such asLabView, VEE, Intouch, etc. as components.COACK-II + SCADA+ ACOP, ActiveXdatabaseCashPC@Windows NTserverWebLabViewHP VEEIn touchLabViewHP VEEIn touch Device layerMMI layerACOPcommercialActiveXMS-SQL 7.0Multi server systemCOACK-IIDCOMOLETCP/IPIPX/SPXWindows NT clientsNT clients, PLC, VME, VXI, etcAcceleratorcommoncontrol kernelMessage exchangerCommand bufferDynamic loadingDynamic loading1084.4 ACOP connectionIn Europe a particular component for accelerators hasbeen developed at DESY/CERN. The concept has beenhighly acclaimed in the PC domain. It can be simplydownloaded from a server and with configuration,implemented on any accelerator. Experimental testresults between ACOP, LabView and VB container haveindicated its stability and ease of connection of thesystem.4.5 Lower layerThe development of an accelerator device driver is notplaned for this fiscal year. Conventional drivers will beused. The presumption is made that COACK-II is notdirectly connected with the devices, but is linked withIOC (Input/Output Controllers) and a device controller.In the lower layer, SCADA software, such as LabViewand HP-VEE, are also applicable, but are treated thesame as those in the upper layer. An intelligentconnection, like IOC in the lower layer, is easy to make,but will reduce the network traffic. In other words,adding intelligent or localized control functions to thelower layer will result in an efficient and functionallyintegrated system.4.6 Installation of COM and DCOMThe installation of COACK-II is based on the COMbuilding method instead of using a procedural language,or group of library files. Moreover, through the adoptionof DCOM, distributed object operation can be kept securethroughout the network.5 COACK-II COPYRIGHTIn 1999 our application to undertake short, intensiveresearch and development in advanced computationalscience and technology was accepted by JST. Based on asingle fiscal years contract, this project started in April.KEK signed a research contract with JST, which calls forboth organizations to jointly own the copyright. KEK isalso cooperating with universities, by drawing up adetailed research and work plan, with the actual jobbeing done at KEK. The component-ware establishedcan be easily downloaded from a web server, with theresult that anyone can use it via adaptation to the specificintended accelerator. The right to use this component-ware is now under review in such a way that the jointdevelopers do not need permission to use it.Joint development and planned users of research labsAccelerator control is virtually the same in bothuniversities and research organizations, owning tocomparable accelerators. This makes it desirable tomutually advance research and development byorganizations that have similar systems. Particularly atthe evaluation stage of the operational traits of thissystem, all peculiarities should be clarified through usewith many accelerators. In the future, work of this typeis expected to advance research activities at ourorganization.6 FUTURE PLANIt is expected that COACK-II will enjoy widespread useas an accelerator control kernel. This will cut theinvestment required to develop software for acceleratorcontrol, make setting up a control system easy, andsimplifying the use of the web to globalize operations.The spread of this system in other technical fields willhelp promote its general use, which is important inexpanding the system. The announcement of this plandrew a great deal of interest not only from universitiesand research institutes, but also from industrial sectors.Thus, multi-faceted progress in this system is predicted.We hope that with the creation of this standardizedcontrol kernel, so too will come the emergence of manyparticipants and supporters. We also look forward to theglobal operation of this accelerator, through theintroduction of new forms of technology.7 CONCLUSIONWe have analyzed common objects in acceleratordomain, and the standard or common objects weredefined. These were installed by COM/DCOM as acomponent-ware on Windows NT. The performances[3]were measured and satisfied. These component-ware areavailable to down from COACK-II web server. ManySCADA and ACOP are easy to connect using COACK-II, and unified accelerator operation become possible.ACKNOWLEDGEMENTThe author is indebted to members of VECC, India, andDr. Nishimura, LBL of USA, for their interest andvaluable discussions that contributed to this COACK-IIproject. The author also wishes to thank Mizuno-san andKitsunai-san of JST for their substantial support.REFERENCES[1] I. Abe, LINAC PC based control system usingActiveX, PCaPAC99 Tsukuba, Japan[2] http://ninja.kek.jp/COACK2/[3] T. Nigorikawa, et al., GUI and I/O on COACK-IIProject, this conference.[4] T. Kosuge, et al., Application server and pushingtechnology on COACK-II, this conference.[5] P. Duval, Using ACOP in HERA ControlApplications PCaPAC99 Tsukuba, Japan[6] F. Momal, From UNIX to PC based SCADA systemPCaPAC99 Tsukuba, Japan109

COACK-II Project on Accelerator Control Kernel Development

Abstract

Similar works

Full text

Available Versions

CERN Document Server