Method and device for clearing faults of motor controller of vehicle, processor and vehicle

Abstract

The invention discloses a method and device for clearing faults of a motor controller of a vehicle, a processor and the vehicle. The method comprises the steps that in response to the detected fault of a motor controller, running state information of a vehicle is obtained, and the running state information is used for representing the running state of the vehicle under the fault of the motor controller; based on the operation state information, determining a target number of times of clearing faults of the motor controller; determining the fault type of the motor controller fault based on the relationship between the target number of times and a target number of times threshold; based on the fault type, a target fault clearing strategy is determined, and the target fault clearing strategy is used for representing a rule for controlling the motor controller to clear the fault of the motor controller under the fault type; and according to the target fault clearing strategy, controlling the motor controller to clear the fault of the motor controller. According to the invention, the technical problem of low accuracy of fault clearing of the motor controller of the vehicle is solved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a method, device, processor and vehicle for clearing a motor controller fault of a vehicle. Background Art

[0002] Currently, during vehicle startup and driving, low-voltage fluctuations, electromagnetic interference, and other factors can cause hardware (such as motor controller) fault detection circuits to falsely detect faults. Directly confirming the fault and immediately stopping the vehicle can lead to reduced vehicle performance, power interruption, and safety issues. Therefore, it is crucial to detect and eliminate faults in the vehicle's motor controller.

[0003] In the related art, for fault detection of the vehicle's motor controller, the fault is detected directly through level judgment. The above method of detecting faults only through level judgment is relatively simple and can only identify those fault types that directly affect the level, resulting in inaccurate determination of the fault type, thereby affecting the accuracy of clearing the vehicle's motor controller fault.

[0004] Currently, no effective solution has been proposed to the above-mentioned technical problem of low accuracy in clearing a motor controller fault in a vehicle. Summary of the Invention

[0005] Embodiments of the present invention provide a method, device, processor, and vehicle for clearing a motor controller fault of a vehicle, so as to at least solve the technical problem of low accuracy in clearing a motor controller fault of a vehicle.

[0006] According to one aspect of an embodiment of the present invention, a method for clearing a motor controller fault in a vehicle is provided. The method may include: in response to detecting a motor controller fault, obtaining operating status information of the vehicle, wherein the operating status information indicates the operating status of the vehicle under the motor controller fault; determining a target number of times to clear the motor controller fault based on the operating status information; determining the fault type of the motor controller fault based on a relationship between the target number of times and a target number threshold; determining a target fault clearing strategy based on the fault type, wherein the target fault clearing strategy indicates a rule for controlling the motor controller to clear the motor controller fault under the fault type; and controlling the motor controller to clear the motor controller fault according to the target fault clearing strategy.

[0007] Optionally, determining a target number of times for clearing the motor controller fault based on the operating status information includes: clearing the motor controller fault based on the operating status information to obtain a clearing result; and determining the target number of times based on the clearing result.

[0008] Optionally, based on the relationship between the target number and the target number threshold, the fault type of the motor controller is determined, including: in response to the target number being less than or equal to the target number threshold, determining the fault type as a false detection fault type; in response to the target number being greater than the target number threshold, determining the fault type as a true fault type.

[0009] Optionally, based on the fault type, a target fault clearing strategy is determined, including: in response to the fault type being a false detection fault type, detecting the electronic components in the motor controller to obtain detection results; based on the detection results, adjusting the electronic components to determine that the target fault clearing strategy represents a rule for clearing the electronic component fault.

[0010] Optionally, the method further includes: in response to the fault type being a real fault type, determining that the target fault clearing strategy represents a rule of shutting down the motor controller.

[0011] Optionally, after determining the fault type of the motor controller based on the relationship between the target number of times and the target number threshold, the method further includes: in response to the fault type being a false detection fault type, sending a control signal of the motor controller to the vehicle, wherein the control signal is used to control the normal driving of the vehicle; in response to the fault type being a true fault type, controlling the motor controller to generate prompt information, wherein the prompt information is used to prompt the vehicle to switch from normal driving to stop driving.

[0012] Optionally, the method further includes: in response to a battery voltage of the motor controller being lower than a voltage threshold, supplying power to the motor controller via a power battery, wherein the power battery includes two power supply paths.

[0013] According to another aspect of an embodiment of the present invention, a device for clearing a motor controller fault in a vehicle is provided. The device may include: an acquisition unit for acquiring vehicle operating status information in response to detecting a motor controller fault, wherein the operating status information indicates the operating status of the vehicle under the motor controller fault; a first determination unit for determining a target number of times for clearing the motor controller fault based on the operating status information; a second determination unit for determining the fault type of the motor controller fault based on a relationship between the target number of times and a target number threshold; a third determination unit for determining a target fault clearing strategy based on the fault type, wherein the target fault clearing strategy indicates a rule for controlling the motor controller to clear the motor controller fault under the fault type; and a control unit for controlling the motor controller to clear the motor controller fault according to the target fault clearing strategy.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium includes a stored program, wherein when the program is executed, the device containing the computer-readable storage medium is controlled to execute the method for clearing a motor controller fault in a vehicle according to an embodiment of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a processor is provided, which is configured to run a program, wherein when the program is run, the method for clearing a motor controller fault of a vehicle according to an embodiment of the present invention is executed.

[0016] According to another aspect of an embodiment of the present invention, a vehicle is provided, which is used to execute the method for clearing a motor controller fault of a vehicle according to an embodiment of the present invention.

[0017] In an embodiment of the present invention, if a motor controller fault of a vehicle needs to be cleared, the vehicle's operating state information can be obtained when a motor controller fault is detected, wherein the operating state information is used to represent the operating state of the vehicle under the motor controller fault; a target number of times for clearing the motor controller fault can be determined based on the operating state information; the fault type of the motor controller fault can be determined based on the relationship between the target number of times and the target number of times threshold; a target fault clearing strategy can be determined based on the fault type, wherein the target fault clearing strategy is used to represent a rule for controlling the motor controller to clear the motor controller fault under the fault type; and the motor controller can be controlled to clear the motor controller fault according to the target fault clearing strategy. In an embodiment of the present invention, according to different operating states of the vehicle (e.g., stationary, low speed, high speed, ultra-high speed, etc.), the motor controller fault is cleared a target number of times, and according to the relationship between the target number of times and the target number of times threshold, it is determined whether the motor controller fault can be cleared, and whether the fault type of the motor controller fault is a true fault type or a false fault type, thereby specifically determining the target fault clearing strategy and clearing the motor controller fault, thereby solving the technical problem of low accuracy in clearing the motor controller fault of the vehicle and achieving the technical effect of improving the accuracy of clearing the motor controller fault of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0019] Figure 1 is a flow chart of a method for clearing a motor controller fault of a vehicle according to an embodiment of the present invention;

[0020] Figure 2is a schematic diagram of a circuit diagram of a backup power supply according to an embodiment of the present invention;

[0021] Figure 3 is a schematic diagram of a circuit diagram of a switching circuit of a backup power supply according to an embodiment of the present invention;

[0022] Figure 4 is a flow chart of a control strategy method according to an embodiment of the present invention;

[0023] Figure 5 The figure is a schematic diagram of a device for clearing a motor controller fault of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only 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 ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0025] It should be noted that the terms "first," "second," and the like in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatus.

[0026] According to an embodiment of the present invention, an embodiment of a method for clearing a motor controller fault in a vehicle is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0027] Figure 1 FIG. 1 is a flow chart of a method for clearing a motor controller fault of a vehicle according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0028] Step S102 : In response to detecting a motor controller failure, obtaining vehicle operation status information.

[0029] In the technical solution provided in step S102 of the present invention, the vehicle may be a new energy vehicle, which is provided for illustrative purposes only and is not specifically limited herein. The operating status information may be used to indicate the operating status of the vehicle in the event of a motor controller failure. The operating status information may include the vehicle's driving speed, the vehicle's motor controller speed, battery voltage information, etc., which is provided for illustrative purposes only and is not specifically limited herein.

[0030] In this embodiment, if a motor controller fault is detected, such as an insulated gate bipolar transistor (IGBT) fault in the motor controller, the vehicle's operating status information can be obtained under the motor controller fault, providing a basis for subsequently determining the target number of times to clear the motor controller fault based on the operating status information.

[0031] Optionally, the vehicle's operating status information can be obtained via an onboard Controller Area Network (CAN) bus or a sensor. It should be noted that the method for obtaining the vehicle's operating status information is merely illustrative and is not specifically limited herein. Any method capable of obtaining the vehicle's operating status in the event of a motor controller failure is within the scope of protection of the embodiments of the present invention.

[0032] Step S104: determining a target number of times to clear the motor controller fault based on the operating status information.

[0033] In the technical solution provided in the above step S104 of the present invention, for the motor controller failure, in order to ensure that under different vehicle operating conditions, the target fault clearing strategy subsequently adopted can not only effectively identify and handle the motor controller failure, but also avoid negative impact on driving safety, the target number of times for clearing the motor controller failure can be determined based on the operating status information.

[0034] In this embodiment, after obtaining the operating status information of the vehicle, a target number of times to clear the motor controller fault can be determined based on the operating status information. The operating state of the vehicle under the motor controller fault can be a stationary state, a low speed state, a relatively high speed state, or an ultra-high speed state. Among them, when the vehicle speed is 0 rpm, it can be identified that the vehicle is in a stationary state. When the speed is lower than 100 rpm, it can be identified that the vehicle is in a low-speed driving state. When the vehicle speed exceeds 100 rpm and does not reach 6000 rpm, it can be identified that the vehicle is in a relatively high speed state. When the speed exceeds 6000 rpm, it can be identified that the vehicle is in an ultra-high speed state.

[0035] Optionally, when the vehicle is stationary, the target number of attempts can be unlimited, as even a failed attempt to clear the fault will not immediately threaten vehicle stability and driver safety. When the vehicle is traveling at a low speed, the target number of attempts can be 8, as the lower vehicle speed means that even a brief power outage will be easier to control and less dangerous. When the vehicle is at a higher speed, the target number of attempts can be 1. In this state, power delays caused by frequent attempts need to be avoided to prevent the vehicle from losing control. When the vehicle is at an extremely high speed, the target number of attempts can be 0. In this state, conservative safety measures should be taken immediately and the motor controller fault should not be cleared.

[0036] It should be noted that the above determination of the target number of times is only for illustration, and no specific limitation is imposed on the numerical value of the target number of times.

[0037] Step S106 : determining the fault type of the motor controller fault based on the relationship between the target number of times and the target number threshold.

[0038] In the technical solution of step S106 of the present invention, determining the fault type of the motor controller is a key link in fault management and safety response. Determining the fault type of the motor controller fault can specifically determine the subsequent target fault clearing strategy.

[0039] In this embodiment, after determining a target number of times to clear the motor controller fault based on the operating status information, a target number threshold can be set. By comparing the target number with the target number threshold, the fault type of the motor controller fault can be determined. The target number threshold can be adjusted according to the operating status of the vehicle.

[0040] For example, when the vehicle is in a low-speed state, the target number threshold can be set to 10 times. If the motor controller fault is cleared on the 5th attempt, it can be considered that the fault type of the motor controller fault is a false detection fault type, that is, a false fault, and this fault type is recoverable. For example, the control chip fault of the motor controller is cleared, and the complex programmable logic device (CPLD) fault is cleared. If the motor controller fault is still not cleared after 10 attempts, it can be considered that the fault type of the motor controller fault is a real fault type, that is, a true fault, and this fault type may not be recoverable in time. At this time, the emergency safety program can be started to control the vehicle to stop safely.

[0041] Step S108: Determine a target fault clearing strategy based on the fault type.

[0042] In the technical solution of step S108 of the present invention, the target fault clearing strategy may be used to indicate a rule for controlling the motor controller to clear the motor controller fault under the fault type.

[0043] In this embodiment, after determining the fault type of the motor controller fault based on the relationship between the target number and the target number threshold, a specific target fault clearing strategy can be formulated based on the fault type to effectively respond to and clear the motor controller fault while ensuring the safe operation and driving experience of the vehicle.

[0044] Alternatively, if the fault type is a true fault, the targeted fault clearance strategy focuses on taking immediate safety measures to prevent further damage and ensure driver safety. For example, the motor controller will no longer respond to start commands from the vehicle and will remain unresponsive even if the driver attempts to restart. Another example, in this true fault type, the vehicle's malfunction warning light will be activated, providing a clear fault signal to the driver and the surrounding environment.

[0045] Optionally, if the fault type is a false detection fault, the target fault clearing strategy focuses on clearing the motor controller fault to reduce unnecessary vehicle downtime and driving distress. For example, attempts are made to clear the motor controller's control chip fault, such as the fault record or status on the microcontroller unit (MCU), or to clear the CPLD fault.

[0046] Optionally, the control chip can control the motor controller's operational and control logic. When the control chip detects an error or fault, it can attempt to restore normal functionality by restarting, resetting, or executing a specific fault-clearing routine. After clearing the control chip fault, the fault status in the CPLD can be cleared, for example, by updating the CPLD configuration or executing a specific clearing routine to ensure that any recorded fault conditions are addressed.

[0047] In an embodiment of the present invention, by accurately determining the fault type of the motor controller fault, a faster response and effective measures can be taken. For example, in a case where the fault type of the motor controller fault is a false detection fault type, the motor controller fault is cleared, and in a case where the fault type of the motor controller fault is a true fault type, the vehicle is controlled to enter a safe mode to prevent potential serious faults, thereby solving the problem that during vehicle startup and driving, the hardware fault (for example, motor controller fault) detection circuit may falsely detect a fault due to low voltage fluctuations, electromagnetic interference, etc., and immediate parking will cause great trouble to the user and also affect driving safety.

[0048] Step S110 : controlling the motor controller to clear the motor controller fault according to the target fault clearing strategy.

[0049] In the technical solution of step S110 of the present invention, after determining the target fault clearing strategy based on the fault type, the motor controller can be controlled to clear the motor controller fault according to the target fault clearing strategy to restore the normal operation of the motor controller.

[0050] For example, if an IGBT fault is detected, it can be uploaded to the CPLD, which will then latch and record the IGBT fault. If the vehicle is stationary, you can continue trying to clear the IGBT fault until the user issues a start command. If the fault can be cleared before the vehicle start signal is received, it indicates that the fault is a false fault, and you can then clear other electronic components of the motor controller. For example, clear the control chip fault first, then clear the CPLD fault. If the IGBT fault is not cleared before the vehicle start signal is received, it indicates that the motor controller fault is a true fault and will not respond to the vehicle start signal. The vehicle fault light will also be on, and the vehicle will fail to start, and the vehicle will be parked and waiting for repairs without clearing other electronic components of the motor controller.

[0051] In the above steps S102 to S110 of the present application, if it is necessary to clear the motor controller fault of the vehicle, the operating status information of the vehicle can be obtained when a motor controller fault is detected, wherein the operating status information is used to indicate the operating status of the vehicle under the motor controller fault; based on the operating status information, the target number of times for clearing the motor controller fault can be determined; based on the relationship between the target number and the target number threshold, the fault type of the motor controller fault can be determined; based on the fault type, a target fault clearing strategy can be determined, wherein the target fault clearing strategy is used to indicate the rules for controlling the motor controller to clear the motor controller fault under the fault type; and according to the target fault clearing strategy, the motor controller can be controlled to clear the motor controller fault. In an embodiment of the present invention, according to different operating states of the vehicle (for example, stationary, low speed, high speed, ultra-high speed, etc.), the motor controller fault is cleared a target number of times, and according to the relationship between the target number and the target number threshold, it is determined whether the motor controller fault can be cleared, and it is judged whether the fault type of the motor controller fault is a real fault type or a false detection fault type, so as to determine the target fault clearing strategy in a targeted manner, and clear the motor controller fault, thereby solving the technical problem of low accuracy in clearing the vehicle's motor controller fault and achieving the technical effect of improving the accuracy of clearing the vehicle's motor controller fault.

[0052] The above method of this embodiment is further introduced below.

[0053] As an optional embodiment, step S104 determines the target number of times to clear the motor controller fault based on the operating status information, including: clearing the motor controller fault based on the operating status information to obtain a clearing result; and determining the target number of times based on the clearing result.

[0054] In this embodiment, in the process of determining the target number of times to clear the motor controller fault based on the operating status information, in order to deal with the motor controller fault more accurately, the motor controller fault can be cleared based on the operating status information to obtain a clearing result; the target number of times can be determined based on the clearing result.

[0055] Optionally, when a motor controller fault is detected, one or a preset number of fault clearing attempts can be performed, depending on the vehicle's current operating state. The target number of subsequent fault clearing attempts can be dynamically adjusted based on the clearing results and the vehicle's operating state. For example, at low vehicle speeds or when stationary, a higher number of clearing attempts can be allowed to increase the likelihood of fault recovery. At very high speeds, for safety reasons, the target number of clearing attempts can be limited, or higher-level safety measures can be immediately implemented.

[0056] As an optional implementation method, step S106 determines the fault type of the motor controller based on the relationship between the target number and the target number threshold, including: in response to the target number being less than or equal to the target number threshold, determining that the fault type is a false detection fault type; in response to the target number being greater than the target number threshold, determining that the fault type is a true fault type.

[0057] In this embodiment, determining whether a motor controller fault can be cleared within a target number of times can be used as an effective method for determining the fault type (e.g., a true fault or a falsely detected fault). In determining the motor controller fault type based on the relationship between the target number of times and the target number of times threshold, the fault type can be determined to be a falsely detected fault type if the target number of times is less than or equal to the target number of times threshold; and the fault type can be determined to be a true fault type if the target number of times is greater than the target number of times threshold.

[0058] Alternatively, a false fault type may be caused by a transient environmental change (e.g., voltage fluctuation, electromagnetic interference, etc.) and can be cleared with a limited number of clearing attempts, thereby restoring normal functionality of the motor controller. A true fault type may indicate an irreversible hardware or software error in the motor controller that cannot be recovered by simple clearing attempts.

[0059] For example, suppose the target threshold number of times set for the vehicle at low speed is 5. The vehicle detects a false IGBT overcurrent fault while driving at low speed, attempts to clear the IGBT fault, and successfully clears the IGBT fault for the third time, returning to normal. In this case, the fault type can be determined to be a false detection fault. Suppose the target threshold number of times set for the vehicle at higher speed is 1. The same IGBT overcurrent fault is detected while driving at higher speed, and attempts to clear it are made. However, even after the predetermined one clearing attempt, the fault persists. In this case, the fault type can be determined to be a true fault.

[0060] As an optional embodiment, step S108 determines a target fault clearing strategy based on the fault type, including: in response to the fault type being a false detection fault type, detecting the electronic components in the motor controller to obtain detection results; based on the detection results, adjusting the electronic components to determine that the target fault clearing strategy represents a rule for clearing the electronic component fault.

[0061] In this embodiment, in the process of determining the target fault clearing strategy based on the fault type, when the fault type is a false detection fault type, the electronic components in the motor controller, such as the control chip and CPLD, can be inspected to obtain the inspection results; based on the inspection results, the electronic components are adjusted to determine the target fault clearing strategy to represent the rules for clearing the electronic component fault.

[0062] Optionally, if the fault type is a false positive, the electronic components in the motor controller can be tested. The stability of the sensor signal can also be tested to confirm whether there are signal fluctuations caused by external environmental interference. The continuity and stability of the hardware circuit can also be tested to ensure that there are no connection problems caused by temperature changes or other vibrations. Based on the test results, the parameters of the electronic components can be fine-tuned, such as adjusting the sensitivity threshold of the sensor to reduce false fault alarms. Alternatively, the hardware circuit can be optimized by adding a voltage stabilization circuit or electromagnetic shielding to reduce the impact of the external environment on the hardware circuit.

[0063] Optionally, after adjusting the electronic device based on the detection result, a target fault clearing strategy for the false detection fault type may be determined according to the adjustment result, for example, clearing the fault of the control chip or CPLD in the motor controller.

[0064] As an optional embodiment, the method further includes: in response to the fault type being a real fault type, determining that the target fault clearing strategy represents a rule for shutting down the motor controller.

[0065] In this embodiment, if the fault type is a true fault type, it means that the motor controller failure is caused by hardware damage, software errors, or other irreversible factors, rather than simply a false alarm caused by environmental factors. In this case, the motor controller can be shut down, making it inoperative, ensuring the safety of the driver and vehicle.

[0066] For example, if an IGBT fails and does not recover after reaching a preset maximum number of clearing cycles, the motor controller can be immediately shut down, disconnecting the circuits associated with the IGBT to ensure that no further damage is done to the motor controller.

[0067] As an optional embodiment, after determining the fault type of the motor controller based on the relationship between the target number of times and the target number threshold, the method also includes: in response to the fault type being a false detection fault type, sending a control signal of the motor controller to the vehicle, wherein the control signal is used to control the normal driving of the vehicle; in response to the fault type being a true fault type, controlling the motor controller to generate a prompt message, wherein the prompt message is used to prompt the vehicle to switch from normal driving to stop driving.

[0068] In this embodiment, after determining the motor controller fault type based on the relationship between the target number of times and the target number threshold, the vehicle can be controlled to drive normally or stop driving according to the different motor controller fault types. If the fault type is a false detection fault type, a control signal from the motor controller can be sent to the vehicle to control normal vehicle driving. If the fault type is a true fault type, the motor controller can be controlled to generate a prompt message to prompt the vehicle to switch from normal driving to stopping driving.

[0069] Optionally, when the fault type is confirmed to be a false detection fault type, a target fault clearing strategy (such as clearing control chip fault, CPLD fault, etc.) can be executed to clear the transient fault state of the electronic device. After successful clearing, a control signal can be sent to the vehicle's driving system, indicating that the motor controller has returned to normal and can control the vehicle to drive normally.

[0070] Optionally, if the fault type is confirmed to be a real fault type, that is, the motor controller fault cannot be cleared within the target threshold, then further attempts to clear the motor controller fault are stopped. At this time, the motor controller can generate specific prompt information, for example, display it to the driver through the vehicle's dashboard, prompting the driver to switch the vehicle from normal driving state to stopped driving state, turn off the power output, ensure that the vehicle is safely parked on the roadside, and wait for further maintenance.

[0071] In an embodiment of the present invention, in response to detecting an IGBT fault, the IGBT fault can be uploaded to the CPLD, and the IGBT fault can be latched and recorded by the CPLD. If the vehicle is in a stationary state at this time, the IGBT fault can be tried to be cleared until the user issues a start command. If the fault can be cleared before receiving the vehicle start signal, it means that the fault type is a false fault, and then other electronic components of the motor controller can be cleared, such as clearing the control chip fault first, then clearing the CPLD fault, and waiting for the vehicle to receive the start signal and then control the pulse width modulation (PWM) signal normally to control the vehicle to run normally. If the IGBT fault is not cleared before receiving the vehicle start signal, it means that the motor controller fault is a real fault, and the vehicle fault light can be turned on and the vehicle can be parked and wait for repairs.

[0072] Optionally, in response to detecting an IGBT fault, the IGBT fault can be uploaded to the CPLD, and the IGBT fault can be latched and recorded by the CPLD. If the vehicle is in a low-speed state at this time, the PWM signal can be controlled to turn off and enter a safe mode, such as the open circuit (OC) mode. After that, the IGBT fault can be cleared up to 10 times until the user issues a start command. If the fault can be cleared within 10 times or before the vehicle start signal is received, it means that the fault is a false fault, and the control chip fault is cleared first, and then the CPLD fault is cleared. However, since the fault will be recorded in the historical faults, after the fault is cleared, the safe mode is exited first, and then the PWM signal is normally controlled after the vehicle receives the start signal to control the vehicle to drive normally; if the fault is not cleared within 10 times or before the vehicle start signal is received, it means that the fault is a true fault, and the vehicle is parked and waiting for repairs.

[0073] Optionally, in response to detecting an IGBT fault, the IGBT fault can be uploaded to the CPLD, and the IGBT fault can be latched and recorded by the CPLD. If the vehicle is in a high speed state at this time, the PWM signal can also be controlled to be turned off and enter the OC mode. After that, the IGBT fault can be attempted to be cleared up to once until the user issues a start command. If the fault can be cleared within one time or before the vehicle start signal is received, it means that the fault is a false fault, and the control chip fault is cleared first, and then the CPLD fault is cleared. However, since the fault will be recorded in the historical faults, after the fault is cleared, the OC mode is exited first, and then the PWM signal is normally controlled after the vehicle receives the start signal to control the vehicle to drive normally. If the fault is not cleared within one time or before the vehicle start signal is received, it means that the fault is a true fault, and the OC mode is maintained and the vehicle is parked and waiting for repairs.

[0074] Optionally, in response to detecting an IGBT fault, the IGBT fault can be uploaded to the CPLD, which latches and records the IGBT fault. If the vehicle is in an extremely high speed state, it can enter Active Safety Control (ASC) mode. Afterwards, the IGBT fault can be cleared up to once. However, multiple fault clearing attempts can delay vehicle response. Long periods without control can cause a noticeable lag, which can be frightening for the user. Therefore, at high speeds, it is recommended to clear the fault only once, or increase the number of clearing attempts based on the duration of the fault clearing attempt without affecting the driving experience. If the fault can be cleared within one or fewer attempts, it indicates a false fault. The control chip fault should be cleared first, followed by the CPLD fault. However, the previous fault will be recorded in the fault history. In this case, ASC safety mode is exited and OC mode is entered. If the motor controller is fault-free, normal control and PWM signal generation will continue, controlling the vehicle's normal driving. If the fault cannot be cleared within one attempt, the vehicle's fault indicator should be illuminated, a high-voltage discharge should be performed, and ASC mode should be maintained until the vehicle's speed is sufficiently reduced, after which the vehicle should be pulled over and parked pending repairs.

[0075] As an optional embodiment, the method further includes: in response to the battery voltage of the motor controller being lower than a voltage threshold, powering the motor controller via a power battery, wherein the power battery includes two power supply paths.

[0076] In this embodiment, the normal operation of the motor controller relies on a stable power supply. If the battery voltage of the motor controller, such as the low-voltage battery voltage, falls below a voltage threshold, the motor controller cannot be powered. Therefore, a power battery, such as a high-voltage power battery, can be used to provide two power paths for powering the motor controller.

[0077] Alternatively, the low-voltage battery's voltage range is 3.2V-28V, while the motor controller's normal operating voltage range is 8-16V. Therefore, a significant portion of the low-voltage battery's voltage falls outside the motor controller's normal operating voltage range. Therefore, a backup power supply is designed as route 2 (Vout2). Vout2's output voltage is a stable 9V. When the low-voltage battery voltage falls below 9V, the backup power supply is used to prevent the motor controller from reporting an undervoltage fault.

[0078] Optionally, there are two power supply paths, one of which may be a path for generating power by an auxiliary winding of a transformer, and the other may be a bus voltage input power supply.

[0079] In an embodiment of the present invention, if a motor controller fault of a vehicle needs to be cleared, the vehicle's operating state information can be obtained when a motor controller fault is detected, wherein the operating state information is used to represent the operating state of the vehicle under the motor controller fault; a target number of times for clearing the motor controller fault can be determined based on the operating state information; the fault type of the motor controller fault can be determined based on the relationship between the target number of times and the target number of times threshold; a target fault clearing strategy can be determined based on the fault type, wherein the target fault clearing strategy is used to represent a rule for controlling the motor controller to clear the motor controller fault under the fault type; and the motor controller can be controlled to clear the motor controller fault according to the target fault clearing strategy. In an embodiment of the present invention, according to different operating states of the vehicle (e.g., stationary, low speed, high speed, ultra-high speed, etc.), the motor controller fault is cleared a target number of times, and according to the relationship between the target number of times and the target number of times threshold, it is determined whether the motor controller fault can be cleared, and whether the fault type of the motor controller fault is a true fault type or a false fault type, thereby specifically determining the target fault clearing strategy and clearing the motor controller fault, thereby solving the technical problem of low accuracy in clearing the motor controller fault of the vehicle and achieving the technical effect of improving the accuracy of clearing the motor controller fault of the vehicle.

[0080] The technical solutions of the embodiments of the present invention are described below with reference to preferred implementation methods.

[0081] Currently, the vehicle's electric drive system, as the power source for electric vehicles, is powered by both a high-voltage power battery and a low-voltage battery. For safety reasons, the vehicle's motor controller is usually equipped with a number of signal monitoring and protection functions, such as low-voltage battery over- and under-voltage monitoring, high-voltage power battery voltage sampling, over- and under-voltage protection, and passive and active discharge. When a motor controller function fails, in order to avoid hazards and risks, the motor controller can be put into a safe working state, gradually reducing the vehicle's speed and discharging the high voltage to a safe range (for example, below 60V). However, if the motor controller failure is not a true fault but a false trigger, then responding to the motor controller as if it were a true fault will bring harm and risks to the vehicle and driver.

[0082] In related technologies, vehicle fault detection often relies on direct voltage level determination, resulting in vehicle shutdown upon failure. This approach fails to adequately account for false detections of hardware faults (e.g., motor controller faults). During vehicle startup and driving, low-voltage fluctuations, electromagnetic interference, and other factors can cause hardware fault detection circuits to falsely detect faults. This can cause significant user distress and compromise safety, leading to the vehicle being shut down. Consequently, the accuracy of clearing motor controller faults remains a major technical issue.

[0083] The embodiment of the present invention proposes a method for clearing a fault of a motor controller of a vehicle. When a fault is detected in the motor controller, the current operating state of the vehicle is obtained, such as a stationary state, a low-speed state, a high-speed state, and an ultra-high-speed state. Thus, different fault clearing operations are performed under different operating states to determine whether the fault can be cleared. If the fault can be cleared, it indicates that the fault type of the motor controller of the vehicle is a false fault. At this time, the control chip fault can be cleared first, and then the CPLD fault can be cleared. After the vehicle receives the start signal, the PWM signal is normally controlled to control the vehicle to travel normally. If the fault is not cleared before the vehicle start signal is received, it indicates that the fault is a true fault. At this time, the vehicle fails to start, and the vehicle stops and waits for maintenance. Through the above method, false alarm faults caused by electronic component dispersion, high and low temperature environments, electromagnetic interference, etc. are avoided, and at the same time, malfunctions caused by false alarms that cause the vehicle to lose power unexpectedly are avoided, thereby improving the user's driving experience.

[0084] The following is a further introduction to the embodiments of the present invention.

[0085] Figure 2 FIG. 1 is a schematic diagram of a circuit diagram of a backup power supply according to an embodiment of the present invention, Figure 2 As shown, a high-voltage backup power solution is provided to provide power when the low-voltage voltage fluctuates. Figure 2 The front end of the circuit uses support capacitor C1 to prevent short voltage drops, absorbs high-voltage surges through transient overvoltage, and provides redundant backup power paths through paths D3 and D4. Path D3 generates power from the transformer's auxiliary winding, while path D4 receives the bus voltage input. Path 2 (Vout2) serves as a backup power source for the low-voltage battery. When the low-voltage battery voltage fluctuates and causes undervoltage, the high-voltage backup power source provides power, preventing undervoltage faults.

[0086] Optionally, Figure 2 Vout2, serving as a backup power source for the low-voltage battery, is converted from the high-voltage power battery through a specific circuit. This provides additional power to the motor controller, for example, when the low-voltage battery voltage drops to an unsafe level or insufficient to support normal operation of the motor controller due to various reasons (such as low temperature, aging, or instantaneous high current demand). Vout1 is the main output voltage of the motor controller during normal operation. It is directly supplied by the low-voltage battery or after preliminary regulation. It is the part of the motor controller that directly supplies the low-voltage power supply.

[0087] Optionally, Figure 2LV+ represents the positive low voltage or logic voltage, and LV represents the negative low voltage or negative low voltage terminal. L1 and L2 represent different input lines, with L1 being the main power supply and L2 being the auxiliary or backup power supply. This circuit conversion ensures that if the main power supply is unstable or fails, the motor controller can immediately switch to the backup power supply to maintain basic functions, thus preventing malfunctions caused by power problems. R1-R20 represent resistors. U1 and U2 represent integrated circuits. C2-C13 represent capacitors. V_in represents the input voltage or power input, such as the input voltage received from the low-voltage battery L_in. D1, D2, D5, and D6 represent diodes, respectively. T1 represents a transistor. VCC represents the positive power supply voltage in the circuit. D0 represents the first data line in the data bus.

[0088] Figure 3 FIG. 1 is a schematic diagram of a circuit diagram of a switching circuit of a backup power supply according to an embodiment of the present invention. Figure 3 As shown, L_in can be used to represent the voltage of the low-voltage battery, and the voltage range can be 3.2V-28V. The normal operating voltage range of the motor controller is 8V-16V. Therefore, a large part of the battery voltage is outside the voltage range that the motor controller can work normally. The backup power supply output is designed to be Vout2, and the output voltage of Vout2 can be a stable 9V. When the battery voltage is lower than 9V, the backup power supply is used.

[0089] Figure 4 is a flow chart of a control strategy method according to an embodiment of the present invention. Figure 4 As shown, the following steps are included:

[0090] Step S401 : In response to detecting an IGBT fault, the fault is uploaded to the CPLD for latching and recording.

[0091] In this embodiment, if an IGBT fault is detected, the fault is uploaded to the CPLD, and the fault is latched and recorded by the CPLD to facilitate later analysis of the fault.

[0092] Step S402: determine whether the vehicle is in a stationary state.

[0093] In this embodiment, if the vehicle is in a stationary state, that is, if the speed is determined to be 0 through speed monitoring, step S403 is executed; otherwise, step S408 is executed.

[0094] Step S403: clear the fault before receiving the vehicle start signal.

[0095] In this embodiment, if the vehicle is in a stationary state and the motor controller detects an IGBT fault, it may keep trying to clear the IGBT fault.

[0096] Step S404: determine whether the fault can be cleared.

[0097] In this embodiment, if the vehicle is stationary and the motor controller detects an IGBT fault, it may try to clear the IGBT fault and determine whether the fault can be cleared before receiving a vehicle start signal.

[0098] Step S405: clear the chip fault first, and then clear the CPLD fault.

[0099] In this embodiment, if the fault can be cleared before the vehicle start signal is received, it means that the fault is a false fault, and the chip (control chip) fault can be cleared first, and then the CPLD fault can be cleared.

[0100] Step S406 , waiting for the vehicle to receive the start signal and then controlling the PWM to drive the vehicle normally.

[0101] In this embodiment, the fault is a false fault, but the fault that has occurred will be recorded in the historical faults. It is possible to wait for the vehicle to receive the start signal and then control the PWM to run normally.

[0102] Step S407: When the vehicle start signal is received, the vehicle fault light is turned on, indicating that the vehicle fails to start.

[0103] In this embodiment, if the fault is not cleared before the vehicle start signal is received, it means that the fault is a real fault. Then, the vehicle fault light will be turned on when the vehicle start signal is received, and the vehicle will fail to start.

[0104] Step S408: Determine whether the vehicle is in a low speed state.

[0105] In this embodiment, if the vehicle is not in a stationary state, it can be determined whether the vehicle is in a low rotation speed state.

[0106] Step S409: turn off the PWM signal and enter the safe mode - OC mode.

[0107] In this embodiment, if the vehicle is in a low speed state, that is, the speed is lower than 100 rpm, if the motor controller detects an IGBT failure, it can control the PWM signal to be turned off and enter the safety mode - OC mode (all six switches of the three-phase full bridge are disconnected).

[0108] Step S410: Determine whether the fault can be cleared.

[0109] In this embodiment, if the vehicle is in a low speed state, if the motor controller detects an IGBT fault, it can try to clear the IGBT fault up to 10 times and determine whether the fault can be cleared before receiving the vehicle start signal.

[0110] Step S411: If the fault can be cleared within 10 times, the chip fault is cleared first, and then the CPLD fault is cleared.

[0111] In this embodiment, if the vehicle is in a low speed state and the fault can be cleared within 10 times, it means that the fault is a false fault and the chip fault can be cleared first and then the CPLD fault.

[0112] Step S412, exit the safety mode, and then wait for the vehicle to receive the start signal and then control the PWM normally, and the vehicle drives normally.

[0113] In this embodiment, if the vehicle is in a low speed state, after clearing the chip fault and CPLD fault, the safe mode can be exited, and the vehicle can be controlled to send PWM normally after receiving the start signal to control the vehicle to drive normally.

[0114] Step S413: If the fault cannot be cleared within 10 times, the vehicle fault light is turned on and the vehicle is parked on the side of the road.

[0115] In this embodiment, if the vehicle is in a low speed state and the fault cannot be cleared within 10 times, it means that the fault is a real fault, the vehicle will not respond to the vehicle start signal, and the vehicle fault light will be lit. The vehicle fails to start and stops at the spot waiting for repair.

[0116] Step S414: determine whether the vehicle is in a relatively high speed state.

[0117] In this embodiment, if the vehicle is neither stationary nor in a low speed state, it can be determined whether the vehicle is in a high speed state. A high speed state is defined as a speed greater than 100 rpm and less than 6000 rpm (6000 rpm is the speed threshold for entering ASC).

[0118] Step S415: Turn off the PWM signal and enter the safe mode - OC mode.

[0119] In this embodiment, if the vehicle is in a high speed state, if the motor controller detects an IGBT failure, it can control the PWM signal to be turned off and enter the safety mode - OC mode (all six switches of the three-phase full-bridge are disconnected).

[0120] Step S416: Determine whether the fault can be cleared.

[0121] In this embodiment, if the vehicle is operating at a high speed, you can attempt to clear the IGBT fault up to once to determine if the fault can be cleared. Because multiple fault clearing attempts can delay vehicle response and cause a noticeable pause when the vehicle is not under control for extended periods, this can be frightening to the user. Therefore, it is recommended to clear the fault only once at higher speeds, or increase the number of attempts based on the duration of the clearing attempt without affecting the driving experience.

[0122] Step S417: If the fault can be cleared within one time, the chip fault is cleared first, and then the CPLD fault is cleared.

[0123] In this embodiment, if the vehicle is in a relatively high speed state and the fault can be cleared within one time, it means that the fault is a false fault, and the chip fault can be cleared first, and then the CPLD fault can be cleared.

[0124] Step S418, exit the safety mode, and then wait for the vehicle to receive the start signal and then control the PWM normally, and the vehicle runs normally.

[0125] In this embodiment, if the vehicle is in a high speed state, after clearing the chip fault and CPLD fault, the safe mode can be exited, and then the vehicle can be controlled to send PWM normally after receiving the start signal to control the vehicle to drive normally.

[0126] Step S419: If the fault cannot be cleared within one time, the vehicle fault light will be turned on and the vehicle will be parked on the side of the road.

[0127] In this embodiment, if the vehicle is in a high speed state and the fault cannot be cleared within one time, it means that the fault is a real fault, then the fault light of the whole vehicle will be turned on and the vehicle will be parked on the side of the road.

[0128] Step S420: Determine whether the vehicle is in an ultra-high speed state.

[0129] In this embodiment, if the vehicle is neither stationary, nor in a low speed state, nor in a high speed state, it can be determined whether the vehicle is in an ultra-high speed state. A speed higher than 6000 rpm (6000 rpm is the speed threshold for entering ASC) can be defined as a high speed state.

[0130] Step S421, enter the safe ASC mode.

[0131] In this embodiment, the speed is determined by speed monitoring. At this time, if the motor controller detects an IGBT failure, it can enter the safety mode - ASC mode (the upper three bridge arms are fully closed, the lower three bridge arms are fully disconnected, or the lower three bridge arms are fully closed, the upper three bridge arms are fully disconnected).

[0132] Step S422: Determine whether the fault can be cleared.

[0133] In this embodiment, after entering the safe ASC mode, the IGBT fault can be cleared at most once to determine whether the fault can be cleared.

[0134] Step S423: If the fault can be cleared within one time, the chip fault is cleared first, and then the CPLD fault is cleared.

[0135] In this embodiment, if the vehicle is in an ultra-high speed state and the fault can be cleared within one time, it means that the fault is a false fault, and the chip fault can be cleared first, and then the CPLD fault can be cleared.

[0136] Step S424, exit the ASC safety mode and enter the OC mode first. If there is no fault, continue to control the PWM normally and the vehicle runs normally.

[0137] In this embodiment, if the vehicle is in an ultra-high speed state, after clearing the chip fault and CPLD fault, the ASC safety mode can be entered into the OC mode, and the normal control of PWM transmission can be continued to control the vehicle to run normally.

[0138] Step S425: If the fault cannot be cleared within one time, the vehicle fault light is turned on and the vehicle is parked on the side of the road.

[0139] In this embodiment, if the vehicle is in an ultra-high speed state and the fault cannot be cleared within one time, it means that the fault is a real fault. The fault light of the entire vehicle can be lit and high voltage discharge can be performed until the vehicle's speed is low enough and then it is pulled over and parked on the spot waiting for repairs.

[0140] In an embodiment of the present invention, according to different operating states of the vehicle (for example, stationary, low speed, high speed, ultra-high speed, etc.), the motor controller fault is cleared a target number of times, and according to the relationship between the target number and the target number threshold, it is determined whether the motor controller fault can be cleared, and it is judged whether the fault type of the motor controller fault is a real fault type or a false detection fault type, so as to determine the target fault clearing strategy in a targeted manner, and clear the motor controller fault, thereby solving the technical problem of low accuracy in clearing the vehicle's motor controller fault and achieving the technical effect of improving the accuracy of clearing the vehicle's motor controller fault.

[0141] According to an embodiment of the present invention, a device for clearing a motor controller fault in a vehicle is also provided. It should be noted that the device for clearing a motor controller fault in a vehicle can be used to execute the method for clearing a motor controller fault in a vehicle in the embodiment.

[0142] Figure 5 FIG. 1 is a schematic diagram of a device for clearing a motor controller fault in a vehicle according to an embodiment of the present invention. Figure 5 As shown, the apparatus 500 for clearing a motor controller fault of a vehicle may include: an acquisition unit 502 , a first determination unit 504 , a second determination unit 506 , a third determination unit 508 and a control unit 510 .

[0143] The acquisition unit 502 is configured to acquire the operating status information of the vehicle in response to detecting a motor controller failure, wherein the operating status information is used to indicate the operating status of the vehicle under the motor controller failure.

[0144] The first determining unit 504 is configured to determine a target number of times for clearing the motor controller fault based on the operating status information.

[0145] The second determining unit 506 is configured to determine a fault type of the motor controller fault based on a relationship between the target number of times and the target number threshold.

[0146] The third determining unit 508 is configured to determine a target fault clearing strategy based on the fault type, wherein the target fault clearing strategy is used to represent a rule for controlling the motor controller to clear the motor controller fault under the fault type.

[0147] The control unit 510 is configured to control the motor controller to clear the motor controller fault according to the target fault clearing strategy.

[0148] Optionally, the first determining unit 504 includes: a clearing module for clearing the motor controller fault based on the operating status information to obtain a clearing result; and a first determining module for determining a target number of times based on the clearing result.

[0149] Optionally, the second determination unit 506 includes: a second determination module, used to determine that the fault type is a false detection fault type in response to the target number being less than or equal to the target number threshold; and a third determination module, used to determine that the fault type is a true fault type in response to the target number being greater than the target number threshold.

[0150] Optionally, the third determination unit 508 includes: a detection module, which is used to detect the electronic components in the motor controller in response to the fault type being a false detection fault type, and obtain a detection result; a fourth determination module, which is used to adjust the electronic components based on the detection result, and determine that the target fault clearing strategy represents a rule for clearing the electronic component fault.

[0151] Optionally, the vehicle motor controller fault clearing device 500 further includes: a fourth determining unit, configured to determine, in response to the fault type being a true fault type, that the target fault clearing strategy represents a rule of shutting down the motor controller.

[0152] Optionally, after determining the fault type of the motor controller based on the relationship between the target number of times and the target number threshold, the vehicle's motor controller fault clearing device 500 also includes: a sending module for sending a control signal of the motor controller to the vehicle in response to the fault type being a false detection fault type, wherein the control signal is used to control the normal driving of the vehicle; a control module for controlling the motor controller to generate prompt information in response to the fault type being a true fault type, wherein the prompt information is used to prompt the vehicle to switch from normal driving to stop driving.

[0153] Optionally, the vehicle motor controller fault clearing device 500 further includes: a power supply unit for supplying power to the motor controller via a power battery in response to the battery voltage of the motor controller being lower than a voltage threshold, wherein the power battery includes two power supply paths.

[0154] In an embodiment of the present invention, in response to detecting a motor controller fault, the acquisition unit 502 acquires the operating status information of the vehicle, wherein the operating status information is used to indicate the operating status of the vehicle under the motor controller fault; the first determination unit 504 determines the target number of times for clearing the motor controller fault based on the operating status information; the second determination unit 506 determines the fault type of the motor controller fault based on the relationship between the target number and the target number threshold; the third determination unit 508 determines the target fault clearing strategy based on the fault type, wherein the target fault clearing strategy is used to indicate the rule for controlling the motor controller to clear the motor controller fault under the fault type; the control unit 510 controls the motor controller to clear the motor controller fault according to the target fault clearing strategy, thereby solving the technical problem of low accuracy in clearing the motor controller fault of the vehicle and achieving the technical effect of improving the accuracy in clearing the motor controller fault of the vehicle.

[0155] According to an embodiment of the present invention, a computer-readable storage medium is further provided. The storage medium includes a stored program, wherein the program executes the method for clearing a motor controller fault of a vehicle in the embodiment.

[0156] According to an embodiment of the present invention, a processor is further provided. The processor is configured to run a program, wherein the method for clearing a motor controller fault of a vehicle in the embodiment is executed when the program is run.

[0157] According to an embodiment of the present invention, a vehicle is further provided. The vehicle is used to execute the method for clearing a motor controller fault of a vehicle according to an embodiment of the present invention.

[0158] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0159] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0160] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0161] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0162] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0163] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk or optical disk, etc., various media that can store program code.

[0164] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for clearing a motor controller fault in a vehicle, characterized in that: include: In response to detecting the motor controller failure, obtaining operating state information of the vehicle, wherein the operating state information is used to indicate an operating state of the vehicle under the motor controller failure; determining a target number of times to clear the motor controller fault based on the operating status information; Determining a fault type of the motor controller fault based on a relationship between the target number of times and a target number threshold; Determining a target fault clearing strategy based on the fault type, wherein the target fault clearing strategy is used to represent a rule for controlling the motor controller to clear the motor controller fault under the fault type; According to the target fault clearing strategy, the motor controller is controlled to clear the motor controller fault.

2. The method according to claim 1, characterized in that Determining a target number of times to clear the motor controller fault based on the operating status information includes: Based on the operating status information, clear the motor controller fault to obtain a clearing result; Based on the clearing result, the target number of times is determined.

3. The method according to claim 1, characterized in that Determining a fault type of the motor controller based on a relationship between the target number of times and the target number threshold includes: In response to the target number being less than or equal to the target number threshold, determining that the fault type is a false detection fault type; In response to the target number being greater than the target number threshold, the fault type is determined to be a real fault type.

4. The method according to claim 3, characterized in that Based on the fault type, a target fault clearing strategy is determined, including: In response to the fault type being the false detection fault type, detecting electronic components in the motor controller to obtain a detection result; Based on the detection result, the electronic device is adjusted, and the target fault clearing strategy is determined to represent a rule for clearing the fault of the electronic device.

5. The method according to claim 3, characterized in that The method further comprises: In response to the fault type being the real fault type, determining that the target fault clearing strategy represents a rule for shutting down the motor controller.

6. The method according to claim 3, characterized in that After determining the fault type of the motor controller based on the relationship between the target number of times and the target number threshold, the method further includes: In response to the fault type being the false detection fault type, sending a control signal of the motor controller to the vehicle, wherein the control signal is used to control the vehicle to run normally; In response to the fault type being the real fault type, the motor controller is controlled to generate prompt information, wherein the prompt information is used to prompt the vehicle to switch from normal driving to stopped driving.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: In response to a battery voltage of the motor controller being lower than a voltage threshold, the motor controller is powered by a power battery, wherein the power battery includes two power supply paths.

8. A device for clearing a motor controller fault in a vehicle, characterized in that: include: an acquiring unit, configured to acquire, in response to detecting a fault in the motor controller, operating status information of the vehicle, wherein the operating status information is used to indicate an operating status of the vehicle under the fault in the motor controller; a first determining unit, configured to determine a target number of times for clearing the motor controller fault based on the operating status information; a second determining unit, configured to determine a fault type of the motor controller fault based on a relationship between the target number of times and a target number threshold; a third determining unit, configured to determine a target fault clearing strategy based on the fault type, wherein the target fault clearing strategy is used to represent a rule for controlling the motor controller to clear the motor controller fault under the fault type; A control unit is used to control the motor controller to clear the motor controller fault according to the target fault clearing strategy.

9. A processor, characterized in that: The processor is configured to run a program, wherein the program executes the method according to any one of claims 1 to 7 when running.

10. A vehicle, characterized in that: The vehicle is used to perform the method according to any one of claims 1 to 7.

Images