Fault code management method, device, equipment and readable storage medium

Abstract

The present application relates to a fault code management method, apparatus, device and readable storage medium, and relates to the field of automobile controller fault technology, including obtaining fault code information corresponding to each controller, wherein the fault code information includes the source address of the controller, the electronic control system number and the fault code number; generating a corresponding controller identification code based on the fault code information of each controller, wherein multiple controller identification codes form an identification code list; and managing the fault codes corresponding to each controller based on the identification code list. The present application generates an identification code that can uniquely identify each controller through the source address, the electronic control system number and the fault code number of the controller, and then uses the mapping relationship between the identification code and the controller to ensure that the controller and its corresponding fault code have a unique correspondence, so as to avoid the problem of one fault code corresponding to different controllers, thereby realizing effective management of the fault code.

Description

Technical Field

[0001] The present application relates to the technical field of automobile controller failure, and in particular to a fault code management method, apparatus, device and readable storage medium. Background Art

[0002] With the rapid development of the economy and the continuous improvement of people's living standards, cars have gradually entered thousands of households and become an increasingly indispensable means of transportation in life, greatly facilitating people's daily travel activities. Among them, commercial trucks as a means of production have also experienced rapid development. With the development of intelligent electronic control technology, the application of electronic controllers and control systems in commercial trucks has also increased. As a result, commercial trucks are no longer satisfied with mechanical logistics transportation and are beginning to pay more attention to intelligent vehicle management and control.

[0003] In related technologies, the vehicle's self-diagnosis and reporting are often performed through the OBD (OnBoard Diagnostics) system, and the OBD system will provide users with multiple series of standardized codes (such as fault codes). The fault codes can help users identify and remedy vehicle faults. However, due to the large number and complexity of electronic controllers and control systems on commercial trucks, and the fact that there are often several controllers from different manufacturers for the same configuration, there are problems such as one fault code corresponding to different controllers. In the fault diagnosis process, it is necessary to accurately distinguish between controllers from different manufacturers and with different functions in order to accurately diagnose vehicle faults. Therefore, how to achieve effective management of fault codes is an issue that needs to be solved urgently. Summary of the Invention

[0004] The present application provides a fault code management method, apparatus, device and readable storage medium to solve the problem that fault codes cannot be effectively managed in the related art.

[0005] In a first aspect, a fault code management method is provided, comprising the following steps:

[0006] Obtaining fault code information corresponding to each controller, wherein the fault code information includes the source address of the controller, the electronic control system number, and the fault code number;

[0007] Generate a corresponding controller identification code based on the fault code information of each controller, and form an identification code list with multiple controller identification codes;

[0008] The fault codes corresponding to the respective controllers are managed based on the identification code list.

[0009] In some embodiments, before the step of obtaining the fault code information corresponding to each controller, the method further includes:

[0010] The suspicious parameter number and fault mode flag of each controller are encoded to obtain the corresponding fault code number.

[0011] In some embodiments, obtaining fault code information corresponding to each controller includes:

[0012] Obtain fault code information corresponding to each controller sent by the supplier and / or OEM.

[0013] In some embodiments, after the step of managing the fault codes corresponding to the respective controllers based on the identification code list, the method further includes:

[0014] Receive a fault code message sent by the application end, wherein the fault code message includes fault code information of the fault to be detected;

[0015] Filtering the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message;

[0016] The first fault code corresponding to the first controller identification code is sent to the application end, so that the application end can perform vehicle fault diagnosis based on the first fault code.

[0017] In some embodiments, after the step of the application end performing vehicle fault diagnosis based on the first fault code, the method further includes:

[0018] Obtaining a vehicle fault diagnosis result, and detecting whether the vehicle fault diagnosis result indicates a fault exists;

[0019] If a fault occurs, updating the error statistics field corresponding to the first controller identification code in the identification code list;

[0020] If there is no fault, the step of obtaining the vehicle fault diagnosis result is performed.

[0021] In some embodiments, the identification code list includes fault level information of the fault code.

[0022] In some embodiments, after the step of selecting the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message, the method further includes:

[0023] The fault level of the first fault code corresponding to the first controller identification code is sent to the application end, so that the application end determines a maintenance strategy for the vehicle based on the fault level of the first fault code.

[0024] In a second aspect, a fault code management device is provided, comprising:

[0025] An acquisition unit, configured to acquire fault code information corresponding to each controller, wherein the fault code information includes a source address of the controller, an electronic control system number, and a fault code number;

[0026] a mapping unit, configured to generate a corresponding controller identification code based on the fault code information of each controller, wherein the plurality of controller identification codes form an identification code list;

[0027] A management unit is used to manage the fault codes corresponding to each controller based on the identification code list.

[0028] In a third aspect, a fault code management device is provided, comprising: a memory and a processor, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the aforementioned fault code management method.

[0029] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer storage medium stores a computer program, and when the computer program is executed by a processor, the aforementioned fault code management method is implemented.

[0030] The beneficial effects brought about by the technical solution provided by this application include: effective management of fault codes.

[0031] The present application provides a fault code management method, apparatus, device and readable storage medium, including obtaining fault code information corresponding to each controller, wherein the fault code information includes the source address of the controller, the electronic control system number and the fault code number; generating a corresponding controller identification code based on the fault code information of each controller, wherein multiple controller identification codes form an identification code list; and managing the fault codes corresponding to each controller based on the identification code list. The present application generates an identification code that can uniquely identify the controller for each controller through the source address, the electronic control system number and the fault code number of the controller, and then uses the mapping relationship between the identification code and the controller to ensure that the controller and its corresponding fault code have a unique correspondence, so as to avoid the problem of one fault code corresponding to different controllers, thereby realizing effective management of the fault code. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0033] Figure 1 A flowchart of a fault code management method provided in an embodiment of the present application;

[0034] Figure 2 A schematic diagram of the structure of a fault code management device provided in an embodiment of the present application;

[0035] Figure 3 A schematic diagram of the structure of a fault code management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0037] The embodiments of the present application provide a fault code management method, apparatus, device and readable storage medium, which can solve the problem in related technologies that effective fault code management cannot be effectively implemented.

[0038] Figure 1 A fault code management method provided in an embodiment of the present application includes the following steps:

[0039] Step S10: Obtaining fault code information corresponding to each controller, wherein the fault code information includes the source address of the controller, the electronic control system number, and the fault code number;

[0040] Furthermore, in the embodiment of the present application, before the step of obtaining the fault code information corresponding to each controller, the following steps are also included:

[0041] The suspicious parameter number and fault mode flag of each controller are encoded to obtain the corresponding fault code number.

[0042] For example, in this embodiment, different controllers may have the same fault code, and the same fault in the same controller from different manufacturers may have different fault codes, resulting in one fault corresponding to multiple fault codes, and one fault code often corresponding to multiple controllers. Therefore, in order to ensure the realization of the vehicle fault diagnosis function, this embodiment realizes the unique correspondence between the fault code and the controller fault.

[0043] Specifically, the type of controller can be identified by the source address of the controller. For example, if the source address of controller A is "0x00", it means that controller A is the engine, and if the source address of controller B is "0x03", it means that controller B is the transmission. The setting of the source address can be determined according to the J1939 protocol (the J1939 protocol is a standard developed by the American Society of Automotive Engineers), or it can be determined according to actual needs, and is not limited here. After knowing the type of controller, it is also necessary to know the manufacturer corresponding to the controller. Therefore, the electronic control system number can be used to distinguish controllers from different manufacturers. For example, if the electronic control system number of controller A is "xxxx", it means that controller A is manufactured by manufacturer M. If the electronic control system number of controller B is "yyyy", it means that controller B is manufactured by manufacturer W.

[0044] This embodiment can identify the specific fault object based on the fault code number, and since one SPN and one PGN can determine a fault code number, this embodiment preferably obtains the fault code number by encoding the suspect parameter number (SPN) and failure mode indicator (FMI) of each controller.

[0045] The fault code number can be composed of a letter and four numbers in sequence. For example, the fault code number for controller A is "P3609" and the fault code number for controller B is "B2503". The first letter represents the system to which the fault belongs. In this embodiment, the vehicle can be divided into four major parts: power, chassis, body, and network communication. For example, P can represent power, B represents body, C represents chassis, and U represents network. The first digit represents the fault type. The second digit represents the subsystem to which the fault belongs. For example, for the power part, "0" can be used to represent the fuel and air metering auxiliary emission control system, "1" represents the fuel and air metering system, "2" represents the fuel and air metering system (injector), "3" represents the ignition system, "4" represents the exhaust control system, "5" represents the cruise and idle control system, and "6" represents control unit-related. The third and fourth digits together represent the conditions that trigger the fault code, which can specifically represent the actual component or a specific fault name, such as low or high voltage, slow response, signal out of range, etc.

[0046] It can be seen that the fault code information of each controller is different, that is, each controller has a unique fault code information.

[0047] Furthermore, in an embodiment of the present application, the obtaining of fault code information corresponding to each controller specifically includes the following steps: obtaining fault code information corresponding to each controller sent by a supplier and / or an OEM.

[0048] For example, since for the same controller, there is often a conflict between the fault codes provided by the supplier and the host factory. Therefore, in this embodiment, the fault codes provided by the supplier and the host factory will also be processed differently. Specifically, the supplier maintains the fault code information in accordance with the requirements of the host factory (including changes to the fault code). After authorization and activation by the host factory, the fault code information is maintained and uploaded in accordance with the requirements of the host factory. Before uploading, the supplier needs to simulate, confirm and review the fault code information internally, and it will be allowed to upload only after passing the internal review. After the supplier uploads the fault code information, the host factory confirms the fault code information and releases it after confirmation. If the confirmation fails, the supplier's application will be rejected. The supplier needs to improve and modify the fault code information and upload it again until it is confirmed to be passed.

[0049] The OEM establishes a fault code information publishing template according to certain rules and is responsible for maintaining the format and content of the fault code information. It also maintains and uploads the developed fault code information. Before uploading, it also needs to simulate, confirm, and review the fault code information. Only after passing the review can it be uploaded. Thus, this embodiment can obtain the fault code information corresponding to each controller sent by the supplier and the OEM in a template format.

[0050] Step S20: generating a corresponding controller identification code based on the fault code information of each controller, and forming an identification code list with multiple controller identification codes;

[0051] For example, in this embodiment, an identification code is generated for each controller's fault code information that can be used to uniquely identify the fault code. A mapping relationship exists between the identification code and the fault code information, that is, the identification code can be used to obtain information such as the controller type, controller manufacturer, system and subsystem to which the fault belongs, fault type, and fault cause corresponding to the fault code. For example, if the fault code information of controller A is: source address "0x00", electronic control system number "CUMMS", and fault code number "P3609", then the controller identification code corresponding to this fault code information is "1501254_CUMMS_01"; if the fault code information of controller B is: source address "0x03", electronic control system number "DDTX", and fault code number "P2503", then the controller identification code corresponding to this fault code information is "1501254_DDTX_01".

[0052] The different controller identification codes are then organized into an identification code sequence, and an identification code list is formed based on the identification code sequence. The identification code list not only records the mapping relationship between the controller identification code and the fault code information, but also presents the basic information corresponding to the fault code (for example, the identification code list includes the name and model of the controller, detailed description of the fault, brief description, fault level, cause of the problem, cause of the problem and solution, etc.).

[0053] Step S30: managing the fault codes corresponding to the respective controllers based on the identification code list.

[0054] For example, in this embodiment, the unique corresponding fault code and related information (such as the name and model of the controller, detailed description of the fault, brief description, fault level, causing the problem, cause of the problem and solution, etc.) can be found from the identification code list based on the controller identification code, and then the fault code can be read or the related information of the fault code can be updated, deleted, added, and other management operations can be performed, and the application end can obtain the fault information it needs by extracting different fields.

[0055] It can be seen that the embodiment of the present application generates an identification code for each controller that can uniquely identify the controller through the controller's source address, electronic control system number and fault code number, and then uses the mapping relationship between the identification code and the controller to ensure that there is a unique correspondence between the controller and its corresponding fault code, so as to avoid the problem of one fault code corresponding to different controllers, thereby realizing effective management of fault codes.

[0056] Furthermore, in the embodiment of the present application, after the step of managing the fault codes corresponding to the respective controllers based on the identification code list, the method further includes:

[0057] Receive a fault code message sent by the application end, wherein the fault code message includes fault code information of the fault to be detected;

[0058] Filtering the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message;

[0059] The first fault code corresponding to the first controller identification code is sent to the application end, so that the application end can perform vehicle fault diagnosis based on the first fault code.

[0060] For example, in this embodiment, since there is a one-to-one correspondence between the controller identification code and the fault code information, when the application end needs to perform fault detection, it only needs to send the fault code information of the fault to be detected. At this time, this embodiment will filter out the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code information of the fault to be detected, and then read the fault code and related information corresponding to the first controller identification code (such as the name and model of the controller, detailed description of the fault, brief description, cause of the problem and cause of the problem, etc.), and send them to the application end. The application end can then perform fault detection based on the received fault code.

[0061] Furthermore, in the embodiment of the present application, after the step of the application end performing vehicle fault diagnosis based on the first fault code, the method further includes:

[0062] Obtaining a vehicle fault diagnosis result, and detecting whether the vehicle fault diagnosis result indicates a fault exists;

[0063] If a fault occurs, updating the error statistics field corresponding to the first controller identification code in the identification code list;

[0064] If there is no fault, the step of obtaining the vehicle fault diagnosis result is performed.

[0065] For example, in this embodiment, in order to more accurately grasp the fault conditions of each controller, statistics will be collected for each fault, that is, the vehicle fault diagnosis results sent by the application end are obtained. If the vehicle fault diagnosis results show that there is a fault corresponding to the fault code, the controller identification code corresponding to the fault code is found in the identification code list, and the number of the error statistics field corresponding to the controller identification code is updated. Then, the number of faults corresponding to the fault code in the vehicle can be accurately learned based on the error statistics field, thereby facilitating the diagnosis of vehicle offline faults and the support of vehicle repair faults after sales. Of course, fault statistics reports can also be generated based on the received vehicle fault diagnosis results to facilitate subsequent big data analysis and processing to obtain higher-quality vehicle fault information.

[0066] Furthermore, in an embodiment of the present application, the identification code list includes fault level information of the fault code.

[0067] Furthermore, in an embodiment of the present application, after the step of filtering out the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message, the method further includes:

[0068] The fault level of the first fault code corresponding to the first controller identification code is sent to the application end, so that the application end determines a maintenance strategy for the vehicle based on the fault level of the first fault code.

[0069] For example, in this embodiment, fault codes are set based on user sensitivity so that users can obtain more effective information about the fault codes and effectively maintain their vehicles. For example, fault codes can be divided into four levels: level 1, level 2, level 3, and level 4. Level 1 faults include faults that cause the vehicle to stop, faults involving safety, and faults that prevent starting. Level 2 faults include faults that require repair at a service station. Level 3 faults include faults that can be repaired during routine maintenance. Level 4 faults include minor faults that only some users would mind. Level 4 faults that are minor do not need to be displayed on the instrument panel. However, for the above-mentioned level 1, level 2, and level 3 faults that involve substantial problems, they should be displayed on the instrument panel so that users can be informed immediately and take appropriate maintenance measures.

[0070] It can be seen from this that users can determine the specific maintenance plan for the vehicle based on the fault level they receive. For example, when the fault level received by the user is a level 2 fault, the vehicle needs to be sent to a service station for repair as soon as possible.

[0071] See also Figure 2 As shown, the embodiment of the present application provides a fault code management device, including:

[0072] An acquisition unit, configured to acquire fault code information corresponding to each controller, wherein the fault code information includes a source address of the controller, an electronic control system number, and a fault code number;

[0073] a mapping unit, configured to generate a corresponding controller identification code based on the fault code information of each controller, wherein the plurality of controller identification codes form an identification code list;

[0074] A management unit is used to manage the fault codes corresponding to each controller based on the identification code list.

[0075] In the embodiment of the present application, an identification code that can uniquely identify the controller is generated for each controller through the source address, electronic control system number and fault code number of the controller, and then a mapping relationship between the identification code and the controller is used to ensure that there is a unique correspondence between the controller and its corresponding fault code, so as to avoid the problem of one fault code corresponding to different controllers, thereby realizing effective management of fault codes.

[0076] Furthermore, in an embodiment of the present application, the management unit is further configured to:

[0077] The suspicious parameter number and fault mode flag of each controller are encoded to obtain the corresponding fault code number.

[0078] Furthermore, in an embodiment of the present application, the acquisition unit is specifically used to: acquire fault code information corresponding to each controller sent by the supplier and / or the host manufacturer.

[0079] Furthermore, in an embodiment of the present application, the management unit is further configured to:

[0080] Receive a fault code message sent by the application end, wherein the fault code message includes fault code information of the fault to be detected;

[0081] Filtering the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message;

[0082] The first fault code corresponding to the first controller identification code is sent to the application end, so that the application end can perform vehicle fault diagnosis based on the first fault code.

[0083] Furthermore, in an embodiment of the present application, the management unit is further configured to:

[0084] Obtaining a vehicle fault diagnosis result, and detecting whether the vehicle fault diagnosis result indicates a fault exists;

[0085] If a fault occurs, updating the error statistics field corresponding to the first controller identification code in the identification code list;

[0086] If there is no fault, the step of obtaining the vehicle fault diagnosis result is performed.

[0087] Furthermore, in an embodiment of the present application, the identification code list includes fault level information of the fault code.

[0088] Furthermore, in an embodiment of the present application, the management unit is further configured to:

[0089] The fault level of the first fault code corresponding to the first controller identification code is sent to the application end, so that the application end determines a maintenance strategy for the vehicle based on the fault level of the first fault code.

[0090] It should be noted that, those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the aforementioned fault code management method embodiment, and will not be repeated here.

[0091] The fault code management provided in the above embodiment can be implemented in the form of a computer program. The computer program can be used in Figure 3 The fault codes shown are run on the management device.

[0092] An embodiment of the present application also provides a fault code management device, comprising: a memory, a processor, and a network interface connected via a system bus, wherein at least one instruction is stored in the memory, and at least one instruction is loaded and executed by the processor to implement all or part of the steps of the aforementioned fault code management method.

[0093] Among them, the network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0094] The processor may be a CPU, or other general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor, or any conventional processor. The processor is the control center of a computer device, connecting various parts of the entire computer device using various interfaces and lines.

[0095] The memory can be used to store computer programs and / or modules. The processor implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store an operating system, at least one application required for a function (such as a video playback function, an image playback function, etc.), etc.; the data storage area can store data created based on the use of the mobile phone (such as video data, image data, etc.). In addition, the memory can include high-speed random access memory and non-volatile memory, such as a hard disk, internal memory, a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0096] An embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, all or part of the steps of the aforementioned fault code management method are implemented.

[0097] The embodiments of the present application implement all or part of the aforementioned processes, and may also be completed by instructing related hardware through a computer program. The computer program may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of each of the above methods may be implemented. Among them, the computer program includes computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0098] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, servers, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage) containing computer-usable program code.

[0099] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0100] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0101] The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims

1. A fault code management method, characterized in that: The following steps are involved: Obtaining fault code information corresponding to each controller, wherein the fault code information includes the source address of the controller, the electronic control system number, and the fault code number; Generate a corresponding controller identification code based on the fault code information of each controller, and form an identification code list with multiple controller identification codes; Managing the fault codes corresponding to each controller based on the identification code list; Before the step of obtaining the fault code information corresponding to each controller, the method further includes: Encode the suspicious parameter number and fault mode flag of each controller to obtain the corresponding fault code number; Wherein, after the step of managing the fault codes corresponding to the respective controllers based on the identification code list, the method further includes: Receive a fault code message sent by the application end, wherein the fault code message includes fault code information of the fault to be detected; Filtering the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message; The first fault code corresponding to the first controller identification code is sent to the application end, so that the application end can perform vehicle fault diagnosis based on the first fault code.

2. The fault code management method according to claim 1, characterized in that: The obtaining of the fault code information corresponding to each controller includes: Obtain fault code information corresponding to each controller sent by the supplier and / or OEM.

3. The fault code management method according to claim 1, wherein: After the step of the application end performing vehicle fault diagnosis based on the first fault code, the method further includes: Obtaining a vehicle fault diagnosis result, and detecting whether the vehicle fault diagnosis result indicates a fault exists; If a fault occurs, updating the error statistics field corresponding to the first controller identification code in the identification code list; If there is no fault, the step of obtaining the vehicle fault diagnosis result is performed.

4. The fault code management method according to claim 1, wherein: The identification code list includes fault level information of the fault codes.

5. The fault code management method according to claim 4, characterized in that: After the step of selecting the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message, the method further includes: The fault level of the first fault code corresponding to the first controller identification code is sent to the application end, so that the application end determines a maintenance strategy for the vehicle based on the fault level of the first fault code.

6. A fault code management device, characterized in that: include: An acquisition unit, configured to acquire fault code information corresponding to each controller, wherein the fault code information includes a source address of the controller, an electronic control system number, and a fault code number; a mapping unit, configured to generate a corresponding controller identification code based on the fault code information of each controller, wherein the plurality of controller identification codes form an identification code list; a management unit, configured to manage the fault codes corresponding to the respective controllers based on the identification code list; The management unit is further configured to encode the suspicious parameter number and fault mode flag of each controller to obtain a corresponding fault code number; The management unit is further configured to: Receive a fault code message sent by the application end, wherein the fault code message includes fault code information of the fault to be detected; Filtering the first controller identification code corresponding to the fault to be detected from the identification code list based on the fault code message; The first fault code corresponding to the first controller identification code is sent to the application end, so that the application end can perform vehicle fault diagnosis based on the first fault code.

7. A fault code management device, characterized in that: include: A memory and a processor, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the fault code management method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the fault code management method according to any one of claims 1 to 5 is implemented.

Images