An automated control system for telescopes based on the Kafka message bus

Abstract

This invention relates to the field of telescope control systems, specifically an automatic telescope control system based on a Kafka message bus. By replacing traditional Socket communication with a Kafka message bus, it solves the bottleneck of large-scale data transmission between multiple subsystems. The operation scheduling system dynamically generates logical interlocking strategies based on the status of each subsystem, automatically decomposing observation tasks into cross-subsystem command stream orchestration, which is then distributed to the communication interface via an information interaction hub. This enables the solar telescope to have end-to-end automated observation capabilities. Each subsystem connects to a unified message bus through embedded Kafka middleware, forming a publish / subscribe communication mode. When adding or upgrading a subsystem, only a dedicated Topic needs to be defined for seamless integration. This solves the problem of insufficient data throughput in current solar telescopes, which hinders automated observation.

Description

Technical Field

[0001] This invention relates to the field of telescope control systems, specifically to an automatic telescope control system based on the Kafka message bus. Background Technology

[0002] Large ground-based solar telescopes used for solar observation and research are high-precision scientific research equipment integrating optoelectronics, mechanics, and computing. Currently, multiple large solar telescopes in the meter range have been built both domestically and internationally to achieve comprehensive observation of the sun with high spatiotemporal resolution imaging, spectrum, and magnetic field. A large solar telescope includes technologies such as optics, precision mechanics, control, and data acquisition, storage, and processing. It also includes multiple subsystems such as telescope pointing and tracking systems, image quality control systems, thermal control systems, terminal scientific instrument systems, dome systems, and environmental monitoring systems. Therefore, it is very important to know how to operate and schedule these subsystems in an organic way to improve the efficiency of telescope use.

[0003] Due to the complexity and uniqueness of solar telescope instruments, automated observation is difficult to achieve. One of the challenges is the large amount of stable data interaction between the various subsystems in the operation and control system architecture. Currently, my country has one meter-class solar telescope used for astronomical observation and research: the New Vacuum Solar Telescope (NVST), the AIMS (AIMS) ...

[0004] The 2-meter Circular Solar Telescope (2MRST) is currently in the testing phase and is still some time away from on-site installation. The main body of 2MRST has been completed. Functionally, the telescope can be divided into seven subsystems: a pointing and tracking control system, a thermal aperture cooling control system, a secondary mirror attitude and image quality control system, a primary mirror cover control system, a dome control system, and a meteorological and environmental monitoring system. There is also a terminal scientific instrument and data acquisition system that is being debugged. At present, each subsystem of 2MRST can work normally, but it can only be controlled independently. The systems are isolated and lack information links and communication platforms. Therefore, it is impossible to operate efficiently, schedule, and conduct further automated observations. If a client / server system architecture based on NVST or AIMS and developed using the socket API is adopted, the efficiency will be low, the data throughput will not meet the requirements, and further performance improvements and expansions will not be possible. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides an automatic control system for telescopes based on the Kafka message bus, which solves the problem of insufficient data throughput in data interaction between subsystems in current solar telescopes, making it difficult for solar telescopes to achieve automated observation.

[0006] To achieve the above objectives, the present invention provides the following technical solution: an automatic control system for a telescope based on a Kafka message bus, the automatic control system specifically comprising:

[0007] The solar telescope operation scheduling system is used to receive commands from observers and display the status data of each subsystem of the solar telescope. It generates scheduling strategies and logical interlocks based on the observation capabilities of each subsystem of the solar telescope, generates command streams based on the scheduling strategies and logical interlocks, orchestrates them among the subsystems of the solar telescope, and generates and transmits Kafka messages based on the orchestration results.

[0008] The solar telescope information interaction center is used to store the status data of each subsystem of the solar telescope, trace the Kafka messages issued by the solar telescope operation scheduling system, and manage, collect and distribute Kafka messages.

[0009] The solar telescope includes various subsystems and communication interfaces. These subsystems and interfaces are used to control the actions of each subsystem based on Kafka messages sent by the solar telescope's information interaction center, and to generate Kafka messages for feedback based on the status data of each subsystem.

[0010] Preferably, the solar telescope operation scheduling system includes:

[0011] The human-machine interface is used to interact with the observer, receive commands from the observer, and display the status data of each subsystem of the solar telescope to the observer.

[0012] The remote control interface is used to execute the communication protocol for remote control, receive commands from remote observers, and display the information status of each subsystem of the solar telescope to the online observers.

[0013] An observation task generation module is used to receive instructions from the human-machine interface and the remote control interface, and generate observation tasks based on the instructions and the observation capabilities of each subsystem of the telescope.

[0014] The telescope operation scheduling strategy and logical interlock are used to formulate a scheduling strategy based on the observation tasks generated by the observation task generation module, and to perform logical interlocks based on the status of each subsystem of the solar telescope and its operational safety.

[0015] The telescope scheduling command organization and arrangement is used to receive the output from the telescope operation scheduling strategy and logical interlocks, convert the telescope operation scheduling strategy and logical interlocks into specific command streams, and arrange them among the various subsystems of the telescope.

[0016] The first Kafka message middleware is used to generate Kafka messages based on the command stream and orchestration results and transmit them to the solar telescope information interaction center, as well as to receive and parse Kafka messages sent by the solar telescope information interaction center and various subsystems and communication interfaces of the solar telescope.

[0017] Preferably, the solar telescope information interaction center includes:

[0018] The Kafka runtime platform is used to store the status data of each subsystem of the solar telescope, track Kafka messages issued by the solar telescope operation scheduling system, and manage, collect and distribute Kafka messages.

[0019] The Kafka message bus is used for transmitting Kafka messages between the solar telescope operation scheduling system, the solar telescope information interaction center, and the various subsystems and communication interfaces of the solar telescope.

[0020] Preferably, the Kafka runtime platform includes:

[0021] A message database is used to store the status data of each subsystem of the solar telescope, as well as the commands and status data of the solar telescope's operation scheduling system.

[0022] The Kafka message bus server is responsible for message management, collection and distribution, as well as information relay and scheduling.

[0023] The second Kafka message middleware is used for the transmission of Kafka messages.

[0024] Preferably, the solar telescope subsystems and communication interface 30 include several solar telescope subsystems, and the communication layer of the control software of each solar telescope subsystem is embedded with a corresponding Kafka message middleware and message generation and parsing module.

[0025] Preferably, the solar telescope subsystem includes a pointing and tracking control system, a thermal aperture temperature control system, a secondary mirror quality control system, a primary mirror cover and other auxiliary control systems, a terminal scientific instrument and data system, a dome control system, and an operating environment and meteorological parameter monitoring system.

[0026] Compared with existing technologies, this invention provides an automatic control system for telescopes based on a Kafka message bus, which has the following advantages:

[0027] 1. This invention replaces traditional Socket communication with Kafka message bus to solve the bottleneck of large data transmission between multiple subsystems. In particular, it supports millisecond-level synchronous / asynchronous transmission of massive scientific data such as telescope imaging and spectra. The operation scheduling system dynamically generates logical interlocking strategies based on the status of each subsystem, automatically decomposes the observation task into cross-subsystem command stream orchestration, and distributes it to the communication interface through the information interaction center. This enables the solar telescope to have full-link automated observation capabilities for the first time, greatly improving observation efficiency.

[0028] 2. Each subsystem of this invention is connected to a unified message bus through an embedded Kafka middleware, forming a publish / subscribe communication mode. When adding or upgrading a subsystem, only a dedicated Topic needs to be defined for seamless integration. The message database of the Kafka runtime platform persistently stores state data, and together with the bus server, it realizes message traceability and redundant backup, ensuring system fault tolerance. This architecture breaks through the limitations of the traditional C / S mode, greatly reducing the subsystem expansion cost of the 2.5-meter-class large solar telescope and significantly reducing maintenance complexity.

[0029] 3. This invention uses message event-driven logical interlocking to monitor critical states in real time. It triggers cross-system protection commands instantly through Kafka. After subsystem fault messages are broadcast via the message bus, the scheduling system dynamically reorganizes the observation process, avoiding system paralysis caused by single point of failure. The response speed for major accidents is shortened from minutes to milliseconds by manual intervention, greatly improving equipment safety.

[0030] 4. The instructions received through the human-machine interface and remote interface are finally converted into standardized Kafka messages by the task generation module, which are adapted to various observation mode parameters such as imaging, magnetic field and spectrum. Remote observers can obtain data from each subsystem in real time by subscribing to status topics, and realize cross-regional multi-terminal collaborative operation by combining the distributed characteristics of Kafka. Attached Figure Description

[0031] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0032] Figure 1 This is a structural block diagram of the telescope automatic control system of the present invention;

[0033] Figure 2 This is a schematic diagram of the communication protocol established by the Kafka message bus in this invention;

[0034] Figure 3 This is a flowchart illustrating the main workflow of the telescope automatic control system of the present invention.

[0035] In the diagram: 10. Solar telescope operation and scheduling system; 101. Human-machine interface; 102. Remote control interface; 103. Observation task generation module; 104. Telescope operation and scheduling strategy and logic interlocks; 105. Telescope scheduling command organization and arrangement; 106. First Kafka message middleware; 20. Solar telescope information interaction center; 201. Kafka operation platform; 20101. Message database; 20102. Kafka message bus server; 20103. Second Kafka message middleware; 202. Kafka message bus; 30. Solar telescope subsystems and communication interfaces; 30103. Pointing and tracking control system; 30203. Thermal aperture temperature control system; 30303. Secondary mirror quality control system; 30403. Primary mirror cover and other auxiliary control systems; 30503. Terminal scientific instruments and data system; 30603. Dome control system; 30703. Operating environment and meteorological parameter monitoring system. Detailed Implementation

[0036] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. This will allow for a full understanding of how the present application uses technical means to solve technical problems and achieve technical effects, and to facilitate its implementation.

[0037] Those skilled in the art will understand that all or part of the steps in the methods of the following embodiments can be implemented by a program instructing related hardware. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0038] To address the problem that current solar telescopes struggle to achieve automated observations due to insufficient data throughput in data interaction between subsystems, this invention provides an automatic control system for solar telescopes based on the Kafka message bus. The Kafka message bus is used to construct a control system that can be used for solar telescopes.

[0039] First, a communication platform is built between the subsystems. The real-time data interaction between the subsystems is solved based on the Kafka message bus. The high data throughput of the Kafka message bus enables real-time image data transmission in the solar telescope. Point-to-point and publish / subscribe communication modes are used to establish synchronous and asynchronous communication between the subsystems. Synchronous communication enables real-time command interaction and acquisition of key status data between the telescope subsystems. Asynchronous communication enables the propagation of non-real-time status data of the telescope subsystems among other subsystems. The safety control and interlocking problems in the telescope are solved by responding to message events in the message bus in real time.

[0040] Then, a communication protocol between the various subsystems of the solar telescope is constructed. Based on Kafka topics and information from each subsystem within the solar telescope, each topic for information transmission by each subsystem and its corresponding message parsing algorithm are established to enable dialogue and communication between the subsystems of the solar telescope. This allows for the identification of which subsystem a particular message originates from, its meaning, and its parameters. Finally, an operational scheduling strategy for the entire system is constructed. The operation and control system generates observation tasks based on observation requirements, formulates scheduling strategies based on the status feedback information from each subsystem, and implements safety supervision and logical interlocks. It generates command streams for each subsystem and transmits them to each subsystem via the message bus. Each subsystem selects the corresponding message for subsequent consumption, including parsing commands, obtaining parameters, and executing corresponding actions, and provides feedback on the subsystem's operational status.

[0041] This invention physically and logically connects and integrates the various isolated subsystems of a solar telescope in the prior art, establishing an operational control system for the solar telescope, such as... Figure 1 The diagram shown is a structural block diagram of the present invention, which mainly includes three parts: a solar telescope operation scheduling system 10, a solar telescope information interaction center 20, and various subsystems and communication interfaces of the solar telescope 30. The following is a detailed description of each of the three components:

[0042] The solar telescope operation scheduling system 10 is used to receive commands from observers and display the status data of each subsystem of the solar telescope. It generates scheduling strategies and logical interlocks based on the observation capabilities of each subsystem of the solar telescope, generates command streams based on the scheduling strategies and logical interlocks, orchestrates them among the subsystems of the solar telescope, and generates and transmits Kafka messages based on the orchestration results. Specifically, it includes: a human-machine interface 101, a remote control interface 102, an observation task generation module 103, a telescope operation scheduling strategy and logical interlocks 104, a telescope scheduling command organization and orchestration 105, and a Kafka first Kafka message middleware 106. The human-machine interface 101 is responsible for interacting with observers, receiving commands from them, and displaying the status data of each subsystem of the solar telescope. The remote control interface 102 executes the remote control communication protocol, receives commands from remote observers, and displays the information status of each subsystem of the solar telescope to online observers. It's important to note that the human-machine interface 101 generally has a higher priority than the remote control interface 102. The observation task generation module 103 receives instructions from both the human-machine interface 101 and the remote control interface 102, and generates observation tasks based on these instructions and the observation capabilities of each subsystem of the telescope. The telescope operation scheduling strategy and logic interlock 104 is the core part of the solar telescope operation scheduling system 10. It formulates a scheduling strategy based on the observation tasks generated by the observation task generation module 103, and simultaneously considers the status of each subsystem of the solar telescope. The system's status is assessed to determine its operational safety, and logical interlocks are implemented. The telescope scheduling command organization and orchestration 105 receives the output from the telescope operation scheduling strategy and logical interlocks 104, converts the scheduling strategy and logical interlocks of the telescope operation scheduling strategy and logical interlocks 104 into specific command streams, and orchestrates them among the various subsystems of the telescope. For example, it includes which commands need to be sent to which subsystems, which commands need to be communicated synchronously point-to-point, which commands need to be communicated asynchronously by publishing / subscribing, and which statuses need to be responded to. Finally, the Kafka first Kafka message middleware 106 in the solar telescope operation scheduling system 10 generates Kafka messages based on the command streams and orchestration results and transmits them to the solar telescope information interaction center 20, as well as receiving and parsing Kafka messages sent by the solar telescope information interaction center 20 and the various subsystems and communication interfaces 30 of the solar telescope.

[0043] The solar telescope information interaction center 20 is used to achieve efficient and stable communication between the telescope subsystems, store the status data of each subsystem, track Kafka messages issued by the solar telescope operation scheduling system 10, and manage, collect, and distribute Kafka messages. The solar telescope information interaction center 20 includes a Kafka runtime platform 201 and a Kafka message bus 202. The Kafka runtime platform 201 is deployed on one or more servers and includes three parts: a message database 20101, a Kafka message bus server 20102, and a second Kafka message middleware 20103. The message database 20101 is used to store the status data of each subsystem of the solar telescope and the data from the solar telescope operation scheduling system 10. Command and status data are stored completely, while larger data, such as image data, are selectively saved. The monitored images are mainly used for operational control judgments rather than scientific data. The message database 20101 helps with the persistence and recoverability of message command data. The Kafka message bus server 20102 is responsible for message management, collection, and distribution, as well as information relay and scheduling. It is the brain of communication data management and uses a platform developed with Kafka. The second Kafka message middleware 20103 is the software interface that specifically implements communication and is used for Kafka message transmission. This invention is based on it for secondary development and packaging of API (Application Programming Interface) to meet the information usage needs between various subsystems of the solar telescope.

[0044] The solar telescope's subsystems and communication interface 30 are used to control the actions of each subsystem based on Kafka messages sent by the solar telescope's information interaction center 20, and to generate Kafka messages for feedback based on the status data of each subsystem. The dotted-line encloses several solar telescope subsystems. Generally, the solar telescope subsystems include a pointing and tracking control system 30103, a thermal aperture temperature control system 30203, a secondary mirror quality control system 30303, a primary mirror cover and other auxiliary control systems 30403, a terminal scientific instrument and data system 30503, a dome control system 30603, and an operating environment and meteorological parameter monitoring system 30703. These subsystems can complete the control and corresponding functions and tasks in the solar telescope, but they are not an organic whole. The communication layer of the control software of each subsystem also needs to embed Kafka message middleware and message generation and parsing modules.

[0045] Since the subsystems of a solar telescope operate independently in existing technologies, this invention integrates these subsystems through a solar telescope information interaction hub 20 to achieve real-time information interaction between them. Each subsystem of the solar telescope is equipped with a Kafka message middleware and a message generation and parsing module. The Kafka message middleware handles information transmission, while the message generation and parsing module packages and decomposes the information. In the information packaging, each subsystem is grouped into a Topic. Below the topic (pic) are the instructions, status, and information parameters of various systems. Logically, instructions are the operations that lower-level consumer systems are instructed to perform, parameters are the parameters passed to lower-level consumer systems, and status data are the images or other data sent by the data acquisition system to the upper-level operation scheduling system. During information exchange, each subsystem of the solar telescope sends the topic (Topic) to the Kafka message bus server 20102 in the solar telescope information exchange hub 20. The Kafka message bus server 20102 then distributes this information to each subsystem, ultimately achieving real-time transmission of large amounts of information between these subsystems at the millisecond level.

[0046] In these systems, the solar telescope operation scheduling system 10 is logically at the top level of the entire system, responsible for scheduling and managing the various subsystems of the solar telescope. Among them, the pointing and tracking control system 30103 is responsible for pointing the telescope at the sun, finding and tracking observation targets on the solar surface; the thermal aperture temperature control system 30203 limits the field of view when the telescope is pointing at the sun, generally reflecting 99% of the light out of the telescope system, allowing only about 1% of the light to enter the telescope and back-end instruments; the thermal aperture temperature control system 30203 needs to cool the thermal aperture to prevent it from burning out; and the primary mirror cover and other auxiliary control systems 3... 0403 is responsible for opening the primary mirror cover of the telescope and closing it when necessary to protect the primary mirror. The secondary mirror quality control system 30303 improves the imaging quality of the telescope by adjusting the attitude of the secondary mirror, including focusing the system. The terminal scientific instrument and data system 30503 performs spectral analysis and imaging of the sun and records the corresponding spectral and imaging data. The dome control system 30603 provides wind and rain protection for the solar telescope. The operating environment and meteorological parameter monitoring system 30703 monitors the operating environment data of the telescope, such as temperature, humidity, air pressure, wind speed and direction, and cloud cover, to determine whether the operating environment of the telescope is safe.

[0047] The operation of the entire automatic control system begins with the solar telescope operation scheduling system 10. After receiving the command, the human-machine interface 101 or remote control interface 102 of the solar telescope operation scheduling system 10 generates the observation task and starts the observation process to schedule, operate and manage the various subsystems of the solar telescope. Depending on the observation mode, the specific operation details may vary, but the sequential execution process of the major links is basically the same, including the stages of observation preparation, starting each subsystem, observation and shutting down each subsystem. After the solar telescope operation scheduling system 10 generates an observation task, it executes the following steps in sequence: First, it monitors the telescope's operating environment and meteorological parameters through the operating environment and meteorological parameter monitoring system 30703. Once the observation conditions are met, it proceeds to step two. Second, it activates the thermal aperture temperature control system 30203. Third, it opens the dome through the dome control system 30603. Fourth, it activates the solar telescope's pointing and tracking control system 30103 to point the telescope at the observation target on the solar surface and track it. Fifth, it activates the primary mirror cover and other auxiliary control systems 30403 to open the telescope cover. Sixth, it opens the secondary mirror quality control system 30303. Seventh, it opens the terminal scientific instrument and data system 30503 and records data. During operation, scheduling, and control, there are several critical logical interlocks: First, if the thermal aperture temperature fails, the telescope pointing and tracking control system 30103 must control the lens to deviate from the sun, the primary mirror cover must be closed for protection, and the data recording system must stop. Second, if the meteorological parameters are not met, the dome must be closed and data recording must stop. The dome can only be opened after the meteorological conditions are met. Third, the terminal scientific instruments and data system can only work after the telescope is pointed at the observation target and the secondary image quality control system 30303 is working properly.

[0048] The 2MRST (2-meter Circular Solar Telescope) is a solar telescope currently undergoing testing. Figure 2 and Figure 3 This is an example of the telescope used in this invention. Figure 2 The definition of a communication protocol based on the Kafka message bus is given. Figure 3 The main process of operation scheduling is given.

[0049] The hardware platform of the solar telescope operation scheduling system 10 is an industrial control computer, a 10 Gigabit network card, and a Windows operating system. The hardware platform of the solar telescope information interaction center 20 is one or more high-performance servers, a Linux operating system or a Windows operating system, a Kafka service platform, and a database. The various subsystems and communication interfaces 30 of the solar telescope are industrial control computer operating platforms. The software modules of this invention are embedded into the original subsystems of 2MRST on the industrial control computer platform. The subsystems in 2MRST can use Windows operating systems or Linux operating systems, etc. The industrial control computer in the solar telescope operation scheduling system 10, the server in the solar telescope information interaction center 20, and the industrial control computers of the various subsystems and communication interfaces 30 of the solar telescope can be connected by a 10 Gigabit switch to ensure data communication speed.

[0050] The structure and establishment of the communication platform: A Kafka service platform, database, and message bus are established within the solar telescope's information interaction hub 20. The specific implementation process is as follows: First, a Kafka server hardware and software platform is established. A server meeting the requirements (such as an Inspur NF8480G7) is selected, and a Linux operating system is installed. On the server, the Kafka server software is installed, the Kafka server's IP address is configured, and Kafka is set to start automatically. Then, communication topics are created for several subsystems: the tracking control system 30103, the thermal aperture temperature control system 30203, the secondary mirror mass control system 30303, the primary mirror cover and other auxiliary control systems 30403, the terminal scientific instrument and data system 30503, the dome control system 30603, and the operating environment and meteorological parameter monitoring system 30703. Second, a message middleware for Kafka communication in each subsystem of the solar telescope is established. This requires downloading the vcpkg software package, installing the librdkafka library, and establishing a C++... The Kafka communication platform uses PUB / SUB communication mode to connect to the Kafka server's IP address and port, listen for messages, and produce messages to topics. Thirdly, it configures message production and consumption (consumption), implementing message generation and parsing. In the message producer configuration, Brokers (an object containing IP and port information) are configured to set up and implement message delivery and callbacks. In the message consumer configuration, Brokers are configured, and the message consumption mode is set to the latest message consumption mode. Finally, the platform subscribes to the topics to be consumed.

[0051] Definition and implementation of communication protocols Figure 2The communication protocol is based on the Kafka message bus. The protocol first sets the TOPICs for each subsystem of the solar telescope for data transmission. Then, it includes commands and corresponding parameters for each subsystem, including commands with and without parameters. In commands without parameters, the part before the hyphen ("-") is the name of the system module. For example, in a system-level command, SYS-ON indicates that the underlying systems are enabled. In commands with parameters, the command itself explains certain parameters. For example, OBV-MODE indicates the observation mode, with three options: IMAGE, MAGNETIC, and SPECTRUM, representing imaging observation mode, magnetic field observation mode, and spectroscopic observation mode, respectively. Based on these message definitions, message generation and parsing in each subsystem of the solar telescope and communication interface 30 are implemented. Specifically, this is done by wrapping application functions in Kafka and providing them for call by the existing subsystems in each subsystem of the solar telescope and communication interface 30.

[0052] The automatic control system of this solar telescope operates by using the solar telescope operation scheduling system 10 to control the operation of each subsystem and complete the designated observation tasks. First, the system is turned on, then the system operates its observations, and finally the system is turned off.

[0053] System startup process: First, the main control system, namely the solar telescope operation scheduling system 10, is started. After receiving the command input by the observer through the human-machine interface, the main control system sends the corresponding message to the Main_control_topic of the Kafka server, and sends the startup command message SYS-ON to each subsystem, such as the tracking control system 30103, the thermal aperture temperature control system 30203, the secondary mirror mass control system 30303, the primary mirror cover and other auxiliary control systems 30403, the terminal scientific instrument and data system 30503, the dome control system 30603, and the operating environment and meteorological parameter monitoring system 30703. After each subsystem listens to the message in the Main_control_topic, it starts up and performs a self-check. Then, each subsystem reports its health status. The main system then decides whether to execute the observation based on the health status of each subsystem. If the observation can be executed, it enters the observation ready state. If the observation cannot be executed, it enters the waiting state and continues to monitor.

[0054] System observation process: After the system is in the observation preparation state, it receives observation commands and generates observation tasks based on the commands. Based on the observation tasks, the observation mode is determined. The system's observation modes include imaging observation, spectroscopic observation, and magnetic field observation. Then, the workflows of each system are initiated, such as... Figure 3As shown. At this time, the various subsystems of the solar telescope begin to operate: based on meteorological parameters, the dome is opened, the thermal aperture temperature control system 30203 begins to operate, cooling the thermal aperture, providing the observation target to the pointing and tracking control system 30103, pointing the telescope at the observation target and tracking it, opening the telescope lens cover to allow light to enter the telescope system, starting to acquire telescope image quality and controlling image quality; the terminal scientific instruments are activated to acquire and store scientific data, specifically as follows:

[0055] After the operating environment and meteorological parameter monitoring system 30703 detects the SYS-ON message in the Main_control_topic of the solar telescope operation scheduling system 10, it begins to monitor the weather. Then, based on the current weather conditions, it decides whether to send ENV_STATE (OK) or ENV_MONIT (NG) to Env_topic. If ENV_STATE (NG) is sent, the task is terminated and a parameter message indicating the reason for termination is sent to Env_topic; if ENV_STATE (OK) is sent, the system proceeds to the next step.

[0056] After the dome control system 30603 detects the environmental status ENV_STATE (OK) message in the Env_ topic of the operating environment and meteorological parameter monitoring system 30703, it starts the dome control system 30603. If the start fails, it sends the DOME_STATE (NG) command to the Dome_topic and sends a parameter message indicating the reason for the failure. If the start is successful, it sends the DOME_STATE (OK) command to the Dome_topic, and the system proceeds to the next step.

[0057] After the thermal aperture temperature control system 30203 sends the Dome_MONIT (OK) message in the Dome_topic of the Dome control system 30603, it performs thermal aperture temperature control according to the preset parameters. If the system malfunctions after running for five minutes, it sends a parameter message to Heat_ctrl_topic indicating the cause of the malfunction. If it is determined that the system is running normally, the thermal aperture temperature control system 30203 sends a command message HEAT_CTRL_STATE (OK) to Heat_ctrl_topic, and the system proceeds to the next step.

[0058] After the tracking control system 30103 detects the HEAT_CTRL_STATE (OK) command from the thermal aperture temperature control system 30203 in the Heat_ctrl_topic message, it starts executing the tracking control system hardware. At the same time, it determines the pointing of the altitude and azimuth axes based on the parameter messages monitored from the Main_control_topic. If the start fails, it sends POINT_TRACK_STATE (NG) to the PointTrack_control_topic and sends a parameter message indicating the reason for the failure. If the start is successful, it sends the POINT_TRACK_STATE (OK) command to the PointTrack_control_topic, and the system proceeds to the next step.

[0059] After the main mirror cover and other auxiliary control systems 30403 detect the POINT_TRACK_STATE (OK) message of the pointing tracking system in the PointTrack_control_topic of the pointing tracking control system 30103, the hardware layer opens the mirror cover. If the mirror cover opening is abnormal, a MIR_STATE (NG) command is sent to the Mirror_cover_topic, and a parameter message is sent to indicate the cause of the abnormality. If the mirror cover opening is normal, a MIR_STATE (OK) command is sent to the Mirror_cover_topic, and the system proceeds to the next step.

[0060] After the secondary mirror quality control system 30303 detects the MIR-START (OK) message in the Mirror_cover_topic message of the primary mirror cover and other auxiliary control systems 30403, the hardware layer activates the secondary mirror quality control system 30303, adjusts the six-bar attitude, and simultaneously sends the wavefront probe image to the Image_control_topic. The main control system will then display the image in the corresponding image frame on the main control interface based on the image data in the Image_control_topic. If the six-bar adjustment and wavefront probe operation malfunctions, an IMAGE_STATE (NG) command is sent to the Image_control_topic along with a parameter message indicating the reason for the failure. If the operation is normal, an IMAGE_STATE (OK) command is sent to the Image_control_topic, and the system proceeds to the next step.

[0061] After the terminal scientific instrument and data system 30503 detects IMAGE_STATE (OK) in the image_control_topic of the sub-image quality control system 30303, it indicates that the entire system has been adjusted and is ready for imaging. Then, all terminal instruments, such as the terminal camera and spectrometer, are activated. If these devices fail to activate, a DATA_STATE (NG) command is sent to the Data_instrument_topic along with a parameter message indicating the reason for the failure. If the operation is normal, a DATA_STATE (OK) command is sent to the Data_instrument_topic.

[0062] System shutdown procedure: The main control system, namely the solar telescope operation scheduling system 10, sends the SYS-OFF command to Main_control_topic. After detecting the SYS-OFF command in Main_control_topic, each subsystem of the telescope shuts down in turn.

[0063] The invention was tested on the 2-meter circumferential solar telescope 2MRST and related simulation platforms. The system can meet the operation and control requirements of 2MRST and can schedule the organic operation of its various subsystems according to the observation requirements.

[0064] It should be noted that the system provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0065] The above embodiments provide a detailed description of the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. An automatic control system for a telescope based on a Kafka message bus, characterized in that, The automatic control system specifically includes: The solar telescope operation scheduling system (10) includes at least: The telescope operation scheduling strategy and logic interlock (104) are used to formulate a scheduling strategy based on the observation task, and to perform logic interlock based on the status of each subsystem of the solar telescope and its operational safety. Telescope scheduling command organization and orchestration (105) is used to receive the output from the telescope operation scheduling strategy and logic interlock (104), convert the scheduling strategy and logic interlock (104) into specific command streams, and orchestrate them among the various subsystems of the telescope. The first Kafka message middleware (106) is used to generate Kafka messages based on the command stream and orchestration results and transmit them to the solar telescope information interaction center (20), as well as to receive and parse Kafka messages sent by the solar telescope information interaction center (20) and the various subsystems and communication interfaces (30) of the solar telescope; The solar telescope information interaction hub (20) includes the Kafka runtime platform (201) and the Kafka message bus (202). The Kafka runtime platform (201) is used to store the status data of each subsystem of the solar telescope and to track Kafka messages issued by the solar telescope operation scheduling system (10), as well as to manage, collect, and distribute Kafka messages, including: The message database (20101) is used to store the status data of each subsystem of the solar telescope and the command and status data of the solar telescope operation scheduling system (10); The Kafka message bus server (20102) is responsible for message management, collection and distribution, as well as message relay and scheduling; The second Kafka message middleware (20103) is used for Kafka message transmission; The Kafka message bus (202) is used for the transmission of Kafka messages between the solar telescope operation scheduling system (10), the solar telescope information interaction center (20), and the various subsystems and communication interfaces (30) of the solar telescope; The solar telescope's subsystems and communication interfaces (30) are used to control the actions of each subsystem based on Kafka messages sent by the solar telescope's information interaction center (20), and to generate Kafka messages for feedback based on the status data of each subsystem. The solar telescope subsystems include a pointing and tracking control system (30103), a thermal aperture temperature control system (30203), a secondary mirror mass control system (30303), a primary mirror cover and other auxiliary control systems (30403), a terminal scientific instrument and data system (30503), a dome control system (30603), and an operating environment and meteorological parameter monitoring system (30703). The solar telescope's operation is scheduled during system startup and shutdown. The system (10) sends start and stop command messages to the preset topics of the Kafka server respectively. The operating environment and meteorological parameter monitoring system (30703) monitors the weather according to the start command message, and sends a message to start the dome control system (30603) when the conditions are met. After the start is successful, it sends a message to start the thermal aperture temperature control system (30203) according to the preset parameters. After the operation is successful, it sends a message to start the pointing tracking control system (30103). After the start is successful, it sends a message to start the sub-image quality control system (30303) to feed back and display the detected image. After the image is detected, it sends a message to start all terminal instruments of the terminal scientific instrument and data system (30503) to take pictures.

2. The telescope automatic control system based on Kafka message bus according to claim 1, characterized in that, The solar telescope operation scheduling system (10) also includes: Human-machine interface (101) is used to interact with the observer, receive commands from the observer, and display the status data of each subsystem of the solar telescope to the observer. The remote control interface (102) is used to execute the communication protocol for remote control, receive commands from remote observers, and display the information status of each subsystem of the solar telescope to the online observers. The observation task generation module (103) is used to receive instructions from the human-machine interface (101) and the remote control interface (102), and generate observation tasks according to the instructions and the observation capabilities of each subsystem of the telescope.

3. The telescope automatic control system based on Kafka message bus according to claim 1, characterized in that, The solar telescope subsystems and communication interface (30) include several solar telescope subsystems. The communication layer of the control software of each solar telescope subsystem is embedded with a corresponding Kafka message middleware and message generation and parsing module.

Images