Methods, devices and systems for diagnosing fuel cell faults

By receiving fuel cell operation data in the diagnostic server and utilizing a preset fault diagnosis mechanism, combined with the OEM's vehicle networking platform, fuel cell faults can be quickly diagnosed and addressed, solving the problem of ineffective utilization of fault data in existing technologies and improving the service life and safety of the fuel cell system.

CN117174966BActive Publication Date: 2026-11-10ANHUI DEEPWAY TECHNOLOGY CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202311110567.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-08-31
Publication Date
2026-11-10
Estimated Expiration
2043-08-31

AI Technical Summary

Technical Problem

In the existing technology, the fault data of fuel cell systems has not been effectively utilized, resulting in low fault diagnosis efficiency of fuel cell vehicles and an inability to resolve mechanistic faults in fuel cell systems in a timely manner, affecting their service life and safety.

Method used

By receiving the vehicle's fuel cell operating data from the diagnostic server, comparing it using a preset fault diagnosis mechanism, issuing fault response strategies to the vehicle controller, or notifying third-party service providers for diagnosis, and combining the resources of the OEM's vehicle networking intelligent monitoring platform, rapid fault diagnosis and response can be achieved.

Benefits of technology

It enables rapid diagnosis and response to fuel cell system faults, optimizes control strategies, improves the lifespan and safety of fuel cell systems, and supports big data analysis and confidence enhancement of response strategies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117174966B_ABST
    Figure CN117174966B_ABST
Patent Text Reader

Abstract

This application discloses a fuel cell fault diagnosis method, apparatus, and system. The method includes: receiving operating data from a vehicle's fuel cell; determining, based on a comparison of the operating data with a preset fault diagnosis mechanism, that fault data exists in the operating data; and, based on the determination result of the fault data, issuing a fault response strategy to the vehicle controller and / or notifying a third-party service provider to diagnose the vehicle containing the fault data. The third-party service provider includes at least one of the following: an OEM, a system supplier, or a vehicle operator. This application achieves full utilization of test data from fuel cells on a test bench and the resources of the OEM's vehicle network intelligent monitoring platform, and enables fault diagnosis of the fuel cell system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of fuel cell fault detection technology, and in particular to a fuel cell fault diagnosis method, device and system. Background Technology

[0002] A fuel cell is a chemical device that directly converts the chemical energy of fuel into electrical energy; it is also known as an electrochemical generator. Because fuel cells convert the Gibbs free energy portion of the fuel's chemical energy into electrical energy through an electrochemical reaction, they are not limited by the Carnot cycle effect and are therefore highly efficient.

[0003] The lifespan of fuel cells is a significant factor limiting the large-scale commercialization of fuel cell vehicles. Therefore, ensuring the safe operation of fuel cell vehicles and extending the lifespan of fuel cells through fault diagnosis is receiving increasing attention.

[0004] In related technologies, many OEMs and fuel cell system suppliers have accumulated some fault data, but there is still no good way to utilize this fault data. The resources and capabilities of the various parties involved have not been fully utilized throughout the process. Summary of the Invention

[0005] This application provides a method, apparatus, and system for diagnosing fuel cell faults, which fully utilizes test data of fuel cells on the test bench and the resources of the vehicle networking intelligent monitoring platform of the OEM to diagnose faults in the fuel cell system.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, embodiments of this application provide a fuel cell fault diagnosis method for diagnosing servers, wherein the method includes:

[0008] Receives operational data from the vehicle's fuel cell;

[0009] Based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, it is determined that there is fault data in the operating data of the vehicle fuel cell.

[0010] Based on the judgment result of the fault data, a fault response strategy is issued to the vehicle controller and / or a third-party service provider is notified to diagnose the vehicle where the fault data is located. The third-party service provider includes at least one of the following: OEM, system supplier, or vehicle operator.

[0011] In some embodiments, the step of issuing a fault response strategy to the vehicle controller based on the judgment result of the fault data includes:

[0012] If it is determined that the fault phenomenon corresponding to the fault data exists in the preset fault diagnosis mechanism, then a fault response strategy is sent to the vehicle controller.

[0013] Receive the fault handling result fed back by the vehicle controller, and determine whether the fault phenomenon corresponding to the fault data has been resolved;

[0014] If the fault has been resolved, the fault phenomenon corresponding to the fault data and the fault response strategy are recorded, and the confidence level of the fault response strategy is adjusted.

[0015] In some embodiments, the step of notifying a third-party service provider to perform diagnostics on the vehicle containing the fault data based on the determination result of the fault data includes:

[0016] If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then a third-party service provider is notified to diagnose the entire vehicle containing the fault data.

[0017] If the fault handling result received from the vehicle controller indicates that the fault phenomenon corresponding to the fault data has not been resolved, then the third-party service provider is notified to diagnose the vehicle in which the fault data is located.

[0018] In some embodiments, notifying a third-party service provider to diagnose the entire vehicle containing the fault data includes:

[0019] The fault data is sent to the test bench and the host computer of the test bench. The fault phenomenon is reproduced on the test bench. The verification results fed back by the test bench are received and fault response measures are generated and fed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator.

[0020] And / or,

[0021] Based on its accumulated historical fault data, the system analyzes the data to generate possible fault response tests, which are then used to verify the tests on the test bench. The system receives the verification results from the test bench and generates fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator.

[0022] Based on the feedback from the third-party service provider, the response strategy for the fault phenomenon corresponding to the fault data is updated to the preset fault diagnosis mechanism, and an initial confidence level is assigned to the fault response strategy.

[0023] In some embodiments, if it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, the vehicle controller is notified so that the vehicle controller can provide driving operation reminders according to the fault level.

[0024] If the fault handling result is received from the vehicle controller and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, the vehicle controller is notified so that it can provide driving operation reminders based on the fault level.

[0025] Secondly, embodiments of this application also provide a fuel cell fault diagnosis system, wherein the system includes:

[0026] Multiple vehicle controllers are used to transmit the vehicle's fuel cell operating data to the diagnostic server;

[0027] The diagnostic server is used to receive the operating data of the vehicle fuel cell and, based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, determine that there is fault data in the operating data of the vehicle fuel cell.

[0028] The diagnostic server is also used to issue fault response strategies to the plurality of vehicle controllers and / or notify third-party service providers to diagnose the vehicle where the fault data is located, based on the judgment results of the fault data. The third-party service providers include at least one of the following: OEM, system supplier, and vehicle operator.

[0029] In some embodiments, the system includes:

[0030] At least one central gateway is used to receive battery test data of the whole vehicle fuel cell system collected by the test bench in real time based on CAN or CAN-FD network, and then send it to a remote terminal in real time via CAN or CAN-FD network. The remote terminal transmits the data to the diagnostic server in real time via 4G or 5G network. The battery test data includes battery test data that needs to reproduce the fault phenomenon.

[0031] Multiple vehicle-mounted remote terminals are used to receive the fault response strategies issued by the diagnostic server and send them to the vehicle controller in real time via CAN or CAN-FD network;

[0032] Each of the vehicle-mounted remote terminals is also used to receive the vehicle fuel cell operation data sent in real time by the vehicle controller via a CAN or CAN-FD network, and send it to the diagnostic server in real time via a 4G or 5G network. The vehicle-mounted remote terminals and the vehicle controller are respectively deployed on the corresponding vehicles.

[0033] In some embodiments, the system includes:

[0034] Multiple remote host computers are connected to the diagnostic server to access the diagnostic server, monitor the comparison results of the vehicle fuel cell operation data with the preset fault diagnosis mechanism, and adjust the calculation process accordingly.

[0035] Multiple host computers for the test bench are connected to the test bench and are used to access the corresponding test bench via Ethernet to monitor the test situation in real time and adjust the test conditions and parameters.

[0036] In some embodiments, the system includes:

[0037] The third-party service provider's access interface is used to receive messages notifying the third-party service provider to diagnose the entire vehicle containing the fault data, and

[0038] The feedback results from the third-party service provider are sent to the diagnostic server.

[0039] Secondly, embodiments of this application also provide a fuel cell fault diagnosis device for diagnosing servers, wherein the device includes:

[0040] The receiving module is used to receive the operating data of the vehicle's fuel cell.

[0041] The judgment module is used to determine whether there is fault data in the operating data of the vehicle fuel cell based on the comparison result between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism.

[0042] The diagnostic module is used to issue fault response strategies to the vehicle controller and / or notify third-party service providers to diagnose the vehicle where the fault data is located, based on the judgment results of the fault data. The third-party service providers include at least one of the following: OEM, system supplier, and vehicle operator.

[0043] Fourthly, embodiments of this application also provide an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform the above-described method.

[0044] Fifthly, embodiments of this application also provide a computer-readable storage medium that stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform the above-described method.

[0045] The at least one technical solution adopted in this application embodiment can achieve the following beneficial effects: The diagnostic server receives the operating data of the vehicle's fuel cell; based on the comparison result of the operating data of the vehicle's fuel cell with a preset fault diagnosis mechanism, it determines that fault data exists in the operating data of the vehicle's fuel cell; based on the judgment result of the fault data, it issues a fault response strategy to the vehicle controller and / or notifies a third-party service provider to diagnose the vehicle where the fault data is located. Through the diagnostic server, a fault response strategy can be issued to the vehicle controller. Simultaneously, if no fault response strategy is found in the judgment result of the fault data, a third-party service provider will be notified to diagnose the vehicle where the fault data is located. Through the pre-stored fault response mechanism, faults in the fuel cell system can be quickly diagnosed and a response mechanism provided. Furthermore, the fault phenomenon, processing mechanism, and processing result can be recorded on the background diagnostic server, which is beneficial for big data analysis.

[0046] In addition, the diagnostic server increases the confidence level of the processing strategy based on the processing results. This way, when multiple response mechanisms are available for the same phenomenon, the response and diagnostic mechanism with higher confidence is selected first. Attached Figure Description

[0047] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0048] Figure 1 This is one of the schematic diagrams of the fuel cell fault diagnosis platform in the embodiments of this application;

[0049] Figure 2 This is the second schematic diagram of the fuel cell fault diagnosis platform in the embodiments of this application;

[0050] Figure 3 This is a flowchart illustrating the fuel cell fault diagnosis method in an embodiment of this application.

[0051] Figure 4 This is a schematic diagram of the structure of the fuel cell fault diagnosis system in the embodiments of this application;

[0052] Figure 5 This is a schematic diagram illustrating the implementation process of the fuel cell fault diagnosis method in the embodiments of this application;

[0053] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0055] Lifespan is a crucial factor limiting the large-scale commercialization of fuel cell vehicles. Therefore, ensuring the safe operation of fuel cell vehicles and extending the lifespan of fuel cells through fault diagnosis is receiving increasing attention.

[0056] During their research, the inventors discovered that, firstly, in bench testing of fuel cell systems, the implementation is typically carried out by the fuel cell system supplier, who may outsource the testing or use their own test bench. During this process, the fuel cell system supplier accumulates and analyzes fault data and proposes corresponding fault response strategies. However, these strategies cannot be immediately validated on the vehicle.

[0057] Secondly, correspondingly, OEMs are the end users of fuel cell systems. An OEM may use multiple different fuel cell systems, thus possessing more real-vehicle test data on fuel cells than fuel cell system suppliers. If they can obtain as much fault data and corresponding strategies as possible from fuel cell systems, OEMs are well-positioned to apply and integrate this data and strategies, and provide feedback to fuel cell system suppliers. Especially with the increasing intelligence and connectivity of new energy vehicles, OEMs have their own vehicle-to-everything (V2X) intelligent monitoring platforms capable of vehicle information management, remote real-time monitoring, intelligent driving information processing, and decision-making. Therefore, these resources of OEMs can indeed be used for fault diagnosis of fuel cell systems.

[0058] However, as mentioned earlier, OEMs face a disadvantage: they cannot obtain timely fault data from fuel cell systems on test benches. Another disadvantage is that OEMs lack a deep understanding of the mechanisms of fuel cell systems. Even when faults occur in the vehicle, engineers from the fuel cell system supplier are required to resolve them. However, because the delivery cycle for fuel cell vehicles is relatively short, this vehicle-level solution only addresses the symptoms and cannot delve into the mechanisms of the fuel cell system to investigate the root causes of the faults and fundamentally resolve them from a design and development perspective. In other words, this data cannot be fully utilized.

[0059] To address the aforementioned shortcomings, this application provides a fuel cell testing and fault diagnosis platform. By using this platform, the test data of fuel cells on the test bench and the resources of the OEM's vehicle network intelligent monitoring platform can be fully utilized to diagnose faults in the fuel cell system. On the one hand, this can optimize the control strategy of the fuel cell system, and on the other hand, it can help fuel point system suppliers improve product quality.

[0060] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0061] like Figure 1 The diagram shown is a schematic of a fuel cell fault diagnosis platform. The platform consists of the following components:

[0062] The system comprises a test bench, a vehicle controller, and a server (i.e., a diagnostic server). The test bench and the vehicle controller can connect to the server via a communication protocol. Multiple test benches are included, allowing for the testing and scenario simulation of multiple fuel cell systems. The vehicle controller is installed on different vehicles and collects data on the actual battery usage of the vehicle's battery system.

[0063] Test benches 1, 2, ..., n collect endurance test data from fuel cell systems 1, 2, ..., n via CAN / CAN-FD networks. Test bench hosts 1, 2, ..., n can access their respective test benches via Ethernet to monitor the test status in real time and adjust test conditions and parameters. Simultaneously, the test benches transmit the test data to the central gateway in real time via the CAN / CAN-FD network. The central gateway collects the test data and then transmits it in real time to remote communication terminal 1 via the CAN / CAN-FD network. Remote communication terminal 1 then transmits the data to the server in real time via a 4G / 5G network. Similarly, remote communication terminals 2... ..., n...

[0064] The server can judge the received fuel cell test data according to the pre-set fuel cell system fault diagnosis mechanism. At the same time, the server can be accessed by remote host computer 1, remote host computer 2, ..., remote host computer 3 to monitor the server's predictive calculations, and adjustments can be made to the big data calculation process individually or collaboratively.

[0065] After analysis and diagnosis, the server sends the fault diagnosis results to vehicle remote communication terminal 1, vehicle remote communication terminal 2, ..., vehicle remote communication terminal 3 in real time via 4G / 5G network. These remote communication terminals then send the fault diagnosis results to vehicle controller 1, vehicle controller 2, ..., vehicle controller n in real time via CAN / CAN-FD network. The vehicle controller takes response measures based on the fault diagnosis results.

[0066] It is understandable that the aforementioned test bench, fuel cell system, and central gateway are all located within the same testing facility or site. The server can be located within the same testing facility or site as the above devices, or it can be located in a different site. It should be noted that the aforementioned vehicle-mounted remote communication terminal and vehicle controller are located on their respective vehicles.

[0067] like Figure 2 The image shown is a schematic diagram of another fuel cell fault diagnosis platform. This platform is similar to... Figure 1 The difference is that test benches, fuel cell systems, and remote communication terminals with different numbers can be located in different testing institutions or locations, and the data they collect can be sent to the server separately.

[0068] Test benches 1, 2, ..., n collect endurance test data from fuel cell systems 1, 2, ..., n via CAN / CAN-FD networks. Test bench hosts 1, 2, ..., n can access their respective test benches via Ethernet to monitor the test status in real time and adjust test conditions and parameters. Simultaneously, the test benches transmit the test data to remote communication terminals 1...n in real time via CAN / CAN-FD networks. Remote communication terminal 1 collects the test data and then transmits it to remote communication terminals 1...n in real time via CAN / CAN-FD networks. Remote communication terminal 1 then transmits the data to the server in real time via a 4G / 5G network. Similarly, remote communication terminals 2......n... ...

[0069] It can be understood that the remote communication terminals 1...n are communication terminals for test bench 1, test bench 2, ..., test bench n.

[0070] The server can judge the received fuel cell test data according to the pre-set fuel cell system fault diagnosis mechanism. At the same time, the server can be accessed by remote host computer 1, remote host computer 2, ..., remote host computer 3 to monitor the server's predictive calculations, and adjustments can be made to the big data calculation process individually or collaboratively.

[0071] After analysis and diagnosis, the server transmits the fault diagnosis results in real time to vehicle remote communication terminal 1, vehicle remote communication terminal 2, ..., vehicle remote communication terminal n via 4G / 5G networks. These vehicle remote communication terminals then transmit the fault diagnosis results in real time to vehicle controller 1, vehicle controller 2, ..., vehicle controller n via CAN / CAN-FD networks. The vehicle controller takes response measures based on the fault diagnosis results. Simultaneously, the vehicle controller transmits the operating data of its respective fuel cell system in real time to vehicle remote communication terminal 1, vehicle remote communication terminal 2, ..., vehicle remote communication terminal n via CAN / CAN-FD networks, and then transmits it to the server in real time via 4G / 5G networks. The server then judges the received fuel cell test data according to the pre-set fuel cell system fault diagnosis mechanism.

[0072] This application provides a method for diagnosing fuel cell faults, such as... Figure 3 The diagram shows a flowchart of a fuel cell fault diagnosis method in an embodiment of this application. The method includes at least the following steps S310 to S330:

[0073] Step S310: Receive the operating data of the vehicle's fuel cell.

[0074] The above method is used to diagnose servers, which are a form of server presentation and have the same functions as the server. The use of diagnostic servers can be categorized according to different business scenarios. Diagnostic servers can adopt a distributed architecture or a centralized architecture, but this application does not impose specific limitations on the embodiments.

[0075] The diagnostic server receives operating data of the vehicle's fuel cell, which comes from the vehicle controllers of different vehicles. It is understood that the operating data of the vehicle's fuel cell may include, but is not limited to, the fuel cell's State of Health (SOH), RUL (Roughness Limit), operating time, etc., and is not specifically limited in the embodiments of this application.

[0076] It should be noted that the operating data of the vehicle fuel cell refers to the data of the fuel cell operating in the vehicle, and a fault diagnosis strategy (mechanism) can be matched according to the data of the fuel cell operating in the vehicle.

[0077] Step S320: Based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, it is determined that there is fault data in the operating data of the vehicle fuel cell.

[0078] The diagnostic server compares the vehicle's fuel cell operating data with pre-stored fault diagnosis mechanisms to determine whether there is a corresponding fault diagnosis mechanism for the vehicle's fuel cell operating data.

[0079] For example, the operating data 1 of the vehicle's fuel cell corresponds to a unique fault diagnosis mechanism a1. Alternatively, the operating data 1 of the vehicle's fuel cell corresponds to multiple possible fault diagnosis mechanisms a1, a2, and a3.

[0080] It is understood that a "pre-stored fault diagnosis mechanism" refers to a pre-configured fault diagnosis mechanism or model. In the embodiments of this application, no specific limitations are imposed on the fault diagnosis mechanism or model, as long as it meets the requirements of fault diagnosis.

[0081] Step S330: Based on the judgment result of the fault data, issue a fault response strategy to the vehicle controller and / or notify a third-party service provider to diagnose the vehicle where the fault data is located, wherein the third-party service provider includes at least one of the following: OEM, system supplier, or vehicle operator.

[0082] Third-party service providers include those other than those providing services for the vehicle and diagnostic servers. OEMs are the end users of fuel cell systems, system suppliers are fuel cell system suppliers, and vehicle operators are vehicle system suppliers. The relationship among them is that system suppliers provide fuel cell systems to OEMs, and OEMs provide fuel cell system services to vehicle operators for use in their vehicles.

[0083] The diagnostic server sends a fault response mechanism to the vehicle controller based on the fault data assessment results (whether a fault exists or not). This allows the vehicle controller to implement response strategies and report the results (fault resolved or not). Afterward, the diagnostic server executes relevant fault diagnosis strategies based on whether the fault symptoms have been resolved.

[0084] Furthermore, the diagnostic server sends fault response strategies to the vehicle controller to diagnose the vehicle where the fault data is located. The corresponding scenario is: when an existing fault response strategy is found, the fault in the fuel cell of the vehicle containing the fault data can be diagnosed.

[0085] Furthermore, the diagnostic server can notify a third-party service provider to diagnose the entire vehicle containing the fault data. The corresponding scenario is: when no fault response strategy is found, the third-party service provider can be notified to diagnose the entire vehicle containing the fault data.

[0086] By employing the above method, the resources of the OEM's vehicle-to-everything (V2X) intelligent monitoring platform can be fully utilized. Through pre-stored fault response mechanisms, faults in the fuel cell system can be quickly diagnosed and corresponding solutions provided. Simultaneously, the fault symptoms, handling mechanisms, and results are recorded on the backend diagnostic server, facilitating big data analysis. Furthermore, the diagnostic server increases the confidence level of the handling strategy based on the processing results. Thus, when multiple handling mechanisms are available for the same phenomenon, the mechanism with the higher confidence level is prioritized.

[0087] Unlike related technologies where fuel cell system suppliers and OEMs lack data sharing on fuel cell usage, the above method enables rapid fault diagnosis and response for fuel cell systems in vehicles. It also records the entire process in the background, facilitating big data analysis and effectively addressing issues such as long diagnostic times and difficulty in locating the root cause of faults in fuel cell systems.

[0088] In one embodiment of this application, the step of issuing a fault response strategy to the vehicle controller based on the judgment result of the fault data includes: if it is determined that the fault phenomenon corresponding to the fault data exists in the preset fault diagnosis mechanism, then issuing a fault response strategy to the vehicle controller; receiving the fault handling result fed back by the vehicle controller, and determining whether the fault phenomenon corresponding to the fault data has been resolved; if it has been resolved, then recording the fault phenomenon corresponding to the fault data and the fault response strategy, and adjusting the confidence level of the fault response strategy.

[0089] When issuing a fault response strategy to the vehicle controller, if the diagnostic server determines that the fault phenomenon corresponding to the fault data exists in the preset fault diagnosis mechanism, then the fault response strategy is issued to the vehicle controller.

[0090] When issuing a fault response strategy to the vehicle controller, the diagnostic server also receives the fault handling result fed back by the vehicle controller and determines whether the fault phenomenon corresponding to the fault data has been resolved. If the diagnostic server receives feedback that the fault has been resolved, it records the fault phenomenon corresponding to the fault data and the fault response strategy, and adjusts the confidence level of the fault response strategy.

[0091] It's important to note that if the problem is resolved, it indicates the fault response strategy is working, and the confidence level of the strategy can be increased. Conversely, if the problem persists, it indicates the fault response strategy is ineffective, and the confidence level needs to be decreased. For example, the server can record the entire chain of this fault phenomenon and response mechanism, and increase the confidence level of the response mechanism. For instance, the confidence level of this response mechanism could be increased from 80% to 85%.

[0092] In one embodiment of this application, the step of notifying a third-party service provider to diagnose the vehicle where the fault data is located based on the judgment result of the fault data includes: if it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then the third-party service provider is notified to diagnose the vehicle where the fault data is located; if the fault handling result fed back by the vehicle controller is received, and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, then the third-party service provider is notified to diagnose the vehicle where the fault data is located.

[0093] In cases where a third-party service provider is notified to diagnose the vehicle containing the fault data, it is possible that the fault phenomenon corresponding to the fault data is determined not to exist in the preset fault diagnosis mechanism, and in such cases, the third-party service provider is notified to diagnose the vehicle containing the fault data.

[0094] Furthermore, if the fault handling result received from the vehicle controller indicates that the fault phenomenon corresponding to the fault data has not been resolved, a third-party service provider is notified to diagnose the vehicle in which the fault data is located. In other words, the diagnostic server notifies the OEM, system supplier, and vehicle operator to conduct a joint diagnostic consultation for this vehicle.

[0095] In one embodiment of this application, the step of notifying a third-party service provider to diagnose the vehicle containing the fault data includes: sending the fault data to a test bench and a host computer on the test bench; reproducing the fault phenomenon on the test bench; receiving the verification results from the test bench and generating fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator; and / or, analyzing historical fault data accumulated by itself, generating possible fault response tests, and using them to verify on the test bench; receiving the verification results from the test bench and generating fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator; updating the fault response strategy corresponding to the fault data to a preset fault diagnosis mechanism and assigning an initial confidence level to the fault response strategy based on the feedback results from the third-party service provider.

[0096] First, after notifying the third-party service provider to diagnose the vehicle containing the fault data, the diagnostic server sends the fault data to the test bench and its host computer, where the fault is reproduced. After the test bench returns the verification results to the server, the diagnostic server provides suggested troubleshooting measures to the OEM, (fuel cell) system supplier, and vehicle operator.

[0097] In addition, after notifying a third-party service provider to diagnose the vehicle containing the fault data, the diagnostic server can also analyze its accumulated big data, provide possible fault response tests, and verify them on a test bench.

[0098] Finally, the diagnostic server updates the fault response measures into the pre-stored fault diagnosis mechanism based on the feedback results and assigns an initial confidence level.

[0099] In one embodiment of this application, if it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, the vehicle controller is notified so that the vehicle controller can provide driving operation reminders according to the fault level; if the fault handling result fed back by the vehicle controller is received and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, the vehicle controller is notified so that the vehicle controller can provide driving operation reminders according to the fault level.

[0100] If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then the third-party service provider is notified to diagnose the entire vehicle where the fault data is located to obtain the fault level diagnosis result, and the vehicle controller will provide the driver with corresponding operation reminders according to the fault level.

[0101] Meanwhile, in another scenario, if the fault handling result received from the vehicle controller indicates that the fault phenomenon corresponding to the fault data has not been resolved, the vehicle controller is notified so that it can provide driving operation reminders based on the fault level.

[0102] In other words, both of the above methods can notify the vehicle controller.

[0103] This application provides a fuel cell fault diagnosis system, such as... Figure 4 As shown, a schematic diagram of the structure of a fuel cell fault diagnosis system in an embodiment of this application is provided. The system includes:

[0104] Multiple vehicle controllers 430 are used to transmit the vehicle fuel cell's operating data to the diagnostic server;

[0105] The diagnostic server 410 is used to receive the operating data of the vehicle fuel cell and, based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, determine that there is fault data in the operating data of the vehicle fuel cell.

[0106] The diagnostic server 410 is also used to issue fault response strategies to the plurality of vehicle controllers and / or notify third-party service providers to diagnose the vehicle where the fault data is located, based on the judgment results of the fault data. The third-party service providers include at least one of the following: OEM, system supplier, and vehicle operator.

[0107] After multiple vehicle controllers 430 establish communication with the diagnostic server 410, they transmit the vehicle fuel cell operating data to the diagnostic server 410. Simultaneously, the diagnostic server 410 also establishes communication with the test bench 420 and begins receiving test data, such as test data that needs to be reproduced.

[0108] The diagnostic server 410 compares the operating data of the vehicle fuel cell with the pre-stored fault diagnosis mechanism to determine whether there is a corresponding fault diagnosis mechanism for the operating data of the vehicle fuel cell.

[0109] For example, the operating data 1 of the vehicle's fuel cell corresponds to a unique fault diagnosis mechanism a1. Alternatively, the operating data 1 of the vehicle's fuel cell corresponds to multiple possible fault diagnosis mechanisms a1, a2, and a3.

[0110] It is understood that a "pre-stored fault diagnosis mechanism" refers to a pre-configured fault diagnosis mechanism or model. In the embodiments of this application, no specific limitations are imposed on the fault diagnosis mechanism or model, as long as it meets the requirements of fault diagnosis.

[0111] Third-party service providers include those other than those providing services for the vehicle and diagnostic servers. OEMs are the end users of fuel cell systems, system suppliers are fuel cell system suppliers, and vehicle operators are vehicle system suppliers. The relationship among them is that system suppliers provide fuel cell systems to OEMs, and OEMs provide fuel cell system services to vehicle operators for use in their vehicles.

[0112] The diagnostic server 410 sends a fault response mechanism to the vehicle controller based on the fault data assessment result (which is sent and synchronized regardless of whether a fault exists). This allows the vehicle controller to implement response strategies and provide feedback on the processing results (fault resolved or not). Afterward, the diagnostic server executes relevant fault diagnosis strategies based on whether the fault has been resolved.

[0113] Furthermore, the diagnostic server 410 sends a fault response strategy to the vehicle controller to diagnose the vehicle where the fault data is located. The corresponding scenario is: when an existing fault response strategy is matched, the fault in the fuel cell of the vehicle where the fault data is located can be diagnosed.

[0114] Furthermore, the diagnostic server 410 can notify a third-party service provider to diagnose the entire vehicle containing the fault data. The corresponding scenario is: when no fault response strategy is found, the third-party service provider can be notified to diagnose the entire vehicle containing the fault data.

[0115] In one embodiment of this application, the system includes: at least one central gateway for receiving battery test data of the vehicle fuel cell system collected by a test bench in real time via a CAN or CAN-FD network, and then transmitting it to a remote terminal in real time via the CAN or CAN-FD network, wherein the remote terminal transmits the data to a diagnostic server in real time via a 4G or 5G network, and wherein the battery test data includes battery test data that needs to reproduce fault phenomena; multiple vehicle-mounted remote terminals for receiving fault response strategies issued by the diagnostic server and transmitting them to the vehicle controller in real time via the CAN or CAN-FD network; each vehicle-mounted remote terminal is also used to receive vehicle fuel cell operation data transmitted in real time by the vehicle controller via the CAN or CAN-FD network, and transmit it to the diagnostic server in real time via the 4G or 5G network, wherein the vehicle-mounted remote terminals and the vehicle controller are respectively deployed on the corresponding vehicle.

[0116] At least one central gateway is used to receive the endurance test data of the whole vehicle fuel cell system collected through the test bench in real time based on the CAN or CAN-FD network, and then send it to the remote terminal in real time through the CAN or CAN-FD network.

[0117] It should be noted that the remote terminal transmits data to the diagnostic server in real time via a 4G or 5G network. It can be understood that "remote terminal" primarily refers to a "remote communication terminal," or the two can be considered to refer to the same thing.

[0118] In addition to the central gateway, it includes multiple vehicle-mounted remote terminals, which mainly receive the fault data identification results sent by the diagnostic server and transmit them to the vehicle controller in real time via CAN or CAN-FD network. Through these multiple vehicle-mounted remote terminals, the fault data identification results of the vehicle's fuel cell system can be sent out, and the battery operation data of the vehicle's fuel cell system can be received.

[0119] When there are multiple vehicle-mounted remote terminals, each of the vehicle-mounted remote terminals is also used to receive the actual operating data of the fuel cell running on the vehicle, which is transmitted in real time by the vehicle controller via a CAN or CAN-FD network, and transmit it to the diagnostic server in real time via a 4G or 5G network. This allows the actual operating data of the fuel cell running on the vehicle to be uploaded to the diagnostic server.

[0120] In one embodiment of this application, the system includes: multiple remote host computers connected to the diagnostic server, used to access the diagnostic server respectively, monitor the comparison results of the vehicle fuel cell operation data with the preset fault diagnosis mechanism, and adjust the calculation process; and multiple test bench host computers connected to the test bench, used to access the corresponding test bench via Ethernet to monitor the test situation in real time, and adjust the test conditions and parameters.

[0121] Multiple remote host computers are connected to the diagnostic server and access it to monitor its judgments. Specifically, big data engineers can access the server through remote host computer 1, remote host computer 2, ..., remote host computer n to monitor its predictive calculations and adjust the big data calculation process individually or collaboratively.

[0122] Multiple host computers are connected to the test bench, and the corresponding test benches are accessed via Ethernet to monitor the test situation in real time and adjust the test conditions and parameters. In specific implementation, test engineers can use host computers 1, 2, ..., n to access the corresponding test benches via Ethernet and monitor the test situation in real time, adjusting the test conditions and parameters.

[0123] In one embodiment of this application, the system includes: a third-party service provider access terminal, used to receive a message notifying the third-party service provider to diagnose the vehicle containing the fault data, and to send the feedback results from the third-party service provider to the diagnostic server.

[0124] The third-party service provider access terminal can receive messages that notify the third-party service provider to diagnose the vehicle containing the fault data, and the third-party service provider access terminal also needs to send the feedback results of the third-party service provider to the diagnostic server.

[0125] This application also provides a fuel cell fault diagnosis device 400, such as... Figure 4 The diagram provided illustrates the structure of a fuel cell fault diagnosis device 400 according to an embodiment of this application. The fuel cell fault diagnosis device 400 includes at least: a receiving module 410, a judging module 420, and a diagnosis module 430, wherein:

[0126] The aforementioned device is used to diagnose a server, which is a form of server presentation and has the same functions as a server. The use of a diagnostic server can be categorized according to different business scenarios; the diagnostic server can adopt a distributed architecture or a centralized architecture, and no specific limitations are imposed on the embodiments of this application.

[0127] In one embodiment of this application, the receiving module 410 is specifically used to: receive the operating data of the vehicle fuel cell.

[0128] The system receives operating data from the vehicle's fuel cell, which originates from the vehicle controllers of different vehicles. It is understood that the operating data may include, but is not limited to, the fuel cell's State of Health (SOH), RUL (Roughness Limit), and operating time, etc., and is not specifically limited in the embodiments of this application.

[0129] It should be noted that the operating data of the vehicle fuel cell refers to the data of the fuel cell operating in the vehicle, and a fault diagnosis strategy (mechanism) can be matched according to the data of the fuel cell operating in the vehicle.

[0130] In one embodiment of this application, the judgment module 420 is specifically used to: determine, based on the comparison result between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, that there is fault data in the operating data of the vehicle fuel cell.

[0131] The diagnostic server compares the vehicle's fuel cell operating data with pre-stored fault diagnosis mechanisms to determine whether there is a corresponding fault diagnosis mechanism for the vehicle's fuel cell operating data.

[0132] For example, the operating data 1 of the vehicle's fuel cell corresponds to a unique fault diagnosis mechanism a1. Alternatively, the operating data 1 of the vehicle's fuel cell corresponds to multiple possible fault diagnosis mechanisms a1, a2, and a3.

[0133] It is understood that a "pre-stored fault diagnosis mechanism" refers to a pre-configured fault diagnosis mechanism or model. In the embodiments of this application, no specific limitations are imposed on the fault diagnosis mechanism or model, as long as it meets the requirements of fault diagnosis.

[0134] In one embodiment of this application, the diagnostic module 430 is specifically used to: issue a fault response strategy to the vehicle controller and / or notify a third-party service provider to diagnose the vehicle where the fault data is located, based on the judgment result of the fault data, wherein the third-party service provider includes at least one of the following: OEM, system supplier, or vehicle operator.

[0135] Third-party service providers include those other than those providing services for the vehicle and diagnostic servers. OEMs are the end users of fuel cell systems, system suppliers are fuel cell system suppliers, and vehicle operators are vehicle system suppliers. The relationship among them is that system suppliers provide fuel cell systems to OEMs, and OEMs provide fuel cell system services to vehicle operators for use in their vehicles.

[0136] The diagnostic server sends a fault response mechanism to the vehicle controller based on the fault data assessment results (whether a fault exists or not). This allows the vehicle controller to implement response strategies and report the results (fault resolved or not). Afterward, the diagnostic server executes relevant fault diagnosis strategies based on whether the fault symptoms have been resolved.

[0137] Furthermore, the diagnostic server sends fault response strategies to the vehicle controller to diagnose the vehicle where the fault data is located. The corresponding scenario is: when an existing fault response strategy is found, the fault in the fuel cell of the vehicle containing the fault data can be diagnosed.

[0138] Furthermore, the diagnostic server can notify a third-party service provider to diagnose the entire vehicle containing the fault data. The corresponding scenario is: when no fault response strategy is found, the third-party service provider can be notified to diagnose the entire vehicle containing the fault data.

[0139] It is understood that the above-described fuel cell fault diagnosis device can realize all the steps of the fuel cell fault diagnosis method provided in the foregoing embodiments. The relevant explanations of the fuel cell fault diagnosis method are applicable to the fuel cell fault diagnosis device, and will not be repeated here.

[0140] To better illustrate the implementation process of this application, as follows: Figure 5 The diagram shown is a schematic representation of the implementation flow of the fuel cell fault diagnosis method in this application embodiment, which specifically includes:

[0141] S001, (Diagnosis) The server imports a pre-configured fault diagnosis mechanism.

[0142] S002, (diagnostic) The server and test bench establish communication and begin receiving test data.

[0143] S003, the (diagnostic) server establishes communication with the vehicle and begins receiving data from the fuel cell running on the vehicle.

[0144] S004, the (diagnostic) server compares the data uploaded by the vehicle with the pre-stored fault diagnosis mechanism.

[0145] S005, (Diagnosis) The server determines whether there is faulty data. If yes, proceed to step S006. If no, proceed to step S003.

[0146] S006, (Diagnosis) The server determines whether the fault phenomenon exists in the pre-stored fault diagnosis mechanism. If yes, proceed to step S007. If no, proceed to step S107.

[0147] S007, (diagnostic) server sends fault response mechanism to vehicle controller.

[0148] S008, the vehicle controller takes appropriate measures and provides feedback on the processing results.

[0149] S009, (Diagnosis) The server takes action based on whether the fault has been resolved. If yes, proceed to step S010. If no, proceed to step S107.

[0150] S010, The (diagnostic) server records the entire chain of this fault phenomenon and response mechanism, and increases the confidence level of the response mechanism. For example, it increases the confidence level of this response mechanism from 80% to 85%.

[0151] S107, (diagnostic) server notifies OEM, system supplier, and vehicle operator to conduct a diagnostic consultation for this vehicle.

[0152] If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then a third-party service provider is notified to diagnose the entire vehicle containing the fault data.

[0153] If the fault handling result received from the vehicle controller indicates that the fault phenomenon corresponding to the fault data has not been resolved, then the third-party service provider is notified to diagnose the vehicle in which the fault data is located.

[0154] S108, the vehicle controller provides corresponding operational reminders to the driver based on the severity of the fault.

[0155] If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then the vehicle controller is notified so that the vehicle controller can provide driving operation reminders according to the fault level.

[0156] If the fault handling result is received from the vehicle controller and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, the vehicle controller is notified so that it can provide driving operation reminders based on the fault level.

[0157] S109, the (diagnostic) server sends the fault data to the test bench and the host computer on the test bench, and reproduces the fault phenomenon on the test bench.

[0158] The S110 (diagnostic) server analyzes its accumulated big data to provide possible fault response tests, which are then verified on a test bench.

[0159] The fault data is sent to the test bench and the host computer of the test bench. The fault phenomenon is reproduced on the test bench. The verification results fed back by the test bench are received and fault response measures are generated and fed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator.

[0160] And / or,

[0161] Based on its accumulated historical fault data, the system analyzes the data to generate possible fault response tests, which are then used to verify the tests on the test bench. The system receives the verification results from the test bench and generates fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator.

[0162] Based on the feedback from the third-party service provider, the response strategy for the fault phenomenon corresponding to the fault data is updated to the preset fault diagnosis mechanism, and an initial confidence level is assigned to the fault response strategy.

[0163] S111, the test bench sends the verification results back to the server. The server then sends the suggested troubleshooting measures back to the OEM, system vendor, and carrier.

[0164] S112: Feedback from OEMs, system suppliers, and operators on the results of verifying the fault response measures recommended in the vehicle.

[0165] S113, The (diagnostic) server updates the fault response measures into the pre-stored fault diagnosis mechanism based on the feedback results and assigns an initial confidence level.

[0166] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 6 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0167] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0168] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0169] The processor reads the corresponding computer program from non-volatile memory into main memory and then runs it, forming a fuel cell fault diagnosis device at the logical level. The processor executes the program stored in memory and specifically performs the following operations:

[0170] Receives operational data from the vehicle's fuel cell;

[0171] Based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, it is determined that there is fault data in the operating data of the vehicle fuel cell.

[0172] Based on the judgment result of the fault data, a fault response strategy is issued to the vehicle controller and / or a third-party service provider is notified to diagnose the vehicle where the fault data is located. The third-party service provider includes at least one of the following: OEM, system supplier, or vehicle operator.

[0173] The above is as stated in this application. Figure 3The method executed by the fuel cell fault diagnosis device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0174] The electronic device can also perform Figure 3 The method for performing a fault diagnosis device for a fuel cell is described, and the method for implementing a fault diagnosis device for a fuel cell is described. Figure 3 The functions of the embodiments shown are not described again in this application.

[0175] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform... Figure 3 The method executed by the fuel cell fault diagnosis device in the illustrated embodiment is specifically used to perform:

[0176] Receives operational data from the vehicle's fuel cell;

[0177] Based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, it is determined that there is fault data in the operating data of the vehicle fuel cell.

[0178] Based on the judgment result of the fault data, a fault response strategy is issued to the vehicle controller and / or a third-party service provider is notified to diagnose the vehicle where the fault data is located. The third-party service provider includes at least one of the following: OEM, system supplier, or vehicle operator.

[0179] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0180] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0181] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0182] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0183] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0184] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0185] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0186] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0187] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0188] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A fuel cell fault diagnosis method for diagnosing servers, wherein, The method includes: Receives operational data from the vehicle's fuel cell; Based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, it is determined that there is fault data in the operating data of the vehicle fuel cell. Based on the judgment results of the fault data, a fault response strategy is issued to the vehicle controller and / or a third-party service provider is notified to diagnose the vehicle where the fault data is located. The third-party service provider includes at least: OEM, system supplier, and vehicle operator. The OEM is the end user of the fuel cell system, the system supplier is the fuel cell system supplier, and the vehicle operator is the supplier of the vehicle system. The system supplier provides the fuel cell system to the OEM, and the OEM provides the fuel cell system service to the vehicle operator in the vehicle. The step of issuing a fault response strategy to the vehicle controller based on the judgment result of the fault data includes: If it is determined that the fault phenomenon corresponding to the fault data exists in the preset fault diagnosis mechanism, then a fault response strategy is sent to the vehicle controller. Receive the fault handling result fed back by the vehicle controller, and determine whether the fault phenomenon corresponding to the fault data has been resolved; If the fault has been resolved, record the fault phenomenon corresponding to the fault data and the fault response strategy, and adjust the confidence level of the fault response strategy. The step of notifying a third-party service provider to diagnose the vehicle containing the fault data based on the fault data's determination result includes: If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then a third-party service provider is notified to diagnose the entire vehicle containing the fault data. If the fault handling result fed back by the vehicle controller is received and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, then the third-party service provider is notified to diagnose the vehicle where the fault data is located. The notification to the third-party service provider to diagnose the entire vehicle containing the fault data includes: The fault data is sent to the test bench and the host computer of the test bench. The fault phenomenon is reproduced on the test bench. The verification results fed back by the test bench are received and fault response measures are generated and fed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator. And / or, Based on its accumulated historical fault data, the system analyzes the data to generate possible fault response tests, which are then used to verify the tests on the test bench. The system receives the verification results from the test bench and generates fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator. Based on the feedback from the third-party service provider, the response strategy for the fault phenomenon corresponding to the fault data is updated to the preset fault diagnosis mechanism, and an initial confidence level is assigned to the fault response strategy.

2. The method as described in claim 1, wherein, If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then the vehicle controller is notified so that the vehicle controller can provide driving operation reminders according to the fault level. If the fault handling result is received from the vehicle controller and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, the vehicle controller is notified so that it can provide driving operation reminders based on the fault level.

3. A fuel cell fault diagnosis system, wherein, The system includes: Multiple vehicle controllers are used to transmit the vehicle's fuel cell operating data to the diagnostic server; The diagnostic server is used to receive the operating data of the vehicle fuel cell and, based on the comparison results between the operating data of the vehicle fuel cell and the preset fault diagnosis mechanism, determine that there is fault data in the operating data of the vehicle fuel cell. The diagnostic server is also used to issue fault response strategies to the multiple vehicle controllers and / or notify third-party service providers to diagnose the vehicle where the fault data is located, based on the judgment results of the fault data. The third-party service providers include at least: OEMs, system suppliers, and vehicle operators. The OEM is the end user of the fuel cell system, the system supplier is the fuel cell system supplier, and the vehicle operator is the supplier of the vehicle system. The system supplier provides the fuel cell system to the OEM, and the OEM provides the fuel cell system service to the vehicle operator in the vehicle. The step of issuing a fault response strategy to the vehicle controller based on the judgment result of the fault data includes: If it is determined that the fault phenomenon corresponding to the fault data exists in the preset fault diagnosis mechanism, then a fault response strategy is sent to the vehicle controller. Receive the fault handling result fed back by the vehicle controller, and determine whether the fault phenomenon corresponding to the fault data has been resolved; If the fault has been resolved, record the fault phenomenon corresponding to the fault data and the fault response strategy, and adjust the confidence level of the fault response strategy. The step of notifying a third-party service provider to diagnose the vehicle containing the fault data based on the fault data's determination result includes: If it is determined that the fault phenomenon corresponding to the fault data does not exist in the preset fault diagnosis mechanism, then a third-party service provider is notified to diagnose the entire vehicle containing the fault data. If the fault handling result fed back by the vehicle controller is received and it is determined that the fault phenomenon corresponding to the fault data has not been resolved, then the third-party service provider is notified to diagnose the vehicle where the fault data is located. The notification to the third-party service provider to diagnose the entire vehicle containing the fault data includes: The fault data is sent to the test bench and the host computer of the test bench. The fault phenomenon is reproduced on the test bench. The verification results fed back by the test bench are received and fault response measures are generated and fed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator. And / or, Based on its accumulated historical fault data, the system analyzes the data to generate possible fault response tests, which are then used to verify the tests on the test bench. The system receives the verification results from the test bench and generates fault response measures to feed back to one or more third-party service providers among the OEM, system supplier, and vehicle operator. Based on the feedback from the third-party service provider, the response strategy for the fault phenomenon corresponding to the fault data is updated to the preset fault diagnosis mechanism, and an initial confidence level is assigned to the fault response strategy.

4. The system according to claim 3, wherein, The system includes: At least one central gateway is used to receive battery test data of the whole vehicle fuel cell system collected by the test bench in real time based on CAN or CAN-FD network, and then send it to a remote terminal in real time via CAN or CAN-FD network. The remote terminal transmits the data to the diagnostic server in real time via 4G or 5G network. The battery test data includes battery test data that needs to reproduce the fault phenomenon. Multiple vehicle-mounted remote terminals are used to receive the fault response strategies issued by the diagnostic server and send them to the vehicle controller in real time via CAN or CAN-FD network; Each of the vehicle-mounted remote terminals is also used to receive the vehicle fuel cell operation data sent in real time by the vehicle controller via a CAN or CAN-FD network, and send it to the diagnostic server in real time via a 4G or 5G network. The vehicle-mounted remote terminals and the vehicle controller are respectively deployed on the corresponding vehicles.

5. The system according to claim 3, wherein, The system includes: Multiple remote host computers are connected to the diagnostic server to access the diagnostic server, monitor the comparison results of the vehicle fuel cell operation data with the preset fault diagnosis mechanism, and adjust the calculation process accordingly. Multiple host computers for the test benches are connected to the test benches and are used to access the corresponding test benches via Ethernet to monitor the test situation in real time and adjust the test conditions and parameters.

6. The system according to claim 3, wherein, The system includes: The third-party service provider's access interface is used to receive messages notifying the third-party service provider to diagnose the entire vehicle containing the fault data, and The feedback results from the third-party service provider are sent to the diagnostic server.

Citation Information

Patent Citations

  • Fuel cell engine fault diagnosis method based on cloud platform

    CN110276372A

  • Full-closed-loop detection system and method for intelligent operation and maintenance of charging equipment

    CN115484291A

  • UDS-based fuel cell engine fault remote diagnosis system

    CN211969176U