Aircraft battery failure processing method, computer device and computer readable storage medium

Abstract

The embodiment of the present application discloses a method for handling aircraft battery faults, a computer device, and a computer-readable storage medium. The method includes the following steps: when a fault signal is obtained during flight, the aircraft state is judged to obtain state information; fault analysis processing is performed based on the fault signal and state information, and the fault analysis processing includes threshold analysis processing, pattern analysis processing, and / or automatic analysis processing; at least one processing result obtained by threshold analysis processing, pattern analysis processing, and / or automatic analysis processing is obtained, and all processing results are summarized to obtain current fault information; adjustment instructions are obtained based on the current fault information; and the adjustment instructions are responded to to perform fault handling operations, and the fault handling operations include at least one of flight plan changes, output mode changes, or battery relevance changes. Therefore, the present application can efficiently and safely manage and control aircraft batteries in a faulty state.

Description

Technical Field

[0001] The present application relates to the field of aircraft technology, and in particular to an aircraft battery failure processing method, a computer device, and a computer-readable storage medium. Background Art

[0002] Aircraft have become increasingly common in everyday life. During takeoff and landing, eVTOL (electric vertical take-off and landing) aircraft often require high-rate discharge. To prevent mid-flight battery system failure, eVTOL aircraft typically utilize a distributed layout with multiple battery packs. If a battery pack fails, such as thermal runaway, an internal short circuit, or overheating of a single cell, the pack is forcibly de-energized.

[0003] However, during takeoff or landing, the required output power must be borne by the remaining power battery packs, which results in a corresponding power output demand significantly higher than in normal use. In order to ensure that the aircraft can take off or land safely under special circumstances, the output power of the power battery system often needs to exceed its normal operating range. This high power output will inevitably have an impact on the normal service life of the battery. How to more efficiently and safely manage aircraft batteries in a fault state is a technical problem that needs to be solved urgently by those skilled in the art.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0005] Based on this, it is necessary to address the above problems and propose an aircraft battery fault handling method, computer equipment and computer-readable storage medium, which can efficiently and safely manage aircraft batteries in a faulty state.

[0006] The present application solves the technical problem by adopting the following technical solutions:

[0007] The present application provides an aircraft battery fault handling method, comprising the following steps: when a fault signal is obtained during flight, determining the aircraft state to obtain state information; performing fault analysis processing based on the fault signal and the state information, performing fault analysis processing based on the fault signal and the state information, including: performing threshold analysis processing on the fault signal; and / or performing pattern analysis processing on the state information; and / or inputting the fault signal and the state information into a pre-trained fault analysis model, and performing automatic analysis processing using the fault analysis model; obtaining at least one processing result obtained from the threshold analysis processing, pattern analysis processing, and / or automatic analysis processing, and summarizing all processing results to obtain current fault information; obtaining an adjustment instruction based on the current fault information; and responding to the adjustment instruction to perform a fault handling operation, the fault handling operation including at least one of a flight plan change, an output mode change, or a battery association change.

[0008] In an optional embodiment of the present application, the aircraft status is judged to obtain status information, including: obtaining flight information, performing flight status judgment based on the flight information to obtain flight status information; the flight information includes at least one of flight altitude, speed, destination distance, ambient temperature, wind speed, and air pressure; obtaining battery information, performing battery status judgment based on the battery information to obtain battery status information; the battery information includes at least one of battery pack health, battery pack charge state, battery pack power output requirement, battery pack power limit, battery cell temperature in the battery pack, and single cell voltage; and summarizing the flight status information and battery status information to obtain status information.

[0009] In an optional embodiment of the present application, fault analysis processing is performed based on the fault signal and status information, including: performing threshold analysis processing on the fault signal; and / or, performing pattern analysis processing on the status information; and / or, inputting the fault signal and status information into a pre-trained fault analysis model, and performing automatic analysis processing using the fault analysis model; obtaining at least one processing result obtained by threshold analysis processing, pattern analysis processing and / or automatic analysis processing; and summarizing all processing results to obtain current fault information.

[0010] In an optional embodiment of the present application, before performing fault analysis processing based on the fault signal and status information, the method also includes: obtaining a flight history data set, the flight history data set consisting of multiple flight history data, each flight history data being used to record historical fault signals, historical status information and historical fault information when a condition occurs; determining whether there is matching flight history data for the fault signal and / or status information in the flight history data set; if so, obtaining the historical fault information in the matching flight history data, marking the historical fault information as current fault information and outputting it; if not, performing fault analysis processing based on the fault signal and status information to obtain current fault information.

[0011] In an optional embodiment of the present application, an adjustment instruction is obtained based on the current fault information, including: obtaining the fault category, fault level and fault duration in the current fault information; judging whether the aircraft can complete the remaining flight plan based on the fault category and fault level; if it cannot be satisfied, generating a flight plan change instruction; the flight plan change instruction is used to execute the flight plan change; when the fault category belongs to the first preset battery type fault, the fault level is higher than the preset level, and the fault duration is longer than the preset duration, a normal battery is determined, and a battery output mode change instruction is generated; the battery output mode change instruction is used to execute a battery output mode change for a normal battery; when the fault category belongs to the second preset battery type fault, a faulty battery is determined; and a battery correlation change instruction is generated; the battery correlation change instruction is used to execute a battery correlation change for the faulty battery.

[0012] In an optional embodiment of the present application, when the fault handling operation includes a flight plan change; performing the fault handling operation includes: determining the flight status of the aircraft; if the flight status is a take-off status, controlling the aircraft to stop taking off; if the flight status is a landing status, obtaining the corrected output power after the battery output mode change is executed, and landing according to the corrected output power; if the flight status is a cruising state, determining a safe landing point, obtaining the corrected output power after the battery output mode change is executed; cruising to a safe landing point according to the corrected output power and landing.

[0013] In an optional embodiment of the present application, when the fault handling operation includes a change in battery output mode; the fault handling operation is performed, including: obtaining battery demand power and battery quantity information, the battery quantity information including the total number of batteries, the number of normal batteries, and the number of faulty batteries; calculating the corrected output power based on the battery demand power and the battery quantity information; determining whether the corrected output power is within the battery limit threshold range; if it is not within the battery limit threshold range, executing a flight plan change to control the aircraft to force a landing; if it is within the battery limit threshold range, adjusting the output power of the normal battery according to the corrected output power.

[0014] In an optional embodiment of the present application, when the fault handling operation includes a change in battery association; the fault handling operation is performed, including: determining the faulty battery, judging the battery priority of the faulty battery; determining the fault priority according to the adjustment instruction; determining the disconnection method according to the battery priority and the fault priority, the disconnection method including disconnecting one by one or disconnecting at the same time; disconnecting the faulty battery according to the disconnection method.

[0015] The present application also provides a computer device, comprising a processor and a memory: the processor is configured to execute a computer program stored in the memory to implement the aforementioned method.

[0016] The present application also provides a computer-readable storage medium storing a computer program, which implements the aforementioned method when the computer program is executed by a processor.

[0017] The embodiments of the present application have the following beneficial effects:

[0018] This application can analyze the fault signal after it is sent out during the flight of the aircraft if a battery fails, so as to determine the treatment measures to control the aircraft to deal with the fault. The admission processing process ensures the normal use of the battery system while adapting to the demand for high-power output of the battery in emergency situations. And through the fault signal recognition trigger mechanism, it realizes the switching of multiple output modes of the power battery system, and intelligently adjusts the power and available power limit in combination with the flight control system's judgment of the aircraft status. A longer range is achieved during the flight phase, and higher power is achieved during the landing phase, thereby ensuring the safe landing of the aircraft in a faulty state. It can improve the safety and reliability of eVTOL aircraft in emergency situations without sacrificing the battery life.

[0019] The above description is only an overview of the technical solution of this application. In order to more clearly understand the technical means of this application, which can be implemented in accordance with the contents of the description, and to make the above and other purposes, features and advantages of this application more obvious and easy to understand, the following preferred embodiments are specifically described in detail with reference to the accompanying drawings. It should be understood that the above general description and the detailed description below are only exemplary and explanatory and do not limit this application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 A flowchart of a method for handling aircraft battery failures is provided in accordance with an embodiment.

[0022] Figure 2 A schematic diagram of a process for determining and obtaining status information provided by an embodiment.

[0023] Figure 3 A flowchart of a fault analysis process provided by an embodiment.

[0024] Figure 4 A flowchart of a process for optimizing fault analysis and processing is provided in an embodiment.

[0025] Figure 5 The present invention is a schematic block diagram of the structure of a computer device provided by an embodiment. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0027] Regarding the response measures for failures in aircraft flight, the existing technology still remains in the traditional, mechanical processing method, and does not actually combine the characteristics of the aircraft in this application to achieve fault handling. Based on this, this application proposes a method for handling aircraft battery failures. In order to clearly describe the method provided in this embodiment, please refer to Figures 1 to 4 , including steps S110~S130.

[0028] Step S110: When a fault signal is obtained during flight, the aircraft status is determined to obtain status information.

[0029] In one embodiment, in response to a fault signal being acquired by the aircraft during flight, the fault signal may primarily be a fault signal of the power battery, including but not limited to abnormal voltage, temperature, current, and thermal runaway of the battery cell. Furthermore, abnormal signals from the flight control system or the external environment outside the battery may also be acquired, all of which may affect the battery status. Specific fault signals may also include motor failure, high-voltage line short circuit, other electrical appliance failure, abnormal wind conditions, weightlessness, and the like.

[0030] In one embodiment, the status of the aircraft is judged to obtain status information, including: obtaining flight information, performing flight status judgment based on the flight information to obtain flight status information; the flight information includes at least one of flight altitude, speed, destination distance, ambient temperature, wind speed, and air pressure; obtaining battery information, performing battery status judgment based on the battery information to obtain battery status information; the battery information includes at least one of battery pack health, battery pack charge state, battery pack power output requirement, battery pack power limit, battery cell temperature in the battery pack, and single cell voltage; and summarizing the flight status information and the battery status information to obtain status information.

[0031] In one embodiment, before analyzing and processing the battery fault, status information can also be obtained to perform status judgment. Specifically, this can include battery status judgment for the battery and flight status judgment for the aircraft, so that the load can determine whether emergency measures need to be taken for the fault after the fault is determined. The flight status judgment and battery status judgment are parallel processes. The specific processing flow can be referred to Figure 2 .

[0032] Step S211: Obtain flight information.

[0033] Step S212: performing flight status determination according to the flight information to obtain flight status information.

[0034] In one embodiment, the flight information includes at least one of flight altitude, speed, distance to destination, ambient temperature, wind speed, and air pressure.

[0035] In one embodiment, flight status information may include the following status categories: flight capability status, flight safety status, navigation and track status. Specifically, flight capability status may include reachability and feasibility. Reachability is used to indicate whether the remaining battery power of the aircraft is sufficient to reach the destination, and the remaining battery power is directly related to the battery status. A judgment can be made directly, or additional battery information, such as that of a normal battery, can be obtained, and the remaining battery power can be calculated based on the battery information to determine whether it is sufficient to reach the destination. Feasibility is to consider the impact of ambient temperature, wind speed, air pressure, and altitude on the power system to determine whether it is feasible for the aircraft to maintain a normal flight attitude. Battery information and flight information can be obtained to determine whether the remaining battery power is sufficient to maintain a normal flight attitude, thereby completing the feasibility status judgment.

[0036] Flight safety status can specifically include: normal flight, low battery, or insufficient power. Normal flight means that the battery failure has no significant impact, that is, after the failure occurs, all parameters in the flight information are within the safe range. Low battery indicates that the current flight environment is complex according to the flight information. For example, environmental factors such as wind speed, ambient temperature, and air pressure exceed normal thresholds. Even in normal conditions, the motor needs to output additional power to maintain normal flight. Due to the battery failure, the remaining battery power is reduced, which inevitably cannot support the remaining range. In this case, an emergency landing or early return is required. Insufficient power indicates that the destination distance in the flight information is still a long way off, or the current flight environment is high altitude and low pressure, resulting in a decrease in propeller thrust. The output power of the remaining normal battery needs to be changed, such as increasing the motor speed or lowering the altitude to meet the current power demand. However, due to the battery failure, the remaining normal battery cannot cope with the current environmental impact.

[0037] Navigation and track status can specifically include the aircraft's altitude, speed, attitude, operating power of various electrical components, and route status, including whether it has deviated from its course, whether it can reach the next waypoint as planned, or whether a change in altitude or heading is necessary to accommodate a battery failure. Navigation and track status can be directly determined and obtained based on flight information.

[0038] Step S221: Obtain battery information.

[0039] Step S222: Execute battery status determination according to the battery information to obtain battery status information.

[0040] In one embodiment, the battery information includes at least one of the battery pack health, battery pack state of charge, battery pack power output requirement, battery pack power limit, battery cell temperature, and single cell voltage. The battery pack health (SOH) represents the long-term health of the battery and is usually expressed as current capacity / rated capacity. Low SOH may mean that the battery is degraded and the discharge capacity is reduced, which can easily lead to insufficient power supply. The state of charge (SOC) represents the current remaining battery power and is usually a percentage value of 0%-100%. Low SOC may cause the battery voltage to decrease and the power output to be insufficient, affecting the endurance of the aircraft. Battery pack power output requirement ( P demand ) reflects the power supply required by the current aircraft. Battery pack power limit ( P limit ), set by the Battery Management System (BMS) to prevent overload damage to the battery. T cell ), too high or too low temperature will affect the battery performance: too high (> 60 ℃): may trigger thermal protection, or even thermal runaway; too low (< 0 ℃): discharge capacity decreases, SOC display may be abnormal. Single cell voltage ( V cell ), which reflects the voltage status of a single battery cell. It is usually within a preset range. For example, for lithium batteries, the preset range can be 3.0V-4.2V. Too low or too high may cause battery imbalance or even damage.

[0041] In one embodiment, battery status information may include, but is not limited to, the following battery status types: normal power supply, low battery, battery aging, insufficient power, abnormal temperature (overheat / overcooling), cell imbalance, abnormal power failure, and abnormal voltage (overdischarge / overcharge). The specific status can be determined based on various parameters. The determination criteria for each battery status type can refer to the examples in Table 1.

[0042] Table 1 Battery status types and corresponding judgment conditions

[0043]

[0044] After step S212 and step S222 , step S230 is executed: the flight status information and the battery status information are aggregated to obtain status information.

[0045] In one embodiment, the flight status information and the battery status information are aggregated to obtain status information, which is used for subsequent fault analysis and processing.

[0046] Step S120: Perform fault analysis processing according to the fault signal and status information. Perform fault analysis processing according to the fault signal and status information, including: performing threshold analysis processing on the fault signal; and / or, performing pattern analysis processing on the status information; and / or, inputting the fault signal and status information into a pre-trained fault analysis model, and performing automatic analysis processing using the fault analysis model; obtaining at least one processing result obtained by threshold analysis processing, pattern analysis processing and / or automatic analysis processing, summarizing all processing results to obtain current fault information; and obtaining adjustment instructions based on the current fault information.

[0047] In one embodiment, fault analysis processing is performed in conjunction with the fault signal and status information to obtain current fault information. This current fault information may include, but is not limited to, fault type identification, fault duration, and fault level. Based on this current fault information, corresponding handling measures, or adjustment instructions, can be determined. For example, this can determine whether operational requirements such as output power, duration, total flight power, temperature limits, and voltage limits are met after fault handling. Based on the battery pack's capabilities, corresponding instructions such as forced disconnection of the faulty battery, alteration of subsequent flight plans, display of flight recommendations, and issuance of flight alerts can be triggered. Thus, adjustment instructions are obtained, which can be used to control the drone to adjust to the battery failure and address the fault. In this embodiment, the determination of the current fault information is first explained, followed by a detailed description of the process for obtaining adjustment instructions, which will not be elaborated here.

[0048] In one embodiment, fault signals and status information are indeed two types of data, and the data content and form are different from each other. Therefore, in a preferred embodiment, when performing fault analysis, they can be processed separately; in other embodiments, the two can also be combined for processing. In this regard, this embodiment provides a fault analysis process, please refer to Figure 3 As shown, it includes steps S310~S340. Figure 3 In the figure, the rounded rectangle represents a type of data, and the rectangle represents a process. The flowchart also shows the input and output relationship of data to the process.

[0049] Step S310: performing threshold analysis processing on the fault signal.

[0050] In one embodiment, battery fault signals include, but are not limited to, voltage, temperature, and current anomalies, as well as thermal runaway of the battery cells. These data are presented as numerical values. Typically, each numerical value is assigned a normal threshold range. Therefore, threshold analysis can be performed by directly comparing the fault signal with its corresponding threshold range. For example, if a battery voltage / temperature anomaly is detected, the fault signal can be compared to the corresponding threshold range to identify conditions such as low voltage, high temperature, or a large voltage differential between individual cells, thereby generating the corresponding processing results.

[0051] Step S320: Perform pattern analysis processing on the status information.

[0052] In one embodiment, battery status information, also taking battery status information as an example, is generally categorized as normal or abnormal. Abnormal states can include low battery, battery aging, insufficient power, abnormal temperature, and so on. Furthermore, battery status information indicates that the battery may be in multiple abnormal states simultaneously, as well as the impact and fault level of each abnormal state. Abnormal states can even interfere with each other, sometimes resulting in a detrimental effect of 1+1 > 2. Therefore, for more complex status information, pattern recognition can be performed in conjunction with historical data to determine which abnormality model the status information in the abnormal state conforms to, thereby determining the processing result. This can determine whether the current battery state corresponds to a fault, the fault level, and the fault impact.

[0053] Step S330: input the fault signal and status information into a pre-trained fault analysis model, and perform automatic analysis processing using the fault analysis model.

[0054] In one embodiment, a fault analysis model may be pre-trained, and the fault analysis model may be a classification model, such as an SVM, a neural network, etc. The fault signal and status information are used as input, and the processing result is output. The fault model is automatically identified by the classification model to obtain the processing result.

[0055] After steps S310 , S320 , and S330 , step S340 is executed: obtaining at least one processing result obtained from the threshold analysis processing, the pattern analysis processing, and / or the automatic analysis processing; and summarizing all processing results to obtain current fault information.

[0056] In one embodiment, steps S310, S320, and S330 are parallel steps, and can be processed independently without interfering with each other to obtain respective processing results. Finally, all the obtained processing results are summarized to obtain the current fault information.

[0057] In one embodiment, before performing fault analysis processing according to the fault signal and status information in step S120, the method further includes: obtaining a flight history data set, the flight history data set being composed of a plurality of flight history data, each flight history data being used to record historical fault signals, historical status information, and historical fault information when a condition occurs; determining whether there is matching flight history data for the fault signal and / or status information in the flight history data set; if so, obtaining the historical fault information in the matching flight history data, marking the historical fault information as current fault information, and outputting it; if not, performing fault analysis processing according to the fault signal and status information to obtain current fault information.

[0058] In one embodiment, when the aircraft uses fault signals and status signals to perform fault analysis and processing, there will inevitably be a certain amount of processing time. The impact of the fault is continuous. If the fault analysis and processing cannot quickly determine the current fault information and generate adjustment instructions and respond, it is very likely to cause more serious consequences. To avoid such incidents, one embodiment of the present application can also optimize the fault analysis and processing process and use the flight history data set to improve processing efficiency. For a clear description of this process, please refer to Figure 4 , including steps S410~S430.

[0059] After step S110 , step S410 is executed: obtaining a flight history data set.

[0060] In one embodiment, various problems inevitably arise during the flight of an aircraft. Each time a problem occurs, the data associated with the problem can be recorded to generate a flight history dataset. The flight history dataset consists of multiple pieces of flight history data, each of which records historical fault signals, historical status information, and historical fault information associated with the problem.

[0061] Step S420: Determine whether the fault signal and / or status information has matching flight history data in the flight history data set.

[0062] If so, step S430 is executed: historical fault information in the matching flight history data is obtained, the historical fault information is marked as current fault information and output; and an adjustment instruction is determined according to the current fault information.

[0063] In one embodiment, the aircraft may search the flight history data set for the fault signal and status signal before performing fault analysis processing to determine whether there is any matching flight history data. The retrieval process may process the frame fault signal and status signal into feature information, and calculate the similarity with the feature information of the historical flight history data in the flight data set. Extract several flight history data with the highest similarity, and the corresponding similarity calculation value. Determine whether the similarity calculation value is greater than a preset similarity threshold. If so, it is determined that there is matching flight history data. Then directly extract the historical fault information in the historical flight data with the largest similarity calculation value, and output it as the current fault information. The above direct method bypasses the fault analysis processing, achieves rapid positioning, and increases processing efficiency.

[0064] If not, step S120 is executed. Step S130 is executed after steps S120 and S430.

[0065] In one embodiment, on the contrary, if no matching flight history data is retrieved, the fault analysis process is still performed according to the previous steps.

[0066] In one embodiment, the current fault information may include, but is not limited to, fault type, fault level, and fault duration. The fault type is the type result obtained based on the aforementioned processing results. The fault duration is the duration directly determined for each type of fault. The fault level can be divided into levels based on the fault type, fault duration, and impact level. For example, there may be four levels: minor, medium, severe, and critical. The minor level indicates that the abnormality caused by the current fault is minor and does not affect the flight, such as a short voltage drop; the medium level indicates that the current fault may affect the flight endurance or safety and requires monitoring, such as the battery voltage is continuously too low; the severe level indicates that the current fault affects flight safety and the flight strategy must be adjusted, such as the battery voltage cannot maintain the motor power; the critical level indicates that the current fault may cause a crash and must be handled urgently, such as multiple batteries stop working and the aircraft can no longer maintain operation. Therefore, different fault levels will affect the adjustment instructions. For example, the mild level only requires recording the log and continuing to fly without generating adjustment instructions; the medium level not only generates an early warning prompt, but also can reduce the load through adjustment instructions; the severe level requires immediate return or emergency landing according to the adjustment instructions; the critical level requires an emergency landing according to the adjustment instructions, triggering the safety mechanism.

[0067] In one embodiment, an adjustment instruction is obtained based on the current fault information, including: obtaining the fault category, fault level and fault duration in the current fault information; judging whether the aircraft can complete the remaining flight plan based on the fault category and fault level; if it cannot be satisfied, generating a flight plan change instruction; the flight plan change instruction is used to execute the flight plan change; when the fault category belongs to the first preset battery type fault, the fault level is higher than the preset level, and the fault duration is longer than the preset duration, a normal battery is determined, and a battery output mode change instruction is generated; the battery output mode change instruction is used to execute a battery output mode change for a normal battery; when the fault category belongs to the second preset battery type fault, a faulty battery is determined; and a battery correlation change instruction is generated; the battery correlation change instruction is used to execute a battery correlation change for the faulty battery.

[0068] In one embodiment, the adjustment instruction is a method for handling a fault, corresponding to a fault handling operation, and includes a flight plan change instruction, a battery output mode change instruction, and a battery relevance change instruction.

[0069] In one embodiment, a determination is made as to whether the aircraft can complete the remaining flight plan based on the fault type and fault level. This calculation can be combined with the remaining flight path and remaining battery power. Applicable scenarios include low battery, abnormal battery temperature but still operable, or insufficient battery power. If these conditions are met, normal flight can be continued, or the battery output power can be adjusted or the load reduced. If these conditions are not met, a flight plan change instruction is generated, which is used to execute the flight plan change. A flight plan can not only indicate the next destination the aircraft needs to reach but also the state that needs to be maintained during flight. Therefore, a flight plan change instruction can specifically include optimizing the route (selecting the nearest landing point); reducing flight speed (reducing power requirements and extending flight range); reducing load (reducing climb rate and thrust); and returning home early (avoiding mission failure or aircraft crash due to power outage).

[0070] In one embodiment, when the fault type belongs to the first preset battery type fault, the first preset battery type fault is generally for the situation where the faulty battery has little impact on other normal batteries, including but not limited to: battery power output is limited, single cell voltage is V cell Large gap, battery temperature T cell High but within the safe range, etc., can be customized by the user. Corresponding to the fault level, in the previous example, it is generally moderate but not higher than severe. This level typically persists for a period of time. This can identify a healthy battery and generate a battery output mode change command. This command is used to adjust the healthy battery. The specific operation will be explained later.

[0071] In one embodiment, when the fault category falls under the second preset battery category, this second preset battery category generally refers to situations where the faulty battery significantly impacts other normal batteries, including but not limited to: thermal runaway of a battery cell, internal short circuit of the battery pack, single cell overtemperature, relay sticking, and other fault phenomena that could affect safe flight. The specific fault category can be set by the user. The faulty battery is identified and a battery association change instruction is generated. The battery association change instruction is used to change the battery association for the faulty battery. The specific operation will be described in detail below.

[0072] Step S130: responding to the adjustment instruction to perform a fault handling operation.

[0073] In one embodiment, when the fault handling operation includes a flight plan change; performing the fault handling operation includes: determining the flight status of the aircraft; if the flight status is a take-off status, controlling the aircraft to stop taking off; if the flight status is a landing status, obtaining the corrected output power after the battery output mode change is executed, and landing according to the corrected output power; if the flight status is a cruising state, determining a safe landing point, obtaining the corrected output power after the battery output mode change is executed; cruising to the safe landing point according to the corrected output power and landing.

[0074] In one embodiment, flight plan changes include shortening the flight range, suggesting a change of destination, prompting to land at an alternate airport, providing an alarm and prompting for an emergency landing, providing an alarm and prompting for a glide and forced landing, etc. Furthermore, different flight plan changes can be implemented based on the aircraft's flight status.

[0075] Accurately determine the aircraft's flight status, which includes takeoff, landing, and cruise control. Once the aircraft is detected in takeoff, both takeoff and landing modes place significant short-term demands on the battery. If a battery failure occurs during takeoff, the remaining battery may not be able to support the aircraft's takeoff, let alone subsequent cruise control. Therefore, in a preferred embodiment, flight plan changes control the aircraft's takeoff process.

[0076] Similar to takeoff, landing also requires additional battery load. However, since the aircraft is already landing, to avoid crashing or crashing, a series of steps can be performed: first, obtain the corrected output power after changing the battery output mode, and then use this corrected output power to guide the aircraft to a safe landing. The method for obtaining the corrected output power will be described later and will not be elaborated here.

[0077] When the aircraft is in cruise mode, its first priority is to determine a safe landing point. It then obtains the corrected output power after the battery output mode change and uses this corrected output power to guide the aircraft to that safe landing point for a safe landing. This safe landing point can be nearby, back to the takeoff point, or the next originally planned node. The specific process depends on the aircraft's battery status and choosing the appropriate landing point is not detailed here.

[0078] In one embodiment, when the fault handling operation includes a change in battery output mode; performing the fault handling operation includes: obtaining battery demand power and battery quantity information, the battery quantity information includes the total number of batteries, the number of normal batteries, and the number of faulty batteries; calculating the corrected output power based on the battery demand power and the battery quantity information; determining whether the corrected output power is within the battery limit threshold range; if not within the battery limit threshold range, executing a flight plan change to control the aircraft to force a landing; if within the battery limit threshold range, adjusting the output power of the normal battery according to the corrected output power.

[0079] In one embodiment, when a fault occurs, the aircraft usually needs to continue to fly to complete landing or patrol, etc. However, due to the loss of function of the faulty battery itself, the output power of the remaining normal batteries needs to be corrected in order to ensure the basic flight function of the aircraft. Obtain the battery demand power P total , battery quantity information, battery quantity information includes the total number of batteries M , number of normal batteries, number of faulty batteries n . Calculate the corrected output power based on the battery power requirement and battery quantity information. The calculation process can be referred to:

[0080] P battery =P total *M / (Mn) (1)

[0081] In the above formula, P batteryTo correct the output power, that is, the power that the remaining normal batteries need to output. In some cases, the corrected output power does not completely match the output power of the normal batteries. For example, it may exceed the normal output power upper limit of the battery. Therefore, before actually adjusting the normal battery power, it is necessary to determine whether the corrected output power is within the battery limit threshold range. If it is not within the battery limit threshold range, it means that the remaining normal batteries are unable to output according to the corrected output power and are no longer able to carry the remaining flight plan. To ensure flight safety and battery life, in a preferred embodiment, an emergency landing is required rather than continuing to complete the original flight plan. Therefore, it is necessary to execute a flight plan change, specifically to control the aircraft to force a landing. If it is within the battery limit threshold range, it means that the remaining normal batteries can still carry the remaining flight plan. The output power of the normal batteries is adjusted according to the corrected output power to complete the subsequent flight plan.

[0082] Correcting the output power can trigger a change in the battery management system's (BMS) output mode to adapt to the current flight state and power battery status. For example, if a forced landing command corresponds to an increase in the battery pack's peak output power requirement, and the original battery discharge power limit cannot meet the emergency needs, fault analysis and processing will trigger the battery to switch to high-power output mode, increasing the battery pack's discharge power limit and discharge voltage limit.

[0083] To facilitate understanding, let's take an example to illustrate how different output modes correspond to different charge / discharge cutoff voltages, peak discharge powers, and discharge power jump logic. For example, the following three modes are possible.

[0084] Mode 1: Normal mode corresponds to the normal operation of all battery packs. The battery discharge cut-off voltage is higher, such as 3.0V, and the discharge power is relatively low, which meets the normal flight and landing requirements of the aircraft and extends the battery system service life.

[0085] Mode 2: Single-pack failure mode, corresponding to a single battery pack forced to power off, the total number of power system battery packs is reduced by 1, the battery discharge cut-off voltage is reduced to 2.5V, and the discharge power is proportionally adjusted and increased to meet the aircraft's emergency flight and landing requirements.

[0086] Mode 3: n-pack failure mode, corresponding to forced power-off of multiple battery packs, the total number of power system battery packs is reduced by 2, the battery discharge end voltage is reduced to 2.0V, and the discharge power is proportionally adjusted and increased to meet the requirements of emergency landing of the aircraft.

[0087] Thus, through multiple modes, not only the output power can be adapted and corrected, but also different flight plans during flight plan changes can be adapted.

[0088] In one embodiment, when the fault handling operation includes a change in battery association; the fault handling operation is performed, including: determining the faulty battery, judging the battery priority of the faulty battery; determining the fault priority according to the adjustment instruction; determining the disconnection method according to the battery priority and the fault priority, the disconnection method including disconnecting one by one or disconnecting simultaneously; disconnecting the faulty battery according to the disconnection method.

[0089] In one embodiment, the battery association change is aimed at the situation where the fault category of the faulty battery belongs to the second preset battery category fault, specifically including but not limited to: battery cell thermal runaway fault, internal short circuit of the battery pack, single cell overtemperature, relay sticking detection, etc. In order to prevent the faulty battery from affecting the normal battery or system, it needs to be disconnected from the battery pack. Determine which batteries have failed, and then evaluate these faulty batteries to determine their respective battery priorities. Next, based on the adjustment instructions received, the aircraft needs to redetermine the fault priority of these faulty batteries. After comprehensively considering the battery priority and the fault priority, the aircraft will decide which disconnection method to use to handle these faulty batteries. There are two main options for disconnection methods: disconnect one by one or disconnect at the same time. Disconnect the faulty battery relay according to the selected disconnection method to avoid interference from the faulty battery.

[0090] In one embodiment, the three change operations in the fault handling operation are not mutually exclusive, but are related to each other. For example, as mentioned above, when the fault handling operation is to perform a flight plan change, the corrected output power calculated during the output mode change process is required.

[0091] Therefore, the present application can analyze the fault signal after the battery fails during the flight of the aircraft to determine the treatment measures to control the aircraft to deal with the fault. This processing flow not only ensures the normal use of the battery system, but also adapts to the demand for high power output of the battery in emergency situations. And through the fault signal recognition trigger mechanism, it realizes the switching of multiple output modes of the power battery system, and combines the flight control system's judgment on the aircraft status to intelligently adjust the power and available power limit. A longer range is achieved during the flight phase, and higher power is achieved during the landing phase, thereby ensuring the safe landing of the aircraft in a faulty state. It can improve the safety and reliability of eVTOL aircraft in emergency situations without sacrificing the battery life.

[0092] Figure 5 FIG1 shows an internal structure diagram of a computer device in an embodiment. The computer device can be a terminal or a server. Figure 5As shown, the computer device includes a processor, a memory, and a network interface connected via a system bus. The memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program. When the computer program is executed by the processor, the processor can implement the aircraft battery failure handling method. The internal memory may also store a computer program. When the computer program is executed by the processor, the processor can implement the aircraft battery failure handling method. It will be understood by those skilled in the art that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0093] In one embodiment, the present application further proposes a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor executes the steps of the method described in any of the aforementioned embodiments.

[0094] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0095] It should be noted that, in this document, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0096] It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0097] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0098] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0099] It should be noted that in this article, step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the order. When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.

[0100] It should be understood that the specific embodiments described herein are intended only to explain the present application and are not intended to limit the present application. The technical features of the above embodiments may be combined in any manner. To simplify the description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction between the combinations of these technical features, they should be considered to be within the scope of this specification.

[0101] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be determined by the appended claims.

Claims

1. A method for handling aircraft battery failure, characterized in that: The steps include: When a fault signal is obtained during flight, the aircraft status is judged to obtain status information; Performing fault analysis processing based on the fault signal and the status information, the performing fault analysis processing based on the fault signal and the status information including: performing threshold analysis processing on the fault signal; and / or performing pattern analysis processing on the status information; and / or inputting the fault signal and the status information into a pre-trained fault analysis model and performing automatic analysis processing using the fault analysis model; obtaining at least one processing result obtained from the threshold analysis processing, the pattern analysis processing, and / or the automatic analysis processing, summarizing all the processing results to obtain current fault information; and obtaining an adjustment instruction based on the current fault information; responding to the adjustment instruction to perform a fault handling operation, the fault handling operation including a flight plan change, an output mode change, and a battery relevance change; When the fault handling operation includes a change in battery output mode; the execution of the fault handling operation includes: obtaining battery demand power and battery quantity information, the battery quantity information including the total number of batteries, the number of normal batteries, and the number of faulty batteries; calculating a corrected output power based on the battery demand power and the battery quantity information; determining whether the corrected output power is within the battery limit threshold range; if not within the battery limit threshold range, executing the flight plan change to control the aircraft to force a landing; if within the battery limit threshold range, adjusting the output power of the normal battery according to the corrected output power.

2. The aircraft battery failure handling method according to claim 1, wherein: The determining of the aircraft status to obtain status information includes: Acquiring flight information, and performing flight status determination based on the flight information to obtain flight status information; the flight information includes at least one of flight altitude, speed, distance to destination, ambient temperature, wind speed, and air pressure; Acquire battery information, and perform battery status determination based on the battery information to obtain battery status information; the battery information includes at least one of battery pack health, battery pack state of charge, battery pack power output requirement, battery pack power limit, battery cell temperature within the battery pack, and single cell voltage; The flight status information and the battery status information are aggregated to obtain the status information.

3. The aircraft battery failure handling method according to claim 1, wherein: Before performing the fault analysis process according to the fault signal and the status information, the method further includes: Acquire a flight history data set, the flight history data set consisting of a plurality of flight history data, each of the flight history data being used to record a historical fault signal, historical status information, and historical fault information when a condition occurs; Determining whether the fault signal and / or the status information has matching flight history data in the flight history data set; If so, obtaining the historical fault information in the matching flight history data, marking the historical fault information as current fault information and outputting it; If not, a fault analysis process is performed on the fault signal and the status information to obtain current fault information.

4. The aircraft battery failure handling method according to claim 1, wherein: The obtaining of an adjustment instruction according to the current fault information includes: Obtaining the fault type, fault level, and fault duration in the current fault information; Determining whether the aircraft can complete the remaining flight plan based on the fault type and the fault level; if the aircraft cannot complete the remaining flight plan, generating a flight plan change instruction; the flight plan change instruction is used to execute the flight plan change; When the fault category belongs to a first preset battery fault, the fault level is higher than a preset level, and the fault duration is longer than a preset duration, determining that the battery is normal and generating a battery output mode change instruction; the battery output mode change instruction is used to execute the battery output mode change for the normal battery; When the fault category belongs to a second preset battery type fault, the faulty battery is determined; and a battery association change instruction is generated; the battery association change instruction is used to execute the battery association change for the faulty battery.

5. The aircraft battery failure handling method according to claim 1, wherein: When the fault handling operation includes a flight plan change; The performing of the fault handling operation includes: Determining the flight status of the aircraft; If the flight state is a take-off state, controlling the aircraft to stop taking off; If the flight state is a landing state, obtaining a corrected output power after executing the battery output mode change, and performing landing according to the corrected output power; If the flight state is a cruising state, a safe landing point is determined, and the corrected output power after the battery output mode change is performed is obtained; and the aircraft cruises to the safe landing point according to the corrected output power and lands.

6. The aircraft battery failure handling method according to claim 1, wherein: When the fault handling operation includes a battery relevance change; The performing of the fault handling operation includes: Identify a faulty battery and determine a battery priority of the faulty battery; determine the fault priority according to the adjustment instruction; Determining a disconnection mode according to the battery priority and the fault priority, wherein the disconnection mode includes disconnecting one by one or disconnecting simultaneously; The faulty battery is disconnected according to the disconnection method.

7. A computer device, characterized in that: including processor and memory; The processor is configured to execute the computer program stored in the memory to implement the method according to any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images