Motor overcurrent protection method and device and vehicle

Abstract

The application provides a motor overcurrent protection method, device and vehicle. The method comprises the following steps: obtaining a motor current of a motor; if the motor current exceeds an overcurrent value of the motor, determining that a hardware overcurrent fault occurs, and sending a first control instruction to a drive board controller, so that the drive board controller controls a switch tube in the drive board to be turned off according to the first control instruction; if the motor current continuously exceeds the overcurrent value of the motor and a continuous time length is less than or equal to a first preset time length, a second control instruction is sent to the drive board controller, so that the drive board controller controls the switch tube to be turned on according to the second control instruction, to realize self-recovery of the motor; if a number of self-recoveries of the motor within a second preset time length is greater than a preset number, a third control instruction is generated to a vehicle controller, so that the vehicle controller controls the motor to be stopped according to the third control instruction. The motor overcurrent protection method provided by the application can realize self-recovery of the motor after the hardware overcurrent, and ensures driving safety.

Description

Technical Field

[0001] This application relates to the field of motor control technology, specifically to a motor control method, electronic equipment, and vehicle. Background Technology

[0002] Currently, overcurrent protection is an essential function for motor controllers in new energy vehicles to protect both the motor and the controller. Overcurrent protection includes software overcurrent protection and hardware overcurrent protection. Software overcurrent protection involves the motor controller using a main control chip (DSP, ARM, FPGA, etc.) to collect three-phase current and determine whether there is an overcurrent. If an overcurrent is detected, the motor controller is shut down via the control chip pins. However, because control and data acquisition are discrete, it cannot monitor and protect against overcurrent in real time. Hardware overcurrent protection involves designing a hardware simulation circuit and using a comparator to compare the current in real time to determine whether there is an overcurrent. If an overcurrent is detected, the comparator output directly controls the motor controller to shut down.

[0003] However, hardware overcurrent may be caused by signal interference or special operating conditions. If the hardware overcurrent is directly blocked without self-recovery, it increases the risk to the driver's safety.

[0004] Therefore, there is an urgent need for an overcurrent protection method that can self-recover under specific conditions after a hardware overcurrent, which would greatly improve the driver's experience and driving safety. Summary of the Invention

[0005] To address the aforementioned problems in the prior art, this application provides a motor overcurrent protection method, device, and vehicle to achieve self-recovery of the motor after a hardware overcurrent, thereby improving the driver's experience and driving safety.

[0006] According to a first aspect of the embodiments of this application, a current overcurrent protection method is provided, the method comprising:

[0007] Obtain the motor current of the motor;

[0008] If the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined, and a first control command is sent to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command.

[0009] If the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to the first preset duration, a second control command is sent to the drive board controller, so that the drive board controller controls the switch to close according to the second control command, thereby realizing the motor's self-recovery.

[0010] If the number of self-recovery cycles of the motor exceeds the preset number within the second preset time period, a third control command is generated and sent to the vehicle controller so that the vehicle controller can control the motor to stop according to the third control command. The second preset time period is longer than the first preset time period.

[0011] In an optional embodiment, the method further includes:

[0012] If the motor current exceeds the motor's overcurrent value, a fourth control command is sent to the vehicle controller, so that the vehicle controller records the motor's hardware overcurrent fault information according to the fourth control command and resets the motor's torque to zero.

[0013] In an optional embodiment, the method further includes:

[0014] If the number of self-recovery cycles of the motor within the second preset time period is less than or equal to the preset number, a fifth control command is sent to the vehicle controller and a sixth control command is sent to the drive board controller. This causes the vehicle controller to clear the hardware overcurrent fault information of the motor according to the fifth control command and increase the torque gradient of the motor to the target torque. The drive board controller controls the switching transistor in the drive board to close according to the sixth control command.

[0015] In an optional embodiment, the method further includes:

[0016] If the motor current is less than the motor's overcurrent value within the third preset time period after the motor's torque gradient increases to the target torque, the self-recovery count will be reset to zero.

[0017] In an optional embodiment, the method further includes:

[0018] If the motor current continuously exceeds the motor's overcurrent value and the duration exceeds the first preset duration, a sixth control command is sent to the vehicle controller, and the vehicle controller controls the motor to stop according to the sixth control command.

[0019] In one optional embodiment, the preset number of times is 2.

[0020] In an optional embodiment, the method further includes: if the motor current exceeds the motor's overcurrent value,

[0021] The seventh control command is sent to the vehicle controller so that the vehicle controller can adjust the motor's operating parameters according to the seventh control command.

[0022] In one optional embodiment, if the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined to have occurred, including:

[0023] Based on the current sensor parameters and motor current in the hardware circuit, determine the output voltage corresponding to the motor current;

[0024] If the output voltage is greater than the voltage threshold in the hardware circuit, it is determined that the motor current exceeds the motor's overcurrent value, and a hardware overcurrent fault has occurred.

[0025] According to a second aspect of the embodiments of this application, a motor overcurrent protection device is provided, the device comprising:

[0026] The acquisition unit is used to acquire the motor current of the motor;

[0027] The first sending unit is used to determine that a hardware overcurrent fault has occurred if the motor current exceeds the motor's overcurrent value, and to send a first control command to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command.

[0028] The second sending unit is used to send a second control command to the drive board controller if the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to the first preset duration, so that the drive board controller controls the switch to close according to the second control command, thereby realizing the motor's self-recovery.

[0029] The third sending unit is used to generate a third control command to the vehicle controller if the number of self-recovery times of the motor within the second preset time period is greater than the preset number of times, so that the vehicle controller controls the motor to stop according to the third control command, and the second preset time period is greater than the first preset time period.

[0030] According to a third aspect of the embodiments of this application, a vehicle is provided, including a motor overcurrent protection device as described in the second aspect.

[0031] This application provides a motor overcurrent protection method, device, and vehicle. The method determines whether a hardware overcurrent fault has occurred by judging whether the motor current exceeds the motor's overcurrent value. When a hardware overcurrent fault occurs, a drive switch is disconnected. Furthermore, if the duration for which the motor current continuously exceeds the motor's overcurrent value is less than or equal to a first preset duration, the drive switch can be closed to achieve motor self-recovery. If the number of self-recoveries within a second preset duration exceeds a preset number, the motor's hardware may be faulty, and the motor is stopped. The motor overcurrent control method provided in this application, by judging the duration of a hardware overcurrent fault and the number of self-recoveries, can effectively avoid overcurrent faults caused by interference signals or intermittent operating conditions. It allows for direct fault self-recovery without requiring a shutdown and fault reporting, thus improving driving experience and road safety. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0033] Figure 1This is a schematic diagram of the implementation environment according to the present invention;

[0034] Figure 2 A flowchart of a motor overcurrent protection method provided in an embodiment of this application;

[0035] Figure 3 This is a structural block diagram of the motor overcurrent protection device provided in the embodiments of this application;

[0036] Figure 4 This is a structural diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0037] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] Currently, overcurrent protection is an essential function in the motor controllers of new energy vehicles to protect the motor and controller. However, hardware overcurrent may be caused by signal interference or special operating conditions. If hardware overcurrent is directly blocked without self-recovery, it increases the risk to driver safety. Therefore, there is an urgent need for an overcurrent protection method that can self-recover under specific conditions after hardware overcurrent, greatly improving the driver's experience and driving safety.

[0039] This application provides a motor overcurrent protection method, device, and vehicle. The method determines whether a hardware overcurrent fault has occurred by judging whether the motor current exceeds the motor's overcurrent value. When a hardware overcurrent fault occurs, a drive switch is disconnected. Furthermore, if the duration for which the motor current continuously exceeds the motor's overcurrent value is less than or equal to a first preset duration, the drive switch can be closed to achieve motor self-recovery. If the number of self-recoveries within a second preset duration exceeds a preset number, the motor's hardware may be faulty, and the motor is stopped. The motor overcurrent control method provided in this application, by judging the duration of a hardware overcurrent fault and the number of self-recoveries, can effectively avoid overcurrent faults caused by interference signals or intermittent operating conditions. It allows for direct fault self-recovery without requiring a shutdown and fault reporting, thus improving driving experience and road safety.

[0040] Exemplary Implementation Environment

[0041] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the implementation environment according to the present invention.

[0042] like Figure 1As shown, this application scenario involves vehicle 1. Vehicle 1 may be equipped with a Vehicle Control Unit (VCU) and a Motor Control Unit (MCU). The VCU is responsible for integrating and processing parameters from vehicle 1, sending commands to the MCU via the CAN bus, and monitoring the status information fed back by the MCU. The MCU can receive torque or speed commands sent by the VCU via the CAN bus. The MCU can also convert the DC power from the battery into three-phase AC power through switching transistors to drive the motor. The MCU can also drive the switching transistors to open and close according to control commands.

[0043] Exemplary methods

[0044] Figure 2 For a flowchart of the motor overcurrent protection method provided in this application embodiment, please refer to [link / reference]. Figure 2 In one exemplary embodiment, a motor overcurrent protection method is provided, the method may include:

[0045] S210: Obtain the motor current of the motor;

[0046] In this embodiment, the motor current can be a three-phase current. In practical applications, the motor current can be indirectly determined by measuring the voltage drop across the resistor through the shunt resistor and operational amplifier circuit.

[0047] S230: If the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined, and a first control command is sent to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command.

[0048] Hardware overcurrent faults can be caused by abnormalities in physical components, such as power devices, which cause the current to exceed the safe threshold, potentially leading to motor damage or system failure.

[0049] The overcurrent value of the motor can be determined based on the battery discharge current, the motor short-circuit current, and the rated current of the switching transistor. For example, the motor overcurrent value can be the smaller of the maximum battery discharge current and the IGBT limit current.

[0050] In practical applications, the MCU outputs PWM signals to the drive controller via GPIO or a dedicated PWM module. The drive controller converts the controller's low-voltage logic signals into drive signals, which then drive the switching transistors to open and close via the drive board.

[0051] When the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined, and a first control command is sent to the drive board controller to cause the drive board controller to disconnect the switching transistor. In this embodiment, after determining that a hardware overcurrent fault has occurred due to the motor current exceeding the overcurrent value, the drive controller directly disconnects the switching transistor, thus protecting the hardware.

[0052] S250: If the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to the first preset duration, a second control command is sent to the drive board controller so that the drive board controller controls the switch to close according to the second control command, thereby realizing the motor's self-recovery.

[0053] Hardware overcurrent faults may be caused by interference signals or occasional operating conditions. In such cases, there is no need to stop the machine and report the fault; the fault can be automatically recovered. When the motor current exceeds the motor's overcurrent value for a duration less than or equal to a first preset duration, it indicates that the hardware is not damaged, and the switching transistor can be controlled to close, achieving motor self-recovery. The first preset duration can be 1 millisecond. It should be understood that the first preset duration can also be set to other values, which will not be elaborated here.

[0054] It should be understood that if the motor current continuously exceeds the motor's overcurrent value and the duration exceeds the first preset duration, it indicates a hardware fault and self-recovery is not allowed.

[0055] S270: If the number of self-recovery cycles of the motor within the second preset time period is greater than the preset number, a third control command is generated to the vehicle controller so that the vehicle controller controls the motor to stop according to the third control command. The second preset time period is greater than the first preset time period.

[0056] If the number of self-recovery attempts of the motor exceeds the preset number within the second preset time period, it indicates that there is a problem with the current operating condition or hardware, and self-recovery is not allowed. A third control command can be sent to the vehicle controller to control the motor to stop, so as to ensure the safety of the vehicle and personnel.

[0057] In one optional embodiment, the preset number of times can be 2. The second preset duration can be 1 minute. It should be understood that the second preset duration and the preset number of times can also be set to other values, which will not be elaborated here.

[0058] The motor overcurrent protection method provided in this application determines whether a hardware overcurrent fault has occurred by judging whether the motor current exceeds the motor's overcurrent value. Furthermore, it determines whether the motor can self-recover based on the duration for which the electrode current continuously exceeds the overcurrent value. The method can also determine self-recovery based on the number of self-recovery attempts. The motor overcurrent control method provided in this application effectively avoids overcurrent faults caused by interference signals or intermittent operating conditions, enabling direct fault self-recovery without requiring a shutdown and fault reporting, thus improving driving experience and road safety.

[0059] In one alternative embodiment, the method may further include:

[0060] If the motor current exceeds the motor's overcurrent value, a fourth control command is sent to the vehicle controller, so that the vehicle controller records the motor's hardware overcurrent fault information according to the fourth control command and resets the motor's torque to zero.

[0061] In practical applications, when the motor exceeds the current value, a raw electrical signal is generated. The digital-to-analog converter in the MCU can convert the electrical signal into a digital signal. The signal is then encapsulated and transmitted to the application layer through middleware. After receiving the fourth control command, the vehicle controller analyzes the signal and obtains the hardware overcurrent fault information. It can then limit the vehicle's power, clear the motor torque to zero, and ensure the safety of the vehicle and the driver.

[0062] In one alternative embodiment, the method may further include:

[0063] If the number of self-recovery cycles of the motor within the second preset time period is less than or equal to the preset number, a fifth control command is sent to the vehicle controller and a sixth control command is sent to the drive board controller. This causes the vehicle controller to clear the hardware overcurrent fault information of the motor according to the fifth control command and increase the torque gradient of the motor to the target torque. The drive board controller controls the switching transistor in the drive board to close according to the sixth control command.

[0064] If the number of self-recovery cycles after a hardware overcurrent fault occurs in the motor is less than or equal to the preset number, it indicates that there is no fault in the current operating condition or hardware. The fifth control command can be sent to clear the fault and determine the target torque based on the current driving parameters to restore the motor to the target torque.

[0065] In practical applications, motors can recover torque using a gradient approach. For example, when recovering torque, a staged torque recovery method can be employed. In the first stage, 5% to 30% of the target torque can be recovered, with the torque slowly increased at a rate of 2%-5% per second. After confirming that the motor is functioning normally, the second stage can recover 30%-70% of the target torque, with the increase rate reduced to 1%-2% per second to avoid mechanical shock from excessive torque. Finally, after confirming that the motor is functioning normally, 70%-100% of the target torque can be recovered. Using a gradient torque recovery method avoids sudden torque increases that could cause a step signal that could lead to hardware overcurrent, thus ensuring motor safety.

[0066] In one alternative embodiment, the method may further include:

[0067] If the motor current is less than the motor's overcurrent value within the third preset time period after the motor's torque gradient increases to the target torque, the self-recovery count will be reset to zero.

[0068] If the motor current is less than the motor's overcurrent value within the third preset time period, it indicates that the motor is operating normally without any hardware overcurrent faults. The self-recovery count will be reset to zero to facilitate the re-detection of hardware overcurrent faults in the motor and improve the safety of motor operation.

[0069] In one alternative embodiment, the method may further include:

[0070] If the motor current continuously exceeds the motor's overcurrent value and the duration exceeds the first preset duration, a sixth control command is sent to the vehicle controller, and the vehicle controller controls the motor to stop according to the sixth control command.

[0071] In practical applications, if the motor current exceeds the motor's overcurrent value for a duration longer than the first preset duration, it indicates that the hardware is damaged and self-recovery is not allowed. A sixth control command is then sent to the vehicle controller to stop the motor, facilitating timely maintenance of the motor.

[0072] In an optional embodiment, the method may further include: if the motor current exceeds the motor's overcurrent value, sending a seventh control command to the vehicle controller so that the vehicle controller adjusts the motor's operating parameters according to the seventh control command.

[0073] When a hardware overcurrent fault occurs in the motor, the MCU can upload the fault information to the VCU through the main control chip. The VCU can then limit the MCU's output torque via CAN commands, restrict the vehicle's speed, and activate the cooling system (such as a water pump or fan). In addition, the VCU can continuously monitor the fault to ensure the safety of the vehicle and the driver.

[0074] In one optional embodiment, determining a hardware overcurrent fault by indicating that the motor current exceeds the motor's overcurrent value may include:

[0075] Based on the current sensor parameters and motor current in the hardware circuit, determine the output voltage corresponding to the motor current;

[0076] If the output voltage is greater than the voltage threshold in the hardware circuit, it is determined that the motor current exceeds the motor's overcurrent value, and a hardware overcurrent fault has occurred.

[0077] The hardware circuit in this embodiment may include an operational amplifier circuit and a comparator circuit. The operational amplifier circuit is used to amplify the output voltage corresponding to the motor current to obtain the analog voltage value when the motor is overcurrent. The comparator circuit is used to compare the analog voltage with a voltage threshold. If the analog voltage value exceeds the voltage threshold, it is determined that the motor current exceeds the overcurrent value and a hardware overcurrent fault has occurred.

[0078] Exemplary device

[0079] Accordingly, this application also provides a motor overcurrent protection device. Figure 3 This is a structural block diagram of the motor overcurrent protection device provided in an embodiment of this application. Figure 3 As shown, the device may include:

[0080] Acquisition unit 320 is used to acquire the motor current of the motor;

[0081] The first sending unit 340 is used to determine that a hardware overcurrent fault has occurred if the motor current exceeds the motor's overcurrent value, and to send a first control command to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command.

[0082] The second sending unit 360 is used to send a second control command to the drive board controller if the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to the first preset duration, so that the drive board controller controls the switch to close according to the second control command, thereby realizing the motor's self-recovery.

[0083] The third sending unit 380 is used to generate a third control command to the vehicle controller if the number of self-recovery times of the motor within the second preset time period is greater than the preset number of times, so that the vehicle controller controls the motor to stop according to the third control command, and the second preset time period is greater than the first preset time period.

[0084] The motor overcurrent protection device provided in this embodiment belongs to the same concept as the motor overcurrent protection method provided in the above embodiments of this application. It can execute the motor overcurrent protection method provided in any of the above embodiments of this application and has the corresponding functional modules and beneficial effects for executing the motor overcurrent protection method. Technical details not described in detail in this embodiment can be found in the specific processing content of the motor overcurrent protection method provided in the above embodiments of this application, and will not be repeated here.

[0085] The functions implemented by the above-mentioned acquisition unit 320, first transmission unit 340, second transmission unit 360 and third transmission unit 380 can be implemented by the same or different processors, and this application embodiment does not limit them.

[0086] It should be understood that the acquisition unit 320, the first transmission unit 340, the second transmission unit 360, and the third transmission unit 380 in the above device can be implemented in the form of a processor calling software. For example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the device. The processor can be a general-purpose processor, such as a CPU or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units in the device can be implemented in the form of hardware circuits. By designing the hardware circuits, some or all of the unit functions can be implemented. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an ASIC, and the functions of some or all of the above units are implemented by designing the logical relationships of the components within the circuit. In another implementation, the hardware circuit can be implemented using a PLD, such as an FPGA, which can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file to implement the functions of some or all of the above units. All units of the above devices can be implemented entirely through processor calling software, or entirely through hardware circuits, or partially through processor calling software with the remaining parts implemented through hardware circuits.

[0087] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a CPU, microprocessor, GPU, or DSP. In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement the functions of some or all of the above units. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as an NPU, TPU, or DPU.

[0088] As can be seen, each unit in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0089] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a System-on-Chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0090] This application also provides a vehicle that includes the above-described motor overcurrent protection device.

[0091] Exemplary electronic devices

[0092] Another embodiment of this application also provides an electronic device, see [link to relevant documentation] Figure 4 As shown, the device includes:

[0093] Memory 400 and processor 410;

[0094] The memory 400 is connected to the processor 410 and is used to store programs;

[0095] The processor 410 is used to implement the motor overcurrent protection method disclosed in any of the above embodiments by running the program stored in the memory 400.

[0096] Specifically, the aforementioned electronic device may also include: a bus, a communication interface 420, an input device 430, and an output device 440.

[0097] The processor 410, memory 400, communication interface 420, input device 430, and output device 440 are interconnected via a bus. Among them:

[0098] A bus can include a pathway for transmitting information between various components of a computer system.

[0099] The processor 410 can be a general-purpose processor, such as a general-purpose central processing unit (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present invention. It can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0100] Processor 410 may include a main processor, as well as a baseband chip, modem, etc.

[0101] The memory 400 stores a program that executes the technical solution of this invention, and may also store an operating system and other key business functions. Specifically, the program may include program code, which includes computer operation instructions. More specifically, the memory 400 may include read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), other types of dynamic storage devices capable of storing information and instructions, disk storage, flash memory, etc.

[0102] Input device 430 may include a device for receiving user input data and information, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor.

[0103] Output device 440 may include devices that allow information to be output to a user, such as a display screen, printer, speaker, etc.

[0104] The communication interface 420 may include a device that uses any transceiver to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0105] The processor 410 executes the program stored in the memory 400 and calls other devices, which can be used to implement any of the steps of motor overcurrent protection provided in the above embodiments of this application.

[0106] This application also proposes a chip including a processor and a data interface. The processor reads and runs a program stored in a memory through the data interface to execute the motor overcurrent protection method described in any of the above embodiments. For the specific processing procedure and its beneficial effects, please refer to the above embodiments of the motor overcurrent protection method.

[0107] This exemplary computer program product and storage medium

[0108] In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps in the motor overcurrent protection methods according to various embodiments of this application as described in any of the above embodiments of this specification.

[0109] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0110] Furthermore, embodiments of this application may also be storage media storing a computer program, which is executed by a processor through steps in the motor overcurrent protection method according to various embodiments of this application described in any of the above embodiments of this specification. Specifically, the following steps can be implemented:

[0111] S210: Obtain the motor current of the motor;

[0112] S230: If the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined, and a first control command is sent to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command.

[0113] S250: If the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to the first preset duration, a second control command is sent to the drive board controller so that the drive board controller controls the switch to close according to the second control command, thereby realizing the motor's self-recovery.

[0114] S270: If the number of self-recovery cycles of the motor within the second preset time period is greater than the preset number, a third control command is generated to the vehicle controller so that the vehicle controller controls the motor to stop according to the third control command. The second preset time period is greater than the first preset time period.

[0115] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0116] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For apparatus embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0117] The steps in the methods of the various embodiments of this application can be adjusted, merged, or deleted in order according to actual needs, and the technical features described in each embodiment can be replaced or combined.

[0118] The modules and sub-modules in the various embodiments of the present application's devices and terminals can be merged, divided, and deleted according to actual needs.

[0119] It should be understood that the disclosed terminals, devices, and methods can be implemented in other ways, given the several embodiments provided in this application. For example, the terminal embodiments described above are merely illustrative. For instance, the division of modules or sub-modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple sub-modules or modules may be combined or integrated into another module, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0120] The modules or submodules described as separate components may or may not be physically separate. The components that constitute a module or submodule may or may not be physical modules or submodules; that is, they may be located in one place or distributed across multiple network modules or submodules. Some or all of the modules or submodules can be selected to achieve the purpose of this embodiment's solution, depending on actual needs.

[0121] Furthermore, the functional modules or sub-modules in the various embodiments of this application can be integrated into one processing module, or each module or sub-module can exist physically separately, or two or more modules or sub-modules can be integrated into one module. The integrated modules or sub-modules described above can be implemented in hardware or in the form of software functional modules or sub-modules.

[0122] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0123] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software unit executed by a processor, or a combination of both. The software unit can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0124] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0125] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for overcurrent protection of a motor, characterized in that, include: Obtain the motor current of the motor; If the motor current exceeds the motor's overcurrent value, a hardware overcurrent fault is determined, and a first control command is sent to the drive board controller, so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command. If the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to a first preset duration, a second control command is sent to the drive board controller, so that the drive board controller controls the switching transistor to close according to the second control command, thereby realizing the motor's self-recovery. If the number of self-recovery cycles of the motor within the second preset time period exceeds the preset number, a third control command is generated and sent to the vehicle controller, so that the vehicle controller controls the motor to stop according to the third control command, wherein the second preset time period is longer than the first preset time period; If the motor current exceeds the motor's overcurrent value, a fourth control command is sent to the vehicle controller, so that the vehicle controller records the hardware overcurrent fault information of the motor according to the fourth control command and clears the motor's torque to zero. If the number of self-recoveries of the motor within the second preset time period is less than or equal to the preset number, a fifth control command is sent to the vehicle controller and a sixth control command is sent to the drive board controller, so that the vehicle controller clears the hardware overcurrent fault information of the motor according to the fifth control command and increases the torque gradient of the motor to the target torque, and the drive board controller controls the switching transistor in the drive board to close according to the sixth control command. If the motor current is less than the motor's overcurrent value within a third preset time period from the moment the motor's torque gradient increases to the target torque, the number of self-recovery counts will be reset to zero.

2. The motor overcurrent protection method according to claim 1, characterized in that, The method further includes: If the motor current continuously exceeds the motor's overcurrent value and the duration exceeds the first preset duration, a sixth control command is sent to the vehicle controller, and the vehicle controller controls the motor to stop according to the sixth control command.

3. The motor overcurrent protection method according to claim 1, characterized in that, The preset number of times is 2.

4. The motor overcurrent protection method according to claim 1, characterized in that, The method further includes: If the motor current exceeds the motor's overcurrent value, A seventh control command is sent to the vehicle controller so that the vehicle controller adjusts the operating parameters of the motor according to the seventh control command.

5. The motor overcurrent protection method according to claim 1, characterized in that, The step of determining a hardware overcurrent fault if the motor current exceeds the motor's overcurrent value includes: Based on the current sensor parameters in the hardware circuit and the motor current, determine the output voltage corresponding to the motor current; If the output voltage is greater than the voltage threshold in the hardware circuit, it is determined that the motor current exceeds the overcurrent value of the motor, and a hardware overcurrent fault has occurred.

6. A motor overcurrent protection device, used to execute the motor overcurrent protection method according to any one of claims 1 to 5, characterized in that, include: Acquisition unit, used to acquire the motor current of the motor; The first sending unit is configured to determine that a hardware overcurrent fault has occurred if the motor current exceeds the motor's overcurrent value, and send a first control command to the drive board controller so that the drive board controller controls the switching transistor in the drive board to disconnect according to the first control command. The second sending unit is used to send a second control command to the drive board controller when the motor current continuously exceeds the motor's overcurrent value and the duration is less than or equal to a first preset duration, so that the drive board controller controls the switching transistor to close according to the second control command, thereby realizing the motor's self-recovery. The third sending unit is used to generate a third control command to the vehicle controller if the number of self-recoveries of the motor within a second preset time period is greater than a preset number, so that the vehicle controller controls the motor to stop according to the third control command, wherein the second preset time period is greater than the first preset time period.

7. A vehicle, characterized in that, Includes the motor overcurrent protection device as described in claim 6.

Images