US20120239246A1 - Vehicular system, ecu, storing instruction transmission device, and storing request transmission device - Google Patents

Vehicular system, ecu, storing instruction transmission device, and storing request transmission device Download PDF

Info

Publication number
US20120239246A1
US20120239246A1 US13/419,903 US201213419903A US2012239246A1 US 20120239246 A1 US20120239246 A1 US 20120239246A1 US 201213419903 A US201213419903 A US 201213419903A US 2012239246 A1 US2012239246 A1 US 2012239246A1
Authority
US
United States
Prior art keywords
ecu
slave
storing
storing instruction
diagnostic information
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.)
Abandoned
Application number
US13/419,903
Other languages
English (en)
Inventor
Masahiko Tanaka
Mitsuyoshi Natsume
Yasuyuki Takahashi
Yuzo Harata
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Original Assignee
Denso Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Denso Corp filed Critical Denso Corp
Assigned to DENSO CORPORATION reassignment DENSO CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TANAKA, MASAHIKO, HARATA, YUZO, TAKAHASHI, YASUYUKI, NATSUME, MITSUYOSHI
Publication of US20120239246A1 publication Critical patent/US20120239246A1/en
Priority to US14/288,473 priority Critical patent/US20140277925A1/en
Priority to US15/209,787 priority patent/US10099703B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/04—Monitoring the functioning of the control system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40091—Bus bridging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40267—Bus for use in transportation systems
    • H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle

Definitions

  • the present disclosure relates to a vehicular system, an electronic control unit (ECU), a storing instruction transmission device, and a storing request transmission device.
  • ECU electronice control unit
  • JP-A-2003-229873 discloses a conventional vehicular system including multiple electronic control units (ECUs).
  • ECUs electronice control units
  • diagnostic information on the ECU is stored in a storage medium, and the stored diagnostic information is read by using a diagnostic tool at a repair shop of the vehicle.
  • control systems in a vehicle have been complicated.
  • the inventors of the present disclosure have studied recent vehicular control systems and consequently focused on multiple ECUs cooperating bilaterally in recent vehicular systems to control vehicular devices.
  • a complicated system for example, when a certain ECU detects a malfunction, It may be insufficient for specifying the cause of the malfunction only with diagnostic information of the certain ECU.
  • a vehicular system equipped to a vehicle comprises a master ECU.
  • the vehicular system further comprises a first slave ECU.
  • the vehicular system further comprises a second slave ECU.
  • the second slave ECU is configured to transmit a storing request to the master ECU on detection of a malfunction.
  • the master ECU is configured to transmit a storing instruction on reception of the storing request.
  • the first slave ECU is configured, on reception of the storing instruction from the master ECU: to generate diagnostic information on the first slave ECU; and to store the generated diagnostic information in a retention storage medium, the retention storage medium being configured to retain validity determination information in a condition where the first slave ECU is not supplied with electric power.
  • a vehicular system equipped to a vehicle comprises a first ECU.
  • the vehicular system further comprises a second ECU.
  • the first ECU is configured to transmit a storing instruction on detection of a malfunction.
  • the second ECU is configured, on reception of the storing instruction transmitted from the first ECU: to generate diagnostic information on the second ECU; and to store the generated diagnostic information on the second ECU in a retention storage medium, the retention storage medium being configured to retain validity determination information in a condition where the second ECU is not supplied with electric power.
  • an ECU equipped to a vehicle configured, on reception of a storing instruction from an outside: to generate diagnostic information on the ECU; and to store the generated diagnostic information in a retention storage medium, the retention storage medium being configured to retain validity determination information in a condition where the ECU is not supplied with electric power.
  • a storing instruction transmission device configured to transmit a storing instruction to a vehicular ECU, the vehicular ECU being configured, on reception of the storing instruction from an outside: to generate diagnostic information on the storing instruction transmission device; and to store the generated diagnostic information in a retention storage medium, the retention storage medium being configured to retain validity determination information in a condition where the storing instruction transmission device is not supplied with electric power.
  • an ECU communicable with a storing instruction transmission device the ECU comprises a storing request transmission unit configured, on detection of an anomaly by the ECU, to transmit a first storing request, which includes a first system identification code corresponding to the anomaly, to a storing instruction transmission device thereby to cause the storing instruction transmission device to transmit a first storing instruction, which includes the first system identification code.
  • the ECU further comprises an instruction correspondence storing unit configured: to receive a second storing instruction, when the storing instruction transmission device transmits the second storing instruction on reception of a second storing request from a device other than the ECU; to determine whether to store diagnostic information on the ECU, according to a second system identification code included in the received second storing instruction; and to store diagnostic information, which includes data corresponding to the second system identification code, in a storage medium of the ECU, on determination to store.
  • FIG. 1 is a block diagram showing a vehicular system according to an embodiment
  • FIG. 2 is a view showing the contents of a vehicle local time
  • FIG. 3 is a flowchart showing a vehicle local time generation and transmission processing implemented by a master ECU
  • FIG. 4 is a flowchart showing an exchange and record processing implemented by a slave ECU
  • FIG. 5 is a flowchart showing an exchange and record processing implemented by the slave ECU
  • FIG. 6 is a graph showing transition of elapsed time information and validity determination information with elapse of the time
  • FIG. 7 is a timing chart showing operation of ECUs
  • FIG. 8 is a view showing the contents of a simultaneous storing request
  • FIG. 9 is a flow chart showing a part of the exchange and record processing in FIG. 4 ;
  • FIG. 10 is a view showing one example of a belonging group list
  • FIG. 11 is a view showing an example of a data configuration of a stored data correspondence table.
  • FIG. 12 is a view showing a configuration of a vehicular system according to another embodiment.
  • FIG. 1 is a block diagram showing a vehicular system 1 according to the present embodiment.
  • the vehicular system 1 is equipped to a vehicle for controlling vehicular devices such as a safety device, a power train, a brake mechanism, an airbag, a convenience and comfortable control device, equipped to the vehicle.
  • vehicular devices such as a safety device, a power train, a brake mechanism, an airbag, a convenience and comfortable control device, equipped to the vehicle.
  • the vehicular system 1 includes an electronic control unit (ECU), such as a master ECU 11 and multiple slave ECUs 12 to 14 .
  • the vehicular system 1 further includes an in-vehicle LAN 15 , such as CAN or FlexRay, as a communication line for communication among the ECUs 11 to 14 .
  • the ECUs 11 to 14 are communicable with each other through the in-vehicle LAN 15 .
  • the master ECU 11 generates information, such as a vehicle local time and a simultaneous storing instruction (described later), and transmits the generated information to the slave ECUs 12 to 14 and the like periodically and repeatedly through the in-vehicle LAN 15 .
  • the slave ECUs 12 to 14 use the vehicle local time transmitted from the master ECU 11 as an inner time of the self device.
  • the slave ECUs 12 to 14 further transmit a simultaneous storing request to the master ECU 11 , on detection of a malfunction.
  • the slave ECUs 12 to 14 further store diagnostic information on reception of a simultaneous storing request from the master ECU 11 .
  • the master ECU 11 is a +B system activated with backup electric power from a battery in both an ON state (IG-ON state) and an OFF state (IG-OFF state) of an ignition device (IG) of the vehicle.
  • the ignition device (IG) of the vehicle is one example of a main power source of the vehicle.
  • the master ECU 11 may be a main body ECU for controlling a vehicular device such as a head lamp and/or an interior light.
  • the present configuration may be employed, since the main body ECU is a +B system with high loading rate in a vehicle and includes a retention storage medium.
  • the retention storage medium is, for example, a non-volatile storage media, such as a flash memory, S-RAM, etc., and configured to retain the validity determination information, even when the ECU equipped with the retention storage medium is not supplied with electric power.
  • Each of the slave ECUs 12 to 14 may be the +B system.
  • each of the slave ECUs 12 to 14 may be an IG system activated with electric power from the battery when the vehicle is in the IG-ON state, and terminated without electric power from the battery when the vehicle is in the IG-OFF state.
  • each of the slave ECUs 12 to 14 may be an ACC system activated with electric power from the battery when an airconditioner of the vehicle is activated in an ACC-ON state, and terminated without electric power from the battery when the airconditioner of the vehicle is deactivated in an ACC-OFF state.
  • the slave ECU 12 and the slave ECU 13 are for controlling a power train of the vehicle, and the slave ECU 13 is for controlling a device of a body system of the vehicle.
  • the ECU for controlling the power train may be, for example, an engine ECU and/or a transmission ECU.
  • the engine ECU is for controlling, for example, fuel supply to an engine, a fuel injection timing, and/or the like.
  • the transmission ECU is for controlling, for example, a transmission device.
  • the device of a body system belongs to a convenience and comfortable control device, such as a door lock system, a door mirror angle adjustment mechanism, and/or the like.
  • Each of the ECUs 11 to 14 has a hardware configuration including, for example, a communication interface circuit communicable with the in-vehicle LAN 15 , the retention storage media such as a flash memory, and a control circuit.
  • the control circuit is configured with a generally-known microcomputer equipped with a CPU, a volatile storage medium such as a RAM and a ROM, a timer, and an I/O device.
  • the CPU executes a program stored in the ROM, arbitrary write data in and read data from the RAM as the retention storage medium, and causes a communication interface circuit to implement communications through the in-vehicle LAN 15 .
  • the CPU further receives a detection signal from a sensor (not shown) arbitrary, and controls an actuator (not shown) being a control object.
  • the master ECU 11 receives a detection signals from devices such as a head lamp operation unit, an interior light operation unit, and/or a sensor, such as a door opening-and-closing sensor for detecting opening and closing of a door.
  • the head lamp operation unit is operated by a driver in order to switch activation and deactivation of a head lamp.
  • the interior light operation unit is operated by a driver in order to switch activation and deactivation of an interior light and automatic control of the interior light.
  • the master ECU 11 further controls the head lamp as an actuator according to the detection signal received from the head lamp operation unit and controls the interior light as an actuator according to the detection signal received from the interior light operation unit and the door opening-and-closing sensor.
  • the slave ECU 12 receives detection signals from sensors, such as an accelerator position sensor, an engine coolant temperature sensor, an engine revolution sensor, and/or a vehicle speed sensor.
  • the slave ECU 12 further controls an engine throttle valve control mechanism and a fuel injection mechanism as actuators, according to the detection signal retrieved from these sensors.
  • the slave ECU 13 receives detection signals from sensors, such as the vehicle speed sensor, a drive range sensor, and the engine revolution sensor.
  • the slave ECU 13 further controls the transmission device as an actuator, according to the detection signals received from these sensors.
  • the slave ECU 14 receives detection signals from sensors, such as the door lock operation unit and a mirror angle adjustment device.
  • the slave ECU 14 controls the door lock system and the door mirror angle adjustment mechanism as actuators, according to the detection signal received from these sensors.
  • a processing implemented by a CPU of a control circuit in an ECU is referred to as a processing implemented by the ECU.
  • the vehicle local time is uniformly used in each of the ECUs 11 to 14 of the vehicular system 1 .
  • the vehicle local time is periodically and repeatedly generated by the master ECU 11 and periodically and repeatedly transmitted from the master ECU 11 to the slave ECUs 12 to 14 .
  • the master ECU 11 and the slave ECUs 12 to 14 associate the diagnostic information with the latest vehicle local time and store the associated diagnostic information and the latest vehicle local time.
  • the master ECU 11 stores data about a vehicle local time 20 in a storage medium, such as the RAM and the retention storage medium.
  • the vehicle local time 20 includes elapsed time information 21 and validity determination information 22 .
  • the master ECU 11 stores the elapsed time information 21 in the RAM and stores the validity determination information 22 in the retention storage medium.
  • the elapsed time information 21 is 22-bit length data for measurement of the elapsed time information and configured to increment by one-second unit, as the time elapses in cycle order.
  • the elapsed time information 21 has the least significant bit (LSB) representing one second.
  • the validity determination information 22 is 2-bit length data configured to increment by one on one reset of the master ECU 11 in cycle order. Specifically, the validity determination information 22 increments by one on one reset of the CPU of the control circuit of the master ECU 11 .
  • the validity determination information 22 has the least significant bit (LSB) representing one reset.
  • the diagnostic tool 2 includes a communication interface unit, an operation unit, a display device, a time counter device, and a control circuit.
  • the communication interface unit is for connecting with the in-vehicle LAN 15 to communicate with the ECUs 11 to 14 .
  • the operation unit accepts a user's operation on a device, such as a button.
  • the display device indicates information.
  • the time counter device measures an absolute time.
  • the absolute time may be a calendar time, which includes the year, the month, the day, the hour, the minute, and the second.
  • the absolute time may be the Coordinated Universal Time (UTC) and/or the like.
  • the control circuit is configured with a generally-known microcomputer equipped with a CPU, a RAM, a ROM, and an I/O device.
  • the CPU executes a program stored in the ROM, arbitrary write data in and read data from the RAM as the retention storage medium, and causes the communication interface circuit to implement communications with the ECUs 11 to 14 through the in-vehicle LAN 15 .
  • the CPU further receives a signal caused by user's operation on the operation unit, causes the display device to indicate information, and receives the present absolute time from the time counter device, thereby to produce specific operation (described later.
  • the processing implemented by the CPU will be referred to as a processing implemented by the diagnostic tool 2 .
  • the vehicular system 1 does not include a time counter device, such as a GPS receiver, a radio-controlled clock, and a quartz watch, for measuring the absolute time.
  • a time counter device such as a GPS receiver, a radio-controlled clock, and a quartz watch.
  • the vehicular system 1 does not use the time counter device.
  • the master ECU 11 causes the CPU to execute a predetermined program thereby to implement a vehicle local time generation and transmission processing shown in FIG. 3 .
  • the master ECU 11 starts the vehicle local time generation and transmission processing in both cases immediately after the master ECU 11 is reset and immediately after the main power source (IG) of the vehicle is switched from the OFF state into ON state.
  • the case where the master ECU 11 is reset may be caused when the processing of the master ECU 11 is reset by a fail-safe processing.
  • the case where the master ECU 11 starts its operation occurs when, for example, the master ECU 11 is disconnected from the battery of the vehicle, and thereafter, the master ECU 11 is connected with the battery of the vehicle and activated.
  • Each of the slave ECUs 12 to 14 implements a reception and record processing shown in FIG. 4 and FIG. 5 when the slave ECU starts its operation.
  • Each of the master ECU 11 and the slave ECUs 12 to 14 implements the processing in FIG. 4 and FIG. 5 in parallel with another processing, such as a processing for engine control, a processing for brake control, and a processing for air-conditioning control.
  • the master ECU 11 When starting the operation of the vehicle local time generation and transmission processing, at step 100 , the master ECU 11 first tries readout of the validity determination information 22 from the retention storage medium into the RAM or a register of the CPU.
  • the register of the CPU is also an example of the volatile memory.
  • step 103 the master ECU 11 determines whether the readout is successful or failed. On determination of successful result, the processing proceeds to step 120 successively. Alternatively, on determination of failed result, the processing proceeds to step 105 successively.
  • the failed result of the readout is caused when, for example, a temporary malfunction occurs due to glitch in the retention storage medium, interfering wave, or the like. Normally, the readout is successful.
  • step 120 it is determined whether the present state is immediately after the master ECU 11 returns from the reset state.
  • the determination whether the present state is immediately after the master ECU 11 returns from the reset state can be made, according to the contents in the RAM. Specifically, the determination can be made by determining whether, for example, the elapsed time information 21 is stored in the RAM. Alternatively, the determination can be made by determining whether the reset processing has been implemented.
  • the master ECU 11 is reset in a case where, for example, the processing of the master ECU 11 goes into an infinite loop to cause a malfunction. Normally, it is determined that the present state is not immediately after returning from the reset state.
  • step 140 the master ECU 11 writes a value of the validity determination information 22 , which was read from the non-volatile storage medium and stored in the RAM at step 100 , in the retention storage medium. Thus, the processing proceeds to step 150 .
  • the processing may proceed to step 145 as it is.
  • step 145 it is determined whether the simultaneous storing request is received after executing step 145 at the last time before the present execution timing of step 145 . It is noted that, in the case where it is the first execution of step 145 after the master ECU 11 is started, it is determined whether the simultaneous storing request is received after the master ECU 11 is started before the present execution timing of step 145 . On determination that the simultaneous storing request is received, the processing proceeds to step 155 successively. Alternatively, on determination that the simultaneous storing request is not received, the processing proceeds to step 150 successively. As follows, the case where the processing proceeds to step 150 on determination that the simultaneous storing request is not received will be described. The processing on determination that the simultaneous storing request is received will be described later.
  • step 150 it is determined whether a measured time of a timer housed in the control circuit reaches a predetermined reference time such as 1000 milliseconds in the present embodiment. On determination that the measured time does not reach the predetermined reference time, step 150 is executed again. Alternatively, on determination that the measured time reaches the predetermined reference time, the processing proceeds to step 160 .
  • a predetermined reference time such as 1000 milliseconds in the present embodiment.
  • the start point of the measured time is the time point when the measured time has reached the reference time at step 150 at the last time. It is noted that, in the case where it has never been determined that the measured time has reached the reference time at step 150 after starting the processing in FIG. 3 , the start point of the measured time is set at the time point at which step 150 is first executed after the start of the processing in FIG. 3 . In this way, the processing proceeds from step 150 to step 160 each time when the reference time elapses.
  • the value of the elapsed time information 21 in the RAM is changed by the time unit according to the elapse of the time in cycle order.
  • the change in the cycle order is implemented such that the value of the 22-bit elapsed time information 21 is incremented by one from its minimum value to its maximum value, and the value of the elapsed time information 21 is returned to the minimum value after the value of the elapsed time information 21 reaches the maximum value.
  • the time unit according to the elapse of the time is “one time unit by one second.”
  • the master ECU 11 increments the value of the elapsed time information 21 by one at step 160 . It is noted that, in the case where the elapsed time information 21 is not stored in the RAM immediately after starting of the master ECU 11 or immediately after returning from the reset state, the elapsed time information 21 with the minimum value is stored in the RAM.
  • step 170 it is determined whether the value of the elapsed time information 21 overflows. Specifically, when the elapsed time information 21 is at the maximum value and when the elapsed time information 21 is incremented by one, the value of the elapsed time information 21 overflows. On determination that the value of the elapsed time information 21 overflows, the elapsed time information 21 is set at the minimum value at step 180 , and thereafter, the processing proceeds to step 190 . On determination that the value of the elapsed time information 21 does not overflow at step 170 , the processing skips step 180 and proceeds to step 190 .
  • data is generated as a simultaneous storing instruction.
  • the simultaneous storing instruction is 8-bit data. It is noted that, the contents of the simultaneous storing instruction being generated presently is a predetermined value representing a failure value.
  • the simultaneous storing instruction may be 8-bit data including eight bits all being set at “1.” Dissimilarly to the simultaneous storing instruction generated at step 194 (described later), the present simultaneous storing instruction is not data for storing diagnostic information.
  • the vehicle local time 20 is generated to include the elapsed time information 21 , which has the value changed by the time unit according to the elapse of the time in the cycle order, as described above, and the latest value of the validity determination information 22 stored in the retention storage medium. Furthermore, the vehicle local time 20 and the simultaneous storing instruction generated at step 190 are included in one data frame. Furthermore, the data frame is caused to include a predetermined address ID for broadcasting, so that the data frame, which includes the vehicle local time 20 and the simultaneous storing instruction, is received by all the ECUs including the slave ECUs 12 to 14 , other than the master ECU 11 , connected to the in-vehicle LAN 15 .
  • step S 145 an interface circuit is caused to send the data frame into the in-vehicle LAN 15 . Subsequently, the processing returns to step S 145 . It is noted that, the transmission at step 192 is implemented only when the vehicle is in the IG-ON state. When the vehicle is in the IG-OFF state, the transmission is not implemented, and the processing returns to step 145 .
  • each of the slave ECUs 12 to 14 first waits for a predetermined time at step 210 .
  • this predetermined time is, for example, 1000 milliseconds being same as a transmission interval at which the master ECU 11 transmits the vehicle local time 10 .
  • each of the slave ECUs 12 to 14 causes the communication interface circuit to receive the data frame, which includes the vehicle local time 20 and the simultaneous storing instruction, transmitted from the master ECU 11 through the in-vehicle LAN 15 .
  • step 220 the vehicle local time 20 included in the received data frame is stored in the RAM and updated as the latest vehicle local time 20 in the slave ECU.
  • the storing event is a predetermined event at which the diagnostic information needs to be stored.
  • the storing event is determined to occur in two cases.
  • One of the two cases is when the simultaneous storing instruction in the data frame received at immediately preceding step 210 is not a failure value, that is, when the simultaneous storing instruction, which is not failure in value, is received at immediately preceding step 210 .
  • the other one of the two cases is when a malfunction is determined to occur according to the detection signal from the sensor and when the malfunction is determined to necessitate storing of the diagnostic information on the self device.
  • the malfunction may occur when the engine revolution deviates from its predetermined normal range or when the brake pressure deviates from its predetermined normal range. It is specified beforehand a malfunction necessitating storing of the diagnostic information on the self device and a malfunction not necessitating storing of the diagnostic information on the self device.
  • the processing proceeds to step 250 where it is determined whether transmission of the simultaneous storing request is needed. Transmission of the simultaneous storing request is determined to be needed when a malfunction is determined to occur according to the detection signal from the sensor and when the malfunction is determined to necessitate transmission of the simultaneous storing request. It is specified beforehand a malfunction necessitating transmission of the simultaneous storing request and a malfunction not necessitating transmission of the simultaneous storing request. In many cases, transmission of the simultaneous storing request is determined not to be needed. In this case, the processing returns to step 210 .
  • each of the slave ECUs 12 to 14 receives the data frame, which includes the vehicle local time 20 , from the master ECU 11 periodically (step 210 ) and synchronizes the inner time with the vehicle local time 20 (step 220 ).
  • each of the slave ECUs 12 to 14 does not implement a processing to change the vehicle local, time 20 by itself.
  • the vehicle local time 20 is sent from the master ECU 11 and received by the slave ECUs 12 to 14 repeatedly and periodically at the cycle of 1000 millisecond.
  • the elapsed time information 21 of the vehicle local time 20 increases by one relative to the elapse of one second at the constant increase rate in proportion to the elapse of the time.
  • the master ECU 11 is reset at the time t 1 in the state where no slave ECUs 12 to 14 transmits the simultaneous storing request.
  • the master ECU 11 stops its processing in the course of the vehicle local time generation and transmission processing in FIG. 3 . Consequently, the elapsed time information 21 is lost from the RAM. Subsequently, the master ECU 11 returns from the reset state immediately and again begins the vehicle local time generation and transmission processing in FIG. 3 .
  • the readout of the validity determination information 22 is usually successful at step 100 , it is determined that the readout is successful at subsequent step 103 , and it is determined that the present state is immediately after returning from the reset state at subsequent step 120 . Thus, the processing proceeds to step 125 .
  • the value of the validity determination information 22 is changed in the cycle order. “The change in the cycle order” is implemented such that the value of the 2-bit validity determination information 22 is incremented by one from its minimum value to its maximum value, and the value of the validity determination information 22 is returned to the minimum value after the value of the validity determination information 22 reaches the maximum value.
  • the validity determination information 22 readout at step 100 is incremented by one.
  • the validity determination information 22 after being changed and stored in the RAM is stored as the latest value of the validity determination information 22 in the retention storage medium. In this way, at the time t 1 in FIG. 5 , the value of the validity determination information 22 changed by one is updated as the latest value of the validity determination information 22 in the retention storage medium.
  • step 145 subsequent to step 140 , it is determined that the simultaneous storing request is not received. Subsequently, the processing proceeds to step 150 at which the processing waits until the measured time reaches 1000 milliseconds.
  • step 160 the elapsed time information 21 is not stored in the RAM, since it is immediately after the master ECU 11 returns form the reset state. Therefore, the value of the elapsed time information 21 at its minimum value (namely, initial value) is newly stored in the RAM. Subsequently, at step 170 , it is determined that the value of the elapsed time information 21 does not overflow.
  • the simultaneous storing request which includes the failure value, is generated.
  • step 192 the vehicle local time 20 , which includes the elapsed time information 21 being set in the above-described way and the validity determination information 22 , and the simultaneous storing request are included into one data frame. Thus, the data frame is transmitted.
  • the master ECU 11 and the slave ECUs 12 to 14 implement the above-described fundamental operation.
  • the elapsed time information 21 increases, with the elapse of the time, while the validity determination information 22 is constant in the ECUs 11 to 14 .
  • the master ECU 11 is in operation to implement the processing in FIG. 3 .
  • the master ECU 11 continues the change in the value of the elapsed time information 21 by the time unit according to the elapse of the time (steps 160 to 180 ).
  • the master ECU 11 continues the change in the value of the validity determination information 22 according to occurrence of reset (steps 120 to 140 ). Therefore, the vehicle local time 20 changes with the elapse of the time in the same form when the vehicle is in the IG-ON state.
  • a series time period, in which the validity determination information 22 is constant to have the same value is referred to as a time group.
  • the storing event occurs in the slave ECU 12 at the time t 2 .
  • the slave ECU 12 determines that the engine coolant temperature exceeds its allowable range according to the detection signal from the engine coolant temperature sensor and determines that a malfunction occurs.
  • the slave ECU 12 determines that the malfunction necessitates storing of the diagnostic information by the self device. In this case, the slave ECU 12 determines that the storing event occurs, and the processing proceeds to step 240 .
  • the diagnostic information on the self device is generated at step 240 . Further, the diagnostic information is associated with the latest vehicle local time 20 stored in the RAM, and the associated information is stored in the retention storage medium. In the vehicle local time 20 stored with the diagnostic information presently, the value of the elapsed time information 21 corresponds to the elapsed time d 0 in FIG. 6 , and the value of the validity determination information 22 is 03.
  • the diagnostic information stored presently includes a diagnosis trouble code (DTC) and a freeze frame data (FFD).
  • DTC diagnosis trouble code
  • FFD freeze frame data
  • the DTC is a malfunction classification code representing the classification of the malfunction related to the high temperature of engine cooling water.
  • the FFD may include data related to, for example, the detected engine coolant temperature.
  • step 240 the proceeds to step 250 , at which it is determined whether the simultaneous storing request is needed. In the present example, it is assumed that the detected malfunction does not need transmission of the simultaneous storing request. In this case, the processing returns to step S 210 .
  • the master ECU 11 and the slave ECUs 12 to 14 implement the above-described fundamental operation.
  • the elapsed time information 21 increases with the elapse of the time, while the validity determination information 22 is constant in the ECUs 11 to 14 .
  • step t 3 it is assumed that the elapsed time information 21 reaches the maximum value, and after the elapse of 1000 milliseconds, it is assumed that overflow occurs at step 160 in the vehicle local time generation and transmission processing in FIG. 3 .
  • the master ECU 11 determines that the overflow occurs at step 170 .
  • the processing proceeds to step 180 at which the elapsed time information 21 is set at the minimum value. In this case, the elapsed time information 21 does not change.
  • the length of the time period from the time t 1 , at which the elapsed time information 21 changes from the minimum value to the maximum value, to the time t 3 is about 48.5 days.
  • the master ECU 11 and the slave ECUs 12 to 14 implement the above-described fundamental operation.
  • the elapsed time information 21 increases from the minimum value with the elapse of the time, while the validity determination information 22 is constant in the ECUs 11 to 14 .
  • step 125 the master ECU 11 determines that the value of the validity determination information 22 overflows.
  • step 130 the processing proceeds to step 130 , at which the value of the validity determination information 22 is set to the minimum value (00), and the processing proceeds to step 140 .
  • the processing subsequent to step 140 is similar to those in the case of the time t 1 .
  • the master ECU 11 and the slave ECUs 12 to 14 implement the above-described fundamental operation.
  • the elapsed time information 21 increases from the minimum value with the elapse of the time, while the validity determination information 22 is constant in the ECUs 11 to 14 .
  • FIG. 7 shows the operation of the ECUs 11 to 14 and the transition of the elapsed time information 21 with the elapse of the time in the time zone t 5 from the time t 51 to the time t 54 .
  • the master ECU 11 implements the vehicle local time generation and the transmission processing in FIG. 3 and transmits the vehicle local time 20 ( 31 a ). Further, the slave ECUs 12 to 14 implements the processing at step 210 in FIG. 4 and receives the vehicle local time 20 ( 31 b to 31 d ).
  • the slave ECU 13 detects that the engine revolution exceeds the allowable range at step 230 in FIG. 4 . It is assumed that the malfunction that the engine revolution exceeds the allowable range is specified beforehand in the slave ECU 13 to necessitate storing of the diagnostic information by the self device and to necessitate transmission of the simultaneous storing request. Therefore, at the time t 52 , the slave ECU 13 determines, at step 230 , that the engine revolution exceeds its allowable range according to the detection signal from the engine revolution sensor and determines that the malfunction occurs. In addition, when the slave ECU 13 determines that the malfunction necessitates storing of the diagnostic information by the self device, the processing proceeds to step 240 .
  • the diagnostic information on the self device is generated at step 240 . Further, the diagnostic information is associated with the latest vehicle local time 20 stored in the RAM, and the associated information is stored in the retention storage medium ( 32 c - 1 ). In the vehicle local time 20 stored with the diagnostic information presently, the value of the elapsed time information 21 corresponds to the elapsed time d 3 in FIG. 7 , and the value of the validity determination information 22 is 00.
  • the diagnostic information stored presently includes the DTC and the FFD. The DTC and the FFD to be stored are determined correspondingly to a malfunction.
  • step 250 subsequent to step 240 , the malfunction is determined to occur according to the detection signal from the sensor, and the malfunction is determined to necessitate transmission of the simultaneous storing request. Consequently, it is determined that the transmission of the simultaneous storing request is necessitated, and the processing proceeds to step 260 in FIG. 5 successively.
  • step 260 it is determined whether the vehicle local time 20 is normally received from the master ECU at immediately preceding step 210 . In usual cases, it is determined that the vehicle local time 20 is normally received from the master ECU. To the contrary, when it is determined that the vehicle local time 20 is not normally received due to a malfunction, the processing is returned to step 210 and the processing waits for reception of the subsequent vehicle local time 20 .
  • step 270 a system identification code and a malfunction classification code are generated.
  • the system identification code and the malfunction classification code are to be included in the simultaneous storing request transmitted to the master ECU 11 .
  • the system identification code and the malfunction classification code are determined according to the classification of the malfunction detected at step 250 .
  • the system identification code is, for example, a 4-bit code for specifying the classification of an ECU relevant to the detected malfunction.
  • the correspondence between the occurring malfunction and the system identification code is beforehand specified uniformly in each of the ECUs 11 to 14 .
  • the value of the system identification code associated with each malfunction may be three values respectively representing three kinds of malfunctions in the power train system, three values respectively representing three kinds of malfunctions in the brake mechanism system, and/or three values respectively representing three kinds of malfunctions in the safety device system.
  • the value of the system identification code associated with each malfunction may be three values respectively representing three kinds of malfunctions in the convenience and comfortable control device system and/or three values respectively representing three kinds of malfunctions of all the ECU systems.
  • the system identification code representing the one value of the power train system is generated.
  • the malfunction classification code is, for example, a 4-bit code for specifying the detected malfunction uniquely. Determination of the combination of the occurring malfunction, the system identification code, and the malfunction classification code enables identification of the category of the malfunction uniquely. The correspondence between the category of malfunction and the malfunction classification code is beforehand specified uniformly in each of the ECUs 11 to 14 .
  • a simultaneous storing request 25 includes a system identification code 26 generated at immediately preceding step 270 and a malfunction classification code 27 .
  • the simultaneous storing request 25 generated at immediately preceding step 280 is transmitted to the master ECU 11 through the in-vehicle LAN 15 ( 32 c - 2 in FIG. 7 ).
  • the master ECU 11 receives the simultaneous storing request 25 ( 32 a ).
  • step 145 in FIG. 3 the master ECU 11 determines that the simultaneous storing request 25 is received, and the processing proceeds to step 155 .
  • step 155 similarly to step 150 , it is determined whether the measured time of the timer reaches the predetermined reference time such as 1000 milliseconds. On determination that the measured time does not reach the predetermined reference time, step 155 is executed again. On determination that the measured time reaches the predetermined reference time at the time t 53 , the processing proceeds to step 165 .
  • the processings at steps 165 , 175 , 185 are equivalent to the processings at steps 160 , 170 , 180 , respectively. Therefore, at each of steps 165 , 175 , 185 , the value of the elapsed time information 21 in the RAM is changed by the time unit (e.g., 1000 milliseconds) according to the elapse of the time in the cycle order.
  • the time unit e.g. 1000 milliseconds
  • the simultaneous storing instruction is generated. Specifically, the contents of the simultaneous storing instruction is modified to include the system identification code 26 in the simultaneous storing request 25 determined to be received at immediately preceding step 145 and the malfunction classification code 27 .
  • the system identification code 26 other than the failure value is employed as the simultaneous storing instruction in this way, and thereby, the simultaneous storing instruction functions as data for storing the diagnostic information.
  • the elapsed time information 21 changed by the time unit according to the elapse of the time in the cycle order value is generated in the manner as described above.
  • the vehicle local time 20 including the latest value of the validity determination information 22 stored in the retention storage medium is further generated.
  • the vehicle local time 20 and the simultaneous storing instruction generated at step 196 are included in one data frame.
  • the predetermined address ID for broadcasting is included in the data frame, so that the data frame, which includes the vehicle local time 20 and the simultaneous storing instruction, are sent to all the ECUs including the slave ECUs 12 to 14 , which are other than the master ECU 11 , connected to the in-vehicle LAN 15 .
  • the interface circuit is caused to send the data frame into the in-vehicle LAN 15 ( 33 a in FIG. 7 ).
  • the diagnostic information is generated according to the simultaneous storing request 25 determined to be received at immediately preceding step 145 . Further, the diagnostic information is associated with the latest vehicle local time 20 stored in the RAM, and the associated information is stored in the retention storage medium. The associated information is stored at the time 33 a in FIG. 7 .
  • the value of the elapsed time information 21 corresponds to the elapsed time d 4 in FIG. 7
  • the value of the validity determination information 22 is 00.
  • the diagnostic information of the self device stored presently includes the DTC and the FFD. It is noted that, the DTC is a value same as the malfunction classification code 27 included in the simultaneous storing request 25 determined to be received at immediately preceding step 145 .
  • the contents of the FFD included in the diagnostic information are determined according to the system identification code 26 in the simultaneous storing request 25 . The correspondence between the system identification code 26 and the contents of FFD is specified beforehand.
  • the master ECU 11 may store the diagnostic information in the retention storage medium at step 198 , since the system identification code is the power train system.
  • the master ECU 11 may not store the diagnostic information in the retention storage medium at step 198 , since the system identification code is the power train system.
  • each of the slave ECUs 12 to 14 receives the data frame ( 33 b to 33 d in FIG. 7 ) transmitted from the master ECU 11 ( 33 a ) at step 210 in FIG. 4 through the communication interface unit.
  • each of the slave ECUs 12 to 14 stores, as the latest vehicle local time 20 , the vehicle local time 20 in the data frame in the RAM of the slave ECU thereby to update the vehicle local time 20 .
  • step 230 the storing event is determined to occur, on determination that the simultaneous storing instruction in the data frame received at immediately preceding step 210 is not the failure value. Thus, the processing proceeds to step 240 .
  • the diagnostic information is generated at step 240 . Further, the diagnostic information is associated with the latest vehicle local time 20 stored in the RAM, and the associated information is stored in the retention storage medium. In the vehicle local time 20 stored with the diagnostic information presently, the value of the elapsed time information 21 corresponds to the elapsed time d 4 in FIG. 7 , and the value of the validity determination information 22 is 00.
  • the diagnostic information stored presently includes the DTC and the FFD. It is noted that, the DTC is a value same as the malfunction classification code 27 included in the simultaneous storing instruction received at immediately preceding step 210 .
  • the contents of the FFD included in the diagnostic information are determined according to the system identification code 26 in the simultaneous storing request 25 . The correspondence between the system identification code 26 and the contents of FFD is specified beforehand.
  • the FFD in the diagnostic information stored at the time t 52 by the slave ECU 13 which is the sender of the simultaneous storing request, may be the same as or may be distinct from the FFD in the diagnostic information stored by the slave ECU 13 presently.
  • the slave ECUs 12 and 13 for controlling the power train system store the diagnostic information at step 240 , only when receiving the simultaneous storing instruction including the system identification code at a value representing the power train system or when receiving the simultaneous storing instruction including the system identification code at a value representing all the ECUs.
  • the slave ECUs 12 and 13 for controlling the power train system do not store the diagnostic information at step 240 when receiving the simultaneous storing instruction including the system identification code at a value other than the value representing the power train system or all the ECUs.
  • the slave ECU 14 for controlling the convenience and comfortable control device system stores the diagnostic information at step 240 , only when receiving the simultaneous storing instruction including the system identification code at a value representing the convenience and comfortable control device system or when receiving the simultaneous storing instruction including the system identification code at a value representing all the ECUs.
  • the slave ECU 14 for controlling the convenience and comfortable control device system does not store the diagnostic information at step 240 when receiving the simultaneous storing instruction including the system identification code at a value other than the value representing the convenience and comfortable control device system or all the ECUs.
  • the simultaneous storing request received by the slave ECUs 12 to 14 includes the system identification code at the value representing the power train system. Therefore, the slave ECUs 12 and 13 store the diagnostic information ( 34 b, 34 c in FIG. 7 ) at step 240 , and the slave ECU 14 does not store the diagnostic information at step 240 .
  • each of the slave ECUs 12 to 14 at step 240 will be described further in detail.
  • the processing proceeds to step 240 on determination that the storing event occurs at step 230 on reception of the simultaneous storing instruction, which is not at the failure value.
  • each of the slave ECUs 12 to 14 implements the processing shown in FIG. 9 .
  • step 240 a the system identification code included in the simultaneous storing instruction is first compared with a code included in a belonging group list stored in the self device. Thus, it is determined whether any one of the codes included in the belonging group list is the same as the system identification code. On determination that the any one of the codes included in the belonging group list is the same as the system identification code, the processing proceeds to step 240 b, at which the diagnostic information and the latest vehicle local time 20 are stored in the retention storage medium. Alternatively, on determination that none of the codes included in the belonging group list is the same as the system identification code being received, the processing skips step 240 b to proceed to step 250 . Thus, the processing at step 240 is terminated.
  • the belonging group list will be described.
  • the belonging group list of the self device is beforehand stored in the retention storage medium or ROM of the self device.
  • the belonging group list stored in each of the slave ECUs 12 , 13 , 14 includes the system identification code corresponding to the group to which the slave ECU belongs.
  • the “group” denotes a group configured with the ECUs as components. Therefore, the ECU(s) for controlling a device of the body system belongs to a group of the body system, the ECU(s) for controlling the power train belongs to a group of the power train system, and the ECU(s) for controlling wireless communication belongs to a group for a wireless system. Furthermore, the ECU(s) for controlling illumination of the vehicle belongs to a group of an illuminations system, and the ECU(s) for controlling the electric power source of the vehicle belongs to a group of an electric power control system.
  • the belonging group list 40 includes, for example, a system identification code corresponding to the group of the wireless system, a system identification code corresponding to the group of the illumination system, and a system identification code corresponding to the group of an electric power control system.
  • the slave ECU storing the belonging group list belongs to the group of the wireless system, the group of the illumination system, and the group of the electric power control system.
  • each of the slave ECUs 12 to 14 stores the diagnostic information on the self device when the system identification code included in the storing instruction sent from the master ECU 11 corresponds to the group to which the self device belongs.
  • each of the slave ECUs 12 to 14 does not store the diagnostic information on the self device when the system identification code included in the storing instruction sent from the master ECU 11 does not correspond to the group to which the self device belongs.
  • the contents of the FFD including the diagnostic information stored at step 240 b are determined according to the system identification code 26 in the simultaneous storing request 25 .
  • the correspondence between the system identification code 26 and the contents of the FFD is specified beforehand.
  • the retention storage medium or the ROM of each of the slave ECUs 12 , 13 , 14 includes the above-described belonging group list and stores the stored data correspondence table.
  • the stored data correspondence table stored in each of the slave ECUs 12 , 13 , 14 includes the system identification codes, which are included in the belonging group list stored in the same slave ECU, each being associated correspondingly with an input-and-output data name.
  • Each of the input-and-output data in a certain ECU is data in the certain ECU retrieved from a sensor or another ECU, data in the certain ECU outputted to control an actuator, or data transmitted to the certain ECU.
  • FIG. 11 shows an example of the belonging group list.
  • the belonging group list included in a certain slave ECU which may be any one of the slave ECUs 12 , 13 , 14 , includes a system identification code 01 , a system identification code 03 , and a system identification code 05 .
  • the system identification code 01 corresponds to the group of the wireless system.
  • the system identification code 03 corresponds to the group of the illumination system.
  • the system identification code 05 corresponds to the group of the electric power control system.
  • the stored data correspondence table includes information on names of the wireless-related input-and-output data corresponding to the system identification code 01 , names of the illumination-related input-and-output data corresponding to the system identification code 03 , and names of the power-control-system-related input-and-output data corresponding to the system identification code 05 .
  • the names of the wireless-related input-and-output data corresponding to the system identification code 01 include, for example, the classification of a manual operation button of a wireless key device, the state of a door lock position SW, the state of a door courtesy SW, and/or the like.
  • the names of the illumination-related input-and-output data corresponding to the system identification code 03 include, for example, the state of an illumination SW, an illumination lighting time, an illumination lighting instruction request from each ECU, and/or the like.
  • the names of the power-control-system-related input-and-output data corresponding to the system identification code 05 include, for example, the state of an ignition switch (IGSW), the state of an airconditioner switch (ACCSW), the state of a brake SW, and/or the like.
  • each of the slave ECUs 12 to 14 reads the input-and-output data name, which is associated with the system identification code in the simultaneous storing request being received, from the stored data correspondence table of the self device. In addition, each of the slave ECUs 12 to 14 sets the data of the readout input-and-output data name as the FFD. Further, each of the slave ECUs 12 to 14 associates the diagnostic information and an operation history including the FFD and DTC with the latest vehicle, local time 20 and store the associated information.
  • the data of the wireless-related input-and-output data name is stored as the FFD in the storage medium, with reference to the stored data correspondence table.
  • the slave ECUs 12 to 14 selectively stores in the storage medium only the input-and-output data in the group corresponding to the system identification code, among all the input-and-output data sent from and received by the self device.
  • the latest vehicle local time 20 is certainly stored with the diagnostic information, irrespectively of the system identification code in the simultaneous storing request being received.
  • the diagnostic information is stored by the self device.
  • the diagnostic information is not stored by the self device. Therefore, information useful for analysis of the malfunction can be selectively stored, and the resource for storing the diagnostic information can be restrained.
  • step 250 subsequent to step 240 , the malfunction is not detected in the self device. Therefore, it is determined that transmission of the simultaneous storing request is not needed, and the processing returns to step 210 .
  • the master ECU 11 implements the vehicle local time generation and the transmission processing in FIG. 3 and transmits the vehicle local time 20 ( 35 a ). Further, the slave ECUs 12 to 14 implements the processing at step 210 in FIG. 4 and receives the vehicle local time 20 ( 35 b to 35 d ).
  • the master ECU 11 and the slave ECUs 12 to 14 implement the above-described fundamental operation.
  • the elapsed time information 21 increases with the elapse of the time, while the validity determination information 22 is constant in the ECUs 11 to 14 .
  • the vehicle is carried into, for example, a repair shop, before the elapsed time information 21 becomes the maximum value.
  • the IG device of the vehicle is once turned OFF and turned ON in the time period after the diagnostic information is stored at the time t 5 before the vehicle is carried into the repair shop. Nevertheless, as described above, the change in the value of the elapsed time information 21 is continued by the time unit according to the elapse of the time, even after the IG device is turned ON and OFF.
  • the diagnostic tool 2 is connected to the vehicular system 1 through the in-vehicle LAN 15 in, for example, the repair shop. Furthermore, it is assumed that a user of the diagnostic tool 2 implements a predetermined operation on an operation device for reading the diagnostic information on a specific slave ECU. In the present example, the specific slave ECU is, for example, the slave ECU 13 .
  • the diagnostic tool 2 may implement either wired communications or wireless communications with the vehicular system 1 .
  • the diagnostic tool 2 causes the interface circuit to transmit a readout command to the master ECU 11 and the slave ECUs 12 and 13 through the in-vehicle LAN 15 .
  • each of the master ECU 11 and the slave ECUs 12 and 13 On receiving the readout command through the interface circuit of the self device, each of the master ECU 11 and the slave ECUs 12 and 13 reads the latest vehicle local time 20 , which is stored in the RAM of the control circuit of the self device, and the vehicle local time 20 , which is associated with the diagnostic information and stored in the retention storage medium of the self device. Further, each of the master ECU 11 and the slave ECUs 12 and 13 causes the interface circuit of the self device to transmit the latest vehicle local time 20 , the diagnostic information, and the vehicle local time 20 (storing-time vehicle local time 20 ), which is associated with the diagnostic information, to the diagnostic tool 2 through the in-vehicle LAN 15 .
  • the diagnostic tool 2 receives the data transmitted from the master ECU 11 and the slave ECUs 12 and 13 through the interface circuit of the self device in this way.
  • the diagnostic tool 2 further determines whether the value of the validity determination information 22 in the latest vehicle local time 20 is the same as the value of the validity determination information 22 in the storing-time vehicle local time 20 .
  • the diagnostic tool 2 calculates a retroactive time, which is equivalent to the difference between the value of the elapsed time information 21 in the latest vehicle local time 20 and the value of the elapsed time information 21 in the storing-time vehicle local time 20 (see FIG. 5 ).
  • the retroactive time corresponding to the difference therebetween is 20480 seconds (about 5 hours and a half).
  • the present absolute time is retrieved from the time counter device, and an absolute time, at which the diagnostic information was stored, is calculated by subtracting the retroactive time from the retrieved present absolute time.
  • the display device is caused to indicate the calculated absolute time at which the diagnostic information was stored. In this case, the display device is also caused to indicate the diagnostic information.
  • the diagnostic tool 2 causes the display device to indicate the storing-time vehicle local time 20 , as it is. In this case, the display device is also caused to indicate the diagnostic information.
  • the master ECU 11 changes the value of the elapsed time information 21 , which is included in the vehicle local time 20 to be transmitted to the slave ECUs 12 to 14 , by the time unit according to the elapse of the time.
  • the master ECU 11 continues the change in the value of the elapsed time information 21 by the time unit according to the elapse of the time, even when the main power source (IG switch) of the vehicle is turned ON or turned OFF.
  • the present configuration enables to reduce possibility of occurrence of a situation where the absolute time, at which the malfunction has occurred, is unclear, since the elapsed time has been reset due to the turning ON and OFF of the IG device. That is, the absolute time, at which the event occurs, can be specified with higher possibility than that of a conventional configuration.
  • a user of the vehicle may inquire about a trouble caused at a specific time (e.g., about 17:30, January 13).
  • a specific time e.g., about 17:30, January 13
  • the present configuration enables to retrieve the absolute time, at which the diagnostic information related to the trouble was stored, together with the diagnostic information by using the diagnostic tool 2 . Therefore, the cause of the trouble can be easily and appropriately specified in response to such an inquiry of the user.
  • the master ECU 11 when the master ECU 11 returns from the reset state, it is unclear the time period, in which the master ECU 11 had been out of operation. Therefore, the recent value of the elapsed time information 21 , when the master ECU 11 was previously in operation, does not represent appropriate progress in time. In consideration of this, the elapsed time information is set to the minimum immediately after the return from the reset state. In addition, in response to the return from the reset state, the master ECU 11 newly stores the elapsed time information 21 at its initial value in the volatile storage medium. Thereby, the elapsed time information 21 is enabled to represent the correct elapsed time from the time point of the return from the reset state.
  • the master ECU 11 stores a valid value of the validity determination information 22 in the retention storage medium, separately from the elapsed time information 21 .
  • the retention storage medium retains the stored content even when the master ECU 11 is reset.
  • the master ECU 11 changes the valid value of the validity determination information 22 stored in retention storage medium (e.g., volatile storage medium) in response to return of the master ECU 11 from the reset state.
  • the master ECU 11 generates the vehicle local time 20 including the validity determination information 22 in addition to the elapsed time information 21 and repeatedly transmits the vehicle local time 20 to the slave ECUs 12 to 14 .
  • the valid value of the validity determination information 22 , the elapsed time information 21 , and the diagnostic information are stored in the storage medium in the slave ECUs 12 to 14 . Therefore, the diagnostic information, which is stored before the return of the master ECU 11 from the reset state, is distinguishable from the diagnostic information, which is stored subsequent to the return of the master ECU 11 from the reset state.
  • the processing proceeds to step 105 on determination that the readout is unsuccessful at step 103 .
  • the vehicle local time 20 is set at the predetermined failure value.
  • the predetermined failure value represents the vehicle local time 20 being at the maximum value (03h) and the elapsed time information 21 being at the maximum value (3FFFFEh).
  • the vehicle local time 20 at the failure value is transmitted to the slave ECUs 12 to 14 ( 110 , 115 ) repeatedly at a constant cycle, such as 1000 ms.
  • the slave ECU 13 (or other slave ECUs 12 and 14 ) transmits the simultaneous storing request to the master ECU 11 , on detection of a malfunction.
  • the master ECU 11 transmits the simultaneous storing instruction for causing the diagnostic information to be stored, on reception of the simultaneous storing request.
  • the slave ECUs 12 and 13 generates the diagnostic information on the self device and stores the generated diagnostic information in the retention storage medium, on reception of the simultaneous storing instruction transmitted from the master ECU 11 .
  • the diagnostic information is generated and stored in the ECUs, such as the master ECU 11 and the slave ECU 12 , other than the slave ECU 13 .
  • the slave ECU 13 includes the malfunction classification code, which represents the classification of the malfunction, in the simultaneous storing request to be transmitted to the master ECU 11 .
  • the master ECU 11 includes the malfunction classification code, which is included in the simultaneous storing request received from the slave ECU 13 , in the simultaneous storing instruction to be transmitted.
  • the slave ECUs 12 and 13 include the malfunction classification code, which is included in the simultaneous storing instruction received from the master ECU 11 , in the diagnostic information on the self device.
  • the present configuration enables easily to specify the classification of the malfunction, which is detected by the other ECU 13 , causing the slave ECU 12 to store the diagnostic information.
  • the slave ECU 13 includes the predetermined system identification code in the simultaneous storing request to be transmitted to the master ECU 11 .
  • the master ECU 11 includes the system identification code, which is included in the simultaneous storing request received from the slave ECU 13 , in the simultaneous storing instruction to be transmitted.
  • the slave ECUs 12 , 13 , 14 determines whether to store the diagnostic information in the slave ECU 12 , according to the system identification code included in the simultaneous storing instruction received from the master ECU 11 .
  • the slave ECU 13 is enabled to control whether to cause the other slave ECUs 12 and 13 to generate and store the diagnostic information by using the system identification code.
  • the master ECU 11 changes the value of the elapsed time information 21 by the time unit according to the elapse of the time.
  • the master ECU 11 generates the vehicle local time 20 including the elapsed time information 21 and transmits the generated vehicle local time 20 with the simultaneous storing instruction to the slave ECU 12 .
  • the slave ECU 12 associates the diagnostic information on the slave ECU 12 with the vehicle local time 20 to each other and stores the associated diagnostic information and the vehicle local time 20 in the retention storage medium.
  • the slave ECU 14 on reception of the vehicle local time 20 and the storing instruction from the master ECU 11 , the slave ECU 14 associates the diagnostic information on the slave ECU 14 with the vehicle local time 20 to each other and store the associated diagnostic information and the vehicle local time 20 in the retention storage medium.
  • the slave ECU 12 and the slave ECU 14 store the vehicle local time 20 provided from the master ECU 11 all together. Therefore, the time used as the storing time of the diagnostic information can be managed uniformly in the master ECU 11 .
  • the simultaneous storing request is transmitted together with the in-vehicle local time at the transmission timing of the in-vehicle local time 20 . Therefore, the vehicle local time stored with the diagnostic information is determined clearly on the side of the slave ECUs.
  • the simultaneous storing request and the in-vehicle local time are received at separate timings, respectively. In such a configuration, it is necessary to determine whether to employ the in-vehicle local time, which is received immediately before reception of the simultaneous storing request or whether to employ the in-vehicle local time, which is received immediately after reception of the simultaneous storing request, as the vehicle local time stored with diagnostic information.
  • the timing of the processing may be delayed.
  • the time elapses after receiving a large number of the simultaneous storing requests until the simultaneous storing requests are processed, and meanwhile, the vehicle local time proceeds in the slave ECU. Consequently, the time, at which the simultaneous storing requests were received, becomes inaccurate.
  • the present configuration enables to store the vehicle local time together with the simultaneous storing request thereby to avoid causing inaccurate time record.
  • the simultaneous storing request is transmitted from the slave ECUs 12 to 14 to the master ECU 11 . It is noted that, the simultaneous storing request may be transmitted from an ECU, other than the slave ECUs 12 to 14 in the vehicular system 1 , to the master ECU 11 .
  • the vehicular system 1 may further include slave ECUs 15 to 18 , in addition to the ECUs 11 to 14 .
  • the slave ECUs 15 to 18 are connected to the in-vehicle LAN 15 and may be configured to transmit the simultaneous storing request to the master ECU 11 , on occurrence of an anomaly such as a malfunction of the self device.
  • the slave ECUs 15 to 18 may include the same functions as the above-described functions of the slave ECUs 12 to 14 .
  • the simultaneous storing request is transmitted at the time t 51 , on detection of a malfunction of the slave ECU 13 .
  • any of the slave ECUs 12 , 14 to 18 may transmit the simultaneous storing request at another time point on detection of an anomaly such as a malfunction of the self device.
  • the operation of the slave ECU on detection of a malfunction may be the same as the operation of the slave ECU 13 subsequent to the time t 51 .
  • any of the slave ECUs 12 to 18 has a detected-anomaly-on-self-device storing function to store the diagnostic information in the retention storage medium of the self device on detection of an anomaly such as a malfunction in the self device.
  • the detected-anomaly-on-self-device storing function may be equivalent to the processing at step 240 subsequent to step 230 on detection of an anomaly such as a malfunction in the self device.
  • Any of the slave ECUs 12 to 18 further has a simultaneous-storing-request transmitting function to select the simultaneous storing request including the system identification code corresponding to the anomaly, on detection of an anomaly such as a malfunction in the self device, and to transmit the selected simultaneous storing request to the master ECU 11 .
  • the simultaneous-storing-request transmitting function may be equivalent to the processing at steps 250 to 290 .
  • Any of the slave ECUs 12 to 18 further has an instruction-correspondence storing function to store the diagnostic information including the input-and-output data corresponding to the system identification code in the retention storage medium of the self device, on reception of the simultaneous storing request from the master ECU 11 , when the belonging group list of the self device includes the system identification code included in the simultaneous storing request.
  • the instruction-correspondence storing function is also not to store the diagnostic information in the retention storage medium of the self device when the belonging group list of the self device does not include the system identification code included in the simultaneous storing request.
  • the instruction correspondence storing function may be equivalent to the processing at steps 240 a and 240 b. With the present configuration, even when any of the slave ECUs detects an anomaly, the data related to the anomaly can be stored in another slave ECU.
  • each of the slave ECUs 12 to 18 transmits, on detection of an anomaly in the self device in a certain case, the simultaneous storing request including the system identification code (one example of a first system identification code) corresponding to the anomaly to the master ECU 11 (one example of a storing instruction transmitting device).
  • the master ECU 11 is caused to transmit the simultaneous storing instruction (one example of a first storing instruction) including the system identification code.
  • the simultaneous storing request is one example of a first storing request.
  • the master ECU 11 transmits the simultaneous storing instruction (one example of a second storing instruction), on reception of another simultaneous storing request (one example of a second storing request) than the above-described simultaneous storing request, from another slave ECU, such as the slave ECU 12 , (one example of another device) other than the slave ECU, such as the slave ECU 15 .
  • the master ECU 11 determines, on reception of the simultaneous storing instruction, and according to the system identification code (one example of a second system identification code) included in the received simultaneous storing instruction, whether to store the diagnostic information in the slave ECU. On determination to store the diagnostic information, the master ECU 11 stores the diagnostic information including the data corresponding to the system identification code in the storage medium of the self device.
  • the present configuration enables each of the slave ECUs 12 to 18 to store the diagnostic information in another device according to the anomaly detected in the self device.
  • the diagnostic information can be stored in the self device.
  • the master ECU 11 may store the belonging group list and the stored data correspondence table of the self device.
  • the master ECU 11 may implement the processings in FIG. 4 , FIG. 5 , FIG. 9 , in addition to the processings described in the above embodiment.
  • the subject generated at step 280 is a simultaneous storing command instead of the simultaneous storing request.
  • the subject transmitted at step 290 is the simultaneous storing command instead of the simultaneous storing request, and the simultaneous storing command is sent to all the ECUs connected to the in-vehicle LAN 15 .
  • the master ECU 11 may store the belonging group list and the stored data correspondence table of the self device. In this case, at step 198 , the master ECU 11 may implement the processings of step 240 a, 240 b in FIG. 9 .
  • the master ECU 11 has a detected-anomaly-on-self-device storing function to store the diagnostic information in the retention storage medium of the self device on detection of an anomaly such as a malfunction in the self device.
  • the detected-anomaly-on-self-device storing function may be equivalent to the processing at step 240 subsequent to step 230 on detection of an anomaly such as a malfunction in the self device.
  • the master ECU 11 further has a simultaneous-storing-instruction transmitting function to select the simultaneous storing instruction including the system identification code corresponding to the anomaly, on detection of an anomaly such as a malfunction in the self device, and to transmit the selected simultaneous storing instruction to all the ECUs 11 to 18 .
  • the simultaneous-storing-instruction transmitting function may be equivalent to the processing at step 196 .
  • the master ECU 11 further has an instruction-correspondence storing function to store the diagnostic information including the input-and-output data corresponding to the system identification code in the retention storage medium of the self device, on reception of the simultaneous storing instruction from the master ECU 11 (self device) through the in-vehicle LAN 15 , when the belonging group list of the self device includes the system identification code included in the simultaneous storing instruction.
  • the instruction-correspondence storing function is also not to store the diagnostic information in the retention storage medium of the self device when the belonging group list of the self device does not include the system identification code included in the simultaneous storing instruction.
  • the instruction correspondence storing function may be equivalent to the processing at steps 198 , 240 a, 240 b.
  • the slave ECUs 12 , 13 , 15 belong to the group of the wireless system.
  • the slave ECUs 12 , 13 , 15 , 16 belong to the group of the electric power control system.
  • the slave ECUs 13 and 14 belong to the group of the illumination system.
  • the slave ECUs 14 , 17 , 18 belong to the group of a lamplight system.
  • the slave ECUs 15 , 16 , 18 belong to the group of the power train system. As exemplified here, one ECU may belong to multiple groups.
  • a user of the diagnostic tool 2 may be enabled to implement a predetermined operation on the operation unit of the diagnostic tool 2 connected to the in-vehicle LAN 15 thereby to cause the diagnostic tool 2 to transmit the simultaneous storing request to the master ECU 11 through the in-vehicle LAN 15 .
  • the contents of the system identification code included in the simultaneous storing request and the malfunction classification code may be specified beforehand.
  • a user of the diagnostic tool 2 may be enabled to set the contents with the operation unit.
  • the wireless communication device may be connected to the in-vehicle LAN 15 , and a center outside the vehicle may implement wireless communications with the wireless communication device.
  • the simultaneous storing request may be transmitted to the master ECU 11 through the wireless communication device and the in-vehicle LAN 15 .
  • the contents of the system identification code included in the simultaneous storing request and the malfunction classification code may be specified beforehand.
  • the center may be enabled to set the contents with the operation unit.
  • a storing request transmission device which is configured to transmit the simultaneous storing request to the master ECU 11 , may be equipped to the vehicle.
  • the storing request transmission device may be a communication device, such as the diagnostic tool 2 , connectable with the in-vehicle LAN 15 as needed.
  • the storing request transmission device may be a communication device, such as the center, located outside the vehicle and configured to implement wireless communications with the master ECU 11 .
  • the master ECU 11 implements the same operation as the operation in the case when receiving the simultaneous storing request from the slave ECUs 12 to 14 . It is noted that, a configuration may be employed to transmit data, which represents a vehicle local time error, to the sender of the simultaneous storing request, when the vehicle local time does not change normally in the master ECU 11 . In this way, the communication device outside the vehicle is enabled to detect an anomaly of the vehicle local time.
  • a user of the diagnostic tool 2 may be enabled to implement a predetermined operation on the operation unit of the diagnostic tool 2 connected to the in-vehicle LAN 15 thereby to cause the diagnostic tool 2 to transmit the simultaneous storing instruction through the in-vehicle LAN 15 to all the ECUs, which include the ECUs 11 to 14 connected to the in-vehicle LAN 15 .
  • the wireless communication device may be connected to the in-vehicle LAN 15 , and a center outside the vehicle may implement wireless communications with the wireless communication device.
  • the simultaneous storing request may be transmitted through the wireless communication device and the in-vehicle LAN 15 to all the ECUs, which include the ECUs 11 to 14 connected to the in-vehicle LAN 15 .
  • a storing request transmission device which is configured to transmit the storing request to the master ECU 11 , may be equipped to the vehicle.
  • the storing request transmission device may be a communication device connectable with the in-vehicle LAN 15 as needed.
  • the storing request transmission device may be a communication device located outside the vehicle and configured to implement wireless communications with the master ECU 11 .
  • a storing instruction transmission device which is configured to transmit the storing instruction to the vehicular ECU including the ECUs 11 to 14 may be the master ECU 11 equipped to the vehicle.
  • the storing instruction transmission device may be a communication device connectable with the in-vehicle LAN 15 as needed.
  • the storing instruction transmission device may be a communication device located outside the vehicle and configured to implement wireless communications with the master ECU 11 .
  • the slave ECUs 12 to 14 transmit the simultaneous storing request to the master ECU 11 on detection of a malfunction.
  • the master ECU 11 transmits the simultaneous storing instruction to each of the ECUs 12 to 14 connected to the in-vehicle LAN 15 . That is, the master ECU 11 functions as a repeater device.
  • the repeater device may be omitted.
  • the one of the slave ECUs 12 to 14 may transmit not the simultaneous storing request but the simultaneous storing instruction to another ECUs, which includes the master ECU and the other slave ECUs, connected to the vehicular LAN.
  • the ECU one example of a second ECU
  • the ECU may store the diagnostic information in the retention storage medium according to the contents of the simultaneous storing instruction, similarly to the slave ECUs 12 to 14 according to the first embodiment.
  • the master ECU 11 transmits periodically the data frame including the simultaneous storing instruction and the vehicle local time 20 . It is noted that, on reception of the multiple simultaneous storing requests from multiple ECUs in the time period after transmitting one data frame before transmitting the subsequent data frame, the master ECU 11 may generate multiple simultaneous storing instructions corresponding to the multiple simultaneous storing requests and may transmit the data frame including the multiple simultaneous storing instructions and the vehicle local time 20 to the slave ECUs 12 to 14 .
  • the slave ECU 13 generates the system identification code at the value representing the power train system, at the time t 52 . It is noted that, in an alternative configuration, at step 270 and at the time t 52 , the slave ECU 13 may generate not the system identification code at the value representing the power train system but the system identification code at a value representing all the ECUs to the malfunction that the engine revolution exceeds the allowable range.
  • both the simultaneous storing request transmitted from the slave ECU 13 and the simultaneous storing instruction transmitted from the master ECU 11 include the system identification code at the value representing all the ECUs. Therefore, all the slave ECUs 12 to 14 , which receive the simultaneous storing instruction, store the diagnostic information with the latest vehicle local time 20 in the retention storage medium.
  • the three ECUs 12 to 14 are exemplified as the slave ECUs. It is noted that, the number of the slave ECU(s) included in the vehicular system 1 may be one or two and may be four or more.
  • the value of the elapsed time information 21 is incremented by one count for each 1 second. It is'noted that, the value of the elapsed time information 21 may be incremented by one count for each another time unit such as 2 seconds, 0.5 second, or 10 seconds.
  • the bit length of the elapsed time information 21 is not limited to 22 bits.
  • the bit length of the validity determination information 22 is not limited to 2 bits.
  • the main body ECU is employed as one example of the master ECU 11 .
  • the master ECU 11 may be another ECU than the main body ECU.
  • the master ECU 11 may be an ECU for exclusive use to transmit the vehicle local time 20 .
  • the slave ECU 12 and the slave ECU 13 are for controlling the power train system
  • the slave ECU 14 is for controlling the devices of the body system.
  • the purpose of the slave ECUs 12 to 14 are not limited to the above-described example.
  • any one of the slave ECUs 12 to 14 may be for another purpose such as for controlling the air-conditioning system, the brake system, and or the like, other than or in combination of the above-described purposes.
  • the diagnostic tool 2 receives the diagnostic information and the vehicle local time 20 associated to each other from the slave ECU 13 .
  • the diagnostic tool 2 receives the latest vehicle local time 20 from the same slave ECU 13 . It is noted that, the combination of the diagnostic tool 2 and the ECU in transmission of the information is not limited to the above-described example.
  • the diagnostic tool 2 may receive the latest vehicle local time 20 from another ECU such as any of the ECUs 11 , 12 , 14 in the vehicular system than the ECU 13 .
  • the ECU 11 may retrieve the absolute time from the time counter device thereby to correct the change rate of the value of the elapsed time information 21 .
  • the elapsed time information 21 changes by T1+ ⁇ T seconds, although it has elapsed by T1 seconds according to the absolute time retrieved from the time counter device.
  • it may be determined whether it has elapsed by (1000 millisecond ⁇ T1/(T1+ ⁇ T)) seconds has elapsed, instead of the determination whether it has elapsed by 1000 milliseconds.
  • the IG device ignition system
  • the main power source of the vehicle is not limited to the IG device.
  • a main electric power source for supplying electricity to an electric motor for driving the vehicle may be exemplified as the main power source of the vehicle.
  • each function produced by execution of a program by the CPU of the control circuit in each of the ECUs 11 to 14 may be produced by another hardware such as an FPGA, which can program a circuit structure having the function.
  • the above-described vehicular system equipped to the vehicle may include: the master ECU ( 11 ); the first slave ECU ( 12 ); and the second slave ECU ( 13 ).
  • the second slave ECU ( 13 ) may be configured to transmit the storing request to the master ECU ( 11 ), on detection of a malfunction.
  • the master ECU ( 11 ) may be configured to transmit the storing instruction for causing the diagnostic information to be stored, on reception of the storing request.
  • the first slave ECU ( 12 ) may be configured, on reception of the storing instruction transmitted from the master ECU ( 11 ): to generate the diagnostic information on the first slave ECU ( 12 ); and to store the generated diagnostic information in the retention storage medium, the retention storage medium being configured to retain the validity determination information in a condition where the first slave ECU is not supplied with electric power source.
  • the storing request is transmitted from the second slave ECU ( 13 ) to the master ECU ( 11 ).
  • the storing instruction is transmitted, on reception of the storing request, from the master ECU ( 11 ) to the first slave ECU ( 12 ).
  • the first slave ECU ( 12 ) stores, on reception of the storing instruction, the diagnostic information on the first slave ECU ( 12 ).
  • the second slave ECU ( 13 ) may be further configured to include the malfunction classification code, which represents the classification of the malfunction, in the storing request to be transmitted to the master ECU ( 11 ).
  • the master ECU ( 11 ) may be further configured to include the malfunction classification code, which is included in the storing request received from the second slave ECU ( 13 ), in the storing instruction to be transmitted.
  • the first slave ECU ( 12 ) may be further configured to include the malfunction classification code, which is included in the storing instruction received from the master ECU ( 11 ), in the diagnostic information on the first slave ECU ( 12 ).
  • the present configuration enables easily to specify the classification of the malfunction, which is detected by another ECU, causing the first slave ECU ( 12 ) to store the diagnostic information.
  • the second slave ECU ( 13 ) may be further configured to include the predetermined system identification code in the storing request to be transmitted to the master ECU ( 11 ).
  • the master ECU ( 11 ) may be further configured to include the system identification code, which is included in the storing request received from the second slave ECU ( 13 ), in the storing instruction to be transmitted.
  • the first slave ECU ( 12 ) may be further configured to determine whether to store the diagnostic information on the first slave ECU ( 12 ) according to the system identification code included in the storing instruction received from the master ECU ( 11 ).
  • the second slave ECU ( 13 ) is enabled to control whether to cause the first slave ECU ( 12 ) to generate and store the diagnostic information by using the system identification code.
  • the system identification code, which the second slave ECU ( 13 ) includes in the storing request, may be the system identification code related to the detected malfunction.
  • the first slave ECU ( 12 ) may be further configured: to store the diagnostic information on the first slave ECU ( 12 ), when the system identification code, which is included in the storing instruction received from the master ECU ( 11 ), is a code corresponding to a group to which the first slave ECU ( 12 ) belongs; and not to store the diagnostic information on the first slave ECU ( 12 ), when the system identification code, which is included in the storing instruction received from the master ECU ( 11 ), is not a code corresponding to the group to which the first slave ECU ( 12 ) belongs.
  • the diagnostic information is stored by the first slave ECU ( 12 ).
  • the diagnostic information is not stored by the first slave ECU ( 12 ). Therefore, information useful for analysis of the malfunction can be selectively stored, and the resource for storing the diagnostic information can be restrained.
  • the first slave ECU ( 12 ) may be further configured: to select data according to the system identification code included in the storing instruction received from the master ECU ( 11 ); and to include the selected data in the diagnostic information and store the diagnostic information.
  • data related to a malfunction occurring in the second slave ECU ( 13 ) can be selectively stored, thereby to restrain a resource for storing the diagnostic information.
  • the vehicular system may further include a third slave ECU ( 14 ).
  • the master ECU ( 11 ) may be further configured: to change the value of the elapsed time information ( 21 ) by a time unit according to the elapse of the time; to generate the vehicle local time ( 20 ) including the elapsed time information ( 21 ); and to transmit the generated vehicle local time ( 20 ) with the storing instruction to the first slave ECU ( 12 ).
  • the first slave ECU ( 12 ) may be further configured, on reception of the vehicle local time ( 20 ) and the storing instruction from the master ECU ( 11 ): to associate the diagnostic information on the first slave ECU ( 12 ) with the vehicle local time ( 20 ); and to store the associated diagnostic information on the first slave ECU ( 12 ) and the vehicle local time ( 20 ) in the retention storage medium.
  • the third slave ECU ( 14 ) may be configured, on reception of the vehicle local time ( 20 ) and the storing instruction from the master ECU ( 11 ): to associate the diagnostic information on the third slave ECU ( 14 ) with the vehicle local time ( 20 ); and to store the associated diagnostic information on the third slave ECU ( 14 ) and the vehicle local time ( 20 ) in the retention storage medium, the retention storage medium being configured to retain the validity determination information in a condition where the third slave ECU is not supplied with electric power source.
  • the first slave ECU ( 12 ) and the third slave ECU ( 14 ) store the vehicle local time ( 20 ) provided from the master ECU ( 11 ) all together. Therefore, the time used as the storing time of the diagnostic information can be managed uniformly in the master ECU ( 11 ).
  • the vehicular system equipped to the vehicle includes the first ECU and the second ECU.
  • the first ECU may be configured to transmit the storing instruction for causing diagnostic information to be stored, on detection of a malfunction.
  • the second ECU may be configured, on reception of the storing instruction transmitted from the first ECU: to generate diagnostic information on the second ECU; and to store the generated diagnostic information on the second ECU in the retention storage medium, the retention storage medium being configured to retain the validity determination information in a condition where the second ECU is not supplied with electric power source.
  • the storing instruction is transmitted from the first ECU to the second ECU, and the second ECU, which receives the storing instruction, stores the diagnostic information on the second ECU.
  • the diagnostic information is generated and stored in the second ECU.
  • the ECU equipped to the vehicle may be configured, on reception of the storing instruction from the outside: to generate the diagnostic information on the ECU; and to store the generated diagnostic information in the retention storage medium, the retention storage medium being configured to retain the validity determination information in a condition where the ECU is not supplied with electric power source.
  • the storing instruction transmission device may be configured to transmit the storing instruction to the vehicular ECU ( 11 to 14 ), the vehicular ECU ( 11 to 14 ) being configured, on reception of the storing instruction from the outside: to generate diagnostic information on the self device; and to store the generated diagnostic information in the retention storage medium, the retention storage medium being configured to retain validity determination information in a condition where the self device is not supplied with electric power source.
  • the present disclosure may also encompass the storing instruction transmission device configured to transmit the storing instruction to the vehicular ECU ( 11 to 14 ).
  • the storing instruction transmission device is equipped to the vehicle and may be configured, on reception of the storing request from the outside, to transmit the storing instruction to the vehicular ECU ( 11 to 14 ).
  • the present disclosure may further encompass the storing request transmission device configured to transmit the storing request to the storing instruction transmission device.
  • the ECU communicable with the storing instruction transmission device ( 11 ) may include the storing request transmission unit configured, on detection of an anomaly by the self device, to transmit the first storing request, which includes the first system identification code corresponding to the anomaly, to the storing instruction transmission device ( 11 ) thereby to cause the storing instruction transmission device ( 11 ) to transmit the first storing instruction, which includes the first system identification code.
  • the ECU may further include the instruction correspondence storing unit configured to receive the second storing instruction, when the storing instruction transmission device ( 11 ) transmits the second storing instruction on reception of the second storing request from a device other than the ECU; to determine whether to store the diagnostic information on the ECU, according to the second system identification code included in the received second storing instruction; and to store the diagnostic information, which includes data corresponding to the second system identification code, in the storage medium of the self device, on determination to store.
  • the instruction correspondence storing unit configured to receive the second storing instruction, when the storing instruction transmission device ( 11 ) transmits the second storing instruction on reception of the second storing request from a device other than the ECU; to determine whether to store the diagnostic information on the ECU, according to the second system identification code included in the received second storing instruction; and to store the diagnostic information, which includes data corresponding to the second system identification code, in the storage medium of the self device, on determination to store.
  • the present configuration enables one ECU to store the diagnostic information in another device according to the anomaly detected in the self device.
  • the diagnostic information can be stored in the self device.
  • the above structures of the embodiments can be combined as appropriate.
  • the above processings such as calculations and determinations may be performed by any one or any combinations of software, an electric circuit, and the like.
  • the software may be stored in a non-transitory computer readable medium, and may be transmitted via a transmission device such as a network device.
  • the electric circuit may be an integrated circuit, and may be a discrete circuit.
  • the elements producing the above processings may be discrete elements and may be partially or entirely integrated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Small-Scale Networks (AREA)
US13/419,903 2011-03-18 2012-03-14 Vehicular system, ecu, storing instruction transmission device, and storing request transmission device Abandoned US20120239246A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/288,473 US20140277925A1 (en) 2011-03-18 2014-05-28 Vehicular system, ecu, storing instruction transmission device, and storage request transmission device
US15/209,787 US10099703B2 (en) 2011-03-18 2016-07-14 Vehicular system, ECU, storing instruction transmission device, and storing request transmission device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2011061098 2011-03-18
JP2011-061098 2011-03-18
JP2012007346A JP5556824B2 (ja) 2011-03-18 2012-01-17 車載システム、ｅｃｕ、記憶指示送信装置、および記憶要求送信装置
JP2012-007346 2012-01-17

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/288,473 Division US20140277925A1 (en) 2011-03-18 2014-05-28 Vehicular system, ecu, storing instruction transmission device, and storage request transmission device

Publications (1)

Publication Number Publication Date
US20120239246A1 true US20120239246A1 (en) 2012-09-20

Family

ID=46757030

Family Applications (3)

Application Number Title Priority Date Filing Date
US13/419,903 Abandoned US20120239246A1 (en) 2011-03-18 2012-03-14 Vehicular system, ecu, storing instruction transmission device, and storing request transmission device
US14/288,473 Abandoned US20140277925A1 (en) 2011-03-18 2014-05-28 Vehicular system, ecu, storing instruction transmission device, and storage request transmission device
US15/209,787 Active US10099703B2 (en) 2011-03-18 2016-07-14 Vehicular system, ECU, storing instruction transmission device, and storing request transmission device

Family Applications After (2)

Application Number Title Priority Date Filing Date
US14/288,473 Abandoned US20140277925A1 (en) 2011-03-18 2014-05-28 Vehicular system, ecu, storing instruction transmission device, and storage request transmission device
US15/209,787 Active US10099703B2 (en) 2011-03-18 2016-07-14 Vehicular system, ECU, storing instruction transmission device, and storing request transmission device

Country Status (3)

Country Link
US (3) US20120239246A1 (ja)
JP (1) JP5556824B2 (ja)
DE (1) DE102012102112A1 (ja)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170270068A1 (en) * 2016-03-15 2017-09-21 Honda Motor Co., Ltd. Communication system
CN110412970A (zh) * 2018-04-27 2019-11-05 罗伯特·博世有限公司 在多ecu系统中执行车辆诊断的方法
FR3097986A1 (fr) * 2019-06-26 2021-01-01 Continental Automotive Gmbh Calculateur de contrôle moteur pour véhicule automobile
US20210157902A1 (en) * 2018-08-10 2021-05-27 Denso Corporation Vehicle information communication system
CN113377393A (zh) * 2020-03-10 2021-09-10 上汽通用汽车有限公司 一种车载系统主节点的诊断刷新系统及方法
US11373464B2 (en) * 2017-07-10 2022-06-28 Sumitomo Electric Industries, Ltd. Vehicle-mounted communications device, log collection method, and log collection program
US20220317753A1 (en) * 2021-03-30 2022-10-06 Honda Motor Co.,Ltd. In-vehicle electronic system, vehicle, control method, and computer-readable storage medium
US11467821B2 (en) 2018-08-10 2022-10-11 Denso Corporation Vehicle master device, installation instruction determination method and computer program product
US11604637B2 (en) 2018-08-10 2023-03-14 Denso Corporation Electronic control unit, vehicle electronic control system, difference data consistency determination method and computer program product
US11656771B2 (en) 2018-08-10 2023-05-23 Denso Corporation Electronic control unit, vehicle electronic control system, activation execution control method and computer program product
US11671498B2 (en) 2018-08-10 2023-06-06 Denso Corporation Vehicle master device, update data verification method and computer program product
US11669323B2 (en) 2018-08-10 2023-06-06 Denso Corporation Vehicle electronic control system, program update notification control method and computer program product
US11683197B2 (en) 2018-08-10 2023-06-20 Denso Corporation Vehicle master device, update data distribution control method, computer program product and data structure of specification data
US11709666B2 (en) 2018-07-25 2023-07-25 Denso Corporation Electronic control system for vehicle, program update approval determination method and program update approval determination program
US11822366B2 (en) 2018-08-10 2023-11-21 Denso Corporation Electronic control unit, vehicle electronic control system, rewrite execution method, rewrite execution program, and data structure of specification data
US11876898B2 (en) 2018-08-10 2024-01-16 Denso Corporation Vehicle master device, security access key management method, security access key management program and data structure of specification data
US11907697B2 (en) 2018-08-10 2024-02-20 Denso Corporation Vehicle electronic control system, center device, vehicle master device, display control information transmission control method, display control information reception control method, display control information transmission control program, and display control information reception control program
US11926270B2 (en) 2018-08-10 2024-03-12 Denso Corporation Display control device, rewrite progress display control method and computer program product
US11928459B2 (en) 2018-08-10 2024-03-12 Denso Corporation Electronic control unit, retry point specifying method and computer program product for specifying retry point
US11934823B2 (en) 2018-07-25 2024-03-19 Denso Corporation Electronic control system for vehicle, program update approval determination method and program update approval determination program
US11941384B2 (en) * 2018-08-10 2024-03-26 Denso Corporation Vehicle master device, rewrite target group administration method, computer program product and data structure of specification data
US11947953B2 (en) 2018-08-10 2024-04-02 Denso Corporation Vehicle electronic control system, progress screen display control method and computer program product
US11999360B2 (en) 2018-08-10 2024-06-04 Denso Corporation Vehicle master device, control method for executing rollback, computer program product for executing rollback and data structure of specification data
US12030443B2 (en) 2018-08-10 2024-07-09 Denso Corporation Vehicle electronic control system, distribution package download determination method and computer program product

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101655685B1 (ko) * 2015-06-16 2016-09-07 현대자동차주식회사 차량용 통합제어기의 고장진단방법
JP2019045914A (ja) * 2017-08-29 2019-03-22 ローベルト ボッシュ ゲゼルシャフト ミット ベシュレンクテル ハフツング 制御装置及び車両の制御システム
JP7147532B2 (ja) * 2018-12-13 2022-10-05 株式会社デンソー 電子制御装置
CN114148271B (zh) * 2021-12-21 2024-03-01 宁波弗浪科技有限公司 一种车机系统的检测控制系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8321086B2 (en) * 2008-06-23 2012-11-27 Mando Corporation Gateway control apparatus for vehicles and travel information recording method thereof

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5491631A (en) * 1991-12-25 1996-02-13 Honda Giken Kogyo Kabushiki Kaisha Fault diagnostic system for vehicles using identification and program codes
JP3657027B2 (ja) * 1995-05-25 2005-06-08 株式会社小松製作所 車両故障診断装置の時間管理システム及び方法
JPH10274602A (ja) * 1997-03-31 1998-10-13 Toyota Motor Corp 車両用通信制御装置
JP2000145533A (ja) * 1998-11-09 2000-05-26 Nissan Motor Co Ltd 車両用電子制御装置
JP2000146765A (ja) 1998-11-09 2000-05-26 Nissan Motor Co Ltd 車両用電子制御装置
JP2002193070A (ja) * 2000-12-26 2002-07-10 Fujitsu Ten Ltd Ｅｃｕ
JP3896858B2 (ja) * 2002-02-01 2007-03-22 株式会社デンソー 車両制御システム及び車両用電子制御装置
JP4306765B2 (ja) * 2007-06-08 2009-08-05 株式会社デンソー 故障診断用情報収集装置
JP5195472B2 (ja) 2009-02-02 2013-05-08 トヨタ自動車株式会社 車両用故障診断システム、車両用故障診断方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8321086B2 (en) * 2008-06-23 2012-11-27 Mando Corporation Gateway control apparatus for vehicles and travel information recording method thereof

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10394739B2 (en) * 2016-03-15 2019-08-27 Honda Motor Co., Ltd. Communication system for in-vehicle diagnostic data
US20170270068A1 (en) * 2016-03-15 2017-09-21 Honda Motor Co., Ltd. Communication system
US11373464B2 (en) * 2017-07-10 2022-06-28 Sumitomo Electric Industries, Ltd. Vehicle-mounted communications device, log collection method, and log collection program
CN110412970A (zh) * 2018-04-27 2019-11-05 罗伯特·博世有限公司 在多ecu系统中执行车辆诊断的方法
US11934823B2 (en) 2018-07-25 2024-03-19 Denso Corporation Electronic control system for vehicle, program update approval determination method and program update approval determination program
US11709666B2 (en) 2018-07-25 2023-07-25 Denso Corporation Electronic control system for vehicle, program update approval determination method and program update approval determination program
US11669323B2 (en) 2018-08-10 2023-06-06 Denso Corporation Vehicle electronic control system, program update notification control method and computer program product
US11822366B2 (en) 2018-08-10 2023-11-21 Denso Corporation Electronic control unit, vehicle electronic control system, rewrite execution method, rewrite execution program, and data structure of specification data
US11467821B2 (en) 2018-08-10 2022-10-11 Denso Corporation Vehicle master device, installation instruction determination method and computer program product
US11604637B2 (en) 2018-08-10 2023-03-14 Denso Corporation Electronic control unit, vehicle electronic control system, difference data consistency determination method and computer program product
US11656771B2 (en) 2018-08-10 2023-05-23 Denso Corporation Electronic control unit, vehicle electronic control system, activation execution control method and computer program product
US11671498B2 (en) 2018-08-10 2023-06-06 Denso Corporation Vehicle master device, update data verification method and computer program product
US12030443B2 (en) 2018-08-10 2024-07-09 Denso Corporation Vehicle electronic control system, distribution package download determination method and computer program product
US11683197B2 (en) 2018-08-10 2023-06-20 Denso Corporation Vehicle master device, update data distribution control method, computer program product and data structure of specification data
US20210157902A1 (en) * 2018-08-10 2021-05-27 Denso Corporation Vehicle information communication system
US11999360B2 (en) 2018-08-10 2024-06-04 Denso Corporation Vehicle master device, control method for executing rollback, computer program product for executing rollback and data structure of specification data
US11876898B2 (en) 2018-08-10 2024-01-16 Denso Corporation Vehicle master device, security access key management method, security access key management program and data structure of specification data
US11907697B2 (en) 2018-08-10 2024-02-20 Denso Corporation Vehicle electronic control system, center device, vehicle master device, display control information transmission control method, display control information reception control method, display control information transmission control program, and display control information reception control program
US11947953B2 (en) 2018-08-10 2024-04-02 Denso Corporation Vehicle electronic control system, progress screen display control method and computer program product
US11926270B2 (en) 2018-08-10 2024-03-12 Denso Corporation Display control device, rewrite progress display control method and computer program product
US11928459B2 (en) 2018-08-10 2024-03-12 Denso Corporation Electronic control unit, retry point specifying method and computer program product for specifying retry point
US11941384B2 (en) * 2018-08-10 2024-03-26 Denso Corporation Vehicle master device, rewrite target group administration method, computer program product and data structure of specification data
FR3097986A1 (fr) * 2019-06-26 2021-01-01 Continental Automotive Gmbh Calculateur de contrôle moteur pour véhicule automobile
CN113377393A (zh) * 2020-03-10 2021-09-10 上汽通用汽车有限公司 一种车载系统主节点的诊断刷新系统及方法
US11914444B2 (en) * 2021-03-30 2024-02-27 Honda Motor Co., Ltd. Managing activation time of slave ECUs in sleep state with a management table when ignition is turned off
US20220317753A1 (en) * 2021-03-30 2022-10-06 Honda Motor Co.,Ltd. In-vehicle electronic system, vehicle, control method, and computer-readable storage medium

Also Published As

Publication number Publication date
US10099703B2 (en) 2018-10-16
JP5556824B2 (ja) 2014-07-23
DE102012102112A1 (de) 2012-09-20
US20160318522A1 (en) 2016-11-03
US20140277925A1 (en) 2014-09-18
JP2012210918A (ja) 2012-11-01

Similar Documents

Publication Publication Date Title
US10099703B2 (en) Vehicular system, ECU, storing instruction transmission device, and storing request transmission device
US6195602B1 (en) Vehicle communication system and method for vehicles capable of automatic storing of vehicle identification code
US7512469B2 (en) Method and system for controlling behaviors of vehicle
JP4511587B2 (ja) 車両の遠隔診断システムためのデータ通信装置
CN101927738B (zh) 一种整车网络配置系统及其配置方法
CN111193649B (zh) 车辆通信系统及其控制方法
US9080530B2 (en) Electronic control apparatus and vehicle control system
JP3596433B2 (ja) 車載用電子制御装置
JP2002163895A (ja) フラッシュメモリの安全な高温作動のための装置及び方法
US20070283110A1 (en) Vehicle Data Backup Method
US7424351B2 (en) Control unit and data transmitting method
JP5861438B2 (ja) 制御装置及び処理監視方法
JP2009150798A (ja) 車両の遠隔診断システム
US20160039254A1 (en) Universal tire pressure sensor
JP2013137729A (ja) プログラム書換システム、制御装置、プログラム配信装置、識別情報記憶装置、及びプログラム書換方法
US9446634B2 (en) Universal tire pressure sensor
JP2009262676A (ja) 電子制御装置
JP2002014702A (ja) 電子制御装置
JP2007206827A (ja) 電子制御ユニット及び車載デバイス制御用プログラムの生成方法
JP2006193146A (ja) 車両診断システム
JP2009262787A (ja) 電子制御装置
JP7183884B2 (ja) 電子制御装置
JP2004042794A (ja) 制御装置及び制御システム
CN111198775A (zh) 修正eeprom存储状态异常的方法、系统和机动车
JP6350911B2 (ja) 車載ネットワークに接続される車載機器

Legal Events

Date Code Title Description
AS Assignment

Owner name: DENSO CORPORATION, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TANAKA, MASAHIKO;NATSUME, MITSUYOSHI;TAKAHASHI, YASUYUKI;AND OTHERS;SIGNING DATES FROM 20120309 TO 20120316;REEL/FRAME:028066/0499

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION