CN113978394A - Vehicle fault detection method and device, electronic equipment and storage medium - Google Patents
Vehicle fault detection method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113978394A CN113978394A CN202111246632.2A CN202111246632A CN113978394A CN 113978394 A CN113978394 A CN 113978394A CN 202111246632 A CN202111246632 A CN 202111246632A CN 113978394 A CN113978394 A CN 113978394A
- Authority
- CN
- China
- Prior art keywords
- detection information
- detection
- ecu
- fault
- ecu system
- 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
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
- B60R16/0232—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions
- B60R16/0234—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions related to maintenance or repairing of vehicles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Abstract
The application is applicable to the technical field of automotive electronics, and provides a method and a device for detecting vehicle faults, electronic equipment and a storage medium. The method comprises the following steps: receiving a detection instruction, wherein the detection instruction carries a first system identifier of a first ECU system to be detected; acquiring first detection information of the first ECU system according to the first system identification; if the first detection information contains a fault code generated by the first ECU system, acquiring second detection information of a second ECU system associated with the fault code; and comparing and displaying the first detection information and the second detection information. The method can help the vehicle maintainer to quickly compare the detection data of the ECU system to be detected and the associated ECU system, thereby accelerating troubleshooting, reducing maintenance time cost and improving maintenance efficiency.
Description
Technical Field
The present application belongs to the field of automotive electronics technologies, and in particular, to a method and an apparatus for vehicle fault detection, an electronic device, and a storage medium.
Background
At present, generally, a fault detection device acquires a fault code of an Electronic Control Unit (ECU) to be detected to help a vehicle maintainer locate a fault, but this method has a problem of inconvenient fault location.
Disclosure of Invention
The embodiment of the application provides a vehicle fault detection method and device, electronic equipment and a storage medium, and can solve the problem of how to facilitate a maintainer to locate a vehicle fault.
In a first aspect, an embodiment of the present application provides a method for vehicle fault detection, including:
receiving a detection instruction, wherein the detection instruction carries a first system identifier of a first ECU system to be detected;
acquiring first detection information of the first ECU system according to the first system identification;
if the first detection information contains a fault code generated by the first ECU system, acquiring second detection information of a second ECU system associated with the fault code;
and comparing and displaying the first detection information and the second detection information.
It should be understood that when the fault code generated by the ECU system to be detected is detected, the detection information of the ECU system associated with the ECU system to be detected is acquired, and the detection information is displayed by comparison, so that the vehicle maintainer can be helped to quickly compare the detection data of the ECU system to be detected and the detection data of the associated ECU system, thereby accelerating troubleshooting, reducing the maintenance time cost and improving the maintenance efficiency.
In a second aspect, an embodiment of the present application provides an apparatus for vehicle fault detection, including:
the detection instruction receiving module is used for receiving a detection instruction, and the detection instruction carries a first system identifier of a first ECU system to be detected;
the first detection information acquisition module is used for acquiring first detection information of the first ECU system according to the first system identifier;
the second detection information acquisition module is used for acquiring second detection information of a second ECU system associated with a fault code if the first detection information contains the fault code generated by the first ECU system;
and the detection information display module is used for comparing and displaying the first detection information and the second detection information.
In a third aspect, an embodiment of the present application provides an electronic device, including:
a memory, a processor and a computer program stored in the memory and executable on the processor, the computer program, when executed by the processor, implementing the method steps of the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including: the computer readable storage medium stores a computer program which, when executed by a processor, performs the method steps of the first aspect described above.
In a fifth aspect, embodiments of the present application provide a computer program product, which, when run on an electronic device, causes the electronic device to perform the method steps of the first aspect.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic view of a vehicle fault detection system provided by an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of a method of vehicle fault detection provided by an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of a method of vehicle fault detection provided by an embodiment of the present application;
FIG. 4 is a schematic view of a user interface provided in an embodiment of the present application;
FIG. 5 is a schematic view of a user interface provided in an embodiment of the present application;
FIG. 6 is a schematic flow chart diagram of a method of vehicle fault detection provided by an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a vehicle fault detection device provided by an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device provided in 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 structures, 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 will 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 and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this 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 present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
At present, a fault code of an ECU to be detected of a vehicle to be detected is generally acquired by fault detection equipment to help a vehicle maintainer locate a fault. However, the applicant has found that if the fault detection device detects only the ECU to be detected and displays only the single ECU communication data, when the vehicle fault relates to a multi-ECU system, the vehicle operation state data and the fault original record and other data recorded in the plurality of ECUs cannot be displayed at the same time. The vehicle maintenance personnel can not visually compare the data of the ECU associated with the fault, so that the operation of the fault detection process is complex, and the vehicle fault can not be solved quickly. That is to say, obtain the fault code that waits to detect the ECU through fault detection equipment, help vehicle service personnel to fix a position the trouble, have the inconvenient problem of location trouble. Based on the above findings, embodiments of the present application provide a vehicle fault detection system, method, device, and electronic device to solve the problem of how to facilitate a service person to locate a vehicle fault.
Fig. 1 illustrates a vehicle fault detection system 10 according to an embodiment of the present application. The system 10 includes: a fault detection device 110 and a vehicle 120 to be detected. In some embodiments, the system 10 also includes a server 130.
Therein, the fault detection device 110 is connected with the vehicle 120 through a fault detection interface. In some embodiments, the fault detection interface may be an On-Board Diagnostics (OBD) interface. In some embodiments, the fault detection device 110 may utilize an OBD interface to establish a connection with the ECU of the vehicle 120 via a Controller Area Network Bus (CANBUS). When the detection software in the failure detection device is started, a Communication Logical Link (CLL) with the ECU is established.
In some embodiments of the present application, the communication logical links may be simultaneously established between the failure detection apparatus 110 and the plurality of ECUs of the vehicle 120, respectively.
In other embodiments, signals from different pins of the OBD interface may be received at the fault detection device configuration processor, implementing multiple communication physical links that may operate in parallel, thereby enabling detection data from different ECUs to be received.
In still other embodiments, multiple communication physical links operable in parallel may be implemented by configuring wireless data links with different ECUs through a fault detection device, receiving detection data from different ECUs from the implementation.
In some specific examples, the logical link is one physical link, one or more virtual communication links being virtualized. In one possible embodiment, the virtual logical link is implemented on a physical link by setting a filter function corresponding to the receive function. Specifically, establishing the logical link of the target ECU system includes initializing a driver of the target ECU system, and specifically includes initializing a filter function and a receive function of the target EUC system. The filtering function may be a filtering rule set according to data characteristics (such as data format, data identifier, etc.) of the corresponding ECU system, and multiple filtering functions may be configured, each filtering function corresponding to a different ECU system. And respectively configuring corresponding filtering functions for each logical link, so that the logical link only receives the data of the ECU corresponding to the logical link according to the receiving function and the corresponding filtering function, thereby realizing the establishment of the logical link.
Communication between the fault detection device and one or more ECU systems of the vehicle under test may be achieved through multiple communication link techniques.
In some embodiments, the fault detection device 110 may also establish a connection and communicate with the vehicle 120 through a connector or a third party device. For example, the connector or third party device is an OBD interface device. The fault detection device 110 communicates with the connector or a third party device via a wired interface or a Wireless interface, for example, via a Universal Serial Bus (USB) interface, or via a bluetooth interface, or via a Wireless Local Area Network (WLAN) interface. It should be understood that these are merely examples of the manner in which the fault detection device 110 communicates with a connector or a third party device and are not limiting.
The form of the fault detection device 110 may be an automobile box, a vehicle-mounted electronic device, or other types of devices such as a mobile terminal connected to a vehicle, for example, a mobile phone, which may be specifically determined according to actual situations, and is not limited herein.
In some embodiments, the server 130 may be a remote server, a cloud server, a server cluster, or the like, which may provide a fault code information query service. The fault detection device 110 and the server 130 may communicate via a wired and/or wireless communication network.
Fig. 2 illustrates a method for vehicle fault detection provided by an embodiment of the present application, which is applied to the vehicle fault detection device 110 in the vehicle fault detection system 10 illustrated in fig. 1, and can be implemented by software and/or hardware of the vehicle fault detection device. As shown in fig. 2, the method includes steps S110 to S140. The specific realization principle of each step is as follows:
s110, receiving a detection instruction, wherein the detection instruction carries a first system identifier of a first ECU system to be detected.
In some embodiments, the detection instruction may be a detection instruction triggered by a user, a detection instruction triggered by internal software and/or hardware of the vehicle failure detection device, or a detection instruction triggered by an external device of the vehicle failure detection device.
In some embodiments, the vehicle fault detection device provides a user operated interface. The user operation interface can be an interface which can receive user specific operation and convert the operation into a trigger signal, such as a touch screen, a key, a voice recognition device, a gesture recognition device and the like.
In a specific example, the vehicle failure detection device receives a trigger signal from a user pressing a start detection button through a user operation interface, such as a touch screen. The vehicle failure detection device generates a detection instruction according to the trigger signal. The detection instruction carries a first system identifier of a first ECU system to be detected. The first system identifier may be configured through a user operation interface before the user clicks a start detection button, or may be a first system identifier pre-stored and default by the vehicle fault detection device.
In one particular example, the vehicle fault detection device may be triggered by a built-in software and/or hardware timer to generate the detection instruction; the vehicle fault detection device may also be triggered to generate a detection instruction by a detected change in an electrical signal of the OBD interface. The first system identifier of the first ECU system to be detected may be a default first system identifier pre-stored in the vehicle fault detection device.
The system identification of the ECU system is used for uniquely identifying the corresponding ECU system. The vehicle fault detection device determines a target ECU system needing to establish a detection link according to the system identification of the ECU system, and establishes the detection link with the target ECU system. Establishing the detection link with the target ECU system includes initializing a communication connection according to a protocol corresponding to the target ECU system. The detection link may be a communication physical link, or may be a communication logical link virtualized based on the communication physical link.
And S120, acquiring first detection information of the first ECU system according to the first system identifier.
In some embodiments, a first detection link is established with the first ECU system based on the first system identification. And acquiring the first detection information of the first ECU through the first detection link. The detection link is based on a first communication protocol of a first ECU system to be detected. The vehicle failure detection apparatus performs an inquiry operation to the ECU system through the first detection link to acquire first detection information.
In the embodiment of the present application, the detection information includes at least one of ECU system operation state data and ECU system failure data. Reference is made to this example for both the first detection information and the second detection information in the present application.
The ECU system operation state data comprises but is not limited to vehicle state data acquired by sensors such as rotating speed, oil quantity and the like. The vehicle state data may be stored in the form of a data stream, such as sensor data stored for a predetermined period of time. The vehicle state data may also be real-time sensor state data.
The ECU system fault data includes, but is not limited to, vehicle fault information detected by the ECU system through sensors such as angle sensors, wheel speed sensors, etc., and may also include vehicle fault information generated by the ECU system through judgment of a plurality of sensors or vehicle state data. The vehicle fault information may be stored in the form of a fault code. A fault Code (DTC) is a Code defined by an Electronic Control Unit (ECU) for each fault, and may also be referred to as a fault Code, an error Code, or other names. Since a plurality of fault codes are usually generated when a vehicle has a fault, the fault codes can be used as a parameter for assisting a vehicle service man in diagnosing a vehicle problem.
And S130, if the first detection information contains the fault code generated by the first ECU system, acquiring second detection information of a second ECU system associated with the fault code.
In some embodiments, the vehicle fault detection device analyzes received first detection information of a first ECU system to be detected, and acquires second detection information of a second ECU system associated with a fault code generated by the first ECU system if it is determined that the first detection information includes the fault code.
In a specific example, the vehicle fault detection device determines a second system identifier of a second ECU system associated with the fault code according to the fault code, and the vehicle fault detection device establishes a second detection link with the second ECU system according to the second system identifier; and acquiring second detection information of the second ECU system through the second detection chain link. The detection chain link is based on a second communication protocol of a second ECU system to be detected. The vehicle failure detection apparatus performs an inquiry operation to the ECU system through the second communication logical link to acquire second detection information. In some embodiments, the second detection chain link may be a communication physical link or a communication logical link virtualized based on the communication physical link.
It should be understood that one fault code may correspond to one or more second ECU systems, each following its own predefined communication protocol.
It should also be understood that the first detection information may include one or more fault codes generated by the first ECU system. And if a plurality of fault codes exist, respectively acquiring second detection information of the second ECU system associated with each fault code. In some embodiments, the fault codes may also be respectively associated with the same second ECU system in the second ECU system for reduction or merging by means of user setting or automatic screening.
In some embodiments, the fault detection device may determine, by way of user settings, the second ECU system associated with the fault code; the second ECU system associated with the fault code may also be determined by querying a third party device. With regard to determining the specific implementation of the second ECU system, reference may be made to the following example.
It is to be understood that in some embodiments, the vehicle malfunction detection apparatus need not acquire the second detection information of the associated second ECU system again if the first detection information does not contain the malfunction code generated by the first ECU system.
S140, comparing and displaying the first detection information and the second detection information.
In some embodiments, the comparing and displaying the first detection information and the second detection information may be displaying the first detection information and the second detection information on the same display interface. In one specific example, the first detection information and the second detection information may be displayed on adjacent display units of a display screen of the failure detection apparatus. The arrangement of the adjacent display units includes, but is not limited to, vertical arrangement, horizontal arrangement or nested arrangement. The nested arrangement mode can be that the display unit for displaying the second detection information is nested in the display unit for displaying the first detection information.
In some embodiments, the fault detection device may also be communicatively coupled to a plurality of display devices, while displaying the first detection information and the second detection information on the plurality of display devices.
In some embodiments, the first detection information and the second detection information may be displayed in different colors. For example, the first detection information is marked with red and the second detection information is marked with gray. So that the maintainers can distinguish the detection information conveniently.
It should be understood that, under the development trends of automobile electronic control, intellectualization and the like, the fault code recorded in a single ECU cannot represent the abnormality of the accessory or the system corresponding to the fault code. More need to be analyzed from the aspect of the electric control system principle. Further troubleshooting and confirmation of a plurality of associated ECUs related to fault codes, such as faults related to safe steering angle sensors, wheel speed sensors and the like, are required, and more ECU information needs to be acquired at the same time to better eliminate the faults. When the fault code generated by the ECU system to be detected is detected, the detection information of the ECU system associated with the ECU system to be detected is acquired, the detection information is contrasted and displayed, the detection data of the ECU system to be detected and the associated ECU system can be rapidly compared by a vehicle maintainer, the data can be rapidly compared by the vehicle maintainer, the troubleshooting is accelerated, the maintenance time cost is reduced, and the maintenance efficiency is improved.
On the basis of the above-described embodiment of vehicle failure detection shown in fig. 2, the step S130 of acquiring the second detection information of the second ECU system associated with the failure code, as shown in fig. 3, includes steps S1311 and S1312:
s1311, determining a second system identification of the second ECU system associated with the fault code in response to a user setting an operation of an associated system.
In some embodiments, as shown in fig. 4, the fault detection apparatus displays information related to the fault code through the fault code display interface 400 after determining that the first detection information of the first ECU system includes the fault code. Specifically, while the first display unit 410 displays the fault code, the user is prompted to view the associated system at the second display unit 420.
As shown in fig. 5, if the user selects to view the associated system, the malfunction detection apparatus displays the second system identification of the second ECU system associated with the malfunction code on the third display unit 430. The third display unit comprises one or more display subunits 431. The display subunit 431 may be a selection frame, for example, a TCM (shift control module) or the like shown in fig. 5, which represents a selection frame of the second ECU system. The user may perform a selection operation for each display subunit to determine the second ECU system associated with the fault code.
It is understood that the second system identifier of the second ECU system associated with the fault code, which may be the second ECU system identifier associated with one or more fault codes selected by the user, or the second ECU system identifier associated with all fault codes by default, is displayed on the third display unit 430.
After the user finishes the selection operation of the second ECU system associated with the user fault code, responding to the operation of the user setting association system, and determining a second system identifier of the second ECU system associated with the fault code.
S1312, acquiring second detection information of the second ECU system according to the second system identification.
In some embodiments, the fault detection device establishes a second detection link with the second ECU system based on the second system identification; and acquiring second detection information of the second ECU system through the second detection link. Reference may be made to the above examples for specific embodiments.
It should be understood that in the case where it is found that the ECU to be detected generates a fault code, the service personnel of the vehicle is referred to as the personnel who need to know the most about the operating conditions of the ECU system associated with the fault code. The embodiment of the application determines the second system identification of the second ECU system associated with the fault code by responding to the operation of a user setting associated system. On one hand, the method can be used for fully utilizing the experience of a service person to determine which associated ECU systems need to be displayed; on the other hand, the method can play a role in filtering relevant ECU systems which are not concerned by the user, and avoid the time-consuming problem caused by excessive detection of the ECU systems and the problem that redundant data interfere with detection of maintainers.
On the basis of the above-described embodiment of vehicle failure detection shown in fig. 2, the step S130 of acquiring the second detection information of the second ECU system associated with the failure code, as shown in fig. 6, includes steps S1321 and S1322:
s1321, sending a correlation system acquisition request to a server, wherein the correlation system acquisition request comprises the fault code; and the associated information acquisition request is used for indicating the server and feeding back a second system identifier of the second ECU system associated with the fault code according to the associated system acquisition request.
In some embodiments, as shown in FIG. 1, the vehicle fault detection system 10 also includes a server 130. The server 130 is an electronic device that can provide a fault code information query service. The server stores the corresponding relation between the fault code and the ECU system identification associated with the fault code. The correspondence may be stored in a manner including, but not limited to, a database, a mapping table, a text library, and the like. In other embodiments, the mapping model may be used to obtain the ECU system identification associated with the fault code based on the fault code. The mapping model can be a trained neural network model or other machine learning models.
In a specific example, after acquiring the first detection information of the first ECU system, the fault detection device generates a correlation system acquisition request if it is determined that the first detection information includes a fault code, where the correlation system acquisition request includes the fault code. The fault code in the associated system acquisition request may be one or more. After receiving an associated system acquisition request sent by the fault detection equipment, the server inquires a pre-stored corresponding relation, or acquires an ECU system identifier associated with the fault code according to the fault code by using a mapping model, and feeds back a second system identifier of the second ECU system associated with the fault code to the fault detection equipment.
And S1322, acquiring second detection information of the second ECU according to the second system identifier.
In some embodiments, the fault detection device establishes a second detection link with the second ECU system based on the second system identification; and acquiring second detection information of the second ECU system through the second detection link. Reference may be made to the above examples for specific embodiments.
It should be appreciated that by the server obtaining the second system identifier of the second ECU system associated with the fault code, more experience of the detecting personnel may be utilized to form a correspondence between the fault code and the ECU system identifier associated with the fault code, or to establish a mapping model of such a correspondence. The second system identification of the second ECU system acquired by the fault detection equipment is more objective, and the problem that the problem positioning is inaccurate due to insufficient experience of vehicle maintenance personnel and the maintenance time is too long is avoided.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Corresponding to the method for detecting vehicle failure shown in fig. 2, fig. 7 shows a device M100 for detecting vehicle failure according to an embodiment of the present application, including:
and the detection instruction receiving module M110 is configured to receive a detection instruction, where the detection instruction carries a first system identifier of a first ECU system to be detected.
A first detection information obtaining module M120, configured to obtain first detection information of the first ECU system according to the first system identifier.
A second detection information obtaining module M130, configured to obtain, if the first detection information includes a fault code generated by the first ECU system, second detection information of a second ECU system associated with the fault code.
And the detection information display module M140 is configured to compare and display the first detection information and the second detection information.
Optionally, the first detection information obtaining module includes:
the first detection link establishing module is used for establishing a first detection link with the first ECU system according to the first system identification;
and a first detection information acquisition module, configured to acquire the first detection information of the first ECU through the first detection link.
Optionally, the second detection information obtaining module includes:
a second system identification determination module for determining a second system identification of the second ECU system associated with the fault code in response to a user setting an operation of an associated system;
and the second detection information acquisition module is specifically used for acquiring second detection information of the second ECU system according to the second system identifier.
Optionally, the second detection information obtaining module includes:
the association system sending module is used for sending an association system acquisition request to a server, wherein the association system acquisition request comprises the fault code; the associated information acquisition request is used for indicating the server and feeding back a second system identifier of the second ECU system associated with the fault code according to the associated system acquisition request;
and the second detection information acquisition module is specifically used for acquiring second detection information of the second ECU according to the second system identifier.
Optionally, the second detection information obtaining module includes:
the second detection link determining module is used for establishing a second detection link with the second ECU system according to the second system identification;
and the second detection information acquisition module is specifically configured to acquire second detection information of the second ECU system through the second detection link.
Optionally, the detection information display module is specifically configured to display the first detection information and the second detection information on the same display interface.
Optionally, the first detection information and the second detection information include: ECU system operating status data and ECU system fault data.
It is understood that various embodiments and combinations of the embodiments in the above embodiments and their advantages are also applicable to this embodiment, and are not described herein again.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application, which is used to implement the fault detection device 110 in the vehicle fault detection system 10. As shown in fig. 8, the electronic device D10 of this embodiment includes: at least one processor D100 (only one is shown in fig. 8), a memory D101, and a computer program D102 stored in the memory D101 and operable on the at least one processor D100, wherein the processor D100 implements the steps of any of the method embodiments described above when executing the computer program D102. Alternatively, the processor D100, when executing the computer program D102, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the modules M110 to 140 shown in fig. 7.
The electronic device D10 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The electronic device may include, but is not limited to, a processor D100, a memory D101. Those skilled in the art will appreciate that fig. 8 is merely an example of the electronic device D10 and does not constitute a limitation of the electronic device D10, and may include more or fewer components than those shown, or some components in combination, or different components, such as input output devices, network access devices, etc.
Processor D100 may be a Central Processing Unit (CPU), and processor D100 may be other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage D101 may be an internal storage unit of the electronic device D10 in some embodiments, such as a hard disk or a memory of the electronic device D10. In other embodiments, the memory D101 may also be an external storage device of the electronic device D10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device D10. Further, the memory D101 may also include both an internal storage unit and an external storage device of the electronic device D10. The memory D101 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer programs. The memory D101 may also be used to temporarily store data that has been output or is to be output.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of 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 processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments may be implemented.
Embodiments of the present application provide a computer program product, which when executed on an electronic device, enables the electronic device to implement the steps in the above method embodiments.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A method of vehicle fault detection, comprising:
receiving a detection instruction, wherein the detection instruction carries a first system identifier of a first ECU system to be detected;
acquiring first detection information of the first ECU system according to the first system identification;
if the first detection information contains a fault code generated by the first ECU system, acquiring second detection information of a second ECU system associated with the fault code;
and comparing and displaying the first detection information and the second detection information.
2. The method of claim 1, wherein said obtaining first detection information of the first ECU system based on the first system identification comprises:
establishing a first detection link with the first ECU system according to the first system identification;
and acquiring the first detection information of the first ECU through the first detection link.
3. The method of claim 2, wherein said obtaining second detection information of a second ECU system associated with the fault code comprises:
determining a second system identification of the second ECU system associated with the fault code in response to operation of a user setting associated system;
and acquiring second detection information of the second ECU system according to the second system identification.
4. The method of claim 2, wherein said obtaining second detection information of a second ECU system associated with the fault code comprises:
sending a correlation system acquisition request to a server, wherein the correlation system acquisition request comprises the fault code; the associated information acquisition request is used for indicating the server and feeding back a second system identifier of the second ECU system associated with the fault code according to the associated system acquisition request;
and acquiring second detection information of the second ECU according to the second system identifier.
5. The method of claim 3 or 4, wherein said obtaining second detection information of the second ECU based on the second system identification comprises:
establishing a second detection link with the second ECU system according to the second system identification;
and acquiring second detection information of the second ECU system through the second detection link.
6. The method of claim 1, wherein the comparing displays the first detected information and the second detected information, comprising:
and displaying the first detection information and the second detection information on the same display interface.
7. The method of any of claims 1, 2, 3, or 6, wherein the first detection information and the second detection information comprise: ECU system operating status data and ECU system fault data.
8. An apparatus for vehicle fault detection, comprising:
the detection instruction receiving module is used for receiving a detection instruction, and the detection instruction carries a first system identifier of a first ECU system to be detected;
the first detection information acquisition module is used for acquiring first detection information of the first ECU system according to the first system identifier;
the second detection information acquisition module is used for acquiring second detection information of a second ECU system associated with a fault code if the first detection information contains the fault code generated by the first ECU system;
and the detection information display module is used for comparing and displaying the first detection information and the second detection information.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111246632.2A CN113978394A (en) | 2021-10-26 | 2021-10-26 | Vehicle fault detection method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111246632.2A CN113978394A (en) | 2021-10-26 | 2021-10-26 | Vehicle fault detection method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113978394A true CN113978394A (en) | 2022-01-28 |
Family
ID=79741478
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111246632.2A Pending CN113978394A (en) | 2021-10-26 | 2021-10-26 | Vehicle fault detection method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113978394A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115016434A (en) * | 2022-06-08 | 2022-09-06 | 河南职业技术学院 | Rack and whole vehicle data linkage method and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090281689A1 (en) * | 2008-05-12 | 2009-11-12 | Denso Corporation | Electronic control system for vehicles |
| CN107356284A (en) * | 2016-05-10 | 2017-11-17 | 中兴通讯股份有限公司 | A kind of detection method, apparatus and system |
| CN109934957A (en) * | 2019-03-20 | 2019-06-25 | 深圳市道通科技股份有限公司 | Show the method, device and mobile terminal of the distribution of vehicle ECU system and state |
| CN112606779A (en) * | 2020-12-24 | 2021-04-06 | 东风汽车有限公司 | Automobile fault early warning method and electronic equipment |
| CN112927392A (en) * | 2021-01-19 | 2021-06-08 | 深圳市元征科技股份有限公司 | Communication method, vehicle communication interface device and readable storage medium |
-
2021
- 2021-10-26 CN CN202111246632.2A patent/CN113978394A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090281689A1 (en) * | 2008-05-12 | 2009-11-12 | Denso Corporation | Electronic control system for vehicles |
| CN107356284A (en) * | 2016-05-10 | 2017-11-17 | 中兴通讯股份有限公司 | A kind of detection method, apparatus and system |
| CN109934957A (en) * | 2019-03-20 | 2019-06-25 | 深圳市道通科技股份有限公司 | Show the method, device and mobile terminal of the distribution of vehicle ECU system and state |
| CN112606779A (en) * | 2020-12-24 | 2021-04-06 | 东风汽车有限公司 | Automobile fault early warning method and electronic equipment |
| CN112927392A (en) * | 2021-01-19 | 2021-06-08 | 深圳市元征科技股份有限公司 | Communication method, vehicle communication interface device and readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115016434A (en) * | 2022-06-08 | 2022-09-06 | 河南职业技术学院 | Rack and whole vehicle data linkage method and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108803580B (en) | Method for matching vehicle CAN protocol and related equipment | |
| US7987028B2 (en) | Method and apparatus for reading and erasing diagnostic trouble codes from a vehicle | |
| JP4453764B2 (en) | Vehicle diagnostic device, vehicle diagnostic system, and diagnostic method | |
| US20130246135A1 (en) | System, device and method of remote vehicle diagnostics based service for vehicle owners | |
| KR102041846B1 (en) | A terminal and a method of collecting CAN date of vehicle using a OBD-Ⅱ | |
| US20120047458A1 (en) | System and Method for Selecting Individual Parameters to Transition from Text-to-Graph or Graph-to-Text | |
| KR20170013896A (en) | Personal vehicle diagnosis system and method based on mobile intelligent terminal | |
| CN105320035B (en) | For data function to be integrated in the equipment in the kinetic control system for vehicle | |
| US20220148349A1 (en) | Automated Vehicle Scan Tool Initialization | |
| CN112034824A (en) | Automobile diagnosis method, device, equipment and computer readable storage medium | |
| US20160171791A1 (en) | Method and Apparatus For Remote Diagnostics and Maintenance of Vehicles | |
| CN110244691B (en) | Automobile diagnosis method, device and system | |
| CN107111536B (en) | Diagnostic assistance method, device and system | |
| US20220277599A1 (en) | Supplementing Vehicle Service Content with Scan Tool Initialization Links | |
| CN203534602U (en) | Testing equipment suitable for vehicle-mounted navigation multimedia terminal | |
| CN113703868A (en) | Vehicle diagnostic software configuration method, electronic device and readable storage medium | |
| KR20130025288A (en) | Car managemtnt system with obd | |
| CN113978394A (en) | Vehicle fault detection method and device, electronic equipment and storage medium | |
| US11450154B2 (en) | Method and system for providing scanner jobs on diagnostic tool | |
| EP4206002A1 (en) | Method and apparatus for displaying function menu interface of automobile tyre pressure monitoring system | |
| US20200184744A1 (en) | Vehicle Scan Tool Configured to Receive Automated Initialization Requests | |
| US20060069963A1 (en) | Device and method for controlling a console | |
| EP3895087A1 (en) | Automated vehicle scan tool initialization | |
| CN109383417B (en) | Non-standard parameter identifier acquisition device, system and method thereof | |
| JP5836222B2 (en) | Vehicle control apparatus and vehicle control system |
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 |