Method for generating fault code, device for generating fault code, and vehicle

Abstract

The application provides a fault code generation method, a fault code generation device and a vehicle. The method comprises the following steps: if a diagnosis instruction in the vehicle is detected, a target component corresponding to the diagnosis instruction is diagnosed to obtain diagnosis data of the target component; wherein the diagnosis data comprises diagnosis results of at least one diagnosis event of the target component; if fault information exists in the diagnosis results, a target diagnosis combination corresponding to the target component is acquired; wherein the target diagnosis combination is used for indicating a combination of different diagnosis events of the target component; and based on the diagnosis results and the target diagnosis combination, a fault code of the target component is generated. The method can reduce the number of fault codes and improve the convenience of vehicle fault management.

Description

Technical Field

[0001] This application relates to the field of vehicles, and more specifically, to a method for generating fault codes, a device for generating fault codes, and a vehicle. Background Technology

[0002] As vehicles become increasingly intelligent, they are able to perform more and more functions. People are paying more attention to vehicle quality and fault management as well.

[0003] Currently, vehicle fault diagnosis primarily relies on manufacturer-defined fault codes. Each diagnostic event has a corresponding fault code, and users must use specialized after-sales diagnostic equipment to determine their meaning, thus reducing the convenience of vehicle fault management. Therefore, reducing the number of fault codes and improving the convenience of vehicle fault management has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method for generating fault codes, a device for generating fault codes, and a vehicle. The method can reduce the number of fault codes and improve the convenience of vehicle fault management.

[0005] In a first aspect, a method for generating a fault code is provided. The method includes: if a diagnostic command is detected in a vehicle, performing a diagnosis on a target component corresponding to the diagnostic command to obtain diagnostic data of the target component; wherein the diagnostic data includes diagnostic results of executing at least one diagnostic event of the target component; if fault information exists in the diagnostic results, obtaining a target diagnostic combination corresponding to the target component; wherein the target diagnostic combination is used to indicate a combination of different diagnostic events of the target component; and generating a fault code for the target component based on the diagnostic results and the target diagnostic combination.

[0006] In the above technical solution, if fault information is found in the diagnostic results, the target diagnostic combination corresponding to the target component is obtained, and a fault code for the target component is generated based on the diagnostic results and the target diagnostic combination. In this application, the target diagnostic combination indicates a combination of different diagnostic events of the target component. By combining the different diagnostic events of the target component through the diagnostic results and the target diagnostic combination, a fault code is generated. Since the fault code is a combination of multiple diagnostic events, compared with each diagnostic event corresponding to one fault code, the number of fault codes can be reduced, thereby improving the convenience of vehicle fault management.

[0007] In conjunction with the first aspect, in some possible implementations, before stating that fault information exists in the diagnostic results, the method further includes: determining whether the fault information exists in the diagnostic results; if at least one diagnostic event in the diagnostic data has a diagnostic result in a set state, determining that the fault information exists in the diagnostic results.

[0008] The above technical solution determines whether fault information exists in the diagnostic results. If at least one diagnostic event in the diagnostic data has a diagnostic result that is set, it is determined that fault information exists in the diagnostic results. Compared with comparing each diagnostic result and determining that the target component has fault information in the diagnostic results when each diagnostic result has fault information, this application can improve the efficiency of determining the presence of fault information in the diagnostic results by judging multiple diagnostic results in the diagnostic data.

[0009] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: determining the logical relationship between different diagnostic events in the target diagnostic combination; generating the fault code based on the status bit corresponding to each diagnostic event and the logical relationship between the different diagnostic events; wherein the status bit is the set state or the unset state.

[0010] The above technical solution determines the logical relationship between different diagnostic events in the target diagnostic combination and generates a fault code based on the status bit corresponding to each diagnostic event and the logical relationship between different diagnostic events. Since the status bit is either set or not set, the results of different diagnostic events are combined into a fault code by combining the status corresponding to each diagnostic event and the logical relationship between different diagnostic events. That is, a fault code can include the diagnostic results of multiple diagnostic events, thereby reducing the number of fault codes and facilitating fault code management.

[0011] In conjunction with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: if the fault information exists in the diagnostic results, obtaining a preset combination relationship; wherein the preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component; and determining the target diagnostic combination based on the target component and the preset combination relationship.

[0012] The above technical solution, if fault information is found in the diagnostic results, obtains the preset combination relationship, and determines the target diagnostic combination based on the target component and the preset combination relationship; since the preset combination relationship indicates the correspondence between the preset diagnostic combination and the vehicle component, the target diagnostic combination can be quickly determined through the target component, thereby improving the efficiency of determining the target diagnostic combination.

[0013] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: determining the target position of the target component in the vehicle; displaying the target position of the target component and outputting fault prompt information; wherein the fault prompt information is used to indicate that the target component has a fault.

[0014] The above technical solution determines the target location of the target component in the vehicle, displays the target location of the target component, and outputs fault prompt information. Since the fault prompt information indicates that the target component is faulty, by displaying the target location of the target component and outputting the fault prompt information, the user can determine the location of the faulty target component, thereby handling the fault in the vehicle and improving driving safety.

[0015] In conjunction with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: if the diagnostic command in the vehicle is detected during a preset time period, diagnosing the target component to obtain updated diagnostic data of the target component; wherein the updated diagnostic data includes updated diagnostic results of executing at least one diagnostic event of the target component; if the fault information exists in the updated diagnostic results, generating the fault code of the target component; determining the number of times the fault code is generated; and outputting prompt information based on the number of generation times.

[0016] The above technical solution determines the number of times a fault code of a target component is generated within a preset time period and outputs a prompt message based on the number of generation. Since the prompt message is used to eliminate the fault of the target component, by outputting the prompt message, the user can be prompted to eliminate the fault of the target component as soon as possible, thereby improving driving safety.

[0017] In conjunction with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: if the number of generation times is less than or equal to a preset number of generation times, outputting a first prompt message; wherein the first prompt message is used to prompt the user to execute a target event, the target event being used to eliminate the fault of the target component; if the number of generation times is greater than the preset number of generation times, outputting a second prompt message; wherein the second prompt message is used to prompt the target component to be inspected.

[0018] The above technical solution outputs a first prompt if the number of generation attempts is less than or equal to a preset number of generation attempts. Since the first prompt is used to prompt the user to perform a target event, which is used to eliminate the fault of the target component, prompting the user to perform the target event through the first prompt can eliminate vehicle faults caused by driving habits, thereby improving user convenience. If the number of generation attempts exceeds the preset number of generation attempts, a second prompt is output. Since the second prompt is used to prompt the user to inspect the target component, outputting the second prompt can promptly prompt the user to inspect the vehicle, thereby improving driving safety.

[0019] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: if the number of generation is less than or equal to the preset number of generation, determining the target event based on the relationship between the target component and the preset event; wherein the preset event relationship is used to represent the correspondence between the preset event and the preset component; and outputting the first prompt information based on the target event.

[0020] The above technical solution, if the number of generation times is less than or equal to the preset number of generation times, determines the target event based on the relationship between the target component and the preset event, and outputs the first prompt information based on the target event; since the preset event relationship is used to represent the correspondence between the preset event and the preset component, the corresponding first prompt information is output based on the target event, thereby prompting the user to execute the first prompt information to eliminate the fault in the target component, and to avoid vehicle repair caused by false alarms as much as possible, which can improve the convenience of user use.

[0021] Secondly, a fault code generation device is provided. This device includes: a diagnostic module, configured to, if a diagnostic command is detected in a vehicle, diagnose a target component corresponding to the diagnostic command and obtain diagnostic data for the target component; wherein the diagnostic data includes diagnostic results of executing at least one diagnostic event of the target component; an acquisition module, configured to, if fault information exists in the diagnostic results, acquire a target diagnostic combination corresponding to the target component; wherein the target diagnostic combination indicates a combination of different diagnostic events of the target component; and a generation module, configured to generate a fault code for the target component based on the diagnostic results and the target diagnostic combination.

[0022] Thirdly, a vehicle is provided, including a memory and a processor, wherein the memory is used to store executable program code; and the processor is used to call and run the executable program code from the memory, causing the vehicle to execute the fault code generation method in the first aspect or any possible implementation thereof.

[0023] Fourthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the fault code generation method of the first aspect or any possible implementation thereof.

[0024] Fifthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to execute the fault code generation method of the first aspect or any possible implementation thereof. Attached Figure Description

[0025] Figure 1 This is a schematic diagram illustrating a method for generating fault codes according to an embodiment of this application.

[0026] Figure 2 This is a schematic diagram illustrating a scenario of another method for generating fault codes provided in an embodiment of this application;

[0027] Figure 3 This is a schematic flowchart illustrating a method for generating fault codes provided in an embodiment of this application;

[0028] Figure 4 This is a schematic diagram of a fault repair scenario provided in an embodiment of this application;

[0029] Figure 5 This is a schematic flowchart illustrating another method for generating fault codes provided in an embodiment of this application;

[0030] Figure 6 This is a schematic diagram of the structure of a fault code generation device provided in an embodiment of this application;

[0031] Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0032] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0033] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0034] It should be noted that since vehicle fault diagnosis mainly relies on fault codes defined by the vehicle manufacturer, each diagnostic event has a corresponding fault code, and users must use dedicated after-sales diagnostic equipment to determine their meaning, thus reducing the convenience of vehicle fault management. In view of this, this application provides a fault code generation method, a fault code generation device, and a vehicle. This method can reduce the number of fault codes and improve the convenience of vehicle fault management.

[0035] Figure 1 This is a schematic diagram illustrating a method for generating fault codes provided in an embodiment of this application.

[0036] For example, such as Figure 1 As shown, if a diagnostic command is detected in the vehicle, the controller corresponding to the diagnostic command is diagnosed, and the diagnostic data of the controller is obtained as the data corresponding to diagnostic event 1. If the diagnostic data is the diagnostic result corresponding to diagnostic event 1: short circuit fault of the controller chip, and the target diagnostic combination is a combination of different diagnostic events of the controller (diagnostic event 1, diagnostic event 2 and diagnostic event 3), then the fault code of bit 7-0 is generated as 001011111 based on the target diagnostic combination and the diagnostic result, and a prompt message is output. The prompt message is used to indicate that there is a fault in the controller.

[0037] Figure 2 This is a schematic diagram illustrating another method for generating fault codes provided in this application.

[0038] For example, such as Figure 2 As shown, if a diagnostic command is detected in the vehicle, the controller corresponding to the diagnostic command is diagnosed, and the diagnostic data of the controller is obtained as the data corresponding to diagnostic event 3. If the diagnostic data is the diagnostic result corresponding to diagnostic event 3: controller electrostatic breakdown fault, and the target diagnostic combination is a combination of different diagnostic events of the controller (diagnostic event 1, diagnostic event 2 and diagnostic event 3), then the fault code bit 7-0 is generated as 001011111 based on the target diagnostic combination and diagnostic result, and a prompt message is output. The prompt message is used to indicate that there is a fault in the controller.

[0039] Understandably, although Figure 1 neutralization Figure 2The diagnostic data obtained are different data from the same vehicle component, but because different diagnostic events of the vehicle component are combined, the resulting fault codes are the same. Since diagnostic combinations are made by merging the characteristics of the vehicle component, the efficiency of fault detection can be improved. Specifically, the characteristics of the vehicle component can be defined by the manufacturer or developers based on the common diagnostic features of different diagnoses and then merged. For example, since chip faults in the controller all require chip repair or replacement, and controller faults such as chip short circuits, open circuits, capacitor aging, and electrostatic discharge are all chip faults, the controller needs to be repaired or replaced if these diagnostic events are not merged. Without merging these diagnostic events, at least four fault codes would be required, including custom fault codes. However, because their maintenance method is consistent, merging these diagnostic events into one fault code helps reduce controller fault codes and facilitates fault management.

[0040] Figure 3 This is a schematic flowchart illustrating a method for generating fault codes provided in an embodiment of this application.

[0041] For example, Figure 3 The method shown can be executed by the vehicle's overall controller or chip.

[0042] For example, such as Figure 3 As shown, the method 300 includes the following procedures:

[0043] S310: If a diagnostic command is detected in the vehicle, the target component corresponding to the diagnostic command is diagnosed to obtain the diagnostic data of the target component.

[0044] For example, a diagnostic instruction may include an identifier for the target component. For instance, if the diagnostic instruction is: "Diagnose the vehicle controller," then the target component is the controller; or, if the diagnostic instruction is: "Diagnose component group number 10 in the vehicle," then based on the preset relationship between the combination and vehicle components, the target component is determined to be the transmitter. The method for determining the target component in the vehicle based on the diagnostic instruction can be determined according to the actual situation and is not specifically limited here.

[0045] It should be noted that the diagnostic data includes the diagnostic results of at least one diagnostic event performed on the target component. It is understood that diagnosing the target component may involve the diagnostic results of multiple diagnostic events; for example, if the target component is a controller, diagnostic events may include controller chip short circuit diagnosis, controller chip open circuit diagnosis, controller electrostatic discharge (ESD) diagnosis, etc., and multiple diagnostic events correspond to multiple diagnostic results, which may include controller chip short circuit faults, controller chip open circuit faults, controller ESD faults, etc.

[0046] It is understood that the diagnostic data includes the diagnostic results of at least one diagnostic event of the target component, and the diagnostic results of at least one diagnostic event may all contain non-fault information or all contain fault information; or, the diagnostic results of multiple diagnostic events may contain both fault information and non-fault information.

[0047] For example, diagnostic results can be represented using text data. If the diagnostic results only include controller circuit diagnostic results, the presence of fault information in the diagnostic results can be determined based on the controller circuit diagnostic results. For example, the controller circuit state may be abnormal, or the control circuit state may be normal. If the controller circuit state is abnormal, it indicates that fault information exists in the diagnostic results; if the controller circuit state is normal, it indicates that fault information does not exist in the diagnostic results. Alternatively, diagnostic results can be represented by the state bit of the diagnostic results. For example, a controller circuit state of 1 indicates that the controller circuit state is abnormal, i.e., fault information exists in the diagnostic results; a controller circuit state of 0 indicates that the controller circuit state is normal, i.e., fault information does not exist in the diagnostic results.

[0048] S320, if fault information is found in the diagnostic results, obtain the target diagnostic combination corresponding to the target component.

[0049] It should be noted that the target diagnostic combination is used to indicate a combination of different diagnostic events for a target component. For example, if the diagnostic events for the target component include diagnostic event 1, diagnostic event 2, and diagnostic event 3, then the target diagnostic combination can be (diagnostic event 1, diagnostic event 2, or diagnostic event 3).

[0050] For example, the target diagnostic combination corresponding to the target component includes a combination of multiple different diagnostic events. Specifically, for a vehicle component, diagnostic events of chips in the vehicle component can be combined, circuit-related diagnostic events in the vehicle component can be combined, and sensor diagnostic events in the vehicle component can be combined. For example, if the vehicle component is a controller, then diagnostic events of chips in the controller (chip short circuit diagnosis, controller chip open circuit diagnosis, and controller electrostatic breakdown) can be combined. Diagnostic events of sensors in the controller (speed sensor diagnosis, acceleration sensor diagnosis, and position sensor diagnosis, etc.) can be combined. Circuit-related diagnostic events in the controller (power system diagnosis, grounding diagnosis, and line integrity diagnosis, etc.) can be combined.

[0051] It is understood that the diagnostic combination methods shown above are only one possible method in actual application, and do not limit the diagnostic combination methods used in actual application. The specific diagnostic combination method can be determined according to the actual situation, and is not limited here.

[0052] In one example, it is determined whether there is fault information in the diagnostic results; if at least one diagnostic event in the diagnostic data has a diagnostic result that is set, it is determined that there is fault information in the diagnostic results; if all diagnostic results in the diagnostic data are not set, it is determined that there is no fault information in the diagnostic results.

[0053] For example, diagnostic events in the diagnostic data include controller chip short circuit diagnosis, controller chip open circuit diagnosis, and controller electrostatic discharge (ESD) diagnosis. If the diagnostic results for controller chip short circuit diagnosis, controller chip open circuit diagnosis, and controller ESD diagnosis are all in a non-set state, then it is determined that there is fault information in the diagnostic results; or, if the diagnostic results for controller chip short circuit diagnosis, controller chip open circuit diagnosis, and controller ESD diagnosis are all in a set state, then it is determined that there is no fault information in the diagnostic results.

[0054] The above technical solution determines whether fault information exists in the diagnostic results. If at least one diagnostic event in the diagnostic data has a diagnostic result that is set, it is determined that fault information exists in the diagnostic results. Compared with comparing each diagnostic result and determining that the target component has fault information in the diagnostic results when each diagnostic result has fault information, this application can improve the efficiency of determining the presence of fault information in the diagnostic results by judging multiple diagnostic results in the diagnostic data.

[0055] In another example, it is determined whether there is fault information in the diagnostic results, that is, whether there are abnormal results in the diagnostic results; if there is at least one diagnostic event in the diagnostic data corresponding to an abnormal result, it is determined that there is fault information in the diagnostic results; if all the diagnostic results in the diagnostic data are normal results, it is determined that there is no fault information in the diagnostic results.

[0056] For example, diagnostic events in the diagnostic data include controller chip short circuit diagnosis, controller chip open circuit diagnosis, and controller electrostatic discharge (ESD) diagnosis. If the diagnostic result for controller chip short circuit diagnosis is normal, the diagnostic result for controller chip open circuit diagnosis is normal, and the diagnostic result for controller ESD diagnosis is abnormal, then it is determined that there is fault information in the diagnostic results; or, if the diagnostic results for controller chip short circuit diagnosis, controller chip open circuit diagnosis, and controller ESD diagnosis are all normal, then it is determined that there is no fault information in the diagnostic results.

[0057] For example, if no fault information is found in the diagnostic results, a preset output relationship is obtained. This preset output relationship indicates the relationship between the diagnostic results of a preset component and the preset output. For instance, if no fault information is found in the diagnostic results of a preset component, the output "Target component diagnosis is normal" is displayed, or no prompt information is output, etc. Furthermore, if no fault information is found in the diagnostic results of a preset component, the output "Target component diagnosis is normal" can be displayed by outputting a diagnostic code, a prompt message, or both.

[0058] For example, if no fault information is found in the diagnostic results, the target diagnostic combination corresponding to the target component is obtained. Based on the diagnostic results and the target diagnostic combination, a diagnostic code for the target component is generated, and a prompt message is output. The diagnostic code is used to indicate that there is no fault in the target component, and the prompt message is used to prompt the user that the target component is diagnosed as normal.

[0059] For example, if fault information is found in the diagnostic results, a preset combination relationship is obtained. The preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component. Based on the target component and the preset combination relationship, the target diagnostic combination is determined.

[0060] For example, preset combination relationships include controller-to-controller diagnostic combinations, where each controller-to-controller diagnostic combination includes a combination of diagnostic events 1, 2, and 3 (or diagnostic event 2 or 3); sensor-to-sensor diagnostic combinations, where each sensor-to-sensor diagnostic combination includes a combination of diagnostic events 4, 5, and 6 (or diagnostic event 4, 5, or 6), and so on. It is understood that the above-described methods are only one possible approach in practice and do not limit the combination methods used in actual applications. Specific combination methods can be determined based on actual circumstances and are not limited here.

[0061] The above technical solution, if fault information is found in the diagnostic results, obtains the preset combination relationship, and determines the target diagnostic combination based on the target component and the preset combination relationship; since the preset combination relationship indicates the correspondence between the preset diagnostic combination and the vehicle component, the target diagnostic combination can be quickly determined through the target component, thereby improving the efficiency of determining the target diagnostic combination.

[0062] For example, the preset combination relationship can be determined using the characteristics of vehicle components, which facilitates fault merging based on the characteristics of vehicle components and improves the efficiency of fault detection. Specifically, the characteristics of vehicle components can be defined and merged by the manufacturer or developer based on the same diagnostic features of different diagnoses.

[0063] Furthermore, for vehicle components, diagnostic events related to chips, circuits, and sensors within the component can be combined. For example, if the vehicle component is a controller, diagnostic events related to chips (chip short circuit diagnosis, controller chip open circuit diagnosis, and controller electrostatic discharge) can be combined. Diagnostic events related to sensors (speed sensor diagnosis, acceleration sensor diagnosis, and position sensor diagnosis, etc.) can be combined. Circuit-related diagnostic events (power system diagnosis, grounding diagnosis, and line integrity diagnosis, etc.) can be combined.

[0064] For example, controller faults such as chip short circuit faults, open circuit faults, capacitor aging, and electrostatic discharge are all chip faults. When the controller has the above faults, it is necessary to repair or replace the controller directly. If the above diagnostic events are not combined, at least 4 DTCs (Diagnostic Trouble Codes) are required, including custom fault codes. Since their maintenance method is consistent, merging the above diagnostic events into 1 DTC is beneficial to reducing controller fault codes and facilitating fault management.

[0065] S330 generates fault codes for the target component based on the diagnostic results and the target diagnostic combination.

[0066] For example, given a diagnostic result and a target diagnostic combination, a fault code for the target component is determined based on the diagnostic result and the target diagnostic combination. Specifically, since the status bits corresponding to each diagnostic event in the diagnostic data include set and unset states, the logical relationship between different diagnostic events in the target diagnostic combination is determined, and a fault code is generated based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events.

[0067] For example, the target diagnostic combination for the target component includes diagnostic event 1, diagnostic event 2, and diagnostic event 3. The logical relationship between different diagnostic events in the target diagnostic combination is (diagnostic event 1 or diagnostic event 2 or diagnostic event 3). If the diagnostic result of diagnostic event 1 is set state 1, the diagnostic result of diagnostic event 2 is non-set state 0, and the diagnostic result of diagnostic event 3 is non-set state 0, then based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events, the corresponding code of bit 0 in the fault code is generated as 1.

[0068] The above technical solution determines the logical relationship between different diagnostic events in the target diagnostic combination and generates a fault code based on the status bit corresponding to each diagnostic event and the logical relationship between different diagnostic events. Since the status bit is either set or not set, the results of different diagnostic events are combined into a fault code by combining the status corresponding to each diagnostic event and the logical relationship between different diagnostic events. That is, a fault code can include the diagnostic results of multiple diagnostic events, thereby reducing the number of fault codes and facilitating fault code management.

[0069] It should be noted that the fault code generation method in this application can reduce the number of fault codes, facilitate fault code management, and thus improve user convenience.

[0070] Table 1 is a schematic table illustrating the generation of a fault code in this application.

[0071] For example, as shown in Table 1, the internationally used fault codes are those specified by the J2012DA protocol. However, since the number of fault codes with clearly defined fault codes in the protocol is relatively small compared to the actual diagnosis of vehicle components, in order for after-sales service personnel or users to directly obtain fault information, it is necessary to use dedicated after-sales diagnostic equipment to determine the meaning of each fault code, thereby reducing the convenience of vehicle fault management.

[0072] Table 1

[0073] Bit describe Is it necessary? mnemonic 0 Test failed M TF 1 Driving cycle test failed M TFTOC 2 Pending fault codes M PDTC 3 Confirm fault codes M CDTC 4 The test has not been completed since the last cleanup. M TNCSLC 5 Tests have failed since the last cleanup. U TFSLC 6 The current driving cycle test is not yet complete. M TNCTOC 7 Request warning indicator U WIR

[0074] For example, as shown in Table 1, fault codes are represented by 8 bits, each with a different definition. "M" indicates bits that the manufacturer must support, and "U" indicates bits that the manufacturer can choose to support. If the fault code generation method in the table above is followed, then for controller faults such as chip short circuit, open circuit, capacitor aging, and electrostatic discharge, corresponding fault codes are required. This would necessitate at least 4 DTCs. Given the large number of vehicle components, requiring multiple fault codes for a single component would complicate subsequent fault management and vehicle maintenance.

[0075] It should be noted that TF (Test Failed) indicates that the current test has failed, signifying a current diagnostic failure; TFTOC (Test Failed This Operation Cycle) indicates a test failure within the current driving cycle; PDTC (Pending DTC) indicates a pending fault code; CDTC (Confirmed DTC) indicates a confirmed fault code; TNCSLC (Test Not Completed Since Last Clear) indicates that the test has not been completed since the last clear; TFSLC (Test Failed Since Last Clear) indicates that the test has failed since the last clear; TNCTOC (Test Not Completed This Operation Cycle) indicates that the test has not been completed within the current driving cycle; and WIR (Warning Indicator Requested (MIL)).

[0076] Table 2 is a schematic table illustrating the generation of another type of fault code in this application.

[0077] For example, as shown in Table 2, by combining different diagnostic events of vehicle components, the number of fault codes can be reduced, thereby improving the ease of managing fault codes.

[0078] Table 2

[0079]

[0080] It should be noted that each bit is determined based on the diagnostic results and diagnostic combinations, and all bits are combined to generate the fault code for the vehicle component. The status bit of each bit is determined as follows:

[0081] The status bit of Bit0 is linked by a logical "Or" according to different diagnostic events in the diagnostic combination. When any single diagnostic event is in the set state (set state 1 indicates that a fault is detected at present), the diagnostic combination Bit0 will be in the set state 1; when all the individual diagnostic events in the diagnostic combination are in the non-set state (non-set state 0 indicates that no fault is detected at present), the diagnostic combination Bit0 is in the non-set state 0.

[0082] The status bit of Bit1 is linked by a logical "Or" according to different diagnostic events in the diagnostic combination. When any single diagnostic event is detected and set before the end of the current driving cycle, the diagnostic combination Bit1 will be in the set state 1. When the individual diagnostic events in the diagnostic combination are linked by a logical "Or", and all individual diagnostic events are detected and no fault is detected before the end of the current operation cycle, the diagnostic combination Bit1 will be in the non-set state 0.

[0083] The state of Bi2 is determined by the diagnostic combination. If any single diagnostic event causes diagnostic combination Bit1 to be set (i.e., diagnostic combination Bit1 is in the set state) before the end of the current driving cycle, then diagnostic combination Bit2 will be in the set state 1; if no diagnostic event causes diagnostic combination Bit1 to be set before the end of the current driving cycle, then diagnostic combination Bit2 will be in the non-set state 0.

[0084] The status of Bit3 is determined by the diagnostic combination. If any single diagnostic event causes Bit2 to be flagged before the end of the current driving cycle, then Bit3 will be in the set state (1). If no diagnostic event causes Bit2 to be flagged before the end of the current driving cycle, then Bit3 will be in the unset state (0). It should be noted that the number of driving cycles for fault confirmation in Table 2 is 1, meaning that pending fault codes and confirmed fault codes change simultaneously. The number of driving cycles can be determined based on actual circumstances and is not specifically limited here.

[0085] The status of Bit4 is determined by the diagnostic combination. If any single diagnostic event has not been detected since the last clearing and is in the set state, then Bit4 will be in the set state (1); if all single diagnostic events have been detected since the last clearing, then Bit4 will be in the non-set state (0).

[0086] The status of Bit5 is determined by the diagnostic combination. If any single diagnostic event since the last clearing of the diagnostic combination diagnoses a fault and is in the set state, then Bit5 will be set to 1; if no single diagnostic event since the last clearing of the diagnostic combination diagnoses a fault, then Bit5 will be set to 0, i.e., Bit5 will be in the unset state.

[0087] The status of Bit6 is determined by the diagnostic combination. If any single diagnostic event is not detected before the end of the current driving cycle, Bit6 will be set to 1, meaning Bit6 will be in the set state. If all single diagnostic events are detected before the end of the current driving cycle, Bit6 will be set to 0, meaning Bit6 will be in the unset state.

[0088] Bit7's status is determined by whether a single diagnostic event in the diagnostic combination sends a light-on request. If so, Bit7 will be set to 1, meaning it will be in the set state. If no light-on request is sent for any single diagnostic event in the diagnostic combination, Bit7 will be set to 0, meaning it will be in the unset state.

[0089] It is understandable that by generating fault codes for target components based on diagnostic results and target diagnostic combinations, the number of fault codes can be reduced compared to each diagnostic event in the target component having a corresponding fault code. This reduces the number of fault codes without affecting vehicle fault diagnosis and improves the convenience of fault code management.

[0090] For example, when a fault code for a target component is generated, the target position of the target component in the vehicle is determined based on a preset positional relationship with the target component. The preset positional relationship indicates the relationship between the preset component and the preset position. Further, the target position of the target component is displayed, and a fault indication message is output to indicate that the target component has a fault.

[0091] For example, if the target component is an engine, the target location of the engine in the vehicle is determined and displayed in the vehicle virtual model. The target location can be highlighted and a fault message can be output to indicate that the target component is faulty, so that the user can determine the location of the faulty target component.

[0092] The above technical solution determines the target location of the target component in the vehicle, displays the target location of the target component, and outputs fault prompt information. Since the fault prompt information indicates that the target component is faulty, by displaying the target location of the target component and outputting the fault prompt information, the user can determine the location of the faulty target component, thereby handling the fault in the vehicle and improving driving safety.

[0093] For example, if a diagnostic command is detected in the vehicle within a preset time period, a diagnostic test is performed on the target component to obtain updated diagnostic data for the target component. The updated diagnostic data includes updated diagnostic results of at least one diagnostic event performed on the target component. If fault information is present in the updated diagnostic results, a target diagnostic combination corresponding to the target component is obtained. The target diagnostic combination indicates a combination of different diagnostic events for the target component. Based on the updated diagnostic results and the target diagnostic combination, a fault code for the target component is generated. It should be noted that the method for generating the fault code for the target component can be based on the method in the aforementioned disclosed embodiments, and is not specifically limited here.

[0094] Furthermore, the number of times a fault code for a target component is generated within a preset time period is determined, and based on this number, a prompt message is output to guide the elimination of the target component's fault. It can be understood that the number of times fault codes for different vehicle components are generated within the preset time period is determined, and corresponding prompt messages are output based on the number of times fault codes for non-universal vehicle components are generated.

[0095] Optionally, the preset time period can be one driving cycle, two driving cycles, etc., or the preset time period can be 3 hours, 5 hours, etc. The preset time period can be determined according to the actual situation, and no specific limitation is made here.

[0096] The above technical solution determines the number of times a fault code of a target component is generated within a preset time period and outputs a prompt message based on the number of generation. Since the prompt message is used to eliminate the fault of the target component, by outputting the prompt message, the user can be prompted to eliminate the fault of the target component as soon as possible, thereby improving driving safety.

[0097] For example, the output prompt information can be determined based on the number of times the fault code is generated. Specifically, it is determined whether the number of times the fault code of the target component is generated is greater than a preset number of generation times, and the corresponding output prompt information is determined based on the comparison result between the number of generation times and the preset number of generation times.

[0098] Optionally, the preset number of generation times is 1 time, 2 times, etc. The preset number of generation times can be determined according to the actual situation, and no specific limit is made here.

[0099] In one example, if the number of generation attempts is less than or equal to a preset number of generation attempts, a first prompt message is output. This first prompt message prompts the user to execute a target event, which is used to eliminate the fault of the target component. Specifically, if the number of generation attempts is less than or equal to a preset number of generation attempts, a target event is determined based on the relationship between the target component and preset events. The preset event relationship represents the correspondence between preset events and preset components. Based on the target event, the first prompt message is output.

[0100] For example, if a fault is detected during vehicle component fault diagnosis, the user can eliminate the fault by performing a corresponding operation. If the target component is an electronic control unit (ECU), and the ECU determines that the corresponding target event is vehicle charging, then the first prompt message will be "Please charge the vehicle as soon as possible to eliminate the ECU fault." It is understandable that if the EV's ECU malfunctions, it may be due to insufficient vehicle battery power. Charging the vehicle can avoid false alarms caused by insufficient battery power, thereby improving user convenience.

[0101] It is understood that the preset event relationships shown above are only one possible preset event relationship in actual application, and do not limit the preset event relationships used in actual application. The specific preset event relationships can be determined according to the actual situation, and are not limited here.

[0102] The above technical solution, if the number of generation times is less than or equal to the preset number of generation times, determines the target event based on the relationship between the target component and the preset event, and outputs the first prompt information based on the target event; since the preset event relationship is used to represent the correspondence between the preset event and the preset component, the corresponding first prompt information is output based on the target event, thereby prompting the user to execute the first prompt information to eliminate the fault in the target component, and to avoid vehicle repair caused by false alarms as much as possible, which can improve the convenience of user use.

[0103] In another example, if the number of generation attempts exceeds a preset limit, a second prompt message is output, suggesting that the target component be inspected. For instance, if the target component's fault code is generated more than once, the second prompt message would be: "Hello, due to a fault in the target component of the vehicle, please have it inspected promptly to ensure driving safety." Alternatively, the second prompt message could be: "Hello, please go to a 4S shop for vehicle repair as soon as possible."

[0104] For example, the system determines the target location of the target component within the vehicle, displays the target location, outputs a fault warning message, and outputs a first warning message to prompt the user to perform a target event to eliminate the fault in the target component. If a fault code for the target component is generated again within a preset time period, a second warning message is output to prompt the user to inspect and repair the target component.

[0105] The above technical solution outputs a first prompt if the number of generation attempts is less than or equal to a preset number of generation attempts. Since the first prompt is used to prompt the user to perform a target event, which is used to eliminate the fault of the target component, prompting the user to perform the target event through the first prompt can eliminate vehicle faults caused by driving habits, thereby improving user convenience. If the number of generation attempts exceeds the preset number of generation attempts, a second prompt is output. Since the second prompt is used to prompt the user to inspect the target component, outputting the second prompt can promptly prompt the user to inspect the vehicle, thereby improving driving safety.

[0106] It is understandable that, since the first prompt message prompts the user to execute the target event, which is used to eliminate the fault of the target component, if the user executes the target event according to the first prompt message and can eliminate the fault of the target component; or, if the user repairs the target component according to the second prompt message and eliminates the fault of the target component, then the diagnostic command in the vehicle is detected again, the target component corresponding to the diagnostic command is diagnosed, and the latest diagnostic data of the target component is obtained. The latest diagnostic data does not contain fault information.

[0107] Figure 4 This is a schematic diagram of a fault repair scenario provided in an embodiment of this application.

[0108] For example, such as Figure 4 As shown, if a diagnostic command is detected in the vehicle during driving cycle 1, the controller corresponding to the diagnostic command is diagnosed, and the diagnostic data of the controller is obtained as the data corresponding to diagnostic event 3. If the diagnostic data is the diagnostic result corresponding to diagnostic event 3: controller electrostatic breakdown fault, and the target diagnostic combination is a combination of different diagnostic events of the controller (diagnostic event 1, diagnostic event 2 and diagnostic event 3), then the fault code 001011111 is generated according to the target diagnostic combination and the diagnostic result, and a prompt message is output. The prompt message is used to indicate that there is a fault in the controller so that the user can repair the fault in the controller.

[0109] Furthermore, if the fault in the controller is repaired, and a diagnostic command is detected in the vehicle during driving cycle 2, the controller corresponding to the diagnostic command is diagnosed. The diagnostic data of the controller is obtained as the data corresponding to diagnostic event 1, diagnostic event 2, and diagnostic event 3. And there is no fault information in the data corresponding to diagnostic event 1, diagnostic event 2, and diagnostic event 3. That is, diagnostic events 1, 2, and 3 have all been completed and there is no fault information. Based on the diagnostic results and the corresponding diagnostic combination of the controller, the diagnostic code of bit 7-0 is generated as 00101000, and a prompt message is output. The prompt message is used to indicate that the controller currently detects no fault, or the controller has a historical fault - P0A1C.

[0110] Understandably, during the fault repair process (Operation Cycle 2), diagnostic events 1, 2, and 3 are all detected but no fault is triggered. At the end of Operation Cycle 2, the combined diagnostic event's diagnostic code is 00101000, indicating no current fault exists. By combining diagnostic events, multiple diagnostic events can be merged, reducing the number of fault codes and improving the convenience of vehicle fault management.

[0111] In the above technical solution, if fault information is found in the diagnostic results, the target diagnostic combination corresponding to the target component is obtained, and a fault code for the target component is generated based on the diagnostic results and the target diagnostic combination. In this application, the target diagnostic combination indicates a combination of different diagnostic events of the target component. By combining the different diagnostic events of the target component through the diagnostic results and the target diagnostic combination, a fault code is generated. Since the fault code is a combination of multiple diagnostic events, compared with each diagnostic event corresponding to one fault code, the number of fault codes can be reduced, thereby improving the convenience of vehicle fault management.

[0112] Figure 5 This is a schematic flowchart illustrating another method for generating fault codes provided in this application embodiment.

[0113] For example, Figure 5 The method shown can be executed by the vehicle controller or chip in the vehicle.

[0114] For example, such as Figure 5 As shown, the method 500 includes the following procedures:

[0115] S501: If a diagnostic command is detected in the vehicle, the target component corresponding to the diagnostic command is diagnosed to obtain the diagnostic data of the target component.

[0116] For example, a diagnostic command may include an identifier for the target component. For instance, a diagnostic command such as "Diagnose the vehicle controller" would identify the controller as the target component.

[0117] It should be noted that the diagnostic data includes the diagnostic results of at least one diagnostic event performed on the target component. Since diagnosing the target component may involve the diagnostic results of at least one diagnostic event, the diagnostic results of at least one diagnostic event may all contain non-fault information or all contain fault information; or, the diagnostic results of multiple diagnostic events may contain both fault and non-fault information.

[0118] S502, If the diagnostic results in the diagnostic data contain fault information, obtain the preset combination relationship.

[0119] For example, if the diagnostic results in the diagnostic data contain fault information, a preset combination relationship is obtained. The preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component.

[0120] For example, the preset combination relationship can be determined using the characteristics of vehicle components, which facilitates fault merging based on the characteristics of vehicle components and improves the efficiency of fault detection. Specifically, the characteristics of vehicle components can be defined and merged by the manufacturer or developers based on the same diagnostic features of different diagnoses. For example, in controller faults, chip short circuit faults, open circuit faults, capacitor aging, and electrostatic breakdown are all chip faults. When the controller has the above faults, it is necessary to repair or replace the controller directly. If the above diagnostic events are not merged, at least 4 DTCs are required. However, by merging the above diagnostic events into 1 DTC, the number of controller fault codes is reduced, which facilitates fault management.

[0121] S503, based on the target component and the preset combination relationship, determine the target diagnostic combination.

[0122] For example, a preset combination relationship is obtained, which is used to indicate the correspondence between a preset diagnostic combination and a vehicle component. Based on the target component and the preset combination relationship, a target diagnostic combination is determined.

[0123] For example, preset combination relationships include controller-to-controller diagnostic combinations, where each controller-to-controller diagnostic combination includes a combination of diagnostic events 1, 2, and 3 (or diagnostic event 2 or 3); sensor-to-sensor diagnostic combinations, where each sensor-to-sensor diagnostic combination includes a combination of diagnostic events 4, 5, and 6 (or diagnostic event 4, 5, or 6), and so on. It is understood that the above-described methods are only one possible approach in practice and do not limit the combination methods used in actual applications. Specific combination methods can be determined based on actual circumstances and are not limited here.

[0124] S504, determine the logical relationship between different diagnostic events in the target diagnostic combination.

[0125] For example, the logical relationship between different diagnostic events in a target diagnostic combination can be that the different diagnostic events are linked by "and" or by "or".

[0126] For example, the target diagnostic combination for a target component includes diagnostic event 1, diagnostic event 2, and diagnostic event 3. The logical relationship between different diagnostic events in the target diagnostic combination is (diagnostic event 1 or diagnostic event 2 or diagnostic event 3).

[0127] S505 generates fault codes and outputs fault prompt information based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events.

[0128] For example, since the status bits corresponding to each diagnostic event in the diagnostic data include set and unset states, the logical relationship between different diagnostic events in the target diagnostic combination is determined, and a fault code is generated based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events.

[0129] For example, the target diagnostic combination for the target component includes diagnostic event 1, diagnostic event 2, and diagnostic event 3. The logical relationship between different diagnostic events in the target diagnostic combination is (diagnostic event 1 or diagnostic event 2 or diagnostic event 3). If the diagnostic result of diagnostic event 1 is set state 1, the diagnostic result of diagnostic event 2 is non-set state 0, and the diagnostic result of diagnostic event 3 is non-set state 0, then based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events, the corresponding code of bit 0 in the fault code is generated as 1.

[0130] For example, when a fault code for a target component is generated, the target position of the target component in the vehicle is determined based on a preset positional relationship with the target component. The preset positional relationship indicates the relationship between the preset component and the preset position. Further, the target position of the target component is displayed, and a fault indication message is output to indicate that the target component has a fault.

[0131] For example, if the target component is an engine, the target location of the engine in the vehicle is determined and displayed in the vehicle virtual model. The target location can be highlighted and a fault message can be output to indicate that the target component is faulty, so that the user can determine the location of the faulty target component.

[0132] S506, determine the number of times a fault code is generated for a target component within a preset time period.

[0133] For example, if a diagnostic command is detected in the vehicle within a preset time period, a diagnostic test is performed on the target component to obtain updated diagnostic data for the target component. The updated diagnostic data includes updated diagnostic results of at least one diagnostic event performed on the target component. If fault information is present in the updated diagnostic results, a target diagnostic combination corresponding to the target component is obtained. The target diagnostic combination indicates a combination of different diagnostic events for the target component. Based on the updated diagnostic results and the target diagnostic combination, a fault code for the target component is generated. Further, the number of times a fault code for the target component is generated within the preset time period is determined.

[0134] Optionally, the preset time period can be one driving cycle, two driving cycles, etc., or the preset time period can be 3 hours, 5 hours, etc. The preset time period can be determined according to the actual situation, and no specific limitation is made here.

[0135] S507, Is the number of generation times greater than the preset number of generation times? If not, then execute S508; if yes, then execute S510.

[0136] For example, it is determined whether the number of times the fault code of the target component is generated is greater than the preset number of times, and the corresponding output prompt information is determined based on the comparison result between the number of times generated and the preset number of times.

[0137] Optionally, the preset number of generation times is 1 time, 2 times, etc. The preset number of generation times can be determined according to the actual situation, and no specific limit is made here.

[0138] S508, determine the target event based on the relationship between the target component and the preset event.

[0139] For example, if the number of generation times is less than or equal to the preset number of generation times, the target event is determined based on the relationship between the target component and the preset event. The preset event relationship is used to represent the correspondence between the preset event and the preset component.

[0140] For example, if a fault is detected during the fault diagnosis of a vehicle component, the fault can be eliminated by the user performing the corresponding operation. It is understood that if the electronic control unit of an electric vehicle malfunctions, it may be due to insufficient vehicle battery power. Charging the vehicle can avoid false alarms caused by insufficient vehicle battery power, thereby improving user convenience.

[0141] S509, output the first prompt message.

[0142] For example, based on the target event, a first prompt message is output. For instance, if the target component is an electronic control unit (ECU), and the ECU determines the corresponding target event as vehicle charging, then the first prompt message is "Please charge the vehicle as soon as possible to eliminate the ECU malfunction." It is understandable that if the vehicle's ECU malfunctions, it may be due to insufficient battery power. Charging the vehicle can prevent false alarms caused by insufficient battery power, thereby improving user convenience.

[0143] S510 outputs the second prompt message.

[0144] For example, if the number of times a fault code is generated exceeds a preset number, a second prompt message is output, which prompts the target component to be inspected. For instance, if the number of times a fault code for the target component is generated is greater than 1, the second prompt message is output as "Hello, due to a fault in the target component of the vehicle, please have it inspected in time to ensure driving safety."

[0145] For example, the system determines the target location of the target component within the vehicle, displays the target location, outputs a fault warning message, and outputs a first warning message to prompt the user to perform a target event to eliminate the fault in the target component. If a fault code for the target component is generated again within a preset time period, a second warning message is output to prompt the user to inspect and repair the target component.

[0146] The above technical solution, if fault information is found in the diagnostic results, obtains the target diagnostic combination corresponding to the target component, and generates a fault code for the target component based on the diagnostic results and the target diagnostic combination. In this application, the target diagnostic combination indicates a combination of different diagnostic events of the target component. By combining the different diagnostic events of the target component through the diagnostic results and the target diagnostic combination, a fault code is generated. Since the fault code is a combination of multiple diagnostic events, compared to each diagnostic event corresponding to one fault code, the number of fault codes can be reduced, thereby improving the convenience of vehicle fault management. Furthermore, by outputting prompt information, the user is prompted to eliminate the fault of the target component. On the one hand, this can eliminate vehicle faults caused by driving habits, thereby improving user convenience; on the other hand, it can prompt the target component to be inspected, thereby improving driving safety.

[0147] It should be understood that the above examples are provided to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the above examples, and such modifications or changes also fall within the scope of the embodiments of this application.

[0148] The above text combined Figures 1 to 5 The method for generating fault codes provided in the embodiments of this application is described in detail below; the following will be combined with Figure 6 and Figure 7 The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus in the embodiments of this application can perform the various methods described in the foregoing embodiments of this application, that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0149] Figure 6 This is a schematic diagram of a fault code generation device provided in an embodiment of this application.

[0150] For example, such as Figure 6 As shown, the fault code generation device 600 includes:

[0151] Diagnostic module 610: If a diagnostic command is detected in the vehicle, it is used to diagnose the target component corresponding to the diagnostic command and obtain diagnostic data of the target component; wherein, the diagnostic data includes the diagnostic results of at least one diagnostic event of the target component.

[0152] Acquisition module 620: used to acquire the target diagnostic combination corresponding to the target component if fault information exists in the diagnostic results; wherein, the target diagnostic combination is used to indicate the combination of different diagnostic events of the target component;

[0153] Generation module 630: Used to generate fault codes for target components based on diagnostic results and target diagnostic combinations.

[0154] Optionally, as an embodiment, before fault information is found in the diagnostic results, the acquisition module 620 is specifically used for:

[0155] Determine whether there is fault information in the diagnostic results; if there is at least one diagnostic event in the diagnostic data whose corresponding diagnostic result is set, determine that there is fault information in the diagnostic results.

[0156] Optionally, as an embodiment, the generation module 630 is specifically used for:

[0157] Determine the logical relationship between different diagnostic events in the target diagnostic combination; generate fault codes based on the status bits corresponding to each diagnostic event and the logical relationship between different diagnostic events; wherein, the status bits are either set or unset.

[0158] Optionally, as an embodiment, the acquisition module 620 is specifically used for:

[0159] If fault information is found in the diagnostic results, a preset combination relationship is obtained; wherein, the preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component; based on the target component and the preset combination relationship, the target diagnostic combination is determined.

[0160] Optionally, as an embodiment, the fault code generation device 600 further includes a display module, which is specifically used for:

[0161] Determine the target location of the target component within the vehicle; display the target location of the target component and output a fault indication message; wherein the fault indication message is used to indicate that the target component has a fault.

[0162] Optionally, as an embodiment, the fault code generation device 600 further includes an output module, which is specifically used for:

[0163] If a diagnostic command is detected in the vehicle within a preset time period, the target component is diagnosed to obtain updated diagnostic data for the target component. The updated diagnostic data includes the updated diagnostic results of at least one diagnostic event performed on the target component. If fault information is present in the updated diagnostic results, a fault code for the target component is generated. The number of times the fault code is generated is determined. Based on the number of generation times, a prompt message is output.

[0164] Optionally, as an example, the output module is specifically used for:

[0165] If the number of generation attempts is less than or equal to the preset number of generation attempts, a first prompt message is output; wherein, the first prompt message is used to prompt the user to execute the target event, and the target event is used to eliminate the fault of the target component; if the number of generation attempts is greater than the preset number of generation attempts, a second prompt message is output; wherein, the second prompt message is used to prompt the target component to be inspected.

[0166] Optionally, as an example, the output module is specifically used for:

[0167] If the number of generation attempts is less than or equal to the preset number of generation attempts, the target event is determined based on the relationship between the target component and the preset event; wherein, the preset event relationship is used to represent the correspondence between the preset event and the preset component; based on the target event, the first prompt message is output.

[0168] It should be noted that the fault code generation device 600 described above is embodied in the form of a functional unit. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0169] For example, a "module" can be a software program, a hardware circuit, or a combination of both that implements the above functions. The hardware circuit may include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components that support the described functions.

[0170] Therefore, the units of the various examples described in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0171] Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application.

[0172] For example, such as Figure 7 As shown, the vehicle 700 includes a memory 710 and a processor 720, wherein the memory 710 stores executable program code 730, and the processor 720 is used to call and execute the executable program code 730 to perform a fault code generation method.

[0173] For example, the memory 710 can be used to store related programs of the fault code generation method provided in the embodiments of this application; the processor 720 can call the related programs of the fault code generation method stored in the memory 710 to execute the fault code generation method of the embodiments of this application; for example, if a diagnostic command is detected in the vehicle, the target component corresponding to the diagnostic command is diagnosed to obtain diagnostic data of the target component; wherein, the diagnostic data includes the diagnostic results of at least one diagnostic event of the target component; if there is fault information in the diagnostic results, the target diagnostic combination corresponding to the target component is obtained; wherein, the target diagnostic combination is used to indicate the combination of different diagnostic events of the target component; based on the diagnostic results and the target diagnostic combination, a fault code of the target component is generated.

[0174] This embodiment can divide the device into functional modules based on the above method example. For example, each module can correspond to a separate function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0175] When each functional module is divided according to its corresponding function, the device may also include a diagnostic module, an acquisition module, and a generation module. It should be noted that all relevant content regarding the steps involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0176] It should be understood that the apparatus provided in this embodiment is used to execute the above-described method for generating fault codes, and therefore can achieve the same effect as the above-described implementation method.

[0177] When using an integrated unit, the device may include a processing module and a storage module. When the device is applied to a vehicle, the processing module can be used to control and manage the vehicle's movements. The storage module can be used to support the vehicle in executing relevant program code.

[0178] The processing module may be a processor or a controller, which can implement or execute various exemplary logic blocks, modules, and circuits shown in conjunction with the disclosure of this application. The processor may also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc., and the storage module may be a memory.

[0179] In addition, the apparatus provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a fault code generation method provided in the above embodiments.

[0180] This application also provides a computer-readable storage medium storing computer program code, which, when run on a computer, causes the computer to execute the aforementioned method steps to implement a fault code generation method provided in the above embodiments. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, Digital Video Discs (DVDs), Compact Disc Read-Only Memory (CD-ROMs), microdrives, and magneto-optical disks, read-only memory (ROMs), random access memory (RAMs), erasable programmable read-only memory (EPROMs), electrically erasable programmable read-only memory (EEPROMs), dynamic random access memory (DRAMs), video random access memory (VRAMs), flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and / or data.

[0181] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement a fault code generation method provided in the above embodiments.

[0182] The vehicle, computer-readable storage medium, computer program product or chip provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0183] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0184] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0185] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for generating fault codes, characterized in that, The method includes: If a diagnostic command is detected in the vehicle, the target component corresponding to the diagnostic command is diagnosed to obtain diagnostic data of the target component; wherein, the diagnostic data includes the diagnostic results of at least one diagnostic event performed on the target component; If fault information is found in the diagnostic results, the target diagnostic combination corresponding to the target component is obtained; wherein, the target diagnostic combination is used to indicate a combination of different diagnostic events of the target component; Based on the diagnostic results and the target diagnostic combination, a fault code for the target component is generated; If fault information is found in the diagnostic results, obtaining the target diagnostic combination corresponding to the target component includes: If the fault information is present in the diagnostic results, a preset combination relationship is obtained. The preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component. The preset diagnostic combination is obtained by merging the same diagnostic characteristics of different diagnostic events of the vehicle component. Based on the target component and the preset combination relationship, the target diagnostic combination is determined.

2. The method according to claim 1, characterized in that, Before the step of "if fault information exists in the diagnostic results", the method further includes: Determine whether the fault information is present in the diagnostic results; If the diagnostic results contain fault information, it includes: If at least one diagnostic event in the diagnostic data has a diagnostic result that is set, it is determined that the fault information exists in the diagnostic result.

3. The method according to claim 1, characterized in that, The step of generating a fault code for the target component based on the diagnostic results and the target diagnostic combination includes: Determine the logical relationships between different diagnostic events in the target diagnostic combination; The fault code is generated based on the status bits corresponding to each diagnostic event and the logical relationship between the different diagnostic events; The status bit can be either set or not set.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Determine the target location of the target component in the vehicle; The target location of the target component is displayed, and a fault prompt message is output; wherein the fault prompt message is used to indicate that the target component has a fault.

5. The method according to claim 4, characterized in that, The method further includes: If the diagnostic command is detected in the vehicle within a preset time period, the target component is diagnosed to obtain updated diagnostic data for the target component; wherein, the updated diagnostic data includes updated diagnostic results of executing at least one diagnostic event of the target component; If the fault information is present in the updated diagnostic results, the fault code of the target component is generated; Determine the number of times the fault code was generated; Based on the number of times the message is generated, a prompt message is output.

6. The method according to claim 5, characterized in that, The step of outputting prompt information based on the number of generation times includes: If the number of generation attempts is less than or equal to the preset number of generation attempts, a first prompt message is output; wherein, the first prompt message is used to prompt the user to perform a target event, and the target event is used to eliminate the fault of the target component; If the number of generation attempts exceeds the preset number of generation attempts, a second prompt message is output; wherein, the second prompt message is used to prompt the target component to be inspected.

7. The method according to claim 6, characterized in that, If the number of generation attempts is less than or equal to the preset number of generation attempts, a first prompt message is output, including: If the number of generation times is less than or equal to the preset number of generation times, a target event is determined based on the relationship between the target component and the preset event; wherein, the preset event relationship is used to represent the correspondence between the preset event and the preset component; Based on the target event, the first prompt message is output.

8. A fault code generation device, characterized in that, The device includes: A diagnostic module is configured to, if a diagnostic command is detected in the vehicle, diagnose the target component corresponding to the diagnostic command and obtain diagnostic data of the target component; wherein, the diagnostic data includes diagnostic results of at least one diagnostic event performed on the target component; The acquisition module is used to acquire the target diagnostic combination corresponding to the target component if fault information is found in the diagnostic results; wherein the target diagnostic combination is used to indicate a combination of different diagnostic events of the target component; A generation module is used to generate a fault code for the target component based on the diagnostic results and the target diagnostic combination. The acquisition module is specifically used to acquire a preset combination relationship if the fault information exists in the diagnostic results. The preset combination relationship is used to indicate the correspondence between the preset diagnostic combination and the vehicle component. The preset diagnostic combination is obtained by merging the same diagnostic characteristics of different diagnostic events of the vehicle component. Based on the target component and the preset combination relationship, the target diagnostic combination is determined.

9. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor is configured to call and run the executable program code from the memory, causing the vehicle to perform the fault code generation method as described in any one of claims 1 to 7.

Images