A space launch data online acquisition monitoring system and method supporting multiple protocols

Abstract

The present application relates to the technical field of space launch monitoring, and in particular to a space launch data online acquisition monitoring system and method supporting multiple protocols, the monitoring system comprising a multiple protocol acquisition module, an address configuration module, a data preprocessing module, a real-time historical database storage module, and a process breakpoint monitoring module, the present application being applied to data acquisition monitoring of space launch processes, and capable of realizing real-time acquisition monitoring of data in various control systems and monitoring systems of space launches, solving the problems of heterogeneous data acquisition fusion, storage, processing, calculation and monitoring, being conducive to overall data analysis and early warning of tasks, realizing automatic start and stop of the whole process of the launch site, providing data support for subsequent intelligent unmanned operation of the launch site, and ensuring safe and reliable completion of tasks.

Description

Technical Field

[0001] The present invention relates to the technical field of space launch monitoring, and in particular to a space launch data online acquisition and monitoring system and method supporting multiple protocols. Background Art

[0002] Currently, launch sites include multiple types of equipment, each dedicated to collecting and monitoring different data and requiring different parameter configurations. Data from each device currently uses its own protocols. Due to the varying collection times and frequencies, data is non-standardized, and the complex data collection environment, including massive amounts of loaded data, complex data relationships, and inconsistent data quality, often leads to protocol conflicts and low collection efficiency.

[0003] Space launches place high demands on safety performance, requiring autonomous monitoring of all systems, subsystems, and equipment within the launch site to identify potential operational hazards and provide early warnings to minimize the likelihood of risk. Currently used data analysis technologies rely on online monitoring and manual inspections of key areas prior to launch. To quickly detect equipment failures and eliminate risks, real-time monitoring and diagnosis of equipment operating conditions are required before launch, ultimately ensuring the safe and stable completion of launch missions. Summary of the Invention

[0004] The purpose of the present invention is to provide a multi-protocol online space launch data acquisition and monitoring system and method to solve the problems of multi-source heterogeneous protocol acquisition difficulties and inaccurate process monitoring, analysis and evaluation in real-time detection and diagnosis, hidden danger investigation and early warning during space launch in the existing technology, so as to reduce the probability of risk occurrence.

[0005] To solve the above technical problems, the present invention provides an online space launch data acquisition and monitoring system that supports multiple protocols, including a multi-protocol acquisition module, an address configuration module, a data preprocessing module, a real-time history library storage module, and a process breakpoint monitoring module, wherein:

[0006] The multi-protocol acquisition module includes a sensor acquisition module, a video acquisition module, and a file acquisition module;

[0007] The address configuration module sets different addresses in the IP network segment, and the IP addresses correspond to the collection devices in the multi-protocol collection module one by one to perform data coding identification;

[0008] The data preprocessing module is responsible for performing data verification on the data collected by the multi-protocol acquisition module, completing data re-recording and data cleaning;

[0009] The real-time history database storage module forms full-range time series data by marking the data with time tags, and stores the data processed by the data preprocessing module;

[0010] The process breakpoint monitoring module calls real-time historical database data and generates a flow chart based on the operating logic of the equipment and the system it is in, through monitoring mode, sequential control mode, and breakpoint mode. By monitoring and alarming process breakpoints, the entire launch site process can be automatically started and stopped.

[0011] The present invention also provides another method for online acquisition and monitoring of space launch data that supports multiple protocols. The method adopts the above system to perform online acquisition and monitoring of space launch data, including the following steps:

[0012] Data acquisition is performed through the sensor acquisition module, video acquisition module, and file acquisition module;

[0013] The address configuration module sets the IP address to correspond to the acquisition devices in the sensor acquisition module, video acquisition module and file acquisition module one by one, and performs data coding identification;

[0014] After receiving the data, the data preprocessing module performs data verification, completes data re-entry and data cleaning;

[0015] The real-time history database storage module stores the data processed by the data pre-processing module;

[0016] The process breakpoint monitoring module calls the data in the real-time historical database storage module, and generates a flow chart through monitoring mode, sequential control mode, and breakpoint mode according to the operating logic of the acquisition device and the module where the acquisition device is located. By monitoring the process breakpoints and issuing alarms, the entire launch site process can be automatically started and stopped.

[0017] By adopting the above technical solution, the present invention has the following beneficial effects:

[0018] 1. This method is applied to data acquisition and monitoring of space launches. It can realize real-time data acquisition and monitoring of various control systems and monitoring systems of space launches, solving the problems of heterogeneous data acquisition, fusion, storage, processing, calculation and monitoring. It is conducive to overall data analysis and early warning of the mission, and realizes automatic start and stop of the entire launch site. It provides data support for the subsequent intelligent unmanned operation of the entire launch site, ensuring the safe and reliable completion of the mission.

[0019] 2. The present invention classifies the same type of devices and then determines the protocol combination of each smart device, which can effectively improve the data management efficiency of each type of device, prevent the problem of confusion in data collection and monitoring of devices of different types and different protocol combinations, and facilitate overall data analysis and early warning of tasks.

[0020] 3. The system data transmission provided by the present invention has high stability and reliability, and can realize real-time data collection and monitoring of various control systems and monitoring systems of space launches, solving the problem that data needs to be displayed by multiple collection devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0022] Figure 1 A schematic diagram of an online space launch data acquisition and monitoring system supporting multiple protocols provided by an embodiment of the present invention;

[0023] Figure 2 A schematic diagram of the classification of launch site equipment provided by another embodiment of the present invention;

[0024] Figure 3 A process breakpoint monitoring hierarchy diagram is provided for another embodiment of the present invention. DETAILED DESCRIPTION

[0025] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0026] In the description of the present invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings and are intended solely to facilitate and simplify the description of the present invention. They are not intended to indicate or imply that the devices or components referred to must have, be constructed, or operate in a specific orientation, and therefore should not be construed as limitations on the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0027] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on the specific circumstances.

[0028] The present invention will be further explained below with reference to specific embodiments.

[0029] like Figure 1 As shown, this embodiment provides an online space launch data acquisition and monitoring system that supports multiple protocols, including a multi-protocol acquisition module, an address configuration module, a data preprocessing module, a real-time history library storage module, and a process breakpoint monitoring module, wherein:

[0030] The multi-protocol acquisition module includes a sensor acquisition module, a video acquisition module, and a file acquisition module;

[0031] The address configuration module sets different addresses in the IP network segment, and the IP addresses correspond to the collection devices in the multi-protocol collection module one by one to perform data coding identification;

[0032] The data preprocessing module is responsible for data collection, data verification, data re-entry and data cleaning;

[0033] The real-time history database storage module forms full-range time series data by marking the data with time tags, and stores the data processed by the data preprocessing module;

[0034] The process breakpoint monitoring module calls real-time historical database data and generates a flow chart based on the operating logic of the equipment and the system it is in, through monitoring mode, sequential control mode, and breakpoint mode. By monitoring and alarming process breakpoints, the entire launch site process can be automatically started and stopped.

[0035] The embodiments of the present invention realize real-time collection and monitoring of data in various control systems and monitoring systems of space launches, solving the problem that data needs to be displayed by multiple collection devices. The data transmission is highly stable and reliable, and a set of process breakpoint verification logic is set up to provide data support for intelligent unattended operation, ensuring the safe and reliable completion of the mission.

[0036] Multi-protocol acquisition can collect more data as a basis for analysis, address configuration and data preprocessing can better understand the data, and the real-time historical database can be used as a data warehouse for data storage and distribution. Process breakpoint monitoring can make some predictive judgments based on the results of visual analysis and data mining, conduct internal process deduction, analyze and judge the severity of failure modes, and build a process breakpoint monitoring and evaluation model.

[0037] In one embodiment of the present invention, the sensor acquisition module, through the adaptation of sensors including fiber Bragg gratings, acceleration, velocity, displacement, pressure, temperature, and humidity, implements interconnected communication using protocols such as Profibus, Modbus, 101, and 104. It connects to an Ethernet network via an Ethernet interface and then to a host computer via a switch, forming an open network system. The video acquisition module establishes and controls media sessions at both ends of the communication using the RTSP (Real-Time Stream Protocol), allowing the client to control the media stream in real time by issuing commands. The file acquisition module encrypts data transmitted from the database using HTTPS (Hypertext Transfer Protocol Secure), FTPS (File Transfer Protocol SSL), or SFTP (Secure File Transfer Protocol), establishing separate transmission channels and ports for acquisition and transmission.

[0038] By classifying the same type of devices and then determining the protocol combination of each smart device, the present invention can effectively improve the data management efficiency of each type of device, prevent the problem of confusion in data collection and monitoring of devices of different types and different protocol combinations, and facilitate overall data analysis and early warning of tasks.

[0039] like Figure 2 As shown, in one embodiment, the launch site equipment is first divided into eight types, specifically A, B1, B2, C, D, E, F, and G. The eight types can be divided into three categories for data transmission: sensors (A, B1, B2, C, E, F), video (D), and file (G), each with a different transmission method.

[0040] Class A devices are direct-connect signal devices. These include various transmitters, actuators, pumps, valves, and more. Analog input and output devices uniformly utilize 4-20mA signal transmission; digital input and output devices uniformly utilize passive access.

[0041] Class B1 equipment is a dedicated interface device. During the launch site renovation process, specialized communication switching equipment was deployed to enable intelligent integration of existing equipment. This type of equipment connects to the cabinet module via ModBus TCP, communicating upstream using a timed response method. Its downstream interface connects to existing equipment via a dedicated interface.

[0042] Class B2 equipment refers to ground-based equipment with a dedicated communication interface. This type of equipment connects to the cabinet's dedicated communication module through its own communication interface. This type of equipment typically has a communication interface compatible with the cabinet's communication module and can be directly connected to the communication module.

[0043] Class C equipment, which is ground equipment with only specific interfaces, requires dedicated communication interface equipment (Class B1) for intelligent transformation. This type of equipment is typically connected to the cabinet via a dedicated interface device. Communication with the dedicated communication interface device is typically handled through a timed response mechanism.

[0044] Class D devices are on-site video devices. Through their own RTSP (Real Time Streaming Protocol) conversion, the device transmits data to a remote monitoring server via Ethernet.

[0045] Class E devices are wireless gateway devices. These devices connect on-site front-end IoT data to the cabinet. They connect to the cabinet's communication module via ModBus TCP and connect to wireless internet devices within the transmitter site via a dedicated wireless network.

[0046] Class F devices are wireless IoT devices. These are transmitters with a specific wireless IoT communication solution, including a mobile terminal and toolkit. Each device has a specific wireless Internet module and communicates with a wireless gateway device (Class E device) using a dedicated communication protocol.

[0047] For Class G equipment, manual data entry is required. This includes uploaded documents (equipment images, manuals, maintenance manuals, videos), manually reported inspection data, and basic information data, including equipment identification, equipment name, specifications, installation location, manufacturer, technical parameters, and spare parts.

[0048] Secondly, in data transmission, proceed as follows:

[0049] Class A signal direct-connect devices can achieve analog sampling at 1 kSPS, generating 16-bit sampled data. Dedicated arrays are used to temporarily store and upload data with a specific depth. Digital input can reach 200 kSPS, generating Boolean data. Sixteen digital input variables are combined to generate a single 16-bit sampled data for upload.

[0050] Class B1 and Class E devices transmit data using the ModBus TCP protocol. Class B1 and Class E devices act as the communication master (Master mode), and the cabinet modules act as slaves (Slave mode).

[0051] Class B2 devices connect to the control cabinet via Ethernet. The control cabinet broadcasts commands every 100ms over the Ethernet link. Upon receiving the commands, the Class B2 device parses and synchronizes the timing, then organizes the data frames for return transmission. The control cabinet then completes the relevant calculations within the control cycle.

[0052] Class D devices transmit data directly to the remote server via Ethernet, and the data frames uploaded by the device are parsed by corresponding decoding software on the server side.

[0053] Class F devices transmit the data to be uploaded to the wireless gateway Class E via the front-end wireless Internet communication method. The command is sent from the Class E device at a fixed time, and the Class F device receives and analyzes it and uploads the reply.

[0054] Class G devices can be divided into structured data and unstructured data, which are directly transmitted to the remote server via Ethernet.

[0055] The system network layer supports the IP protocol, the transport layer supports the TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) protocols, and the audio and video streams support the RTP (Real-time Transport Protocol) / RTCP (RTP Control Protocol) protocols when transmitted on an IP-based network.

[0056] The address configuration module sets a one-to-one correspondence between different addresses within the IP network segment and the collection devices in the multi-protocol collection module. When multiple protocol collection devices are operating simultaneously, the system first identifies and categorizes the different types of collection devices, establishing a unified data encoding system and forming a complete system data encoding. A unique device code is automatically assigned to each type of collection device. Each device code then has a corresponding data code, completing the collection of three types of data.

[0057] Data encoding is determined by the encoding length and is expressed in three sections:

[0058] The first section is a management domain, indicating the ownership and geographical location of the space launch site; the second section is a process flow domain, indicating process flow classification information; and the third section is an equipment component domain, indicating information and measuring points of each specific equipment and component. The two parts are combined to form a unique and regular code.

[0059] (1) Management domain:

[0060]

[0061] X: superior agency code, YY: city code, Z: work station code

[0062] (2) Process flow domain:

[0063]

[0064] UU: process flow domain, including platform system, filling system, gas supply system, air conditioning system, fire fighting system, launch pad system, swing rod system, elevator system, power distribution system, and communication system; V: launch site partition area; WW: space area code in the partition area.

[0065] (3) Equipment component domain:

[0066] SS: equipment type code, including sensor, video, and file type; PP: equipment collection name, including temperature transmitter, pressure transmitter, regulating valve, on-off valve, speed regulating pump, constant speed pump, power distribution cabinet, liquid level meter, camera, optical fiber sensor, and manual input; and TT: component number, indicating multiple data collection equipment.

[0067] The data collection equipment is coded, and the data code is configured with an address, and the data code is identified to clearly indicate the unique number address of the equipment, such as 192.168.1.10. After the data code is used to standardize the equipment operation parameter data, the data is transmitted to the data preprocessing module through Ethernet.

[0068] In another embodiment of the present application, the data preprocessing module loads data into a data buffer area, and the data is converted and cleaned through connection, merging, and segmentation. The data in the data buffer area and the data storage area is processed and summarized according to the cleaning rules, and finally loaded into the data storage area. The data loading provides data for the target system according to the data interface requirements.

[0069] We resolve various data production failures, including insufficient computing resources, insufficient storage resources, data defects, incorrect data content, and uneven data distribution, and complete data re-entry and cleansing. We also provide data backup, duplicate checking, and recovery to maintain data stability and consistency, achieving data standardization and centralization.

[0070] Through software redundancy and data caching, production process information is protected from interruptions or loss due to communication failures or local system outages. After a data interruption, the data re-entry function provides the system with local cache storage, loading the data into the data buffer and timestamping it. Once communication is restored, data is traversed across all cached areas, verified against the missing time on the server, and ultimately transferred from the cache to the real-time historical database.

[0071] In another embodiment of the present invention, after data is lost and cannot be retrieved, the system uses historical data and contemporaneous data to perform prediction and supplementation, and annotates the data. The prediction and supplementation includes substitution and model supplementation, and may also be other prediction and supplementation methods.

[0072] The replacement and supplementation, when the data collected before and after the missing data are stable data, is judged by the lost data collected before and after. In a preferred embodiment, the data is supplemented by comparing the data of the previous day and the next day. If there is still a missing data, the data of the previous day and the next day are continued to be supplemented until the data is fully supplemented. After the supplementation, the data will be marked and recorded as the predicted data; when the missing data has a strong trend, the trend change of the historical data is fitted by the historical data sample, and several historical data points with the most similar data near the missing point are found and supplemented. After the supplementation, the data will be marked and recorded as the predicted data; in another embodiment, the average value of all values ​​on the attribute where the missing data is located or a certain percentile value can be used as a substitute; in another embodiment, for time series, the value or average value of adjacent data records is used to replace the missing data.

[0073] Preferably, for model supplementation, such as for time series, interpolation methods can be used to fill missing data using values ​​from "similar" records to the missing data, including but not limited to linear and nonlinear interpolation. Alternatively, a model can be constructed based on non-missing data, and parameters estimated, and then the missing data can be predicted.

[0074] In another embodiment of the present invention, the data preprocessing module also cleans the data. When data inconsistencies, errors, or conflicts are detected, the raw data is cleaned through redundancy elimination and anomaly detection. If data contains special characters, such as spaces, #, and @, the data is automatically identified and verified for consistency with historical data, and these characters are removed before being stored in the real-time historical database.

[0075] The data preprocessing module can mainly process space launch data in the following ways:

[0076] Data filtering: Filter business data that does not comply with application rules or is invalid to unify data standards.

[0077] Data conversion: convert data formats, information codes, and value conflicts.

[0078] Data loading: The main operations are insert and modify operations, which insert pre-processed clean data and invalid data into different data tables respectively.

[0079] Data cleaning rules: Data cleaning rules include non-empty check, primary key duplication, illegal code cleaning, illegal value cleaning, data format check, and record number check. The non-empty check: when a field is non-empty, the field data is checked; the primary key duplication: after the same type of data in multiple business systems is cleaned, the primary key uniqueness is guaranteed when it is saved in a unified manner, and the check is performed; the illegal code and illegal value cleaning: abnormal information appears in individual fields, including illegal codes, inconsistent codes with data standards, etc. Abnormal information appears in individual fields, including incorrect values, incorrect formats, extra characters, garbled codes, etc.; the data format check: the accuracy is measured by checking the correct format of the attribute values ​​in the table, such as time format, currency format, extra characters, garbled codes; the record number check: the total number of data between the related data of each system or the fluctuation of the daily data volume in the data table.

[0080] Invalid data processing: Missing values ​​cause data records to lose some information. Some models with poor robustness may also be unable to calculate data due to missing data. In this case, discard and estimate methods are used.

[0081] In another embodiment of the present invention, by marking the data in the real-time historical database storage module with a time tag and using a lossless compression algorithm, the collected data is classified according to time series storage and distributed file storage. The time series data with time tags is the basis for real-time data analysis at the launch site.

[0082] The time series storage is performed by marking the real-time database and sensor data with time tags to form time series data within the entire launch field and store them.

[0083] The distributed file storage: through streaming data access, the video data, picture data and file data collected by the camera and manually input are stored.

[0084] Each launch site system, such as refueling, fire protection, power distribution, elevators, and air conditioning, is stored as a separate dataset based on specific themes. An information directory is provided to store and update data, allowing users to access and understand the data. The directory comprehensively describes the data in the database, how it was obtained, and how to access it.

[0085] The real-time historical database storage module provides an interface for the upper layer and provides management and configuration functions for the lower layer, and is responsible for resource management and scheduling. Data maintenance and management are performed through the real-time historical database storage module, including security and privilege management, tracking data updates, data quality checks, managing and updating metadata, auditing and reporting data usage and status, deleting and copying data, segmenting and distributing data, backup and recovery, and storage management. The real-time historical database storage module primarily includes the following functions:

[0086] Interacts with clients and processes requests from them, such as querying application status and requesting and receiving resources through RPC (Remote Procedure Call) in a polling manner.

[0087] Start and manage each application, and restart the application if it fails to start or run;

[0088] Receive resource and node health status reports from the platform, such as lifecycle, heartbeat processing, and blacklist response processing, and issue resource management commands;

[0089] Resource management and scheduling: receiving resource requests from the system and allocating resources to them.

[0090] In one embodiment of the present invention, taking the filling system process as an example, a filling system information directory is created in the real-time historical database. The switching quantity and valve opening information of the pneumatic ball valve and manual valve on the tower are stored in the time series library; pressure sensors are installed at the filling ports of the fixed platforms at all levels and the liquid pipelines of the rotary platform to monitor the pipeline pressure of each important part, and the pressure information is stored in the time series library; cameras are installed in the closed areas at all levels to monitor the status of the filling valves and overflow valves at all levels in real time, and the video information is stored in the distributed file library; the temperature and pressure data of the storage tank are stored in the time series library. When each process node needs to monitor data, the real-time historical database will distribute the data and communicate it to each monitoring module for display.

[0091] The process breakpoint monitoring module serves as a redundant backup, ensuring normal launch site control when not in use. It is a comprehensive management and control unit that automatically starts and shuts down launch site operations throughout the entire process. Based on intelligent automatic start-stop control, the process breakpoint monitoring module can be applied to start-stop management for systems such as fire protection, power distribution, refueling, gas supply, and boom arm. Based on equipment status, camera alerts, infrared monitoring, image recognition, and manual confirmation, it customizes test launch processes, equipment start-stop, and real-time data display. Specific failure modes and alarms for key equipment are embedded. When problems are detected, feedback is immediately provided to the engineering station for manual breakpoint confirmation, ensuring mission safety and efficiency. It intelligently responds to various launch mission requirements, enabling real-time status monitoring of the launch site during launch operations, predicting and automatically isolating faults to ensure normal system operation. It enables intelligent operation of all systems throughout the entire process, including transfer, refueling, testing, launch, and emergency response, enabling unmanned operation at the launch site.

[0092] In one embodiment of the present invention, a method for online acquisition and monitoring of space launch data supporting multiple protocols is provided. The method employs the above-mentioned system to perform online acquisition and monitoring of space launch data, including the following steps:

[0093] Data acquisition is performed through the sensor acquisition module, video acquisition module, and file acquisition module;

[0094] The address configuration module sets the IP address to correspond to the acquisition devices in the sensor acquisition module, video acquisition module and file acquisition module one by one, and performs data coding identification;

[0095] After receiving the data, the data preprocessing module performs data verification, completes data re-entry and data cleaning;

[0096] The real-time history database storage module stores the data processed by the data pre-processing module;

[0097] The process breakpoint monitoring module calls the data in the real-time historical database storage module, and generates a flow chart through monitoring mode, sequential control mode, and breakpoint mode according to the operating logic of the acquisition device and the module where the acquisition device is located. By monitoring the process breakpoints and issuing alarms, the entire launch site process can be automatically started and stopped.

[0098] The online data collection and monitoring method provided by the embodiment of the present invention is applied to data collection and monitoring of space launches. It can realize real-time data collection and monitoring of various control systems and monitoring systems of space launches, solve the problems of heterogeneous data collection, fusion, storage, processing, calculation and monitoring, and is conducive to overall data analysis and early warning of the mission, realizing automatic start and stop of the entire launch site, providing data support for the subsequent intelligent unmanned operation of the entire launch site, and ensuring the safe and reliable completion of the mission.

[0099] In another embodiment of the present invention, a hierarchical control structure is adopted for the refueling system, and the refueling process is decomposed into several local independent processes. According to the unique characteristics of the launch site, the design is based on the equipment level, single system level, and full process level. Figure 3 The process breakpoint monitoring includes the following steps:

[0100] Step 1: Divide the overall structure into device level, single system level, and full process level hierarchical architecture;

[0101] Step 2: According to the seven single systems of conventional filling, liquid oxygen filling, liquid nitrogen filling, liquid hydrogen filling, liquid oxygen replenishment, liquid hydrogen replenishment, and pre-fire replenishment as each independent breakpoint, the sequence is automatically controlled;

[0102] Step 3: The whole process level coordinates the single system level and the device level to control the entire system. When a device in the currently executing single system fails and the execution of the unit times out, process control is executed, including operation management logic, sequence control logic, and breakpoint instruction logic.

[0103] Step 4: Automatically adjust the equipment and parameters;

[0104] Step 5: After the system recovers, the process will continue automatically. If it does not recover, an alarm will be issued for manual confirmation.

[0105] Step 6: After manually troubleshooting, the system continues with steps 2 to 4 until the task flow is completed.

[0106] Relatively independent start and stop phases are achieved by device-level control devices. In one embodiment of the present invention, taking the filling system as an example, the storage tank, storage tank, filling pump, valve, pipeline, etc. are independent devices. Alarm values ​​are set for the devices, and the monitoring mode is used to classify and control each system according to the start or stop requirements of the equipment. Automatic start and stop control is performed according to the operating process, which is divided into start sequence control and stop sequence control. It can automatically complete the start and stop under different working conditions. If the alarm value is reached during operation, an alarm will be issued and the parameters will be automatically adjusted at the same time. If it still does not recover, the personnel will be notified. The important indicators of the equipment are as follows:

[0107] Storage tanks: liquid level information, filling gas pressure and temperature, fuel tank internal pressure and temperature, fuel filling error, etc.

[0108] Valve / Pipeline: Valve feedback information, pipeline pressure information, propellant flow information, propellant flow rate information, pump front pressure information, etc.

[0109] Filling pump: pump inlet and outlet pressure information, pump flow information, pump inlet and outlet temperature information, pump current information, bearing vibration, etc.

[0110] The single system level connects the equipment levels to achieve single-system startup and shutdown, as well as automatic control. The independent equipment is divided into regular filling, liquid oxygen filling, liquid nitrogen filling, liquid hydrogen filling, liquid oxygen supplementation, liquid hydrogen supplementation, and pre-launch supplementation stages according to the filling process. Each stage treats all equipment as a whole, with corresponding alarm values ​​and start / stop values, enabling full-process automatic adjustment and scheduling of each device and system. Based on the sequential automatic control at the equipment level, the control strategy performs judgments and calculations based on the needs and characteristics of the filling process, according to predetermined sequence, timing, and logical conditions, ultimately issuing instructions to control the equipment to complete the sequential control actions. The single system can accurately determine the current system operating conditions, such as using infrared cameras to monitor the temperature in the pipeline in real time. It then determines whether to continue operation based on the equipment and parameters of the preceding and following processes of the faulty equipment. Hierarchical parameters are set, such that if the required shutdown value is reached, the system automatically shuts down the equipment to ensure the safety of the entire system. By automatically engaging automatic control under specific conditions, each device can seamlessly connect to achieve full control of the single system.

[0111] Ultimately, the full-process level coordinates control of the entire system at the individual system and equipment levels to achieve comprehensive start-stop control of launch site refueling. The seven individual systems are considered independent breakpoints. Sequential control within these breakpoints features interrupt and resume functionality, automatically selecting execution based on the equipment's operational status. If a device failure occurs within the currently executing unit and the execution of that unit times out, the individual system automatically interrupts that unit and issues an alarm to alert operators, preventing further, ineffective operations. If the work at the previous breakpoint is incomplete and all work at the current breakpoint is completed, the work required by the first unfinished breakpoint will be initiated first. Only after all work is completed can the next breakpoint be entered.

[0112] This full-process control system structure is clear and rigorous, which helps improve the efficiency of design, configuration, and commissioning. Furthermore, the independence of each level of hierarchical control allows for great flexibility, facilitating operational management and maintenance. Operators can choose from a variety of control methods based on specific circumstances.

[0113] Breakpoints are implemented by designing different automatic start-stop operation modes, such as monitoring mode, sequential control mode, and breakpoint mode, along with their switching management logic. This design also incorporates a combination of soft and hard breakpoints, serial and parallel branches, with variable constraints and flexible control structures. This, along with various dynamic pre-judgment and early warning conditions, enhances the practicality and applicability of the entire space launch automatic start-stop control function and simplifies the functionality and operational interface of the automatic start-stop control system. In one embodiment of the present invention, the breakpoint function can be implemented using three different logics at the device level, single system level, and full process level: operation management logic, sequential control logic, and breakpoint instruction logic.

[0114] The first layer is the operation management logic, which is responsible for selecting and determining whether the device is in operation, whether to start or stop it, which breakpoint to select, and whether the conditions for allowing the breakpoint to proceed are met. If the conditions are met, a signal is generated to initiate the breakpoint. If the last breakpoint is reached, the generated instruction determines whether the previous breakpoint has been completed. If not, the work required by the first unfinished breakpoint is initiated first. This allows for the selection of breakpoints, thereby enabling the initiation of the next action. The breakpoint operation logic design includes input and output signals. Input signals include: automatic start, operation permission conditions, breakpoint execution start, breakpoint execution completion, and breakpoint continue / wait. Output signals include: breakpoint execution interrupt alarm, breakpoint execution allowed, breakpoint execution in progress, breakpoint execution start, and breakpoint execution completion.

[0115] The second layer is the sequential control logic. Each breakpoint has a roughly identical sequential control program structured in a similar way. This program structure consists of enabling condition determination, reset condition generation, and sequential control timing. When a breakpoint start command is issued and there is no end signal for that breakpoint, sequential control begins. Each control step verifies whether the conditions are met, and the previous action is reset when the current control begins. If the sequential control timeout occurs, an alarm is issued indicating that the breakpoint is abnormal.

[0116] The third layer is the breakpoint command logic. For example, during routine fuel and oxidizer refueling, if equipment parameters exceed standards, flow rate anomalies occur, pipeline leaks occur, or personnel are stranded, a breakpoint confirmation is initiated. Commands are sent to each sequential control system group to start or stop each device. After each device starts or stops, a completion signal is returned. The system automatically recovers or manually confirms the alarm is cleared before continuing and proceeding to the next step.

[0117] The process breakpoint monitoring was converted into control logic and put into configuration simulation deduction. After a period of operation verification, the expected goals were achieved, providing data support for subsequent intelligent unattended operation and ensuring the safe and reliable completion of the task.

[0118] Multi-protocol acquisition can collect more data as a basis for analysis, address configuration and data preprocessing can better understand the data, the real-time historical database can be used as a data warehouse for data storage and distribution, and the process breakpoint monitoring can make some predictive judgments based on the results of visual analysis and data mining, conduct internal process deduction, analyze and judge the severity of failure modes, and build a process breakpoint monitoring and evaluation model.

[0119] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A space launch data online acquisition and monitoring system supporting multiple protocols, characterized by: It includes multi-protocol acquisition module, address configuration module, data pre-processing module, real-time history library storage module, and process breakpoint monitoring module, among which: The multi-protocol acquisition module includes a sensor acquisition module, a video acquisition module, and a file acquisition module; The address configuration module sets different addresses in the IP network segment, and the IP addresses correspond to the collection devices in the multi-protocol collection module one by one to perform data coding identification; The data preprocessing module is responsible for performing data verification on the data collected by the multi-protocol acquisition module, completing data re-recording and data cleaning; The real-time history library storage module forms full-range time series data by marking the data with time tags, and stores the data processed by the data preprocessing module; The process breakpoint monitoring module calls real-time historical database data, configures and generates a flow chart based on the operating logic of the online space launch data acquisition and monitoring system of the acquisition equipment and the space launch data it is located in, through monitoring mode, sequential control mode, and breakpoint mode, and realizes automatic start and stop of the entire launch site process by monitoring and alarming process breakpoints.

2. The online acquisition and monitoring system according to claim 1, characterized in that: The sensor acquisition module realizes interconnection communication by adapting various sensors including fiber Bragg grating, acceleration, velocity, displacement, pressure, temperature, and humidity. It is connected to the Ethernet through the Ethernet interface and then to the host computer through the switch to form an open network system.

3. The online acquisition and monitoring system according to claim 2, characterized in that: The video acquisition module establishes and controls media sessions at both ends of the communication through the RTSP protocol, and the client controls the media stream in real time by issuing commands.

4. The online acquisition and monitoring system according to claim 3, characterized in that: The file acquisition module transmits encrypted data from the database through HTTPS, FTPS or SFTP protocols, and establishes respective transmission channel ports for acquisition and transmission.

5. The online acquisition and monitoring system according to claim 1, characterized in that: The data supplementation includes: providing local cache storage after data interruption, and then continuing to transmit the data stored in the local cache to the real-time historical database after communication is restored; when data is lost, data prediction and supplementation are carried out through historical data and contemporaneous data, and annotation is performed.

6. The online acquisition and monitoring system according to claim 5, characterized in that: The data cleaning is to clean the original data through redundancy elimination, anomaly detection or normalization methods when data inconsistency, data error, data conflict or data duplication is detected.

7. The online acquisition and monitoring system according to claim 1, characterized in that: The data storage includes: Time series storage: By adding time tags to the real-time database and sensor data, time series data within the entire launch site is formed and stored; Distributed file storage: Through streaming data access, video data, image data, and file data collected by cameras or manually input are stored; Database management: By establishing an information directory, it provides fast retrieval and query of data, provides an interface upward, and provides management and configuration functions downward, and is responsible for resource management and scheduling.

8. A method for online acquisition and monitoring of space launch data supporting multiple protocols, characterized in that: The system according to any one of claims 1 to 7 is used to perform online acquisition and monitoring of space launch data, comprising the following steps: Data acquisition is performed through the sensor acquisition module, video acquisition module, and file acquisition module; The address configuration module sets the IP address to correspond to the acquisition devices in the sensor acquisition module, video acquisition module and file acquisition module one by one, and performs data coding identification; After receiving the data, the data preprocessing module performs data verification, completes data re-entry and data cleaning; The real-time history library storage module stores the data processed by the data pre-processing module; The process breakpoint monitoring module calls the data in the real-time history library storage module, and according to the operating logic of the acquisition device and the module where the acquisition device is located, configures and generates a flow chart through monitoring mode, sequential control mode, and breakpoint mode. By monitoring and alarming the process breakpoints, the entire launch site process can be automatically started and stopped.

9. The online acquisition and monitoring method according to claim 8, characterized in that: In the filling system, the process breakpoint monitoring includes the following steps: Step 1: Divide the overall structure into device level, single system level, and full process level hierarchical architecture; Step 2: Set the seven single systems of conventional filling, liquid oxygen filling, liquid nitrogen filling, liquid hydrogen filling, liquid oxygen replenishment, liquid hydrogen replenishment, and pre-fire replenishment as independent breakpoints and automatically control them in sequence; Step 3: The whole process level coordinates the single system level and the device level to control the entire system. If a device in the currently executing single system fails and the execution of the single system times out, process control is executed, including operation management logic, sequence control logic, and breakpoint instruction logic. Step 4: Automatically adjust the equipment and parameters; Step 5: After the system recovers, the process will continue automatically. If it does not recover, an alarm will be issued for manual confirmation. Step 6: After manually troubleshooting, the system continues with steps 2 to 4 until the task flow is complete.

Images