CN112485019A - Vehicle fault diagnosis method and device, vehicle and storage medium - Google Patents
Vehicle fault diagnosis method and device, vehicle and storage medium Download PDFInfo
- Publication number
- CN112485019A CN112485019A CN202011327432.5A CN202011327432A CN112485019A CN 112485019 A CN112485019 A CN 112485019A CN 202011327432 A CN202011327432 A CN 202011327432A CN 112485019 A CN112485019 A CN 112485019A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- electronic control
- control unit
- fault
- fault code
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M17/00—Testing of vehicles
- G01M17/007—Wheeled or endless-tracked vehicles
-
- 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)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
Abstract
The embodiment of the invention provides a vehicle fault diagnosis method, a vehicle fault diagnosis device, a vehicle and a storage medium, and relates to the technical field of vehicle diagnosis, wherein the vehicle fault diagnosis method is applied to a vehicle-mounted communication terminal which is communicated with an electronic control unit of the vehicle, and comprises the following steps: receiving a first message actively sent by an electronic control unit; judging whether the electronic control unit generates a fault code according to the data information of the first message; in the case where the electronic control unit generates a fault code, the fault code of the electronic control unit is acquired. The vehicle failure diagnosis device is used for executing the vehicle failure diagnosis method. The vehicle and the storage medium each store a computer program for implementing the above-described vehicle failure diagnosis method. The vehicle-mounted communication terminal can timely acquire the fault condition of the vehicle so as to be timely uploaded to the background server for analysis and pushed to the client terminal.
Description
Technical Field
The invention relates to the technical field of vehicles, in particular to a vehicle fault diagnosis method and device, a vehicle and a storage medium.
Background
With the rapid development of the automobile industry, vehicles have become a major transportation tool in the daily life of users. Meanwhile, potential safety hazard problems such as vehicle faults and the like in the driving process are also shown. Therefore, it becomes important to perform the vehicle failure diagnosis efficiently in time to ensure the driving safety.
However, the fault diagnosis of the existing vehicle is usually triggered by a background instruction, and the method inevitably has time delay, so that the fault condition of the vehicle cannot be acquired in time.
Disclosure of Invention
The object of the present invention includes, for example, providing a vehicle failure diagnosis method, apparatus, vehicle, and storage medium, which can acquire a failure situation of the vehicle in a timely manner.
Embodiments of the invention may be implemented as follows:
in a first aspect, an embodiment of the present invention provides a vehicle fault diagnosis method, which is applied to a vehicle-mounted communication terminal, where the vehicle-mounted communication terminal communicates with an electronic control unit of a vehicle, and the method includes:
receiving a first message actively sent by an electronic control unit;
judging whether the electronic control unit generates a fault code according to the data information of the first message;
in the case where the electronic control unit generates a fault code, the fault code of the electronic control unit is acquired.
In an alternative embodiment, the step of acquiring a fault code of the electronic control unit comprises:
sending a fault diagnosis command to the electronic control unit;
and receiving a second message fed back by the electronic control unit in response to the fault diagnosis command, and acquiring a fault code of the electronic control unit according to data information of the second message.
In an alternative embodiment, the step of acquiring a fault code of the electronic control unit comprises:
and acquiring the fault code of the electronic control unit according to the data information of the first message and a prestored fault code comparison table.
In an optional embodiment, the data information of the electronic control unit includes a character string, a plurality of character bits of the character string correspond to different fault codes respectively, and a character on each character bit is used to characterize whether a corresponding fault code exists, the fault code comparison table includes a one-to-one correspondence relationship between a plurality of fault codes and a plurality of character bits, and when a fault code corresponding to a character characterization on a character bit exists, the corresponding fault code is obtained through the corresponding character bit and the fault code comparison table.
In an optional implementation manner, the character string is a binary number, a plurality of digits of the binary number correspond to different fault codes respectively, and the digits on each digit are used for representing whether the corresponding fault code exists, the fault code comparison table includes a one-to-one correspondence relationship between a plurality of fault codes and a plurality of digits, and when the fault code corresponding to the digit representation on the digit exists, the corresponding fault code is determined through the corresponding digit and the fault code comparison table.
In an optional embodiment, the step of receiving the first message actively sent by the electronic control unit further includes:
detecting whether the running state of the vehicle meets a preset condition or not;
the step of receiving the first message actively sent by the electronic control unit comprises the following steps:
and receiving a first message actively sent by the electronic control unit when the running state of the vehicle meets a preset condition.
In an alternative embodiment, the preset condition comprises the speed of the vehicle being less than or equal to a first threshold.
In a second aspect, an embodiment of the present invention provides a vehicle fault diagnosis device, which is applied to a vehicle-mounted communication terminal, where the vehicle-mounted communication terminal communicates with an electronic control unit of a vehicle, and the vehicle fault diagnosis device includes a receiving module, a determining module, and an obtaining module, where the receiving module is used to receive a first message actively sent by the electronic control unit; the judging module is used for judging whether the electronic control unit has a fault according to the data information of the first message; the acquisition module is used for acquiring a fault code of the electronic control unit under the condition that the electronic control unit has a fault.
In a third aspect, an embodiment of the present invention provides a vehicle, including a vehicle-mounted communication terminal and an electronic control unit that communicates with the vehicle-mounted communication terminal, where the vehicle-mounted communication terminal includes a memory and a processor, the memory stores a computer program, and the processor executes the computer program to implement the vehicle fault diagnosis method according to any one of the foregoing embodiments.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the vehicle fault diagnosis method of any one of the foregoing embodiments is implemented.
The beneficial effects of the embodiment of the invention include, for example:
the vehicle fault diagnosis method provided by the embodiment of the invention is applied to a vehicle-mounted communication terminal which is communicated with an electronic control unit of a vehicle, the vehicle-mounted communication terminal can judge whether the electronic control unit generates a fault code according to a first message which is actively sent by the electronic control unit, if the fault code is generated, the fault code of the electronic control unit is acquired, namely, the diagnosis operation is triggered by the electronic control unit which generates the fault code, and the vehicle-mounted communication terminal does not wait for a diagnosis instruction of a background server like the prior art, so that the vehicle-mounted communication terminal can acquire the fault condition of the vehicle in time, and the fault condition is conveniently uploaded to the background server for analysis and pushed to a client terminal, and the defects of the existing vehicle fault diagnosis technology are effectively overcome.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is an application scenario diagram of a vehicle fault diagnosis method according to a first embodiment of the present invention;
fig. 2 is a block diagram of a vehicle-mounted communication terminal according to a first embodiment of the present invention;
fig. 3 is a flowchart illustrating interaction among the electronic control unit, the vehicle-mounted communication terminal, the background server, and the client terminal according to the first embodiment of the present invention;
fig. 4 is a flowchart of a vehicle fault diagnosis method according to a first embodiment of the present invention;
fig. 5 is a flowchart illustrating sub-steps of step S400 of a vehicle fault diagnosis method according to a first embodiment of the present invention;
fig. 6 is a schematic diagram of fault information displayed on a client terminal according to a first embodiment of the present invention;
fig. 7 is a block diagram showing the configuration of a vehicle failure diagnosis apparatus according to a first embodiment of the present invention;
fig. 8 is a block diagram of an obtaining module according to a first embodiment of the present invention;
fig. 9 is a flowchart illustrating sub-steps of step S300 of a vehicle fault diagnosis method according to a second embodiment of the present invention;
fig. 10 is a block diagram showing the construction of a vehicle failure diagnosis apparatus according to a second embodiment of the present invention;
fig. 11 is a flowchart of a vehicle fault diagnosis method according to a third embodiment of the present invention;
fig. 12 is a block diagram showing a configuration of a vehicle failure diagnosis apparatus according to a third embodiment of the present invention.
Icon: 100-vehicle communication terminal; 101-a memory; 102-a communication interface; 103-a processor; 104-a bus; 200-an electronic control unit; 210-a gateway; 300-background server; 400-a client terminal; 500-vehicle fault diagnosis means; 510-a receiving module; 520-a judgment module; 530-an acquisition module; 540-a diagnostic module; 550-an analysis module; 560-a lookup module; 570-detection module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Furthermore, the appearances of the terms "first," "second," and the like, if any, are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance. It should also be noted that features in the embodiments of the invention may be combined with each other without conflict.
The first embodiment:
referring to fig. 1, fig. 1 is a view of an application scenario of a vehicle fault diagnosis method according to a first embodiment of the present invention. In this application scenario, the in-vehicle communication terminal 100 of the vehicle communicates with the electronic control unit 200 of the vehicle through the gateway 210, and simultaneously communicates with the backend server 300 through the network, and the backend server 300 communicates with the client terminal 400 through the network.
The vehicle can be a traditional fuel vehicle or a new energy vehicle (including a hybrid vehicle, an electric vehicle and the like). The electronic control unit 200(ECU) may include an Engine Management System (EMS), a Transmission Control Unit (TCU), an Electric Power Steering (EPS), etc. if the vehicle is a fuel-powered vehicle, and the electronic control unit 200(ECU) may include a Vehicle Control Unit (VCU), a Battery Management System (BMS), a motor controller (DCU), etc. if the vehicle is a new energy vehicle. The electronic control unit 200 and the gateway 210 and the vehicle-mounted communication terminal 100 are connected by a vehicle bus, which is a CAN bus in the present embodiment, and may be a LIN bus, a FlexRay bus, or the like in other embodiments. The network can be a 3G network, a 4G network, a 5G network, etc. The client terminal 400 may be a mobile phone, a tablet computer, a smart band, etc.
Referring to fig. 2, fig. 2 is a block diagram of a vehicle-mounted communication terminal 100 according to a first embodiment of the present invention. The vehicle-mounted communication terminal 100 may be, but is not limited to, a T-BOX device or an OBD (On-Board Diagnostics) device. The vehicle-mounted communication terminal 100 includes a memory 101, a communication interface 102, a processor 103, and a bus 104, wherein the memory 101, the communication interface 102, and the processor 103 are connected via the bus 104, and the processor 103 is configured to execute an executable module stored in the memory 101, such as a computer program, code of which may be in a source code form, an object code form, an executable file or some intermediate form, and the like.
The Memory 101 may include a high-speed Random Access Memory 101 (RAM) and may also include a non-volatile Memory 101 (e.g., at least one disk Memory 101). The communication between the vehicle-mounted communication terminal 100 and the gateway 210, the electronic control unit 200 and the background server 300 is realized through at least one communication interface 102 (which may be wired or wireless). The bus 104 may be an ISA bus 104, a PCI bus 104, or an EISA bus 104, among others. Only one bi-directional arrow is shown in fig. 2, but this does not indicate only one bus 104 or one type of bus 104.
The memory 101 is used to store a program, such as a vehicle failure diagnosis apparatus 500 shown in fig. 7. The vehicle failure diagnosis apparatus 500 includes at least one software functional module that can be stored in the memory 101 in the form of software or firmware (firmware). The processor 103 executes a program to implement the vehicle fault diagnosis method disclosed by the embodiment of the invention after receiving the execution instruction.
Referring to fig. 3, fig. 3 is a flowchart illustrating interaction among the electronic control unit 200, the vehicle-mounted communication terminal 100, the background server 300 and the client terminal 400 according to the first embodiment of the present invention. In the embodiment of the invention, the vehicle fault diagnosis method can be applied to the vehicle-mounted communication terminal 100. After the vehicle is started or powered on, the electronic control unit 200 is initialized, and then the electronic control unit 200 starts to continuously monitor the operating conditions of the corresponding vehicle components. When a fault of a component is monitored, the electronic control unit 200 generates and stores a corresponding fault code, meanwhile, the electronic control unit 200 actively sends a first message to the vehicle-mounted communication terminal 100, the vehicle-mounted communication terminal 100 judges whether the electronic control unit 200 generates the fault code according to data information of the first message after receiving the first message actively sent by the electronic control unit 200, and acquires the fault code of the electronic control unit 200 under the condition that the electronic control unit 200 generates the fault code. Then, the vehicle-mounted communication terminal sends the fault code of the electronic control unit 200 to the backend server 300, and after receiving the fault code of the electronic control unit 200, the backend server 300 analyzes the fault code according to a fault knowledge base stored by itself, so as to acquire fault information corresponding to the fault code, and sends the corresponding fault information to the client terminal 400 for display, so that the client can view the fault information.
Referring to fig. 4, fig. 4 is a flowchart of a vehicle fault diagnosis method according to a first embodiment of the present invention. The vehicle fault diagnosis method provided by the embodiment of the invention comprises the following steps:
step S100: receiving a first message actively sent by the electronic control unit 200. The electronic control unit 200 will actively send a first message for indicating whether there is a fault code generation to the vehicle-mounted communication terminal 100. The sending time interval may be determined according to actual conditions, and in order to ensure real-time performance and timeliness of the vehicle fault, in this embodiment, the time interval for sending the first message by the electronic control unit 200 may be 1 to 5S. In other embodiments, the time interval may be longer, such as 1-5 minutes.
Step S200: and judging whether the electronic control unit 200 generates a fault code according to the data information of the first message. After receiving the first message, the vehicle-mounted communication terminal 100 analyzes the first message to determine whether the corresponding electronic control unit 200 has a fault code.
Step S300: in the case where the electronic control unit 200 generates a fault code, the fault code of the electronic control unit 200 is acquired. The fault code of the ecu 200 may be obtained in different manners, referring to fig. 5, and fig. 5 is a flowchart illustrating a sub-step S400 of a vehicle fault diagnosis method according to a first embodiment of the present invention. In this embodiment, the step of acquiring the fault code of the electronic control unit 200 specifically includes the following steps:
s310: a failure diagnosis command is sent to the electronic control unit 200. When the in-vehicle communication terminal 100 determines that a fault code is generated for one or some of the electronic control units 200, a fault diagnosis command is transmitted to the electronic control units 200. In this embodiment, the vehicle-mounted communication terminal 100 sends a fault diagnosis command to one or some electronic control units 200 that generate a fault code, so as to accurately acquire the fault code of the corresponding electronic control unit 200. In other embodiments, in order to avoid missing the electronic control units 200 that generate the fault codes, the in-vehicle communication terminal 100 may also transmit the fault diagnosis command to all the electronic control units 200.
S320: and receiving a second message fed back by the electronic control unit 200 in response to the fault diagnosis command, and acquiring a fault code of the electronic control unit 200 according to data information of the second message. After receiving the second message fed back by a corresponding part or all of the electronic control units 200, the vehicle-mounted communication terminal 100 analyzes the second message to obtain data information in the second message, and then extracts the fault code of the electronic control unit 200 from the data information in the second message. The data information in the second message may be identical to the fault code of the electronic control unit 200, or may contain data other than the fault code of the electronic control unit 200.
Step S400: the fault code of the electronic control unit 200 is sent to the backend server 300 for the backend server 300 to analyze so as to obtain the corresponding fault information. The in-vehicle communication terminal 100 acquires the fault code of the electronic control unit 200 and then transmits the fault code to the background server 300. After receiving the fault code, the background server 300 analyzes the fault code according to a fault knowledge base (at least including a corresponding relationship between the fault code and the fault name) stored in the background server, so as to obtain corresponding fault information.
For example, if the fault code received by the background server 300 and sent by the in-vehicle communication terminal 100 is P0055, the background server 300 may search for a fault name corresponding to the fault code P0055 from a fault knowledge base, for example, the power voltage is low. The backend server 300 will then collate the information related to the fault code to obtain fault information. The failure information may include the vehicle VIN code, the name of the electronic control unit 200, the time and place of generation of the failure code, and the like, in addition to the failure code and the failure name. Finally, the backend server 300 will edit the fault information according to a preset format (such as that shown in fig. 6) and then send the edited fault information to the client terminal 400 for the client to view in time.
Meanwhile, the background server 300 stores all the reported fault codes, and the subsequent vehicles can fetch corresponding fault records during fault judgment and maintenance, so that the efficiency of fault judgment and maintenance is improved.
The vehicle fault diagnosis method provided by the embodiment of the invention is applied to the vehicle-mounted communication terminal 100 which is communicated with the electronic control unit 200 of the vehicle, the vehicle-mounted communication terminal 100 can judge whether the electronic control unit 200 generates the fault code according to the first message actively sent by the electronic control unit 200, if the fault code is generated, the fault code of the electronic control unit 200 is acquired, namely, the diagnosis operation is triggered by the electronic control unit 200 which generates the fault code, and the diagnosis instruction of the background server 300 is not waited for as in the prior art, so that the vehicle-mounted communication terminal 100 can acquire the fault condition of the vehicle in time so as to be timely uploaded to the background server 300 for analysis and pushed to the client terminal 400, and the defects of the existing vehicle fault diagnosis technology are effectively overcome.
Referring to fig. 7, fig. 7 is a block diagram of a vehicle fault diagnosis device 500 according to a first embodiment of the present invention. The vehicle fault diagnosis device 500 may be applied to the vehicle-mounted communication terminal 100, and includes a receiving module 510, a determining module 520, and an obtaining module 530.
The receiving module 510 is configured to receive a first message actively sent by the electronic control unit 200. In this embodiment, the receiving module 510 is configured to execute step S100.
The determining module 520 is configured to determine whether the electronic control unit 200 fails according to the data information of the first packet. In this embodiment, the determining module 520 is configured to execute the step S200.
The obtaining module 530 is configured to obtain a fault code of the electronic control unit 200 in case of a fault of the electronic control unit 200. In this embodiment, the obtaining module 530 is configured to execute step S300.
In detail, referring to fig. 8, fig. 8 is a block diagram of a structure of an obtaining module 530 according to a first embodiment of the present invention, where the obtaining module 530 includes a diagnosing module 540 and an analyzing module 550. The diagnosis module 540 is used to send a fault diagnosis command to the electronic control unit 200. In this embodiment, the diagnosis module 540 is configured to execute step S310.
The parsing module 550 is configured to receive a second message fed back by the electronic control unit 200 in response to the fault diagnosis command, and obtain a fault code of the electronic control unit 200 according to data information of the second message. In this embodiment, the parsing module 550 is configured to execute step S320.
The vehicle fault diagnosis device 500 provided by the embodiment of the invention is applied to the vehicle-mounted communication terminal 100 which is in communication with the electronic control unit 200 of the vehicle, so that the vehicle-mounted communication terminal 100 can judge whether the electronic control unit 200 generates a fault code according to the first message actively sent by the electronic control unit 200, if the fault code is generated, the fault code of the electronic control unit 200 is acquired, namely, the diagnosis operation is triggered by the electronic control unit 200 which generates the fault code, and the vehicle fault condition can be acquired by the vehicle-mounted communication terminal 100 in time without waiting for a diagnosis instruction of the background server 300 as in the prior art, so that the vehicle fault condition can be timely uploaded to the background server 300 for analysis and pushed to the client terminal 400, and the defects of the existing vehicle fault diagnosis technology are effectively overcome.
Second embodiment:
the embodiment of the invention provides a vehicle fault diagnosis method which is basically the same as the vehicle fault diagnosis method provided by the first embodiment and comprises the steps of S100, S200, S300 and S400. The difference is in the specific manner of acquiring the fault code of the electronic control unit 200 in step S300.
Referring to fig. 9, fig. 9 is a flowchart illustrating a sub-step S300 of a vehicle fault diagnosis method according to a second embodiment of the present invention. In this embodiment, the step of acquiring the fault code of the electronic control unit 200 specifically includes the following steps:
s330: and acquiring the fault code of the electronic control unit 200 according to the data information of the first message and a prestored fault code comparison table.
When the fault code is acquired in this manner, it is necessary that the data information of the electronic control unit 200 include a character string. A plurality of character bits of the character string respectively correspond to different fault codes, and characters on each character bit are used for representing whether the corresponding fault codes exist or not. The number of character bits of the character string is determined according to the number of the fault codes of the electronic control unit 200, and the two are generally equal (sometimes, the number of the character bits may be greater than the number of the fault codes, at this time, only part of the character bits need to be in one-to-one correspondence with a plurality of fault codes, and the rest of the character bits and the characters thereon may be used for other purposes), the number of the fault codes of different electronic control units 200 is different, and accordingly, the number of the character bits of the character string in the first message sent by different electronic control units 200 is also different. Assuming that a certain ecu 200 has 8 fault codes, the character string in the first message sent by it also generally has 8-bit character bits, and 8 character bits correspond to 8 fault codes one to one.
Each character bit can adopt different characters to represent whether a corresponding fault code exists, in this embodiment, all the character bits use the same character to represent whether a corresponding fault code exists, for example, a character X can be used to represent that a fault code does not exist, and a character Y can be used to represent that a fault code exists.
Under the condition that the data information of the electronic control unit 200 adopts the above setting, the fault code comparison table is further required to include the one-to-one correspondence relationship between the plurality of fault codes and the plurality of character bits, so that when a fault code corresponding to a character on a character bit exists, the corresponding fault code can be acquired through the corresponding character bit and the fault code comparison table. For example, when the number on the 6 th character bit of the character string is Y, that is, the fault code corresponding to the 6 th character bit exists, the fault code corresponding to the 6 th character bit in the fault code comparison table can be searched.
Further, the character string may take any form, including numbers, letters, punctuations, etc., in this embodiment, the character string is a binary number, a plurality of digits of the binary number respectively correspond to different fault codes, and the number on each digit is used to represent whether the corresponding fault code exists. And the fault code comparison table comprises a one-to-one correspondence relationship between a plurality of fault codes and a plurality of digits, and when the fault code corresponding to the digital representation on the digit exists, the corresponding fault code is determined through the corresponding digit and the fault code comparison table.
It is assumed that a character string of a first message sent by a certain electronic control unit 200 is 00000101, a character 0 represents that a corresponding fault code does not exist, a character 1 represents that a corresponding fault code exists, and it is assumed that the specific contents of a fault table look-up table are as follows:
| numerical order | Fault code |
| 1 | P0011 |
| 2 | P0022 |
| 3 | P0033 |
| 4 | P0044 |
| 5 | P0055 |
| 6 | P0066 |
| 7 | P0077 |
| 8 | P0088 |
The analysis and search process of the fault code is as follows: if the binary number has 8 digits, it means that the corresponding ecu 200 has 8 fault codes, and if 2 digits of the 8 digits are 1, it means that the corresponding ecu 200 generates 2 fault codes, and the 2 fault codes correspond to the 6 th digit and the 8 th digit of the character string, respectively. Thus, the fault codes generated by the electronic control unit 200, i.e., P0066 and P0088, can be obtained by searching the two fault codes corresponding to the 6 th digit and the 8 th digit of the binary number in the fault code comparison table.
Accordingly, the present embodiment provides a vehicle fault diagnosis apparatus 500, which is substantially the same as the vehicle fault diagnosis apparatus 500 provided in the first embodiment, and includes a receiving module 510, a determining module 520, and an obtaining module 530. The difference is in the specific structure of the acquisition module 530.
Referring to fig. 10, fig. 10 is a block diagram of a vehicle fault diagnosis apparatus according to a second embodiment of the present invention, in this embodiment, the obtaining module 530 includes a searching module 560, and the searching module 560 is configured to obtain a fault code of the ecu 200 according to data information of the first message and a pre-stored fault code comparison table. In this embodiment, the searching module 560 is configured to execute step S330.
The third embodiment:
the embodiment of the invention provides a vehicle fault diagnosis method which is basically the same as the vehicle fault diagnosis method provided by the first embodiment and comprises the steps of S100, S200, S300 and S400. With reference to fig. 11, fig. 11 is a flowchart of a vehicle fault diagnosis method according to a third embodiment of the present invention, where the vehicle fault diagnosis method according to the present embodiment further includes, before step S100:
step S010: whether the running state of the vehicle meets a preset condition is detected. When the running state of the vehicle satisfies the preset condition, step S100 is executed again. In this embodiment, S100 of this week is specifically: and receiving a first message actively sent by the electronic control unit 200 when the running state of the vehicle meets a preset condition.
The preset condition may be set as needed, and in the present embodiment, the preset condition includes that the speed of the vehicle is less than or equal to the first threshold. In other embodiments, the preset condition may further include that the start-up or power-on time of the vehicle is greater than or equal to a second threshold.
Accordingly, referring to fig. 12, fig. 12 is a block diagram of a vehicle fault diagnosis device 500 according to a third embodiment of the present invention, and the vehicle fault diagnosis device 500 according to the embodiment of the present invention is substantially the same as the vehicle fault diagnosis method according to the first embodiment, and includes a receiving module 510, a determining module 520, and an obtaining module 530.
The vehicle fault diagnosis device 500 provided by the embodiment further includes a detection module 570, and the detection module 570 is used for detecting whether the running state of the vehicle meets a preset condition. In this embodiment, the detecting module 570 is configured to execute step S010.
The fourth embodiment:
the embodiment of the invention provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor 103 to implement the vehicle fault diagnosis method of any one of the foregoing embodiments. Note that the computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory 101, Read-Only Memory 101 (ROM), Random Access Memory 101 (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A vehicle fault diagnosis method is applied to a vehicle-mounted communication terminal which is communicated with an electronic control unit of a vehicle, and is characterized by comprising the following steps:
receiving a first message actively sent by the electronic control unit;
judging whether the electronic control unit generates a fault code according to the data information of the first message;
and acquiring the fault code of the electronic control unit under the condition that the electronic control unit generates the fault code.
2. The vehicle failure diagnosis method according to claim 1, wherein the step of acquiring the failure code of the electronic control unit includes:
sending a fault diagnosis command to the electronic control unit;
and receiving a second message fed back by the electronic control unit in response to the fault diagnosis command, and acquiring a fault code of the electronic control unit according to data information of the second message.
3. The vehicle failure diagnosis method according to claim 1, wherein the step of acquiring the failure code of the electronic control unit includes:
and acquiring the fault code of the electronic control unit according to the data information of the first message and a prestored fault code comparison table.
4. The vehicle fault diagnosis method according to claim 3, wherein the data information of the electronic control unit includes a character string, a plurality of character bits of the character string correspond to different fault codes respectively, and characters on each of the character bits are used for representing whether a corresponding fault code exists, the fault code comparison table includes a one-to-one correspondence relationship between a plurality of fault codes and a plurality of character bits, and when the fault code corresponding to the character representation on the character bit exists, the corresponding fault code is obtained through the corresponding character bit and the fault code comparison table.
5. The vehicle fault diagnosis method according to claim 4, wherein the character string is a binary number, a plurality of digits of the binary number correspond to different fault codes, respectively, and digits on each digit are used for representing whether a corresponding fault code exists, the fault code comparison table includes a one-to-one correspondence relationship between a plurality of fault codes and a plurality of digits, and when the fault code corresponding to the digit representation on the digit exists, the corresponding fault code is determined through the corresponding digit and the fault code comparison table.
6. The vehicle fault diagnosis method according to claim 1, wherein the step of receiving the first message actively transmitted by the electronic control unit further comprises, before the step of:
detecting whether the running state of the vehicle meets a preset condition or not;
the step of receiving the first message actively sent by the electronic control unit comprises:
and receiving a first message actively sent by the electronic control unit when the running state of the vehicle meets a preset condition.
7. The vehicle malfunction diagnosis method according to claim 6, characterized in that the preset condition includes that the speed of the vehicle is less than or equal to a first threshold value.
8. A vehicle fault diagnosis device is applied to a vehicle-mounted communication terminal, the vehicle-mounted communication terminal is communicated with an electronic control unit of a vehicle, and the vehicle fault diagnosis device is characterized by comprising a receiving module, a judging module and an obtaining module, wherein the receiving module is used for receiving a first message actively sent by the electronic control unit; the judging module is used for judging whether the electronic control unit generates a fault code according to the data information of the first message; the acquisition module is used for acquiring the fault code of the electronic control unit under the condition that the electronic control unit generates the fault code.
9. A vehicle characterized by comprising an in-vehicle communication terminal and an electronic control unit that communicates with the in-vehicle communication terminal, the in-vehicle communication terminal comprising a memory that stores a computer program and a processor that implements the vehicle failure diagnosis method according to any one of claims 1 to 7 when the processor executes the computer program.
10. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the vehicle fault diagnosis method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011327432.5A CN112485019B (en) | 2020-11-24 | 2020-11-24 | Vehicle fault diagnosis method and device, vehicle and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011327432.5A CN112485019B (en) | 2020-11-24 | 2020-11-24 | Vehicle fault diagnosis method and device, vehicle and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112485019A true CN112485019A (en) | 2021-03-12 |
| CN112485019B CN112485019B (en) | 2023-06-09 |
Family
ID=74933436
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011327432.5A Active CN112485019B (en) | 2020-11-24 | 2020-11-24 | Vehicle fault diagnosis method and device, vehicle and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112485019B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377590A (en) * | 2021-06-09 | 2021-09-10 | 东软睿驰汽车技术（沈阳）有限公司 | Fault diagnosis method and device, vehicle-mounted terminal and medium |
| CN114115172A (en) * | 2021-10-26 | 2022-03-01 | 江西五十铃汽车有限公司 | Vehicle fault diagnosis method and device, readable storage medium and vehicle |
| CN114137932A (en) * | 2021-11-11 | 2022-03-04 | 上汽通用五菱汽车股份有限公司 | Vehicle diagnosis method, vehicle control unit, vehicle and readable storage medium |
| CN114167846A (en) * | 2021-12-31 | 2022-03-11 | 中国第一汽车股份有限公司 | Remote fault diagnosis system and method for new energy automobile |
| CN114237205A (en) * | 2021-12-16 | 2022-03-25 | 北京福田戴姆勒汽车有限公司 | Vehicle fault diagnosis method and device, vehicle and storage medium |
| CN114863582A (en) * | 2022-04-13 | 2022-08-05 | 岚图汽车科技有限公司 | Vehicle-mounted diagnosis method and device, electronic equipment and readable storage medium |
| CN115050117A (en) * | 2022-08-15 | 2022-09-13 | 深圳市星卡软件技术开发有限公司 | Vehicle diagnosis report generation method and device and diagnosis equipment |
| CN115695149A (en) * | 2022-10-31 | 2023-02-03 | 东风商用车有限公司 | Fault management method, device, equipment and storage medium of vehicle controller |
| CN116560342A (en) * | 2023-05-25 | 2023-08-08 | 无锡车联天下信息技术有限公司 | Vehicle fault diagnosis method and device |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004302675A (en) * | 2003-03-28 | 2004-10-28 | Mazda Motor Corp | Remote failure diagnostic system |
| JP2010108014A (en) * | 2008-10-28 | 2010-05-13 | Hitachi Ltd | Maintenance support system for computer product |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103336522A (en) * | 2013-05-30 | 2013-10-02 | 长城汽车股份有限公司 | Vehicle fault inquiry system, controller and vehicle |
| CN103439961A (en) * | 2013-08-02 | 2013-12-11 | 浙江吉利汽车研究院有限公司 | Automobile electronic control unit diagnostic function test method and system |
| US20140121888A1 (en) * | 2012-10-29 | 2014-05-01 | Beijing Wiselink Software Co., Ltd. | Method, server and system for vehicle diagnosis |
| CN104460644A (en) * | 2013-09-25 | 2015-03-25 | 比亚迪股份有限公司 | Vehicle fault solution method and device |
| CN104834303A (en) * | 2014-12-19 | 2015-08-12 | 北汽福田汽车股份有限公司 | Vehicle fault diagnosis method and system, and vehicle |
| CN105025058A (en) * | 2014-04-28 | 2015-11-04 | 广州汽车集团股份有限公司 | Vehicle remote diagnosis method, vehicle remote monitoring method and vehicle-mounted terminal |
| CN107272649A (en) * | 2017-07-05 | 2017-10-20 | 东南（福建）汽车工业有限公司 | Malfunction remote diagnosis system and method |
| CN107450514A (en) * | 2017-07-31 | 2017-12-08 | 广州亿程交通信息有限公司 | Vehicle remote fault diagnosis management method and system |
| CN108132663A (en) * | 2017-12-19 | 2018-06-08 | 风度（常州）汽车研发院有限公司 | The analytic method of vehicle trouble messages, device and system |
| CN108444727A (en) * | 2018-02-27 | 2018-08-24 | 广州汽车集团股份有限公司 | Vehicular remote monitoring method, monitoring device and monitoring system |
| CN109901555A (en) * | 2019-03-22 | 2019-06-18 | 深圳市元征科技股份有限公司 | A kind of car fault diagnosis method, equipment and storage medium |
| CN110597224A (en) * | 2019-09-09 | 2019-12-20 | 一汽解放汽车有限公司 | Vehicle fault information display method and device, vehicle and storage medium |
| CN111708353A (en) * | 2020-06-30 | 2020-09-25 | 深圳市元征科技股份有限公司 | Data display method and system for vehicle diagnosis equipment and related equipment |
| CN111949000A (en) * | 2019-05-17 | 2020-11-17 | 株洲中车时代电气股份有限公司 | Intelligent locomotive fault diagnosis system and method |
| CN111966081A (en) * | 2020-09-02 | 2020-11-20 | 上海博泰悦臻网络技术服务有限公司 | Fault diagnosis method, system, medium, equipment and vehicle based on vehicle-mounted display |
-
2020
- 2020-11-24 CN CN202011327432.5A patent/CN112485019B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004302675A (en) * | 2003-03-28 | 2004-10-28 | Mazda Motor Corp | Remote failure diagnostic system |
| JP2010108014A (en) * | 2008-10-28 | 2010-05-13 | Hitachi Ltd | Maintenance support system for computer product |
| US20140121888A1 (en) * | 2012-10-29 | 2014-05-01 | Beijing Wiselink Software Co., Ltd. | Method, server and system for vehicle diagnosis |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103336522A (en) * | 2013-05-30 | 2013-10-02 | 长城汽车股份有限公司 | Vehicle fault inquiry system, controller and vehicle |
| CN103439961A (en) * | 2013-08-02 | 2013-12-11 | 浙江吉利汽车研究院有限公司 | Automobile electronic control unit diagnostic function test method and system |
| CN104460644A (en) * | 2013-09-25 | 2015-03-25 | 比亚迪股份有限公司 | Vehicle fault solution method and device |
| CN105025058A (en) * | 2014-04-28 | 2015-11-04 | 广州汽车集团股份有限公司 | Vehicle remote diagnosis method, vehicle remote monitoring method and vehicle-mounted terminal |
| CN104834303A (en) * | 2014-12-19 | 2015-08-12 | 北汽福田汽车股份有限公司 | Vehicle fault diagnosis method and system, and vehicle |
| CN107272649A (en) * | 2017-07-05 | 2017-10-20 | 东南（福建）汽车工业有限公司 | Malfunction remote diagnosis system and method |
| CN107450514A (en) * | 2017-07-31 | 2017-12-08 | 广州亿程交通信息有限公司 | Vehicle remote fault diagnosis management method and system |
| CN108132663A (en) * | 2017-12-19 | 2018-06-08 | 风度（常州）汽车研发院有限公司 | The analytic method of vehicle trouble messages, device and system |
| CN108444727A (en) * | 2018-02-27 | 2018-08-24 | 广州汽车集团股份有限公司 | Vehicular remote monitoring method, monitoring device and monitoring system |
| CN109901555A (en) * | 2019-03-22 | 2019-06-18 | 深圳市元征科技股份有限公司 | A kind of car fault diagnosis method, equipment and storage medium |
| CN111949000A (en) * | 2019-05-17 | 2020-11-17 | 株洲中车时代电气股份有限公司 | Intelligent locomotive fault diagnosis system and method |
| CN110597224A (en) * | 2019-09-09 | 2019-12-20 | 一汽解放汽车有限公司 | Vehicle fault information display method and device, vehicle and storage medium |
| CN111708353A (en) * | 2020-06-30 | 2020-09-25 | 深圳市元征科技股份有限公司 | Data display method and system for vehicle diagnosis equipment and related equipment |
| CN111966081A (en) * | 2020-09-02 | 2020-11-20 | 上海博泰悦臻网络技术服务有限公司 | Fault diagnosis method, system, medium, equipment and vehicle based on vehicle-mounted display |
Non-Patent Citations (2)
| Title |
|---|
| 汪志斌;吴长水;黄敏涛;冯琛;: "基于J1939协议的车辆故障诊断与ECU报文解析" * |
| 汪志斌等: "基于J1939协议的车辆故障诊断与ECU报文解析", 《单片机与嵌入式系统应用》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377590A (en) * | 2021-06-09 | 2021-09-10 | 东软睿驰汽车技术（沈阳）有限公司 | Fault diagnosis method and device, vehicle-mounted terminal and medium |
| CN114115172A (en) * | 2021-10-26 | 2022-03-01 | 江西五十铃汽车有限公司 | Vehicle fault diagnosis method and device, readable storage medium and vehicle |
| CN114137932A (en) * | 2021-11-11 | 2022-03-04 | 上汽通用五菱汽车股份有限公司 | Vehicle diagnosis method, vehicle control unit, vehicle and readable storage medium |
| CN114237205A (en) * | 2021-12-16 | 2022-03-25 | 北京福田戴姆勒汽车有限公司 | Vehicle fault diagnosis method and device, vehicle and storage medium |
| CN114167846A (en) * | 2021-12-31 | 2022-03-11 | 中国第一汽车股份有限公司 | Remote fault diagnosis system and method for new energy automobile |
| CN114863582A (en) * | 2022-04-13 | 2022-08-05 | 岚图汽车科技有限公司 | Vehicle-mounted diagnosis method and device, electronic equipment and readable storage medium |
| CN115050117A (en) * | 2022-08-15 | 2022-09-13 | 深圳市星卡软件技术开发有限公司 | Vehicle diagnosis report generation method and device and diagnosis equipment |
| CN115695149A (en) * | 2022-10-31 | 2023-02-03 | 东风商用车有限公司 | Fault management method, device, equipment and storage medium of vehicle controller |
| CN116560342A (en) * | 2023-05-25 | 2023-08-08 | 无锡车联天下信息技术有限公司 | Vehicle fault diagnosis method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112485019B (en) | 2023-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112485019B (en) | Vehicle fault diagnosis method and device, vehicle and storage medium | |
| CN112491671B (en) | Method and system for monitoring whole vehicle feed problem and vehicle CAN network gateway | |
| US20240137737A1 (en) | System and method for managing a fleet of vehicles including electric vehicles | |
| CN109164789B (en) | Vehicle-mounted multimedia system for vehicle information diagnosis | |
| KR101448753B1 (en) | System and method for vehicles diagnosis using gateway | |
| CN103676923A (en) | An automobile fault diagnosing and processing method | |
| CN110445719B (en) | Routing table management method, device, equipment and storage medium | |
| US20210264383A1 (en) | Method and system of providing cloud-based vehicle history session | |
| CN110545220B (en) | Automobile diagnosis protocol detection method and related product | |
| US11288054B2 (en) | Vehicular communication system | |
| CN108153286B (en) | Fault diagnosis method and device and follower diagnosis system | |
| CN112347047B (en) | Vehicle data file generation method and device | |
| CN113433923A (en) | Vehicle remote diagnosis method, system, readable storage medium and device | |
| CN115145241A (en) | SOA service-based remote diagnosis method for vehicle-end CAN node and storage medium | |
| CN111929079A (en) | Annual inspection pre-examining method for vehicle and vehicle | |
| CN106557773B (en) | Vehicle fault diagnosis method and system | |
| CN109857085A (en) | Simulation generates method, system, simulation terminal and the test macro of travelling data | |
| CN105635241A (en) | Method, system and computer-readable recording medium for managing abnormal state of vehicle | |
| CN113409488A (en) | Data processing method and device, vehicle-mounted terminal and automobile | |
| CN118093400A (en) | Test method, test device, electronic equipment and storage medium | |
| CN113505056A (en) | Vehicle diagnosis method, system, device and storage medium | |
| CN115817179B (en) | Power battery safety early warning method and device, server and storage medium | |
| CN107205241B (en) | Wireless communication detection method and equipment thereof | |
| CN114415646B (en) | Remote vehicle diagnosis method, system and terminal equipment based on DoIP protocol | |
| CN112381966A (en) | Method for acquiring driving data signal and related device thereof |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |