JP4872417B2 - In-vehicle data recorder and data recording method - Google Patents

Description

  The present invention relates to an in-vehicle data recorder that records various data of electronic control conditions relating to the running state of a vehicle and is used for fault diagnosis and investigation of the cause of an accident.

  For example, a vehicle drive recorder or an in-vehicle data recorder used for fault diagnosis and investigation of the cause of an accident is known in which a vehicle that is running is equipped with a control device that captures various types of vehicle data such as vehicle travel control, engine control, and continuous transmission control. Each of these control devices can be connected to an external diagnostic device for diagnosing abnormal operation of each part of the vehicle from the various vehicle control data (for example, Patent Document 1 and Patent Document 2 below). However, according to the apparatus having such a configuration, it is necessary to determine recording data corresponding to the type and number of control apparatuses that are different for each vehicle, create respective recording processing programs, and record them in the drive recorder. There was a problem that the work man-hours became enormous.

  In order to solve the above problem, in Patent Document 3 below, a vehicle drive for storing a communication procedure and communication contents when collecting vehicle data between a control device mounted on the vehicle and an external diagnostic device. A recorder is connected, the stored communication procedure and communication contents are transferred to an external diagnostic device, and the external diagnostic device collects vehicle control information from the control device and performs an abnormality diagnosis of the device. As a result, the collected data is determined corresponding to the type and number of control devices that are different for each vehicle, which has been required in the past, and a recording processing program for these collected data is created and stored in advance in a data recorder serving as a drive recorder. There has been disclosed a vehicle drive recorder that eliminates the need for work to be performed and automatically determines collected data in accordance with the type and number of control devices.

In particular, in the case of Patent Document 3, when an in-vehicle data recorder performs an abnormality diagnosis after acquiring data, the in-vehicle data recorder is connected to the in-vehicle data recorder to collect control information of each control device. It is necessary to manually switch from this line to an external diagnostic device. Here, the same identifier as that of the control device mounted on the vehicle is used for communication between the external diagnostic device and the in-vehicle data recorder. For this reason, when an external diagnostic device is connected without performing this switching operation, data for communication transmitted from the external diagnostic device is mixed with data recorded by the in-vehicle data recorder, and accurate data recording is guaranteed. There was a problem that disappeared.
Japanese Unexamined Patent Publication No. 7-37133 JP-A-8-235491 JP 2001-266199 A

  In order to solve the above-mentioned problem, in the present invention, the in-vehicle data recorder capable of automatically switching the in-vehicle data recorder when the external diagnostic apparatus is connected without causing such a mixture of data, and data recording related thereto The purpose was to provide a method.

In order to achieve the above object, the present invention has the following configuration as a basic configuration.
That is, the plurality of electronic control units drive the LAN that is connected-vehicle data recorder one is connected via a first cable, in the I from the first cable to the second cable Rikuruma branches the LAN output, thereby enabling a connection to the external diagnostic device that diagnoses the control information from the electronic control device connected to the vehicle LAN.
In this configuration, an identifier dedicated to the in-vehicle data recorder is set, and this dedicated identifier is different from the identifier set before the communication message from the external diagnostic device, thereby avoiding data confusion in the in-vehicle data recorder. Yes.

In claim 1 of the present invention, an identifier (i.e., ID) for recording the control information from the electronic control device connected to the car in the LAN to one vehicle data recorder, which like the control of the electronic control device In order to diagnose information, an identifier attached to data from an external diagnostic device connected outside the vehicle is set to a different ID.
In other words, when the external diagnostic device performs one-to-one communication with each electronic control device, a dedicated ID is set for each of the plurality of electronic control devices. Similarly, the in-vehicle data recorder communicates with each of the plurality of electronic control devices. When performing, it is characterized in that an ID different from that of the external diagnostic apparatus is set.
As a result, the separation of data from the external diagnostic device is clarified, and accurate communication messages can be transmitted and received without mixing data.

  The present invention will be described below with reference to the drawings. FIG. 1 shows a basic configuration of an in-vehicle data recorder 1 according to the present invention. In FIG. 1, the central processing unit 10 is monitored for power supply status by a power supply monitoring circuit 11. The central processing unit 10 is connected to a volatile memory 12 and a non-volatile memory 13, and data serving as information relating to the vehicle control state is transmitted to the in-vehicle LAN 2 and the in-vehicle LAN 3 shown in FIG. The data is taken into the central processing unit 10 via the bidirectional communication IF (interface) 15.

  FIG. 2 shows the configuration of the entire in-vehicle system for vehicle control monitoring using the in-vehicle data recorder 1 according to the present invention. The in-vehicle LAN 2 and the in-vehicle LAN 3 are shown as a plurality of networks in the vehicle 4. 2, five electronic control devices (hereinafter referred to as control devices) 21, 22, 23, 24, 25 and 31, 32, 33, 34, 35 are connected to two in-vehicle LAN 2 and in-vehicle LAN 3, respectively. Thus, data is collected regarding information on various vehicle control states during traveling such as vehicle traveling control data and engine control data. Each data from the control devices 21 to 25 and 31 to 35 is input to the in-vehicle data recorder 1 via the cables 61 and 71 and simultaneously branched by the cables 611 and 711 and taken out to the outside via the connector 81. Are input to the external diagnostic apparatus 5 that can be connected via the cables 62 and 72 and the connector 82.

  FIG. 3 is a state transition diagram showing the transition of the basic operation and operation mode of the in-vehicle data recorder 1 according to the present invention. First, the in-vehicle data recorder 1 transits to the initial diagnosis mode S101 in response to a power-on reset that causes a system reset by turning on the power switch or turning on the ignition switch (IGN ON) or a reset request S100 from the external diagnostic device 5. In this initial diagnosis mode S101, the initial state of the in-vehicle data recorder 1 is checked, that is, the registers (not shown) built in the central processing unit 10, the volatile memory 12, the nonvolatile memory 13, and the registers (not shown) of the bidirectional interfaces 14 and 15 are checked. Diagnose each of them for abnormal operation.

  If the operations of the registers (not shown) built in the central processing unit 10, the volatile memory 12, the non-volatile memory 13, and the registers (not shown) of the bidirectional interfaces 14 and 15 are all normal, a transition is made to the recording mode S102. In the recording mode S102, the in-vehicle data recorder 1 includes the control devices 21, 22, 23, 24, and 25 connected to the in-vehicle LAN 2 and the control devices 31, 32, 33, 34, and 35 connected to the in-vehicle LAN 3, respectively. Communication is performed sequentially on a one-to-one basis. Thus, the data of each electronic control device is recorded in the in-vehicle data recorder 1 by receiving the response in response to the data transmission request related to the control state information transmitted from the central processing unit 10.

  The received data is temporarily recorded in the volatile memory 12, and for example, a condition for transferring the data stored in the volatile memory 12 to the nonvolatile memory 13, such as checking that there is no data error or address error, is established. Data transfer between the memories. Here, a data transmission request for acquiring data from the control devices 21, 22, 23, 24, 25 connected to the in-vehicle LAN 2 and the control devices 31, 32, 33, 34, 35 connected to the in-vehicle LAN 3 It is assumed that conditions for transferring data from the volatile memory 12 to the nonvolatile memory 13 are set in the in-vehicle data recorder 1 in advance.

  Further, in the initial diagnosis mode S101, any one of the registers (not shown) incorporated in the central processing unit 10, the volatile memory 12, the nonvolatile memory 13, and the registers (not shown) incorporated in the bidirectional interfaces (IF) 14 and 15 is abnormal. In some cases, the data from the control devices 21 to 25 and 31 to 35 is not recorded in the in-vehicle data recorder 1, and the external diagnostic device communication mode S <b> 103 is entered. Do.

  FIG. 4 is a flowchart for explaining the operation of the initial diagnosis mode S101 in FIG. In FIG. 4, in the initial diagnosis mode S <b> 101, first, the presence or absence of a failure in the central processing unit 10, the volatile memory 12, the nonvolatile memory 13, and the bidirectional interfaces (IF) 14 and 15 mounted on the in-vehicle data recorder is checked. (Step S200). Following this failure diagnosis, all of the registers built in the central processing unit 10, the volatile memory 12, the nonvolatile memory 13, and the bidirectional interfaces 14 and 15 are checked for abnormal operation. Here, if there is no abnormality (step S201: NO), the recording mode S102 is entered, and control state data collection is started from the control devices 21 to 25 and 31 to 35 connected to the in-vehicle LAN 2 and the in-vehicle LAN 3. (Step S202). Also, if an operation abnormality is found (step S201: YES), the fact that there is an abnormality is recorded in the nonvolatile memory 13 as an error log (step S203), and thereafter, transition is made to the external diagnostic device communication mode S103 in FIG. (Step S204). Here, in the present invention, whether or not the external diagnostic apparatus 5 is connected is automatically recognized, so that the confirmation process for the connection of the external diagnostic apparatus 5 is not particularly necessary for this mode transition.

Each of the transmission process of FIG. 5 and the reception process of FIG. 6 is a flowchart showing the processing procedure of the data transmission / reception process executed in the recording mode S102 of FIG. 1. First, the transmission process of FIG.
Data transmission request for acquiring data from the control devices 21, 22, 23, 24, 25 connected to the in-vehicle LAN 2 and the control devices 31, 32, 33, 34, 35 connected to the in-vehicle LAN 3 in FIG. Is performed at a predetermined fixed period, and this period is monitored by a timer. When this timer times out, the timing of a predetermined period is reached (step S300: YES), and data acquisition from each control device is started. To do. At this time, it is first checked whether the network (LAN) is overloaded. The network load state, that is, whether or not the communication frequency in the network before the current time is equal to or greater than a predetermined amount of data is checked by a flag indicating the network load state.

  That is, when the in-vehicle data recorder 1 sequentially performs one-on-one diagnostic communication with each of the plurality of electronic control devices, the diagnostic communication is performed while monitoring the network load that is the frequency of communication information existing on the in-vehicle LAN. It is configured to control the frequency of data recording by.

  Here, if the flag is 0 (step S301: YES), communication via the network is possible, so the in-vehicle data recorder 1 sequentially transmits a data transmission request signal to each control device (step S302) Data from each of the control devices 21 to 25 and 31 to 35 is acquired. Further, if the flag is 1 (step S301: NO), it indicates that the in-vehicle LAN 2 or 3 is in an overload state, and therefore data communication cannot be performed. Therefore, measurement is performed to confirm the load state of the network without issuing a data transmission request (step S303). Even when a data transmission request is issued in step S302, it is checked whether the in-vehicle LAN 2 or 3 is overloaded by fetching new data (step S303).

  The measurement result in step S303 is used to determine whether or not the upper limit of the communication amount set for the in-vehicle LAN 2 or 3 is exceeded. If not (step S304: NO), the in-vehicle LAN 2 or 3 is determined. The network load over flag is set to 0 to end this series of processing, return to (Start), and enter the standby state for the next processing. If the network load exceeds the upper limit value in step S304 (step S304: YES), this indicates that the network is overloaded by reading new data. A series of processing ends, and the process returns to (start) and enters a standby state for the next processing. In this case, it means that the flag indicating overload in the in-vehicle LAN is 1 in the next processing, and therefore the loop of step S301: NO is followed. That is, when the in-vehicle data recorder 1 communicates with each of the control devices 21 to 25 and 31 to 35 on a one-to-one basis, the diagnostic communication is performed while monitoring the frequency of communication information existing on the in-vehicle LAN 2 or 3, that is, the network load. The frequency of data recording by was controlled. As a result, communication errors due to data overload in the in-vehicle LAN 2 or 3 can be suppressed.

  In step S300, if the timer has not reached the time-out state (step S300: NO), it indicates that it is not the time to transmit the data transmission request. Return to the state of (start) via, and wait for the next timeout, that is, wait until the timing of the data transmission request.

  FIG. 6 is a flowchart showing a procedure of reception processing executed in the recording mode 102 in FIG. When data from the control devices 21 to 25 and 31 to 35 respectively connected to the in-vehicle LAN 2 and the in-vehicle LAN 3 is transferred to the in-vehicle data recorder 1, the in-vehicle data recorder 1 interrupts data reception (step S400). . Here, if the data has not arrived (step S400: NO), the reception process is not performed, the process returns to (start) through (end), and enters the data arrival standby state.

  When the data arrives and the received data is interrupted (step 400: YES), the process proceeds to step 401, where the ID (identifier) set in the received data is first checked. It is confirmed whether or not data within the range of the hexacode display (0x700 to 0x7FF) assigned as a standard for communication in the in-vehicle LAN 3 is received.

  If ID data within the above range is not received (step S401: NO), the data is out of the target and is not subject to diagnosis by the external diagnostic device 5. The process is terminated only by recording in the volatile memory 12 having the function as a reception buffer without sending it out (step S404), and the next reception interrupt is waited. This data recorded in the reception buffer is overwritten when data that does not satisfy the above condition (step S401: NO) among subsequent data to be input next time is received.

  When data having an ID within the above range is received (step S401: YES), the control device 21 for in-vehicle LAN 2 from the external diagnostic device 5 that the in-vehicle data recorder 1 has for the ID of this received data. 22, 22, 23, 24, 25 and the in-vehicle LAN 3 control devices 31, 32, 33, 34, and 35, a comparison list is made with reference to a list of IDs for transmitting data transmission requests, ie, data transmission request ID lists S402). Here, in step S402 of FIG. 6, C / U indicates the plurality of control devices. As a result of this comparison and reference, if the ID of the received data is present in the data transmission request ID list (step S403: YES), it indicates that the external diagnostic device 5 is connected, so communication with the external diagnostic device 5 is performed. A transition is made to the mode (step S405), a series of processing is (finished), and the processing returns to (start) and waits for the next reception interrupt. If the ID of the received data does not exist in the data transmission request ID list as a result of the comparison and reference (step S403: NO), the data is stored in the volatile memory 12 that is the buffer memory of the received data together with the ID. Keep it. This data is overwritten and stored with the subsequent data, and the reception process is terminated (finished), returning to (start) and waiting for the next reception interrupt.

From the above configuration, there are the following two methods for setting IDs for the in-vehicle data recorder 1 and the external diagnostic device 5. That is,
(First setting method)
The control devices 21 to 25 and 31 to 35 for detecting the control state of the vehicle and transmitting the detected data are connected in common to the two in-vehicle LANs 2 and 3, respectively. In one in-vehicle data recorder 1 capable of recording the control state of each control device, the two in-vehicle LANs 2 and 3 and the in-vehicle data recorder 1 are connected by two cables 61 and 71, respectively. Yes. These cables 61 and 71 branch to the external diagnostic device 5 that collects control information from each of the control devices and diagnoses an abnormality with the other two cables 611 and 711, and includes a connector 81, a cable 62, 72 and the connector 82 can be connected. When the in-vehicle data recorder 1 performs diagnostic communication on the control state of the vehicle one by one with each of the plurality of control devices connected to the two in-vehicle LANs, data from the plurality of control devices Is set before the communication message from the external diagnostic device 5, and an identifier for communication is set before each communication message including It is assumed that the identifier is different.

(Second setting method)
When the vehicle-mounted control devices 21 to 25 and 31 to 35 communicate with the external diagnostic device 5, it is assumed that the following IDs are set in advance for each communication direction. Here, the ECU indicates an electronic control device, and numerals 1, 2,... Are numbers sequentially assigned corresponding to the reference numerals 21-25 and 31-35 attached to the control device in FIG. Further, h represents a hexacode.

External diagnostic device → ECU 1: 701h, ECU1 → External diagnostic device: 741h
External diagnostic device → ECU 2: 702h, ECU 2 → External diagnostic device: 742h
When the ID as described above is set, the function switching of the in-vehicle data recorder is performed according to any of the following conditions.

・ When an on-board data recorder detects an external diagnostic device ID that is not transmitted ・ When an abnormality is detected during the self-diagnosis function or initial diagnosis ・ The communication frequency on the network is greater than a predetermined value, When it becomes an overload state When none of these vehicle data recorder switching conditions is satisfied, the vehicle data recorder 1 will collect data from the control devices connected to the in-vehicle LANs 2 and 3,
In-vehicle data recorder → ECU1: 701h,
ECU1 → In-vehicle data recorder: 741h
In-vehicle data recorder → ECU 2: 702h,
ECU2 → In-vehicle data recorder: 742h
Thus, the in-vehicle data recorder 1 and the external diagnostic device 5 collect data from each control device with the same ID. In this case, the in-vehicle data recorder 1 collects data using the same ID instead of the external diagnostic device 5.

That is, it is connected in common via two cables 61 and 71 to two in-vehicle LANs 2 and 3 to which a plurality of electronic control devices that detect the control state of the vehicle and send out the detected data are respectively connected. In the in-vehicle data recorder 1 capable of recording the control states of the plurality of electronic control devices 21 to 25 and 31 to 35, the two in-vehicle LANs 2 and 3 are connected to the in-vehicle data recorder 1. The two cables 61 and 71 to be connected are branched by the other two cables 611 and 711, and the plurality of electronic control devices 21 to 25 and 31 to 35 are connected via the other two cables 611 and 711. An external diagnostic device 5 that collects data from and diagnoses an abnormality can be connected via a connector. If the Tarekoda 1 performs diagnostic communication in sequential one-to-one and one by one of the plurality of electronic control devices 21 to 25 and 31 to 35, the communication before the communication message including the data from the plurality of electronic control units Set a dedicated identifier before the communication message of the in-vehicle data recorder 1, and set the same identifier as the dedicated identifier in the in-vehicle data recorder 1 also in the communication message of the external diagnostic device 5. When the external diagnostic device 5 is connected to the two in-vehicle LANs 2 and 3 and the in-vehicle data recorder 1, the in-vehicle data recorder 1 receives data from the electronic control devices 21 to 25 and 31 to 35. The collection was stopped.

  In addition, after detecting the connection of the external diagnostic device 5, the in-vehicle data recorder 1 stops collecting data until it is turned on after the next ignition is turned off, and the data is turned on when the next ignition is turned on or the power is turned on. Collection is resumed. That is, in the in-vehicle data recorder 1, when collecting data from various electronic control devices using the same identifier as that used by the external diagnostic device 5, after detecting the connection of the external diagnostic device 5, from the next ignition off Until the process of turning on, the data collection is stopped and the data collection is resumed by the next ignition on or power on.

  This configuration eliminates the need for a special tool or switch for returning the function after the data collection is stopped and restarting the data collection. Further, with this configuration, it is not necessary to set a dedicated ID for communicating with the external diagnostic device 5 or the in-vehicle data recorder 1, and the data processing procedure can be simplified.

Moreover, since the on-board data recorder function switching condition is established, the external diagnostic device 5 is connected,
External diagnostic device → in-vehicle data recorder: 7C1h
In-vehicle data recorder → external diagnostic device: 7F1h
As seen from the external diagnostic device 5, the in-vehicle data recorder 1 functions as one of the control devices connected to the in-vehicle LANs 2 and 3.

  With the above configuration, it is possible to automatically detect that the external diagnostic device 5 is connected from the ID list collation, and to handle the in-vehicle data recorder in the same row as other in-vehicle electronic control devices. In addition, since the data of each electronic control device can be intensively stored by the in-vehicle data recorder 1, the memory in each control device can be reduced. Furthermore, the present configuration makes it possible to diagnose an abnormality without impairing the function of the external diagnostic device 5 or modifying it, and the present invention can be easily applied to any vehicle.

  In the above embodiment, the case in which the in-vehicle LAN has two systems has been described. However, this configuration can be applied to two or more systems.

The block diagram which shows the basic composition of this invention. Connection diagram of in-vehicle system including in-vehicle data recorder. The state transition diagram explaining the operation mode in this invention. The processing flowchart in an initial diagnosis mode. The processing flowchart of a transmission process. The processing flowchart of a reception process.

Explanation of symbols

1: In-vehicle data recorder 2: In-vehicle LAN
3: In-vehicle LAN 4: Vehicle 5: External diagnostic device 10: Central processing unit 11: Power monitoring circuit 12: Volatile memory 13: Non-volatile memory 14, 15: Bidirectional communication interface 21, 22, 23, 24, 35, 31, 32, 33, 34, 35:
Electronic control device 61, 62, 71, 72: Cable 81, 82: Connector

Claims (8)

Detecting the control state of the vehicle, an electronic control unit for sending the data the detected relative drive the LAN that is connected few cars double, are connected via a first cable, the plurality of electronic control In one in-vehicle data recorder capable of recording the control state of each device,
Branched from the first cable connecting the front Symbol car within LAN to the in-vehicle data recorder by the second cable, the abnormality diagnosis to collect data from the plurality of electronic control unit via the second cable Can be connected via a connector,
When the in-vehicle data recorder performs diagnostic communication regarding the control state of the vehicle one by one with each of the plurality of electronic control devices , a communication message regarding the vehicle control state for each of the plurality of electronic control devices an identifier for the communication set each before,
A dedicated identifier is also set before the communication message of the in- vehicle data recorder, and the identifier dedicated to the in-vehicle data recorder is different from the identifier set before the communication message from the external diagnostic device. An in-vehicle data recorder. Detecting the control state of the vehicle, an electronic control unit for sending the data the detected relative drive the LAN that is connected few cars double, are connected via a first cable, the plurality of electronic control In one in-vehicle data recorder capable of recording the control state of each device,
Branched from the first cable connecting the front Symbol car within LAN to the in-vehicle data recorder by the second cable, the abnormality diagnosis to collect data from the plurality of electronic control unit via the second cable Can be connected via a connector,
When said vehicle data recorder performs sequential diagnostic communication in one-to-one and one by one of the plurality of electronic control units, an identifier for the communication prior to the plurality of electronic control units that communicate messages to each set, respectively ,
Set a dedicated identifier before the communication message of the in-vehicle data recorder, and set the same identifier as the dedicated identifier of the in-vehicle data recorder also in the communication message of the external diagnostic device,
The external diagnostic device is connected to the in-vehicle LAN and the in-vehicle data recorder , and the in-vehicle data recorder detects communication from the external diagnostic device to any of the electronic control devices, thereby connecting the external diagnostic device. When the vehicle data is detected , the vehicle data recorder stops collecting data from the electronic control unit. The in-vehicle data recorder according to claim 2 ,
When collecting data from the electronic control device using the same identifier as that the outer portion diagnostic apparatus is used, after detecting the connection of the external diagnostic device, until through the process turns on the next ignition off Is a vehicle data recorder characterized by continuing data collection stop and restarting data collection upon the next ignition on or power on. The in-vehicle data recorder according to any one of claims 1 to 3,
When the in-vehicle data recorder performs diagnostic communication sequentially with one of the plurality of electronic control devices one by one,
A vehicle-mounted data recorder that controls the frequency of communication information existing on the in-vehicle LAN, that is, the frequency of data recording by diagnostic communication while monitoring the network load. One vehicle data recorder that is connected to the car's LAN, the data recording method of recording control information for a plurality of electronic control device connected to 該車 the LAN,
When said vehicle data recorder performs sequential diagnostic communication in one-to-one and one by one of the plurality of electronic control units, an identifier for the communication prior to the plurality of electronic control units that communicate messages to each set, respectively In addition, a dedicated identifier is also set before the communication message of the in-vehicle data recorder, and the identifier is set before the communication message from the external diagnostic device that collects data from the electronic control device and performs abnormality diagnosis A data recording method, wherein the identifier is different from the identifier. One vehicle data recorder that is connected to the vehicle LAN is, in the data recording method for recording control information for a plurality of electronic control units are connected before Symbol car inside LAN,
When said vehicle data recorder performs sequential diagnostic communication in one-to-one and one by one of the plurality of electronic control units, an identifier for the communication prior to the plurality of electronic control units for each of the communication message set respectively,
Set a dedicated identifier for the communication message of the in-vehicle data recorder,
Set the same identifier as the dedicated identifier in the communication message of the external diagnostic device that performs abnormality diagnosis of the plurality of electronic control devices,
When the external diagnostic device is connected to the in-vehicle LAN and the in-vehicle data recorder , and the in-vehicle data recorder detects communication from the external diagnostic device, the in-vehicle data recorder is connected to the electronic control device. A data recording method characterized by stopping data collection. The data recording method according to claim 6, wherein
When the in-vehicle data recorder collects data from the electronic control device with the same identifier as the external diagnostic device, after detecting the connection of the external diagnostic device, until the process of turning on from the next ignition off, A data recording method characterized by stopping data collection and restarting data collection upon the next ignition on or power on. The data recording method according to any one of claims 5 to 7,
When the in-vehicle data recorder performs diagnostic communication on a one-to-one basis with the plurality of electronic control devices,
A data recording method, wherein the frequency of communication information existing on the in-vehicle LAN, that is, the frequency of data recording by diagnostic communication is controlled while monitoring the network load.

Images