Fuel cell vehicle fault processing method, device, system and storage medium

Abstract

Embodiments of the present application provide a fuel cell vehicle fault processing method, device, system and storage medium, and relate to the technical field of new energy vehicles. The method determines a fault pre-diagnosis result of the vehicle by receiving an abnormal message detected by a controller, generates a first control instruction based on the fault pre-diagnosis result to execute the corresponding controller. Then receive the feedback of the first control instruction execution result, determine the fault final diagnosis result according to the first control instruction execution result, and generate the corresponding second control instruction to execute the corresponding controller, complete the fault processing. The present application further obtains the fault final diagnosis result through the first control instruction on the basis of obtaining the fault pre-diagnosis result, so that the fault judgment is more accurate and reliable.

Description

Technical Field

[0001] This invention relates to the field of new energy vehicle technology, and more specifically, to a method, apparatus, system, and storage medium for handling faults in fuel cell vehicles. Background Technology

[0002] Fault diagnosis of fuel cell vehicles generally adopts intelligent diagnostic technology, which achieves efficient interaction between knowledge base and database through highly integrated dialectical and mathematical logic, symbolic and numerical processing, and the unification of reasoning and algorithms.

[0003] Existing intelligent fault diagnosis technologies for fuel cell vehicles generally rely on sensors to acquire data and determine the corresponding faults by judging whether the data is abnormal. However, fuel cell systems are highly complex, involving multiple subsystems such as electrochemistry, thermal management, and control management. Fault manifestations are diverse and interconnected, making it difficult for intelligent diagnostic technologies to accurately identify complex fault modes, resulting in low accuracy in fault diagnosis using existing technologies. Summary of the Invention

[0004] The objectives of this invention include, for example, providing a method, apparatus, system, and storage medium for handling faults in fuel cell vehicles, which can at least partially solve the aforementioned technical problems.

[0005] The embodiments of the present invention can be implemented as follows:

[0006] In a first aspect, embodiments of the present invention provide a method for handling faults in a fuel cell vehicle, applied to a server of a fuel cell vehicle fault handling system. The fuel cell vehicle fault handling system further includes an on-board intelligent terminal, a gateway, and multiple controllers. The gateway is communicatively connected to each of the controllers and the on-board intelligent terminal, and the on-board intelligent terminal is communicatively connected to the server. The method includes:

[0007] Receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal to obtain at least one fault code and the abnormal parameters corresponding to the fault code;

[0008] Based on the fault codes and corresponding abnormal parameters, the vehicle's fault pre-diagnosis results are determined.

[0009] Based on the fault pre-diagnosis results, a first control command is generated and sent to the vehicle-mounted intelligent terminal, so that the vehicle-mounted intelligent terminal sends the first control command to the corresponding controller for execution through the gateway;

[0010] The system receives the execution result of the first control instruction fed back by the controller through the vehicle-mounted intelligent terminal, determines the final fault diagnosis result of the vehicle based on the first control instruction execution result, and generates a second control instruction corresponding to the final fault diagnosis result and sends it to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

[0011] Optionally, the execution result of the first control instruction includes an execution completion response code and vehicle parameters reacquired by the controller after executing the first control instruction; determining the final fault diagnosis result of the vehicle based on the execution result of the first control instruction includes:

[0012] Determine whether the reacquired vehicle parameters are within the preset parameter range;

[0013] If so, then the final diagnosis result of the fault is determined to be fault elimination;

[0014] If not, then the final diagnosis result of the fault is determined to be the vehicle fault corresponding to the fault code.

[0015] Optionally, the second control command includes an electronic controller reset command, a fault code clearing command, and a fault information prompt command; the generation of the second control command corresponding to the final fault diagnosis result and its transmission to the vehicle-mounted intelligent terminal to cause the corresponding controller to execute includes:

[0016] If the final diagnosis result of the fault is that the fault is eliminated, then the electronic controller reset command is generated and sent to the corresponding controller through the vehicle intelligent terminal to control the electronic controller to reset, and the reset success response code of the electronic controller is received.

[0017] If the reset success response code is received, the fault code clearing instruction is generated and sent to the corresponding controller through the vehicle intelligent terminal to clear the fault codes stored in the controller. The fault code clearing success response code fed back by the controller is then received, and the fault handling is completed.

[0018] Optionally, the second control command includes a fault information prompt command; the generation of the second control command corresponding to the final fault diagnosis result and its transmission to the in-vehicle intelligent terminal to cause the corresponding controller to execute includes:

[0019] If the final diagnosis result of the fault is a vehicle fault corresponding to the fault code, then the fault information prompt instruction is generated and sent to the corresponding controller through the vehicle intelligent terminal to prompt the user to stop using the vehicle.

[0020] Optionally, the controller includes a fuel system controller, a VCU controller, a fan controller, a DC-DC controller, a shift controller, a BCM controller, a PEPS controller, an instrument controller, an audio controller, a tire pressure controller, an EHB controller, and an MPC controller.

[0021] The parameters acquired by the fuel system controller, the VCU controller, the fan controller, the DC-DC controller, and the shift controller are encapsulated in a first type of message; the parameters acquired by the BCM controller, the PEPS controller, the instrument controller, the audio controller, and the tire pressure controller are encapsulated in a second type of message; and the parameters acquired by the EHB controller and the MPC controller are encapsulated in a third type of message.

[0022] Secondly, embodiments of the present invention provide a method for handling faults in a fuel cell vehicle, applied to an on-board intelligent terminal of a fuel cell vehicle fault handling system as described in any of the above claims. The fuel cell vehicle fault handling system further includes a server, a gateway, and multiple controllers; the gateway is communicatively connected to each of the controllers and the on-board intelligent terminal, and the on-board intelligent terminal is communicatively connected to the server; the method includes:

[0023] Receive at least one abnormal message sent by each of the controllers through the gateway, and determine the fault code corresponding to the abnormal message;

[0024] The fault code and the abnormal message are encapsulated and encrypted, and then sent to the server;

[0025] The system receives a first control instruction generated by the server based on an encapsulated and encrypted exception message, converts the first control instruction into a first network message, and sends the first network message to the corresponding controller for execution through the gateway.

[0026] The system receives the execution result of the first control command fed back by the controller through the gateway and transmits it to the server.

[0027] The system receives a second control instruction generated by the server based on the execution result of the first control instruction, converts the second control instruction into a second network message, and sends the second network message to the corresponding controller for execution through the gateway to complete the fault handling.

[0028] Optionally, determining the fault code corresponding to the abnormal message includes:

[0029] For each abnormal message, the abnormal information reading bits of the abnormal message are determined according to the message header of the abnormal message;

[0030] Read the exception information from the exception information read bit;

[0031] The fault code corresponding to the abnormal message is determined based on the abnormal information.

[0032] Thirdly, embodiments of the present invention provide a fault handling system for a fuel cell vehicle, including a server, an on-board intelligent terminal, a gateway, and multiple controllers; the gateway is communicatively connected to each of the controllers and the on-board intelligent terminal, and the on-board intelligent terminal is communicatively connected to the server.

[0033] Each of the controllers is used to acquire the corresponding vehicle parameters and generate an exception message and send it to the gateway when the vehicle parameters are abnormal.

[0034] The gateway is used to package the abnormal messages sent by the controllers corresponding to the same CAN bus, and send the packaged abnormal messages to the vehicle-mounted intelligent terminal.

[0035] The vehicle-mounted intelligent terminal is used to determine the corresponding fault code from the packaged abnormal message sent by the gateway, and encapsulate and encrypt the fault code and the abnormal message before sending them to the server.

[0036] The server is configured to receive and parse abnormal messages sent by the in-vehicle intelligent terminal to obtain at least one fault code and the corresponding abnormal parameters; determine the vehicle's pre-diagnosis result based on the fault code and the corresponding abnormal parameters; generate a first control command according to the pre-diagnosis result, and send the first control command to the corresponding controller for execution through the in-vehicle intelligent terminal and the gateway; receive the execution result of the first control command fed back by the controller through the in-vehicle intelligent terminal, determine the vehicle's final fault diagnosis result according to the first control command execution result, and generate a second control command corresponding to the final fault diagnosis result and send it to the in-vehicle intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

[0037] Fourthly, embodiments of the present invention provide a fuel cell vehicle fault handling device, which is applied to a server of a fuel cell vehicle fault handling system. The fuel cell vehicle fault handling system further includes an on-board intelligent terminal, a gateway, and multiple controllers. The gateway is communicatively connected to each of the controllers and the on-board intelligent terminal, and the on-board intelligent terminal is communicatively connected to the server. The fuel cell vehicle fault handling device includes:

[0038] The parsing unit is used to receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal to obtain at least one fault code and the abnormal parameters corresponding to the fault code.

[0039] The fault pre-diagnosis result determination unit is used to determine the vehicle's fault pre-diagnosis result based on the fault code and the corresponding abnormal parameters.

[0040] The first control command generation unit is used to generate a first control command based on the fault pre-diagnosis result and send it to the vehicle intelligent terminal so that the vehicle intelligent terminal can send the first control command to the corresponding controller for execution through the gateway.

[0041] The second control command generation unit is used to receive the execution result of the first control command fed back by the controller through the vehicle-mounted intelligent terminal, determine the final fault diagnosis result of the vehicle based on the first control command execution result, and generate a second control command corresponding to the final fault diagnosis result and send it to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

[0042] Fifthly, embodiments of the present invention provide a computer-readable storage medium, the computer-readable storage medium including a computer program, wherein the computer program, when executed, controls a server where the computer-readable storage medium is located to implement the steps of any of the methods described above.

[0043] The beneficial effects of the embodiments of the present invention include, for example:

[0044] By receiving abnormal messages detected by the controller, the system determines the vehicle's pre-diagnosis fault result and generates a first control command based on the result, which is then executed by the corresponding controller. The system then receives the execution result of the first control command, determines the final fault diagnosis result based on this result, and generates a corresponding second control command for the corresponding controller to execute, thus completing the fault handling.

[0045] Because the final fault diagnosis result is obtained through the first control command based on the pre-diagnosis result, the fault judgment is more accurate and reliable. Attached Figure Description

[0046] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is a structural diagram of a fuel cell vehicle fault handling system provided in an embodiment of the present invention;

[0048] Figure 2 This invention provides a method for handling faults in fuel cell vehicles applied to servers.

[0049] Figure 3 This invention provides a method for handling faults in fuel cell vehicles applied to in-vehicle intelligent terminals.

[0050] Figure 4 This is an architectural diagram of a fuel cell vehicle fault handling device provided in an embodiment of the present invention.

[0051] Icons: 01-Fuel cell vehicle fault handling system; 11-Server; 12-On-board intelligent terminal; 13-Gateway; 14-Controller; 300-Fuel cell vehicle fault handling device; 301-Analysis unit; 302-Fault pre-diagnosis result determination unit; 303-First control command generation unit; 304-Second control command generation unit. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0053] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0054] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0055] Furthermore, the terms "first" and "second" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0056] It should be noted that, where there is no conflict, the features in the embodiments of the present invention can be combined with each other.

[0057] As a future trend in the automotive industry, fuel cell vehicles present significantly increased technological complexity and troubleshooting challenges, rendering traditional methods relying on human experience inadequate. Intelligent diagnostic technology has emerged in this context. Through a highly integrated approach combining dialectical and mathematical logic, symbolic and numerical processing, and the unification of reasoning and algorithms, it achieves efficient interaction between knowledge bases and databases. This technological framework has demonstrated its immense potential in automotive repair, particularly in troubleshooting fuel cell vehicle faults, by rapidly locating and resolving problems through data processing and analysis, providing a scientific, rigorous, and efficient solution for handling highly technological and complex systems.

[0058] Existing intelligent fault diagnosis technologies for fuel cell vehicles generally rely on sensors to acquire data and determine the corresponding faults by judging whether the data is abnormal. However, fuel cell systems are highly complex, involving multiple subsystems such as electrochemistry, thermal management, and control management. Fault manifestations are diverse and interconnected, making it difficult for intelligent diagnostic technologies to accurately identify complex fault modes, resulting in low accuracy in fault diagnosis using existing technologies.

[0059] Based on the above, embodiments of the present invention provide a method, apparatus, system, and storage medium for handling faults in fuel cell vehicles, which can effectively alleviate the aforementioned technical problems.

[0060] Please refer to Figure 1 This application provides a fuel cell vehicle fault handling system 01, which includes a server 11, an on-board intelligent terminal 12, a gateway 13, and multiple controllers 14. The gateway 13 is communicatively connected to each controller 14 and the on-board intelligent terminal 12, and the on-board intelligent terminal 12 is communicatively connected to the server 11.

[0061] Each controller 14 is used to obtain the corresponding vehicle parameters and generate an exception message to send to the gateway 13 when the vehicle parameters are abnormal.

[0062] Gateway 13 is used to package the abnormal messages sent by the controller 14 corresponding to the same CAN bus and send the packaged abnormal messages to the vehicle intelligent terminal 12.

[0063] The vehicle-mounted intelligent terminal 12 is used to determine the corresponding fault code from the packaged abnormal message sent by the gateway 13, and encapsulate and encrypt the fault code and the abnormal message before sending it to the server 11.

[0064] Server 11 receives and parses abnormal messages sent by the in-vehicle intelligent terminal 12 to obtain at least one fault code and corresponding abnormal parameters. Based on the fault code and corresponding abnormal parameters, it determines the vehicle's pre-diagnosis result. According to the pre-diagnosis result, it generates a first control command and sends it to the corresponding controller 14 for execution via the in-vehicle intelligent terminal 12 and gateway 13. It receives the execution result of the first control command fed back by the controller 14 through the in-vehicle intelligent terminal 12, determines the final diagnosis result of the vehicle's fault based on the execution result, and generates a second control command corresponding to the final diagnosis result, which is then sent to the in-vehicle intelligent terminal 12 to enable the corresponding controller 14 to execute and complete the fault handling.

[0065] like Figure 1 As shown, each controller 14 is connected to the gateway 13 via a CAN bus. In order to facilitate the integration and classification of messages sent by each controller 14, the controllers 14 can be classified by function. Messages sent by controllers 14 with the same function are sent to the gateway 13 via the same CAN bus.

[0066] The controller 14 collects relevant parameters at a preset frequency, such as fan speed and tire pressure value. When at least one controller 14 collects vehicle parameters that are outside the normal range, the controller 14 generates an error message and sends it to the gateway 13 via the corresponding CAN bus.

[0067] After receiving an abnormal message, gateway 13 packages all abnormal messages sent on the same CAN bus and sends the packaged abnormal message to vehicle intelligent terminal 12. Vehicle intelligent terminal 12 receives the packaged abnormal message sent from gateway 13, determines the corresponding fault code from the abnormal message, encapsulates and encrypts the fault code and the abnormal message, and sends it to server 11.

[0068] Server 11 receives the encapsulated and encrypted exception message, decapsulates and decodes it to obtain the exception parameters and corresponding fault codes in the exception message. The exception parameters and corresponding fault codes determine the vehicle's pre-diagnosis result. Based on the pre-diagnosis result, a first control command is generated and sent to the corresponding controller 14 for execution via the in-vehicle intelligent terminal 12 and gateway 13. Then, the server receives the execution result of the first control command from the controller 14 via the in-vehicle intelligent terminal 12, determines the final fault diagnosis result of the vehicle based on the first control command execution result, and generates a second control command corresponding to the final fault diagnosis result, which is sent to the in-vehicle intelligent terminal 12 to cause the corresponding controller 14 to execute, thereby completing the fault handling.

[0069] Optionally, controller 14 includes a fuel system controller, a VCU (Vehicle Control Unit) controller, a fan controller, a DCDC (DC-to-DC Converter) controller, a gear shift controller, a BCM (Body Control Module) controller, a PEPS (Passive Entry Passive Start) controller, an instrument controller, an audio controller, a tire pressure controller, an EHB (Electronic Hydraulic Brake) controller, and an MPC (Model Predictive Control) controller.

[0070] The parameters acquired by the fuel system controller, VCU controller, fan controller, DCDC controller, and shift controller are encapsulated in the first type of message; the parameters acquired by the BCM controller, PEPS controller, instrument controller, audio controller, and tire pressure controller are encapsulated in the second type of message; and the parameters acquired by the EHB controller and MPC controller are encapsulated in the third type of message.

[0071] In one optional implementation, controller 14 may include a fuel system controller, VCU controller, fan controller, DC-DC controller, shift controller, BCM controller, PEPS controller, instrument controller, audio controller, tire pressure controller, EHB controller, and MPC controller. To better categorize and integrate the parameters obtained by these controllers, the parameters obtained by the fuel system controller, VCU controller, fan controller, DC-DC controller, and shift controller can be encapsulated in a first type of message transmitted via the powertrain CAN bus; the parameters obtained by the BCM controller, PEPS controller, instrument controller, audio controller, and tire pressure controller can be encapsulated in a second type of message transmitted via the comfort CAN bus; and the parameters obtained by the EHB controller and MPC controller can be encapsulated in a third type of message transmitted via the chassis CAN bus.

[0072] Corresponding to the fuel cell vehicle fault handling system 01, this embodiment of the invention provides a fuel cell vehicle fault handling method, applied to the server 11 of the fuel cell vehicle fault handling system 01. The fuel cell vehicle fault handling system 01 also includes an on-board intelligent terminal 12, a gateway 13, and multiple controllers 14. The gateway 13 is communicatively connected to each controller 14 and the on-board intelligent terminal 12, and the on-board intelligent terminal 12 is communicatively connected to the server 11. The method includes, as follows: Figure 2 The following steps are shown:

[0073] Step S110: Receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal to obtain at least one fault code and the abnormal parameters corresponding to the fault code.

[0074] Step S120: Based on the fault code and the corresponding abnormal parameters, determine the vehicle's fault pre-diagnosis result.

[0075] Step S130: Based on the fault pre-diagnosis results, generate a first control command and send it to the vehicle intelligent terminal so that the vehicle intelligent terminal can send the first control command to the corresponding controller for execution through the gateway.

[0076] Step S140: Receive the execution result of the first control command fed back by the controller through the vehicle intelligent terminal, determine the final fault diagnosis result of the vehicle based on the execution result of the first control command, and generate a second control command corresponding to the final fault diagnosis result and send it to the vehicle intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

[0077] In step S110, the abnormal message sent by the vehicle-mounted intelligent terminal is received and parsed to obtain at least one fault code and the abnormal parameters corresponding to the fault code.

[0078] After the controller 14 sends the detected abnormal parameters to the vehicle-mounted intelligent terminal 12 in the form of an abnormal message, the vehicle-mounted intelligent terminal 12 sends the message to the server 11. The server 11 receives the abnormal message, parses it to obtain the abnormal parameters and the corresponding fault codes.

[0079] In step S120, the vehicle's fault pre-diagnosis result is determined based on the fault code and the corresponding abnormal parameters.

[0080] After receiving the abnormal parameters and corresponding fault codes, server 11 can preliminarily determine the vehicle's fault based on a preset strategy, i.e., the fault pre-diagnosis result. For example, if the abnormal parameter is the vehicle's fuel cell coolant outlet temperature, the corresponding fault code is P0C78, and the preset strategy is a fault prediction model, then server 11 will input the vehicle's fuel cell coolant outlet temperature and fault code P0C78 into the fault prediction model. The model output will then indicate a battery cooling system fault, thus confirming the battery cooling system fault as the fault pre-diagnosis result.

[0081] In step S130, based on the fault pre-diagnosis results, a first control command is generated and sent to the vehicle-mounted intelligent terminal, so that the vehicle-mounted intelligent terminal can send the first control command to the corresponding controller for execution through the gateway.

[0082] After obtaining the fault pre-diagnosis result, in order to determine whether the fault pre-diagnosis result is accurate, the server 11 can generate a first control instruction, causing the controller 14 corresponding to the first control instruction to perform the corresponding action and feed back the execution result, thereby verifying the fault pre-diagnosis result.

[0083] In step S140, the system receives the execution result of the first control command fed back by the controller through the vehicle-mounted intelligent terminal, determines the final fault diagnosis result of the vehicle based on the execution result of the first control command, and generates a second control command corresponding to the final fault diagnosis result and sends it to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

[0084] After the controller 14 corresponding to the first control command completes its action, it feeds back the execution result of the first control command through the gateway 13 and the vehicle-mounted intelligent terminal 12. Upon receiving the execution result of the first control command, the server 11 determines the final fault diagnosis result of the vehicle based on the result. By generating a second control command for the controller 14 to execute, the fault is eliminated or the user is notified to stop operating the vehicle.

[0085] Optionally, the execution result of the first control command includes an execution completion response code and vehicle parameters reacquired by the controller after executing the first control command. The final fault diagnosis result of the vehicle is determined based on the execution result of the first control command, including:

[0086] Determine whether the newly acquired vehicle parameters are within the preset parameter range.

[0087] If yes, the final diagnostic result is determined to be fault resolution. If no, the final diagnostic result is determined to be the vehicle fault corresponding to the fault code.

[0088] After receiving the execution result of the first control command, the server 11 parses the execution result to obtain the execution completion response code and the vehicle parameters reacquired by the controller 14 after executing the first control command. The execution completion response code is used to indicate that the controller 14 has completed the execution of the first control command, and the reacquired vehicle parameters are used by the server 11 to further determine the vehicle fault.

[0089] If the reacquired vehicle parameters are within the preset parameter range, the fault is considered resolved, and the final fault diagnosis result is "fault resolved." If the reacquired vehicle parameters are not within the preset parameter range, the final fault diagnosis result is the vehicle fault corresponding to the fault code.

[0090] For example, if the pre-diagnosis result is a battery cooling system fault, the first control command sent by server 11 could be to instruct fan controller 14 to control the fan to run at a larger set duty cycle for a set duration. After fan controller 14 runs at the set duty cycle for the set duration, it generates an execution completion response code. Fuel cell coolant outlet temperature controller 14 then re-acquires the vehicle fuel cell coolant outlet temperature value and sends the execution completion response code and the re-acquired vehicle fuel cell coolant outlet temperature value to server 11. If server 11 analyzes and finds that the re-acquired vehicle fuel cell coolant outlet temperature value has returned to the preset parameter range, then the final fault diagnosis result is determined to be fault resolution.

[0091] Optionally, the second control command includes an electronic controller reset command, a fault code clearing command, and a fault information prompt command; a second control command corresponding to the final fault diagnosis result is generated and sent to the vehicle-mounted intelligent terminal 12 so that the corresponding controller 14 executes it, including:

[0092] If the final fault diagnosis result is that the fault is eliminated, an electronic controller reset command is generated and sent to the corresponding controller 14 through the vehicle intelligent terminal 12 to control the electronic controller to reset, and a reset success response code for successful electronic controller reset is received.

[0093] If a reset success response code is received, a fault code clearing command is generated and sent to the corresponding controller 14 via the vehicle-mounted intelligent terminal 12 to clear the fault codes stored in the controller 14. The fault code clearing success response code fed back by the controller 14 is then received, and the fault handling is completed.

[0094] If the final fault diagnosis result indicates that the fault has been resolved, the fault code needs to be cleared and the electronic controller needs to be reset. Server 11 generates an electronic controller reset command (e.g., 02 11 01 00 00 00 00 00) and sends it to the corresponding controller 14 via the vehicle-mounted intelligent terminal 12. Controller 14 executes the command and returns a reset success response code (e.g., 02 51 01 00 00 0000 00).

[0095] After receiving the reset success response code, server 11 further generates a fault code clearing command (e.g., 04 14FFFFFF 00 00 00) and sends it to the corresponding controller 14. Controller 14 executes the command and sends back a fault code clearing success response code (e.g., 01 54 00 00 00 00 00). Server 11 receives the fault code clearing success response code and completes the fault handling.

[0096] Optionally, the second control command includes a fault information prompt command. A second control command corresponding to the final fault diagnosis result is generated and sent to the vehicle-mounted intelligent terminal 12 to cause the corresponding controller 14 to execute, including:

[0097] If the final diagnosis result is a vehicle fault corresponding to the fault code, a fault information prompt instruction is generated and sent to the corresponding controller 14 through the vehicle intelligent terminal 12 to prompt the user to stop using the vehicle.

[0098] If the final diagnostic result indicates a vehicle fault corresponding to the fault code, the vehicle should be immediately taken out of service and returned to the factory for repair. Therefore, the server 11 will generate a fault information prompt instruction, which will be sent to the corresponding controller 14 (e.g., the central control display controller) via the in-vehicle intelligent terminal 12 to prompt the user to stop using the vehicle.

[0099] Based on the same inventive concept, this invention provides a method for handling faults in a fuel cell vehicle, applied to the onboard intelligent terminal 12 of the aforementioned fuel cell vehicle fault handling system 01. The fuel cell vehicle fault handling system 01 also includes a server 11, a gateway 13, and multiple controllers 14. The gateway 13 is communicatively connected to each controller 14 and the onboard intelligent terminal 12, respectively. The onboard intelligent terminal 12 is communicatively connected to the server 11. The method includes, as follows: Figure 3 The following steps are shown:

[0100] Step S210: Receive at least one abnormal message sent by each controller through the gateway, and determine the fault code corresponding to the abnormal message.

[0101] Step S220: Encapsulate and encrypt the fault code and the abnormal message, and send them to the server.

[0102] Step S230: Receive the first control command generated by the server based on the encapsulated and encrypted exception message, convert the first control command into a first network message, and send the first network message to the corresponding controller for execution through the gateway.

[0103] Step S240: Receive the execution result of the first control command fed back by the controller through the gateway and transmit it to the server.

[0104] Step S250: Receive the second control instruction generated by the server based on the execution result of the first control instruction, convert the second control instruction into a second network message, and send the second network message to the corresponding controller for execution through the gateway to complete the fault handling.

[0105] When one or more controllers 14 detect that the vehicle parameters they have collected are abnormal, they will send the abnormal parameters to the gateway 13 via the corresponding CAN bus in the form of an abnormal message. The gateway 13 will package the abnormal messages transmitted on the same CAN bus and then send them to the vehicle intelligent terminal 12.

[0106] After receiving an abnormal message, the vehicle-mounted intelligent terminal 12 determines the fault code of the abnormal message, encapsulates and encrypts the fault code and the abnormal message, and then sends it to the server 11. The server 11 generates a first control command based on the encapsulated and encrypted abnormal message and sends it to the vehicle-mounted intelligent terminal 12. The vehicle-mounted intelligent terminal 12 converts the first control command into a first network message and sends it to the corresponding controller 14 for execution through the gateway 13.

[0107] After the controller 14 executes the first control instruction, it sends the execution result of the first control instruction to the vehicle intelligent terminal 12 via the gateway 13. The vehicle intelligent terminal 12 then transmits the execution result of the first control instruction to the server 11.

[0108] The server 11 generates a second control command based on the execution result of the first control command and sends it to the vehicle-mounted intelligent terminal 12. The vehicle-mounted intelligent terminal 12 converts the second control command into a second network message and sends it to the corresponding controller 14 through the gateway 13 for execution, thus completing the fault handling.

[0109] Optionally, the fault code corresponding to the abnormal message is determined, including:

[0110] For each abnormal message, determine the abnormal information reading bits based on the message header.

[0111] Read the exception information from the read bits. Determine the fault code corresponding to the exception message based on the exception information.

[0112] To ensure data security and privacy, abnormal parameters need to be encrypted during the upload process. For example, encryption can be performed using a header + length information + data format. The header identifies the parameter, the length information defines the data length, and the data contains the parameter information. Each header corresponds to one or more specific parameters, and each parameter value is simplified to a hexadecimal value. For example, 0x88 represents the cooling water temperature, and 000A indicates that this definition is ten bytes long, with each two bytes defining a temperature parameter value.

[0113] After receiving an abnormal message, the vehicle-mounted intelligent terminal 12 can determine the abnormal information reading bits through the message header and read the abnormal information from the abnormal information reading bits. After obtaining the abnormal information, it looks up the corresponding fault code in the table based on the abnormal information.

[0114] For example, for an abnormal message in the power CAN bus with a header of 0x5DD, the vehicle intelligent terminal 12 extracts the FC_PSTDG_Code information located at bits 8 to 14 of the abnormal message based on the message header to obtain the fault code of the fuel cell system status; it also extracts the FC_DCT1_Code information located at bits 56 to 47 of the abnormal message to obtain the fault code of the DC converter 1.

[0115] Based on the same inventive concept, such as Figure 4 As shown in the figure, this embodiment of the invention provides a fuel cell vehicle fault handling device 300, which is applied to a server 11 of a fuel cell vehicle fault handling system 01. The fuel cell vehicle fault handling system 01 also includes an on-board intelligent terminal 12, a gateway 13, and multiple controllers 14. The gateway 13 is communicatively connected to each controller 14 and the on-board intelligent terminal 12, and the on-board intelligent terminal 12 is communicatively connected to the server 11. The fuel cell vehicle fault handling device 300 includes:

[0116] The parsing unit 301 is used to receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal 12 to obtain at least one fault code and the abnormal parameters corresponding to the fault code.

[0117] The fault pre-diagnosis result determination unit 302 is used to determine the vehicle's fault pre-diagnosis result based on the fault code and the corresponding abnormal parameters.

[0118] The first control command generation unit 303 is used to generate a first control command based on the fault pre-diagnosis result and send it to the vehicle intelligent terminal 12 so that the vehicle intelligent terminal 12 can send the first control command to the corresponding controller 14 for execution through the gateway 13.

[0119] The second control command generation unit 304 is used to receive the execution result of the first control command fed back by the controller 14 through the vehicle-mounted intelligent terminal 12, determine the final fault diagnosis result of the vehicle based on the execution result of the first control command, and generate a second control command corresponding to the final fault diagnosis result and send it to the vehicle-mounted intelligent terminal 12 so that the corresponding controller 14 can execute it to complete the fault handling.

[0120] Regarding the aforementioned fuel cell vehicle fault handling device 300, the specific functions of each unit have been described in detail in the embodiments of the fuel cell vehicle fault handling method provided in this specification, and will not be elaborated further here.

[0121] Based on the same inventive concept, embodiments of this invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods in the aforementioned fuel cell vehicle fault handling method.

[0122] The present invention has at least the following beneficial effects:

[0123] By receiving abnormal messages detected by the controller, the system determines the vehicle's pre-diagnosis fault result and generates a first control command based on the result, which is then executed by the corresponding controller. The system then receives the execution result of the first control command, determines the final fault diagnosis result based on this result, and generates a corresponding second control command for the corresponding controller to execute, thus completing the fault handling.

[0124] Because the final fault diagnosis result is obtained through the first control command based on the pre-diagnosis result, the fault judgment is more accurate and reliable.

[0125] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0126] In addition, the functional modules in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0127] If the functionality is implemented as a software 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 this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for handling faults in a fuel cell vehicle, characterized in that, A server is used in a fuel cell vehicle fault handling system, which also includes an on-board intelligent terminal, a gateway, and multiple controllers. The gateway is communicatively connected to each of the controllers and the in-vehicle intelligent terminal, and the in-vehicle intelligent terminal is communicatively connected to the server; the method includes: Receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal to obtain at least one fault code and the abnormal parameters corresponding to the fault code; Based on the fault codes and corresponding abnormal parameters, the vehicle's fault pre-diagnosis results are determined. Based on the fault pre-diagnosis results, a first control command is generated and sent to the vehicle-mounted intelligent terminal, so that the vehicle-mounted intelligent terminal sends the first control command to the corresponding controller for execution through the gateway; The system receives the execution result of the first control instruction fed back by the controller through the vehicle-mounted intelligent terminal, determines the final fault diagnosis result of the vehicle based on the first control instruction execution result, and generates a second control instruction corresponding to the final fault diagnosis result and sends it to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

2. The fuel cell vehicle fault handling method as described in claim 1, characterized in that, The execution result of the first control command includes an execution completion response code and the vehicle parameters reacquired by the controller after executing the first control command; Determining the final fault diagnosis result of the vehicle based on the execution result of the first control command includes: Determine whether the reacquired vehicle parameters are within the preset parameter range; If so, then the final diagnosis result of the fault is determined to be fault elimination; If not, then the final diagnosis result of the fault is determined to be the vehicle fault corresponding to the fault code.

3. The fuel cell vehicle fault handling method as described in claim 2, characterized in that, The second control command includes an electronic controller reset command, a fault code clearing command, and a fault information prompt command; the generation of the second control command corresponding to the final fault diagnosis result and its transmission to the vehicle-mounted intelligent terminal to enable the corresponding controller to execute includes: If the final diagnosis result of the fault is that the fault is eliminated, then the electronic controller reset command is generated and sent to the corresponding controller through the vehicle intelligent terminal to control the electronic controller to reset, and the reset success response code of the electronic controller is received. If the reset success response code is received, the fault code clearing instruction is generated and sent to the corresponding controller through the vehicle intelligent terminal to clear the fault codes stored in the controller. The fault code clearing success response code fed back by the controller is then received, and the fault handling is completed.

4. The fuel cell vehicle fault handling method as described in claim 2, characterized in that, The second control command includes a fault information prompt command; the generation of the second control command corresponding to the final fault diagnosis result and its transmission to the vehicle-mounted intelligent terminal to cause the corresponding controller to execute includes: If the final diagnosis result of the fault is a vehicle fault corresponding to the fault code, then the fault information prompt instruction is generated and sent to the corresponding controller through the vehicle intelligent terminal to prompt the user to stop using the vehicle.

5. The fuel cell vehicle fault handling method as described in claim 1, characterized in that, The controllers include a fuel system controller, a VCU controller, a fan controller, a DC-DC controller, a shift controller, a BCM controller, a PEPS controller, an instrument controller, an audio controller, a tire pressure controller, an EHB controller, and an MPC controller. The parameters acquired by the fuel system controller, the VCU controller, the fan controller, the DC-DC controller, and the shift controller are encapsulated in a first type of message; the parameters acquired by the BCM controller, the PEPS controller, the instrument controller, the audio controller, and the tire pressure controller are encapsulated in a second type of message; and the parameters acquired by the EHB controller and the MPC controller are encapsulated in a third type of message.

6. A fault handling system for fuel cell vehicles, characterized in that, It includes a server, an in-vehicle intelligent terminal, a gateway, and multiple controllers; the gateway is communicatively connected to each of the controllers and the in-vehicle intelligent terminal, and the in-vehicle intelligent terminal is communicatively connected to the server. Each of the controllers is used to acquire the corresponding vehicle parameters and generate an exception message and send it to the gateway when the vehicle parameters are abnormal. The gateway is used to package the abnormal messages sent by the controllers corresponding to the same CAN bus, and send the packaged abnormal messages to the vehicle-mounted intelligent terminal. The vehicle-mounted intelligent terminal is used to determine the corresponding fault code from the packaged abnormal message sent by the gateway, and encapsulate and encrypt the fault code and the abnormal message before sending them to the server. The server is used to receive and parse the abnormal messages sent by the vehicle-mounted intelligent terminal, and obtain at least one fault code and the abnormal parameters corresponding to the fault code. Based on the fault codes and corresponding abnormal parameters, the vehicle's fault pre-diagnosis results are determined. Based on the fault pre-diagnosis result, a first control command is generated and sent to the corresponding controller for execution via the vehicle-mounted intelligent terminal and the gateway; the execution result of the first control command is received from the controller via the vehicle-mounted intelligent terminal, the final fault diagnosis result of the vehicle is determined based on the first control command execution result, and a second control command corresponding to the final fault diagnosis result is generated and sent to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

7. A fault handling device for fuel cell vehicles, characterized in that, A server is used in a fault handling system for fuel cell vehicles. The fault handling system for fuel cell vehicles also includes an on-board intelligent terminal, a gateway, and multiple controllers. The gateway is communicatively connected to each of the controllers and the on-board intelligent terminal, and the on-board intelligent terminal is communicatively connected to the server. The fuel cell vehicle fault handling device includes: The parsing unit is used to receive and parse the abnormal message sent by the vehicle-mounted intelligent terminal to obtain at least one fault code and the abnormal parameters corresponding to the fault code. The fault pre-diagnosis result determination unit is used to determine the vehicle's fault pre-diagnosis result based on the fault code and the corresponding abnormal parameters. The first control command generation unit is used to generate a first control command based on the fault pre-diagnosis result and send it to the vehicle intelligent terminal so that the vehicle intelligent terminal can send the first control command to the corresponding controller for execution through the gateway. The second control command generation unit is used to receive the execution result of the first control command fed back by the controller through the vehicle-mounted intelligent terminal, determine the final fault diagnosis result of the vehicle based on the first control command execution result, and generate a second control command corresponding to the final fault diagnosis result and send it to the vehicle-mounted intelligent terminal so that the corresponding controller can execute it to complete the fault handling.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program, which, when executed, controls the server where the computer-readable storage medium is located to implement the steps of the method according to any one of claims 1 to 5.

Images