CN112148538B - A vehicle fault identification method, device, system, vehicle and computer-readable storage medium - Google Patents

Abstract

The invention provides a complete vehicle fault identification method, which comprises the following steps: when the whole vehicle is in a non-air upgrade mode and the whole vehicle is not in a power-on state, judging whether the whole vehicle network is dormant, if not, acquiring whole vehicle network communication data, judging whether an ECU (electronic control unit) transmits data under the condition that the network communication condition is not met according to the whole vehicle network communication data, and if so, judging that the ECU transmitting the data under the condition that the network communication condition is not met is a fault ECU; the whole vehicle network communication data comprise network management messages, vehicle state data and network wake-up source signals. The invention can accurately position the failure ECU of the vehicle and the failure occurrence reason.

Description

A vehicle fault identification method, device, system, vehicle and computer-readable storage medium

Technical Field

The present invention relates to the field of automobile technology, and in particular to a whole vehicle fault identification method, device, system, automobile and computer-readable storage medium.

Background Art

With the continuous development of vehicle intelligence, in order to better improve customer experience, there are more and more electronic control components in vehicles. However, if there are too many electronic control components in a vehicle, it is very likely that the electronic control components will be abnormal. After the vehicle is powered off, it will still be in the network communication state for a long time, causing the vehicle network to be awakened for a long time and cause the vehicle to run out of power. This situation is not easy to be noticed by the driver, and the fault may disappear after the vehicle is powered on again. Therefore, it is difficult to troubleshoot the fault, and reproducing the fault will consume a lot of manpower and material resources.

According to the survey, in order to avoid the problem of low battery due to various reasons, the commonly used method is to display the battery status through the instrument during the driving process of the vehicle to remind the user to replace the battery or check the charging system, such as Audi, BMW, Peugeot, SAIC, etc.; or, when the battery power is low, cut off the comfort load. However, the current solutions cannot directly locate the abnormal electronic control components and record the fault data in time.

Summary of the invention

In order to solve the above technical problems, the present invention provides a vehicle fault locating method, system and vehicle, which can accurately locate the vehicle fault ECU and the cause of the fault.

The present invention provides a vehicle fault identification method, comprising the following steps:

When the vehicle is in a non-air upgrade mode and the vehicle is not powered on, determine whether the vehicle network is dormant. If not, obtain the vehicle network communication data, and determine whether there is an ECU sending data when the network communication conditions are not met based on the vehicle network communication data. If so, the ECU that sends data when the network communication conditions are not met is a faulty ECU;

Among them, the whole vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals.

Preferably, judging whether there is an ECU sending data when the network communication conditions are not met according to the vehicle network communication data, and if so, the ECU sending data when the network communication conditions are not met is a faulty ECU, specifically:

Determine whether there is an ECU that sends data without receiving a data request instruction first according to the network management message; if so, determine whether the ECU that sends data without receiving a data request instruction first belongs to a network wake-up source ECU according to the network wake-up source signal; if it does not belong to the network wake-up source ECU, the ECU that sends data without receiving a data request instruction first is a faulty ECU; if it belongs to the network wake-up source ECU, determine whether there is a network wake-up source ECU that sends data without satisfying a data sending trigger condition according to the vehicle status data; if so, the network wake-up source ECU that sends data without satisfying a data sending trigger condition is a faulty ECU.

Among them, the network wake-up source signal includes a brake status signal, a remote key remote control command signal, and a door status signal, and the network wake-up source ECU includes a brake control ECU, a remote key control ECU, and a door control ECU.

Preferably, the determining whether the vehicle network is dormant is specifically: determining whether the vehicle gateway is in a state of receiving or sending network data, if so, the vehicle network is in a non-dormant state, otherwise, the vehicle network is in a dormant state;

The obtaining of the whole vehicle network communication data specifically includes: the vehicle-mounted communication terminal obtaining the whole vehicle network communication data through the whole vehicle gateway.

Preferably, the method further comprises the following steps:

After the vehicle-mounted communication terminal obtains the vehicle network communication data through the vehicle gateway, it also obtains the vehicle VIN code and uploads the vehicle VIN code and the vehicle network communication data to the background server.

Preferably, the following steps are also included: the background server determines the vehicle configuration parameters according to the vehicle VIN code, and judges whether there is an ECU sending data without meeting the network communication conditions according to the vehicle configuration parameters and the whole vehicle network communication data. If so, the ECU sending data without meeting the network communication conditions is a faulty ECU.

The present invention also provides a vehicle fault identification device, which comprises:

The network status judgment module is used to judge whether the vehicle network is dormant when the vehicle is in a non-air upgrade mode and the vehicle is not powered on. If not, it is used to judge whether the duration of the vehicle network being in a non-dormant state is greater than a preset time threshold. If so, it is used to send the vehicle network communication data to the vehicle communication terminal.

A network fault judgment module is used to judge whether there is an ECU sending data when the network communication conditions are not met according to the vehicle network communication data, and if so, the ECU sending data when the network communication conditions are not met is a faulty ECU;

Among them, the whole vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals.

The present invention also provides a whole vehicle fault identification system, which includes the above-mentioned whole vehicle fault identification device, and further includes:

A data uploading module is used to obtain the vehicle VIN code and upload the vehicle VIN code and the vehicle network communication data to the backend server;

The backend server is used to determine the vehicle configuration parameters according to the vehicle VIN code, and judge whether there is an ECU sending data when the network communication conditions are not met according to the vehicle configuration parameters and the whole vehicle network communication data. If so, the ECU sending data when the network communication conditions are not met is a faulty ECU.

The present invention also provides a car, which comprises the above-mentioned whole-vehicle fault identification device.

The present invention also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute the vehicle fault identification method as described above.

The present invention also provides a whole vehicle fault locating device, comprising a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the above-mentioned whole vehicle fault identification method when executing the computer program.

The implementation of the present invention has the following beneficial effects: when the whole vehicle is powered off, the electronic control unit that is still in the network communication state when the network communication conditions are not met due to a fault can be accurately identified, thereby preventing the risk of the whole vehicle being out of power due to the long-term wake-up of the whole vehicle network caused by the faulty electronic control unit continuously sending data.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a flow chart of a vehicle fault identification method provided by the present invention.

FIG. 2 is a schematic diagram of specific implementation steps of a vehicle fault identification method in an embodiment of the present invention.

FIG3 is a functional block diagram of a vehicle fault identification system provided by the present invention.

DETAILED DESCRIPTION

The present invention provides a vehicle fault identification method, which comprises the following steps:

When the vehicle is in non-air upgrade mode and the vehicle is not powered on, determine whether the vehicle network is dormant. If not, obtain the vehicle network communication data, and determine whether there is an ECU (Electronic Control Unit) sending data when the network communication conditions are not met according to the vehicle network communication data. If so, the ECU that sends data when the network communication conditions are not met is a faulty ECU;

Among them, the vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals.

Here, the air upgrade mode signal sent by the ECU in the vehicle can be used to determine whether the vehicle is in the air upgrade mode. When all the CAN (Controller Area Network) buses connected to the vehicle gateway are dormant, the vehicle network is determined to be dormant. When the CAN bus is dormant, the CAN controller connected to the CAN bus knows the dormant state of the CAN bus.

Furthermore, it is determined whether there is an ECU sending data when the network communication conditions are not met according to the vehicle network communication data. If so, the ECU sending data when the network communication conditions are not met is a faulty ECU, specifically:

It is determined based on the network management message whether there is an ECU that sends data without receiving the data request instruction first. If so, it is determined based on the network wake-up source signal whether the ECU that sends data before receiving the data request instruction first belongs to the network wake-up source ECU. If it does not belong to the network wake-up source ECU, the ECU that sends data before receiving the data request instruction first is a faulty ECU. If it belongs to the network wake-up source ECU, it is determined based on the vehicle status data whether there is a network wake-up source ECU that sends data without meeting the data sending trigger condition. If so, the network wake-up source ECU that sends data without meeting the data sending trigger condition is a faulty ECU.

Among them, the network wake-up source signals include brake status signals, remote key remote control command signals, and door status signals, and the network wake-up source ECUs include brake control ECU, remote key control ECU, and door control ECU.

Determine whether the vehicle network is dormant, specifically: determine whether the vehicle gateway is in a state of receiving or sending network data. If so, the vehicle network is in a non-dormant state; otherwise, the vehicle network is in a dormant state;

Obtaining the vehicle network communication data, specifically: the vehicle communication terminal obtains the vehicle network communication data through the vehicle gateway.

The above steps of determining the faulty ECU can all be executed by a T-box (Telematics BOX, referred to as an on-board communication terminal, ie, a telematics processor).

For example, as shown in Figure 2, when the T-box determines that the vehicle is in a non-air upgrade mode and the vehicle is not on high voltage, and when the vehicle power position changes from a non-power-off position (ON, ACC, CRANK, etc.) to a power-off position (OFF position) or the vehicle is powered off and the vehicle network is awakened after being dormant, the timer tVehOffNetWakeAccum is started. During the operation of the vehicle gateway, it is determined whether the vehicle network is dormant. If the vehicle network is dormant and the timing time of tVehOffNetWakeAccum is less than the preset time threshold, the bus is dormant, then the timer is canceled. If the vehicle network is not dormant and the timing time of tVehOffNetWakeAccum is greater than the preset time threshold, a record trigger instruction is sent to the T-box, and the T-box starts to collect instruction data. The T-box then determines the faulty ECU and the cause of its failure based on the instruction data. The instruction data includes the network management message of the network management ECU, the vehicle status data, and the network wake-up source associated signal. The vehicle status data contains data such as the power status, door opening status, location information, and current time of the vehicle.

Among them, through the two conditions of "non-air upgrade mode" and "the whole vehicle is not on high voltage", the normal operating conditions where users need to wake up the network for a long time (operating condition duration > preset time threshold, such as air upgrade, etc.) are avoided, avoiding the false triggering of the timer. The timer is canceled by the condition of "all network sleep", and the accumulation of short-term wake-up time such as T-box remote control is stipulated to avoid the accumulation of short-term vehicle operation time by users, which leads to false triggering of the timer.

The vehicle fault identification method also includes the following steps:

After the vehicle communication terminal obtains the vehicle network communication data through the vehicle gateway, it also obtains the vehicle VIN code (Vehicle Identification Number, vehicle identification number or frame number), and uploads the vehicle VIN code and vehicle network communication data to the backend server;

The backend server determines the vehicle configuration parameters based on the vehicle VIN code, and determines whether any ECU sends data when the network communication conditions are not met based on the vehicle configuration parameters and the vehicle network communication data. If so, the ECU that sends data when the network communication conditions are not met is a faulty ECU.

The backend server can troubleshoot problems and analyze data on low-battery quality issues based on the vehicle VIN code and vehicle network communication data.

Specifically, for example, the vehicle communication data collected by the background server includes network management messages. The background server makes judgments based on these network management messages. Among these network management messages, when a certain ECU actively wakes up the network, a network management message will occur, locking the ECU as a faulty ECU. At the same time, the throttle status signal is on, then the throttle status of the entire vehicle is locked as on, which is the reason why the vehicle network continues to wake up.

The background server is used as a reference for locating the faulty ECU and the cause of the fault. Data collection is based on the vehicle function design. The faulty ECU is initially determined through the ECU's network management message, and then the specific cause of the fault is further determined through the network wake-up source correlation signal of the faulty ECU.

The present invention also provides a whole vehicle fault identification device, which can be arranged in the T-box shown in FIG. 3 . The whole vehicle fault identification device includes: a network status judgment module and a network fault judgment module.

The network status judgment module is used to determine whether the vehicle network is dormant when the vehicle is in non-air upgrade mode and the vehicle is not powered on. If not, it is used to determine whether the duration of the vehicle network being in a non-dormant state is greater than a preset time threshold. If so, the vehicle network communication data is sent to the on-board communication terminal.

The network fault judgment module is used to judge whether there is an ECU sending data when the network communication conditions are not met based on the vehicle network communication data. If so, the ECU sending data when the network communication conditions are not met is a faulty ECU.

Among them, the vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals.

The present invention also provides a whole vehicle fault identification system, which includes the above-mentioned whole vehicle fault identification device, and also includes: a data upload module arranged in a T-box and a background server shown in FIG. 3 .

The data upload module is used to obtain the vehicle VIN code and upload the vehicle VIN code and vehicle network communication data to the backend server.

The backend server is used to determine the vehicle configuration parameters based on the vehicle VIN code, and to determine whether any ECU sends data without meeting the network communication conditions based on the vehicle configuration parameters and the vehicle network communication data. If so, the ECU that sends data without meeting the network communication conditions is a faulty ECU.

The present invention also provides a car, which comprises the above-mentioned whole-vehicle fault identification device.

The present invention also provides a computer-readable storage medium, which includes a stored computer program; wherein the computer program, when running, controls the device where the computer-readable storage medium is located to execute the above-mentioned vehicle fault identification method.

The present invention also provides a whole vehicle fault locating device, which includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, the above-mentioned whole vehicle fault identification method is implemented.

The present invention has the following beneficial effects:

1. Reduce the difficulty of troubleshooting power failure. Data collection is done before power failure to prevent the failure from disappearing after the ECU is restarted. The troubleshooting direction provides clear guidance for after-sales troubleshooting and reduces the manpower/material costs of troubleshooting.

2. Accurate fault location can improve the power loss rate from the perspective of power balance. Accurate fault location can quickly discover and permanently solve the power loss caused by the current fault;

3. Data is stored in the background, which is convenient for after-sales personnel to access anytime and anywhere, and also provides data support for subsequent quality problem design improvements.

The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims (9)

1. A vehicle fault identification method, characterized in that it comprises the following steps: When the vehicle is in a non-air upgrade mode and the vehicle is not powered on, determine whether the vehicle network is dormant. If not, obtain the vehicle network communication data, and determine whether there is an ECU sending data when the network communication conditions are not met based on the vehicle network communication data. If so, the ECU that sends data when the network communication conditions are not met is a faulty ECU; The vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals; The method of judging whether there is an ECU sending data when the network communication conditions are not met according to the vehicle network communication data, and if so, the ECU sending data when the network communication conditions are not met is a faulty ECU, specifically: Judging whether there is an ECU that sends data without receiving a data request instruction first, according to the network management message; if so, judging whether the ECU that sends data without receiving a data request instruction first belongs to a network wake-up source ECU according to the network wake-up source signal; if not, the ECU that sends data without receiving a data request instruction first is a faulty ECU; if it is a network wake-up source ECU, judging whether there is a network wake-up source ECU that sends data without satisfying a data sending trigger condition, according to the vehicle status data; if so, the network wake-up source ECU that sends data without satisfying a data sending trigger condition is a faulty ECU; Among them, the network wake-up source signal includes a brake status signal, a remote key remote control command signal, and a door status signal, and the network wake-up source ECU includes a brake control ECU, a remote key control ECU, and a door control ECU. 2. The vehicle fault identification method according to claim 1 is characterized in that the determining whether the vehicle network is dormant is specifically: determining whether the vehicle gateway is in a state of receiving or sending network data, if so, the vehicle network is in a non-dormant state, otherwise, the vehicle network is in a dormant state; The obtaining of the whole vehicle network communication data specifically includes: the vehicle-mounted communication terminal obtaining the whole vehicle network communication data through the whole vehicle gateway. 3. The vehicle fault identification method according to claim 2, characterized in that it also includes the following steps: After the vehicle-mounted communication terminal obtains the vehicle network communication data through the vehicle gateway, it also obtains the vehicle VIN code and uploads the vehicle VIN code and the vehicle network communication data to the background server. 4. The vehicle fault identification method according to claim 3 is characterized in that it also includes the following steps: the background server determines the vehicle configuration parameters according to the vehicle VIN code, and judges whether there is an ECU sending data when the network communication conditions are not met according to the vehicle configuration parameters and the vehicle network communication data. If so, the ECU that sends data when the network communication conditions are not met is a faulty ECU. 5. A vehicle fault identification device, characterized by comprising: The network status judgment module is used to judge whether the vehicle network is dormant when the vehicle is in a non-air upgrade mode and the vehicle is not powered on. If not, it is used to judge whether the duration of the vehicle network being in a non-dormant state is greater than a preset time threshold. If so, it is used to send the vehicle network communication data to the vehicle communication terminal. A network fault judgment module is used to judge whether there is an ECU sending data when the network communication conditions are not met according to the vehicle network communication data, and if so, the ECU sending data when the network communication conditions are not met is a faulty ECU; The vehicle network communication data includes network management messages, vehicle status data, and network wake-up source signals; The network fault judgment module is specifically used for: judging whether there is an ECU that sends data without receiving a data request instruction first according to the network management message; if so, judging whether the ECU that sends data without receiving a data request instruction first belongs to a network wake-up source ECU according to the network wake-up source signal; if not, the ECU that sends data without receiving a data request instruction first is a faulty ECU; if it belongs to a network wake-up source ECU, judging whether there is a network wake-up source ECU that sends data without satisfying a data sending trigger condition according to the vehicle status data; if so, the network wake-up source ECU that sends data without satisfying a data sending trigger condition is a faulty ECU; Among them, the network wake-up source signal includes a brake status signal, a remote key remote control command signal, and a door status signal, and the network wake-up source ECU includes a brake control ECU, a remote key control ECU, and a door control ECU. 6. A vehicle fault identification system, comprising the vehicle fault identification device according to claim 5, and further comprising: A data uploading module is used to obtain the vehicle VIN code and upload the vehicle VIN code and the vehicle network communication data to the backend server; The backend server is used to determine the vehicle configuration parameters according to the vehicle VIN code, and judge whether there is an ECU sending data when the network communication conditions are not met according to the vehicle configuration parameters and the whole vehicle network communication data. If so, the ECU sending data when the network communication conditions are not met is a faulty ECU. 7. An automobile, characterized by comprising the vehicle fault identification device as claimed in claim 5. 8. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a stored computer program; wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute the vehicle fault identification method as claimed in claim 1. 9. A whole vehicle fault locating device, characterized in that it comprises a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the whole vehicle fault identification method as claimed in claim 1 when executing the computer program.