Accelerator equipment monitoring system based on epics

Abstract

The application discloses an accelerator equipment monitoring system based on EPICS, which comprises a client, an equipment monitoring server and a local control device. The client is used for providing a monitoring interface of a target accelerator equipment, receiving a control instruction of the target accelerator equipment through the monitoring interface, and sending the control instruction to the local control device through the equipment monitoring server. The local control device is used for controlling the target accelerator equipment according to the control instruction and sending state data of the target accelerator equipment to the equipment monitoring server. The equipment monitoring server is used for converting the state data into a PV value supported by EPICS, processing the PV value by using a plug-in service provided by the equipment monitoring server, and feeding back the PV value and a processing result thereof to the client. The system can monitor an accelerator system comprising multiple devices.

Description

Technical Field

[0001] This invention relates to the field of equipment monitoring technology, and in particular to an accelerator equipment monitoring system based on EPICS (Experimental Physics and Industrial Control System). Background Technology

[0002] Remote monitoring technology for equipment operation status is crucial for the normal operation of large-scale distributed control systems. Distributed control systems, such as those in superconducting cyclotron accelerators, are complex in structure, involve numerous controlled devices, require monitoring of a vast number of states, involve diverse underlying hardware types and communication methods, and each system needs to monitor the operation status of multiple devices. Therefore, a device monitoring system is needed to monitor systems with multiple controlled devices. Summary of the Invention

[0003] This invention aims to at least partially address one of the technical problems in related technologies. Therefore, the object of this invention is to propose an accelerator device monitoring system based on EPICS for monitoring accelerator systems comprising multiple devices.

[0004] To achieve the above objectives, this invention proposes an accelerator device monitoring system based on EPICS. The system includes a client, a device monitoring server, and a local control device. The client provides a monitoring interface for the target accelerator device, receives control commands from the target accelerator device through the monitoring interface, and sends the control commands to the local control device through the device monitoring server. The local control device controls the target accelerator device according to the control commands and sends the target accelerator device's status data to the device monitoring server. The device monitoring server converts the status data into PV (Process Variable) values ​​supported by EPICS, processes the PV values ​​using its own plugin services, and feeds back the PV values ​​and processing results to the client.

[0005] The EPICS-based accelerator device monitoring system of this invention controls the target accelerator device through a local control device and sends the status data of the target accelerator device to the device monitoring server. After receiving the status data, the device monitoring server converts the status data into PV values ​​supported by EPICS and feeds the PV values ​​back to the client. Thus, by converting the status data into PV values, the client can monitor multiple accelerator devices.

[0006] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0007] Figure 1 This is a structural block diagram of an accelerator device monitoring system based on EPICS according to an embodiment of the present invention;

[0008] Figure 2 This is a schematic diagram of the structure of a client-side example of the present invention;

[0009] Figure 3 This is a schematic diagram illustrating the operation of an accelerator device monitoring system based on EPICS, as an example of the present invention.

[0010] Figure 4 This is a schematic diagram of the structure of an accelerator device monitoring system based on EPICS, which is an example of the present invention. Detailed Implementation

[0011] The following description of an EPICS-based accelerator device monitoring system according to embodiments of the present invention is based on the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described with reference to the accompanying drawings are exemplary and should not be construed as limiting the present invention.

[0012] Figure 1 This is a structural block diagram of an accelerator equipment monitoring system based on EPICS according to an embodiment of the present invention.

[0013] like Figure 1 As shown, the EPICS-based accelerator device monitoring system 100 includes: a client 101, a device monitoring server 103, and a local control device 102.

[0014] The client 101 provides a monitoring interface for the target accelerator device, receives control commands from the target accelerator device through the monitoring interface, and sends the control commands to the local control device 102 through the device monitoring server 103. The local control device 102 controls the target accelerator device according to the control commands and sends the status data of the target accelerator device to the device monitoring server 103. The device monitoring server 103 converts the status data into PV values ​​supported by EPICS, processes the PV values ​​using its own plugin services, and feeds back the PV values ​​and processing results to the client 101.

[0015] Specifically, users of client 101 can be administrators, developers, ordinary users, guests, etc. Client 101 is used to communicate with device monitoring server 103, read and write PV values, monitor target accelerator devices in real time, configure and view alarm, archive, and interlock information, and can be directly used to develop remote monitoring programs and interfaces for accelerator devices.

[0016] The equipment monitoring server 103 is used to receive status data such as the operating status, parameters, and collected data of the target accelerator equipment and convert them into PV values ​​supported by EPICS. On the other hand, it receives control signals and write parameters from the client 101 to change the corresponding PV values, and processes information such as alarms, archives, and interlocking information, and writes it into the database.

[0017] Specifically, after receiving status data, the device monitoring server 103 converts the status data into PV values ​​supported by EPICS and feeds the PV values ​​back to the client 101. The device monitoring server 103 also reads the PV values ​​of the alarm parameters already configured on the client 101, compares them with the configured alarm values, and generates a high alarm if the PV values ​​are greater than the configured high limit, and generates a low alarm if the PV values ​​are less than the configured low limit.

[0018] The local control device 102 includes multiple devices and various communication protocols, used for local control of the target accelerator device, and transmits the operating status, parameters, and collected data of the target accelerator device to the device monitoring server 103 in real time.

[0019] Therefore, the target accelerator device is controlled by the local control device 102, and the status data of the target accelerator device is sent to the device monitoring server 103. After receiving the status data, the device monitoring server 103 converts the status data into PV values ​​supported by EPICS and feeds the PV values ​​back to the client 101. Thus, by converting the status data into PV values, the client 101 can monitor multiple accelerator devices.

[0020] The aforementioned local control device 102 supports multiple communication protocols, such as OPC UA (OPC Unified Architecture, a time-sensitive networking technology based on the OPC unified architecture), Modbus (Modbus protocol, MODBUS communication protocol), and S7nodave (the device driver for EPICS of S7 PLCs). The local control device 102 also supports custom development of interface programs and monitoring interfaces. For standard protocols, users do not need to develop interface programs specifically; they only need to configure the device using the device monitoring system to automatically generate the interface program. For devices using the TCP / IP (Transmission Control Protocol / Internet Protocol) protocol, users can use EPICS technology to custom develop corresponding interface programs.

[0021] In one embodiment of the present invention, the client 101 is further configured to: receive a template creation request for the target accelerator device and provide a corresponding configuration template according to the template creation request; receive configuration information of the target accelerator device based on the configuration template and configure the target accelerator device according to the configuration information; compile the target accelerator device to generate an executable program and deploy it to the device monitoring server 103 after configuration; receive a monitoring interface configuration instruction and configure the monitoring interface according to the monitoring interface configuration instruction; receive a service start instruction and start the corresponding service according to the service start instruction; and receive a run instruction so that the client 101 can realize the monitoring function of the target accelerator device.

[0022] Specifically, Client 101 includes: Template Management Component, Device Management Component, Archive Management Component, Alarm Management Component, and Interlock Management Component. The Template Management Component is used for creating and deleting device templates. Devices of the same type can use the same template, and there are multiple ways to create templates, including directly selecting the corresponding protocol in Client 101 or using Excel's import / export function. The Device Management Component is used for creating, deleting, configuring, compiling, and deploying devices. It creates devices based on templates, configures them, compiles them, and deploys the generated executable to the server. The Archive Management Component is used for creating, deleting, and configuring archive parameters. The Alarm Management Component is used for creating, deleting, and configuring alarm parameters, configuring corresponding high and low limits according to design requirements. The Interlock Management Component is used for creating, deleting, and configuring interlock alarm parameters. Interlock alarms are designed with three triggering methods: 0 for falling edge triggering, 1 for rising edge triggering, and 2 for both falling and rising edge triggering.

[0023] In one embodiment of the present invention, the client 101 further includes: a user management component for managing system users; an application management component for managing the switching of system services; a configuration editing component for configuring and editing the management interface of the target accelerator device; and a runtime component for controlling the operation of the system.

[0024] As an example, see Figure 2 The system comprises several components: a user management component for creating and deleting users, setting passwords, and managing permissions; users are divided into multiple permission groups, including administrators, developer users, regular users, and guests; an application management component for enabling and disabling services such as EPICS, MTC (Machine Type Communication), alarm services, archiving services, and interlocking alarm services; a UI (User Interface) configuration editing component for designing and configuring the device interface; and a CSS (Cascading Style Sheets) runtime component for controlling the operation of the device monitoring system. All of these components are located in the application layer. Developer users on client 101 can use the device monitoring system to create projects, configure management templates, manage devices, manage alarm information, manage archived data, manage interlocking information, configure the editing interface, manage users, manage applications, and run the designed monitoring system. Operational users on client 101, such as regular users and guests, can use the device monitoring system to view and confirm alarms, view archived data, view and confirm interlocking alarms, and monitor the runtime interface.

[0025] See Figure 3 The example shown illustrates how, when developing a monitoring system for a specific target accelerator device using the EPICS-based accelerator device monitoring system 100, a template is first created based on the device's communication protocol. Then, a new device is created based on the template. After configuring the device information, archiving, alarm, and interlocking alarm information are configured. Next, the device is compiled to generate an executable program and deployed to the server. The monitoring interface is then drawn and configured using the UI configuration editing function. Finally, services such as EPICS, MTC, alarm, archiving, and interlocking alarm services are started and the monitoring system is run. This standardizes and systematizes the development process, shortens the system development cycle, and makes the entire system standard and open, facilitating subsequent expansion and upgrades.

[0026] Moreover, see Figure 2 In the example shown, client 101 also includes a core framework layer and a language platform layer. The core framework layer includes the core application logic and the core UI, and the language platform layer includes Java and JavaFX.

[0027] In one embodiment of the present invention, the device monitoring server 103 includes: an EPICS service device for converting status data into PV values ​​and converting control commands into PV commands, and sending the PV commands to the local control device 102; a database; and a real-time control framework for providing real-time services based on status data and writing real-time service data into the database, wherein the real-time services include at least one of alarm services, archiving services, and interlocking alarm services.

[0028] Specifically, the EPICS service device is used to receive the operating status, parameters, and collected data of the accelerator equipment and convert them into PV values ​​supported by EPICS. On the other hand, it receives control signals and write parameters from the client 101, changes the corresponding PV values, and transmits them to the accelerator local control device 102. The real-time control framework integrates various plug-in services, including alarm services, archiving services, and interlocking alarm services, to process alarm, archiving, and interlocking information and store it in the database. The database is used to store equipment information, alarm information, archiving information, interlocking information, user information, etc.

[0029] The aforementioned real-time control framework includes: an EPICS client for communicating with EPICS service devices to obtain PV values; a database client for communicating with the database; and an archive service component, an alarm service component, and an interlocking alarm service component, which are used to implement alarm services, archive services, and interlocking alarm services, respectively.

[0030] Specifically, the EPICS client interacts with the EPICS service device, writing and reading PV values; the database client interacts with the database, writing and reading database data; the alarm service component processes alarm information, reading the PV values ​​of the alarm parameters configured on client 101 in real time, comparing them with the configured alarm values, generating a high alarm if the PV values ​​are greater than the configured high limit, and generating a low alarm if the PV values ​​are less than the configured low limit; the archiving service component processes data archiving information, acquiring the archived parameter values ​​configured on client 101 in real time and storing them in the database; and the interlocking alarm service component processes interlocking alarm information, monitoring the interlocking signals configured on client 101 in real time, and writing the interlocking alarm information to the database when the interlocking alarm requirements are met.

[0031] In one embodiment of the present invention, the real-time control framework further includes: an XML (Extensible Markup Language) configuration component, a ZeroMQ communication component, and an MTC message transmission center, which serve as the basic modules of the framework and are used to configure plugin service information and transmit messages for processing plugin services.

[0032] As an example, see Figure 4 The EPICS service device and the real-time control framework communicate using CA digital certificates. The real-time control framework and the database communicate via ODBC (Open Database Connectivity). The database and client 101 communicate via JDBC (Java Database Connectivity). The real-time control framework and client 101 communicate via message queues. Client 101 and device monitoring server 103 communicate via a local area network (LAN), and device monitoring server 103 and local control device 102 communicate via a LAN. Local control device 102 is a PLC (Programmable Logic Controller).

[0033] In summary, the EPICS-based accelerator device monitoring system of this invention controls the target accelerator device through a local control device and sends the status data of the target accelerator device to the device monitoring server. After receiving the status data, the device monitoring server converts the status data into PV values ​​supported by EPICS and feeds the PV values ​​back to the client. Thus, by converting status data into PV values, the client can monitor multiple accelerator devices. Moreover, the target accelerator device can be changed arbitrarily, meeting the requirements of scalability and flexibility. Furthermore, the monitoring of each target accelerator device in the accelerator system is independent and does not interfere with each other.

[0034] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein can be considered as a ordered list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0035] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0036] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0037] In the description of this specification, the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and should not be construed as limiting the present invention.

[0038] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0039] In this specification, unless otherwise stated, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise explicitly defined. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0040] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can mean that the first feature is in direct contact with the second feature, or that the first feature is in indirect contact with the second feature through an intermediate medium. Furthermore, "above," "over," and "on top" of the second feature can mean that the first feature is directly above or diagonally above the second feature, or simply that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature can mean that the first feature is directly below or diagonally below the second feature, or simply that the first feature is at a lower horizontal level than the second feature.

[0041] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. An accelerator equipment monitoring system based on EPICS, characterized in that, The system includes: a client, a device monitoring server, and a local control device; wherein... The client is used to provide a monitoring interface for the target accelerator device, and to receive control commands from the target accelerator device through the monitoring interface, and to send the control commands to the local control device through the device monitoring server. The local control device is used to control the target accelerator device according to the control command, and to send the status data of the target accelerator device to the device monitoring server; The device monitoring server is used to convert the status data into PV values ​​supported by EPICS, process the PV values ​​using its own plugin services, and feed back the PV values ​​and processing results to the client. The client is also used for: Receive the template creation request of the target accelerator device, and provide the corresponding configuration template according to the template creation request; Based on the configuration template, the configuration information of the target accelerator device is received, and the target accelerator device is configured according to the configuration information; After configuration, the target accelerator device is compiled to generate an executable program and deployed to the device monitoring server. The device monitoring server includes: An EPICS service device is used to convert the status data into PV values, convert the control commands into PV commands, and send the PV commands to the local control device. database; A real-time control framework is used to provide real-time services based on the status data and to write the real-time service data into the database. The real-time services include at least one of alarm services, archiving services, and interlocking alarm services.

2. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The client is also configured to: receive monitoring interface configuration instructions and configure the monitoring interface according to the monitoring interface configuration instructions; The system receives a service activation command and activates the corresponding service according to the command, and also receives a run command to enable the client to monitor the target accelerator device.

3. The accelerator equipment monitoring system based on EPICS according to claim 2, characterized in that, The client includes: User management component, used for managing system users; Application management components are used to manage the on / off management of system services of the system. A configuration editing component is used for configuring and editing the management interface of the target accelerator device; Runtime components are used to control the operation of the system.

4. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The EPICS service device and the real-time control framework communicate using digital certificates, and the real-time control framework and the database communicate using open database interconnect.

5. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The real-time control framework includes: An EPICS client is used to communicate with the EPICS service device to obtain the PV value; A database client, used to communicate with the database; The archiving service component, alarm service component, and interlocking alarm service component are used to implement the alarm service, archiving service, and interlocking alarm service, respectively.

6. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The database and the client communicate via a Java database connection.

7. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The real-time control framework and the client communicate using a message queue.

8. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The client and the device monitoring server communicate via a local area network (LAN), and the device monitoring server and the local control device communicate via a LAN.

9. The accelerator equipment monitoring system based on EPICS according to claim 1, characterized in that, The local control device is a programmable logic controller.

Images