Fault detection method, device and equipment based on controller and readable storage medium

Abstract

The invention discloses a fault detection method, device and equipment based on a controller and a readable storage medium, and the method comprises the steps: carrying out the fault reset processing of the controller through employing a preset fault reset rule in response to a received fault reset instruction for carrying out the fault reset of the controller, and obtaining the controller after the fault reset processing, the preset fault reset rule comprises at least one driving fault reset strategy arranged according to a reset sequence; determining whether a fault event exists in the controller or not according to the acquired operation information of the controller subjected to the fault reset processing; in response to the presence of the fault event, it is determined that the controller has a fault. Therefore, the operation stability of the controller is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a controller-based fault detection method, electronic equipment and computer-readable storage medium. Background Art

[0002] The electric drive assembly is the core component of new energy vehicles, providing them with operating power. As the control unit of the electric drive assembly, the controller plays a major role in safety and stability. Fault detection and fault protection are important functions in terms of safety.

[0003] Traditional fault detection is mainly based on level judgment. If a fault signal is received, the vehicle will shut down immediately without considering the possibility of false fault detection. In addition, in the actual operation of the vehicle, the driver chip in the controller may report a driver fault due to harsh environmental conditions, interference with the controller wiring harness, poor contact of the connector, etc. The vehicle will immediately shut down and lose power, which seriously affects the driving comfort of the vehicle. Summary of the invention

[0004] The main technical problem solved by the present application is to provide a controller-based fault detection method, an electronic device and a computer-readable storage medium, which can improve the accuracy of fault detection.

[0005] In order to solve the above technical problems, a technical solution adopted in the present application is: a controller-based fault detection method is provided, the method comprising: in response to receiving a fault reset instruction for resetting the controller, performing fault reset processing on the controller using a preset fault reset rule to obtain a controller after the fault reset processing, the preset fault reset rule including at least one drive fault reset strategy arranged in a reset order; determining whether the controller has a fault event based on the obtained operating information of the controller after the fault reset processing; and in response to the existence of the fault event, determining that the controller has a fault.

[0006] In some embodiments, the preset fault reset rules include a first reset strategy for a drive fault and a second reset strategy for a drive fault arranged in a reset order. The step of, in response to receiving a fault reset instruction for the controller, performing fault reset processing on the controller using the preset fault reset rules to obtain a controller after the fault reset processing includes: in response to receiving a fault reset instruction for resetting the controller, performing a first fault reset processing on the controller based on the first reset strategy for the drive fault to obtain the controller after the first fault reset processing; in response to determining that a fault event exists in the controller according to the operating information of the controller after the first fault reset processing, performing a second fault reset processing on the controller based on the second reset strategy for the drive fault to obtain the controller after the fault reset processing.

[0007] In some embodiments, the first reset strategy for the drive fault includes at least one time of performing fault reset processing on the controller using a fault reset method, and the step of performing a first fault reset processing on the controller based on the first reset strategy for the drive fault in response to receiving a fault reset instruction for performing fault reset on the controller to obtain the controller after the first fault reset processing includes: in response to receiving a fault reset instruction for performing fault reset on the controller, obtaining a current fault reset result obtained by performing fault reset processing on the controller using the fault reset method; in response to the current fault reset result not meeting a preset reset requirement, performing a fault reset processing on the controller using the fault reset method to obtain the next fault reset result; in response to the next fault reset result meeting the preset reset requirement, obtaining the controller after the first fault reset fault processing.

[0008] In some embodiments, the fault reset instruction includes a drive axle fault reset signal, the fault reset mode includes a three-phase short circuit mode, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method further includes: in response to receiving a drive axle fault reset signal for performing fault reset on the controller, obtaining a current fault reset result obtained by performing fault reset processing on the controller using the three-phase short circuit mode; in response to the current fault reset duration being less than or equal to a first preset reset time and the current fault reset number being less than or equal to a first preset reset number, performing fault reset processing on the controller using the three-phase short circuit mode to obtain a next fault reset result, the next fault reset result including a next fault reset duration and a next fault reset number, the next fault reset number being accumulated based on the current fault reset number; in response to the next fault reset duration being greater than the first preset reset time and / or the next fault reset number being greater than the first preset reset number, obtaining a controller after the first fault reset fault processing.

[0009] In some embodiments, the fault reset instruction includes a drive undervoltage fault reset signal, the fault reset mode includes a shut-off reset mode, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method further includes: when the controller is in a first operating condition, in response to receiving a drive undervoltage fault reset signal for performing fault reset on the controller, obtaining a current fault reset result obtained by performing fault reset processing on the controller using the shut-off reset mode; in response to the current fault reset duration being less than or equal to a second preset reset time and the current fault reset number being less than or equal to a second preset reset number, performing fault reset processing on the controller using the shut-off reset mode to obtain a next fault reset result, the next fault reset result including a next fault reset duration and a next fault reset number, the next fault reset number being accumulated based on the current fault reset number; in response to the next fault reset duration being greater than the second preset reset time and / or the next fault reset number being greater than the second preset reset number, obtaining a controller after the first fault reset fault processing.

[0010] In some embodiments, the fault reset instruction includes a drive undervoltage fault reset signal, the fault reset method includes a shut-off reset method, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method also includes: when the controller is in a second operating condition, in response to receiving a drive undervoltage fault reset signal for performing a fault reset on the controller, the shut-off reset method is used to perform a fault reset process on the controller to obtain a current fault reset result; in response to the current fault reset duration being less than or equal to a third preset reset time, the shut-off reset method is used to perform a fault reset process on the controller to obtain a next fault reset result, and the next fault reset result includes a next fault reset duration; in response to the next fault reset duration being greater than the third preset reset time, a controller after the first fault reset fault process is obtained.

[0011] In some embodiments, the second reset strategy for the drive fault includes at least one time of performing fault reset processing on the controller by a restart reset method, and in response to determining that the controller has a fault event according to the operating information of the controller after the first fault reset processing, performing a second fault reset processing on the controller based on the second reset strategy for the drive fault to obtain the controller after the fault reset processing, the step includes: in response to determining that the controller has a fault event according to the operating information of the controller after the first fault reset processing, performing fault reset processing on the controller by the restart reset method, and obtaining a current restart reset result, wherein the current restart reset result includes a current restart number; in response to the current restart number being less than or equal to a preset restart number, performing a next fault reset processing on the controller by the restart reset method to obtain a next fault reset result, wherein the current restart reset result includes a next restart number; in response to the next restart number being greater than the preset restart number, obtaining the controller after the fault reset processing.

[0012] In order to solve the above technical problems, another technical solution adopted in the present application is: providing a controller-based fault detection device, the device includes a fault reset module, a judgment module and a fault determination module, the fault reset module is used to respond to receiving a fault reset instruction for resetting the controller, and adopt a preset fault reset rule to perform fault reset processing on the controller to obtain a controller after the fault reset processing, and the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; the judgment module is used to determine whether the controller has a fault event based on the obtained operating information of the controller after the fault reset processing; the fault determination module is used to determine that the controller has a fault in response to the existence of the fault event.

[0013] To solve the above technical problem, another technical solution adopted in the present application is: to provide an electronic device, including a memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the above fault detection method.

[0014] In order to solve the above technical problem, another technical solution adopted by the present application is: providing a computer-readable storage medium including program data stored therein, wherein the program data is used to implement the above fault detection method when executed by a processor.

[0015] Compared with the traditional method of receiving a fault signal and then stopping the whole vehicle, which results in low driving comfort for users, the above scheme provides a fault detection method based on a controller, which includes: in response to receiving a fault reset instruction for resetting the controller, performing fault reset processing on the controller using a preset fault reset rule to obtain a controller after the fault reset processing, wherein the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; determining whether there is a fault event in the controller based on the operation information of the controller after the fault reset processing; and determining that there is a fault in the controller in response to the presence of a fault event. Therefore, after receiving the fault reset instruction, the fault of the controller is reset using the preset fault reset rule. If the controller still fails to reset normally, it is determined that there is a fault in the controller, which can reduce the loss of power of the whole vehicle due to false detection of faults and improve the stability of operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0017] Figure 1 is a flowchart of an exemplary embodiment of a fault detection method shown in the present application;

[0018] Figure 2 yes Figure 1 A flow chart of an exemplary embodiment of step S110 in the fault detection method is shown;

[0019] Figure 3 is a schematic diagram of the fault signal transmission process shown in the present application;

[0020] Figure 4 It is a flowchart of an application scenario of the fault detection method shown in the present application;

[0021] Figure 5 is a flow chart of another application scenario of the fault detection method shown in the present application;

[0022] Figure 6 It is a flowchart of an application scenario of the second fault strategy shown in the present application;

[0023] Figure 7 is a schematic diagram of a framework of an exemplary embodiment of a fault detection method shown in the present application;

[0024] Figure 8 is a structural schematic diagram of an exemplary embodiment of a fault detection device shown in the present application;

[0025] Fig. 9 It is a structural schematic diagram of an embodiment of an electronic device provided by the present application;

[0026] Fig.10 It is a structural schematic diagram of an embodiment of a computer-readable storage medium provided by the present application. DETAILED DESCRIPTION

[0027] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It will be appreciated that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some but not all structures related to the present application are shown in the drawings. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the art without making creative work are within the scope of protection of the present application.

[0028] First of all, it should be noted that with the rapid development of the new energy vehicle industry, the market has shown a trend of sustained growth, and technology is also constantly improving and innovating. Today, more and more consumers regard new energy vehicles as an ideal choice for daily travel. Under this trend, people have higher expectations and requirements for the safety performance and ride comfort of new energy vehicles. Ensuring that vehicles can provide drivers and passengers with a safe and reliable experience and a pleasant and comfortable riding environment while providing environmental protection and energy saving has become the key to the further development of the industry.

[0029] During actual operation, occasional drive failures that can be recovered after power-off may occur. At this time, if the entire vehicle is shut down using traditional methods, it will seriously affect the driving comfort of the driver and passengers.

[0030] Based on this, this application proposes a controller-based fault detection method, electronic device and computer-readable storage medium, which can effectively reduce the frequency of vehicle shutdown due to drive failure and improve driving comfort. Figure 1 , Figure 1It is a flowchart of an exemplary embodiment of a fault detection method shown in the present application.

[0031] The execution subject of the fault detection method may be a terminal device or a server or other processing device, wherein the terminal device may be a user equipment (UE), a computer, a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. The execution subject of the fault detection method may also be a fault detection device. In some possible implementations, the fault detection method may be implemented by a processor calling a computer-readable instruction stored in a memory.

[0032] Specifically, the fault detection method of this embodiment includes the following steps:

[0033] S110: In response to receiving a fault reset instruction for resetting a controller, performing fault reset processing on the controller using a preset fault reset rule to obtain a controller after the fault reset processing, wherein the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order.

[0034] The controller can be the electric drive controller of a new energy vehicle. As the main component of the three-electric system of a new energy vehicle, it mainly provides power for the new energy vehicle. If a controller fails, it needs to be resolved in a timely manner to avoid further damage. The causes of the controller failure may include but are not limited to overheating, short circuit, unstable voltage, etc.

[0035] The fault reset instruction is used to instruct the controller to perform a fault reset. For example, when the internal circuit of the driver chip detects a fault event, it will output a driver fault level signal, which will be transmitted to the complex programmable logic device (CPLD) through the wiring harness. The CPLD processes the received driver fault level signal and feeds it back to the main chip (MCU). The MCU determines the preset fault reset rule based on the fault level signal fed back by the CPLD, and uses the preset fault reset rule to reset the controller. Among them, the fault event may include but is not limited to driver upper and lower bridge faults, driver undervoltage faults, etc.

[0036] The preset fault reset rule may be to perform fault reset processing on the controller with the fault event according to the reset sequence of the drive fault reset strategy. The preset fault rule may include at least one drive fault reset strategy. Exemplarily, the number of drive fault reset strategies in the preset fault rule may be 1, 2, 3, etc., and the multiple drive fault reset strategies may be the same or different.

[0037] The drive fault reset strategy is used to reset the fault of the controller. Exemplarily, the drive fault reset strategy may be to use at least one fault reset method to perform fault reset processing on the controller with a fault event. Exemplarily, the step of the fault detection device executing the drive fault reset strategy may be to repeatedly execute the same fault reset method until the fault reset is successful or the preset reset requirements are no longer met.

[0038] After receiving the fault reset instruction for resetting the controller, the fault detection device may first perform multiple repeated fault reset processing on the controller using the first fault reset method. If the number of repetitions reaches the preset reset number or the single fault reset processing time is greater than the preset reset time, the controller may be repeatedly reset using the second fault reset method to obtain a controller after the fault reset processing. It should be noted that after each fault reset processing of the controller using the fault reset method, the fault detection device will detect whether there is still a fault event in the controller. If not, the fault reset processing will no longer be performed, and the execution will continue according to the current control requirements of the vehicle, and the control operation information will continue to be obtained in real time to perform fault reset processing in a timely manner when a fault event occurs in the controller.

[0039] S120: Determine whether a fault event occurs in the controller according to the acquired operation information of the controller after the fault reset process.

[0040] The operation information refers to the operation status of the controller during operation, and may include the temperature, voltage, current, speed, etc. of the controller. For example, it may be obtained through an on-board diagnostic system or an on-board sensor of the vehicle.

[0041] A fault event refers to an event that occurs during the operation of the controller and causes the normal operation or performance degradation of the vehicle. Fault events can be caused by a variety of factors. For example, an IGBT short circuit, continuous high-load operation, voltage drop, loose or damaged electronic components in the controller, etc. As an example, a short circuit in a phase of the insulated gate bipolar transistor (IGBT) causes a sharp increase in current. When it increases to a certain value, the working state of the IGBT enters the saturation region from the linear region. At this time, there is a risk of burning out the power module, and the desaturation monitoring pin of the driver chip will rise to 5-7V. When the current is detected to be too large, the driver chip will actively pull down the voltage of the driver upper or lower bridge fault signal pin to send a driver upper or lower bridge fault signal to the CPLD; the CPLD processes the driver upper or lower bridge fault signal to obtain the corresponding fault event, and feeds the fault event back to the MCU, and the MCU performs fault reset processing according to the fault event.

[0042] S130: In response to a fault event, determining that a controller fault exists.

[0043] When the fault detection device detects that a fault event exists in the controller, it performs fault reset processing on the controller using at least one drive fault reset strategy arranged in a reset order to obtain a controller after the fault reset processing. At this time, the controller is detected again to see if there is still a fault event. If there is still a fault event, it means that the fault reset cannot be achieved through the preset fault reset rules. It is determined that the fault event is a real fault event, and the drive fault is reported, and the whole vehicle is shut down.

[0044] It can be seen that the controller-based fault detection method of the embodiment of the present application responds to receiving a fault reset instruction for resetting the controller, and uses a preset fault reset rule to perform fault reset processing on the controller to obtain a controller after the fault reset processing. The preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; it is determined whether the controller has a fault event based on the operation information of the controller after the fault reset processing; in response to the existence of a fault event, it is determined that the controller has a fault. Therefore, after receiving the fault reset instruction, the fault of the controller is reset by the preset fault reset rule. If the controller still fails to reset normally, it is determined that the controller has a fault, which can reduce the power loss of the whole vehicle due to false detection of faults and improve the stability of operation.

[0045] Based on the above embodiments, the embodiments of the present application adopt Figure 2 The flowchart details the preset fault reset rules, see Figure 2 , Figure 2 yes Figure 1 The flowchart of an exemplary embodiment of step S110 in the fault detection method is shown. Specifically, step S110 responds to receiving a fault reset instruction for the controller, performs fault reset processing on the controller using a preset fault reset rule, and the process of obtaining the controller after the fault reset processing may include the following steps:

[0046] S210: In response to receiving a fault reset instruction for resetting a controller, performing a first fault reset process on the controller based on a first drive fault reset strategy to obtain a controller after the first fault reset process.

[0047] In some embodiments, the preset fault reset rules include a first reset strategy for drive faults and a second reset strategy for drive faults arranged in order of reset. Exemplarily, the first reset strategy for drive faults can determine the corresponding drive fault reset strategy based on the fault event, and the second reset strategy for drive faults can also be determined based on the fault event. As an example, when a drive axle fault event occurs, the first reset strategy for drive faults can be set to a three-phase short circuit strategy, that is, at least once a three-phase short circuit method is used to perform fault reset processing on the controller; the second reset strategy for drive faults can be set to a restart reset strategy, that is, at least once a restart reset method is used to perform fault reset processing on the controller. Of course, in other embodiments, the preset fault reset rules can also include only one drive fault reset strategy, or include more than two drive fault reset strategies, which are not specifically limited here and can be set according to actual needs.

[0048] It can be understood that the second reset strategy for the driver fault in the preset fault reset rule is a conditionally executed driver fault reset strategy, and the second reset strategy for the driver fault will be executed only when the first reset strategy for the driver fault fails to achieve fault reset. The failure to achieve can mean that the first reset strategy for the driver fault fails to reset the controller fault within the preset reset time or the preset reset number of times. If the first reset strategy for the driver fault can successfully reset the controller fault, then exit the reset and continue to run.

[0049] Specifically, the first reset strategy for the drive fault includes at least one time of using a fault reset method to perform a fault reset process on the controller. In response to receiving a fault reset instruction for performing a fault reset on the controller, the current fault reset result obtained by performing a fault reset process on the controller using the fault reset method is obtained; in response to the current fault reset result not meeting a preset reset requirement, the fault reset process is performed on the controller using the fault reset method to obtain a next fault reset result; in response to the next fault reset result meeting the preset reset requirement, the controller after the first fault reset process is obtained.

[0050] Among them, the fault reset mode is used to reset the fault of the controller. Exemplarily, the fault reset mode can be determined according to different fault events. For example, if the fault event is a drive axle fault event, the fault reset mode can be a three-phase short circuit mode; if the fault event is a drive undervoltage fault event, the fault reset mode can be a shut-off reset mode, etc.

[0051] The current fault reset result includes the number of fault resets, fault reset time, and reset status of the controller, etc. The preset reset requirement can be that the number of fault resets using the fault reset method reaches the preset reset number, or the fault reset time of a single fault reset method reaches the preset reset time, or the controller drive fault has been reset.

[0052] It can be understood that the first reset strategy of the drive fault in this embodiment is a cyclic process, and when the cyclic condition is met, the loop is jumped out of the loop, and if it is not met, the loop is continued. Specifically, when the fault detection device receives the fault reset instruction of the controller to perform fault reset, it obtains the current fault reset result obtained by performing fault reset processing on the controller using the fault reset method; if the current fault reset result meets the preset reset requirement, the loop is jumped out to obtain the controller after the first fault reset processing; if the preset reset requirement is not met, the fault reset method is used to perform fault reset processing on the controller again to obtain the next fault reset result; if the next fault reset result meets the preset reset requirement, the loop is jumped out to obtain the controller after the first fault reset processing; if the preset reset requirement is not met, the fault reset method is used to perform fault reset processing on the controller again to obtain the next fault reset result. This cycle continues until the preset reset requirement is met.

[0053] In some embodiments, the fault reset instruction includes a drive axle fault reset signal, the fault reset mode includes a three-phase short circuit mode, and the current fault reset result includes the current fault reset duration and the current fault reset number; in response to receiving the drive axle fault reset signal for fault reset of the controller, the current fault reset result obtained by performing fault reset processing on the controller using the three-phase short circuit mode is obtained; in response to the current fault reset duration being less than or equal to the first preset reset time and the current fault reset number being less than or equal to the first preset reset number, the controller is fault reset by using the three-phase short circuit mode to obtain the next fault reset result, the next fault reset result includes the next fault reset duration and the next fault reset number, and the next fault reset number is accumulated based on the current fault reset number; in response to the next fault reset duration being greater than the first preset reset time and / or the next fault reset number being greater than the first preset reset number, the controller after the first fault reset fault processing is obtained. Thus, when a drive axle fault is found, the fault reset is first performed by the three-phase short circuit mode, and the fault reset is performed without affecting the normal driving of the vehicle, thereby improving the running stability.

[0054] The drive axle fault reset signal is a reset signal generated when a drive axle fault occurs. The transmission process of the fault signal and the fault reset command can be referred to Figure 3When a phase (including U phase, V phase and W phase) of the insulated gate bipolar transistor (IGBT) is short-circuited, the current increases sharply. When it increases to a certain value, the working state of the IGBT enters the linear region from the saturation region, and the power module is at risk of burning. The desaturation monitoring pin voltage of the driver chip will rise to 5-7V, and the voltage of the fault signal pin of the driver upper bridge or lower bridge will be pulled down at this time; the driver chip detects the fault signal of the driver upper bridge or lower bridge, and transmits it to the complex programmable logic device (CPLD) through the wiring harness. The CPLD chip processes the fault signal to obtain the corresponding fault event and feeds it back to the main chip (MCU). The main chip (MCU) determines the corresponding preset fault reset rule according to the received fault event, and generates a fault reset instruction, which is sent by the CPLD and the driver chip to the IGBT module. The driver fault reset instruction includes the driver bridge fault reset signal. The main chip can also control PWM and send the corresponding PWM to the CPLD, the driver chip and the IGBT module. Among them, PWM_UB and PWM_UT represent the lower bridge arm switch and the lower bridge arm switch of the U phase respectively.

[0055] After the fault monitoring device receives the reset signal of the drive axle fault, the drive axle fault reset signal includes a fault reset method corresponding to the drive axle fault event. Exemplarily, the fault reset method corresponding to the drive axle fault event can be a three-phase short circuit method. The three-phase short circuit method is also called active three-phase short circuit protection (Active Short Circuit, ASC), which is a safety measure used in motor drive systems to deal with fault conditions. The main purpose of ASC is to quickly reduce the energy level of the system by shorting the output of the inverter when a serious electrical fault is detected (such as an IGBT module failure or loss of control signal), thereby protecting key components from further damage.

[0056] For details, please refer to Figure 4After the fault detection device detects the fault signal of the driving upper bridge and the lower bridge, the controller is reset by a three-phase short circuit method to obtain the current fault reset result. The current fault reset result includes the current fault reset duration and the current fault reset times. The current fault reset times are accumulated based on the historical fault reset times. That is, when a drive axle fault event is detected, a fault reset is performed on it by a three-phase short circuit method to obtain the current fault reset result. At this time, the fault reset times are increased by 1. If the controller still has a drive axle fault event in the current fault reset result, it is determined whether the current fault reset times are greater than the first preset reset times and the current fault reset duration. Whether the time is greater than the first preset reset time; if the current fault reset duration is less than or equal to the first preset reset time and the current fault reset number is less than or equal to the first preset reset number, then enter the three-phase short circuit protection, continue to use the three-phase short circuit method to perform fault reset processing on the controller, and obtain the next fault reset result. At this time, the fault reset number continues to increase by 1; if the current fault reset duration is greater than the first preset reset time or the current fault reset number is greater than the first preset reset number, then exit the three-phase short circuit protection, obtain the controller after the first fault reset fault processing, and use the second reset strategy of the drive fault to reset the controller after the first fault reset fault processing. In this way, the judgment is continuously looped until the exit condition is met. The first preset reset number can be set to 20 times, and the first preset reset time can be set to 50ms. It should be noted that after each three-phase short circuit method is used to perform fault reset processing on the controller, the CPLD will accumulate the reset times, clear the judgment time, and only retain the fault reset duration of the current fault reset. When performing active three-phase short-circuit protection, the main chip controls the CPLD chip reset pin to clear the historical faults latched in the CPLD chip. After the drive fault signal level is pulled high, the state machine jumps to exit the three-phase short-circuit protection. After monitoring that there is no drive fault and the pipe can be opened normally, it continues to execute according to the current control requirements of the vehicle, thereby making the controller run in safe mode.

[0057] It should be noted that the prerequisite for using the three-phase short-circuit method to reset the controller fault in this embodiment is to receive the drive axle fault reset signal for resetting the controller fault. If no signal is received, it means that the controller fault has been reset, and there is no need to use the three-phase short-circuit method to reset the fault.

[0058] In other embodiments, the fault reset instruction includes an undervoltage fault reset signal, the fault reset method includes a shut-off reset method, and the current fault reset result includes the current fault reset duration and the current fault reset number; when the controller is in the first operating condition, in response to receiving a driving undervoltage fault reset signal for resetting the controller, the current fault reset result obtained by performing fault reset processing on the controller using the shut-off reset method is obtained; it is determined whether the current fault reset duration is less than or equal to the second preset reset time and whether the current fault reset number is less than or equal to the second preset reset number; if the current fault reset duration is less than or equal to the second preset reset time and the current fault reset number is less than or equal to the second preset reset number, the controller is fault reset using the shut-off reset method to obtain the next fault reset result, the next fault reset result includes the next fault reset duration and the next fault reset number, and the next fault reset number is accumulated based on the current fault reset number; in response to the next fault reset duration being greater than the second preset reset time and / or the next fault reset number being greater than the second preset reset number, the controller after the first fault reset fault processing is obtained. Therefore, when a driver undervoltage fault event occurs, a shutdown reset method is used to reset the fault, thereby preventing the driver chip from working unstably and causing uncontrollable PWM (Pulse Width Modulation) waves when a driver undervoltage fault event occurs.

[0059] The operating condition refers to how the controller works to meet the power requirements of the vehicle under different driving conditions and load conditions. Some typical operating conditions include starting conditions, normal driving conditions, low-speed driving conditions, parking conditions, idling conditions, etc. The first operating condition can be a normal driving condition, a low-speed driving condition, etc. The second operating condition can be a parking condition.

[0060] The current fault reset duration refers to the duration of a single shutdown reset. The current fault reset times are accumulated based on the historical fault reset times. The current fault reset times and historical fault reset times are based on the CPLD latched historical faults. It should be noted that each time the controller is reset by the shutdown reset method, the CPLD will accumulate the reset times, clear the judgment time, and only retain the fault reset duration of the current fault reset.

[0061] The driver undervoltage fault reset signal is a reset signal generated when a driver undervoltage fault event occurs. The transmission process of the fault signal and the fault reset instruction can be found in Figure 3When the gate turn-on voltage of the insulated gate bipolar transistor (IGBT) is insufficient, the on-resistance of the IGBT will increase, resulting in greater power loss. At this time, the temperature of the IGBT will rise, which may cause it to burn out. When the voltage of the secondary-side desaturation detection pin of the driver chip to the ground is detected to be lower than 9.9V, the voltage of the driver undervoltage fault signal pin is pulled low; the driver chip detects the driver undervoltage fault signal and transmits it to the complex programmable logic device (CPLD) through the wiring harness. The CPLD chip processes the fault signal to obtain the corresponding fault event and feeds it back to the main chip (MCU). The main chip (MCU) determines the corresponding preset fault reset rule according to the received fault event and generates a fault reset instruction, which is sent by the CPLD and the driver chip to the IGBT module. The driver fault reset instruction includes the driver undervoltage fault reset signal.

[0062] After the fault monitoring device receives the driver undervoltage fault reset signal, the driver undervoltage fault reset signal includes a fault reset method corresponding to the driver undervoltage fault event. Exemplarily, the fault reset method corresponding to the drive bridge fault event can be a gate reset method. Gate reset protection (GRP) is a safety mechanism used in power electronic equipment, especially in motor drive systems, to protect power semiconductor switches (such as IGBTs or MOSFETs) from damage. This protection measure is usually activated when an abnormal situation is detected, preventing further damage by forcibly closing all switches and ensuring that they are in a safe state.

[0063] It should be noted that the prerequisite for using the shut-off reset method to reset the controller fault in this embodiment is to receive the drive axle fault reset signal for resetting the controller fault. If no signal is received, it means that the controller fault has been reset, and there is no need to use the shut-off reset method to reset the fault.

[0064] When the controller is in the second operating condition, in response to receiving a drive undervoltage fault reset signal for resetting the controller, the controller is reset by a shut-off reset method to obtain a current fault reset result; in response to the current fault reset duration being less than or equal to a third preset reset time, the controller is reset by a shut-off reset method to obtain a next fault reset result, and the next fault reset result includes a next fault reset duration; in response to the next fault reset duration being greater than the third preset reset time, the controller after the first fault reset fault processing is obtained.

[0065] When the controller is in the second operating condition, the number of fault resets using the shut-off reset method may not be limited. For example, the second operating condition may be a parking condition, in which case multiple resets using the shut-off reset method do not affect the normal operation of the vehicle. In addition, the third preset reset time when the controller is in the second operating condition may be higher than the second preset reset time when the controller is in the first operating condition. For example, the second preset reset time may be set to 50ms, and the third preset reset time may be set to 1s.

[0066] As an example, see Figure 5 After the fault detection device detects the drive undervoltage fault signal, it determines whether the current controller is in a parking condition. If it is in a parking condition, the controller is reset by using a closed-tube reset method to obtain the current fault reset result. The current fault reset result includes the current fault reset duration. It is determined whether the current fault reset duration is greater than the third preset reset time. If it is greater, the closed-tube reset protection is exited and the second reset strategy for the drive fault is executed. If it is less than or equal to the third preset reset time, the closed-tube reset protection is continued to be entered. At this time, the number of fault resets continues to increase by 1. If the current controller is not in a parking condition, the controller is reset by using a closed-tube reset method to obtain the current fault reset result. The current fault reset result includes the current fault reset duration and the current Fault reset times, judge whether the current fault reset times are greater than the second preset reset times and whether the current fault reset duration is greater than the second preset reset time; if the current fault reset duration is less than or equal to the second preset reset time and the current fault reset times are less than or equal to the second preset reset times, enter the shutdown reset protection, continue to use the shutdown reset method to perform fault reset processing on the controller, and obtain the next fault reset result, at this time the fault reset times continue to increase by 1; if the current fault reset duration is greater than the second preset reset time or the current fault reset times are greater than the second preset reset times, exit the shutdown reset protection, obtain the controller after the first fault reset fault processing, and use the second reset strategy of the drive fault to reset the controller after the first fault reset fault processing. In this way, the judgment is continuously looped until the exit condition is met.

[0067] S220: In response to determining that a fault event exists in the controller according to the operation information of the controller after the first fault reset process, a second fault reset process is performed on the controller based on the second reset strategy for the drive fault to obtain a controller after the fault reset process.

[0068] The fault detection device determines that the controller has a fault event based on the operation information of the controller after the first fault reset process. The fault event is consistent with the fault event detected initially. Specifically, if the fault detection device receives a drive axle fault reset signal for resetting the controller, after resetting the fault through the first reset strategy for the drive fault, the controller after the first fault reset process is obtained. At this time, based on the operation information of the controller after the first fault reset process, it is determined that the controller still has a drive axle fault reset signal, and then the controller is subjected to a second fault reset process based on the second reset strategy for the drive fault, to obtain the controller after the fault reset process.

[0069] In some embodiments, the second reset strategy for the driver fault includes at least one use of a restart reset method to perform a fault reset process on the controller; in response to determining that a fault event exists in the controller according to the operating information of the controller after the first fault reset process, the current restart reset result obtained by performing a fault reset process on the controller using the restart reset method is obtained, and the current restart reset result includes the current restart number; in response to the current restart number being less than or equal to the preset restart number, the next fault reset process is performed on the controller using the restart reset method to obtain the next fault reset result, and the current restart reset result includes the next restart number; in response to the next restart number being greater than the preset restart number, the controller after the fault reset process is obtained. Thus, the restart reset method is used as the second layer of barrier, and after the first layer of driver fault reset strategy fails, the driver fault is not reported first, and the fault is reported after the restart reset strategy fails, thereby reducing the possibility of false detection.

[0070] The restart reset method can include the following steps, please refer to Figure 6 :The main chip controls the power supply enable signal of the driver board, sends a low-level control to power off the driver board, turns off the power of the driver board, and then sends a high-level control to power on the driver board and turns on the power of the driver board. Because it takes time to power on the driver board, the power-on waiting state is maintained, and the count of the number of times the driver board is restarted is increased by 1. At this time, it is detected whether a fault event exists. If not, the driver board is restarted and reset successfully. If a fault exists, it is determined whether the number of restarts is less than the preset number of restarts. If so, the restart reset method is re-executed until the number of restarts is greater than or equal to the preset number of restarts and the fault is reported.

[0071] In order to elaborate on the fault detection method of the present application, Figure 7 The framework diagram shown further illustrates it, as follows:

[0072] First, the drive fault level signal is obtained, and the drive fault level signal is analyzed to determine the specific fault event; if the fault event is a drive axle fault event, the three-phase short circuit method (ASC reset) is used for fault reset processing. If the fault reset is successful, the three-phase short circuit protection is jumped out, and the number of fault resets and the count are cleared. Reset the normal control state according to a certain slope, and continue to follow the vehicle control command to drive; if the fault is not reset successfully, the condition for unsuccessful reset may be that the current fault reset duration is greater than the first preset reset time or the current fault reset number is greater than the first preset fault reset number, then the restart reset method is used to restart the controller's drive board. If the fault reset is successful, the fault reset operation is jumped out, and the current control requirements of the vehicle are continued to be executed and the controller operation information is continuously monitored; if the fault is not reset successfully, it is determined that the controller is faulty and the vehicle is shut down. If the fault event is a drive undervoltage fault event, the fault reset process is performed by closing the pipe and resetting the fault. If the fault reset is successful, the pipe is opened normally, and the execution continues according to the current control requirements of the whole vehicle and the controller operation information is continuously monitored. If the fault is not reset successfully, there are different judgment conditions for determining whether the reset is successful under different operating conditions. The condition for failure to reset under driving conditions may be that the current fault reset duration is greater than the first preset reset time or the current fault reset number is greater than the first preset fault reset number. The condition for failure to reset under parking conditions may be that the current fault reset duration is greater than the first preset reset time. If the reset is not successful, the restart reset method is used to restart the driver board of the controller. If the fault reset is successful, the fault reset operation is no longer performed, and the execution continues according to the current control requirements of the whole vehicle and the controller operation information is continuously monitored. If the fault is not reset successfully, it is determined that there is a fault in the controller and the whole vehicle is shut down.

[0073] See also Figure 8 It is a structural diagram of an exemplary embodiment of a fault detection device shown in the present application. The fault detection device 800 includes a fault reset module 810, a judgment module 820 and a fault determination module 830. The fault reset module 810 is used to respond to receiving a fault reset instruction for resetting the controller, and use a preset fault reset rule to perform a fault reset process on the controller to obtain a controller after the fault reset process. The preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; the judgment module 820 is used to determine whether the controller has a fault event based on the operation information of the controller after the fault reset process; the fault determination module 830 is used to determine that the controller has a fault in response to the existence of a fault event.

[0074] In the above scheme, the fault detection device of the embodiment of the present application responds to receiving a fault reset instruction for resetting the controller, and uses a preset fault reset rule to perform fault reset processing on the controller to obtain a controller after the fault reset processing, and the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; determines whether the controller has a fault event based on the operation information of the controller after the fault reset processing; and determines that the controller has a fault in response to the presence of a fault event. Therefore, after receiving the fault reset instruction, the fault of the controller is reset by using the preset fault reset rule. If the controller still fails to reset normally, it is determined that the controller has a fault, which can reduce the loss of power of the whole vehicle due to false detection of faults and improve the stability of operation.

[0075] The functions of each module can be found in the fault detection method embodiment, which will not be described in detail here.

[0076] In order to implement the fault detection method of the above embodiment, the present application proposes another electronic device, which can be seen in detail in Fig. 9 , Fig. 9 It is a structural schematic diagram of an embodiment of an electronic device provided by the present application.

[0077] The electronic device 900 includes a memory 910 and a processor 920 , wherein the memory 910 and the processor 920 are coupled.

[0078] The memory 910 is used to store program data, and the processor 920 is used to execute the program data to implement the fault detection method of the above embodiment.

[0079] In this embodiment, the processor 920 may also be referred to as a CPU (Central Processing Unit). The processor 920 may be an integrated circuit chip having signal processing capabilities. The processor 920 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor or the processor 920 may also be any conventional processor, etc.

[0080] The present application also provides a computer-readable storage medium, such as Fig.10 As shown, the computer-readable storage medium 1000 is used to store program data 1001. When the program data 1001 is executed by the processor, it is used to implement the fault detection method in the method embodiment of the present application.

[0081] The method involved in the embodiment of the fault detection method of the present application, when implemented in the form of a software functional unit and sold or used as an independent product, can be stored in a device, such as a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially 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, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk.

[0082] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A controller-based fault detection method, characterized in that: The controller-based fault detection method includes: In response to receiving a fault reset instruction for resetting the controller, performing fault reset processing on the controller using a preset fault reset rule to obtain a controller after the fault reset processing, wherein the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; Determining whether a fault event occurs in the controller according to the acquired operation information of the controller after the fault reset process; In response to the presence of the fault event, it is determined that the controller is faulty.

2. The controller-based fault detection method according to claim 1, characterized in that: The preset fault reset rule includes a first reset strategy for a drive fault and a second reset strategy for a drive fault arranged in a reset order. In response to receiving a fault reset instruction for the controller, the preset fault reset rule is used to perform fault reset processing on the controller to obtain a controller after the fault reset processing, including: In response to receiving a fault reset instruction for performing fault reset on the controller, performing a first fault reset process on the controller based on the first drive fault reset strategy to obtain a controller after the first fault reset process; In response to determining that a fault event exists in the controller according to the operation information of the controller after the first fault reset processing, a second fault reset processing is performed on the controller based on the second drive fault reset strategy to obtain the controller after the fault reset processing.

3. The controller-based fault detection method according to claim 2, characterized in that: The first reset strategy for the drive fault includes performing a fault reset process on the controller in a fault reset manner at least once, and the step of performing a first fault reset process on the controller based on the first reset strategy for the drive fault in response to receiving a fault reset instruction for performing a fault reset on the controller to obtain the controller after the first fault reset process includes: In response to receiving a fault reset instruction for performing fault reset on the controller, obtaining a current fault reset result obtained by performing fault reset processing on the controller using the fault reset method; In response to the current fault reset result not meeting the preset reset requirement, the controller is subjected to fault reset processing using the fault reset method to obtain a next fault reset result; In response to the next fault reset result satisfying the preset reset requirement, a controller after the first fault reset fault processing is obtained.

4. The controller-based fault detection method according to claim 3, characterized in that: The fault reset instruction includes a drive axle fault reset signal, the fault reset mode includes a three-phase short circuit mode, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method further includes: In response to receiving a drive axle fault reset signal for resetting the controller, obtaining a current fault reset result obtained by performing fault reset processing on the controller in the three-phase short-circuit manner; In response to the current fault reset duration being less than or equal to the first preset reset time and the current fault reset number being less than or equal to the first preset reset number, the controller is subjected to fault reset processing in the three-phase short circuit manner to obtain a next fault reset result, the next fault reset result including a next fault reset duration and a next fault reset number, the next fault reset number being accumulated based on the current fault reset number; In response to the next fault reset duration being greater than the first preset reset time and / or the next fault reset number being greater than the first preset reset number, a controller after the first fault reset fault processing is obtained.

5. The controller-based fault detection method according to claim 3, characterized in that: The fault reset instruction includes a drive undervoltage fault reset signal, the fault reset mode includes a shut-off reset mode, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method further includes: When the controller is in the first operating condition, in response to receiving a drive undervoltage fault reset signal for resetting the controller, a current fault reset result is obtained by performing fault reset processing on the controller using the shutdown reset method; In response to the current fault reset duration being less than or equal to the second preset reset time and the current fault reset number being less than or equal to the second preset reset number, the controller is subjected to fault reset processing by adopting the shut-off reset mode to obtain a next fault reset result, the next fault reset result including the next fault reset duration and the next fault reset number, the next fault reset number being accumulated based on the current fault reset number; In response to the next fault reset duration being greater than the second preset reset time and / or the next fault reset number being greater than the second preset reset number, a controller after the first fault reset fault processing is obtained.

6. The controller-based fault detection method according to claim 3, characterized in that: The fault reset instruction includes a drive undervoltage fault reset signal, the fault reset mode includes a shut-off reset mode, the current fault reset result includes a current fault reset duration and a current fault reset number, and the method further includes: When the controller is in the second operating condition, in response to receiving a drive undervoltage fault reset signal for resetting the controller, the controller is reset by using the shut-off reset method to obtain a current fault reset result; In response to the current fault reset duration being less than or equal to a third preset reset time, the controller is subjected to fault reset processing by adopting the switch-off reset mode to obtain a next fault reset result, wherein the next fault reset result includes a next fault reset duration; In response to the next fault reset duration being greater than the third preset reset time, a controller after the first fault reset fault processing is obtained.

7. The controller-based fault detection method according to claim 2, characterized in that: The second reset strategy for the drive fault includes at least one step of performing a fault reset process on the controller by a restart reset mode, and in response to determining that a fault event exists in the controller according to the operation information of the controller after the first fault reset process, performing a second fault reset process on the controller based on the second reset strategy for the drive fault to obtain the controller after the fault reset process, comprising: In response to determining that a fault event exists in the controller according to the operation information of the controller after the first fault reset process, obtaining a current restart and reset result obtained by performing fault reset process on the controller in the restart and reset manner, wherein the current restart and reset result includes a current restart number; In response to the current restart number being less than or equal to the preset restart number, the controller is subjected to the next fault reset process using the restart reset mode to obtain a next fault reset result, wherein the current restart reset result includes the next restart number; In response to the next restart number being greater than the preset restart number, a controller after the fault reset process is obtained.

8. A controller-based fault detection device, characterized in that: The device comprises: a fault reset module, configured to, in response to receiving a fault reset instruction for resetting the controller, perform fault reset processing on the controller using a preset fault reset rule to obtain a controller after the fault reset processing, wherein the preset fault reset rule includes at least one drive fault reset strategy arranged in a reset order; A judgment module, used for determining whether a fault event occurs in the controller according to the acquired operation information of the controller after the fault reset process; The fault determination module is configured to determine that a fault exists in the controller in response to the presence of the fault event.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: include: Program data is stored, and when the program data is executed by a processor, it is used to implement the method according to any one of claims 1 to 7.

Images