Vehicle motor fault control method, device and system

Abstract

The invention discloses a vehicle motor fault control method, device and system, and the method comprises the steps: recognizing whether a target motor of a vehicle is at a first fault level, the first fault level is greater than or equal to a first preset level, and the first preset level is the minimum fault level affecting the dynamic property of the vehicle; under the condition that the target motor is at the first fault level, the fault recovery probability of the target motor is obtained, the fault recovery probability is the probability that a second fault level is smaller than or equal to a second preset level after the target motor is restarted, and when the second fault level is smaller than or equal to the second preset level, the dynamic property of the vehicle is not affected; and if the fault recovery probability is greater than or equal to a set probability threshold, controlling the target motor to restart. The influence on the dynamic property of the vehicle can be reduced as much as possible, and the user experience is improved.

Description

Technical Field

[0001] The present application belongs to the field of vehicle control technology, and in particular, relates to a vehicle motor fault control method, device and system. Background Art

[0002] During vehicle use, if the motor fails, it will affect the vehicle performance. Therefore, the quality of vehicle control after motor failure plays an important role in ensuring vehicle performance and improving user experience.

[0003] In some vehicle products, motor failure may be an occasional failure. In related technologies, occasional failures are mainly eliminated by restarting the motor. However, if the motor is restarted once it fails to eliminate the failure, it may affect the vehicle's power and thus affect the user experience to a certain extent. Summary of the invention

[0004] The embodiments of the present application provide a vehicle motor fault control method, device and system, which can minimize the impact on the vehicle's dynamic performance to at least a certain extent and improve the user experience.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to a first aspect of an embodiment of the present application, a vehicle motor fault control method is provided, comprising: Identifying whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; When the target motor is at the first fault level, obtaining a fault recovery probability of the target motor, the fault recovery probability being a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; If the fault recovery probability is greater than or equal to a set probability threshold, the target motor is controlled to restart.

[0007] In some embodiments of the present application, based on the above solution, the step of identifying whether the target motor of the vehicle is in the first fault level includes: Obtaining a target fault type and a target fault parameter of the target motor; Whether the target motor is in the first fault level is identified according to the target fault type and the target fault parameter.

[0008] In some embodiments of the present application, based on the above solution, identifying whether the target motor is in the first fault level according to the target fault type and the target fault parameter includes: Obtaining a mapping relationship table, wherein the mapping relationship table records multiple fault levels of the target motor, and a fault type and fault parameters corresponding to each fault level; Traversing the mapping relationship table to determine a target fault level corresponding to the target fault type and the target fault parameter; If the target fault level is greater than or equal to the first preset level, it is determined that the target motor is at the first fault level.

[0009] In some embodiments of the present application, based on the above solution, obtaining the fault recovery probability of the target motor includes: The fault recovery probability of the target motor is obtained from a cloud server, wherein the fault recovery probability is obtained by the cloud server based on a ratio between a historical restart recovery number and a historical fault number of multiple motors.

[0010] In some embodiments of the present application, based on the above solution, the vehicle includes a motor controller and a motor power supply, and the controlling the target motor to restart includes: Sending a restart instruction to the motor controller so that the motor controller controls the target motor to restart; or The motor power supply is controlled to start, so that the target motor is restarted.

[0011] In some embodiments of the present application, based on the above solution, before controlling the target motor to restart, the method further includes: According to the set corresponding relationship, determine the upper limit of the number of restarts corresponding to the fault recovery probability, wherein the upper limit of the number of restarts is the upper limit of the number of restarts of the target motor after the current fault, and the fault recovery probability is negatively correlated with the upper limit of the number of restarts; The controlling the target motor to restart includes: The target motor is controlled to restart within the upper limit of the restart times.

[0012] In some embodiments of the present application, based on the above solution, controlling the target motor to restart includes: When the throttle depth of the vehicle is less than or equal to a depth threshold, the target motor is controlled to restart.

[0013] According to a second aspect of an embodiment of the present application, a vehicle motor fault control device is provided, comprising: an identification unit, configured to identify whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; an acquisition unit, configured to acquire a fault recovery probability of the target motor when the target motor is at the first fault level, wherein the fault recovery probability is a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; A control unit is used to control the target motor to restart if the fault recovery probability is greater than or equal to a set probability threshold.

[0014] According to a third aspect of an embodiment of the present application, a vehicle motor fault control system is provided, including a vehicle controller and a cloud server, wherein the cloud server is communicatively connected to the vehicle controller, and the vehicle controller is used to: Identifying whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; When the target motor is at the first fault level, obtaining a fault recovery probability of the target motor from the cloud server, wherein the fault recovery probability is a probability that a second fault level of the target motor after restart is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; If the fault recovery probability is greater than or equal to a set probability threshold, the target motor is controlled to restart.

[0015] In some embodiments of the present application, based on the above solution, the cloud server is used to: Get the historical restart recovery times and historical fault times of multiple motors; The failure recovery probability is obtained according to the ratio between the historical restart recovery number and the historical failure number.

[0016] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein at least one computer program instruction is stored in the computer-readable storage medium, and the at least one computer program instruction is loaded and executed by a processor to implement the operations performed by any method described in the first aspect.

[0017] According to the fifth aspect of an embodiment of the present application, an electronic device is provided, comprising one or more processors and one or more memories, wherein at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by any of the methods described in the first aspect.

[0018] One or more technical solutions provided by the embodiments of the present invention achieve at least the following technical effects or advantages: In the present application, it is identified whether the target motor of the vehicle is in the first fault level, the first fault level is greater than or equal to the first preset level, and the first preset level is the minimum fault level that affects the power of the vehicle; when the target motor is in the target fault level, the fault recovery probability of the target motor is obtained, and the fault recovery probability is the probability that the second fault level after the target motor is restarted is less than or equal to the second preset level, wherein, when the second fault level is less than or equal to the second preset level, the power of the vehicle is not affected; if the fault recovery probability is greater than or equal to the set probability threshold, the target motor is controlled to restart. Therefore, the present application does not restart the drive motor when the fault level is low, and when the fault recovery probability of the target motor (the probability of the fault recovery to be less than or equal to the second preset level) is greater than the set probability threshold, the target motor is controlled to restart to eliminate occasional faults, thereby minimizing the impact on the power of the vehicle and improving the user experience.

[0019] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings: Figure 1 A flow chart showing a vehicle motor fault control method according to an embodiment of the present application is shown; Figure 2 A structural diagram of a vehicle motor failure control device according to an embodiment of the present application is shown; Figure 3 A structural diagram of a vehicle motor fault control system according to an embodiment of the present application is shown; Figure 4 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0022] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0023] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0024] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0025] It should also be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the objects used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those shown or described.

[0026] See also Figure 1 , shows a flow chart of a vehicle motor fault control method according to an embodiment of the present application.

[0027] According to a first aspect of an embodiment of the present application, a vehicle motor fault control method is provided, which can be executed in a vehicle controller, and the method includes: Step S1. Identify whether a target motor of a vehicle is in a first fault level, where the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; It can be understood that in the embodiment of the present application, the motor mainly refers to the drive side motor that has an impact on the vehicle's dynamics. Different models can be equipped with different types of motors, wherein the motor types include but are not limited to P1 motors, P2 motors, P3 motors and P4 motors. For example, in the embodiment of the present application, a hybrid vehicle is used, and the hybrid vehicle is provided with a P1 motor and a P3 motor, wherein the generator adopts a P1 motor, and the drive motor adopts a P3 motor. The P1 motor is located at the sun gear of the planetary gear set, and the engine is located at the planet carrier. The transmission path from the P1 motor to the engine is: P1 motor-planet carrier-torque damper-engine. The P1 motor can make the transmission efficiency of the engine high, assist the engine to start and stop, provide power assistance for the engine, improve the vehicle torque, increase the driving experience, and realize kinetic energy recovery. The P3 motor is arranged at the rear end of the hybrid gearbox, located after the differential, and shares the same output shaft with the engine, and works on the vehicle together, realizing the effect of separating the engine and the motor, and driving the vehicle alone, with high power output efficiency and high kinetic energy recovery efficiency.

[0028] Based on the above, the target motor may be one or more of a P1 motor, a P2 motor, a P3 motor or a P4 motor.

[0029] It is understandable that the embodiments of the present application can pre-calibrate various fault levels corresponding to motor faults, thereby providing data support for quickly identifying the fault level of the target motor during actual vehicle operation.

[0030] It should be noted that the purpose of the embodiment of the present application to identify the situation where the target motor is in the first fault level is: since the first preset level is the minimum fault level that affects the power of the vehicle, if the target motor is in the first fault level greater than or equal to the first preset level, it means that the current fault of the target motor will more or less affect the power of the vehicle, so it is necessary to take certain measures to eliminate or reduce the fault. If the target motor currently has no fault or the fault is less than the first preset level, it means that the current fault of the target motor will not affect the power of the vehicle. In order to reduce the impact of the motor restart on the power of the vehicle, when the fault level of the target motor is less than the first preset level, the target motor is not processed, for example, the target motor continues to operate according to the current operating parameters.

[0031] In some embodiments, the step of identifying whether the target motor of the vehicle is in a first fault level includes: Step S11. Obtaining a target fault type and target fault parameters of the target motor; It should be noted that for a certain type of motor, the motor fault types include but are not limited to motor phase overcurrent fault, motor overvoltage fault, motor torque fault, motor state fault, motor resolver fault, etc. Different fault types may have different corresponding fault parameter ranges. For example, the motor output power range corresponding to the motor phase overcurrent fault is the first range, and the motor output power range corresponding to the motor overvoltage fault is the second range. The first range and the second range may not overlap, or may partially overlap.

[0032] It is understandable that the motor fault type and fault parameters can be reported by the motor controller itself, or other controllers can perform motor fault diagnosis. For example, the vehicle controller diagnoses the motor torque fault. For example, the difference between the motor torque requested by the vehicle controller to the motor controller and the actual motor output torque exceeds the set threshold. Suppose the requested motor torque is 100 Nm and the actual motor output torque is 130 Nm, which exceeds the set threshold by 20 Nm. Therefore, there is a motor torque fault. For another example, the vehicle controller diagnoses the motor state fault. Suppose the requested motor state is power generation and the actual motor state is power consumption, then the requested motor state is inconsistent with the actual motor state. Therefore, there is a motor state fault.

[0033] Step S12: Identify whether the target motor is in the first fault level according to the target fault type and the target fault parameter.

[0034] In some embodiments, the identifying, according to the target fault type and the target fault parameter, whether the target motor is in the first fault level includes: Step S121. Obtain a mapping relationship table, wherein the mapping relationship table records multiple fault levels of the target motor, and a fault type and fault parameters corresponding to each fault level; It is understandable that there may be multiple motors in the same vehicle, and there may be multiple models for the same motor. For example, for the P1 motor, there may be model A, model B and model C, and different models of motors may have different representations when a motor failure occurs, such as different fault parameters, etc. Therefore, in an embodiment of the present application, the fault parameters and fault levels can be calibrated in advance for each model of motor, thereby providing data support for the determination of the motor fault level during actual vehicle operation.

[0035] For ease of understanding, the mapping relationship between the fault level, the fault type and the fault parameter is described below through Table 1.

[0036] Table 1 Mapping relationship between fault level, fault type and fault parameters As can be seen from Table 1, the fault level of the motor is divided into 3 levels, where level 1 may indicate a minor fault, the vehicle's power is not affected, level 2 may indicate a moderate fault, the vehicle's power is limited, and level 3 may indicate a serious fault, the vehicle's power is impaired. Of course, it is understandable that when multiple motors of a vehicle have faults, the maximum fault level of the multiple motors can be used as the maximum fault level of the vehicle to determine the overall impact on the vehicle's power.

[0037] Step S122. Traverse the mapping relationship table to determine the target fault level corresponding to the target fault type and the target fault parameter; Step S123: If the target fault level is greater than or equal to the first preset level, determine that the target motor is at the first fault level.

[0038] For example, if the first preset level is level 2 fault, then when the target fault level is greater than or equal to level 2, it indicates that the target motor is at the first fault level.

[0039] In addition, it can be understood that in the embodiments of the present application, the target fault level can also be determined by means of a function mapping model, a fault level prediction model, etc., which will not be explained one by one here.

[0040] Step S2. When the target motor is at the first fault level, obtain a fault recovery probability of the target motor, wherein the fault recovery probability is a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the dynamic performance of the vehicle is not affected; It is understandable that for some occasional faults of the motor, the occasional fault can be eliminated by restarting the motor. However, since the power of the vehicle will be affected during the motor restart process, if the occasional fault is eliminated by restarting the motor, or by continuously restarting the motor, the vehicle power will be affected and the occasional fault cannot be eliminated, resulting in a poor user experience. Based on this, in the embodiment of the present application, when the target motor is at the first fault level, the fault recovery probability of the target motor is obtained, and then based on the fault recovery probability, it is determined whether to restart the motor, so as to improve the success rate of eliminating the occasional fault after the motor is restarted to a certain extent.

[0041] It should be noted that the fault recovery probability of the embodiment of the present application refers to the probability that the fault level of the motor is reduced to below the second preset level (including the second preset level) after restarting. For example, the second preset level is level 1, which means a minor fault. Then, after the motor is restarted, if the fault level is less than or equal to level 1, it means that there will be no impact on the vehicle's power, so the vehicle can continue to operate stably.

[0042] In some embodiments, obtaining the fault recovery probability of the target motor includes: The fault recovery probability of the target motor is obtained from a cloud server, wherein the fault recovery probability is obtained by the cloud server based on a ratio between a historical restart recovery number and a historical fault number of multiple motors.

[0043] It is understandable that the cloud server can continuously collect and count the historical failure conditions and historical restart and recovery conditions of several motors installed in different vehicles, so as to obtain the probability of the target motor being able to recover after a failure when installed in different vehicles based on big data statistics.

[0044] Among them, if the motor fails while the vehicle's power state is in the starting state, it is recorded as one fault. After the vehicle's power state switches from starting to off and then to starting (i.e. restarting), if the fault is eliminated, it is a restart recovery.

[0045] It can be understood that the fault recovery probability refers to the fault recovery probability of a certain fault type of the motor, that is, each fault type has a corresponding fault recovery probability. For example, if the vehicle has 10 motor phase overcurrent faults in the power-on state, and the phase overcurrent fault is eliminated 5 times after switching from the start state to the flameout state and then to the start state, the probability of restarting and recovering from the motor phase overcurrent fault is calculated to be 50%.

[0046] It is understandable that as the vehicle's running time accumulates, the historical fault counts and historical restart recovery counts of each motor are also dynamically updated. Therefore, the fault recovery probability is also a dynamically updated value. For example, at time A, the fault recovery probability of the target motor's over-phase flow fault is 50%, and at time B, the fault recovery probability of the target motor's over-phase flow fault is 40%. Therefore, through the continuous accumulation of the motor's historical fault counts and historical restart recovery counts, the fault recovery probability can more and more accurately reflect the actual fault recovery probability corresponding to a certain fault type of the same model of target motor, thereby making the subsequent motor restart control more accurate.

[0047] Step S3: If the fault recovery probability is greater than or equal to a set probability threshold, control the target motor to restart.

[0048] For example, the failure recovery probability is greater than or equal to 20%, 30%, 40%, etc. The specific setting can be based on actual needs and is not limited here.

[0049] In some embodiments, the vehicle includes a motor controller and a motor power supply, and the controlling the target motor to restart includes: Sending a restart instruction to the motor controller so that the motor controller controls the target motor to restart; or The motor power supply is controlled to start, so that the target motor is restarted.

[0050] For example: the vehicle controller VCU sends a CAN signal command to control the motor controller to restart (i.e., control the motor controller to reset) or to control the motor power to start so that the target motor restarts.

[0051] In some embodiments, before controlling the target motor to restart, the method further includes: According to the set corresponding relationship, determine the upper limit of the number of restarts corresponding to the fault recovery probability, wherein the upper limit of the number of restarts is the upper limit of the number of restarts of the target motor after the current fault, and the fault recovery probability is negatively correlated with the upper limit of the number of restarts; It is understandable that for the target motor, if it is necessary to eliminate occasional faults by continuous restarting, then if the number of restarts is too many, it may lead to a poor user experience. Therefore, the embodiment of the present application establishes a corresponding relationship between the fault recovery probability and the upper limit of the number of restarts of the motor, so that when the motor is subsequently restarted, the motor can be restarted within the upper limit of the restart number, avoiding too many times and causing user dissatisfaction.

[0052] The negative correlation between the fault recovery probability and the upper limit of the restart times can be: within a certain range of times, the greater the fault recovery probability, the smaller the upper limit of the restart times, and the smaller the fault recovery probability, the greater the upper limit of the restart times. For example: if the fault recovery probability is 50%, the upper limit of the control motor restart times is 2 times; if the probability of fault elimination after fault restart is 25%, the upper limit of the control motor restart times is 4 times.

[0053] The controlling the target motor to restart includes: The target motor is controlled to restart within the upper limit of the restart times.

[0054] For example: The upper limit of the number of restarts of the target motor is 3. If it restarts once, twice or three times, If the motor fault is restored, the motor will be enabled. If the motor fault is not restored after three restarts, the motor will no longer be controlled to restart.

[0055] In some embodiments, controlling the target motor to restart includes: When the throttle depth of the vehicle is less than or equal to a depth threshold, the target motor is controlled to restart.

[0056] It is understandable that before the motor restarts, if the throttle depth of the vehicle is too large, the vehicle may suddenly accelerate after the motor restarts, thus posing a safety hazard. Based on this, before controlling the target motor to restart, the throttle depth can be identified. If the throttle depth is too large, for example, greater than 10%, the throttle depth can be adjusted. When the throttle depth is less than or equal to the depth threshold, for example, less than 10%, the target motor is controlled to restart, thereby avoiding sudden acceleration of the vehicle after restarting and improving driving safety.

[0057] Based on the above disclosed content, in an embodiment of the present application, it is identified whether the target motor of the vehicle is in the first fault level, the first fault level is greater than or equal to the first preset level, and the first preset level is the minimum fault level that affects the power of the vehicle; when the target motor is in the target fault level, the fault recovery probability of the target motor is obtained, and the fault recovery probability is the probability that the second fault level after the target motor is restarted is less than or equal to the second preset level, wherein, when the second fault level is less than or equal to the second preset level, the power of the vehicle is not affected; if the fault recovery probability is greater than or equal to the set probability threshold, the target motor is controlled to restart. Therefore, the present application does not restart the drive motor when the fault level is low, and when the fault recovery probability of the target motor (the probability of the fault recovery to be less than or equal to the second preset level) is greater than the set probability threshold, the target motor is controlled to restart to eliminate occasional faults, thereby minimizing the impact on the power of the vehicle and improving the user experience.

[0058] See also Figure 2 , shows a structural diagram of a vehicle motor fault control device according to an embodiment of the present application.

[0059] According to a second aspect of an embodiment of the present application, a vehicle motor failure control device 200 is provided, comprising: An identification unit 201, used to identify whether a target motor of a vehicle is in a first fault level, where the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; an acquisition unit 202, configured to acquire a fault recovery probability of the target motor when the target motor is at the first fault level, wherein the fault recovery probability is a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the dynamic performance of the vehicle is not affected; The control unit 203 is configured to control the target motor to restart if the fault recovery probability is greater than or equal to a set probability threshold.

[0060] See also Figure 3 , shows a structural diagram of a vehicle motor fault control system according to an embodiment of the present application.

[0061] According to a third aspect of an embodiment of the present application, a vehicle motor fault control system is provided, including a vehicle controller 10 and a cloud server 20, wherein the cloud server 20 is communicatively connected to the vehicle controller 10, for example, through a vehicle-mounted communication terminal TBOX, and the vehicle controller 10 is used to: Identifying whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; When the target motor is at the first fault level, obtaining a fault recovery probability of the target motor from the cloud server 20, wherein the fault recovery probability is a probability that a second fault level of the target motor after restart is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the dynamic performance of the vehicle is not affected; If the fault recovery probability is greater than or equal to a set probability threshold, the target motor is controlled to restart.

[0062] In some embodiments of the present application, based on the above solution, the cloud server 20 is used to: Get the historical restart recovery times and historical fault times of multiple motors; The failure recovery probability is obtained according to the ratio between the historical restart recovery number and the historical failure number.

[0063] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein at least one computer program instruction is stored in the computer-readable storage medium, and the at least one computer program instruction is loaded and executed by a processor to implement the operations performed by any method described in the first aspect.

[0064] The computer readable storage medium may be a portable compact disk read-only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the computer readable storage medium of the present application is not limited thereto, and in the present application, the readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, apparatus, or device.

[0065] The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more conductors, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0066] Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0067] See also Figure 4 , which is a schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application.

[0068] According to the fifth aspect of an embodiment of the present application, an electronic device is provided, comprising one or more processors and one or more memories, wherein at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by any of the methods described in the first aspect.

[0069] The electronic device 400 is in the form of a general-purpose computing device. The components of the electronic device 400 may include, but are not limited to: the at least one processing unit 410, the at least one storage unit 420, and a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410).

[0070] The storage unit stores program codes, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps described in the above “Embodiment Method” section of this specification according to various exemplary implementations of the present application.

[0071] The storage unit 420 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 421 and / or a cache 422 , and may further include a read-only memory unit (ROM) 423 .

[0072] The storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0073] Bus 430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0074] The electronic device 400 may also communicate with one or more external devices 500 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 400, and / or communicate with any device that enables the electronic device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed through an I / O (input / output) interface 450, wherein the I / O interface 450 may also be connected to a display unit 440, and the communication content may be displayed through the display unit 440. In addition, the electronic device 400 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 460. As shown in the figure, the network adapter 460 communicates with other modules of the electronic device 400 through a bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0075] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium or transmitted via a computer-readable medium. Other examples and implementations are within the scope and spirit of the present invention and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. In addition, each functional unit may be integrated into a processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

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

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

[0078] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which 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 of each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc., which can store program code.

[0079] The above description is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.

Claims

1. A vehicle motor fault control method, characterized in that: include: Identifying whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; When the target motor is at the first fault level, obtaining a fault recovery probability of the target motor, the fault recovery probability being a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; If the fault recovery probability is greater than or equal to a set probability threshold, the target motor is controlled to restart.

2. The method according to claim 1, characterized in that The identifying whether the target motor of the vehicle is in a first fault level includes: Obtaining a target fault type and a target fault parameter of the target motor; Whether the target motor is in the first fault level is identified according to the target fault type and the target fault parameter.

3. The method according to claim 2, characterized in that The step of identifying whether the target motor is in the first fault level according to the target fault type and the target fault parameter includes: Obtaining a mapping relationship table, wherein the mapping relationship table records multiple fault levels of the target motor, and a fault type and fault parameters corresponding to each fault level; Traversing the mapping relationship table to determine a target fault level corresponding to the target fault type and the target fault parameter; If the target fault level is greater than or equal to the first preset level, it is determined that the target motor is at the first fault level.

4. The method according to claim 1, characterized in that: The obtaining of the fault recovery probability of the target motor includes: The fault recovery probability of the target motor is obtained from a cloud server, wherein the fault recovery probability is obtained by the cloud server based on a ratio between a historical restart recovery number and a historical fault number of multiple motors.

5. The method according to claim 1, characterized in that The vehicle includes a motor controller and a motor power supply, and the controlling the target motor to restart includes: Sending a restart instruction to the motor controller so that the motor controller controls the target motor to restart; or The motor power supply is controlled to start, so that the target motor is restarted.

6. The method according to claim 1, characterized in that Before controlling the target motor to restart, the method further includes: According to the set corresponding relationship, determine the upper limit of the number of restarts corresponding to the fault recovery probability, wherein the upper limit of the number of restarts is the upper limit of the number of restarts of the target motor after the current fault, and the fault recovery probability is negatively correlated with the upper limit of the number of restarts; The controlling the target motor to restart includes: The target motor is controlled to restart within the upper limit of the restart times.

7. The method according to claim 1, characterized in that The controlling the target motor to restart includes: When the throttle depth of the vehicle is less than or equal to a depth threshold, the target motor is controlled to restart.

8. A vehicle motor fault control device, characterized in that: include: an identification unit, configured to identify whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; an acquisition unit, configured to acquire a fault recovery probability of the target motor when the target motor is at the first fault level, wherein the fault recovery probability is a probability that a second fault level of the target motor after restarting is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; A control unit is used to control the target motor to restart if the fault recovery probability is greater than or equal to a set probability threshold.

9. A vehicle motor fault control system, characterized in that: It includes a vehicle controller and a cloud server, wherein the cloud server is in communication connection with the vehicle controller, and the vehicle controller is used for: Identifying whether a target motor of a vehicle is in a first fault level, wherein the first fault level is greater than or equal to a first preset level, and the first preset level is a minimum fault level that affects the power of the vehicle; When the target motor is at the first fault level, obtaining a fault recovery probability of the target motor from the cloud server, wherein the fault recovery probability is a probability that a second fault level of the target motor after restart is less than or equal to a second preset level, wherein when the second fault level is less than or equal to the second preset level, the power performance of the vehicle is not affected; If the fault recovery probability is greater than or equal to a set probability threshold, the target motor is controlled to restart.

10. The system according to claim 9, characterized in that The cloud server is used for: Get the historical restart recovery times and historical fault times of multiple motors; The failure recovery probability is obtained according to the ratio between the historical restart recovery number and the historical failure number.

Images