JP5040950B2 - Fault diagnosis information recording device - Google Patents

Description

  The present invention relates to a failure diagnosis information recording apparatus for recording failure diagnosis information.

  In recent years, vehicles have been electronically controlled, and a large number of ECUs (Electronic Control Units) are mounted. The ECUs are connected by a communication network (vehicle-mounted LAN). A plurality of ECUs operate in cooperation or configure a system control application. In addition, the scale of an electronic control system configured by cooperation of the plurality of ECUs is increasing.

  In such a large-scale electronic control system, it is often difficult to identify the cause of failure and elucidate the cause when a failure occurs. In particular, since an electronic control system mounted on a vehicle is used in a special environment, it may be difficult to reproduce environmental conditions when a failure occurs. Since environmental conditions cannot be reproduced, phenomena cannot be reproduced, and failure diagnosis and analysis may not be possible.

  Conventionally, in order to support failure diagnosis and analysis in an ECU mounted on a vehicle, it has been devised to store failure diagnosis information in a memory in the ECU. However, an ECU mounted on a vehicle often has a limited memory capacity (memory size) for reasons such as cost.

  Therefore, Patent Document 1 discloses an automotive diagnostic data management system that can store failure diagnosis information reliably and efficiently even in a memory with limited capacity. This automotive diagnostic data management system temporarily stores time-sequentially created diagnostic data in the buffer memory on the RAM while temporarily updating it, while the diagnostic data on the buffer memory is updated by overwriting, etc. In order to prevent this from happening, it is transferred to a non-volatile memory, and is read from the non-volatile memory and used whenever necessary for failure analysis or the like. At this time, instead of transferring the diag data sent to the buffer memory to the non-volatile memory without limitation, a specific reaction operation by the user is determined in advance when the electronic device does not operate as expected by the user. Only when the specific reaction operation is detected, the diagnostic data in the buffer memory is transferred to the non-volatile memory to determine the storage.

JP 2006-309511 A

  However, in the diagnostic data management system for automobiles disclosed in Patent Document 1, failure diagnosis information (diag data) corresponding to an environmental condition when a failure occurs is stored among environmental conditions that change every moment. It has not been done.

  By the way, the communication record in the in-vehicle LAN as described above is very effective as information for performing failure diagnosis and analysis, and plays an important role. However, the information indicating this communication record is a huge amount of data. Further, as described above, the memory capacity is limited. Therefore, all communication records cannot be recorded in the memory.

  The present invention has been made in view of the above problems, and can appropriately and efficiently record information indicating communication records of the in-vehicle LAN when a failure occurs and failure diagnosis information corresponding to environmental conditions. An object of the present invention is to provide a fault diagnosis information recording apparatus capable of performing the above.

In order to achieve the above object, the failure diagnosis information recording apparatus according to claim 1 comprises:
Connected to at least one in-vehicle LAN, and when receiving a fault diagnosis code from an electronic control device connected to the in-vehicle LAN, records fault diagnosis information used for fault diagnosis and analysis corresponding to the fault diagnosis code A fault diagnosis information recording device comprising:
Information and failure including failure diagnosis code, conditions for determining whether failure diagnosis information needs to be recorded for each failure diagnosis code, and communication record of in-vehicle LAN related to failure corresponding to failure diagnosis code A table associated with a recording target indicating information to be recorded as failure diagnosis information among information corresponding to environmental conditions when
Code receiving means for receiving a fault diagnosis code output from an electronic control device connected to the in-vehicle LAN;
Condition determining means for determining whether or not the condition of the vehicle satisfies a condition associated with the failure diagnosis code received by the code receiving means in the table;
If the condition determination means determines that the condition is satisfied, a recording means for recording information to be recorded associated with the failure diagnosis code received by the code reception means in the table as failure diagnosis information;
It is characterized by providing.

  Thus, by recording information indicating the communication record of the in-vehicle LAN and information corresponding to the environmental condition when the failure occurs as failure diagnosis information, which is related to the failure corresponding to the received failure diagnosis code. Fault diagnosis information suitable for fault diagnosis and analysis can be recorded as much as necessary. In addition, since the environmental conditions at the time of the failure can be narrowed down, the phenomenon (failure) can be easily reproduced. Therefore, the accuracy of failure diagnosis and analysis using the failure diagnosis information can be improved.

  Furthermore, the failure diagnosis information can be recorded only when necessary by recording the failure diagnosis information only when the vehicle condition satisfies the condition associated with the received failure diagnosis code. That is, it is possible to appropriately and efficiently record information indicating the communication record of the in-vehicle LAN when a failure occurs and failure diagnosis information corresponding to the environmental conditions.

  In addition, as shown in claim 2, information indicating a recording time corresponding to a failure corresponding to the failure diagnosis code is associated with the table for each piece of information indicating the communication record of the in-vehicle LAN that is a recording target. It may be.

  As described above, by including information related to the recording time of the information indicating the communication record of the in-vehicle LAN corresponding to the failure corresponding to the failure diagnosis code, the information indicating the communication record of the in-vehicle LAN is recorded as much as necessary. Can do.

  Further, as shown in claim 3, for each piece of information indicating the communication record of the in-vehicle LAN that is a recording target, information indicating the transmission source ECU corresponding to the failure corresponding to the failure diagnosis code is associated with the table. You may do it.

  By associating information indicating the transmission source ECU in this way, it is possible to further improve the accuracy of failure diagnosis and analysis using the failure diagnosis information.

It is a block diagram which shows schematic structure of navigation ECU in embodiment of this invention. It is a flowchart which shows the recording process of the diagnostic information of navigation ECU in embodiment of this invention. It is an image figure which shows schematic structure of the table in embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, an example in which the failure diagnosis information recording apparatus of the present invention is applied to a navigation ECU (Electronic Control Unit) mounted on a vehicle will be described.

  As shown in FIG. 1, the navigation ECU 10 is connected to the first in-vehicle LAN, the second in-vehicle LAN, and the third in-vehicle LAN, and the ECUs 10 to 70 connected to the first to third in-vehicle LANs. When a failure diagnosis code (hereinafter also referred to as a diagnosis code) is received from any one of them, failure diagnosis information (hereinafter also referred to as diagnosis information) used for diagnosis and analysis of a failure corresponding to the diagnosis code is recorded. The first to third in-vehicle LANs are a control system LAN, a body system LAN, and the like. The first in-vehicle LAN includes the navigation ECU 10, the ECU 20, and the ECU 30. The second in-vehicle LAN includes the navigation ECU 10, ECU 40, and ECU 50. The third in-vehicle LAN includes the navigation ECU 10, ECU 60, and ECU 70. In addition, if ECU20-70 detects a failure (abnormality), it will output the diagnostic code which is a code preset according to the kind, location, etc. of the failure (abnormality) to vehicle-mounted LAN.

  In the present embodiment, the navigation ECU 10 will be described using an example in which it is connected to three in-vehicle LANs (first to third in-vehicle LANs), but the present invention is not limited to this. The object of the present invention can be achieved if it is connected to at least one in-vehicle LAN. Further, the number of ECUs included in the first to third in-vehicle LANs is not particularly limited.

  As shown in FIG. 1, the navigation ECU 10 includes a CPU 1, an RTC (real time clock) 2, a gyro sensor 3, a GPS receiver 4, an antenna 4a, a video input processing unit 5, a camera 5a, an HDD 6, a ROM 7, a RAM 8, and an I / F. (Interface) 9 and the like.

  The CPU 1 reads out the program stored in the ROM 7, receives signals from the RTC 2, the gyro sensor 3, the GPS receiver 4, the video input processing unit 5 and the external (first to third in-vehicle LANs) input via the I / F 9. A predetermined arithmetic process is executed using signals from the ECUs 20 to 70) connected to the CPU 20 and data stored in the HDD 6 and ROM 7, and a route search process, a vehicle situation determination process, etc. are performed while saving the process result in the RAM 8. Execute. Further, the CPU 1 performs processing for recording diagnostic information, which is a feature of the present invention. This diag information recording process will be described in detail later.

  The RTC 2 counts the current time and inputs the counted current time to the CPU 1.

  The gyro sensor 3 inputs data for detecting the position of the host vehicle to the CPU 1. The gyro sensor 3 detects the angular velocity of the vehicle when the direction of the vehicle is changed, and inputs the angular velocity data and the relative bearing data to the CPU 1.

  The GPS receiver 4 receives radio waves for detecting the current position of the vehicle from a plurality of GPS satellites via the antenna 4 a and inputs them to the CPU 1.

  The video input processing unit 5 inputs video data captured by the camera 5 a to the CPU 1. The camera 5a captures, for example, the vicinity of the vehicle.

  The HDD 6 associates a map data, a condition for determining whether or not a diagnosis code and diagnosis information need to be recorded (recording determination condition), and a recording target (recording content) indicating information to be recorded as the diagnosis information. The attached table or the like is stored. In other words, this table shows a recording method of diag information linked to a diag code. The HDD 6 records diagnosis information based on an instruction from the CPU 1.

  Here, the table stored in the HDD 6 will be described with reference to FIG. FIG. 3 is an image diagram illustrating an example of a table. This table is stored in the HDD 6 in advance.

  The table may be updated as appropriate. In this case, for example, the navigation ECU 10 is provided with a communication unit that performs communication with the outside. And it can achieve by updating by communication from a dedicated update terminal capable of communicating with a communication unit provided in the navigation ECU 10, a mobile phone, or a center.

  The diagnosis code is a code set in advance depending on the type or location of failure (abnormality).

  The condition for determining whether or not the diagnosis information needs to be recorded is set for each diagnosis code based on the situation of the vehicle. For example, this condition (vehicle situation) can be set based on past defect extraction results, non-reproduction failures, and the like.

  The situation of the vehicle is related to a failure corresponding to the diagnosis code. Specifically, the situation of the vehicle includes, for example, situations such as an in-vehicle environment, a vehicle behavior, and a traveling environment. The situation related to the in-vehicle environment includes image ID information, a reproduced video type, a reproduced audio type, and other variables used inside the ECU for other operations and controls. The situation related to the vehicle behavior includes running, stopping, reverse, turning and the like. Conditions related to the driving environment include location, general roads, expressways, tunnels, and bridges. The failure corresponding to the diag code is, in other words, a failure (abnormality) that triggers the output of the diag code.

  The recording target indicating the information to be recorded as the diag information is information including the communication record of the in-vehicle LAN related to the failure corresponding to the diag code and the transmission source ECU of the diag code, and the information corresponding to the environmental condition when the failure occurs. Of these, information to be recorded as diagnostic information is shown. The information corresponding to the environmental conditions refers to information indicating the above-mentioned conditions related to the in-vehicle environment, the vehicle behavior, and the driving environment. In other words, what information is recorded as diag information for each diag code. Is shown.

  Moreover, you may link | link the information which shows the recording time according to the failure corresponding to a diagnosis code | cord | chord for every information which shows the communication recording of the vehicle-mounted LAN which is a recording object. That is, information indicating how long the communication record of the in-vehicle LAN is recorded may be associated. As described above, by including the information related to the recording time of the information indicating the communication record of the in-vehicle LAN corresponding to the failure corresponding to the diagnosis code, the information indicating the communication record of the in-vehicle LAN can be recorded as much as necessary. it can.

  Furthermore, information for limiting the communication record of the in-vehicle LAN to be recorded by the transmission source ECU according to the failure corresponding to the diagnosis code may be associated. That is, not all the in-vehicle LAN communication records are to be recorded, but only the communication records transmitted from a specific transmission source ECU are to be recorded, so that information indicating the in-vehicle LAN communication records is further required. Only minutes can be recorded.

  As described above, the information to be recorded (diag information) includes information on the connection LAN including the communication record of the in-vehicle LAN related to the failure corresponding to the diagnosis code, and the failure when the failure corresponding to the diagnosis code occurs. Information corresponding to relevant environmental conditions. In other words, the diagnosis information is information necessary for failure diagnosis and analysis of a failure corresponding to each diagnosis code. Note that the diagnosis information for each diagnosis code can be set based on past defect extraction results, non-reproducible defects, and the like.

  Specifically, as illustrated in FIG. 3, the diagnosis information includes information about the connection LAN, information about the source, information about the signal, information about the traveling environment, and the like. Moreover, the information regarding connection LAN contains the information which shows the communication record of vehicle-mounted LAN relevant to the failure corresponding to a diagnosis code, the information which shows object ECU (transmission origin ECU of a diagnosis code), etc. The information regarding the source includes information indicating the playback video type, information indicating the playback audio type, and the like. The information related to the signal includes information indicating the value of the power supply voltage, information indicating detection signals (various signals) from various sensors, and the like. The information on the traveling environment is an environment in which the vehicle was traveling at the time of diag code output, and includes information indicating the position, road type, inside the tunnel, and on the bridge.

  For example, in the diagnosis code D1234, information indicating that the vehicle is traveling in a general road tunnel as a condition for recording the diagnosis information, information indicating that the transmission source of the diagnosis code is the ECU 20 as information recorded as the diagnosis information, Information indicating communication records of the first to third in-vehicle LANs for 15 seconds before and after the output of the code, information indicating the reproduction audio type, information indicating the reproduction audio type, information indicating the value of the power supply voltage, information indicating various signals, Information indicating the position of the vehicle, the type of road on which the vehicle exists, and information indicating that the vehicle is in a tunnel is associated.

  The ROM 7 stores programs executed by the CPU 1 and fixed data. The above table may be stored in the ROM 7.

  The RAM 8 temporarily stores the calculation result of the CPU 1 and the like. The I / F 9 is an interface with the first to third in-vehicle LANs and the vehicle speed sensor 80. The vehicle speed sensor 80 is a sensor that sequentially detects the vehicle speed, which is the speed of the host vehicle, and sequentially inputs information on the detected vehicle speed to the navigation ECU 10 (CPU 1).

  Here, the diagnosis information recording process of the navigation ECU 10 will be described with reference to the flowchart shown in FIG. The flowchart shown in FIG. 2 starts when a diagnostic code is received (code receiving means) from any of the first to third vehicle-mounted LANs to which the navigation ECU 10 is connected. The navigation ECU 10 itself starts in the same manner when the abnormality is detected inside and a diagnosis code is generated. That is, when any of the ECUs 20 to 70 connected to the first to third vehicle-mounted LANs detects a failure (abnormality), a diagnostic code defined in advance by the ECU is generated and output to the vehicle-mounted LAN. The operation starts when the navigation ECU 10 receives the diagnosis code.

  In step S10, the CPU 1 of the navigation ECU 10 identifies the received diagnostic code. The CPU 1 of the navigation ECU 10 temporarily stores the received diagnostic code in the RAM 8. The received diagnostic code is identified from the table stored in the HDD 6.

  In step S11, the CPU 1 of the navigation ECU 10 proceeds to step S12 when determining that the received diagnostic code is present in the table, and ends the process when determining that it is not present in the table. If the received diagnostic code does not exist in the table, there may be an abnormality in the table, ECU that output the diagnostic code, in-vehicle LAN, etc. This may be notified to the user.

  In step S12, the CPU 1 of the navigation ECU 10 determines the vehicle status indicated by the condition in order to determine whether the vehicle status satisfies the condition associated with the diagnostic code received in the table ( Condition determination means). At this time, the CPU 1 of the navigation ECU 10 receives the signals from the gyro sensor 3, the GPS receiver 4, the video input processing unit 5 and the external input via the I / F 9 (the ECU 20 connected to the first to third in-vehicle LANs). ˜70, based on the signal from the vehicle speed sensor 80), the vehicle status is detected. In step S13, the CPU 1 of the navigation ECU 10 determines whether or not the condition of the vehicle satisfies a condition associated with the received diagnostic code. If it is determined that the condition is satisfied, the process proceeds to step S14. Terminates the process (condition determining means). That is, the CPU 1 of the navigation ECU 10 determines whether or not the condition of the vehicle satisfies a condition associated with the received diagnostic code (condition determining means).

  In step S14, the CPU 1 of the navigation ECU 10 records information to be recorded associated with the diag code received in the table in the HDD 6 as diag information (recording means).

  For example, when the diagnosis code D1234 is received, the CPU 1 of the navigation ECU 10 detects the state of the vehicle and determines whether or not the vehicle is traveling in a general road tunnel. When the CPU 1 of the navigation ECU 10 determines that the vehicle is traveling in a tunnel on a general road, the communication records of the first to third in-vehicle LANs 15 seconds before and after the output of the diagnosis code, and the ECU 20 and the ECU 40 , Information indicating that the ECU 60 is a transmission source, information indicating a reproduction sound type, information indicating a reproduction sound type, information indicating a value of a power supply voltage, information indicating various signals, a position where the vehicle travels, a road type, Information indicating that it is in the tunnel is recorded in the HDD 6 as diagnostic information.

  As described above, the information related to the failure corresponding to the received diag code is recorded as the diag information by recording the information indicating the communication record of the in-vehicle LAN and the information corresponding to the environmental condition when the failure occurs. Diagnostic information appropriate for diagnosis and analysis can be recorded as much as necessary. In addition, since the environmental conditions at the time of the failure can be narrowed down, the phenomenon (failure) can be easily reproduced. Therefore, the accuracy of failure diagnosis and analysis using the diagnosis information can be improved. Furthermore, the diag information can be recorded only when necessary by recording the diag information only when the condition of the vehicle satisfies the condition associated with the received diag code. That is, it is possible to appropriately and efficiently record information indicating the communication record of the in-vehicle LAN when a failure occurs and diagnostic information corresponding to the environmental conditions.

  10 navigation ECU, 1 CPU, 2 RTC, 3 gyro sensor, 4 GPS receiver, 4a antenna, 5 video input processing unit, 5a camera, 6 HDD, 7 ROM, 8 RAM, 9 I / F, 20-70 ECU

Claims (3)

When it is connected to at least one vehicle-mounted LAN and receives a failure diagnosis code from an electronic control device connected to the vehicle-mounted LAN, failure diagnosis information used for failure diagnosis and analysis corresponding to the failure diagnosis code is obtained. A failure diagnosis information recording device for recording,
The failure diagnosis code, a condition for determining whether or not the failure diagnosis information needs to be recorded for each failure diagnosis code, and the communication record of the in-vehicle LAN related to the failure corresponding to the failure diagnosis code And a table associated with a recording target indicating information to be recorded as the failure diagnosis information among information corresponding to environmental conditions at the time of occurrence of the failure,
Code receiving means for receiving the fault diagnosis code output from the electronic control device connected to the in-vehicle LAN;
Condition determining means for determining whether or not a vehicle condition satisfies a condition associated with the failure diagnosis code received by the code receiving means in the table;
If the condition determining means determines that the condition is satisfied, a recording means for recording information to be recorded associated with the failure diagnosis code received by the code receiving means in the table as the failure diagnosis information;
A failure diagnosis information recording apparatus comprising:   2. The table is associated with information indicating a recording time corresponding to a failure corresponding to the failure diagnosis code for each piece of information indicating a communication record of the in-vehicle LAN that is a recording target. The failure diagnosis information recording device according to claim 1.   The information indicating a transmission source ECU corresponding to a failure corresponding to the failure diagnosis code is linked to the table for each piece of information indicating a communication record of the in-vehicle LAN that is a recording target. The failure diagnosis information recording apparatus according to 1 or 2.

Images