CN116501016A - Vehicle fault code setting method, vehicle-mounted terminal and medium - Google Patents

Vehicle fault code setting method, vehicle-mounted terminal and medium Download PDF

Info

Publication number
CN116501016A
CN116501016A CN202310483667.0A CN202310483667A CN116501016A CN 116501016 A CN116501016 A CN 116501016A CN 202310483667 A CN202310483667 A CN 202310483667A CN 116501016 A CN116501016 A CN 116501016A
Authority
CN
China
Prior art keywords
fault
vehicle
driving cycle
code
code information
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.)
Pending
Application number
CN202310483667.0A
Other languages
Chinese (zh)
Inventor
魏英英
葛张成
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Great Wall Motor Co Ltd
Original Assignee
Great Wall Motor Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Great Wall Motor Co Ltd filed Critical Great Wall Motor Co Ltd
Priority to CN202310483667.0A priority Critical patent/CN116501016A/en
Publication of CN116501016A publication Critical patent/CN116501016A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0262—Confirmation of fault detection, e.g. extra checks to confirm that a failure has indeed occurred
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24065—Real time diagnostics
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T10/00—Road transport of goods or passengers
    • Y02T10/10—Internal combustion engine [ICE] based vehicles
    • Y02T10/40—Engine management systems

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Electric Propulsion And Braking For Vehicles (AREA)

Abstract

The application is applicable to the technical field of automobiles, and provides a fault code setting method, a vehicle-mounted terminal and a medium for a vehicle, wherein the method comprises the following steps: when detecting that the vehicle has a fault in the current driving cycle, acquiring fault diagnosis code information corresponding to the fault; and setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information. Compared with the prior art that the same fault is detected in two continuous driving cycles of the vehicle and the fault confirming fault code is stored, the method provided by the application can set the fault confirming fault code in the fault diagnosis code information of the fault to be in a valid state as long as the fault is detected in the current driving cycle of the vehicle, and store the modified fault diagnosis code information, so that the fault confirming fault code is read when the vehicle is subsequently maintained, and the vehicle is correspondingly maintained according to the fault.

Description

Vehicle fault code setting method, vehicle-mounted terminal and medium
Technical Field
The application belongs to the technical field of automobiles, and particularly relates to a fault code setting method of a vehicle, a vehicle-mounted terminal and a medium.
Background
The vehicle-mounted automatic diagnosis system (On Board Diagnostic, OBD) can monitor whether the automobile exhaust exceeds the standard at any time according to the running condition of the engine, and can immediately give out an alarm once the automobile exhaust exceeds the standard. When the OBD system fails, a fault indicator or engine warning light will light up, and the powertrain control module stores fault information into the memory. According to the prompt of the fault code, maintenance personnel can quickly and accurately determine the nature and the position of the fault.
The prior art generally follows the relevant requirements of OBD in that a fault-confirming fault code is stored after the same fault is detected for two consecutive driving cycles of the vehicle. However, in practice there are some faults, which are detected in the current driving cycle of the vehicle, but which are repaired in the next driving cycle of the vehicle, so that the confirmed fault code of the fault is not stored. Therefore, when the vehicle is required to be maintained later, the fault confirmation code of the fault cannot be read, so that the fault position and the fault reason of the fault cannot be determined, and the vehicle is difficult to maintain accurately.
Disclosure of Invention
The embodiment of the application provides a fault code setting method, a vehicle-mounted terminal and a medium for a vehicle, and the fault code setting method, the vehicle-mounted terminal and the medium can store a fault code for confirming the fault even if the fault is repaired in the next driving cycle of the vehicle, so that a vehicle maintenance person can accurately maintain the vehicle.
In a first aspect, an embodiment of the present application provides a method for setting a fault code of a vehicle, including:
when detecting that a fault occurs in the vehicle in the current driving cycle, acquiring fault diagnosis code information corresponding to the fault;
and setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information.
Optionally, the setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information includes:
acquiring the fault identification;
and if the identification exists in a preset fault identification table, setting the confirmed fault code in the fault diagnosis code information to be in an effective state in the current driving cycle according to unified diagnosis service, and storing the fault diagnosis code information.
Optionally, after obtaining the identification of the fault, the method further includes:
if the identification is not in the fault identification table, detecting whether the fault occurs in the vehicle in the driving cycle which is the last to the current driving cycle;
If the vehicle fails in the previous driving cycle, setting a confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to a vehicle-mounted automatic diagnosis system, and storing the fault diagnosis code information;
and if the vehicle does not generate the fault in the last driving cycle, setting a pending fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to an on-board automatic diagnosis system, and storing the fault diagnosis code information.
Optionally, the detecting whether the failure occurs in the vehicle in the driving cycle previous to the current driving cycle includes:
if the pending fault code in the fault diagnosis code information is in a valid state in the last driving cycle, determining that the fault occurs in the last driving cycle;
and if the pending fault code in the fault diagnosis code information is in an invalid state in the last driving cycle, determining that the fault does not occur in the last driving cycle.
Optionally, the fault identification table is used for storing faults of the set identification; wherein the set identifier is used to characterize the type of fault as an sporadic fault, and the vehicle generates a fault response when the fault is detected.
Optionally, when detecting that the vehicle has a fault in the current driving cycle, after obtaining the fault diagnosis code information corresponding to the fault, the method further includes:
detecting whether the vehicle has failed in a driving cycle previous to the current driving cycle;
if the vehicle has the fault in the previous driving cycle, setting a confirmed fault code in the fault diagnosis code information in the current driving cycle to be in a valid state according to a vehicle-mounted automatic diagnosis system, and storing the fault diagnosis code information;
correspondingly, according to the unified diagnosis service, setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle, and storing the fault diagnosis code information comprises:
and if the vehicle does not generate the fault in the driving cycle which is the last driving cycle of the current driving cycle, setting the confirmed fault code in the fault diagnosis code information into a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information.
Optionally, the setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information includes:
And setting a bit value of a designated position in the fault diagnosis code information to a designated numerical value in the current driving cycle according to the unified diagnosis service so as to enable the confirmed fault code to be in a valid state.
Optionally, after the setting the confirmed fault code in the fault diagnosis code information to a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information, the method further includes:
recording the number of times that the confirmed fault code in the fault diagnosis code information corresponding to the fault is set to be in an effective state in the running process of the vehicle;
determining the fault level of the fault according to the times;
and executing setting operation corresponding to the fault level.
In a second aspect, an embodiment of the present application provides a fault code setting device for a vehicle, including:
the first acquisition unit is used for acquiring fault diagnosis code information corresponding to a fault when the fault of the vehicle in the current driving cycle is detected;
and the first setting unit is used for setting the confirmed fault code in the fault diagnosis code information into a valid state in the current driving cycle according to the unified diagnosis service and storing the fault diagnosis code information.
In a third aspect, an embodiment of the present application provides a vehicle-mounted terminal, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the fault code setting method according to any one of the first aspects when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, which when executed by a processor implements the fault code setting method according to any one of the first aspects above.
In a fifth aspect, embodiments of the present application provide a computer program product, which when run on a vehicle-mounted terminal, enables the vehicle-mounted terminal to perform the fault code setting method of any one of the above first aspects.
Compared with the prior art, the embodiment of the application has the beneficial effects that:
according to the fault code setting method for the vehicle, when the fault of the vehicle in the current driving cycle is detected, fault diagnosis code information corresponding to the fault is obtained; and setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information. Compared with the prior art that the same fault is required to be detected in two continuous driving cycles of the vehicle and the fault confirming fault code of the fault is stored, the method provided by the invention has the advantages that the fault confirming fault code in the fault diagnosis code information of the fault can be set to be in a valid state only when the fault occurs in the current driving cycle of the vehicle, and the modified fault diagnosis code information is stored, so that the fault confirming fault code can be stored even if a fault is repaired in the next driving cycle of the vehicle, and the fault confirming fault code of the fault can be read when the vehicle is repaired later, so that the vehicle can be accurately repaired according to the fault.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method for setting a fault code of a vehicle according to an embodiment of the present application;
FIG. 2 is a flowchart of an implementation of a method for setting a fault code of a vehicle according to another embodiment of the present application;
FIG. 3 is a flowchart of an implementation of a method for setting a fault code of a vehicle according to still another embodiment of the present application;
FIG. 4 is a flowchart of an implementation of a method for setting a fault code of a vehicle according to another embodiment of the present application;
fig. 5 is a schematic structural view of a fault code setting device for a vehicle according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a vehicle-mounted terminal 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 particular system configurations, 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.
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 should also be understood that the term "and/or" as used in this 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 and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
In the practical application of the present invention,
referring to fig. 1, fig. 1 is a flowchart illustrating an implementation of a fault code setting method for a vehicle according to an embodiment of the present application. In this embodiment of the present application, the execution main body of the fault code setting method of the vehicle is a vehicle-mounted terminal.
As shown in fig. 1, the method for setting a fault code of a vehicle according to an embodiment of the present application may include S101 to S102, which are described in detail below:
In S101, when it is detected that the vehicle is faulty in the current driving cycle, fault diagnosis code information corresponding to the fault is acquired.
In the embodiment of the application, when the vehicle-mounted terminal detects the fault signal, it can be determined that the fault of the vehicle occurs in the current driving cycle.
In one implementation manner of the embodiment of the present application, the vehicle is provided with a fault indicator (such as an engine fault lamp, an engine oil system fault lamp, and a battery fault lamp, etc.), so when the vehicle-mounted terminal detects that the fault indicator is turned on, it indicates that a fault signal is detected, that is, that the vehicle is faulty in the current driving cycle.
In practice, a driving cycle refers to the complete process of the vehicle completing ignition, running (should a vehicle malfunction be detected), and flameout.
The current driving cycle refers to the driving cycle of the vehicle when the vehicle terminal detects that the vehicle is in fault.
In the embodiment of the application, when detecting that the vehicle breaks down in the current driving cycle, the vehicle-mounted terminal can acquire the fault diagnosis code information corresponding to the fault.
In one implementation manner of the embodiment of the present application, the vehicle-mounted terminal may obtain, in real time, the fault diagnosis code information corresponding to the fault through the vehicle-mounted server/server group connected with the vehicle-mounted terminal in a wireless communication manner.
Specifically, the in-vehicle terminal may request the 0×19 service from the in-vehicle server, and after detecting that the in-vehicle terminal requests the 0×19 service, the in-vehicle server may transmit the fault diagnosis code information corresponding to the fault to the in-vehicle terminal, and the in-vehicle terminal may receive the fault diagnosis code information.
In practical applications, a 0 x 19 service is used to read fault diagnosis code information (Read DTC Information).
The fault diagnosis code information is composed of eight fault diagnosis code (Diagnostic Trouble Code, DTC) status bits. Referring to table 1, table 1 is an example of a fault diagnosis code status bit configuration table provided in the embodiments of the present application.
TABLE 1
Based on this, the in-vehicle terminal can determine the number of bits of the confirmation fault code in the fault diagnosis code information.
In S102, according to the unified diagnostic service, the confirmed fault code in the fault diagnosis code information is set to a valid state in the current driving cycle, and the fault diagnosis code information is stored.
In practical application, since the on-board automatic diagnosis system (On Board Diagnostic, OBD) is required to comply with relevant regulations in the light vehicle pollutant emission limit and measurement method (sixth stage of china), that is, the fault identification code is stored only after two continuous driving cycles of the vehicle detect the same fault, in this embodiment of the present application, after detecting that the vehicle has a fault in the current driving cycle, the on-board terminal may use the unified diagnosis service (Unified Diagnostic Services, UDS) to set the fault identification code in the obtained fault diagnosis code information to be in a valid state in the current driving cycle, thereby completing updating the fault diagnosis code information and storing the updated fault diagnosis code.
It should be noted that, whether or not a fault occurs in two consecutive driving cycles of the vehicle, that is, when the vehicle-mounted terminal detects that the vehicle has not failed in the previous driving cycle of the current driving cycle, the confirmation fault code in the above fault diagnosis code information may still be set to a valid state in the current driving cycle according to the unified diagnostic service, and the fault diagnosis code information may be stored.
In the embodiment of the application, the state of the confirmed fault code comprises a valid state and an invalid state. Wherein the active state is for describing that the fault code of the fault is confirmed and the inactive state is for describing that the fault code of the fault is not confirmed.
Based on this, in connection with table 1, the status of the validation fault code may be represented by a number, illustratively, a number "0" representing an invalid status and a number "1" representing a valid status.
In practical applications, the unified diagnostic service is a diagnostic communication protocol in the context of an automotive electronic control unit (Electronic Control Unit, ECU).
In one embodiment of the present application, since the fault diagnosis code information is composed of eight fault diagnosis code (Diagnostic Trouble Code, DTC) status bits, the in-vehicle terminal may set a bit value (i.e., a status bit) of a specified position of the fault diagnosis code information to a specified value at a current driving cycle according to the unified diagnosis service, so that the above-mentioned confirmed fault code is in a valid state.
In connection with table 1, the designated position may be a position where Bit number 3 is located, and the designated value may be a value of 1.
As can be seen from the above, according to the method for setting the fault code of the vehicle provided by the embodiment of the application, when the fault of the vehicle in the current driving cycle is detected, fault diagnosis code information corresponding to the fault is obtained; and setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information. Compared with the prior art that the same fault is required to be detected in two continuous driving cycles of the vehicle and the fault confirming fault code of the fault is stored, the method provided by the invention has the advantages that the fault confirming fault code in the fault diagnosis code information of the fault can be set to be in a valid state only when the fault occurs in the current driving cycle of the vehicle, and the modified fault diagnosis code information is stored, so that the fault confirming fault code can be stored even if a fault is repaired in the next driving cycle of the vehicle, and the fault confirming fault code of the fault can be read when the vehicle is repaired later, so that the vehicle can be accurately repaired according to the fault.
Referring to fig. 2, fig. 2 is a fault code setting method of a vehicle according to another embodiment of the present application. In contrast to the embodiment corresponding to fig. 1, step S102 in this embodiment may specifically include S201 to S202, which are described in detail below:
in S201, an identification of the fault is obtained.
In this embodiment, in combination with S101, the fault signal detected by the vehicle-mounted terminal carries an identifier of a fault that occurs in the current driving cycle of the vehicle. Wherein the type used to describe the fault is identified.
The vehicle-mounted terminal is provided with a preset fault identification table in advance. The fault identification table is used for storing faults of the set identification. The set identifiers are used for representing the fault type as sporadic faults, and the fault response is generated when the fault is detected by the vehicle.
Based on the above, after the vehicle-mounted terminal obtains the fault identification, the fault identification can be compared with each set identification in the preset fault identification table one by one so as to detect whether the fault identification table has the fault identification.
In one embodiment of the present application, when the in-vehicle terminal detects that the identification of the fault exists in the preset fault identification table, the in-vehicle terminal may execute step S202.
In another embodiment of the present application, when the vehicle terminal detects that the fault identifier is not in the preset fault identifier table, steps S301 to S303 shown in fig. 3 may be specifically executed as follows:
in S301, if the identification is not in the failure identification table, it is detected whether the failure of the vehicle occurs in a driving cycle previous to the current driving cycle.
In this embodiment, when the vehicle-mounted terminal detects that the fault identifier exists in the preset fault identifier table, in order to determine how to set the pending fault code and confirm the fault code in the fault diagnosis code information of the fault, the vehicle-mounted terminal may detect whether the fault occurs in the previous driving cycle of the current driving cycle, that is, determine whether the fault occurs in two consecutive driving cycles.
In practical application, when the vehicle-mounted terminal detects a fault of the vehicle, the vehicle-mounted terminal can set the pending fault code in the fault diagnosis code information corresponding to the fault to be in a valid state in a driving cycle when the fault occurs through the OBD system, and store the pending fault code of the fault, so that before any processing is performed on the fault diagnosis code information corresponding to the fault obtained by the current driving cycle, the vehicle-mounted terminal can determine whether the fault occurs in the last driving cycle by detecting the state in the last driving cycle of the pending fault code in the fault diagnosis code information corresponding to the fault, and based on this, in an embodiment of the present application, the vehicle-mounted terminal can specifically detect whether the vehicle has a fault in the last driving cycle of the current driving cycle through steps S401 to S402 as shown in fig. 4, which are described in detail as follows:
In S401, if a pending fault code in the fault diagnosis code information is in a valid state in the last driving cycle, it is determined that the fault occurs in the last driving cycle.
In S402, if the pending fault code in the fault diagnosis code information is in an invalid state in the previous driving cycle, it is determined that the fault does not occur in the previous driving cycle.
In this embodiment, before any processing is performed on the fault diagnosis code information corresponding to the fault obtained in the current driving cycle, the vehicle-mounted terminal detects that the pending fault code in the obtained fault diagnosis code information is in a valid state in the previous driving cycle, and indicates that the fault has occurred in the previous driving cycle of the vehicle.
Before any processing is performed on fault diagnosis code information corresponding to the fault obtained by the current driving cycle, the vehicle-mounted terminal detects that a pending fault code in the obtained fault diagnosis code information is in an invalid state in the last driving cycle, and indicates that the fault does not occur in the last driving cycle of the vehicle.
According to the method, before any processing is carried out on the fault diagnosis code information corresponding to the fault obtained by the vehicle-mounted terminal in the current driving cycle, whether the fault occurs in the previous driving cycle of the vehicle or not can be determined directly through the state of the pending fault code in the fault diagnosis code information, the operation is simple, whether the fault occurs in the previous driving cycle or not can be judged without obtaining data of other sensors of the vehicle, and the processing efficiency of the vehicle-mounted terminal is improved.
In S302, if the vehicle has failed in the previous driving cycle, the confirmed failure code in the failure diagnosis code information is set to a valid state in the current driving cycle according to an on-board automatic diagnosis system, and the failure diagnosis code information is stored.
In this embodiment, the vehicle-mounted terminal detects that the above-mentioned fault has occurred in the last driving cycle of the vehicle, which means that the fault has occurred in two consecutive driving cycles, and therefore, the vehicle-mounted terminal may set the confirmed fault code in the fault diagnosis code information of the fault to a valid state in the current driving cycle directly through the OBD system, thereby completing updating the fault diagnosis code information and storing the updated fault diagnosis code.
When the confirmed fault code in the fault diagnosis code information of the fault is set to be in a valid state in the current driving cycle, the vehicle-mounted terminal sets the pending fault code in the fault diagnosis code information corresponding to the fault to be in a valid state in the current driving cycle until the fault is not detected in the next driving cycle of the current driving cycle of the vehicle.
In S303, if the vehicle has not failed in the previous driving cycle, the pending failure code in the failure diagnosis code information is set to a valid state in the current driving cycle according to an on-board automatic diagnosis system, and the failure diagnosis code information is stored.
In this embodiment, the vehicle-mounted terminal detects that the above-mentioned fault does not occur in the previous driving cycle of the vehicle, which means that the fault does not occur in two consecutive driving cycles, so that the vehicle-mounted terminal may directly set the confirmed fault code in the fault diagnosis code information of the fault to an invalid state in the current driving cycle through the OBD system, thereby completing updating the fault diagnosis code information and storing the updated fault diagnosis code.
When the vehicle-mounted terminal sets the confirmed fault code in the fault diagnosis code information of the fault to the invalid state in the current driving cycle, the vehicle-mounted terminal may set the state of the pending fault code in the fault diagnosis code information corresponding to the fault from the invalid state to the valid state because the fault does not occur in the previous driving cycle (at this time, the pending fault code in the fault diagnosis code information of the fault is the invalid state) and has occurred in the current driving cycle.
The above can show that when the vehicle-mounted terminal detects that the fault identifier is not in the fault identifier table, the state of the confirmed fault code and the state of the pending fault code in the fault diagnosis code information of the fault can be set in an OBD diagnosis mode, so that the application range of fault diagnosis is expanded.
In S202, if the identifier exists in a preset fault identifier table, the confirmed fault code in the fault diagnosis code information is set to be in a valid state in the current driving cycle according to the unified diagnosis service, and the fault diagnosis code information is stored.
In this embodiment, the vehicle-mounted terminal indicates that the fault meets the requirement when the identifier of the fault is detected to be in the preset fault identifier table, so that the vehicle-mounted terminal can set the confirmed fault code in the obtained fault diagnosis code information to be in a valid state in the current driving cycle by using unified diagnostic service (Unified Diagnostic Services, UDS), thereby completing updating the fault diagnosis code information and storing the updated fault diagnosis code.
As can be seen from the above, in the method for setting a fault code of a vehicle provided in the present embodiment, when detecting that a fault occurs in a vehicle in a current driving cycle, it is further required to obtain an identifier of the fault; and only when the identification is detected to exist in the preset fault identification table, the confirmed fault code in the fault diagnosis code information is set to be in a valid state in the current driving cycle according to the unified diagnosis service, and the fault diagnosis code information is stored, so that the fault which does not exist in the fault identification table is avoided, the vehicle-mounted terminal still uses the unified diagnosis service to set the confirmed fault code in the fault diagnosis code information to be in the valid state, and the workload of the vehicle-mounted terminal is increased.
In another embodiment of the present application, after performing step S101, the vehicle-mounted terminal may further perform the following steps, which are described in detail below:
detecting whether the vehicle has failed in a driving cycle previous to the current driving cycle;
if the vehicle has the fault in the previous driving cycle, setting a confirmed fault code in the fault diagnosis code information in the current driving cycle to be in a valid state according to a vehicle-mounted automatic diagnosis system, and storing the fault diagnosis code information;
and if the vehicle does not generate the fault in the driving cycle which is the last driving cycle of the current driving cycle, setting the confirmed fault code in the fault diagnosis code information into a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information.
In this embodiment, in order to determine the setting mode of the confirmation fault code in the fault diagnosis code information, after the vehicle-mounted terminal obtains the fault diagnosis code information of the fault, the vehicle-mounted terminal may detect whether the fault occurs in the previous driving cycle of the current driving cycle, that is, determine whether the fault occurs in two consecutive driving cycles, so as to determine the setting mode of the confirmation fault code in the fault diagnosis code information.
In practical application, when the vehicle-mounted terminal detects the fault of the vehicle, the vehicle-mounted terminal can set the pending fault code in the fault diagnosis code information corresponding to the fault to be in a valid state in a driving cycle when the fault occurs through the OBD system, and store the pending fault code of the fault, so that before any processing is performed on the fault diagnosis code information corresponding to the fault obtained by the current driving cycle, the vehicle-mounted terminal can determine whether the fault occurs in the previous driving cycle or not by detecting the state of the pending fault code in the fault diagnosis code information corresponding to the fault in the previous driving cycle.
Based on this, the in-vehicle terminal, upon detecting that the above-described failure of the vehicle occurred in the last driving cycle, indicates that the failure has occurred in two consecutive driving cycles, and therefore, the in-vehicle terminal may set the confirmation failure code in the failure diagnosis code information of the current driving cycle to the valid state according to the in-vehicle automatic diagnosis system, and store the updated failure diagnosis code information.
When the vehicle terminal detects that the fault does not occur in the previous driving cycle, the vehicle terminal indicates that the fault does not occur in two continuous driving cycles, so the vehicle terminal can set a confirmation fault code in the fault diagnosis code information of the fault in the current driving cycle to be in a valid state according to the unified diagnosis service, and store the updated fault diagnosis code information.
In still another embodiment of the present application, after performing step S102, the vehicle-mounted terminal may further perform the following steps, which are described in detail below:
recording the number of times that the confirmed fault code in the fault diagnosis code information corresponding to the fault is set to be in an effective state in the running process of the vehicle;
determining the fault level of the fault according to the times;
and executing setting operation corresponding to the fault level.
In this embodiment, when a certain fault frequently occurs during the running of the vehicle, it is indicated that a serious problem occurs in a certain portion of the vehicle, in order to allow the vehicle to be maintained in time and prolong the service life of the vehicle, after executing step S102, the vehicle-mounted terminal may record the number of times that the confirmed fault code in the fault diagnosis code information corresponding to the fault is set to be in an effective state during the running of the vehicle, and compare the number of times with a plurality of preset time thresholds one by one, so as to determine the fault level of the fault according to the comparison result.
In some possible embodiments, if a fault occurs in two consecutive driving cycles of the vehicle, the vehicle-mounted terminal may set the confirmed fault code in the fault diagnosis code information of the fault to a valid state according to the OBD system, that is, at this time, the vehicle-mounted terminal does not need to set the confirmed fault code in the fault diagnosis code information of the fault to a valid state according to the UDS, so, in order to improve the accuracy of the number of times of setting the confirmed fault code in the fault diagnosis code information of the fault to the valid state according to the UDS and the number of times of setting the confirmed fault code in the fault diagnosis code information of the fault to the valid state according to the OBD system, the vehicle-mounted terminal may determine the number of times of setting the recorded as the valid state.
In other possible embodiments, when a vehicle has a fault in any one driving cycle, the vehicle-mounted terminal may set the fault code in the fault diagnosis code information of the fault to a valid state according to the UDS, regardless of whether the fault has occurred in two consecutive driving cycles, so, in order to improve the processing efficiency of the vehicle-mounted terminal, the vehicle-mounted terminal may directly determine, as the number of times of setting the record to the valid state, the number of times of setting the fault code in the fault diagnosis code information of the fault to the valid state according to the UDS without querying the number of times of setting the fault code in the fault diagnosis code information of the fault to the valid state according to the OBD system.
The preset frequency threshold and the fault level can be set according to actual needs, and the preset frequency threshold can comprise a first threshold and a second threshold, and the fault level can comprise a first level, a second level and a third level. Wherein the first threshold is less than the second threshold.
In this embodiment, when the number of times is detected to be less than or equal to the first threshold, the terminal device may determine that the failure level of the failure is a first level, when the number of times is detected to be greater than the first threshold and less than or equal to the second threshold, the terminal device may determine that the failure level of the failure is a second level, and when the number of times is detected to be greater than the second threshold, the terminal device may determine that the failure level of the failure is a third level.
In this embodiment, the vehicle-mounted terminal stores the correspondence between each failure level and each setting operation in advance, so that after determining the failure level of the failure, the vehicle-mounted terminal can determine the setting operation corresponding to the failure level and execute the setting operation.
Wherein the setting operation includes, but is not limited to: and lighting the fault indicator lamp, outputting voice prompt information and the like. The voice prompt information can be that the fault occurs for many times, and the vehicle is required to be maintained in time.
In some possible embodiments, the vehicle-mounted terminal may associate the fault level of the first level with the setting operation of lighting the fault indicator, associate the fault level of the second level with the setting operation of outputting the voice prompt information, and associate the fault level of the third level with the setting operation of lighting the fault indicator and outputting the voice prompt information.
Based on the above, the vehicle-mounted terminal can light the fault indicator lamp when the fault level of the detected fault is the first level, can output voice prompt information when the fault level of the detected fault is the second level, and can light the fault indicator lamp and output voice prompt information when the fault level of the detected fault is the third level.
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 of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Fig. 5 shows a schematic structural diagram of a fault code setting device for a vehicle 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. Referring to fig. 5, the fault code setting device 500 of the vehicle includes: a first acquisition unit 51 and a first setting unit 52. Wherein:
the first obtaining unit 51 is configured to obtain, when detecting that a failure occurs in the vehicle in the current driving cycle, failure diagnosis code information corresponding to the failure.
The first setting unit 52 is configured to set the confirmed fault code in the fault diagnosis code information to a valid state in the current driving cycle according to a unified diagnosis service, and store the fault diagnosis code information.
In one embodiment of the present application, the first setting unit 52 specifically includes: a second acquisition unit and a second setting unit. Wherein:
The second acquisition unit is used for acquiring the identification of the fault.
And the second setting unit is used for setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service if the identification exists in a preset fault identification table, and storing the fault diagnosis code information.
In one embodiment of the present application, the fault code setting device 500 of the vehicle further includes: a first detection unit, a third setting unit and a fourth setting unit. Wherein:
the first detection unit is used for detecting whether the vehicle has the fault in the driving cycle which is the last driving cycle of the current driving cycle if the identification is not in the fault identification table.
And the third setting unit is used for setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the vehicle-mounted automatic diagnosis system and storing the fault diagnosis code information if the fault occurs in the previous driving cycle of the vehicle.
And the fourth setting unit is used for setting the pending fault code in the fault diagnosis code information into a valid state in the current driving cycle according to the vehicle-mounted automatic diagnosis system and storing the fault diagnosis code information if the fault does not occur in the previous driving cycle of the vehicle.
In one embodiment of the present application, the detection unit specifically includes: a first determination unit and a second determination unit. Wherein:
the first determining unit is configured to determine that the vehicle has the fault in the previous driving cycle if a pending fault code in the fault diagnosis code information is in a valid state in the previous driving cycle.
The second determining unit is configured to determine that the failure does not occur in the previous driving cycle of the vehicle if the pending failure code in the failure diagnosis code information is in an invalid state in the previous driving cycle.
In one embodiment of the present application, the fault identification table is used to store faults for setting identification; wherein the set identifier is used to characterize the type of fault as an sporadic fault, and the vehicle generates a fault response when the fault is detected.
In one embodiment of the present application, the fault code setting device 500 of a vehicle includes: the second detecting unit and the fifth setting unit, correspondingly, the first setting unit 52 specifically includes: and a sixth setting unit. Wherein:
the second detection unit is configured to detect whether the failure occurs in a driving cycle previous to the current driving cycle.
And the fifth setting unit is used for setting the confirmed fault code in the fault diagnosis code information in the current driving cycle into a valid state according to an on-board automatic diagnosis system and storing the fault diagnosis code information if the fault occurs in the previous driving cycle of the vehicle.
And the sixth setting unit is used for setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service if the fault does not occur in the driving cycle which is the last driving cycle of the current driving cycle, and storing the fault diagnosis code information.
In one embodiment of the present application, the first setting unit 51 specifically includes: and a seventh setting unit.
And a seventh setting unit is configured to set, according to the unified diagnostic service, a bit value of a specified position in the fault diagnosis code information to a specified value in the current driving cycle, so that the confirmed fault code is in a valid state.
In one embodiment of the present application, the fault code setting device 500 of the vehicle further includes: a recording unit, a third determining unit and an executing unit. Wherein:
the recording unit is used for recording the times of setting the confirmed fault code in the fault diagnosis code information corresponding to the fault to be in an effective state in the running process of the vehicle.
And the third determining unit is used for determining the fault level of the fault according to the times.
The execution unit is used for executing setting operation corresponding to the fault level.
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 again.
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, specific names of the functional units and modules are only for convenience of 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.
Fig. 6 is a schematic structural diagram of a vehicle-mounted terminal according to an embodiment of the present application. As shown in fig. 6, the in-vehicle terminal 6 of this embodiment includes: at least one processor 60 (only one is shown in fig. 6), a memory 61 and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, the processor 60 implementing the steps in any of the respective vehicle fault code setting method embodiments described above when executing the computer program 62.
The in-vehicle terminal may include, but is not limited to, a processor 60, a memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the in-vehicle terminal 6 and is not intended to limit the in-vehicle terminal 6, and may include more or less components than illustrated, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), the processor 60 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, 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 61 may in some embodiments be an internal storage unit of the in-vehicle terminal 6, such as a memory of the in-vehicle terminal 6. The memory 61 may also be an external storage device of the in-vehicle terminal 6 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the in-vehicle terminal 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the in-vehicle terminal 6. The memory 61 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs, etc., such as program codes of the computer program. The memory 61 may also be used for temporarily storing data that has been output or is to be output.
Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps that may implement the various method embodiments described above.
The embodiments of the present application provide a computer program product that, when run on a vehicle-mounted terminal, causes the vehicle-mounted terminal to perform steps that may be implemented in the various method embodiments described above.
The integrated 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 implements all or part of the flow in the methods of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program may implement the steps of each method embodiment described above when executed by a processor. 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 at least: any entity or device capable of carrying the computer program code to the in-vehicle terminal, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
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.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 (10)

1. A fault code setting method of a vehicle, characterized by comprising:
when detecting that a fault occurs in the vehicle in the current driving cycle, acquiring fault diagnosis code information corresponding to the fault;
and setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to the unified diagnosis service, and storing the fault diagnosis code information.
2. The fault code setting method as claimed in claim 1, wherein the setting the confirmed fault code in the fault diagnosis code information to a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information, comprises:
Acquiring the fault identification;
and if the identification exists in a preset fault identification table, setting the confirmed fault code in the fault diagnosis code information to be in an effective state in the current driving cycle according to unified diagnosis service, and storing the fault diagnosis code information.
3. The fault code setting method as claimed in claim 2, further comprising, after acquiring the identification of the fault:
if the identification is not in the fault identification table, detecting whether the fault occurs in the vehicle in the driving cycle which is the last to the current driving cycle;
if the vehicle fails in the previous driving cycle, setting a confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to a vehicle-mounted automatic diagnosis system, and storing the fault diagnosis code information;
and if the vehicle does not generate the fault in the last driving cycle, setting a pending fault code in the fault diagnosis code information to be in a valid state in the current driving cycle according to an on-board automatic diagnosis system, and storing the fault diagnosis code information.
4. The fault code setting method as claimed in claim 3, wherein said detecting whether the fault has occurred in the vehicle in the driving cycle immediately preceding the current driving cycle includes:
if the pending fault code in the fault diagnosis code information is in a valid state in the last driving cycle, determining that the fault occurs in the last driving cycle;
and if the pending fault code in the fault diagnosis code information is in an invalid state in the last driving cycle, determining that the fault does not occur in the last driving cycle.
5. The fault code setting method as claimed in claim 2, wherein the fault identification table is for storing faults for which identification is set; wherein the set identifier is used to characterize the type of fault as an sporadic fault, and the vehicle generates a fault response when the fault is detected.
6. The fault code setting method as claimed in claim 1, wherein when a fault of the vehicle in a current driving cycle is detected, after obtaining fault diagnosis code information corresponding to the fault, the method further comprises:
detecting whether the vehicle has failed in a driving cycle previous to the current driving cycle;
If the vehicle has the fault in the previous driving cycle, setting a confirmed fault code in the fault diagnosis code information in the current driving cycle to be in a valid state according to a vehicle-mounted automatic diagnosis system, and storing the fault diagnosis code information;
correspondingly, according to the unified diagnosis service, setting the confirmed fault code in the fault diagnosis code information to be in a valid state in the current driving cycle, and storing the fault diagnosis code information comprises:
and if the vehicle does not generate the fault in the driving cycle which is the last driving cycle of the current driving cycle, setting the confirmed fault code in the fault diagnosis code information into a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information.
7. The fault code setting method as claimed in claim 1, wherein the setting the confirmed fault code in the fault diagnosis code information to a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information, comprises:
and setting a bit value of a designated position in the fault diagnosis code information to a designated numerical value in the current driving cycle according to the unified diagnosis service so as to enable the confirmed fault code to be in a valid state.
8. The fault code setting method according to any one of claims 1 to 7, characterized by further comprising, after the setting of the confirmed fault code in the fault diagnosis code information to a valid state in the current driving cycle according to a unified diagnosis service, and storing the fault diagnosis code information:
recording the number of times that the confirmed fault code in the fault diagnosis code information corresponding to the fault is set to be in an effective state in the running process of the vehicle;
determining the fault level of the fault according to the times;
and executing setting operation corresponding to the fault level.
9. A vehicle-mounted terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the fault code setting method according to any one of claims 1 to 8 when executing the computer program.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the fault code setting method according to any one of claims 1 to 8.
CN202310483667.0A 2023-04-28 2023-04-28 Vehicle fault code setting method, vehicle-mounted terminal and medium Pending CN116501016A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310483667.0A CN116501016A (en) 2023-04-28 2023-04-28 Vehicle fault code setting method, vehicle-mounted terminal and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310483667.0A CN116501016A (en) 2023-04-28 2023-04-28 Vehicle fault code setting method, vehicle-mounted terminal and medium

Publications (1)

Publication Number Publication Date
CN116501016A true CN116501016A (en) 2023-07-28

Family

ID=87316197

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310483667.0A Pending CN116501016A (en) 2023-04-28 2023-04-28 Vehicle fault code setting method, vehicle-mounted terminal and medium

Country Status (1)

Country Link
CN (1) CN116501016A (en)

Similar Documents

Publication Publication Date Title
US10178094B2 (en) Communication system and information collection method executed in communication system
JPH11326140A (en) Vehicle diagnosing system
CN111140391A (en) Air intake sensor fault processing method, device and system, vehicle and medium
CN111267756B (en) Vehicle speed limit control method, vehicle and medium
KR101332022B1 (en) ECU monitoring system and monitoring method
CN113961386A (en) Automatic management method for software version of whole vehicle
CN116501016A (en) Vehicle fault code setting method, vehicle-mounted terminal and medium
CN116701177A (en) Method and device for testing interface pins of vehicle-mounted diagnostic system and electronic equipment
US20180208136A1 (en) Electronic control device for vehicles
CN113655776B (en) Vehicle detection method and device, electronic equipment and storage medium
CN114837776B (en) SCR system control method, electronic device and storage medium
CN114115170B (en) Method and device for determining vehicle configuration module and after-sale diagnostic instrument
CN112282954B (en) Method and equipment for detecting cheating fault of nitrogen-oxygen sensor
CN112153578B (en) Vehicle configuration code self-checking method and vehicle
CN111636955B (en) Heavy diesel vehicle and engine aftertreatment anti-cheating method and system thereof
CN114756585A (en) Vehicle data acquisition method and device, electronic equipment and storage medium
CN114089119A (en) High-voltage loop fault positioning method and device, electric vehicle and storage medium
JP2014037197A (en) Vehicle control device and vehicle control system
CN114859868B (en) Error-proofing processing method for off-line configuration of passenger car combination instrument system
JP2007286018A (en) On-board fault diagnosis control device
CN116610090A (en) Fault processing method and device and electronic equipment
CN112751822B (en) Communication apparatus, operation method, abnormality determination apparatus, abnormality determination method, and storage medium
US20220254201A1 (en) Accident information recording device
CN116208521A (en) Sensor message channel identification method and device, electronic equipment and storage medium
CN114185731A (en) Method, device, equipment and storage medium for detecting data tampering

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