Vehicle fault diagnosis platform and vehicle

Abstract

The invention provides a vehicle fault diagnosis platform and a vehicle, and the platform is configured to receive a fault diagnosis instruction which comprises a vehicle identifier and a controller identifier; identifying a vehicle identifier and a controller identifier, and determining a vehicle with a fault and a target controller with the fault; issuing a message acquisition signal to the vehicle, and receiving a communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, whether the vehicle has communication related faults or not is judged; if the vehicle has the communication related fault, directly outputting a platform feedback result; if the vehicle does not have the communication-related fault, issuing a fault data acquisition signal to the vehicle, and receiving fault data which is returned by the vehicle and correspondingly fed back by the target controller; and analyzing the fault data, and outputting a platform feedback result. According to the invention, the fault data of the vehicle can be diagnosed remotely after the vehicle is powered on, and the fault diagnosis efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle fault detection, and in particular to a vehicle fault diagnosis platform and a vehicle. Background Art

[0002] Fault diagnosis of traditional vehicles relies on on-board OBD technology (On-Board Diagnostics). At the repair service station, the faulty vehicle is plugged into the passenger car's OBD (On Board Diagnostics) interface to obtain fault information from each ECU (Electronic Control Unit) and conduct troubleshooting. However, this method of obtaining fault information through communication between special instruments and the on-board OBD system obviously no longer meets the growing diagnostic needs of new energy vehicles. In other words, the surge in the number of controllers has led to an increase in fault information, and real-time feedback on fault diagnosis is also an important requirement.

[0003] The after-sales model in which the vehicle must be taken to a repair service station for offline diagnosis by personnel will result in vehicle failures not being resolved in a timely manner due to the vehicle being too serious to drive to the repair service station or the driver being busy at work and lacking time to repair the vehicle. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a vehicle fault diagnosis platform and a vehicle to overcome at least one of the above-mentioned defects.

[0005] In a first aspect, an embodiment of the present application provides a vehicle fault diagnosis platform, wherein the platform is configured to: receive a fault diagnosis instruction, wherein the fault diagnosis instruction includes a vehicle identification and a controller identification; identify the vehicle identification and the controller identification, and determine a faulty vehicle and a target controller where the fault occurs; send a message acquisition signal to the vehicle, and receive a communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, determine whether the vehicle has a communication-related fault; if the vehicle has a communication-related fault, directly output the platform feedback result; if the vehicle does not have a communication-related fault, send a fault data acquisition signal to the vehicle, and receive the fault data corresponding to the feedback from the target controller returned by the vehicle; analyze the fault data, and output the platform feedback result.

[0006] In an optional embodiment of the present application, the platform feedback result includes a first platform feedback result, wherein the platform is further configured to: if the communication frame is empty, continue to send the message acquisition signal to the vehicle and detect the communication frame; when it is detected that the communication frames are all empty within a preset time period, output the first platform feedback result.

[0007] In an optional embodiment of the present application, the vehicle includes a remote communication controller, a central gateway controller, a battery management controller, a power domain controller and a transmitter controller, and the target controller is at least one of the battery management controller, the power domain controller and the transmitter controller, wherein the remote communication controller is used to receive the fault data acquisition signal from the vehicle fault diagnosis platform and transmit the fault data acquisition signal to the central gateway controller; the central gateway controller is used to receive the fault data acquisition signal from the remote communication controller and transmit the fault data acquisition signal to the target controller.

[0008] In an optional embodiment of the present application, the target controller is used to receive the fault data acquisition signal from the central gateway controller, and transmit the fault data corresponding to the feedback of the target controller to the central gateway controller; the central gateway controller is also used to receive the fault data from the target controller, and transmit the fault data to the remote communication controller; the remote communication controller is also used to receive the fault data from the central gateway controller, and transmit the fault data to the vehicle fault diagnosis platform.

[0009] In an optional embodiment of the present application, the platform feedback result includes a second platform feedback result and a third platform feedback result, and the platform is further configured to: organize and parse the fault data corresponding to the feedback of the target controller returned by the vehicle; determine whether the fault data is negative feedback; if the fault data is negative feedback, it means that the platform has not recognized the fault data and outputs the second platform feedback result; if the fault data is not negative feedback, it means that the platform has recognized the fault data, stores the fault data, and outputs the third platform feedback result.

[0010] In an optional embodiment of the present application, the platform is further configured to: when it is detected that the communication frame is not empty, send a fault detection signal to the vehicle, and the communication frame is not empty to indicate that the vehicle has been powered on; receive a message signal fed back by the vehicle, and determine the communication fault result of the vehicle based on the message signal.

[0011] In an optional embodiment of the present application, the platform feedback result also includes a fourth platform feedback result, wherein the platform is further configured to: determine whether the message signal transmitted by the remote communication controller indicates communication loss or communication verification failure of the central gateway controller; if the message signal transmitted by the remote communication controller indicates communication loss or communication verification failure of the central gateway controller, determine that the vehicle has a communication-related fault and output the fourth platform feedback result; if the message signal transmitted by the remote communication controller does not indicate communication loss and communication verification failure of the central gateway controller, determine whether the message signal transmitted by the central gateway controller indicates communication loss or communication verification failure of the remote communication controller; if the message signal transmitted by the central gateway controller indicates communication loss or communication verification failure of the remote communication controller, determine that the vehicle has a communication-related fault and output the fourth platform feedback result; if the message signal transmitted by the central gateway controller does not indicate communication loss and communication verification failure of the remote communication controller, it indicates that no communication-related fault occurs between the central gateway controller and the remote communication controller.

[0012] In an optional embodiment of the present application, the platform is further configured to: determine whether the message signal transmitted by the target controller indicates a loss of communication or a communication verification failure of the central gateway controller; if the message signal transmitted by the target controller indicates a loss of communication or a communication verification failure of the central gateway controller, determine that the vehicle has a communication-related fault, and output a fourth platform feedback result; if the message signal transmitted by the target controller does not indicate a loss of communication and a communication verification failure of the central gateway controller, determine whether the message signal transmitted by the central gateway controller indicates a loss of communication or a communication verification failure of the target controller; if the message signal transmitted by the central gateway controller indicates a loss of communication or a communication verification failure of the target controller, determine that the vehicle has a communication-related fault, and output a fourth platform feedback result; if the message signal transmitted by the central gateway controller does not indicate a loss of communication and a communication verification failure of the target controller, it indicates that no communication-related fault occurs between the central gateway controller and the target controller; when it is detected that no communication-related fault occurs between the central gateway controller and the remote communication controller and between the central gateway controller and the target controller, it is confirmed that the vehicle does not have a communication-related fault.

[0013] In the second aspect, an embodiment of the present application also provides a vehicle fault diagnosis method, which is applied to a vehicle fault diagnosis platform, including: receiving a fault diagnosis instruction, the fault diagnosis instruction including a vehicle identification and a controller identification; identifying the vehicle identification and the controller identification, and determining the faulty vehicle and the target controller where the fault occurs; sending a message acquisition signal to the vehicle, and receiving a communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, determining whether the vehicle has a communication-related fault; if the vehicle has a communication-related fault, directly outputting the platform feedback result; if the vehicle does not have a communication-related fault, sending a fault data acquisition signal to the vehicle, and receiving the fault data corresponding to the feedback from the target controller returned by the vehicle; analyzing the fault data, and outputting the platform feedback result.

[0014] In a third aspect, an embodiment of the present application further provides a vehicle, comprising a remote communication controller, a central gateway controller and a target controller, wherein the remote communication controller is used to receive the fault diagnosis instruction from the central gateway controller, and transmit the fault diagnosis instruction to a vehicle fault diagnosis platform, and receive a message acquisition signal from the vehicle fault diagnosis platform, and transmit the message acquisition signal to the central gateway controller, and receive the communication frame from the central gateway controller, and transmit the communication frame to the vehicle fault diagnosis platform, and receive a fault data acquisition signal from the vehicle fault diagnosis platform, and transmit the fault data acquisition signal to the central gateway controller, and receive the fault data from the central gateway controller, and transmit the fault data to the vehicle fault diagnosis platform; the central gateway controller is used to receive the fault diagnosis instruction from the target controller, and transmit the fault diagnosis instruction to the vehicle fault diagnosis platform. When a fault signal is received, a fault diagnosis instruction is generated and the fault diagnosis instruction is reported to the remote communication controller, and the message acquisition signal is received from the remote communication controller, and the message acquisition signal is transmitted to the target controller, and a communication frame is received from the target controller, and the communication frame is transmitted to the remote communication controller, and a fault data acquisition signal is received from the remote communication controller, and the fault data acquisition signal is transmitted to the target controller, and fault data is received from the target controller and transmitted to the remote communication controller; the target controller is used to receive the message acquisition signal from the central gateway controller, and transmit the communication frame of the target controller to the central gateway controller, and receive the fault data acquisition signal from the central gateway controller, and transmit the fault data to the central gateway controller.

[0015] The vehicle fault diagnosis platform and vehicle provided by the embodiment of the present application, the platform is configured to: receive fault diagnosis instructions, the fault diagnosis instructions include vehicle identification and controller identification; identify the vehicle identification and controller identification, determine the vehicle with fault and the target controller with fault; send a message acquisition signal to the vehicle, and receive the communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, determine whether the vehicle has a communication-related fault; if the vehicle has a communication-related fault, directly output the platform feedback result; if the vehicle does not have a communication-related fault, send a fault data acquisition signal to the vehicle, and receive the fault data corresponding to the feedback of the target controller returned by the vehicle; analyze the fault data, and output the platform feedback result. Through this application, the fault data of the vehicle can be remotely diagnosed after the vehicle is powered on, which improves the diagnostic efficiency.

[0016] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 One of the flow charts of the vehicle fault diagnosis platform provided in the embodiment of the present application;

[0019] Figure 2 The second flowchart of the vehicle fault diagnosis platform provided in the embodiment of the present application;

[0020] Figure 3 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0022] First, the application scenarios to which the present application is applicable are introduced. The present application can be applied in the field of vehicle fault detection technology.

[0023] Research has found that the fault diagnosis of traditional vehicles relies on on-board OBD technology (On-Board Diagnostics). At the repair service station, the faulty vehicle is plugged into the OBD (On Board Diagnostics) interface of the passenger car to obtain the fault information of each ECU (Electronic Control Unit) and conduct troubleshooting. However, this method of obtaining fault information through communication between special instruments and the on-board OBD system obviously no longer meets the growing diagnostic needs of new energy vehicles. The after-sales mode in which the vehicle must enter the repair service station for offline diagnosis by personnel will lead to the problem that the vehicle fault cannot be solved in time due to serious vehicle faults and the driver is busy with work and lacks time for vehicle repairs. In addition, if the vehicle is diagnosed remotely, the vehicle fault data cannot be diagnosed in real time due to the inability to determine the wake-up time of the vehicle controller, and the fault diagnosis efficiency is low.

[0024] Based on this, the embodiment of the present application provides a vehicle fault diagnosis platform and a vehicle, and the platform is configured to: receive a fault diagnosis instruction, the fault diagnosis instruction includes a vehicle identification and a controller identification; identify the vehicle identification and the controller identification, determine the vehicle with the fault and the target controller with the fault; send a message acquisition signal to the vehicle, and receive the communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, determine whether the vehicle has a communication-related fault; if the vehicle has a communication-related fault, directly output the platform feedback result; if the vehicle does not have a communication-related fault, send a fault data acquisition signal to the vehicle, and receive the fault data of the target controller returned by the vehicle corresponding to the feedback; analyze the fault data, and output the platform feedback result. Through this application, the fault data of the vehicle can be remotely diagnosed after the vehicle is powered on, and the platform can automatically send a fault data acquisition signal after identifying that the vehicle is powered on, thereby improving the efficiency of fault diagnosis.

[0025] See also Figure 1 , Figure 1 This is one of the flow charts of the vehicle fault diagnosis platform provided in the embodiment of the present application. Figure 1 As shown in , the vehicle fault diagnosis platform provided in the embodiment of the present application is configured as follows:

[0026] S101: Receive a fault diagnosis instruction.

[0027] The fault diagnosis instructions include vehicle identification and controller identification.

[0028] In this step, the vehicle fault diagnosis platform first receives a fault diagnosis instruction. This instruction contains two key pieces of information: vehicle identification and controller identification. The vehicle identification is used to uniquely identify a specific vehicle, while the controller identification is used to identify a specific controller inside the vehicle, which may be an engine controller, a brake system controller, or a controller for any other critical system. These two identifications together form the basis for fault diagnosis, allowing the vehicle fault diagnosis platform to accurately locate the vehicle and its faulty components that need to be diagnosed.

[0029] In an optional embodiment, the owner can proactively inform the vehicle fault diagnosis platform that his vehicle has a fault in a variety of ways. For example, the owner can use the application on the smartphone to directly click the "Fault Report" button and fill in a brief fault description or select a preset fault type. The application will then send this information to the vehicle fault diagnosis platform in real time. In addition, some advanced vehicles may be equipped with an on-board communication system that allows the vehicle to automatically send fault warnings to the platform without the owner's manual operation. After receiving the instructions sent by the owner or the automatic fault warning, the vehicle fault diagnosis platform will immediately start the fault data diagnosis process for the vehicle, using big data analysis and advanced algorithms to identify possible problems and generate a preliminary fault diagnosis report.

[0030] In another optional embodiment, the vehicle fault diagnosis platform can not only respond to the owner's instructions, but also autonomously screen and monitor the vehicle information stored on the platform. This function relies on the platform's ability to continuously collect and process massive amounts of vehicle data. The platform will regularly or in real time analyze each vehicle's operating data, including mileage, engine status, fuel consumption, sensor readings, etc., to identify potential abnormal signs. This random but targeted vehicle screening mechanism helps to detect and prevent faults in advance, improve road safety, and also saves car owners the maintenance costs and inconvenience caused by faults.

[0031] In summary, whether through active reporting by car owners or intelligent screening by the platform, the vehicle fault diagnosis platform is constantly optimizing its service processes and technical means to ensure vehicle safety in a more efficient and intelligent way and enhance the travel experience of car owners.

[0032] S102: Identify the vehicle identification and the controller identification, and determine the faulty vehicle and the target controller where the fault occurs.

[0033] Here, the vehicle ID and controller ID are identified by the $19 (or 0x19) signal. The vehicle fault diagnosis platform identifies the vehicle ID and controller ID by parsing the received fault diagnosis instructions. Then, it searches its database for vehicle and controller information that matches these IDs. Once a match is found, the faulty vehicle and the specific controller that has failed can be determined. This step is the basis for subsequent fault diagnosis work and ensures the accuracy and pertinence of the diagnosis.

[0034] S103: Send a message acquisition signal to the vehicle, and receive a communication frame from the target controller returned by the vehicle.

[0035] Here, after determining the faulty vehicle and the target controller, the vehicle fault diagnosis platform will send a message acquisition signal to the vehicle, which contains an instruction requesting the target controller to send its current status. After receiving this signal, the vehicle will forward it to the target controller, which will generate the corresponding communication frame according to the instruction and return it to the vehicle fault diagnosis platform through the vehicle.

[0036] S104: When it is detected that the communication frame of the target controller is not empty, determine whether the vehicle has a communication-related fault.

[0037] In this step, first, it is determined whether the communication frame of the target controller is empty. The platform feedback result includes the first platform feedback result. If the communication frame is empty, continue to send messages to the vehicle to obtain signals and detect the communication frames. When it is detected that the communication frames are all empty within a preset time period, it is determined whether there is historical fault data of the vehicle on the vehicle fault diagnosis platform. If there is historical fault data, the historical fault data recorded by the platform is output as a possible fault to facilitate subsequent fault diagnosis of the vehicle. Here, historical fault data refers to faults that have occurred in the vehicle before and parts that have been replaced in the past.

[0038] If there is no historical fault data, the detection is stopped and the feedback result of the first platform is output. It is inferred that the vehicle has not been powered on for a long time and the usage frequency is low. The detection is stopped. When the platform detects the vehicle again, the fault diagnosis is performed in real time based on the fault data.

[0039] Specifically, if the communication frame received by the vehicle fault diagnosis platform is empty, that is, no response is received from the target controller, then the vehicle fault diagnosis platform will think that the target controller may be in a fault state or cannot work normally. At this time, the vehicle fault diagnosis platform will continue to send messages to the vehicle to obtain signals and detect the communication frame again. This process may be repeated multiple times to ensure the accuracy of the diagnosis.

[0040] If the vehicle fault diagnosis platform continues to receive empty communication frames within a preset time period, that is, the target controller does not respond during this period, it will stop further detection and output a first platform feedback result. This feedback result usually indicates that the target controller cannot communicate or may have a serious fault, requiring further inspection or repair.

[0041] It is recognized that any CAN communication frame uploaded by the target controller is not empty, that is, the target controller has been awakened and the signal transmission is normal.

[0042] Determine if the vehicle has a communication-related fault by:

[0043] The platform is also configured to:

[0044] When it is detected that the communication frame is not empty, a fault detection signal is sent to the vehicle. Here, the communication frame is not empty to indicate that the vehicle is powered on.

[0045] In this step, when it is detected that the communication frame received from the vehicle is not empty, it indicates that the vehicle has been powered on and its control system is operating normally, at least to a certain extent, and can respond to external requests. At this time, it is not immediately concluded that the vehicle has no fault, but a series of operations are further performed to check whether the vehicle has a communication-related fault.

[0046] Receive the message signal fed back by the vehicle, and determine the communication failure result of the vehicle according to the message signal.

[0047] When the communication frame is confirmed to be not empty, the platform will immediately send a fault detection signal to the vehicle. This signal is a specific request that requires the vehicle to perform a self-test on its communication system and return the test results, which helps the system to better understand the vehicle's communication status and whether there is a potential communication fault.

[0048] After receiving the fault detection signal, the vehicle will perform the corresponding self-detection procedure and generate a message signal containing the detection results and return it to the system. After receiving this message signal, the system will parse it to extract detailed information about the vehicle's communication status.

[0049] Specifically, the vehicle includes a telematics box (TBOX), a central control unit (CCU), a battery management system (BMS), a motor drive control unit (MDCU) and an engine management system (EMS).

[0050] Here, the target controller is at least one of a battery management controller, a power domain controller, and a transmitter controller.

[0051] Here, the platform feedback result also includes a fourth platform feedback result.

[0052] The platform is also configured to:

[0053] Determine whether the message signal transmitted by the remote communication controller indicates that the central gateway controller has lost communication or a communication verification failure; if the message signal transmitted by the remote communication controller indicates that the central gateway controller has lost communication or a communication verification failure, determine that the vehicle has a communication-related failure, and output a fourth platform feedback result;

[0054] If the message signal transmitted by the remote communication controller does not indicate a communication loss or a communication verification failure of the central gateway controller, determining whether the message signal transmitted by the central gateway controller indicates a communication loss or a communication verification failure of the remote communication controller;

[0055] If the message signal transmitted by the central gateway controller indicates that the remote communication controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure and the fourth platform feedback result is output;

[0056] If the message signal transmitted by the central gateway controller does not indicate a communication loss and a communication verification failure of the remote communication controller, it means that no communication-related failure occurs between the central gateway controller and the remote communication controller.

[0057] Here, the platform is also configured as:

[0058] Determine whether the message signal transmitted by the target controller indicates that the central gateway controller has lost communication or a communication verification failure; if the message signal transmitted by the target controller indicates that the central gateway controller has lost communication or a communication verification failure, determine that the vehicle has a communication-related failure, and output a fourth platform feedback result;

[0059] If the message signal transmitted by the target controller does not indicate a communication loss or a communication verification failure of the central gateway controller, determining whether the message signal transmitted by the central gateway controller indicates a communication loss or a communication verification failure of the target controller;

[0060] If the message signal transmitted by the central gateway controller indicates that the target controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure, and the fourth platform feedback result is output; if the message signal transmitted by the central gateway controller does not indicate that the target controller has lost communication and a communication verification failure, it means that there is no communication-related failure between the central gateway controller and the target controller;

[0061] Among them, by analyzing the message signal, the platform can determine whether the vehicle has a communication-related fault. This may include communication line failure, controller failure, communication protocol mismatch and other issues. The platform will conduct a comprehensive analysis and evaluation of the parsed information based on the preset fault judgment logic and rules, and ultimately determine the result of the communication failure.

[0062] When it is detected that no communication-related faults occur between the central gateway controller and the remote communication controller and between the central gateway controller and the target controller, it is confirmed that there are no communication-related faults in the vehicle.

[0063] When a communication-related fault occurs in any path between the central gateway controller and the remote communication controller or between the central gateway controller and the target controller, that is, the fault code of any controller is identified, the fourth platform directly feeds back the result, that is, the communication link fault.

[0064] In an optional embodiment, the vehicle fault diagnosis platform screens whether there are communication-related faults in key nodes on the three communication links of TBOX, CCU, and target controller, that is, whether TBOX reports CCU communication loss and communication verification fault, whether CCU reports TBOX communication loss and communication verification fault, whether CCU reports MDCU communication loss and communication verification fault, and whether MDCU reports CCU communication loss and communication verification fault, to ensure that the communication quality of the controller with direct network communication is guaranteed to avoid the execution failure, execution error and other consequences of the subsequently issued tasks. If there is no such communication failure, the next step of task distribution is carried out.

[0065] S105. If the vehicle has a communication-related fault, directly output the platform feedback result.

[0066] If the vehicle has a communication-related fault, the platform will directly determine and feedback the corresponding results. In this scenario, if the detected fault is related to the communication link, the platform will clearly feedback "communication link failure".

[0067] This means that there is a problem in the communication link inside the vehicle or between the vehicle and external systems (such as remote monitoring systems, diagnostic platforms, etc.). Communication link failure can be caused by many reasons, including but not limited to:

[0068] Physical connection problems: For example, the communication line is disconnected, poorly connected, or damaged.

[0069] Communication protocol mismatch: The communication protocol between the vehicle controller and the external system is incompatible.

[0070] Controller failure: The controller responsible for the communication function (such as TBOX, CCU, etc.) fails.

[0071] Software problem: There are errors or exceptions in the communication-related software program, resulting in the inability to communicate normally.

[0072] Electromagnetic interference: External electromagnetic interference may cause communication signal distortion or loss.

[0073] When the platform reports a "communication link failure", vehicle maintenance personnel or technical support personnel need to further analyze and locate the specific cause of the failure based on this information, combined with the actual situation of the vehicle and the fault phenomenon. It is recommended to use professional diagnostic tools and equipment to conduct comprehensive inspection and testing of the vehicle's communication system to find and solve the fault point.

[0074] At the same time, it is determined that the vehicle owner is advised to take appropriate measures according to the maintenance suggestions to ensure the safe operation of the vehicle and the normal functioning of the communication function.

[0075] S106: If there is no communication-related fault in the vehicle, a fault data acquisition signal is sent to the vehicle, and fault data corresponding to feedback from the target controller returned by the vehicle is received.

[0076] Wherein, the remote communication controller is used to receive a fault data acquisition signal from the vehicle fault diagnosis platform and transmit the fault data acquisition signal to the central gateway controller;

[0077] The central gateway controller is used to receive a fault data acquisition signal from the remote communication controller and transmit the fault data acquisition signal to a target controller.

[0078] The target controller is used to receive a fault data acquisition signal from the central gateway controller, and transmit the fault data fed back by the target controller to the central gateway controller;

[0079] The central gateway controller is also used to receive fault data from the target controller and transmit the fault data to the remote communication controller;

[0080] The remote communication controller is also used to receive fault data from the central gateway controller and transmit the fault data to the vehicle fault diagnosis platform.

[0081] S107, analyzing the fault data and outputting the platform feedback results.

[0082] See also Figure 2 , Figure 2 This is the second flow chart of the vehicle fault diagnosis platform provided in the embodiment of the present application. Figure 2 As shown in , the vehicle fault diagnosis platform provided in the embodiment of the present application is configured as follows:

[0083] Here, the platform feedback result includes the second platform feedback result and the third platform feedback result.

[0084] S201, sorting and analyzing the fault data corresponding to the feedback from the target controller returned by the vehicle;

[0085] Fault data is collected from the target controller of the vehicle, which is usually done through the vehicle's diagnostic interface (such as OBD-II) using dedicated data reading tools or software to ensure that the normal operation of the vehicle is not affected during the data collection process while protecting the security and integrity of the data.

[0086] Perform preliminary processing on the collected fault data to remove duplicate, invalid or incorrectly formatted data, ensure that key information is not lost during the data cleaning process, and improve the readability and usability of the data. Convert the cleaned data into a format recognizable by the platform and extract key information (such as fault code, fault description, occurrence time, etc.) to ensure the accuracy and completeness of the analysis and avoid misjudgment or omissions.

[0087] S202, determining whether the fault data is negative feedback;

[0088] According to the preset rules or algorithms, determine whether the fault data contains unrecognizable information or does not conform to the expected format. The rule-based matching algorithm and machine learning classification algorithm ensure the accuracy of negative feedback identification and avoid false alarms or missed alarms.

[0089] S203: If the fault data is negative feedback, it means that the platform has not identified the fault data, and outputs the second platform feedback result;

[0090] When negative feedback is identified, the second platform feedback result is that the specific content of the fault data is not identified, then a feedback message containing the cause of the failure is generated. The feedback message includes: the cause of the failure, possible solutions, and recommended follow-up operations, ensuring the clarity and accuracy of the feedback information and helping users quickly locate the problem.

[0091] The generated feedback messages will be sent to users or related systems via email notifications, SMS notifications, and platform message push notifications to ensure the timeliness and reliability of feedback output and avoid information loss or delay.

[0092] S204: If the fault data is not negative feedback, it means that the platform recognizes the fault data, stores the fault data, and outputs a third platform feedback result.

[0093] When it is identified that it is not negative feedback, the feedback result of the third platform is the identification of the specific content of the fault data, and the identified fault data is stored in the database or cloud storage for subsequent analysis and processing. Here, the database includes but is not limited to relational databases and NoSQL databases to ensure the security and consistency of data storage and avoid data loss or damage.

[0094] Generate a feedback message containing successful read information, confirmation of successful read, storage location, and possible follow-up operation suggestions, ensuring the conciseness and clarity of the feedback information to help users understand the read results.

[0095] Like the feedback result of the second platform mentioned above, the generated feedback message will be sent to the user or related system by email notification, SMS notification and platform message push to ensure the timeliness and reliability of the feedback output and avoid information loss or delay.

[0096] The vehicle fault diagnosis platform and vehicle provided in the embodiment of the present application, the platform is configured to: receive fault diagnosis instructions, the fault diagnosis instructions include vehicle identification and controller identification; identify the vehicle identification and controller identification, determine the vehicle with fault and the target controller with fault; send a message acquisition signal to the vehicle, and receive the communication frame of the target controller returned by the vehicle; when it is detected that the communication frame of the target controller is not empty, determine whether the vehicle has a communication-related fault; if the vehicle has a communication-related fault, directly output the platform feedback result; if the vehicle does not have a communication-related fault, send a fault data acquisition signal to the vehicle, and receive the fault data corresponding to the feedback of the target controller returned by the vehicle; analyze the fault data, and output the platform feedback result. Through this application, the fault data of the vehicle can be remotely diagnosed after the vehicle is powered on, and the platform can automatically send a fault data acquisition signal after identifying that the vehicle is powered on, thereby improving the efficiency of fault diagnosis.

[0097] The vehicle fault diagnosis platform has greatly changed the traditional after-sales model in which vehicles must be taken to service stations for offline diagnosis by personnel. The online real-time diagnosis can realize remote vehicle fault diagnosis, obtain the necessary information for after-sales maintenance in a timely manner, and perform fault diagnosis and early warning in advance.

[0098] This application is used for all new energy vehicles with remote communication, and proposes a vehicle fault diagnosis platform based on real-time task triggering. The platform can actively identify the wake-up state of the vehicle controller and automatically issue diagnostic tasks. The completion of the diagnostic task no longer depends on whether the vehicle is online, which greatly removes the restrictions implemented manually. It can detect whether there is a communication failure in the remote diagnostic path through periodic detection when the user powers on (communication frame is detected), and then remotely diagnose the vehicle fault data when there is no communication failure, thereby improving the diagnostic efficiency.

[0099] Based on the same inventive concept, a vehicle fault diagnosis method corresponding to the vehicle fault diagnosis platform is also provided in the embodiment of the present application. Since the principle of solving the problem by the platform in the embodiment of the present application is similar to the above-mentioned vehicle fault diagnosis method in the embodiment of the present application, the implementation of the method can refer to the implementation of the method, and the repeated parts will not be repeated.

[0100] The embodiment of the present application also provides a vehicle fault diagnosis method, which is applied to a vehicle fault diagnosis platform. The vehicle fault diagnosis method includes:

[0101] receiving a fault diagnosis instruction, wherein the fault diagnosis instruction includes a vehicle identification and a controller identification;

[0102] Identifying the vehicle identifier and the controller identifier, and determining a faulty vehicle and a target controller having a fault;

[0103] Sending a message acquisition signal to the vehicle, and receiving a communication frame from the target controller returned by the vehicle;

[0104] When it is detected that the communication frame of the target controller is not empty, determining whether the vehicle has a communication-related fault;

[0105] If the vehicle has a communication-related fault, the platform feedback result will be directly output;

[0106] If the vehicle does not have a communication-related fault, a fault data acquisition signal is sent to the vehicle, and fault data corresponding to feedback from the target controller returned by the vehicle is received;

[0107] Analyze the fault data and output the platform feedback result.

[0108] The present application also provides a vehicle, see Figure 3 , Figure 3 This is a schematic diagram of the structure of a vehicle provided in an embodiment of the present application. Figure 3 As shown in , the vehicle 300 provided in the embodiment of the present application includes a remote communication controller 301 , a central gateway controller 302 and a target controller 303 .

[0109] The remote communication controller 301 is used to receive the fault diagnosis instruction from the central gateway controller 302, and transmit the fault diagnosis instruction to the vehicle fault diagnosis platform, and receive the message acquisition signal from the vehicle fault diagnosis platform, and transmit the message acquisition signal to the central gateway controller 302, and receive the communication frame from the central gateway controller 302, and transmit the communication frame to the vehicle fault diagnosis platform, and receive the fault data acquisition signal from the vehicle fault diagnosis platform, and transmit the fault data acquisition signal to the central gateway controller 302, and receive the fault data from the central gateway controller 302, and transmit the fault data to the vehicle fault diagnosis platform;

[0110] The central gateway controller 302 is used for generating a fault diagnosis instruction when receiving a fault signal from the target controller 303, and reporting the fault diagnosis instruction to the remote communication controller 301, and receiving the message acquisition signal from the remote communication controller 301, transmitting the message acquisition signal to the target controller 303, and receiving a communication frame from the target controller 303, and transmitting the communication frame to the remote communication controller 301, and receiving a fault data acquisition signal from the remote communication controller 301, transmitting the fault data acquisition signal to the target controller 303, and receiving fault data from the target controller 303, and transmitting the fault data to the remote communication controller 301;

[0111] The target controller 303 is used to receive the message acquisition signal from the central gateway controller 302, and transmit the communication frame of the target controller 303 to the central gateway controller 302, and receive the fault data acquisition signal from the central gateway controller 302, and transmit the fault data to the central gateway controller 302.

[0112] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

[0114] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0115] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0116] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0117] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A vehicle fault diagnosis platform, characterized in that: The platform is configured to: receiving a fault diagnosis instruction, wherein the fault diagnosis instruction includes a vehicle identification and a controller identification; Identifying the vehicle identifier and the controller identifier, and determining a faulty vehicle and a target controller having a fault; Sending a message acquisition signal to the vehicle, and receiving a communication frame from the target controller returned by the vehicle; When detecting that the communication frame of the target controller is not empty, determining whether the vehicle has a communication-related fault; If the vehicle has a communication-related fault, the platform feedback result will be directly output; If the vehicle does not have a communication-related fault, a fault data acquisition signal is sent to the vehicle, and fault data corresponding to feedback from the target controller returned by the vehicle is received; Analyze the fault data and output the platform feedback result.

2. The platform according to claim 1, characterized in that The platform feedback result includes a first platform feedback result, Wherein, the platform is further configured as: If the communication frame is empty, continue to send the message acquisition signal to the vehicle and detect the communication frame; When it is detected that the communication frames are all empty within a preset time period, the first platform feedback result is output.

3. The platform according to claim 1, characterized in that: The vehicle includes a remote communication controller, a central gateway controller, a battery management controller, a power domain controller and a transmitter controller, and the target controller is at least one of the battery management controller, the power domain controller and the transmitter controller. Wherein, the remote communication controller is used to receive the fault data acquisition signal from the vehicle fault diagnosis platform and transmit the fault data acquisition signal to the central gateway controller; The central gateway controller is used for receiving the fault data acquisition signal from the remote communication controller and transmitting the fault data acquisition signal to the target controller.

4. The platform according to claim 3, characterized in that: The target controller is used to receive the fault data acquisition signal from the central gateway controller, and transmit the fault data fed back by the target controller to the central gateway controller; The central gateway controller is also used to receive the fault data from the target controller and transmit the fault data to the remote communication controller; The remote communication controller is also used to receive the fault data from the central gateway controller and transmit the fault data to the vehicle fault diagnosis platform.

5. The platform according to claim 1, characterized in that: The platform feedback result includes a second platform feedback result and a third platform feedback result, and the platform is further configured to: Arrange and analyze the fault data corresponding to the feedback from the target controller returned by the vehicle; Determining whether the fault data is negative feedback; If the fault data is negative feedback, it means that the platform does not recognize the fault data, and outputs the second platform feedback result; If the fault data is not negative feedback, it means that the platform recognizes the fault data, stores the fault data, and outputs a third platform feedback result.

6. The platform according to claim 2, characterized in that: The platform is also configured to: When it is detected that the communication frame is not empty, a fault detection signal is sent to the vehicle, and the communication frame is not empty to indicate that the vehicle is powered on; Receive the message signal fed back by the vehicle, and determine the communication failure result of the vehicle according to the message signal.

7. The platform according to claim 6, characterized in that The platform feedback result also includes a fourth platform feedback result, Wherein, the platform is further configured as: Determining whether the message signal transmitted by the remote communication controller indicates a communication loss or a communication verification failure of the central gateway controller; If the message signal transmitted by the remote communication controller indicates that the central gateway controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure, and a fourth platform feedback result is output; If the message signal transmitted by the remote communication controller does not indicate a communication loss or a communication verification failure of the central gateway controller, determining whether the message signal transmitted by the central gateway controller indicates a communication loss or a communication verification failure of the remote communication controller; If the message signal transmitted by the central gateway controller indicates that the remote communication controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure, and a fourth platform feedback result is output; If the message signal transmitted by the central gateway controller does not indicate communication loss and communication verification failure of the remote communication controller, it means that no communication-related failure occurs between the central gateway controller and the remote communication controller.

8. The platform according to claim 7, characterized in that The platform is also configured to: Determining whether the message signal transmitted by the target controller indicates a communication loss or a communication verification failure of the central gateway controller; If the message signal transmitted by the target controller indicates that the central gateway controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure, and a fourth platform feedback result is output; If the message signal transmitted by the target controller does not indicate a communication loss or a communication verification failure of the central gateway controller, determining whether the message signal transmitted by the central gateway controller indicates a communication loss or a communication verification failure of the target controller; If the message signal transmitted by the central gateway controller indicates that the target controller has lost communication or a communication verification failure, it is determined that the vehicle has a communication-related failure, and a fourth platform feedback result is output; If the message signal transmitted by the central gateway controller does not indicate a communication loss and a communication verification failure of the target controller, it means that no communication-related failure occurs between the central gateway controller and the target controller; When it is detected that no communication-related fault occurs between the central gateway controller and the remote communication controller and between the central gateway controller and the target controller, it is confirmed that no communication-related fault occurs in the vehicle.

9. A vehicle fault diagnosis method, characterized in that: Applied to vehicle fault diagnosis platform, including: receiving a fault diagnosis instruction, wherein the fault diagnosis instruction includes a vehicle identification and a controller identification; Identifying the vehicle identifier and the controller identifier, and determining a faulty vehicle and a target controller having a fault; Sending a message acquisition signal to the vehicle, and receiving a communication frame from the target controller returned by the vehicle; When detecting that the communication frame of the target controller is not empty, determining whether the vehicle has a communication-related fault; If the vehicle has a communication-related fault, the platform feedback result will be directly output; If the vehicle does not have a communication-related fault, a fault data acquisition signal is sent to the vehicle, and fault data corresponding to feedback from the target controller returned by the vehicle is received; Analyze the fault data and output platform feedback results.

10. A vehicle, characterized in that: The vehicle includes a remote communication controller, a central gateway controller and a target controller, Wherein, the remote communication controller is used to receive the fault diagnosis instruction from the central gateway controller and transmit the fault diagnosis instruction to the vehicle fault diagnosis platform, and receive the message acquisition signal from the vehicle fault diagnosis platform and transmit the message acquisition signal to the central gateway controller, and receive the communication frame from the central gateway controller and transmit the communication frame to the vehicle fault diagnosis platform, and receive the fault data acquisition signal from the vehicle fault diagnosis platform and transmit the fault data acquisition signal to the central gateway controller, and receive the fault data from the central gateway controller and transmit the fault data to the vehicle fault diagnosis platform; The central gateway controller is used for generating a fault diagnosis instruction when receiving a fault signal from the target controller, and reporting the fault diagnosis instruction to the remote communication controller, and receiving the message acquisition signal from the remote communication controller, transmitting the message acquisition signal to the target controller, and receiving a communication frame from the target controller, and transmitting the communication frame to the remote communication controller, and receiving a fault data acquisition signal from the remote communication controller, transmitting the fault data acquisition signal to the target controller, and receiving fault data from the target controller, and transmitting the fault data to the remote communication controller; The target controller is used to receive the message acquisition signal from the central gateway controller and transmit the communication frame of the target controller to the central gateway controller, and to receive the fault data acquisition signal from the central gateway controller and transmit the fault data to the central gateway controller.

Images