A Fault Code Library Management Method, Device, Equipment and Medium

Abstract

The present application discloses a method, apparatus, device and medium for fault code library management, which relates to the field of computer technology, and includes: obtaining an original fault code library corresponding to an electronic control unit of at least one vehicle model; wherein, each original fault code library includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; screening out the same fault code information from each original fault code library to construct an abstract fault code library; for each electronic control unit, inheriting from the abstract fault code library based on the original fault code library to obtain a corresponding target fault code library. The present application further constructs an abstract fault code library by screening out the same fault code information from each original fault code library, and each electronic control unit inherits the abstract fault code library based on the original fault code library to obtain a corresponding target fault code library. By means of inheritance and overloading, the redundancy of the fault code library in each electronic control unit is reduced, and the occupied space is also reduced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to a method, device, equipment and medium for managing a fault code library. Background Art

[0002] With the continuous development of automotive electronic technology, Electronic Control Units (ECUs) have been widely used in modern vehicles. While improving the power performance, economy, comfort and safety of vehicles, ECUs also make the vehicle's electrical and electronic systems more and more complex, which has also promoted the greater development of automotive diagnostic technology. Each ECU of the current vehicle has an independent fault code library, and the same ECU in different vehicle models, such as high-end models and low-end models, also has its own independent fault code library due to different fault codes. When repairing a vehicle, diagnostic software is needed to read the relevant fault codes of the vehicle's ECU, and then the fault description information corresponding to this fault code is found in the fault code library by the read fault code number. Then, the maintenance personnel analyze and repair the vehicle according to the fault description information. However, on the one hand, as vehicles become more complex and there are more vehicle models, there are more ECUs and faults, resulting in a very large fault code library for the vehicle, and the occupied space will also become larger and more download traffic is required; on the other hand, when operations such as modification, deletion or addition need to be performed on the fault code libraries of multiple ECUs, each ECU's fault code library needs to be edited, and the workload is very large and not flexible enough, resulting in very troublesome maintenance of the fault code library.

[0003] In summary, how to manage the fault code libraries of each electronic control unit, reduce the redundancy of the fault code libraries in each electronic control unit and reduce the occupied space, and facilitate the maintenance of the fault code library are problems to be solved at present. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method, device, equipment and medium for managing a fault code library, which can manage the fault code libraries of each electronic control unit, reduce the redundancy of the fault code libraries in each electronic control unit and reduce the occupied space, and facilitate the maintenance of the fault code library. The specific solutions are as follows:

[0005] In the first aspect, the present application discloses a method for managing a fault code library, including:

[0006] Obtain the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and the corresponding fault code description information;

[0007] Screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library;

[0008] For each of the electronic control units, inherit from the abstract fault code library based on the original fault code library to obtain a corresponding target fault code library.

[0009] Optionally, the electronic control units of the at least one vehicle model are of the same type of electronic control units of the at least one vehicle model.

[0010] Optionally, the inheriting from the abstract fault code library based on the original fault code library to obtain a corresponding target fault code library includes:

[0011] If the fault codes in the original fault code library are the same as the fault codes in the abstract fault code library, determine whether the corresponding fault code description information in the original fault code library and the abstract fault code library is the same;

[0012] If they are the same, directly inherit from the abstract fault code library to obtain a corresponding target fault code library.

[0013] Optionally, after determining whether the corresponding fault code description information in the original fault code library and the abstract fault code library is the same, it further includes:

[0014] If they are not the same, determine the fault codes in the original fault code library that are inconsistent with the fault code description information in the abstract fault code library to obtain first target fault codes;

[0015] After inheriting from the abstract fault code library, configure the first target fault codes with a first preset tag to obtain a corresponding target fault code library.

[0016] Optionally, the inheriting from the abstract fault code library based on the original fault code library to obtain a corresponding target fault code library includes:

[0017] If the fault codes in the original fault code library are not the same as the fault codes in the abstract fault code library, determine second target fault codes in the electronic control unit; where the second target fault codes are not included in the abstract fault code library;

[0018] After inheriting from the abstract fault code library, configure the second target fault codes with a second preset tag to obtain a corresponding target fault code library.

[0019] Optionally, the fault code library management method further includes:

[0020] If update information of the abstract fault code library is detected, each of the target fault code libraries performs corresponding update operations based on the update information.

[0021] Optionally, the fault code library management method further includes:

[0022] When an information search instruction is obtained, search for the target trouble code description information corresponding to the information search instruction from the target trouble code library;

[0023] If the target trouble code description information does not exist in the target trouble code, search for the target trouble code description information from the abstract code library, so as to perform a fault repair operation on the target device according to the target trouble code description information.

[0024] In a second aspect, the present application discloses a fault code library management device, including:

[0025] A fault code library acquisition module, configured to acquire an original fault code library corresponding to an electronic control unit of at least one vehicle model; wherein, each of the original fault code libraries includes a plurality of pieces of fault code information, and the fault code information includes a fault code and a corresponding fault code description information;

[0026] A fault code library construction module, configured to screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library;

[0027] An inheritance module, configured to inherit from the abstract fault code library based on the original fault code library for each of the electronic control units to obtain a corresponding target fault code library.

[0028] In a third aspect, the present application discloses an electronic device, including:

[0029] A memory, configured to store a computer program;

[0030] A processor, configured to execute the computer program to implement the steps of the foregoing disclosed fault code library management method.

[0031] In a fourth aspect, the present application discloses a computer-readable storage medium, configured to store a computer program; wherein, when the computer program is executed by a processor, the steps of the foregoing disclosed fault code library management method are implemented.

[0032] It can be seen that the present application obtains the original fault code libraries corresponding to at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library; for each of the electronic control units, inheritance is performed from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library. Thus, it can be seen that after the present application obtains the original fault code libraries corresponding to at least one vehicle model, the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library, and then each electronic control unit inherits from the original fault code library to the abstract fault code library to obtain the corresponding target fault code library. In this way, through the method of inheritance and overloading, the redundancy of the fault code libraries in each electronic control unit can be reduced, the occupied space can be reduced, and at the same time, it is convenient for subsequent maintenance of the fault code libraries. Description of the Drawings

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0034] Figure 1 It is a flowchart of a fault code library management method disclosed in the present application;

[0035] Figure 2 It is a schematic diagram of an existing fault code library disclosed in the present application;

[0036] Figure 3 It is a flowchart of a specific fault code library management method disclosed in the present application;

[0037] Figure 4 It is a schematic diagram of fault code library inheritance disclosed in the present application;

[0038] Figure 5 It is a schematic diagram of a fault code library in a specific inheritance and overloading format disclosed in the present application;

[0039] Figure 6 It is a schematic diagram of the structure of a fault code library management device disclosed in the present application;

[0040] Figure 7 It is a structural diagram of an electronic device disclosed in the present application. Detailed Embodiments

[0041] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0042] Each ECU of the current vehicle has an independent fault code library, and for the same ECU in different vehicle models such as high - end models and low - end models, due to differences in fault codes, they also have their own independent fault code libraries. However, on the one hand, as vehicles become more complex and there are more vehicle models, the number of ECUs and faults is increasing, resulting in a very large fault code library for the vehicle, and the occupied space will also become larger and more download traffic is required; on the other hand, when operations such as modification, deletion, or addition need to be performed on the fault code libraries of multiple ECUs, each ECU's fault code library needs to be edited, with a very large workload and lack of flexibility, making the maintenance of the fault code library very troublesome. For this reason, the embodiments of the present application disclose a fault code library management method, device, equipment, and medium, which can manage the fault code libraries of each electronic control unit, reduce the redundancy of the fault code libraries in each electronic control unit and reduce the occupied space, and facilitate the maintenance of the fault code library.

[0043] See Figure 1 As shown, the embodiments of the present application disclose a fault code library management method, which includes:

[0044] Step S11: Obtain the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a certain number of fault code information, and the fault code information includes a fault code and corresponding fault code description information.

[0045] In this embodiment, since each electronic control unit of the same vehicle has an independent fault code library, and the same electronic control unit in different vehicle models also has its own independent fault code library, therefore, the embodiments of the present application first need to obtain the original fault code libraries corresponding to the electronic control units of at least one vehicle model, and each original fault code library includes a certain number of fault code information, and the fault code information also includes a fault code and corresponding fault code description information.

[0046] Step S12: Screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library.

[0047] In this embodiment, after determining the original fault code libraries corresponding to each electronic control unit, the original fault code libraries are sorted out, and the same fault code information is screened out from each original fault code library to construct an abstract fault code library. That is to say, the fault code information existing in each electronic control unit is extracted and separately formed into an abstract fault code library. Refer to Figure 2 as shown in Figure 2 FIG. Figure 2 is a schematic diagram of an existing fault code library disclosed in the present application. There are three examples of fault code libraries of electronic control units in the figure, named ENGINE_ECU1, ENGINE_ECU2, and ENGINE_ECU3 respectively. Therefore, the fault code information existing in all three electronic control units can be screened out to construct an abstract fault code library.

[0048] In another specific embodiment, the same fault codes can be selected to construct an abstract fault code library. It can be understood that there is fault code information in each original fault code library where the fault codes are the same but the corresponding fault code description information is different. Taking the Figure 2 fault code libraries of the three electronic control units in Figure 2 as an example, in , ENGINE_ECU1 has 10 fault codes, ENGINE_ECU2 has 10 fault codes, and ENGINE_ECU3 has 11 fault codes. There are 10 fault codes that are the same among the three electronic control units. Among them, the description information corresponding to one fault code in ENGINE_ECU1 and ENGINE_ECU2 is inconsistent. At this time, any one of the fault code libraries of ENGINE_ECU1 and ENGINE_ECU2 can be randomly screened out as the abstract fault code library. Further, since the description information in ENGINE_ECU1 is the same as that in ENGINE_ECU3, in order to reduce the changes when inheriting the abstract fault code library, ENGINE_ECU1 can be preferentially selected as the abstract fault code library. That is to say, when selecting the abstract fault library, the one with a higher similarity to the other fault code libraries is selected as the abstract fault code library, which is more convenient for the subsequent inheritance process.

[0049] Step S13: For each of the electronic control units, inherit from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library.

[0050] In this embodiment, after obtaining the abstract fault code library, for each electronic control unit, inherit from the abstract fault code library based on its respective original fault code library to obtain the corresponding target fault code library. It can be understood that inheriting from which library means including all the fault codes and fault code description information in the inherited library. In this way, through the method of inheritance and overloading, a large amount of redundancy in the fault code library can be reduced, and at the same time, the occupied space is reduced.

[0051] It can be seen that the present application obtains the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library; for each of the electronic control units, based on the original fault code library, inheritance is performed from the abstract fault code library to obtain the corresponding target fault code library. Thus, it can be seen that after the present application obtains the original fault code libraries corresponding to the electronic control units of at least one vehicle model, the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library, and then each electronic control unit performs inheritance on the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library. In this way, through the method of inheritance and overloading, the redundancy of the fault code libraries in each electronic control unit can be reduced, the occupied space can be reduced, and at the same time, it is convenient for subsequent maintenance of the fault code libraries.

[0052] See Figure 3 As shown, an embodiment of the present application discloses a specific fault code library management method. Compared with the previous embodiment, this embodiment further illustrates and optimizes the technical solution. Specifically, it includes:

[0053] Step S21: Obtain the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information.

[0054] In this embodiment, the electronic control units of the above at least one vehicle model are the same type of electronic control units of at least one vehicle model. That is, considering that the fault codes of different types of ECUs are basically inconsistent, in a specific embodiment, the present application can obtain the original fault code libraries of the same type of ECU to improve the applicability of the present solution. For example, they can all be engine ECUs.

[0055] Step S22: Screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library.

[0056] Step S23: For each of the electronic control units, if the fault code in the original fault code library is the same as the fault code in the abstract fault code library, then determine whether the corresponding fault code description information in the original fault code library and the abstract fault code library is the same.

[0057] In this embodiment, for each electronic control unit, if the fault code in the corresponding original fault code is the same as the fault code in the abstract fault code library, then further determine whether the corresponding fault code description information in the original fault code and the abstract fault code library is the same.

[0058] Step S24: If they are consistent, directly inherit from the abstract fault code library to obtain the corresponding target fault code library.

[0059] In a specific embodiment, if the original fault code is consistent with the corresponding fault code description information in the abstract fault code library, directly inherit the abstract fault code library to obtain the target fault code library corresponding to the electronic control unit. That is, if the fault code and the fault code description information in the original fault code library corresponding to the electronic control unit are both consistent with the fault code and the fault code description information in the abstract fault code, directly inherit from the abstract fault code library to obtain the corresponding target fault code library.

[0060] In the second specific embodiment, after determining whether the corresponding fault code description information in the original fault code library and the abstract fault code library is consistent, it further includes: if they are inconsistent, determine the fault codes in the original fault code library that are inconsistent with the fault code description information in the abstract fault code library to obtain the first target fault code; after inheriting from the abstract fault code library, configure the first target fault code with a first preset tag to obtain the corresponding target fault code library. That is, if the corresponding fault code description information in the original fault code library and the abstract fault code library is inconsistent, determine the fault codes with inconsistent fault code description information to obtain the first target fault code, and then after inheriting the abstract fault code library, configure the first target fault code with the first preset tag to obtain the corresponding target fault code library. That is to say, for the fault codes with inconsistent description information in the abstract fault code library, they need to be configured separately with the first preset tag. The first preset tag can specifically be <diff>。

[0061] In the third specific embodiment, the above-mentioned inheritance from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library includes: if the fault codes in the original fault code library are inconsistent with the fault codes in the abstract fault code library, determine the second target fault code in the electronic control unit; wherein, the second target fault code is not included in the abstract fault code library; after inheriting from the abstract fault code library, configure the second target fault code with a second preset tag to obtain the corresponding target fault code library. That is to say, if the fault codes in the original fault code library corresponding to the electronic control unit are inconsistent with the fault codes in the abstract fault code library, then determine the redundant second target fault code in the original fault code library. From the foregoing public content, it can be seen that the abstract fault codes are constructed by screening out the same fault code information from each original fault code library. Therefore, the number of fault codes in the original fault code library is greater than the number of fault codes in the abstract fault code library. Therefore, the second target fault code is not included in the abstract fault code library. Then, after inheriting the abstract fault code library, configure the second target fault code with a second preset tag to obtain the corresponding target fault code library. The second preset tag can specifically be <new>Label.

[0062] For example, see Figure 4 As shown, each subsystem ECU, such as Engine 1, Engine 2, Engine 3, inherits from this abstract ECU fault code library. If the subsystem ECU has the same function as the abstract ECU, it can be directly inherited without duplicate writing. If there are differences, they can be modified in the subsystem ECU to override the different items in the corresponding fault code library of the abstract ECU. If a new fault code description is added to the subsystem ECU, it can also be added in the subsystem ECU. This can greatly reduce the redundancy of the fault code library.

[0063] See Figure 5 As shown, Figure 5 is a schematic diagram of a fault code library in a specific inheritance and override format disclosed in this application. Among them, the abstract fault code library is constructed based on the fault code library of ENGINE_ECU1 in Figure 2 and named ABSTRACT_ECU_CODE_LIB. Then, when ENGINE_ECU1 inherits from the abstract fault code library later, since the fault codes and corresponding description information of ENGINE_ECU1 are exactly the same as those of the abstract fault code library, it directly inherits the abstract fault code library without the need to modify or add other additional information. The specific code is as follows:

[0064] <LIB PARENT=ABSTRACT_ECU_CODE_LIB>ENGINE_ECU1; where the PARENT attribute indicates from which fault code library to inherit, and ABSTRACT_ECU_CODE_LIB is the name of the library to be inherited.

[0065] ENGINE_ECU2 also inherits from the abstract fault code library ABSTRACT_ECU_CODE_LIB, <LIB PARENT=ABSTRACT_ECU_CODE_LIB>ENGINE_ECU2. However, since the description information of the fault code U241683 in ENGINE_ECU2 is different from the description of the U241683 fault code in ABSTRACT_ECU_CODE_LIB, it needs to be distinguished after inheriting the abstract fault code library. Specifically, use <diff>Use tags to configure diagnostic trouble codes with the same diagnostic trouble code number but inconsistent descriptions, that is, configure the second target diagnostic trouble code.

[0066] ENGINE_ECU3 also inherits from the abstract diagnostic trouble code library ABSTRACT_ECU_CODE_LIB, <LIB PARENT=ABSTRACT_ECU_CODE_LIB>ENGINE_ECU3. However, since there is one more diagnostic trouble code P119F68 in ENGINE_ECU3 than in the ABSTRACT_ECU_CODE_LIB library, tags need to be used after inheriting the abstract diagnostic trouble code library. <new>Configure multiple fault codes.

[0067] Furthermore, in this embodiment, the above-mentioned fault code library management method further includes: if it is detected that the abstract fault code library has update information, each of the target fault code libraries performs corresponding update operations based on the update information. It can be understood that since each electronic control unit inherits from the abstract fault code library, when it is detected that the abstract fault code library has update information, the target fault code libraries corresponding to each electronic control unit perform corresponding update operations based on the update information. The above update information can be that it is detected that the fault code description information has additional content or modified content, etc. In other words, if each electronic control unit needs to add or modify the same fault code description information, only the fault code description information in the abstract fault code library needs to be modified or added, so that the fault code description information corresponding to the corresponding target fault code libraries in all the electronic control units inherited from it will be automatically modified or added. In this way, there is no need to modify the target fault code library of each electronic control unit, greatly reducing the workload and making the processing method more flexible.

[0068] Moreover, in this embodiment, the above-mentioned fault code library management method further includes: when an information search instruction is obtained, search for the target fault code description information corresponding to the information search instruction from the target fault code library; if the target fault code description information does not exist in the target fault code, search for the target fault code description information from the abstract code library, so as to perform a fault repair operation on the target device according to the target fault code description information. That is, the search priority of the target fault code library of the electronic control unit is higher than that of the inherited abstract fault code library. When a fault code search instruction is obtained, first search for the target description information corresponding to the fault code search instruction from the target fault code library; if the target description information does not exist in the target fault code, then search for the target description information from the abstract code library, so that the maintenance personnel can perform fault analysis and fault repair operations on the target device according to the target description information, where the target device can specifically be a vehicle. For example Figure 2 Taking the fault code shown as an example, if you want to search for the description information of the U241683 fault code, it will first be searched in the target fault code library corresponding to ENGINE_ECU2 itself. If it is found, the corresponding description information will be obtained. If it is not found in the fault code library of ENGINE_ECU2, then it will be searched from the inherited abstract fault code library.

[0069] Among them, for a more specific processing process of the above step S22, reference can be made to the corresponding content disclosed in the foregoing embodiment, and details will not be elaborated here.

[0070] It can be seen that the electronic control unit in the embodiment of the present application is a same-type electronic control unit for at least one vehicle model, and there are three situations when the electronic control unit inherits the abstract fault code library, and corresponding solutions are provided for the three different situations. If the fault codes and description information in the electronic control unit are the same as those in the abstract fault code library, the abstract fault code library is directly inherited without additional operations; if the fault codes are the same but the description information is different, after inheriting the abstract fault code library, the first preset tag is used to configure the first target fault code with inconsistent description information; if the number of fault codes in the target fault code library is more than that in the abstract fault code library, after inheriting the abstract fault code library, the second preset tag is used to configure the second target fault code that is more. In addition, if updated information of the abstract fault code library is detected, each target fault code library performs corresponding update operations based on the updated information, greatly reducing the workload. And when repairing the target device, it is necessary to read the fault codes and find the corresponding description information, and in this embodiment, the search priority of the target fault code library of the electronic control unit is higher than that of the inherited abstract fault code library.

[0071] See Figure 6 As shown, the embodiment of the present application discloses a fault code library management device, and the device includes:

[0072] A fault code library acquisition module 11, configured to acquire the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a plurality of pieces of fault code information, and the fault code information includes a fault code and corresponding fault code description information;

[0073] A fault code library construction module 12, configured to screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library;

[0074] An inheritance module 13, configured to inherit from the abstract fault code library based on the original fault code library for each of the electronic control units to obtain a corresponding target fault code library.

[0075] It can be seen that the present application obtains the original fault code libraries corresponding to the electronic control units of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library; for each of the electronic control units, based on the original fault code library, inheritance is performed from the abstract fault code library to obtain the corresponding target fault code library. Thus, it can be seen that after the present application obtains the original fault code libraries corresponding to the electronic control units of at least one vehicle model, the same fault code information is screened out from each of the original fault code libraries to construct an abstract fault code library, and then each electronic control unit performs inheritance from the original fault code library to the abstract fault code library to obtain the corresponding target fault code library. In this way, through the method of inheritance and overloading, the redundancy of the fault code libraries in each electronic control unit can be reduced, the occupied space can also be reduced, and at the same time, it is convenient for subsequent maintenance of the fault code libraries.

[0076] In some specific embodiments, in the fault code library acquisition module 11, the electronic control units of the at least one vehicle model are the same type of electronic control units of the at least one vehicle model.

[0077] In some specific embodiments, the inheritance module 13 may specifically include:

[0078] A first judgment unit, configured to judge whether the fault code description information corresponding to the fault code in the original fault code library is consistent with that in the abstract fault code library if the fault code in the original fault code library is consistent with the fault code in the abstract fault code library;

[0079] A first inheritance unit, configured to directly perform inheritance from the abstract fault code library to obtain the corresponding target fault code library if they are consistent.

[0080] In some specific embodiments, after the first judgment unit, it may further include:

[0081] A first determination unit, configured to determine the fault code in the original fault code library that is inconsistent with the fault code description information in the abstract fault code library to obtain a first target fault code if they are inconsistent;

[0082] A first configuration unit, configured to configure the first target fault code with a first preset tag after performing inheritance from the abstract fault code library to obtain the corresponding target fault code library.

[0083] In some specific embodiments, the inheritance module 13 may specifically include:

[0084] A second determination unit, configured to determine a second target fault code in the electronic control unit if the fault code in the original fault code library is inconsistent with the fault code in the abstract fault code library; wherein, the second target fault code is not included in the abstract fault code library;

[0085] A second configuration unit, configured to, after inheriting from the abstract fault code library, configure the second target fault code with a second preset tag to obtain a corresponding target fault code library.

[0086] In some specific embodiments, the fault code library management device may further include:

[0087] An update unit, configured to, if update information of the abstract fault code library is detected, perform corresponding update operations on each of the target fault code libraries based on the update information.

[0088] In some specific embodiments, the fault code library management device may further include:

[0089] A first search unit, configured to, when an information search instruction is obtained, search for target fault code description information corresponding to the information search instruction in the target fault code library;

[0090] A second search unit, configured to, if the target fault code description information does not exist in the target fault code, search for the target fault code description information in the abstract code library, so as to perform a fault repair operation on the target device according to the target fault code description information.

[0091] Figure 6 The structure diagram of an electronic device provided by an embodiment of the present application. Specifically, it may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Wherein, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the fault code library management method executed by the electronic device disclosed in any of the foregoing embodiments.

[0092] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is any communication protocol applicable to the technical solution of the present application, and specific limitations are not imposed on it here; the input / output interface 25 is used to obtain external input data or output data to the outside, and its specific interface type can be selected according to specific application needs, and specific limitations are not imposed here.

[0093] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor used to process data in the wake state, also known as the CPU (Central Processing Unit); the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may further include an AI (Artificial Intelligence) processor, and the AI processor is used to process computational operations related to machine learning.

[0094] In addition, the memory 22, as a carrier for resource storage, may be a read-only memory, a random access memory, a disk, or an optical disc, etc. The resources stored thereon include an operating system 221, a computer program 222, data 223, etc., and the storage method may be temporary storage or permanent storage.

[0095] Among them, the operating system 221 is used to manage and control each hardware device and the computer program 222 on the electronic device 20, so as to enable the processor 21 to perform operations and processing on the massive data 223 in the memory 22. It may be Windows, Unix, Linux, etc. In addition to the computer program that can be used to complete the fault code library management method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program that can be used to complete other specific tasks. The data 223 may include not only the data transmitted by external devices received by the electronic device, but also the data collected by its own input / output interface 25, etc.

[0096] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium. When the computer program stored in the storage medium is loaded and executed by a processor, it implements the method steps executed during the fault code library management disclosed in any of the foregoing embodiments.

[0097] In this specification, the various embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description in the method section.

[0098] Those skilled in the art can further realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been generally described according to their functions in the above description. Whether these functions are executed in a hardware or software manner 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 to exceed the scope of this application.

[0099] The steps of the methods or algorithms described in combination with the embodiments disclosed in this article can be directly implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the technical field.

[0100] Finally, it should also be noted that in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

[0101] The above has introduced in detail a method, device, equipment and storage medium for managing a fault code library. In this article, specific examples are used to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.< / new> < / diff> < / new> < / diff>

Claims

1. A method for managing a fault code library, characterized in that, Including: Obtain the original fault code library corresponding to the electronic control unit of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; Screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library; For each of the electronic control units, inherit from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library; Wherein, the inheriting from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library includes: If the fault code in the original fault code library is the same as the fault code in the abstract fault code library, determine whether the corresponding fault code description information in the original fault code library and the abstract fault code library is the same; If they are the same, directly inherit from the abstract fault code library to obtain the corresponding target fault code library.

2. The fault code library management method according to claim 1, wherein The electronic control units of the at least one vehicle model are of the same type of electronic control units of the at least one vehicle model.

3. The fault code library management method according to claim 2, wherein, After determining whether the corresponding fault code description information in the original fault code library and the abstract fault code library is the same, it further includes: If they are not the same, determine the fault code in the original fault code library that is inconsistent with the fault code description information in the abstract fault code library to obtain the first target fault code; After inheriting from the abstract fault code library, configure the first target fault code with a first preset tag to obtain the corresponding target fault code library.

4. The fault code library management method according to claim 1, wherein The inheriting from the abstract fault code library based on the original fault code library to obtain the corresponding target fault code library includes: If the fault code in the original fault code library is different from the fault code in the abstract fault code library, determine the second target fault code in the electronic control unit; wherein, the second target fault code is not included in the abstract fault code library; After inheriting from the abstract fault code library, configure the second target fault code with a second preset tag to obtain the corresponding target fault code library.

5. The fault code library management method according to claim 1, characterized in that It further includes: If it is detected that the abstract fault code library has update information, each of the target fault code libraries performs corresponding update operations based on the update information.

6. The fault code library management method according to any one of claims 1 to 5, characterized in that It further includes: When an information search instruction is obtained, search for the corresponding target fault code description information from the target fault code library; If the target fault code description information does not exist in the target fault code, search for the target fault code description information from the abstract fault code library, so as to perform fault repair operations on the target device according to the target fault code description information.

7. A fault code library management device, characterized in that, Including: A fault code library acquisition module, configured to obtain the original fault code library corresponding to the electronic control unit of at least one vehicle model; wherein, each of the original fault code libraries includes a number of fault code information, and the fault code information includes a fault code and corresponding fault code description information; A fault code library construction module, configured to screen out the same fault code information from each of the original fault code libraries to construct an abstract fault code library; An inheritance module, configured to inherit from the abstract fault code library based on the original fault code library for each of the electronic control units to obtain a corresponding target fault code library; Wherein, the inheritance module includes: A first determination unit, configured to determine whether the fault code description information corresponding to the fault codes in the original fault code library and the abstract fault code library is consistent if the fault codes in the original fault code library are the same as those in the abstract fault code library; A first inheritance unit, configured to directly inherit from the abstract fault code library to obtain a corresponding target fault code library if they are consistent.

8. An electronic device, characterized in that, Comprising: A memory, configured to store a computer program; A processor, configured to execute the computer program to implement the steps of the fault code library management method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, For storing a computer program; wherein, when the computer program is executed by the processor, the steps of the fault code library management method according to any one of claims 1 to 6 are implemented.

Images