Controller redundancy method and system for launcher

By designing a redundant control subsystem in the rocket launcher control system, data synchronization and failover between the first and second control subsystems are achieved, the system paralysis problem caused by the failure of the main controller is solved, and the reliability of the system is improved and stability reduce maintenance costs.

CN118963214APending Publication Date: 2024-11-15BEIJING ZHONGKE AEROSPACE TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411048210.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The main controller of the rocket launcher is prone to failure due to complex environments and emergencies, causing the entire launch control system to be paralyzed, affecting production efficiency and safety, and lacking effective fault tolerance capabilities.

Method used

Design a redundant control system to realize data synchronization and failover through the CAN bus connection between the first control subsystem and the second control subsystem, and automatically switch to the second control subsystem when the first control subsystem fails , ensure the stable operation of the system.

Benefits of technology

It improves the reliability and stability of the transmission control system, avoids overall failure caused by single point failure, ensures the continuity and safety of the production line, reduces maintenance costs, and enhances the fault tolerance of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118963214A_ABST
    Figure CN118963214A_ABST
Patent Text Reader

Abstract

The invention discloses a controller redundancy method and system for a launcher, and relates to the technical field of space.The controller redundancy system for the launcher comprises a first control subsystem and a second control subsystem; wherein the first control subsystem and the second control subsystem are both connected with the CAN bus; the first control subsystem and the second control subsystem are both connected with the launching rack; the first control subsystem is connected with the second control subsystem; in the working process, data are sent to the first control subsystem and / or the second control subsystem through the CAN bus; the launcher is controlled through the first control subsystem, and if the first sub-control system breaks down, the second control subsystem is used for controlling the launcher. The reliability and the stability of the launching control system can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of aerospace technology, and in particular to a controller redundancy method and system for a launch pad. Background Art

[0002] As an important part of space launch, the stability and safety of the rocket launcher are directly related to the success or failure of the space mission. During the rocket launch process, the rocket launcher not only has to withstand huge weight and vibration, but also has to face complex external environments and various emergencies.

[0003] In a complex industrial environment, various factors may cause the main controller of a rocket launcher to fail. However, the existing launch control system usually has only one main controller (i.e., no redundant controller), and its fault tolerance is low. Once the main controller of a rocket launcher fails, the entire launch control system will be paralyzed, resulting in production interruptions and even safety accidents. Therefore, it is necessary to shut down for maintenance, which not only affects production efficiency, but also increases maintenance costs and time costs. The risk of this single point of failure will greatly affect the normal operation and production benefits of the enterprise.

[0004] Therefore, control redundancy is particularly important in the design of rocket launchers. Summary of the invention

[0005] The purpose of the present application is to provide a controller redundancy method and system for a launch pad, which can improve the reliability and stability of the launch control system.

[0006] To achieve the above-mentioned purpose, the present application provides a controller redundancy system for a launcher, comprising: a first control subsystem and a second control subsystem; wherein, the first control subsystem and the second control subsystem are both connected to a CAN bus; the first control subsystem and the second control subsystem are both connected to the launcher; the first control subsystem is connected to the second control subsystem; when working, data is sent to the first control subsystem and / or the second control subsystem via the CAN bus; the launcher is controlled by the first control subsystem, and if the first subcontrol system fails, the launcher is replaced by the second control subsystem.

[0007] As above, wherein the first control subsystem at least includes: a first controller, a first interface module, a first power supply, a first reset module, a first clock and a second clock; the second control subsystem at least includes: a second controller, a second interface module, a second power supply, a second reset module, a third clock and a fourth clock; wherein the first controller is connected to the first interface module, the first power supply, the first reset module and the first clock; the first interface module is connected to the first power supply, the first reset module, the second clock and the CAN bus; the second controller is connected to the second interface module, the second power supply, the second reset module, the third clock and the first controller; the second interface module is connected to the second power supply, the second reset module, the fourth clock, the CAN bus and the first interface module; wherein the first controller: is used to send launcher control instructions and receive launcher status data ; The first interface module: is used to receive the data sent by the CAN bus and send the data to the first controller; the first power supply: is used to supply power to the first controller and the first interface module; the first reset module: is used to reset the first controller and the first interface module; the first clock: is used to provide the clock frequency for the first controller; the second clock: is used to provide the clock frequency for the first interface module; the second controller: is used to send the launcher control instructions and receive the launcher status data; the second interface module: is used to receive the data sent by the CAN bus and send the data to the second controller; the second power supply: is used to supply power to the second controller and the second interface module; the second reset module: is used to reset the second controller and the second interface module; the third clock: is used to provide the clock frequency for the second controller; the fourth clock: is used to provide the clock frequency for the second interface module.

[0008] As above, wherein the first controller at least includes: a first serial port, a second serial port, a third serial port and a status IO pin; the second controller at least includes: a first serial port, a second serial port, a third serial port and a status IO pin; wherein the first serial port of the first controller is connected to the first serial port of the second controller, and the first controller and the second controller synchronize data through the first serial port; the second serial port of the first controller is connected to the second serial port of the second controller, and the first controller and the second controller communicate through the second serial port and transmit communication data, wherein the communication data at least includes: data received from the CAN bus, and the data received from the CAN bus at least includes: launcher status data, launcher action operation data and heartbeat information; the third serial port and status IO pin of the first controller are both connected to the first interface module; the third serial port and status IO pin of the second controller are both connected to the second interface module.

[0009] As above, while the second serial port of the first controller sends heartbeat information to the second serial port of the second controller, the second serial port of the second controller also sends heartbeat information to the second serial port of the first controller.

[0010] As above, wherein the first interface module at least includes: a first serial port, a status IO pin, a second serial port, a CAN controller and an IO pin; the second interface module at least includes: a first serial port, a status IO pin, a second serial port, a CAN controller and an IO pin; wherein the first serial port of the first interface module communicates with the third serial port of the first controller; the status IO pin of the first interface module is connected to the status IO pin of the first controller; the CAN controller of the first interface module is connected to the CAN bus; the first serial port of the second interface module communicates with the third serial port of the second controller; the status IO pin of the second interface module is connected to the status IO pin of the second controller; the CAN controller of the second interface module is connected to the CAN bus; the IO pin of the second interface module is connected to the IO pin of the first interface module; the second serial port of the second interface module is connected to the second serial port of the first interface module.

[0011] As above, the status IO pin of the first interface module is used to determine whether the first interface module receives data successfully; when the first controller sends data and the first interface module receives data, the status IO pin of the first interface module is set to a high position, and the status IO pin of the first controller collects the IO pin status of the status IO pin of the first interface module. If the IO pin status is collected, it indicates that the current communication between the first controller and the first interface module is normal; if the IO pin status is not collected, it indicates that the current communication between the first controller and the first interface module is faulty.

[0012] As above, the status IO pin of the second interface module is used to determine whether the second interface module receives data successfully; when the second controller sends data and the second interface module receives data, the status IO pin of the second interface module is set to a high position, and the status IO pin of the second controller collects the IO pin status of the status IO pin of the second interface module. If the IO pin status is collected, it indicates that the communication between the second controller and the second interface module is normal; if the IO pin status is not collected, it indicates that the communication between the second controller and the second interface module is faulty.

[0013] As above, wherein the first control subsystem or the second control subsystem: is used to control the opening / closing of the upper clamp, the opening / closing of the lower clamp, the upward / downward movement of the load-balancing support, and the opening / closing of the unrepaired insulation device of the launch pad; is used to monitor the horizontality of the launch pad; is used to control the movement of the launch pad, wherein the movement of the launch pad at least includes: erecting and leveling.

[0014] The present application also provides a controller redundancy method for a launcher, which is applied to the above-mentioned controller redundancy system for a launcher, and the method includes the following steps: S1: performing system initialization settings on the first control subsystem and the second control subsystem, and determining that the first controller of the first control subsystem is the master controller and the second controller of the second control subsystem is the slave controller; wherein the system initialization settings at least include: controller initialization and interface initialization; wherein the controller initialization at least includes: controller serial port settings, controller clock configuration and external interrupt initialization; interface initialization at least includes: interface clock configuration, interface serial port configuration and CAN communication initialization; system initialization settings also include: control words and status words; S2: after completing the initialization settings, the master controller and the slave controller perform synchronous negotiation to eliminate the power-on time difference between the master controller and the slave controller, and when the preset conditions are met, the slave controller sends heartbeat information to the master controller, and the master controller also sends heartbeat information to the slave controller; if the master controller and / or the slave controller do not receive the heartbeat information sent by the slave controller and / or the master controller when the preset conditions are met, then The master controller and / or slave controller perform fault diagnosis processing; if both the master controller and the slave controller receive heartbeat information when the preset conditions are met, execute S3; S3: inquire the first interface module and the second interface module, if it is determined according to the inquiry that the first interface module and the second interface module are both in normal working state, the CAN bus sends data to the first interface module and the second interface module at the same time; S4: the master controller backs up the data, extracts the system status, backs up the status word and the control word, thereby obtaining the backup data, and performs CRC check on the backup data to obtain the first CRC check code; the slave controller backs up the data, extracts the system status, backs up the status word and the control word, thereby obtaining the backup data, and performs CRC check on the backup data to obtain the second CRC check code; compare the first CRC check code with the second CRC check code, if the first CRC check code is consistent with the second CRC check code, then the verification data is correct, and enter the controller logic processing program; if the first CRC check code is inconsistent with the second CRC check code, then the verification data is incorrect, then the master controller and the slave controller perform fault diagnosis processing.

[0015] As mentioned above, the fault diagnosis process at least includes: master controller and / or slave controller fault processing, hardware fault processing and interface module fault processing.

[0016] The beneficial effects achieved by this application are as follows:

[0017] (1) The controller redundancy method and system for a launcher of the present application can improve the reliability and stability of the launch control system.

[0018] (2) The controller redundancy method and system for the launcher of the present application sets up multiple backup or alternative solutions in the key control system to ensure that when a problem occurs in a certain control link, it can quickly switch to other control paths, thereby ensuring the stable operation of the entire system.

[0019] (3) The controller redundancy method and system for the launcher of the present application can automatically switch from the main controller to the slave controller through redundant design, which can avoid overall failure caused by single point failure and ensure the continuity and safety of the production line.

[0020] (4) The controller redundancy method for the launcher and the controller redundancy of the system (i.e., the first control subsystem and the second control subsystem) of the present application can be repaired and / or replaced online without interrupting the mission execution, which greatly reduces the maintenance cost and improves the production efficiency.

[0021] (5) The controller redundancy method and system for the launch pad of the present application enhance the system's fault tolerance and risk resistance. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0023] Figure 1 A schematic diagram of the structure of an embodiment of a controller redundancy system for a launcher;

[0024] Figure 2 A flowchart of an embodiment of a controller redundancy method for a launcher;

[0025] Figure 3 A schematic diagram of an embodiment of a control word or a status word. DETAILED DESCRIPTION

[0026] The following is a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0027] like Figure 1As shown, the present application provides a controller redundancy system for a launcher, comprising: a first control subsystem and a second control subsystem; wherein, the first control subsystem and the second control subsystem are both connected to a CAN bus (Controller Area Network); the first control subsystem and the second control subsystem are both connected to the launcher; the first control subsystem is connected to the second control subsystem; when working, data is sent to the first control subsystem and / or the second control subsystem via the CAN bus; the launcher is controlled by the first control subsystem, and if the first subcontrol system fails, the launcher is replaced by the second control subsystem.

[0028] Specifically, the first control subsystem and the second control subsystem are hardware redundant.

[0029] The first control subsystem is used to control the opening / closing of the upper clamp of the launcher, the opening / closing of the lower clamp, the upward / downward movement of the load-balancing support, and the opening / closing of the final maintenance insulation device; it is used to monitor the horizontality of the launcher; it is used to control the movement of the launcher, wherein the movement of the launcher includes at least: erecting and leveling.

[0030] When the first sub-control system fails, the second control subsystem is used to control the opening / closing of the upper clamp of the launch rack, the opening / closing of the lower clamp, the upward / downward movement of the load-balancing support, and the opening / closing of the unrepaired insulation device; to monitor the horizontality of the launch rack; and to control the movement of the launch rack, wherein the movement of the launch rack includes at least: erecting and leveling.

[0031] Furthermore, the data sent via the CAN bus includes at least: launcher status data, launcher action operation data and heartbeat information.

[0032] Among them, the launch pad status data at least includes: the upper clamp open / closed status, the lower clamp open / closed status, the launch platform support plate retracted / extended status, the final maintenance and insulation in place / retracted status and the equalizing support in place / retracted status.

[0033] The launch pad action operation data includes at least: upper clamp opening / closing action, lower clamp opening / closing action, launch pad support plate retraction / extension action and final maintenance insulation in place / retraction action.

[0034] Furthermore, the first control subsystem at least includes: a first controller (ie: Figure 1 Controller 1 in), first interface module (ie: Figure 1 Interface module 1), first power supply (ie: Figure 1 The power supply 1), the first reset module (ie: Figure 1 Reset 1), the first clock (ie: Figure 1 Clock 1 in) and the second clock (ie: Figure 1 The second control subsystem at least includes: a second controller (ie: Figure 1 Controller 2 in), the second interface module (ie: Figure 1 Interface module 2 in), second power supply (ie: Figure 1 Power supply 2), the second reset module (ie: Figure 1 Reset 2), the third clock (ie: Figure 1 Clock 3) and the fourth clock (ie: Figure 1 The first controller is connected to the first interface module, the first power supply, the first reset module and the first clock. The first interface module is connected to the first power supply, the first reset module, the second clock and the CAN bus. The second controller is connected to the second interface module, the second power supply, the second reset module, the third clock and the first controller. The second interface module is connected to the second power supply, the second reset module, the fourth clock, the CAN bus and the first interface module.

[0035] Wherein, the first controller is used to send launcher control instructions and receive launcher status data.

[0036] Specifically, the control logic of the first controller is: controlling the launcher action according to the launcher state.

[0037] The first interface module is used to receive data sent by the CAN bus and send the data to the first controller.

[0038] Specifically, the data is sent to the first controller through the first serial port of the first interface module.

[0039] The first power supply is used to supply power to the first controller and the first interface module.

[0040] The first reset module is used to reset the first controller and the first interface module.

[0041] First clock: used to provide a clock frequency for the first controller.

[0042] Second clock: used to provide clock frequency for the first interface module.

[0043] Second controller: used to send launcher control instructions and receive launcher status data.

[0044] Specifically, the control logic of the second controller is: controlling the launcher action according to the launcher state.

[0045] The second interface module is used to receive data sent by the CAN bus and send the data to the second controller.

[0046] Specifically, the data is sent to the second controller through the first serial port of the second interface module.

[0047] Second power supply: used to supply power to the second controller and the second interface module.

[0048] Second reset module: used to reset the second controller and the second interface module.

[0049] The third clock is used to provide a clock frequency for the second controller.

[0050] Fourth clock: used to provide a clock frequency for the second interface module.

[0051] Furthermore, the first controller at least includes: a first serial port (ie: Figure 1 Serial port 1 in controller 1), the second serial port (ie: Figure 1 Serial port 2 in controller 1), the third serial port (ie: Figure 1 The serial port 3 in the controller 1) and the status IO pin (ie: Figure 1 The state IO in the controller 1); the second controller at least includes: a first serial port (ie: Figure 1 Serial port 1 in controller 2), the second serial port (ie: Figure 1 Serial port 2 in controller 2), the third serial port (ie: Figure 1 The serial port 3 in the controller 2) and the status IO pin (ie: Figure 1 Status IO in controller 2).

[0052] The first serial port of the first controller is connected to the first serial port of the second controller, and the first controller and the second controller perform data synchronization via the first serial port.

[0053] The second serial port of the first controller is connected to the second serial port of the second controller. The first controller and the second controller communicate through the second serial port and transmit communication data, wherein the communication data at least includes: data received from the CAN bus, and the data received from the CAN bus at least includes: launcher status data, launcher action operation data and heartbeat information.

[0054] The third serial port and the status IO pin of the first controller are both connected to the first interface module.

[0055] The third serial port and the status IO pin of the second controller are both connected to the second interface module.

[0056] Furthermore, while the second serial port of the first controller sends heartbeat information to the second serial port of the second controller, the second serial port of the second controller also sends heartbeat information to the second serial port of the first controller, that is, the heartbeat information is sent by the first controller and the second controller to each other at the same time.

[0057] Furthermore, the first interface module at least includes: a first serial port (ie: Figure 1 Serial port 1 in interface module 1), status IO pin (ie: Figure 1 The status IO in the interface module 1), the second serial port (ie: Figure 1 The serial port 2 in the interface module 1), the CAN controller (ie: Figure 1 CAN controller in interface module 1) and IO pins (ie: Figure 1 IO in the interface module 1); the second interface module at least includes: a first serial port (ie: Figure 1 Serial port 1 in interface module 2), status IO pin (ie: Figure 1 The status IO in the interface module 2), the second serial port (ie: Figure 1 Serial port 2 in interface module 2), CAN controller (ie: Figure 1 CAN controller in interface module 2) and IO pins (ie: Figure 1 IO in interface module 2).

[0058] The first serial port of the first interface module communicates with the third serial port of the first controller; the status IO pin of the first interface module is connected with the status IO pin of the first controller; and the CAN controller of the first interface module is connected with the CAN bus.

[0059] The first serial port of the second interface module communicates with the third serial port of the second controller; the state IO pin of the second interface module is connected with the state IO pin of the second controller; and the CAN controller of the second interface module is connected with the CAN bus.

[0060] The IO pin of the second interface module is connected to the IO pin of the first interface module.

[0061] The second serial port of the second interface module is connected to the second serial port of the first interface module.

[0062] Among them, the first serial port of the first interface module is used to communicate with the third serial port of the first controller.

[0063] The status IO pin of the first interface module is used to determine whether the first interface module receives data successfully.

[0064] The second serial port of the first interface module is used to synchronize data with the second serial port of the second interface module.

[0065] The CAN controller of the first interface module is used to receive data sent by the CAN bus or send data to the CAN bus.

[0066] IO pin of the first interface module: used to determine whether the second interface module has completed receiving the data sent by the CAN bus.

[0067] Among them, the first serial port of the second interface module is used to communicate with the third serial port of the second controller.

[0068] The status IO pin of the second interface module is used to determine whether the second interface module receives data successfully.

[0069] The second serial port of the second interface module is used to synchronize data with the second serial port of the first interface module.

[0070] The CAN controller of the second interface module is used to receive data sent by the CAN bus or send data to the CAN bus.

[0071] IO pin of the second interface module: used to determine whether the first interface module has completed receiving the data sent by the CAN bus.

[0072] Furthermore, when the first controller sends data and the first interface module receives the data, the status IO pin of the first interface module is set to a high position, and the status IO pin of the first controller collects the IO pin status of the status IO pin of the first interface module. If the IO pin status is collected, it indicates that the current communication between the first controller and the first interface module is normal; if the IO pin status is not collected, it indicates that the current communication between the first controller and the first interface module is faulty.

[0073] Furthermore, when the second controller sends data and the second interface module receives the data, the status IO pin of the second interface module is set to a high position, and the status IO pin of the second controller collects the IO pin status of the status IO pin of the second interface module. If the IO pin status is collected, it indicates that the communication between the second controller and the second interface module is normal; if the IO pin status is not collected, it indicates that the communication between the second controller and the second interface module is faulty.

[0074] Specifically, state IO refers to state input / output, which is one or more pins on a hardware device or microcontroller (MCU) that can be configured as input or output state to read the state of an external signal or output a signal to an external device.

[0075] like Figure 2 As shown, the present application provides a controller redundancy method for a launcher, which is applied to the above-mentioned controller redundancy system for a launcher, and the method includes the following steps:

[0076] S1: Perform system initialization settings on the first control subsystem and the second control subsystem, and determine that the first controller of the first control subsystem is the master controller, and the second controller of the second control subsystem is the slave controller; wherein the system initialization settings at least include: controller initialization and interface initialization; wherein the controller initialization at least includes: controller serial port setting, controller clock configuration and external interrupt initialization; interface initialization at least includes: interface clock configuration, interface serial port configuration and CAN communication initialization.

[0077] Specifically, the controller initialization is to initialize the first controller and the second controller.

[0078] The controller serial port setting at least includes: setting the first serial port, the second serial port and the third serial port of the first controller, and the first serial port, the second serial port and the third serial port of the second controller.

[0079] Specifically, the specific settings of each controller serial port (i.e., the first serial port, the second serial port and the third serial port of the first controller, and the first serial port, the second serial port and the third serial port of the second controller) depend on the actual situation. The present application preferably sets each controller serial port to: baud rate 115200bps, 8 data bits, no parity bit, and one stop bit.

[0080] The controller clock configuration at least includes: configuring the first clock and the third clock, and synchronizing and regulating the operation rhythm of the first controller and the second controller through the first clock and the third clock.

[0081] Specifically, the controller clock configuration refers to initializing the first clock and the third clock to a uniform frequency.

[0082] The external interrupt is in the fault diagnosis and processing program. When the first controller or the second controller starts the fault diagnosis program, the second controller or the first controller is notified to start the fault diagnosis.

[0083] The fault diagnosis (ie, fault diagnosis processing) at least includes: master controller and / or slave controller fault processing, hardware fault processing, and interface module fault processing. The fault diagnosis is used to determine whether the first controller and / or the second controller is faulty.

[0084] The interface initialization is to initialize the first interface module and the second interface module.

[0085] The interface serial port configuration at least includes: setting the first serial port and the second serial port of the first interface module, and the first serial port and the second serial port of the second interface module.

[0086] Specifically, the specific settings of each interface serial port (i.e., the first serial port and the second serial port of the first interface module, and the first serial port and the second serial port of the second interface module) depend on the actual situation. The present application preferably sets each interface serial port to: baud rate 115200bps, 8 data bits, no parity bit, and one stop bit.

[0087] The interface clock configuration at least includes: configuring the second clock and the fourth clock, and synchronizing and regulating the operation rhythm of the first controller and the second controller through the second clock and the fourth clock.

[0088] Specifically, the interface clock configuration refers to initializing the second clock and the fourth clock to a uniform frequency.

[0089] Further, the first clock, the second clock, the third clock and the fourth clock are all initialized to a uniform frequency.

[0090] The CAN communication initialization at least includes: initializing the CAN controller of the first interface module and the CAN controller of the second interface module.

[0091] Specifically, CAN communication initialization is automatic initialization upon power-on.

[0092] Furthermore, the system initialization setting also includes: a control word and a status word, the control word is used to control the operation of the controller redundant system used for the launcher, and the status word is used to mark the operation status of the controller redundant system used for the launcher.

[0093] Specifically, the control word is the data sent to the CAN line, and the status word is the data received on the CAN line.

[0094] As an example, Figure 3 As shown, COB-ID is the device ID, which comes from different devices connected to the CAN bus. Data (Data) includes 8 bytes; among which, the first byte is: start flag, fixed to 0x80; the second byte is: command output address; the third byte is: command output address; the fourth byte is: action instruction; the fifth byte is: acquisition data (low bit); the sixth byte is: acquisition data (high bit); the seventh byte is: reserved; the eighth byte is: reserved. Timestamp represents the timestamp.

[0095] S2: After completing the initialization settings, the master controller and the slave controller perform synchronous negotiation to eliminate the power-on time difference between the master controller and the slave controller, and when the preset conditions are met, the slave controller sends a heartbeat message to the master controller, and the master controller also sends a heartbeat message to the slave controller; if the master controller and / or the slave controller do not receive the heartbeat message sent by the slave controller and / or the master controller when the preset conditions are met, the master controller and / or the slave controller are fault diagnosed; if both the master controller and the slave controller receive the heartbeat message when the preset conditions are met, S3 is executed.

[0096] Specifically, the heartbeat information is a message sent in a program to ensure that two controllers (i.e., the master controller and the slave controller) can run synchronously. The master controller and the slave controller monitor each other for failures by sending heartbeat information to each other, so as to ensure that the two controllers can run normally at the same time.

[0097] Furthermore, the preset condition is a preset time length. In order to ensure that the two controllers run synchronously, heartbeat information is sent within the preset time length. If the master-slave controller receives the heartbeat information within the preset time length, fault diagnosis processing will be performed.

[0098] Specifically, the specific value of the preset duration depends on the actual situation, and the present application preferably uses a duration of three cycles.

[0099] S3: Inquiring the first interface module and the second interface module. If it is determined according to the inquiry that the first interface module and the second interface module are both in normal working state, the CAN bus sends data to the first interface module and the second interface module at the same time.

[0100] Specifically, when the first interface module and the second interface module receive data on the bus, they first take the data out of the FIFO and release the FIFO. The main interface asks whether to send it to the backup interface to determine whether it is working properly. After receiving the inquiry, the backup interface needs to respond to the main interface. After confirming that both parties are normal, data is sent to the master and slave controllers at the same time. The purpose of sending an inquiry signal before sending data is to ensure that the master and slave controllers can run synchronously. If the data is sent to the controller for inquiry, there may be a failure in one of the controllers, resulting in the inability of the controllers to synchronize.

[0101] S4: The master controller backs up the data, extracts the system status, backs up the status word and the control word to obtain the backup data, and performs CRC check on the backup data to obtain the first CRC check code; the slave controller backs up the data, extracts the system status, backs up the status word and the control word to obtain the backup data, and performs CRC check on the backup data to obtain the second CRC check code; compares the first CRC check code with the second CRC check code, if the first CRC check code is consistent with the second CRC check code, then the verification data is correct, and enters the controller logic processing program; if the first CRC check code is inconsistent with the second CRC check code, then the verification data is incorrect, and fault diagnosis processing is performed on the master controller and the slave controller.

[0102] Specifically, during the data transmission process, due to external factors or internal failures, data transmission errors may occur. In order to ensure the correctness of data transmission, the CRC check bit is used to verify the correctness of the data.

[0103] Furthermore, the fault diagnosis process at least includes: master controller and / or slave controller fault processing, hardware fault processing and interface module fault processing.

[0104] Specifically, the judgment conditions for the failure of the master controller and / or the slave controller are: whether the master controller and the slave controller can receive notifications from each other, whether they can receive heartbeat information sent by each other and / or compare whether the received bus data is consistent (that is, whether the CRC check verifies that the data is correct).

[0105] The judgment conditions for hardware fault processing are: if communication fails, there may be a hardware fault problem. Excluding the normal serial port communication of the first controller and the normal serial port communication of the second controller, and the normal operation of the first interface module and the second interface module, it is judged to be a hardware problem.

[0106] The interface module fault processing at least includes: CAN controller fault or CAN transceiver fault. If the first interface module (i.e., the master interface module) fails, the second interface module (i.e., the slave interface module) detects the fault of the first interface module; if the second interface module fails, the first interface module detects the fault of the first interface module.

[0107] Specifically, the controller redundancy method for a launcher and the control system redundancy design in the system of the present application mainly include two aspects: hardware redundancy and software redundancy.

[0108] Hardware redundancy is achieved by installing backup components and subsystems at key locations to ensure rapid switching in the event of a hardware failure. That is, a first control subsystem and a second control subsystem are set up so that if the first sub-control system that controls the launch pad fails, it can be quickly replaced with the second control subsystem to control the launch pad.

[0109] Software redundancy is to realize multiple protections for the control system by writing redundant control algorithms and programs. Among them, software redundancy can be realized by using existing technologies.

[0110] Furthermore, software redundancy includes at least: data redundancy and processing redundancy.

[0111] Data redundancy is to copy data into multiple copies and store the copies in different storage locations. When one copy fails, the system can restore the data through other copies.

[0112] Processing redundancy is: distributing processing tasks to multiple processors or processing threads. When one processor or processing thread fails, the system can continue to execute the processing tasks through other processors or processing threads.

[0113] Specifically, software redundancy can significantly enhance the fault tolerance of the system (i.e., the redundant controller system for the launcher). In a complex launch environment, software failures are difficult to avoid. Software redundancy ensures that when the main module (i.e., the first control subsystem) fails, the backup module (i.e., the second control subsystem) can quickly take over by backing up the software module, thereby ensuring the continuity and stability of the launch mission. Software redundancy improves the flexibility and maintainability of the system. With the continuous advancement of technology and changes in launch requirements, the control system needs to be continuously upgraded and optimized. Software redundancy makes this process more convenient. By replacing and upgrading modules (i.e., the first control subsystem and the second control subsystem), the system can quickly adapt to new launch requirements. Software redundancy also reduces the maintenance cost of the system. Through modular design, faulty modules can be accurately located and replaced, avoiding large-scale changes to the entire system, thereby reducing maintenance costs and time costs.

[0114] The beneficial effects achieved by this application are as follows:

[0115] (1) The controller redundancy method and system for a launcher of the present application can improve the reliability and stability of the launch control system.

[0116] (2) The controller redundancy method and system for the launcher of the present application sets up multiple backup or alternative solutions in the key control system to ensure that when a problem occurs in a certain control link, it can quickly switch to other control paths, thereby ensuring the stable operation of the entire system.

[0117] (3) The controller redundancy method and system for the launcher of the present application can automatically switch from the main controller to the slave controller through redundant design, which can avoid overall failure caused by single point failure and ensure the continuity and safety of the production line.

[0118] (4) The controller redundancy method for the launcher and the controller redundancy of the system (i.e., the first control subsystem and the second control subsystem) of the present application can be repaired and / or replaced online without interrupting the mission execution, which greatly reduces the maintenance cost and improves the production efficiency.

[0119] (5) The controller redundancy method and system for the launch pad of the present application enhance the system's fault tolerance and risk resistance.

[0120] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the scope of protection of the present application is intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application. Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the protection scope of the present application and its equivalent technology, the present application is also intended to include these modifications and variations.

Claims

1. A controller redundancy system for a launcher, characterized in that: include: a first control subsystem and a second control subsystem; Wherein, the first control subsystem and the second control subsystem are both connected to the CAN bus; The first control subsystem and the second control subsystem are both connected to the launcher; The first control subsystem is connected to the second control subsystem; When working, data is sent to the first control subsystem and / or the second control subsystem through the CAN bus; the launcher is controlled by the first control subsystem, and if the first subcontrol system fails, the second control subsystem is used to control the launcher.

2. The controller redundancy system for a launcher according to claim 1, characterized in that: The first control subsystem at least includes: a first controller, a first interface module, a first power supply, a first reset module, a first clock and a second clock; the second control subsystem at least includes: a second controller, a second interface module, a second power supply, a second reset module, a third clock and a fourth clock; Wherein, the first controller is connected to the first interface module, the first power supply, the first reset module and the first clock; The first interface module is connected to the first power supply, the first reset module, the second clock and the CAN bus; The second controller is connected to the second interface module, the second power supply, the second reset module, the third clock and the first controller; The second interface module is connected to the second power supply, the second reset module, the fourth clock, the CAN bus and the first interface module; Wherein, the first controller is used to send launcher control instructions and receive launcher status data; The first interface module is used to receive data sent by the CAN bus and send the data to the first controller; First power supply: used to supply power to the first controller and the first interface module; A first reset module: used to reset the first controller and the first interface module; First clock: used to provide a clock frequency for the first controller; Second clock: used to provide clock frequency for the first interface module; The second controller is used to send launcher control instructions and receive launcher status data; The second interface module is used to receive data sent by the CAN bus and send the data to the second controller; Second power supply: used to supply power to the second controller and the second interface module; A second reset module: used for resetting the second controller and the second interface module; The third clock is used to provide a clock frequency for the second controller; Fourth clock: used to provide a clock frequency for the second interface module.

3. The controller redundancy system for a launcher according to claim 2, characterized in that: The first controller includes at least: a first serial port, a second serial port, a third serial port and a status IO pin; the second controller includes at least: a first serial port, a second serial port, a third serial port and a status IO pin; Wherein, the first serial port of the first controller is connected to the first serial port of the second controller, and the first controller and the second controller perform data synchronization through the first serial port; The second serial port of the first controller is connected to the second serial port of the second controller, and the first controller and the second controller communicate through the second serial port and transmit communication data, wherein the communication data at least includes: data received from the CAN bus, and the data received from the CAN bus at least includes: launcher status data, launcher action operation data and heartbeat information; The third serial port and the status IO pin of the first controller are both connected to the first interface module; The third serial port and the status IO pin of the second controller are both connected to the second interface module.

4. The controller redundancy system for a launcher according to claim 3, characterized in that: While the second serial port of the first controller sends the heartbeat information to the second serial port of the second controller, the second serial port of the second controller also sends the heartbeat information to the second serial port of the first controller.

5. The controller redundancy system for a launcher according to claim 3, characterized in that: The first interface module at least includes: a first serial port, a status IO pin, a second serial port, a CAN controller and an IO pin; the second interface module at least includes: a first serial port, a status IO pin, a second serial port, a CAN controller and an IO pin; The first serial port of the first interface module communicates with the third serial port of the first controller; the state IO pin of the first interface module is connected with the state IO pin of the first controller; the CAN controller of the first interface module is connected with the CAN bus; The first serial port of the second interface module communicates with the third serial port of the second controller; the state IO pin of the second interface module is connected with the state IO pin of the second controller; the CAN controller of the second interface module is connected with the CAN bus; The IO pin of the second interface module is connected to the IO pin of the first interface module; The second serial port of the second interface module is connected to the second serial port of the first interface module.

6. The controller redundancy system for a launcher according to claim 5, characterized in that: The status IO pin of the first interface module is used to determine whether the first interface module receives data successfully; When the first controller sends data and the first interface module receives the data, the status IO pin of the first interface module is set to a high position, and the status IO pin of the first controller collects the IO pin status of the status IO pin of the first interface module. If the IO pin status is collected, it indicates that the communication between the first controller and the first interface module is normal; if the IO pin status is not collected, it indicates that the communication between the first controller and the first interface module is faulty.

7. The controller redundancy system for a launcher according to claim 6, characterized in that: The status IO pin of the second interface module is used to determine whether the second interface module receives data successfully; When the second controller sends data and the second interface module receives the data, the status IO pin of the second interface module is set to a high position, and the status IO pin of the second controller collects the IO pin status of the status IO pin of the second interface module. If the IO pin status is collected, it indicates that the communication between the second controller and the second interface module is normal; if the IO pin status is not collected, it indicates that the communication between the second controller and the second interface module is faulty.

8. The controller redundancy system for a launcher according to claim 7, characterized in that: The first control subsystem or the second control subsystem: used to control the opening / closing of the upper clamp of the launcher, the opening / closing of the lower clamp, the upward / downward movement of the load-balancing bracket, and the opening / closing of the last-repair insulation device; used to monitor the horizontality of the launcher; Used to control the movement of the launcher, wherein the movement of the launcher at least includes: erecting and leveling.

9. A controller redundancy method for a launcher, characterized in that: The controller redundancy system for a launcher as claimed in any one of claims 1 to 8 comprises the following steps: S1: Perform system initialization settings on the first control subsystem and the second control subsystem, and determine that the first controller of the first control subsystem is the master controller, and the second controller of the second control subsystem is the slave controller; wherein the system initialization settings at least include: controller initialization and interface initialization; wherein the controller initialization at least includes: controller serial port setting, controller clock configuration and external interrupt initialization; interface initialization at least includes: interface clock configuration, interface serial port configuration and CAN communication initialization; system initialization settings also include: control word and status word; S2: After completing the initialization setting, the master controller and the slave controller conduct synchronous negotiation to eliminate the power-on time difference between the master controller and the slave controller, and when the preset condition is met, the slave controller sends a heartbeat message to the master controller, and the master controller also sends a heartbeat message to the slave controller; if the master controller and / or the slave controller do not receive the heartbeat message sent by the slave controller and / or the master controller when the preset condition is met, the master controller and / or the slave controller are fault diagnosed; if both the master controller and the slave controller receive the heartbeat message when the preset condition is met, S3 is executed; S3: querying the first interface module and the second interface module. If it is determined according to the query that the first interface module and the second interface module are both in normal working state, the CAN bus sends data to the first interface module and the second interface module at the same time; S4: The master controller backs up the data, extracts the system status, backs up the status word and the control word to obtain the backup data, and performs CRC check on the backup data to obtain the first CRC check code; the slave controller backs up the data, extracts the system status, backs up the status word and the control word to obtain the backup data, and performs CRC check on the backup data to obtain the second CRC check code; compares the first CRC check code with the second CRC check code, if the first CRC check code is consistent with the second CRC check code, then the verification data is correct, and enters the controller logic processing program; if the first CRC check code is inconsistent with the second CRC check code, then the verification data is incorrect, and fault diagnosis processing is performed on the master controller and the slave controller.

10. The controller redundancy method for a launcher according to claim 9, characterized in that: Fault diagnosis processing at least includes: master controller and / or slave controller fault processing, hardware fault processing and interface module fault processing.

Citation Information

Cited By

  • High-reliability on-line switchable erecting control system, control method and electronic equipment

    CN122131571A