Fault protection method and device for motor controller, and electronic equipment

By obtaining the fault information of the motor controller and selecting the appropriate safety status for fault protection, the problem of insufficient fault protection methods in the existing technology is solved, and multiple ways of protection of the motor controller is realized, and the timeliness of fault feedback is improved. and security.

CN119078526APending Publication Date: 2024-12-06GAC AION NEW ENERGY AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411185943.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

When faced with multiple faults, the existing motor controllers are not rich enough to effectively protect the hardware, and the safety status selection is not flexible enough to take into account driving comfort and system stability.

Method used

By obtaining the fault information of the motor controller, selecting multiple safety states for fault protection according to different fault conditions, including judging the status of the drive circuit, control unit and relay, selecting the appropriate safety state to protect the hardware, and performing according to the fault type and vehicle status Refine adjustments.

Benefits of technology

It realizes fault protection in multiple ways and methods during the operation of the motor controller, improves the timeliness of fault feedback and the flexibility of safe state, and ensures the stable operation and driving comfort of the motor controller.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119078526A_ABST
    Figure CN119078526A_ABST
Patent Text Reader

Abstract

The invention provides a fault protection method and device for a motor controller, electronic equipment and a storage medium, and the method comprises the steps: obtaining fault information of the motor controller; when the fault information shows that the driving circuit of the motor controller is normal, selecting a first safety state or a second safety state to carry out fault protection; when the fault information shows that the control unit of the motor controller is normal, selecting a third safety state to carry out fault protection; and when the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor, selecting a fourth safety state to carry out fault protection. By implementing the application, a fault protection state can be entered through multiple ways, hardware is effectively protected, feedback after a fault occurs is more timely, selection of a safety state is more flexible and changeable, and safety in the operation process of the motor controller can be considered.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of motor control technology, and in particular to a fault protection method, device, electronic device and storage medium for a motor controller. Background Art

[0002] The control of the motor controller is an important process in vehicle driving. It can improve the safety performance of the vehicle drive system, avoid safety accidents and respond to faults in a timely manner. Therefore, the fault protection measures of the motor controller are particularly important. The existing technical strategy can select the fault state and path to be entered by the electric drive system according to the fault state of the electric drive system and the operation of the whole vehicle, effectively protecting the hardware of the electric drive system and improving driving comfort.

[0003] However, the existing technology does not have enough ways to enter the fault state, and cannot effectively protect the electric drive hardware when two faults occur at the same time. The way to enter the safe state is not flexible enough and cannot take into account driving comfort. The selected safe state cannot effectively alleviate the system's fault state. Summary of the invention

[0004] The purpose of this application is to provide a fault protection method, device, electronic device and storage medium for a motor controller, which can enter the fault protection state through multiple ways, effectively protect the hardware, provide more timely feedback after a fault occurs, and make the selection of safe states more flexible and varied, so as to take into account the safety of the motor controller during operation.

[0005] In a first aspect, an embodiment of the present application provides a fault protection method for a motor controller, the method comprising:

[0006] Obtaining fault information of the motor controller;

[0007] When the fault information shows that the driving circuit of the motor controller is normal, selecting the first safety state or the second safety state for fault protection;

[0008] When the fault information shows that the control unit of the motor controller is normal, selecting the third safety state for fault protection;

[0009] When the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor, the fourth safety state is selected for fault protection.

[0010] In the above implementation process, a variety of different safety states are selected according to the fault information, and the fault protection state can be entered through a variety of channels to effectively protect the hardware. The feedback after the fault occurs is more timely, and the selection of safety states is more flexible and changeable, which can take into account the safety of the motor controller during operation.

[0011] Furthermore, the step of selecting the fourth safety state for fault protection includes:

[0012] Determine whether the motor controller has a driving abnormality;

[0013] If so, performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state;

[0014] If not, perform fault protection according to the relay status.

[0015] In the above implementation process, different methods are selected for fault protection according to whether there is a driving abnormality in the motor controller, so that the motor controller can be protected in multiple ways and channels during operation, which is conducive to maintaining the stability of the motor controller.

[0016] Furthermore, the step of performing fault protection according to the relay state includes:

[0017] Determining whether the main relay is disconnected according to the relay state;

[0018] If so, performing fault protection according to the first state of the driving chip of the motor controller;

[0019] If not, fault protection is performed according to the second state of the driving chip of the motor controller.

[0020] In the above implementation process, different fault protection methods are selected according to whether the main relay is disconnected, which can protect the main relay so that the main relay can maintain stable operation when a fault occurs, thereby minimizing damage to the hardware.

[0021] Furthermore, the step of performing fault protection according to the first state of the driving chip of the motor controller includes:

[0022] The first state of the driver chip of the motor controller is that both the upper bridge driver chip and the lower bridge driver chip cannot be normally controlled, and it is determined whether the upper bridge driver chip is completely disconnected and the lower bridge driver chip is fully turned on;

[0023] If so, performing fault protection on the motor controller according to the third sub-safety state in the fourth safety state;

[0024] If not, determine whether the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on. If the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on, perform fault protection on the motor controller according to the second sub-safety state in the fourth safety state. If the lower bridge driver chip is not fully disconnected or the upper bridge driver chip is not fully turned on, perform fault protection on the motor controller according to the first sub-safety state in the fourth safety state.

[0025] In the above implementation process, fault protection is performed according to the first state of the driver chip of the motor controller, and the state of the driver chip is refined, so that the fault condition of the motor controller can be measured in multiple dimensions and refined fault adjustment can be achieved.

[0026] Furthermore, the step of performing fault protection according to the second state of the driving chip of the motor controller includes:

[0027] The second state of the driver chip of the motor controller is that the upper bridge driver chip or the lower bridge driver chip cannot be normally controlled, and it is determined whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is completely turned on;

[0028] If yes, determine whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is under normal control; if the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is under normal control, perform fault protection on the motor controller according to the fifth sub-safety state in the fourth safety state;

[0029] If not, determine whether the lower bridge driver chip of the motor controller is completely disconnected and the upper bridge driver chip is under normal control; if the lower bridge driver chip of the motor controller is completely disconnected and the upper bridge driver chip is under normal control, perform fault protection on the motor controller according to the fourth sub-safety state in the fourth safety state; if the lower bridge driver chip of the motor controller is not completely disconnected or the upper bridge driver chip is not under normal control, perform fault protection according to the first state of the driver chip of the motor controller.

[0030] In the above implementation process, fault protection is performed according to the second state of the driver chip of the motor controller to implement fault protection outside the first state, further dividing the possible faults of the driver chip into multiple aspects to improve the protection capability of the driver chip.

[0031] Furthermore, before the step of performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state, the method further includes:

[0032] Fault protection is performed according to the fault type.

[0033] In the above implementation process, the fault protection method is selected more accurately according to the fault type, so that the motor controller can be protected from faults faster and more efficiently.

[0034] Furthermore, the step of performing fault protection according to the fault type includes:

[0035] When the fault type is over-high voltage, determine whether the vehicle is stationary, if so, determine whether the current vehicle speed is low, if the current vehicle speed is low, enter the third safety state for fault protection, if the current vehicle speed is high, enter the first sub-safety state in the fourth safety state for fault protection, if not, perform fault protection according to the voltage recovery situation;

[0036] When the fault type is overcurrent, determine whether the current vehicle speed is low speed, if the current vehicle speed is low speed, enter the third safety state for fault protection, if the current vehicle speed is high speed, enter the first sub-safety state in the fourth safety state for fault protection;

[0037] When the fault type is a drive abnormality, it is determined whether it is a self-fault, if so, the first sub-safety state is entered through the SBC, if not, the first sub-safety state is entered through the MCU.

[0038] In the above implementation process, fault protection is determined according to the fault type and the status of the vehicle, which can reduce damage to the vehicle and other hardware, ensure the safety performance of the motor controller in a more timely manner, and provide more comfort for safe driving of the vehicle.

[0039] In a second aspect, an embodiment of the present application further provides a fault protection device for a motor controller, the device comprising:

[0040] An acquisition module, used for acquiring fault information of the motor controller;

[0041] A fault protection module is used to select the first safety state or the second safety state for fault protection when the fault information shows that the driving circuit of the motor controller is normal; select the third safety state for fault protection when the fault information shows that the control unit of the motor controller is normal; and select the fourth safety state for fault protection when the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor.

[0042] In the above implementation process, a variety of different safety states are selected according to the fault information, and the fault protection state can be entered through a variety of channels to effectively protect the hardware. The feedback after the fault occurs is more timely, and the selection of safety states is more flexible and changeable, which can take into account the safety of the motor controller during operation.

[0043] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.

[0044] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed on a computer, the computer executes the method as described in any one of the first aspects.

[0045] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method as described in any one of the first aspects.

[0046] Other features and advantages of the present disclosure will be set forth in the following description, or some features and advantages may be inferred or unambiguously determined from the description, or may be learned by implementing the above-mentioned technology of the present disclosure.

[0047] And it can be implemented according to the contents of the specification. The following is a detailed description of the preferred embodiments of the present application with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the range values. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0049] Figure 1 A schematic flow chart of a fault protection method for a motor controller provided in an embodiment of the present application;

[0050] Figure 2 A schematic diagram of the structure of a fault protection device for a motor controller provided in an embodiment of the present application;

[0051] Figure 3 A schematic diagram of the structural composition of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0053] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0054] The specific implementation methods of the present application are further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present application, but are not used to limit the scope of the present application.

[0055] Embodiment 1

[0056] Figure 1 is a flow chart of a fault protection method for a motor controller provided in an embodiment of the present application, such as Figure 1 As shown, the method includes:

[0057] S1, obtain the fault information of the motor controller;

[0058] S2, when the fault information shows that the drive circuit of the motor controller is normal, selecting the first safety state or the second safety state for fault protection;

[0059] S3, when the fault information shows that the control unit of the motor controller is normal, the third safety state is selected for fault protection;

[0060] S4, when the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor, the fourth safety state is selected for fault protection.

[0061] In the above implementation process, a variety of different safety states are selected according to the fault information, and the fault protection state can be entered through a variety of channels to effectively protect the hardware. The feedback after the fault occurs is more timely, and the selection of safety states is more flexible and changeable, which can take into account the safety of the motor controller during operation.

[0062] The motor controller consists of three parts: a microcontroller unit or main control chip (MCU), a driver chip (upper bridge driver chip, lower bridge driver chip), and an insulated gate bipolar transistor (IGBT). The main control chip controls the switching action of the IGBT (including normal torque output, three-phase short circuit, and tube shutdown, etc.) through 2×3 PWM outputs. When PWMEn is not enabled, the 2×3 PWM outputs are intercepted, and the driver chip outputs 6 0% duty cycles to control all IGBTs to be non-conductive. When the ASC control outputs a control signal, the driver chip outputs 0% duty cycle for the upper tube and 100% duty cycle for the lower tube, entering a three-phase short circuit state.

[0063] The safety status of the embodiment of the present application includes four types, and a reasonable state can be flexibly selected according to the severity of the fault, the type of fault, and the operation status of the vehicle to ensure the safety of the system and personnel while improving driving comfort. The safety status is as follows:

[0064] Active discharge; zero torque control; 6 IGBTs of the upper and lower bridges are disconnected at the same time (referred to as FW); 3 IGBTs of the upper bridge are disconnected, 3 IGBTs of the lower bridge are closed, or 3 IGBTs of the lower bridge are closed, and the lower bridge IGBT is disconnected (referred to as ASC state).

[0065] In S2, the two safety states of active discharge and zero torque control require that the drive circuit is normal and the MCU can normally control the duty cycle of the six IGBTs.

[0066] FW requires that the MCU works normally, there should be no driver chip faults, the IGBT should not be stuck in the "on" state, and the MCU should be able to control 6 IGBTs to be turned off at the same time. After entering the FW state, the PWM control IGBT instruction will not be executed.

[0067] Furthermore, S4 includes:

[0068] Determine whether there is a driving abnormality in the motor controller;

[0069] If so, performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state;

[0070] If not, perform fault protection according to the relay status.

[0071] In the above implementation process, different methods are selected for fault protection according to whether there is a driving abnormality in the motor controller, so that the motor controller can be protected in multiple ways and multiple channels during operation, which is conducive to maintaining the stability of the motor controller.

[0072] There are several forms of ASC state. When you need to enter the ASC state, select the ASC method according to the following logic. When you need to enter immediately or the drive system is abnormal, select direct HWASC to ensure that the lower bridge is turned on quickly from the back end of the driver chip.

[0073] Table 1 Several forms of ASC safety status

[0074]

[0075] In the embodiment of the present application, HWASC corresponds to the first sub-security state, UpASC corresponds to the second sub-security state, DwnASC corresponds to the third sub-security state, UpGradASC corresponds to the fourth sub-security state, and DwnGradASC corresponds to the fifth sub-security state.

[0076] Further, the step of performing fault protection according to the relay state includes:

[0077] Determine whether the main relay is disconnected based on the relay status;

[0078] If so, performing fault protection according to the first state of the driver chip of the motor controller;

[0079] If not, fault protection is performed according to the second state of the driving chip of the motor controller.

[0080] In the above implementation process, different fault protection methods are selected according to whether the main relay is disconnected, which can protect the main relay so that the main relay can maintain stable operation when a fault occurs, thereby minimizing damage to the hardware.

[0081] Further, the step of performing fault protection according to the first state of the driving chip of the motor controller includes:

[0082] The first state of the driver chip of the motor controller is that both the upper bridge driver chip and the lower bridge driver chip cannot be controlled normally, and it is determined whether the upper bridge driver chip is completely disconnected and the lower bridge driver chip is fully turned on;

[0083] If so, performing fault protection on the motor controller according to the third sub-safety state in the fourth safety state;

[0084] If not, determine whether the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on. If the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on, the motor controller is fault protected according to the second sub-safety state in the fourth safety state. If the lower bridge driver chip is not fully disconnected or the upper bridge driver chip is not fully turned on, the motor controller is fault protected according to the first sub-safety state in the fourth safety state.

[0085] In the above implementation process, fault protection is performed according to the first state of the driver chip of the motor controller, and the state of the driver chip is refined, so that the fault condition of the motor controller can be measured in multiple dimensions and refined fault adjustment can be achieved.

[0086] In the embodiment of the present application, the current limiting ASC cannot be executed when the main relay is disconnected. If it is determined that the upper bridge drive chip can be completely disconnected and the lower bridge can be fully turned on, DwnASC is selected. Otherwise, it is determined whether the lower bridge drive chip can be completely disconnected and the upper bridge can be fully turned on. If so, UpASC is selected, otherwise HWASC is executed.

[0087] When the main relay is closed, current limiting ASC is executed first to reduce the damage of instantaneous large current to power components. If the upper bridge driver chip can be fully disconnected and the lower bridge driver chip can execute the duty cycle normally, DwnGradASC is selected. Otherwise, it is determined whether the lower bridge driver chip can be fully disconnected and the upper bridge driver chip can output the duty cycle normally. If so, UpGradASC is selected. Otherwise, it is considered that current limiting ASC cannot be executed, and the ASC strategy is executed directly.

[0088] Further, the step of performing fault protection according to the second state of the driving chip of the motor controller includes:

[0089] The second state of the driver chip of the motor controller is that the upper bridge driver chip or the lower bridge driver chip cannot be controlled normally, and it is determined whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is completely turned on;

[0090] If yes, determine whether the upper bridge driver chip of the motor controller is fully disconnected and the lower bridge driver chip is under normal control. If the upper bridge driver chip of the motor controller is fully disconnected and the lower bridge driver chip is under normal control, perform fault protection on the motor controller according to the fifth sub-safety state in the fourth safety state;

[0091] If not, determine whether the lower bridge driver chip of the motor controller is fully disconnected and the upper bridge driver chip is under normal control; if the lower bridge driver chip of the motor controller is fully disconnected and the upper bridge driver chip is under normal control, perform fault protection on the motor controller according to the fourth sub-safety state in the fourth safety state; if the lower bridge driver chip of the motor controller is not fully disconnected or the upper bridge driver chip is not under normal control, perform fault protection according to the first state of the driver chip of the motor controller.

[0092] In the above implementation process, fault protection is performed according to the second state of the driver chip of the motor controller to implement fault protection outside the first state, further dividing the possible faults of the driver chip into multiple aspects to improve the protection capability of the driver chip.

[0093] Furthermore, before the step of performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state, the method further includes:

[0094] Fault protection is performed according to the fault type.

[0095] In the above implementation process, the fault protection method is selected more accurately according to the fault type, so that the motor controller can be protected from faults faster and more efficiently.

[0096] The types of faults that cause a motor system to lose power are classified as follows:

[0097] High voltage overvoltage fault; three-phase overcurrent fault; abnormal drive system fault, this type of fault cannot normally control the IGBT switch action and torque output; abnormal internal fault of the non-drive system, this type of fault can still normally control the IGBT switch action and torque output; abnormal communication fault and other external system faults.

[0098] Furthermore, the steps of performing fault protection according to the fault type include:

[0099] When the fault type is over-voltage, determine whether the vehicle is stationary. If so, determine whether the current vehicle speed is low. If the current vehicle speed is low, enter the third safety state for fault protection. If the current vehicle speed is high, enter the first sub-safety state in the fourth safety state for fault protection. If not, perform fault protection according to the voltage recovery situation.

[0100] When the fault type is overcurrent, determine whether the current vehicle speed is low speed. If the current vehicle speed is low speed, enter the third safety state for fault protection. If the current vehicle speed is high speed, enter the first sub-safety state in the fourth safety state for fault protection.

[0101] When the fault type is drive abnormality, determine whether it is a self-fault. If so, enter the first sub-safe state through the SBC. If not, enter the first sub-safe state through the MCU.

[0102] In the above implementation process, fault protection is determined according to the fault type and the status of the vehicle, which can reduce damage to the vehicle and other hardware, ensure the safety performance of the motor controller in a more timely manner, and provide more comfort for safe driving of the vehicle.

[0103] Over-voltage fault is a more serious fault with the potential risk of damaging power components. The vehicle needs to enter the HWASC state immediately when it is running to protect the electric drive power components from being damaged by high voltage. When the vehicle is stationary (such as charging in situ), it needs to enter the FW state to prevent the IGBT freewheeling diode from being broken down by high voltage.

[0104] If the vehicle is in a non-stationary condition, after entering the safe state (HWASC), the application software will take over, and after the voltage returns to normal, ASC and FW will be switched according to the speed. The FW state will be entered at low speed to ensure the smooth operation of the vehicle, and the ASC state will be entered at high speed to protect the hardware from damage. If the vehicle is in a stationary condition, after entering the safe state (FW), the application software will take over, without judging whether the voltage has returned to normal, and ASC and FW will be switched directly according to the speed. The FW state will be entered at low speed to ensure the smooth operation of the vehicle, and the ASC state will be entered at high speed to protect the hardware from damage.

[0105] Phase current overcurrent (overcurrent) fault is a more serious fault with the potential risk of damaging power components. When phase current appears, the interrupt function is immediately entered to handle the fault. During the interrupt function, it is determined whether the system is already in the ASC / FW state. If so, no processing is performed to maintain the original state. Otherwise, the system is immediately shut down and enters the FW state to quickly reduce the current and ensure that the power components are not damaged. After exiting the interrupt function, the ASC / FW state is switched according to the vehicle speed.

[0106] Drive abnormality faults can be divided into two categories. If it is a fault of the MCU itself, the system enters the HWASC state through the SBC control system. Otherwise, the system enters the HWASC state through the MCU control system.

[0107] MCU's own failure, such as watchdog timeout, abnormal reset, SBC chip; driver peripheral failure, such as low voltage power supply abnormality, driver chip failure, power component abnormality.

[0108] In the case of non-drive abnormality faults, the MCU and system drive circuits can still work normally. Serious faults occur in non-drive related components, such as motor overtemperature, sensor hardware abnormalities, etc. In the case of such faults, the MCU can still correctly control the switching action of the IGBT and output the correct torque command. With the goal of alleviating the fault state, zero torque control is performed at medium and high vehicle speeds to reduce system current, and FW is performed at low vehicle speeds to reduce power consumption.

[0109] Abnormal communication failure, the motor controller itself can work normally, and the driving requirements of the whole vehicle cannot be determined. For safety reasons, the power output should be cut off to avoid sports injuries, and the active discharge state should be entered to avoid high-voltage electric shock injuries.

[0110] Other external system failures require the motor controller to cut off power output, and the motor controller itself can work normally, also with the goal of alleviating the fault state. If it is a cooling system failure, zero torque control is performed at medium and high speeds to reduce system current, and FW is performed at low speeds to reduce power consumption. If it is a non-cooling system failure, ASC is performed at medium and high speeds, and FW is performed at low speeds.

[0111] The embodiment of the present application provides a motor controller fault protection strategy. The safety state includes zero torque control, active discharge, IGBT full shutdown and multiple ASC states. The safety state can be flexibly selected according to the cause of the fault and the operation status of the vehicle. On the premise of protecting personal safety and the safety of the electric drive system, the driving comfort is maximized and the driver's anxiety about new energy vehicle failures is reduced.

[0112] Embodiment 2

[0113] In order to execute the method corresponding to the above embodiment 1 to achieve the corresponding functions and technical effects, a fault protection device for a motor controller is provided below, such as Figure 2 As shown, the device comprises:

[0114] Acquisition module 1, used to acquire fault information of the motor controller;

[0115] Fault protection module 2 is used to select the first safety state or the second safety state for fault protection when the fault information shows that the driving circuit of the motor controller is normal; select the third safety state for fault protection when the fault information shows that the control unit of the motor controller is normal; select the fourth safety state for fault protection when the fault information shows that the control unit of the motor controller cannot control the bipolar transistor normally.

[0116] In the above implementation process, a variety of different safety states are selected according to the fault information, and the fault protection state can be entered through a variety of channels to effectively protect the hardware. The feedback after the fault occurs is more timely, and the selection of safety states is more flexible and changeable, which can take into account the safety of the motor controller during operation.

[0117] Furthermore, the fault protection module 2 is also used for:

[0118] Determine whether there is a driving abnormality in the motor controller;

[0119] If so, performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state;

[0120] If not, perform fault protection according to the relay status.

[0121] In the above implementation process, different methods are selected for fault protection according to whether there is a driving abnormality in the motor controller, so that the motor controller can be protected in multiple ways and multiple channels during operation, which is conducive to maintaining the stability of the motor controller.

[0122] Furthermore, the fault protection module 2 is also used for:

[0123] Determine whether the main relay is disconnected based on the relay status;

[0124] If so, performing fault protection according to the first state of the driver chip of the motor controller;

[0125] If not, fault protection is performed according to the second state of the driving chip of the motor controller.

[0126] In the above implementation process, different fault protection methods are selected according to whether the main relay is disconnected, which can protect the main relay so that the main relay can maintain stable operation when a fault occurs, thereby minimizing damage to the hardware.

[0127] Furthermore, the fault protection module 2 is also used for:

[0128] The first state of the driver chip of the motor controller is that both the upper bridge driver chip and the lower bridge driver chip cannot be controlled normally, and it is determined whether the upper bridge driver chip is completely disconnected and the lower bridge driver chip is fully turned on;

[0129] If so, performing fault protection on the motor controller according to the third sub-safety state in the fourth safety state;

[0130] If not, determine whether the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on. If the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on, the motor controller is fault protected according to the second sub-safety state in the fourth safety state. If the lower bridge driver chip is not fully disconnected or the upper bridge driver chip is not fully turned on, the motor controller is fault protected according to the first sub-safety state in the fourth safety state.

[0131] In the above implementation process, fault protection is performed according to the first state of the driver chip of the motor controller, and the state of the driver chip is refined, so that the fault condition of the motor controller can be measured in multiple dimensions and refined fault adjustment can be achieved.

[0132] Furthermore, the fault protection module 2 is also used for:

[0133] The second state of the driver chip of the motor controller is that the upper bridge driver chip or the lower bridge driver chip cannot be controlled normally, and it is determined whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is completely turned on;

[0134] If yes, determine whether the upper bridge driver chip of the motor controller is fully disconnected and the lower bridge driver chip is under normal control. If the upper bridge driver chip of the motor controller is fully disconnected and the lower bridge driver chip is under normal control, perform fault protection on the motor controller according to the fifth sub-safety state in the fourth safety state;

[0135] If not, determine whether the lower bridge driver chip of the motor controller is fully disconnected and the upper bridge driver chip is under normal control; if the lower bridge driver chip of the motor controller is fully disconnected and the upper bridge driver chip is under normal control, perform fault protection on the motor controller according to the fourth sub-safety state in the fourth safety state; if the lower bridge driver chip of the motor controller is not fully disconnected or the upper bridge driver chip is not under normal control, perform fault protection according to the first state of the driver chip of the motor controller.

[0136] In the above implementation process, fault protection is performed according to the second state of the driver chip of the motor controller to implement fault protection outside the first state, further dividing the possible faults of the driver chip into multiple aspects to improve the protection capability of the driver chip.

[0137] Furthermore, the fault protection module 2 is also used for:

[0138] Fault protection is performed according to the fault type.

[0139] In the above implementation process, the fault protection method is selected more accurately according to the fault type, so that the motor controller can be protected from faults faster and more efficiently.

[0140] Furthermore, the fault protection module 2 is also used for:

[0141] When the fault type is over-voltage, determine whether the vehicle is stationary. If so, determine whether the current vehicle speed is low. If the current vehicle speed is low, enter the third safety state for fault protection. If the current vehicle speed is high, enter the first sub-safety state in the fourth safety state for fault protection. If not, perform fault protection according to the voltage recovery situation.

[0142] When the fault type is overcurrent, determine whether the current vehicle speed is low speed. If the current vehicle speed is low speed, enter the third safety state for fault protection. If the current vehicle speed is high speed, enter the first sub-safety state in the fourth safety state for fault protection.

[0143] When the fault type is drive abnormality, determine whether it is a self-fault. If so, enter the first sub-safe state through the SBC. If not, enter the first sub-safe state through the MCU.

[0144] In the above implementation process, fault protection is determined according to the fault type and the status of the vehicle, which can reduce damage to the vehicle and other hardware, ensure the safety performance of the motor controller in a more timely manner, and provide more comfort for safe driving of the vehicle.

[0145] The fault protection device of the motor controller described above can implement the method of the above embodiment 1. The options in the above embodiment 1 are also applicable to this embodiment and will not be described in detail here.

[0146] The rest of the contents of the embodiments of the present application can refer to the contents of the above-mentioned embodiment 1, and will not be repeated in this embodiment.

[0147] Embodiment 3

[0148] An embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the fault protection method of the motor controller of the first embodiment.

[0149] Optionally, the above-mentioned electronic device may be a server.

[0150] See also Figure 3 , Figure 3A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 31, a communication interface 32, a memory 33 and at least one communication bus 34. The communication bus 34 is used to realize direct connection and communication between these components. The communication interface 32 of the device in the embodiment of the present application is used to communicate signaling or data with other node devices. The processor 31 may be an integrated circuit chip with signal processing capabilities.

[0151] The processor 31 mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor 31 can also be any conventional processor, etc.

[0152] The memory 33 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc. The memory 33 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 31, the device can execute the above-mentioned Figure 1 The method embodiment involves various steps.

[0153] Optionally, the electronic device may further include a storage controller and an input / output unit. The memory 33, the storage controller, the processor 31, the peripheral interface, and the input / output unit are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components may be electrically connected to each other via a communication bus 34. The processor 31 is used to execute executable modules stored in the memory 33, such as software function modules or computer programs included in the device.

[0154] The input and output unit is used to provide users with the task creation and to create an optional time period or preset execution time for the task to enable interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and a keyboard.

[0155] Understandably, Figure 3 The structure shown is for illustration only. The electronic device may also include Figure 3 More or fewer components as shown, or with Figure 3 Different configurations are shown. Figure 3 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0156] In addition, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which implements the fault protection method of the motor controller of the first embodiment when executed by a processor.

[0157] The embodiment of the present application also provides a computer program product, which, when running on a computer, enables the computer to execute the method described in the method embodiment.

[0158] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart, can be implemented with a dedicated hardware-based device that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0159] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0160] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0161] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. It should be noted that similar numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0162] The above is only a specific implementation of the present application, but the protection range of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical range disclosed in the present application, which should be included in the protection range of the present application. Therefore, the protection range of the present application should be based on the protection range of the claims.

[0163] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A fault protection method for a motor controller, characterized in that: The method comprises: Obtaining fault information of the motor controller; When the fault information shows that the driving circuit of the motor controller is normal, selecting the first safety state or the second safety state for fault protection; When the fault information shows that the control unit of the motor controller is normal, selecting the third safety state for fault protection; When the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor, the fourth safety state is selected for fault protection.

2. The fault protection method for a motor controller according to claim 1, characterized in that: The step of selecting the fourth safety state for fault protection comprises: Determine whether the motor controller has a driving abnormality; If so, performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state; If not, perform fault protection according to the relay status.

3. The fault protection method for a motor controller according to claim 2, characterized in that: The step of performing fault protection according to the relay state comprises: Determining whether the main relay is disconnected according to the relay state; If so, performing fault protection according to the first state of the driving chip of the motor controller; If not, fault protection is performed according to the second state of the driving chip of the motor controller.

4. The fault protection method for a motor controller according to claim 3, characterized in that: The step of performing fault protection according to the first state of the driving chip of the motor controller comprises: The first state of the driver chip of the motor controller is that both the upper bridge driver chip and the lower bridge driver chip cannot be normally controlled, and it is determined whether the upper bridge driver chip is completely disconnected and the lower bridge driver chip is fully turned on; If so, performing fault protection on the motor controller according to the third sub-safety state in the fourth safety state; If not, determine whether the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on. If the lower bridge driver chip is fully disconnected and the upper bridge driver chip is fully turned on, perform fault protection on the motor controller according to the second sub-safety state in the fourth safety state. If the lower bridge driver chip is not fully disconnected or the upper bridge driver chip is not fully turned on, perform fault protection on the motor controller according to the first sub-safety state in the fourth safety state.

5. The fault protection method for a motor controller according to claim 3, characterized in that: The step of performing fault protection according to the second state of the driving chip of the motor controller comprises: The second state of the driver chip of the motor controller is that the upper bridge driver chip or the lower bridge driver chip cannot be normally controlled, and it is determined whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is completely turned on; If yes, determine whether the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is under normal control; if the upper bridge driver chip of the motor controller is completely disconnected and the lower bridge driver chip is under normal control, perform fault protection on the motor controller according to the fifth sub-safety state in the fourth safety state; If not, determine whether the lower bridge driver chip of the motor controller is completely disconnected and the upper bridge driver chip is under normal control; if the lower bridge driver chip of the motor controller is completely disconnected and the upper bridge driver chip is under normal control, perform fault protection on the motor controller according to the fourth sub-safety state in the fourth safety state; if the lower bridge driver chip of the motor controller is not completely disconnected or the upper bridge driver chip is not under normal control, perform fault protection according to the first state of the driver chip of the motor controller.

6. The fault protection method for a motor controller according to claim 2, characterized in that: Before the step of performing fault protection on the motor controller according to the first sub-safety state in the fourth safety state, the method further includes: Fault protection is performed according to the fault type.

7. The fault protection method of the motor controller according to claim 6, characterized in that: The step of performing fault protection according to the fault type includes: When the fault type is over-high voltage, determine whether the vehicle is stationary, if so, determine whether the current vehicle speed is low, if the current vehicle speed is low, enter the third safety state for fault protection, if the current vehicle speed is high, enter the first sub-safety state in the fourth safety state for fault protection, if not, perform fault protection according to the voltage recovery situation; When the fault type is overcurrent, determine whether the current vehicle speed is low speed, if the current vehicle speed is low speed, enter the third safety state for fault protection, if the current vehicle speed is high speed, enter the first sub-safety state in the fourth safety state for fault protection; When the fault type is a drive abnormality, it is determined whether it is a self-fault, if so, the first sub-safety state is entered through the SBC, if not, the first sub-safety state is entered through the MCU.

8. A fault protection device for a motor controller, characterized in that: The device comprises: An acquisition module, used for acquiring fault information of the motor controller; A fault protection module is used to select the first safety state or the second safety state for fault protection when the fault information shows that the driving circuit of the motor controller is normal; select the third safety state for fault protection when the fault information shows that the control unit of the motor controller is normal; and select the fourth safety state for fault protection when the fault information shows that the control unit of the motor controller cannot normally control the bipolar transistor.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the fault protection method for the motor controller according to any one of claims 1 to 7.

10. A storage medium, characterized in that: A computer program is stored therein, and when the computer program is executed by a processor, the fault protection method for the motor controller as claimed in any one of claims 1 to 7 is implemented.