CN113535881B - Fault code information storage method, device, communication equipment and storage medium - Google Patents
Fault code information storage method, device, communication equipment and storage medium Download PDFInfo
- Publication number
- CN113535881B CN113535881B CN202110699354.XA CN202110699354A CN113535881B CN 113535881 B CN113535881 B CN 113535881B CN 202110699354 A CN202110699354 A CN 202110699354A CN 113535881 B CN113535881 B CN 113535881B
- Authority
- CN
- China
- Prior art keywords
- text
- fault
- fault code
- level
- universal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000004891 communication Methods 0.000 title claims abstract description 43
- 238000013507 mapping Methods 0.000 claims abstract description 116
- 238000012986 modification Methods 0.000 claims description 22
- 230000004048 modification Effects 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 20
- 238000006243 chemical reaction Methods 0.000 claims description 7
- 238000000605 extraction Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 208000024891 symptom Diseases 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000004806 packaging method and process Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application is applicable to the technical field of computers, and provides a fault code information storage method, a device, communication equipment and a storage medium, wherein the method comprises the following steps: acquiring a fault code text, wherein the fault code text comprises a general text of a fault; converting the universal text in the fault code text into a corresponding fault variable according to a preset relation mapping table of the universal text and the fault variable to form target fault code information; and storing the target fault code information. The embodiment of the application can improve the storage efficiency of the fault code information and save the storage space.
Description
Technical Field
The present application belongs to the field of computer technology, and in particular, relates to a method and apparatus for storing fault code information, a communication device, and a storage medium.
Background
The failure code of the vehicle is data reflecting the failure of the vehicle. When a vehicle fails, an electronic control unit (Electronic control unit, ECU) of the vehicle may analyze and record a current fault code of the vehicle by acquiring sensor data of the vehicle, thereby reflecting the current fault of the vehicle.
Typically, the vehicle is shipped with original fault code text that records the fault code that the vehicle's ECU may have and the fault content (i.e., meaning of the fault code) that it represents. The diagnosis equipment can store the fault texts in advance so as to analyze and determine the fault content corresponding to the fault code when detecting that the corresponding fault code exists in the ECU of the vehicle, thereby being convenient for maintenance personnel to carry out corresponding vehicle maintenance processing.
However, since there are many ECUs in the vehicle, the fault code that may occur to each ECU is also many, and thus the data amount of the existing fault code text is generally large, resulting in a need to occupy a large amount of storage space when storing the fault code information.
Disclosure of Invention
In view of this, the embodiments of the present application provide a method, an apparatus, a communication device, and a storage medium for storing fault code information, so as to solve the problem in the prior art how to improve the storage efficiency of fault code information and save the storage space.
A first aspect of an embodiment of the present application provides a method for storing fault code information, including:
Acquiring a fault code text, wherein the fault code text comprises a general text of a fault;
Converting the universal text in the fault code text into a corresponding fault variable according to a preset relation mapping table of the universal text and the fault variable to form target fault code information;
And storing the target fault code information.
Optionally, before the acquiring the fault code text, the method includes:
Collecting all fault code texts of the vehicle;
Extracting the universal texts according to all the fault code texts, wherein the universal texts are at least preset numbers of texts universal in the fault code texts;
And determining a fault variable corresponding to each universal text, and establishing a relation mapping table of the universal text and the fault variable.
Optionally, the general text includes a vehicle-level general text, where the vehicle-level general text is a text that is common to all fault code texts corresponding to at least two ECUs of the same vehicle;
and extracting the universal text according to all the fault code texts, wherein the extracting comprises the following steps:
extracting the vehicle-level general text according to the fault code texts;
correspondingly, the determining the fault variable corresponding to each universal text and establishing a relation mapping table of the universal text and the fault variable comprises the following steps:
And determining a vehicle-level fault variable corresponding to each vehicle-level universal text, and establishing a first relation mapping table of the vehicle-level universal text and the vehicle-level fault variable.
Optionally, the general text further includes an ECU-level general text, where the ECU-level general text is a text that is common to all fault code texts corresponding to a single ECU;
The extracting the universal text according to the all fault code texts further comprises:
Extracting the ECU-level universal text according to the all fault code texts;
Correspondingly, the determining the fault variable corresponding to each universal text, and establishing a relation mapping table between the universal text and the fault variable, further includes:
And determining an ECU level fault variable corresponding to each ECU level universal text, and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable.
Optionally, the converting the general text in the fault code text into the corresponding fault variable according to the preset relation mapping table of the general text and the fault variable to form the target fault code information includes:
According to the first relation mapping table and the second relation mapping table, converting the vehicle-level general text in the fault code text into corresponding vehicle-level fault variables, and converting the ECU-level general text in the fault code text into corresponding ECU-level fault variables to form target fault code information;
And if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
Optionally, after the storing the target fault code information, the method further includes:
Acquiring a fault code information modification request;
and modifying the general text in the relation mapping table according to the fault code information modification request.
Optionally, after the storing the target fault code information, the method further includes:
Acquiring a fault variable increasing request;
according to the fault variable increasing request, a new fault variable is added in the relation mapping table and the target fault code information; wherein the new fault variable is different from other fault variables of the same level.
A second aspect of an embodiment of the present application provides a fault code information storage device, including:
The acquisition module is used for acquiring fault code texts, wherein the fault code texts comprise fault universal texts;
the conversion module is used for converting the universal text in the fault code text into the corresponding fault variable according to a preset relation mapping table of the universal text and the fault variable to form target fault code information;
And the storage module is used for storing the target fault code information.
Optionally, the fault code information storage device further includes:
The collecting module is used for collecting all fault code texts of the vehicle;
The extraction module is used for extracting the universal text according to all the fault code texts, wherein the universal text is a text which is universal in at least a preset number of fault code texts;
and the relation mapping table establishing module is used for determining the fault variable corresponding to each universal text and establishing the relation mapping table of the universal text and the fault variable.
Optionally, the general text includes a vehicle-level general text, where the vehicle-level general text is a text that is common to all fault code texts corresponding to at least two ECUs of the same vehicle;
the extraction module comprises:
The first extraction unit is used for extracting the vehicle-level universal text according to all the fault code texts;
the relation mapping table building module comprises:
And the first relation mapping table establishing unit is used for determining a vehicle-level fault variable corresponding to each vehicle-level general text and establishing a first relation mapping table of the vehicle-level general text and the vehicle-level fault variable.
Optionally, the general text further includes an ECU-level general text, where the ECU-level general text is a text that is common to all fault code texts corresponding to a single ECU;
The extraction module further comprises:
The second extraction unit is used for extracting the ECU-level universal text according to all the fault code texts;
The relation mapping table establishing module further comprises:
And the second relation mapping table establishing unit is used for determining the ECU level fault variable corresponding to each ECU level universal text and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable.
Optionally, the conversion module is specifically configured to convert the vehicle-level general text in the fault code text into a corresponding vehicle-level fault variable according to the first relationship mapping table and the second relationship mapping table, and convert the ECU-level general text in the fault code text into a corresponding ECU-level fault variable, so as to form target fault code information; and if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
Optionally, the fault code information storage device further includes:
The modifying unit is used for acquiring the fault code information modifying request; and modifying the general text in the relation mapping table according to the fault code information modification request.
Optionally, the fault code information storage device further includes:
The adding unit is used for obtaining the fault code information modification request; and modifying the general text in the relation mapping table according to the fault code information modification request.
A third aspect of the embodiments of the present application provides a communication device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, which when executed by the processor causes the communication device to implement the steps of the fault code information storage method.
A fourth aspect of the embodiments of the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, causes a communication device to implement the steps of the fault code information storage method.
A fifth aspect of an embodiment of the present application provides a computer program product for, when run on a communication device, causing the communication device to perform the fault code information storage method of any one of the first aspects described above.
Compared with the prior art, the embodiment of the application has the beneficial effects that: in the embodiment of the application, the general text in the fault code text is converted into the corresponding fault variable according to the preset relation mapping table of the general text and the fault variable to form the target fault code information; and storing the target fault code information. Because the redundant general text in the fault code text can be represented by replacing the fault variable through the preset relation mapping table of the general text and the fault code variable, the generated target fault code information can efficiently represent the fault content of the fault code with a small data quantity, so that the original fault code text storage is replaced by storing the target fault code information, the storage efficiency of the fault code information can be improved, and the storage space is saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a schematic implementation flow chart of a first fault code information storage method according to an embodiment of the present application;
fig. 2 is a schematic implementation flow chart of a second fault code information storage method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a fault code information storage device according to an embodiment of the present application;
Fig. 4 is a schematic diagram of a communication device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to illustrate the technical scheme of the application, the following description is made by specific examples.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," etc. are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
Currently, since there are numerous ECUs in a vehicle, the fault code that may occur in each ECU is also numerous, the data volume of the existing fault code text is generally huge, and thus a large amount of storage space is required for storing the fault code information.
In order to solve the above technical problems, embodiments of the present application provide a method, an apparatus, a communication device, and a storage medium for storing fault code information, including: the method comprises the steps of obtaining a fault code text, and converting the general text in the fault code text into a corresponding fault variable according to a preset relation mapping table of the general text and the fault variable to form target fault code information; and storing the target fault code information. Because the redundant general text in the fault code text can be represented by replacing the fault variable through the preset relation mapping table of the general text and the fault code variable, the generated target fault code information can efficiently represent the fault content of the fault code with a small data quantity, so that the original fault code text storage is replaced by storing the target fault code information, the storage efficiency of the fault code information can be improved, and the storage space is saved.
Embodiment one:
Fig. 1 is a schematic flow chart of a first method for storing fault code information according to an embodiment of the present application, where an execution body of the fault code information storing method is a communication device, for example, may be a diagnostic device or a server. The fault code information storage method shown in fig. 1 is described in detail as follows:
in S101, a fault code text is obtained, the fault code text including a general text of a fault.
In the embodiment of the application, the fault code text is a text which represents the fault code and the fault content (namely the meaning of the fault code) thereof, and the fault code text is defined in advance by a vehicle manufacturer. In one embodiment, the trouble code text may be obtained from a download link or readable storage medium provided by the vehicle manufacturer.
Specifically, the fault code text includes a general text of a fault, which is text in which fault contents of a plurality of fault codes all exist. In some embodiments, the generic text may include symptom description text or part identification text commonly used by vehicles.
The fault code text may be represented by an extensible markup language (Extensible Markup Language, XML), for example. For example:
<dtc>P001664The position of the intake camshaft(cylinder bank 1)is implausible relative to the position of the crankshaft.There is an implausible signal.</dtc>
Wherein "< dtc > </dtc >" is an XML tag pair for encapsulating a piece of fault code information in the form of a fault code plus the fault content of the fault code. For example, the fault code "P001664" plus the subsequent fault content "The position of the intake camshaft(cylinder bank 1)is implausible relative to the position of the crankshaft.There is an implausible signal."( is: the position of the intake camshaft (cylinder bank 1) is not trusted with respect to the position of the crankshaft. This is an untrusted signal. "). In The fault content, the texts of 'The position of THE INTAKE CAMSHAFT' (representing The position of an air inlet cam shaft ',' is implausible relative to The position of THE CRANKSHAFT '(representing The position relative to a crank shaft is not trusted', 'THERE IS AN implausible signal', 'representing The position is an untrusted signal') are symptom description texts in general texts; "cylinder bank 1" (meaning "cylinder bank 1") is part identification text in the general text.
Specifically, in this step, a fault code text corresponding to one fault code may be obtained, or a plurality of fault code texts corresponding to a plurality of fault codes may be obtained.
In S102, according to a preset relation mapping table between the general text and the fault variable, the general text in the fault code text is converted into the corresponding fault variable, so as to form target fault code information.
In the embodiment of the application, the preset relation mapping table of the universal texts and the fault variables is a mapping table which is obtained by setting the fault variables corresponding to the universal texts in advance and storing the universal texts and the fault variables corresponding to the universal texts. The preset relationship mapping table may be stored in advance in a storage unit of the communication device.
In one embodiment, the relationship map may be represented in tabular form, as shown in Table 1.
Table 1:
in another embodiment, the relationship mapping table may be represented by XML formatted data, such as:
<vars>
<var name＝"p1">The position of the intake camshaft</var>
<var name＝"p2">The position of the exhaust camshaft</var>
<var name＝"s1">is implausible relative to the position of the crankshaft</var>
<var name＝"s2">There is an implausible signal</var>
<var name＝"s3">There is a signabove the permissible limit value</var>
<var name＝"cb1">cylinder bank 1</var>
</vars>
wherein "< vars > </vars >" is a group tag pair for encapsulating a mapping relationship of a group of fault variables and a general text; the "< var name=" > "is a label pair for packaging a mapping relation between a fault variable and a universal text, wherein the name of the fault code variable is packaged in a first label of the label pair, and the universal text corresponding to the fault code variable is packaged between two labels of the label pair.
In this step, the general text in the fault code text obtained in step S101 may be converted into a corresponding fault variable according to the above-mentioned relation mapping table, so as to obtain the target fault code information corresponding to the fault code text.
Illustratively, the fault code text corresponding to the fault code "P001664" illustrated in step S101 is converted according to the relationship mapping table illustrated above, and the obtained target fault information is: < dtc > P001664% P1% (% cb 1%)% s1% >% s2% >
In the target fault code information, "%" is a reference symbol of a fault variable, and reference to one fault variable is achieved through two reference symbols (the fault variable is located between the two reference symbols). The reference symbol may also be any other predetermined symbol, for example: ">"? "etc., without limitation herein.
In S103, the target fault code information is stored.
After the target fault code information corresponding to the fault code text is obtained through conversion, the target fault code information is stored in a storage unit of the communication equipment so as to replace the original fault text to finish fault code information storage.
In the embodiment of the application, the general text in the fault code text is converted into the corresponding fault variable according to the preset relation mapping table of the general text and the fault variable to form the target fault code information; and storing the target fault code information. Because the redundant general text in the fault code text can be represented by replacing the fault variable through the preset relation mapping table of the general text and the fault code variable, the generated target fault code information can efficiently represent the fault content of the fault code with a small data quantity, so that the original fault code text storage is replaced by storing the target fault code information, the storage efficiency of the fault code information can be improved, and the storage space is saved.
Embodiment two:
fig. 2 is a schematic flow chart of a second method for storing fault code information according to an embodiment of the present application, where an execution body of the fault code information storing method is a communication device. The fault code clearing method of the embodiment of the application is further improved on the basis of the method of the first embodiment, and the same points as the first embodiment are not repeated. The fault code information storage method shown in fig. 2 is described in detail as follows:
in S201, all trouble code text of the vehicle is collected.
In the embodiment of the application, all fault code texts of the vehicle are fault code texts corresponding to all fault codes possibly occurring in all ECUs of the vehicle of at least one vehicle type. In one embodiment, all fault code text for the vehicle may be obtained from a download link or readable storage medium provided by the vehicle manufacturer. In another embodiment, the method can communicate with each ECU of the vehicle in advance, and all fault code texts corresponding to all ECUs of the vehicle are obtained.
In S202, extracting the universal text according to the fault code texts, where the universal text is a text that is common in at least a preset number of fault code texts.
After all the fault code texts are collected, determining the texts existing in at least a preset number of fault code texts as universal texts. The preset number may be 2 or any number above 2. In particular, the general text extracted from the fault code text may include symptom description text or part identification text commonly used by vehicles.
In S203, determining a fault variable corresponding to each of the universal texts, and establishing a relationship mapping table between the universal texts and the fault variables.
After extracting each general text, setting a corresponding fault variable for each general text, establishing and storing the mapping relation between each general text and the corresponding fault variable, and obtaining a relation mapping table of the general text and the fault variable.
In S204, a fault code text is obtained, the fault code text comprising a generic text of the fault.
In S205, according to a preset relation mapping table between the general text and the fault variable, the general text in the fault code text is converted into the corresponding fault variable, so as to form the target fault code information.
In S206, the target fault code information is stored.
In the embodiment of the application, all fault code texts of the vehicle can be collected in advance to establish the relation mapping table of the general text and the fault variable, so that after the fault code texts are acquired later, the corresponding target fault code information can be accurately determined and stored according to the relation mapping table, and the efficient and accurate fault code information storage is realized.
Optionally, the general text includes a vehicle-level general text, where the vehicle-level general text is a text that is common to all fault code texts corresponding to at least two ECUs of the same vehicle; step S202 described above includes:
extracting the vehicle-level general text according to the fault code texts;
Correspondingly, the step S203 includes:
And determining a vehicle-level fault variable corresponding to each vehicle-level universal text, and establishing a first relation mapping table of the vehicle-level universal text and the vehicle-level fault variable.
In the embodiment of the application, the vehicle-level general text is a text which exists in a plurality of fault code texts of a plurality of ECUs of the same vehicle. After all fault code texts are acquired, texts which are common to most ECUs of the vehicle, such as some symptom description texts, can be arranged, and the texts are taken as vehicle-level common texts.
Illustratively, the partial data of all the trouble code texts acquired in step S201 are set as follows:
<vehicle>
<ecu>
<name>engine1</name>
<dtc>P001664The position of the intake camshaft(cylinder bank 1)is implausible relative to the position of the crankshaft.There is an implausible signal.</dtc>
<dtc>P001785The position of the exhaust camshaft(cylinder bank 1)is implausible relative to the position of the crankshaft.There is a signal above the permissible limit value.</dtc>
<dtc>P001864The position of the intake camshaft(cylinder bank 2)is implausible relative to the position of the crankshaft.There is an implausible signal.</dtc>
<dtc>P001985The position of the exhaust camshaft(cylinder bank 2)is implausible relative to the position of the crankshaft.There is a signal above the permissible limit value.</dtc>
</ecu>
<ecu>
<name>engine2</name>
<dtc>P001674The position of the intake camshaft(cylinder bank 3)is implausible relative to the position of the crankshaft.There is an implausible signal.</dtc>
<dtc>P001795The position of the exhaust camshaft(cylinder bank 3)is implausible relative to the position of the crankshaft.There is a signal above the permissible limit value.</dtc>
<dtc>P001874The position of the intake camshaft(cylinder bank 4)is implausible relative to the position of the crankshaft.There is an implausible signal.</dtc>
<dtc>P001995The position of the exhaust camshaft(cylinder bank 4)is implausible relative to the position of the crankshaft.There is a signal above the permissible limit value.</dtc>
</ecu>
</vehicle>
Wherein "< vehicle > </vehicle >" is an XML tag pair for encapsulating fault code information of one vehicle; "< ECU > </ECU >" is an XML tag pair for packaging fault code information of one ECU; "< name > </name >" is an XML tag pair for packaging the ECU name; engine1 represents engine1, engine2 represents engine 2; "cylinder bank 2" means "cylinder bank 2"; "cylinder bank 3" means "cylinder bank 3"; "cylinder bank 4" means "cylinder bank 4"; "P001664", "P001785", "P001864", "P001985", "P001674", "P001795", "P001874", "P001995" are fault codes, and text information behind the fault codes is the fault content corresponding to the fault codes; other label pairs and text information meanings that are the same as those in the trouble code text example in the previous embodiment are referred to in the related description in the previous embodiment, and are not repeated here.
In the above embodiment ,"The position of the intake camshaft""The position of the exhaust camshaft","is implausible relative to the position of the crankshaft","There is an implausible signal","There is a signal above the permissible limit value", these texts appear in the fault code text corresponding to each of the two different ECUs of engine1 and engine2, and therefore these texts are determined as vehicle-level general-purpose texts.
Then, corresponding vehicle-level fault variables are defined according to the vehicle-level general texts. The vehicle-level fault variable is a vehicle-level fault variable, and fault codes of all ECUs in the same vehicle can be used for corresponding meaning description. And establishing the mapping relation between the vehicle-level universal texts and the corresponding vehicle-level fault variables to obtain a first relation mapping table.
Illustratively, the first relationship mapping table may be tabular form data, as shown in table 2 below.
Table 2:
or the first relationship mapping table may be XML formatted data, for example:
<vars>
<var name＝"p1">The position of the intake camshaft</var>
<var name＝"p2">The position of the exhaust camshaft</var>
<var name＝"s1">is implausible relative to the position of the crankshaft</var>
<var name＝"s2">There is an implausible signal</var>
<var name＝"s3">There is a signabove the permissible limit value</var>
</vars>
In the embodiment of the application, the general text of the vehicle level can be sorted out, the corresponding fault variable of the vehicle level is defined, and the first relation mapping table of the general text of the vehicle level and the fault variable of the vehicle level is established, so that texts possibly used by each ECU are uniformly described through the fault variable of the vehicle level when the text of the subsequent fault code is converted, the repeated occurrence of the subsequent redundant description information is reduced, and the storage efficiency of the fault code information is improved.
Optionally, the general text further includes an ECU-level general text, where the ECU-level general text is a text that is common to all fault code texts corresponding to a single ECU; step S202 described above further includes:
The universal text also comprises ECU-level universal text, wherein the ECU-level universal text is a text which is universal in the fault code text corresponding to a single ECU;
correspondingly, the step S203 further includes:
And determining an ECU level fault variable corresponding to each ECU level universal text, and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable.
In the embodiment of the application, the ECU-level universal text is a text which appears at least twice in each fault code text corresponding to the same ECU. Specifically, for each ECU of a vehicle, the fault code text belonging to the ECU is respectively sorted, and the ECU-level general text corresponding to each ECU is determined.
In some embodiments, the text repeated in the fault code text of the ECU is determined as the ECU-level general text separately for each ECU, in addition to the vehicle-level general text, specifically after the vehicle-level general text.
The ECU-level general text is typically part identification information for the part that the ECU is responsible for managing. Illustratively, in the fault code text shown above, for the ECU named engine1, the corresponding ECU-level general text includes: "cylinderbank 1", "cylinderbank 2"; for an ECU named engine2, its corresponding ECU-level generic text includes: "cylinderbank 3", "cylinderbank 4".
After the ECU level general texts corresponding to the ECUs are determined, corresponding ECU level fault variables are defined for the ECU level general texts, and corresponding relations between the ECU level general texts and the corresponding ECU level fault variables are established to obtain a second relation mapping table.
Illustratively, according to the above-determined ECU-level general text, the second relationship map established for the ECU named engine1 may be as shown in table 3 below.
Table 3:
| ECU level fault variable | ECU-level general text |
| cb1 | cylinder bank 1 |
| cb2 | cylinder bank 2 |
The second relationship map established for the ECU named engine2 may be as shown in table 4 below.
Table 4:
The second relationship mapping table may also be represented in XML format data. For example, the second relation map in XML format corresponding to ECU of engine1 is as follows:
<vars>
<var name＝"cb1">cylinder bank 1</var>
<var name＝"cb2">cylinder bank 2</var>
</vars>
The second relation mapping table in XML format corresponding to ECU of engine2 is as follows:
<vars>
<var name＝"cb3">cylinder bank 3</var>
<var name＝"cb4">cylinder bank 4</var>
</vars>
In the embodiment of the application, besides determining the fault variable vehicle level fault variable, the corresponding ECU level fault variable is determined for each ECU, so that the text repeatedly appearing in the same subsequent ECU can be replaced by a variable reference mode, redundant information in the fault information of the same ECU can be reduced, and the fault information storage efficiency is improved.
Optionally, step S206 described above includes:
According to the first relation mapping table and the second relation mapping table, converting the vehicle-level general text in the fault code text into corresponding vehicle-level fault variables, and converting the ECU-level general text in the fault code text into corresponding ECU-level fault variables to form target fault code information;
And if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
In the embodiment of the application, after the first relation mapping table and the second relation mapping table are determined, if a vehicle-level general text exists in the fault code text acquired later, the vehicle-level general text is converted into a corresponding vehicle-level fault variable, and if the ECU-level general text exists, the ECU-level general text is converted into a corresponding ECU-level fault variable.
Specifically, if there is a general text that is both a vehicle-level general text and an ECU-level general text in one fault text, the general text is preferentially converted into an ECU-level fault variable. For example, if the trouble code text includes the general text "1234567", which is both the vehicle-level general text and the ECU-level general text, the corresponding vehicle-level trouble variable a1 is included in the first relationship map, and the corresponding ECU-level trouble variable a2 is included in the second relationship map. Then the general text "1234567" in the failure text is replaced with the ECU-level failure variable a2 preferentially at this time.
Illustratively, according to the first relationship mapping table and the second relationship mapping table of the above examples, the fault code text of the above examples may be converted into the data after the corresponding target description information as follows:
Therefore, through the vehicle-level fault variable and the ECU-level fault variable, repeated redundant description information in the fault code text can be orderly replaced and expressed in a variable reference mode, so that ordered target fault information with smaller data size is obtained, the original fault code text is replaced by storing the target fault information to store the fault information, the storage efficiency of the fault information can be improved, and the storage space is saved.
Optionally, after the step S103 or the step S206, the method further includes:
Acquiring a fault code information modification request;
and modifying the general text in the relation mapping table according to the fault code information modification request.
In the embodiment of the application, when the general text needing to be modified exists in the stored original text of the fault code, a user (the user can be a vehicle owner, a maintenance person or a communication equipment manager) operates the communication equipment to generate a fault code information modification request, or the fault code information modification request is sent to the communication equipment through a user terminal. The communication device obtains the fault code information modification request by obtaining operation information of a user or receiving information sent by a user terminal.
In one embodiment, the fault code information modification request contains name information of a target fault variable (i.e., a fault variable to be modified) and target generic text (i.e., modified generic text). After the fault code information modification request is obtained, the target fault variable can be searched from the relation mapping table according to the name information of the target fault variable, and the general text corresponding to the target fault variable in the relation mapping table is modified into the target general text.
In another embodiment, the trouble code modification request contains the generic text to be modified and the corresponding target generic text. After the fault code information modification request is obtained, searching a universal text matched with the universal text to be modified from universal texts corresponding to each fault variable contained in the relation mapping table (the fault variable corresponding to the matched text is the target fault variable), and modifying the universal text into the target universal text.
In the embodiment of the application, when the universal text needing to be modified exists, the universal text corresponding to the target fault variable in the relation mapping table is uniformly modified according to the fault code modification request, so that the fault code text is uniformly updated along with the updating of the relation mapping table, and compared with the original mode of modifying the universal text of each fault code in each fault code text one by one, the fault code information modification efficiency can be improved.
Optionally, after the step S103 or the step S206, the method further includes:
Acquiring a fault variable increasing request;
according to the fault variable increasing request, a new fault variable is added in the relation mapping table and the target fault code information; wherein the new fault variable is different from other fault variables of the same level.
In the embodiment of the application, after the target fault code information is stored, the fault variable adding request can be continuously acquired, a new fault variable is added in the relation mapping table, and the new fault variable is referenced in the corresponding target fault code information.
When a new fault variable is added, the communication device needs to determine the name of the new fault variable, which needs to be different from the names of other fault variables in the same level. For example, if there is only one level of fault variable in the relationship mapping table, the name of the new fault variable needs to be different from the names of other defined fault variables. If the relationship mapping table includes the first relationship mapping table and the second relationship mapping table, and the vehicle level fault variable and the ECU level fault variable exist, when the new fault variable is the vehicle level fault variable, the name of the new fault variable needs to be different from the names of other vehicle level fault variables defined in the first relationship mapping table; when the new fault variable is an ECU-level fault variable, the name of the new fault variable needs to be different from the names of other ECU-level fault variables that have been defined in the second relationship map.
In the embodiment of the application, after the target fault code information is stored, new fault variables can be continuously added in the relation mapping table and the target fault code information according to the fault variable adding request, so that the flexibility and expansibility of fault code information storage can be improved.
Optionally, after the step S104 or the step S206, the method further includes:
Acquiring a fault code information inquiry request, wherein the fault code information inquiry request comprises a fault code to be inquired;
determining the target fault code information corresponding to the fault code to be queried according to the fault code to be queried;
And analyzing the target fault code information corresponding to the fault code to be queried according to the relation mapping table to obtain fault content corresponding to the fault code to be queried.
After the target trouble code information is stored, a trouble code information query request may be acquired. The trouble code information inquiry request is a request generated by a user operating the communication device or a request sent to the communication device by the user through the user terminal. The fault code information query request includes a fault code to be queried, such as "P001674".
And then, inquiring the matched target fault code information according to the fault code to be inquired. For example, if the fault code to be queried is "P001664", the query target fault code information is < dtc > P001664% p1% (% cb 1%)% s1% >% s2% > </dtc >
And then, acquiring universal texts corresponding to fault variables p1, cb1, s1 and s2 of the target fault code information from a preset relation mapping table, and sequentially combining the universal texts to analyze the target fault code information, so that fault content ："The position of the intake camshaft(cylinder bank 1)is implausible relative to the position of the crankshaft.There is an implausible signal.". corresponding to the fault code to be queried is obtained.
Optionally, the analyzing the target fault code information corresponding to the fault code to be queried according to the relation mapping table to obtain the fault content corresponding to the fault code to be queried includes:
according to a preset reference symbol (for example%), sequentially determining each fault variable (called as a fault variable to be queried for short) in target fault code information corresponding to the fault code to be queried;
Preferentially searching in a second relation mapping table, and if the ECU level fault variable consistent with the fault variable to be queried is searched, directly acquiring a universal text corresponding to the ECU level fault variable as a text corresponding to the fault variable to be queried; otherwise, searching from the first relation mapping table, and obtaining a general text corresponding to the vehicle level fault variable consistent with the fault variable to be queried, wherein the general text is used as the text corresponding to the fault variable to be queried;
and combining texts corresponding to the fault variables to be queried in sequence to obtain fault contents corresponding to the fault codes to be queried.
Through the analysis method, the text of each fault variable to be queried can be accurately acquired in sequence, and the fault content corresponding to the fault code to be queried can be accurately acquired.
In the embodiment of the application, after the target fault information is stored, when the fault code information query request is acquired, the fault content corresponding to the fault code to be queried can be accurately combined and restored according to the relation mapping table, namely, the fault code text in the original fault code data is not required to be stored one by one, and the fault content corresponding to the fault code can be restored according to the target code information with smaller data quantity, so that the accuracy of the fault code information query can be ensured on the premise of saving the storage space.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
Embodiment III:
fig. 3 is a schematic structural diagram of a fault code information storage device according to an embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown:
The fault code information storage device includes: an acquisition module 31, a conversion module 32, and a storage module 33.
Wherein:
The obtaining module 31 is configured to obtain a fault code text, where the fault code text includes a general text of a fault.
The conversion module 32 is configured to convert the general text in the fault code text into a corresponding fault variable according to a preset relation mapping table of the general text and the fault variable, so as to form target fault code information.
And a storage module 33, configured to store the target fault code information.
Optionally, the fault code information storage device further includes:
The collecting module is used for collecting all fault code texts of the vehicle;
The extraction module is used for extracting the universal text according to all the fault code texts, wherein the universal text is a text which is universal in at least a preset number of fault code texts;
and the relation mapping table establishing module is used for determining the fault variable corresponding to each universal text and establishing the relation mapping table of the universal text and the fault variable.
Optionally, the general text includes a vehicle-level general text, where the vehicle-level general text is a text that is common to all fault code texts corresponding to at least two ECUs of the same vehicle;
the extraction module comprises:
The first extraction unit is used for extracting the vehicle-level universal text according to all the fault code texts;
the relation mapping table building module comprises:
And the first relation mapping table establishing unit is used for determining a vehicle-level fault variable corresponding to each vehicle-level general text and establishing a first relation mapping table of the vehicle-level general text and the vehicle-level fault variable.
Optionally, the general text further includes an ECU-level general text, where the ECU-level general text is a text that is common to all fault code texts corresponding to a single ECU;
The extraction module further comprises:
The second extraction unit is used for extracting the ECU-level universal text according to all the fault code texts;
The relation mapping table establishing module further comprises:
And the second relation mapping table establishing unit is used for determining the ECU level fault variable corresponding to each ECU level universal text and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable.
Optionally, the conversion module is specifically configured to convert the vehicle-level general text in the fault code text into a corresponding vehicle-level fault variable according to the first relationship mapping table and the second relationship mapping table, and convert the ECU-level general text in the fault code text into a corresponding ECU-level fault variable, so as to form target fault code information; and if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
Optionally, the fault code information storage device further includes:
The modifying unit is used for acquiring the fault code information modifying request; and modifying the general text in the relation mapping table according to the fault code information modification request.
Optionally, the fault code information storage device further includes:
The adding unit is used for obtaining the fault code information modification request; and modifying the general text in the relation mapping table according to the fault code information modification request.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.
Embodiment four:
Fig. 4 is a schematic diagram of a communication device according to an embodiment of the present application. As shown in fig. 4, the communication device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42, such as a fault code information storage program, stored in the memory 41 and executable on the processor 40. The steps in the above-described respective fault code information storage method embodiments, such as steps S101 to S103 shown in fig. 1, are implemented when the processor 40 executes the computer program 42. Or the processor 40, when executing the computer program 42, performs the functions of the modules/units in the above-described device embodiments, such as the functions of the data acquisition module 31 to the storage module 33 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing the specified functions describing the execution of the computer program 42 in the communication device 4.
The communication device may include, but is not limited to, a processor 40, a memory 41. It will be appreciated by those skilled in the art that fig. 4 is merely an example of communication device 4 and is not intended to limit communication device 4, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., the communication device may further include an input-output device, a network access device, a bus, etc.
The Processor 40 may be a central processing unit (Central Processing Unit, CPU), other general purpose Processor, digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the communication device 4, such as a hard disk or a memory of the communication device 4. The memory 41 may also be an external storage device of the communication device 4, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like, which are provided on the communication device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the communication device 4. The memory 41 is used for storing the computer program as well as other programs and data required by the communication device. The memory 41 may also be used for temporarily storing data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/communication device and method may be implemented in other manners. For example, the apparatus/communication device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (6)
1. A fault code information storage method, comprising:
Collecting all fault code texts of the vehicle;
Extracting universal texts according to all the fault code texts, wherein the universal texts are at least preset numbers of texts universal in the fault code texts;
determining a fault variable corresponding to each universal text, and establishing a relation mapping table of the universal text and the fault variable;
Acquiring a fault code text, wherein the fault code text comprises a general text of a fault;
Converting the universal text in the fault code text into a corresponding fault variable according to a preset relation mapping table of the universal text and the fault variable to form target fault code information;
Storing the target fault code information;
the general text comprises a vehicle-level general text, and the vehicle-level general text is a text which is general in the fault code texts corresponding to at least two ECUs of the same vehicle; after all fault code texts are obtained, arranging texts which are common to most of ECUs of the vehicle, and taking the texts as vehicle-level common texts;
and extracting the universal text according to all the fault code texts, wherein the extracting comprises the following steps:
extracting the vehicle-level general text according to the fault code texts;
correspondingly, the determining the fault variable corresponding to each universal text and establishing a relation mapping table of the universal text and the fault variable comprises the following steps:
Determining a vehicle-level fault variable corresponding to each vehicle-level general text, and establishing a first relation mapping table of the vehicle-level general text and the vehicle-level fault variable;
The universal text also comprises ECU-level universal text, wherein the ECU-level universal text is a text which is universal in the fault code texts corresponding to a single ECU and is a text which at least appears twice in each fault code text corresponding to the same ECU; for each ECU of a vehicle, respectively sorting fault code texts belonging to the ECU, and determining ECU-level universal texts corresponding to each ECU;
The extracting the universal text according to the all fault code texts further comprises:
Extracting the ECU-level universal text according to the all fault code texts;
Correspondingly, the determining the fault variable corresponding to each universal text, and establishing a relation mapping table between the universal text and the fault variable, further includes:
Determining an ECU level fault variable corresponding to each ECU level universal text, and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable;
The method for converting the universal text in the fault code text into the corresponding fault variable according to the preset relation mapping table of the universal text and the fault variable to form target fault code information comprises the following steps:
According to the first relation mapping table and the second relation mapping table, converting the vehicle-level general text in the fault code text into corresponding vehicle-level fault variables, and converting the ECU-level general text in the fault code text into corresponding ECU-level fault variables to form target fault code information;
And if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
2. The fault code information storage method as claimed in claim 1, further comprising, after said storing said target fault code information:
Acquiring a fault code information modification request;
and modifying the general text in the relation mapping table according to the fault code information modification request.
3. The fault code information storage method as claimed in any one of claims 1 to 2, further comprising, after said storing said target fault code information:
Acquiring a fault variable increasing request;
according to the fault variable increasing request, a new fault variable is added in the relation mapping table and the target fault code information; wherein the new fault variable is different from other fault variables of the same level.
4. A fault code information storage device, comprising:
The mapping table building module is used for collecting all fault code texts of the vehicle; extracting universal texts according to all the fault code texts, wherein the universal texts are at least preset numbers of texts universal in the fault code texts; determining a fault variable corresponding to each universal text, and establishing a relation mapping table of the universal text and the fault variable;
The acquisition module is used for acquiring fault code texts, wherein the fault code texts comprise fault universal texts;
the conversion module is used for converting the universal text in the fault code text into the corresponding fault variable according to a preset relation mapping table of the universal text and the fault variable to form target fault code information;
The storage module is used for storing the target fault code information;
the general text comprises a vehicle-level general text, and the vehicle-level general text is a text which is general in the fault code texts corresponding to at least two ECUs of the same vehicle; after all fault code texts are obtained, arranging texts which are common to most of ECUs of the vehicle, and taking the texts as vehicle-level common texts;
and extracting the universal text according to all the fault code texts, wherein the extracting comprises the following steps:
extracting the vehicle-level general text according to the fault code texts;
correspondingly, the determining the fault variable corresponding to each universal text and establishing a relation mapping table of the universal text and the fault variable comprises the following steps:
Determining a vehicle-level fault variable corresponding to each vehicle-level general text, and establishing a first relation mapping table of the vehicle-level general text and the vehicle-level fault variable;
The universal text also comprises ECU-level universal text, wherein the ECU-level universal text is a text which is universal in the fault code texts corresponding to a single ECU and is a text which at least appears twice in each fault code text corresponding to the same ECU; for each ECU of a vehicle, respectively sorting fault code texts belonging to the ECU, and determining ECU-level universal texts corresponding to each ECU;
The extracting the universal text according to the all fault code texts further comprises:
Extracting the ECU-level universal text according to the all fault code texts;
Correspondingly, the determining the fault variable corresponding to each universal text, and establishing a relation mapping table between the universal text and the fault variable, further includes:
Determining an ECU level fault variable corresponding to each ECU level universal text, and establishing a second relation mapping table of the ECU level universal text and the ECU level fault variable;
The method for converting the universal text in the fault code text into the corresponding fault variable according to the preset relation mapping table of the universal text and the fault variable to form target fault code information comprises the following steps:
According to the first relation mapping table and the second relation mapping table, converting the vehicle-level general text in the fault code text into corresponding vehicle-level fault variables, and converting the ECU-level general text in the fault code text into corresponding ECU-level fault variables to form target fault code information;
And if the fault code text comprises a general text which is not only the vehicle-level general text but also the ECU-level general text, preferentially converting the fault code text into the ECU-level fault variable.
5. A communication device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the computer program, when executed by the processor, causes the communication device to carry out the steps of the method according to any one of claims 1 to 3.
6. A computer readable storage medium storing a computer program, which, when executed by a processor, causes a communication device to carry out the steps of the method according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110699354.XA CN113535881B (en) | 2021-06-23 | 2021-06-23 | Fault code information storage method, device, communication equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110699354.XA CN113535881B (en) | 2021-06-23 | 2021-06-23 | Fault code information storage method, device, communication equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535881A CN113535881A (en) | 2021-10-22 |
| CN113535881B true CN113535881B (en) | 2024-07-12 |
Family
ID=78096505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110699354.XA Active CN113535881B (en) | 2021-06-23 | 2021-06-23 | Fault code information storage method, device, communication equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535881B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708353A (en) * | 2020-06-30 | 2020-09-25 | 深圳市元征科技股份有限公司 | Data display method and system for vehicle diagnosis equipment and related equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9665994B1 (en) * | 2015-11-11 | 2017-05-30 | Snap-On Incorporated | Methods and systems for providing a vehicle repair tip |
| US10331687B2 (en) * | 2017-08-10 | 2019-06-25 | Snap-On Incorporated | System and method for accessing vehicle communication applications requiring vehicle identification without re-entering vehicle identification |
| US11210434B2 (en) * | 2017-10-17 | 2021-12-28 | Textron Innovations Inc. | Fault isolation |
| US11024102B2 (en) * | 2018-05-10 | 2021-06-01 | Mahle International Gmbh | Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling |
| CN112684779B (en) * | 2020-12-25 | 2022-07-05 | 长城汽车股份有限公司 | Vehicle fault detection method, system, storage medium and electronic device |
| CN112732982B (en) * | 2021-01-18 | 2024-09-10 | 深圳市元征科技股份有限公司 | Fault code storage method and device, terminal equipment and readable storage medium |
-
2021
- 2021-06-23 CN CN202110699354.XA patent/CN113535881B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708353A (en) * | 2020-06-30 | 2020-09-25 | 深圳市元征科技股份有限公司 | Data display method and system for vehicle diagnosis equipment and related equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535881A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113010116B (en) | Data processing method, device, terminal equipment and readable storage medium | |
| CN107368500B (en) | Data extraction method and system | |
| CN113535881B (en) | Fault code information storage method, device, communication equipment and storage medium | |
| CN104750814B (en) | The automatic storage method of polynary heterogeneous data flow based on multisensor | |
| CN117880060A (en) | Network operation and maintenance method, system, equipment and medium based on rule engine | |
| CN112445816B (en) | Vehicle diagnosis data reference method, device, terminal equipment and storage medium | |
| CN112445797B (en) | Vehicle diagnosis data reference method, device, terminal equipment and storage medium | |
| CN113342430B (en) | Fault code processing method and device, terminal equipment and readable storage medium | |
| CN110737707A (en) | Multi-system log searching method and device and computer readable storage medium | |
| CN114756585A (en) | Vehicle data acquisition method and device, electronic equipment and storage medium | |
| CN111309623B (en) | Coordinate class data classification test method and device | |
| CN114547011A (en) | Data extraction method and device, electronic equipment and storage medium | |
| CN115729752A (en) | Register checking method and device and storage medium | |
| CN112859805A (en) | Engine controller online diagnosis method and related device | |
| CN112445491B (en) | File sequence processing method, device, terminal equipment and storage medium | |
| CN112990466A (en) | Redundancy rule detection method and device and server | |
| CN111581207B (en) | File generation method and device of Azkaban project and terminal equipment | |
| CN113572628A (en) | Data association method and device, computing equipment and computer storage medium | |
| CN112104766B (en) | Diagnostic protocol reconstruction method, device, terminal equipment and storage medium | |
| CN116303404B (en) | Big data storage system for preventing data redundancy based on data classification and peer comparison | |
| CN113033832B (en) | Method and device for inputting automobile repair data, terminal equipment and readable storage medium | |
| CN116431677B (en) | Data routing method, system and readable storage medium based on memory database | |
| CN116185835A (en) | Relay protection device testing method and device, electronic device and storage medium | |
| CN111596641B (en) | Fault analysis method and device, storage medium and equipment for emergency diesel engine of nuclear power station | |
| CN115357655A (en) | Method and device for automatically integrating change information, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20221014 Address after: 518000 Guangdong province Shenzhen Longgang District Bantian Street five and Avenue North 4012 Yuan Zheng Industrial Park. Applicant after: LAUNCH TECH Co.,Ltd. Address before: 518000 522, headquarters office building of Yuanzheng technology plant, No. 4012, North Wuhe Avenue, Bantian street, Longgang District, Shenzhen, Guangdong Province Applicant before: Shenzhen Yuanzheng Future Automobile Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |