Software development for linear accelerator control in Labview and DSC Environment J. Boecher, M. Koryevkina, O. Strekalovskiy JINR, Dubna

The software for slow-control of accelerator systems Specialized and even non-standard equipment Variety of hardware interfaces Distance between the connected equipment and the operator Use of mathematical methods of data analysis and processing (including on-line) Necessity of on-line and off-line access to the data, including through Web Monitoring of system parameters Timely alerting to off-optimum situations in equipment performance Saving data into the database for their future analysis and processing should allow: should consider:

Traditional programming Methods of slow-control accelerator system software development SCADA usage SCADA help resolve the main part of these problems for they comprise a set of interrelated components allowing for simplification and unification of software development procedures. The development of slow-control system software for the LUE- 200 accelerator was implemented in the LabView+DSC environment. Following problems may evoke: high labor costs at every level of application development absence of a common solution platform passing the developed software to other programmers for support

. Typical hardware organization

Software levels in accelerator system software Data acquisition layer Data transmission layer Data processing layer Data storage layer Data presentation layer

1. Creating/installing, configuring and testing data servers which assure connection with devices 2. Creating a configuration file, whose content conditions on the data processing process 3. Creating user interface Phases of software development in the LabView+DSC environment

Servers Сбор данных от устройств Передача управляющих сигналов из пользовательского интерфейса к устройствам OPC and VI-based servers Information about available servers is registered and stored in the Common Communication DataBase (CCDB)

Configuretion file and Tag-Engine Настройка тегов Archive database configuration Alarms settings “Real-time” database configuration Tags configuration The server-to-client application and conversely data transmission is implemented using Tag-Engine mechanism and tags Configuation file is used in Tag- Engine

Citadel Data Base Data storage Event storage Alarms storage The initial settings of database record conditions and rate are defined in the configuration file The data stored in the DB may be accessed using historical trends, SQL-queries, and ODBC-compliant applications (Microsoft Query, Microsoft Access, or Microsoft Excel).

HMI-application Monitoring Control Alarms Real-time and historical trends The HMI-application receives and sends data to the tags described in the Tag-Engine configuration file

Time Syncronization Settings Citadel PCOperatorPCServer1PCServer2PC None listedCitadel PC ──OperatorPC

Web Embedded Snapshot Monitor Representation mode Request Control for representation Embedded mode

Advantages Time saving The embedded DB and ready-to-use tools for data review and analysis The use of unified technology in the software development