Fault processing method and system, vehicle, and storage medium

Abstract

Disclosed are a fault processing method and system, a vehicle, and a storage medium. The fault processing method comprises: performing fault detection on a fuel pump controller of a vehicle to obtain a fault detection result; determining a fault type on the basis of the fault detection result; outputting a fault control signal on the basis of the fault type, wherein the fault control signal is set to reduce a level signal on a signal input side of the fuel pump controller; and in response to the fault control signal output, determining a fault processing measure on the basis of the fault control signal.

Description

Fault handling method, system, vehicle and storage medium

[0001] Cross-reference

[0002] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on December 14, 2023, with application number 2023117281586 and application name “Fault Handling Method, System, Vehicle and Storage Medium,” the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present disclosure belongs to the technical field of fault handling, and in particular, relates to a fault handling method, system, vehicle, and storage medium. Background Art

[0004] The fuel pump in a traditional fuel vehicle is generally directly connected to the vehicle power supply to pump oil at the maximum speed. Its NVH noise is relatively large and its power consumption is also high. In fact, under certain working conditions with low vehicle load, the fuel pump does not need to supply fuel at the maximum speed. Therefore, a technical solution of on-demand fuel supply has emerged, which is to add a fuel pump controller solution. The fuel pump speed is reduced by adjusting the system demand, achieving many benefits such as reducing NVH noise, reducing oil pump power, and reducing fuel consumption.

[0005] In existing fuel pump controller technology, there is little research on subsequent treatment measures when the fuel pump controller detects a fault. The imperfect treatment method increases the risk of engine stalling due to insufficient fuel supply while the vehicle is driving.

[0006] Summary of the Invention

[0007] The embodiments of the present disclosure provide a fault handling method, system, vehicle, and storage medium to at least solve the technical problem in the prior art of an incomplete handling method when a fuel pump controller detects a fault.

[0008] According to a first aspect of an embodiment of the present disclosure, a fault handling method is provided, comprising: performing fault detection on a vehicle fuel pump controller to obtain a fault detection result; determining a fault type based on the fault detection result; outputting a fault control signal based on the fault type, wherein the fault control signal is configured to lower the level of a signal on a signal input side of the fuel pump controller; and determining a fault handling measure based on the fault control signal in response to the output of the fault control signal.

[0009] Optionally, performing fault detection on the vehicle fuel pump controller to obtain a fault detection result includes: performing fault detection on the vehicle fuel pump controller according to a preset fault detection rule comparison table, wherein the preset fault detection rule comparison table includes multiple fault determination rules, and each preset fault detection rule corresponds to a fault type; in response to the vehicle fuel pump controller satisfying any fault determination rule, determining the fault detection result according to the corresponding fault determination rule.

[0010] Optionally, outputting a fault control signal according to the fault type includes: determining a fault priority according to the fault type; and determining a fault control signal according to the fault priority, wherein the fault control signal includes a duration period for reducing the level signal on the signal input side of the fuel pump controller.

[0011] Optionally, determining the fault priority according to the fault type includes: in response to there being multiple fault types, determining a to-be-selected fault priority corresponding to each fault type to obtain a fault priority set; and selecting the largest to-be-selected fault priority from the fault priority set as the fault priority.

[0012] Optionally, the fault types include: fuel pump controller internal fault, fuel pump controller overtemperature fault, fuel pump controller oil pump side fault, and pulse width modulation line fault.

[0013] Optionally, after the step of determining fault handling measures based on the fault control signal in response to the output of the fault control signal, the method further includes: performing real-time fault detection on the vehicle fuel pump controller to obtain real-time fault detection results; and stopping outputting the fault control signal in response to the real-time fault detection results indicating that there is no fault in the vehicle fuel pump controller.

[0014] Optionally, the fault handling method also includes: in response to the vehicle being powered on, clearing historical fault detection results, wherein the historical fault detection results are the fault detection results for the vehicle fuel pump controller when the vehicle was last powered on; in response to the historical fault detection results being cleared, performing a fault detection on the vehicle fuel pump controller to obtain a fault detection result.

[0015] According to a second aspect of an embodiment of the present disclosure, a fault handling system is further provided, including:

[0016] The detection module is configured to perform fault detection on the vehicle fuel pump controller to obtain a fault detection result; the determination module is configured to determine the fault type based on the fault detection result; the output module is configured to output a fault control signal based on the fault type, wherein the fault control signal is configured to reduce the level signal on the signal input side of the fuel pump controller; and the control module is configured to respond to the fault control signal output and determine the fault handling measures based on the fault control signal.

[0017] Optionally, the detection module is further configured to: perform fault detection on the vehicle fuel pump controller according to a preset fault detection rule comparison table, wherein the preset fault detection rule comparison table includes multiple fault determination rules, and each preset fault detection rule corresponds to a fault type; in response to the vehicle fuel pump controller satisfying any fault determination rule, determine the fault detection result according to the corresponding fault determination rule.

[0018] Optionally, the output module is further configured to: determine a fault priority according to the fault type; and determine a fault control signal according to the fault priority, wherein the fault control signal includes a duration period for reducing the level signal on the signal input side of the fuel pump controller.

[0019] Optionally, the determination module is further configured to: in response to multiple fault types, determine the to-be-selected fault priority corresponding to each fault type to obtain a fault priority set; and select the largest to-be-selected fault priority from the fault priority set as the fault priority.

[0020] Optionally, the fault type determined by the determination module includes: internal fault of the fuel pump controller, over-temperature fault of the fuel pump controller, fuel pump side fault of the fuel pump controller, and pulse width modulation line fault.

[0021] Optionally, the detection module is further configured to: perform real-time fault detection on the vehicle fuel pump controller to obtain a real-time fault detection result; and stop outputting the fault control signal in response to the real-time fault detection result indicating that there is no fault in the vehicle fuel pump controller.

[0022] Optionally, the detection module is further configured to: clear historical fault detection results in response to vehicle power-on, wherein the historical fault detection results are the fault detection results for the vehicle fuel pump controller when the vehicle was last powered on; and perform fault detection on the vehicle fuel pump controller to obtain a fault detection result in response to the historical fault detection results being cleared.

[0023] According to a third aspect of an embodiment of the present disclosure, a vehicle is also provided, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the fault handling method described in any embodiment of the first aspect above.

[0024] According to a fourth aspect of an embodiment of the present disclosure, a non-volatile storage medium is further provided, in which a computer program is stored, wherein the computer program is configured to execute the fault handling method described in any embodiment of the first aspect when running on a computer or processor.

[0025] In an embodiment of the present disclosure, a vehicle fuel pump controller is subjected to fault detection to obtain a fault detection result; a fault type is determined based on the fault detection result; a fault control signal is output based on the fault type, wherein the fault control signal is configured to reduce the level of the signal input to the fuel pump controller; and in response to the output of the fault control signal, a fault handling measure is determined based on the fault control signal. By determining the fault control signal based on the fault type and then determining the fault handling measure based on the fault signal, the present disclosure provides more comprehensive handling when a fuel pump controller detects a fault, thereby resolving the technical problem of inadequate handling methods for detecting a fault in a fuel pump controller in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] FIG1 is a flow chart of a fault handling method according to one embodiment of the present disclosure;

[0028] FIG2 is a diagram showing a system configuration applicable to a fault handling method according to one embodiment of the present disclosure;

[0029] FIG3 is a schematic diagram of a portion of an interface circuit of a system applicable to a fault handling method according to one embodiment of the present disclosure;

[0030] FIG4 is a schematic structural diagram of a fuel pump controller according to one embodiment of the present disclosure;

[0031] FIG5 is a structural block diagram of a fault handling system according to one embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present disclosure.

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

[0034] According to an embodiment of the present disclosure, an embodiment of a fault handling method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system containing at least one set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0035] The method embodiment can also be executed in an electronic device including a memory and a processor, a similar control device, or the cloud. Taking an electronic device as an example, the electronic device may include one or more processors and a memory configured to store data. Optionally, the electronic device may also include a communication device configured to have a communication function and a display device. It will be understood by those skilled in the art that the above structural description is only illustrative and does not limit the structure of the above electronic device. For example, the electronic device may also include more or fewer components than those described in the above structural description, or have a configuration different from that described in the above structural description.

[0036] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a programmable logic device (field-programmable gate array, FPGA), a neural network processor (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, and the like. Among them, different processing units may be independent components or integrated into one or more processors. In some instances, the electronic device may also include one or more processors.

[0037] The memory may be configured to store a computer program, such as a computer program corresponding to the fault handling method in the embodiment of the present disclosure, and the processor implements the above-mentioned fault handling method by running the computer program stored in the memory. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely located relative to the processor, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0038] The communication device is configured to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the communication device includes a network adapter (network interface controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the communication device can be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly. In some embodiments of the present solution, the communication device is configured to be connected to a mobile device such as a mobile phone or a tablet, and instructions can be sent to the electronic device through the mobile device.

[0039] The display device may be a touchscreen-type liquid crystal display (LCD) or a touch display (also referred to as a "touch screen" or "touch display"). The LCD may enable a user to interact with a user interface of the electronic device. In some embodiments, the electronic device may include a graphical user interface (GUI), and a user may interact with the GUI by touching a touch-sensitive surface with a finger and / or performing gestures. Executable instructions configured to perform the aforementioned human-computer interaction functions are configured / stored in a computer program product or readable storage medium executable by one or more processors.

[0040] It should be noted that, with reference to Figure 2, the method described in the following embodiments is applicable to the system configuration shown in Figure 2. It comprises an engine management system (EMS), a fuel pump controller (PEM), a fuel pressure sensor (FPS), and a fuel pump (FP). The EMS is responsible for collecting vehicle load information and issuing a pump speed demand command to the fuel pump controller. This command is a PWM (pulse-width modulation) signal with a fixed frequency and a variable duty cycle. Different duty cycles correspond to different fuel pump speeds. The fuel pump controller receives this PWM signal, identifies the duty cycle, and then outputs the corresponding PWM signal to the fuel pump via PWM. This adjusts the average effective voltage across the fuel pump and, in turn, the fuel pump speed. A linear relationship exists between the PWM signal received by the fuel pump controller and the PWM signal output to the fuel pump, or the target fuel pump speed, determined through bench testing. Changes in fuel pump speed cause changes in fuel pressure, which in turn changes the output value of the fuel pressure sensor. The EMS reads this sensor value to establish closed-loop control of the fuel system.

[0041] FIG1 is a flow chart of a fault handling method according to one embodiment of the present disclosure. As shown in FIG1 , the method includes the following steps:

[0042] Step S101 : performing a fault detection on a vehicle fuel pump controller to obtain a fault detection result.

[0043] Specifically, the fault detection system configured on the vehicle can detect faults on the signal input side of the vehicle fuel controller, faults on the vehicle fuel controller itself, and faults on the output side of the vehicle fuel pump.

[0044] It should be noted that the above fault detection process can be completed by the vehicle fuel pump itself.

[0045] Step S102: Determine the fault type according to the fault detection result.

[0046] Specifically, after the fault detection result is detected in the above step S101, the fault type of the fuel pump controller can be determined according to the fault detection result.

[0047] For example, if the fault result indicates that the fault of the fuel pump controller is a fuel pump controller overtemperature fault, then the fault type corresponding to the fault is a fuel pump controller self-fault.

[0048] Step S103: outputting a fault control signal according to the fault type, wherein the fault control signal is configured to reduce the level of the signal input side of the fuel pump controller.

[0049] Specifically, after the fault type is determined in step S102 , a fault control signal corresponding to the fault type is determined according to the fault type, that is, different fault types correspond to different fault control signals.

[0050] It should be noted that the various fault control signals all function to reduce the level of the signal input to the fuel pump controller. This reduction in level is configured to notify the engine management system of a fuel pump controller fault.

[0051] It should be noted that the fuel pump controller's hardware circuitry requires support from pull-up resistors and components capable of pulling down the voltage level (such as transistors). Referring to Figure 3, which is a schematic diagram of a portion of the interface circuitry of a system applicable to a fault handling method according to one embodiment of the present disclosure, the engine management system continuously controls the on and off times of transistor T1 to generate a PWM signal duty cycle output. Simultaneously, the AD port continuously monitors changes in the voltage level on the PWM signal line to determine whether the fuel pump controller has signaled a fault. Resistor R1 acts as a current-limiting resistor, while resistor R2 acts as a pull-up resistor and also serves as a current-limiting resistor. The fuel pump controller uses the MCU to identify the input duty cycle signal to regulate the fuel pump. When a fault is detected, it controls transistor T2 to ground. This way, regardless of whether T1 is on or off, the signal line remains at a low level, allowing the engine management system to determine that the fuel pump controller has signaled a fault. It should be noted that pull-up resistor R2 can be provided by either the engine management system or the fuel pump controller.

[0052] Step S104 : In response to the output of the fault control signal, a fault handling measure is determined according to the fault control signal.

[0053] Specifically, after detecting the output of the fault control signal, it can be determined that the fuel pump controller has failed, and then the fault handling measures are determined according to the fault type carried by the fault control signal.

[0054] It should be noted that different fault types correspond to different fault handling measures.

[0055] In an embodiment of the present disclosure, a vehicle fuel pump controller is subjected to fault detection to obtain a fault detection result; a fault type is determined based on the fault detection result; a fault control signal is output based on the fault type, wherein the fault control signal is configured to reduce the level of the signal input to the fuel pump controller; and in response to the output of the fault control signal, a fault handling measure is determined based on the fault control signal. By determining the fault control signal based on the fault type and then determining the fault handling measure based on the fault signal, the present disclosure provides more comprehensive handling when a fuel pump controller detects a fault, thereby resolving the technical problem of inadequate handling methods for detecting a fault in a fuel pump controller in the prior art.

[0056] Optionally, in step S101, performing fault detection on the vehicle fuel pump controller to obtain a fault detection result may include the following steps:

[0057] Step S1011 , performing fault detection on the vehicle fuel pump controller according to a preset fault detection rule comparison table, wherein the preset fault detection rule comparison table includes multiple fault determination rules, and each preset fault detection rule corresponds to a fault type.

[0058] For example, the preset fault detection rule comparison table is shown in Table 1:

[0059] Table 1

[0060] It is understandable that if it is detected that the current at the output end of the fuel pump exceeds the short-circuit current for a duration exceeding a set time, it is determined that the fuel pump controller has an internal fault of the fuel pump controller.

[0061] Step S1012 : In response to the vehicle fuel pump controller satisfying any one of the fault determination rules, determining a fault detection result according to the corresponding fault determination rule.

[0062] Specifically, when the vehicle fuel pump controller satisfies any one of the fault determination rules in Table 1 above, the corresponding fault type can be found according to the satisfied fault determination rule to obtain the fault detection result.

[0063] It is understandable that when the vehicle fuel pump controller satisfies multiple fault determination rules in Table 1 above, it indicates that multiple faults have occurred in the fuel pump controller. In this case, the fault detection result includes multiple fault types.

[0064] Optionally, in step S103, outputting a fault control signal may include the following steps according to the fault type:

[0065] Step S1031: Determine the fault priority according to the fault type.

[0066] Step S1032: determining a fault control signal according to the fault priority, wherein the fault control signal includes a duration period for reducing the level signal of the signal input side of the fuel pump controller.

[0067] For example, the relationship between the fault type, the fault priority, and the duration of reducing the level signal on the signal input side of the fuel pump controller is shown in Table 2:

[0068] Table 2

[0069] For example, if the fault type is an overcurrent fault on the fuel pump side of the fuel pump controller, the corresponding fault priority is level 5. At this time, the fault control signal is set to reduce the level signal on the signal input side of the fuel pump controller for 25 times the cycle.

[0070] Optionally, determining the fault priority according to the fault type includes: in response to there being multiple fault types, determining a to-be-selected fault priority corresponding to each fault type to obtain a fault priority set; and selecting the largest to-be-selected fault priority from the fault priority set as the fault priority.

[0071] Specifically, when multiple fault types are identified from the fault detection results, the fault priority level to be selected corresponding to each fault type is determined to obtain a fault priority set. The highest fault priority level to be selected from the set is then selected as the selected fault priority level. For example, if the fault types include both a fuel pump controller oil pump side dry-run fault (fault priority 6) and a fuel pump controller oil pump side open circuit fault (fault priority 7), the fault priority level is determined to be 7.

[0072] Optionally, the fault types include: fuel pump controller internal fault, fuel pump controller overtemperature fault, fuel pump controller oil pump side fault, and pulse width modulation line fault.

[0073] Specifically, fuel pump controller faults include at least one of the following: a short circuit fault, a stall fault, an overcurrent fault, a dry-run fault, or an open circuit fault. Pulse width modulation line faults include at least one of the following: a PWM line input frequency out of range, a PWM line short to power / open, or a PWM line short to ground.

[0074] It should be noted that the corresponding troubleshooting measures for different fault types are shown in Table 3:

[0075] Table 3

[0076] Optionally, after the step of determining fault handling measures based on the fault control signal in response to the output of the fault control signal, the method further includes: performing real-time fault detection on the vehicle fuel pump controller to obtain real-time fault detection results; and stopping outputting the fault control signal in response to the real-time fault detection results indicating that there is no fault in the vehicle fuel pump controller.

[0077] Specifically, after determining the fault handling measures based on the fault control signal, the vehicle fuel pump controller is subjected to real-time fault detection to obtain a real-time fault detection result. When the real-time fault detection result indicates that there is no fault in the vehicle fuel pump controller, it indicates that the fault has been eliminated and the output of the fault control signal is stopped.

[0078] It can be understood that, while the fault persists, the fault control signal continues to be output to the engine management system.

[0079] Optionally, the fault handling method also includes: in response to the vehicle being powered on, clearing historical fault detection results, wherein the historical fault detection results are the fault detection results for the vehicle fuel pump controller when the vehicle was last powered on; in response to the historical fault detection results being cleared, performing a fault detection on the vehicle fuel pump controller to obtain a fault detection result.

[0080] Specifically, when the vehicle is powered on again, the historical fault detection results need to be cleared, and then the vehicle fuel pump controller fault detection is re-performed to obtain the fault detection results. In other words, the fault detected at the nth power-on will not be retained until the (n+1)th power-on, and the fault must be re-detected at each power-on.

[0081] Optionally, in some embodiments of the present disclosure, after a fault detection result is obtained for the fuel pump controller, a fault signal is continuously sent to the engine management system. When transmitting the fault signal, the following principles are followed:

[0082] a) The higher the fault priority, the longer the duration period in Table 2 above;

[0083] b) For different fault priorities, the step size of the continuous cycle increase remains consistent;

[0084] c) When multiple faults are detected at the same time, the fault with the highest priority is sent;

[0085] d) The current fault should be sent completely, even if a higher priority fault is detected during the fault transmission;

[0086] e) After the fault is confirmed, it should be sent as soon as possible;

[0087] f) Before the fault is repaired, the message should be sent continuously at a preset time interval, which can be 1 second;

[0088] g) After the fault is repaired, the transmission will stop, but the fault that is currently being transmitted should be completed and cannot be interrupted;

[0089] h) The preset time interval is a fixed value that cannot be changed;

[0090] i) All faults need to be reset and cleared after powering on again, even if the faults were not sent during the last power on.

[0091] Referring to FIG4 , the fuel pump controller provided by the present disclosure is described. The fuel pump controller includes: a microprocessor (MCU), a current monitoring module, a temperature monitoring module, a voltage monitoring module, a fault feedback module, a power conversion module, a power processing module, and a motor drive module. The microprocessor includes an internal fault monitoring module and a PWM signal processing module. Specifically, the internal fault monitoring module is configured to detect whether an internal fault has occurred in the fuel pump controller; the PWM signal processing module is configured to process received PWM signals; the current monitoring module is configured to monitor the output current of the motor drive module; the temperature monitoring module is configured to monitor the operating temperature of the fuel pump controller; the voltage monitoring module is configured to monitor the output voltage of the motor drive module; the motor drive module is configured to send a drive signal to the fuel pump; and the fault feedback module is configured to report faults to the engine management system via a PWM line. The power conversion module and the power processing module are conventional designs in the art and will not be described in detail.

[0092] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0093] This embodiment also provides a fault handling system that is configured to implement the above-described embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" refers to a combination of software and / or hardware that can implement a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0094] Figure 5 is a structural block diagram of a fault handling system 200 according to one embodiment of the present disclosure. As shown in Figure 5, the fault handling system 200 is taken as an example, including: a detection module 201, configured to perform fault detection on a vehicle fuel pump controller to obtain a fault detection result; a determination module 202, configured to determine a fault type based on the fault detection result; an output module 203, configured to output a fault control signal based on the fault type, wherein the fault control signal is configured to reduce the level signal on the signal input side of the fuel pump controller; and a control module 204, configured to output a fault control signal in response to the fault control signal and determine a fault handling measure based on the fault control signal.

[0095] Optionally, the detection module 201 is further configured to: perform fault detection on the vehicle fuel pump controller according to a preset fault detection rule comparison table, wherein the preset fault detection rule comparison table includes multiple fault determination rules, and each preset fault detection rule corresponds to a fault type; in response to the vehicle fuel pump controller satisfying any fault determination rule, determine the fault detection result according to the corresponding fault determination rule.

[0096] Optionally, the output module 203 is further configured to: determine a fault priority according to the fault type; and determine a fault control signal according to the fault priority, wherein the fault control signal includes a duration period of reducing the level signal on the signal input side of the fuel pump controller.

[0097] Optionally, the determination module 202 is further configured to: in response to multiple fault types, determine the to-be-selected fault priority corresponding to each fault type to obtain a fault priority set; and select the largest to-be-selected fault priority from the fault priority set as the fault priority.

[0098] Optionally, the fault type determined by the determination module 202 includes: a fuel pump controller internal fault, a fuel pump controller overtemperature fault, a fuel pump controller oil pump side fault, and a pulse width modulation line fault.

[0099] Optionally, the detection module 201 is further configured to: perform real-time fault detection on the vehicle fuel pump controller to obtain a real-time fault detection result; and stop outputting the fault control signal in response to the real-time fault detection result indicating that there is no fault in the vehicle fuel pump controller.

[0100] Optionally, the detection module 201 is further configured to: clear historical fault detection results in response to vehicle power-on, wherein the historical fault detection results are the fault detection results for the vehicle fuel pump controller when the vehicle was last powered on; and perform fault detection on the vehicle fuel pump controller to obtain a fault detection result in response to the historical fault detection results being cleared.

[0101] An embodiment of the present disclosure further provides a vehicle, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the fault handling method described in any of the above embodiments.

[0102] Optionally, in this embodiment, the processor in the vehicle may be configured to run a computer program to perform the following steps:

[0103] Step S101 : performing a fault detection on a vehicle fuel pump controller to obtain a fault detection result.

[0104] Step S102: Determine the fault type according to the fault detection result.

[0105] Step S103: outputting a fault control signal according to the fault type, wherein the fault control signal is configured to reduce the level of the signal input side of the fuel pump controller.

[0106] Step S104 : In response to the output of the fault control signal, a fault handling measure is determined according to the fault control signal.

[0107] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0108] An embodiment of the present disclosure further provides a non-volatile storage medium, in which a computer program is stored. The computer program is configured to execute the fault handling method described in any of the above embodiments when running on a computer or processor.

[0109] Optionally, in this embodiment, the computer program may be configured to store a computer program configured to perform the following steps:

[0110] Step S101 : performing a fault detection on a vehicle fuel pump controller to obtain a fault detection result.

[0111] Step S102: Determine the fault type according to the fault detection result.

[0112] Step S103: outputting a fault control signal according to the fault type, wherein the fault control signal is configured to reduce the level of the signal input side of the fuel pump controller.

[0113] Step S104 : In response to the output of the fault control signal, a fault handling measure is determined according to the fault control signal.

[0114] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

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

[0116] In some embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the modules can be a logical function division. In actual implementation, there may be other division methods, such as multiple modules 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, modules or indirect coupling or communication connection of modules, which can be electrical or other forms.

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

[0118] In addition, the functional modules in the various embodiments of the present disclosure may be integrated into a single processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module. The integrated modules may be implemented in the form of hardware or software functional modules.

[0119] If the integrated module is implemented in the form of a software function module 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 is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

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

[0121] The disclosed embodiments propose a vehicle control method, system, vehicle, and medium, which can determine a fault control signal based on the fault type, and then determine a fault handling measure based on the fault signal, so that the handling is more complete when a fuel pump controller detects a fault, thereby solving the technical problem in the prior art of an imperfect handling method when a fuel pump controller detects a fault.

Claims

1. A fault handling method, applied to a vehicle, comprising: Performing fault detection on a vehicle fuel pump controller to obtain a fault detection result; Determining the fault type according to the fault detection result; Outputting a fault control signal according to the fault type, wherein the fault control signal is configured to reduce the level signal of the signal input side of the fuel pump controller; In response to the fault control signal being output, a fault handling measure is determined according to the fault control signal.

2. The fault handling method according to claim 1, wherein: The performing fault detection on the vehicle fuel pump controller to obtain a fault detection result comprises: Performing fault detection on the vehicle fuel pump controller according to a preset fault detection rule comparison table, wherein the preset fault detection rule comparison table includes a plurality of fault determination rules, and each of the preset fault detection rules corresponds to one of the fault types; In response to the vehicle fuel pump controller satisfying any one of the fault determination rules, the fault detection result is determined according to the corresponding fault determination rule.

3. The fault handling method according to claim 1, wherein: Outputting a fault control signal according to the fault type includes: Determine the fault priority according to the fault type; A fault control signal is determined according to the fault priority, wherein the fault control signal includes a duration period of reducing the level signal at the signal input side of the fuel pump controller.

4. The fault handling method according to claim 3, wherein: Determining the fault priority according to the fault type includes: In response to the plurality of fault types, determining a to-be-selected fault priority corresponding to each of the fault types to obtain a fault priority set; The largest to-be-selected fault priority level is selected from the fault priority set as the fault priority level.

5. The fault handling method according to claim 1, wherein: The fault types include: internal fault of the fuel pump controller, over-temperature fault of the fuel pump controller, fuel pump side fault of the fuel pump controller, and pulse width modulation line fault.

6. The fault handling method according to claim 1, wherein: After the step of determining a fault handling measure according to the fault control signal in response to the fault control signal output, the step further includes: Performing real-time fault detection on the vehicle fuel pump controller to obtain real-time fault detection results; In response to the real-time fault detection result indicating that the vehicle fuel pump controller has no fault, outputting a fault control signal is stopped.

7. The fault handling method according to claim 1, wherein: Also includes: In response to the vehicle being powered on, clearing historical fault detection results, wherein the historical fault detection results are fault detection results for a vehicle fuel pump controller when the vehicle was last powered on; In response to the historical fault detection result being cleared, a fault detection is performed on the vehicle fuel pump controller to obtain the fault detection result.

8. A fault handling system, comprising: A detection module, configured to perform fault detection on a vehicle fuel pump controller to obtain a fault detection result; A determination module, configured to determine a fault type according to the fault detection result; An output module, configured to output a fault control signal according to the fault type, wherein the fault control signal is configured to reduce a level signal at a signal input side of the fuel pump controller; The control module is configured to respond to the fault control signal output and determine a fault handling measure according to the fault control signal.

9. A vehicle comprising a memory and a processor, wherein: The memory stores a computer program, and the processor is configured to run the computer program to execute the fault handling method described in any one of claims 1 to 7.

10. A non-volatile storage medium, wherein: The non-volatile storage medium stores a computer program, wherein the computer program is configured to execute the fault handling method described in any one of claims 1 to 7 when running on a computer or a processor.

Images