DATA OUTPUT DEVICE FOR A VEHICLE

Abstract

A data output device (15) for a vehicle performs data communication with at least one external diagnostic tool (3, 4) and performs data communication with at least one vehicle-side control unit (11-14), which outputs specific diagnostic data in response to a request from the diagnostic tool (3, 4). The data output device (15) comprises: a cache memory section (23) for storing the specific diagnostic data; a cache memory section (24) for controlling the cache memory section (23) to store the specific diagnostic data output from the control unit (11-14); and a cache read section (25) for reading the specific diagnostic data in the cache memory section (23) and responding to the diagnostic tool (3, 4) based on the specific diagnostic data when the request from the diagnostic tool (3, 4) requests the specific diagnostic data.

Description

[0001] The present invention relates to a data output device for a vehicle which is applicable to a vehicle-mounted self-system or on-board system including a plurality of electronic control units or control devices.

[0002] Both JP 2003 - 87 174 A and JP 2011 - 203 082 A (corresponding to US 2011 / 0 238 262 A1) describe an in-vehicle system in which a plurality of electronic control units (hereinafter referred to as ECUs) are connected via a communication line to enable communication or data exchange. The in-vehicle system is capable of communicating diagnostic data between the plurality of ECUs. The in-vehicle system is also capable of transmitting data to an external device located outside a vehicle. For example, a configuration is known that outputs diagnostic data to an external device to assist in fault diagnosis in a vehicle, for example, in a repair shop or the like.

[0003] An in-vehicle system contains multiple ECUs. Each of the ECUs must be able to provide its own specific control function to manage the equipment and devices in a vehicle. As a result, it may take a long time for the ECU to transmit diagnostic data to an external device.

[0004] Furthermore, the communication line of the vehicle-side system must also be able to provide its own specific data communication function in order to control the vehicle. As a result, the communication line may take a long time to transmit / receive data related to a diagnosis. From another perspective, it is also undesirable for data traffic on the communication line to increase when transmitting / receiving data related to a diagnosis.

[0005] Furthermore, the on-board system and the external device should use a common communication standard to enable data communication between them. However, manufacturers may select and use different communication standards for the on-board system and the external device. For example, if the external device is a general-purpose microcomputer, it is desirable that a multi-purpose or general-purpose communication standard can be used. This requires the on-board system to be compatible with a variety of communication standards.

[0006] US 2011 / 0 264 318 A1 discloses a method for remote monitoring of a plurality of vehicles.

[0007] It is an object of the present invention to provide a data output device for a vehicle which allows high-speed transmission of data relating to a diagnosis.According to an exemplary aspect of the present invention, a data output device for a vehicle that performs data communication with a diagnostic tool outside the vehicle and performs data communication with an on-vehicle control unit that outputs specific diagnostic data in response to a request from the diagnostic tool comprises: a buffer or cache storage section for storing the specific diagnostic data; a cache storage section for controlling the cache storage section to store the specific diagnostic data output from the control unit; and a cache reading section for reading the specific diagnostic data in the cache storage section and responding to the diagnostic tool based on the specific diagnostic data when the request from the diagnostic tool requests the specific diagnostic data.

[0008] In this configuration, the cache storage section stores the specific diagnostic data in the storage section. After the storage operation by the cache storage section, a request for the specific diagnostic data can be transmitted from the diagnostic tool. In this case, the cache reading section reads the specific diagnostic data stored in the cache storage section and responds to the diagnostic tool based on the stored specific diagnostic data. Thus, from the diagnostic tool's perspective, the specific diagnostic data is supplied from a data output section for a vehicle that is closer to the diagnostic tool than the control unit. Consequently, high-speed transmission of the data related to the diagnosis becomes achievable.

[0009] The data output device thus allows high-speed transmission of diagnostic data by means of a control unit having a gateway function to enable communication between different communication standards.

[0010] Further details, aspects and advantages of the present invention will become more apparent from the following detailed description with reference to the drawings.

[0011] It shows: Fig. 1 is a block diagram of a system according to a first embodiment; Fig. 2 is a block diagram showing the structure of a cache memory section in the first embodiment; Fig. 3 is a flowchart of a transmission / reception process in the first embodiment; Fig. 4 is a flowchart of a response process in the first embodiment; Fig. 5 is a flowchart of an update process in the first embodiment; Fig. 6 is a flowchart of a collection process in a second embodiment; Fig. 7 is a flowchart of a portion of the collection process in a third embodiment; Fig. 8 is a flowchart of another part of the collection process in the third embodiment; and Fig. 9 is a flowchart of a transmission / reception process in a fourth embodiment. < First embodiment >

[0012] In Fig. 1, a maintenance support system 1 for a vehicle includes an in-vehicle control system (VH-SYS) 2 installed in a vehicle, and diagnostic tools (DIAG-TL1 and DIAG-TL2) 3 and 4. The diagnostic tools 3 and 4 are located at a vehicle dealership and / or vehicle repair shop. The diagnostic tools 3 and 4 receive data related to diagnosis (hereinafter referred to as diagnostic data) from the in-vehicle control system 2. The diagnostic tools 3 and 4 support a vehicle maintenance or repair process based on this diagnostic data. For example, the diagnostic tools 3 and 4 support the maintenance process by presenting diagnostic data to a mechanic or the like.Diagnostic tools 3 and 4 can also automatically diagnose the condition of the vehicle-side control system 2 based on the diagnostic data, for example, using a preset condition determination function. In this case, the diagnostic tools display the diagnostic results to the technician. Diagnostic tools 3 and 4 can be configured as the first diagnostic tool 3 and the second diagnostic tool 4.

[0013] The maintenance process may include a diagnosis to determine whether or not the vehicle-side control system 2 is normal. The maintenance process may also include a diagnosis to locate the faulty or failed section of the vehicle-side control system 2. Furthermore, the maintenance process may include a process to repair the faulty or failed section in the vehicle-side control system 2.

[0014] The diagnostic data may include various data points that may contribute to the vehicle maintenance process. For example, the diagnostic data may include real-time data showing the current operating status of control units. The diagnostic data may include recorded data showing the operating status of the vehicle-side control system 2 when a particular event occurs or has occurred. The recorded data is data that shows at least one operating status in the past, has a relatively high capacity, and has been recorded without changes. Examples of events for which such data may be recorded include any anomalies, a predetermined driving condition, or a predetermined or specified operating condition.The diagnostic data may also include data showing the result of a self-diagnosis obtained in the vehicle-side control system 2.

[0015] The first diagnostic tool 3 is connected to the vehicle-side control system 2 in a wired or wireless connection. Thus, a wired connection device comprising a cable and corresponding connectors or plugs, or a transmission / reception system for wireless communication, may be provided between the first diagnostic tool 3 and the vehicle-side control system 2. The first diagnostic tool 3 provides data communication via the connection according to a specified communication protocol. For example, the first diagnostic tool 3 may handle CAN (Controller Area Network) or LIN (Local Interconnect Network), which are used as the vehicle LAN (Local Area Network). Thus, the first diagnostic tool 3 may also be referred to as a selected or dedicated tool that has a selected interface that conforms to a specified vehicle communication standard.

[0016] The second diagnostic tool 4 is connected to the on-vehicle control system 2 via a wired connection or wireless connection via an external communication line 5. A wired connection device including a cable and connectors or a wireless communication transmission / reception system may be provided between the communication line 5 and the on-vehicle control system 2. The communication line 5 may be constituted, for example, by a mobile phone line or the Internet. The second diagnostic tool 4 provides data communication via the communication line 5 according to a predetermined communication protocol. The second diagnostic tool 4 can handle a general-purpose communication standard, such as Ethernet (registered trademark). Thus, the second diagnostic tool 4 can be called a general-purpose tool, which has a general-purpose interface conforming to a general-purpose communication standard.

[0017] The diagnostic tools 3 and 4 transmit the request signal RQ for requesting or querying diagnostic data from one of the control units 11 to 14 to the on-board system 2. The diagnostic tools 3 and 4 also transmit the request signal RQ to the on-board control system 2 when specific diagnostic data included in a plurality of diagnostic data types is requested. The diagnostic tools 3 and 4 receive diagnostic data DATA from the on-board control system 2. The diagnostic tools 3 and 4 also receive a delay signal DF indicating that the response to the request signal RQ is delayed.

[0018] The vehicle-side control system 2 includes a plurality of vehicle-side control units (ECUs) 11 to 15. The plurality of control units 11 to 15 are constituted by electronic control units. The electronic control units are constituted by a microcomputer containing a computer-readable storage medium. The storage medium non-temporarily (non-volatilely) stores a computer-readable program. The storage medium may be constituted by a semiconductor memory or a hard disk or the like. The program is executed by the electronic control units to cause the electronic control units to operate as the device set forth in this specification and to cause the electronic control units to perform the control method set forth in this specification.The means formed by the electronic control units can also be called a functional block to obtain a specific function or module.

[0019] The plurality of control units 11 to 15 are interconnected directly or indirectly via an internal communication line 16 installed in the vehicle to enable data transmission between them. The communication line 16 is provided by a vehicle network, for example, CAN or LIN. The control units 11, 13, 14, and 15 are directly connected to the communication line 16. The control unit 12 is indirectly connected to the communication line 16 via the control unit 11. The vehicle-side control system 2 may include a plurality of control units, the number of which is greater than that of the control units shown in the drawing.

[0020] Upon receiving the request signal RQ, the control units 11 to 14 perform a predetermined diagnostic process. In one of the diagnostic processes performed by the control units 11 to 14, response data containing the diagnostic data is transmitted in response to the request signal RQ. If the request signal RQ requests specified diagnostic data, the control units 11 to 14 respond with response data containing the specified diagnostic data.

[0021] The control unit (ECU1) 11 and the control unit (ECU2) 12 provide a power supply control system for controlling the vehicle's power supply or power source. For example, the control unit 11 is an engine control unit for controlling the engine. The control unit 12 is a dependent control unit for controlling accessories or peripherals associated with the engine. The control unit (ECU3) 13 is a control unit for controlling body equipment of the vehicle, such as a door locking device, a lighting device, or the speedometer. The control unit (ECUn) 14 is a control unit for controlling, for example, the vehicle's air conditioning system.

[0022] The control unit (ECU4) 15 is configured to communicate with the other control units 11 to 14 via the communication line 16. The control unit 15 is also configured to communicate with the diagnostic tools 3 and 4. The control unit 15 is provided in the on-vehicle control system 2 to provide a data output device for the vehicle that outputs data to the outside of the on-vehicle control system 2.

[0023] The control unit 15 conforms to a plurality of communication standards and provides data communication between the plurality of communication standards. The control unit 15 provides a gateway function by which data exchange is established between the plurality of communication standards. The control unit 15 is also referred to as a gateway control unit (GW-ECU) or an external connection control unit. For example, the control unit 15 provides CAN-compliant communication between itself and the diagnostic tool 3. The control unit 15 provides CAN-compliant communication between itself and the communication line 16. The control unit 15 also provides Ethernet (registered trademark)-compliant communication between itself and the diagnostic tool 4, i.e., the communication line 5.

[0024] The control unit 15 includes a data relay section (DATA-TRF) 21 that provides the gateway function. The data relay section 21 establishes communication between different types of communication standards between the diagnostic tools 3 and 4 and the communication line 16. The data relay section 21 has the gateway function of relaying data between the diagnostic tools 3 and 4 and the control units 11 to 14, which conform to different communication standards. In this configuration, even if the communication standards of the diagnostic tools 3 and 4 are different from the communication standards of the control units 11 to 14, data communication is established between them using the gateway function of the data relay section 21. This allows the control unit 15 with the gateway function to achieve faster transmission of data related to diagnosis.

[0025] The control unit 15 includes a cache management section (CASH-MNG) 22 and a cache storage section (CASH-MRP) 23. The cache management section 22 includes a cache storage section (CASH-IN) 24 and a cache read section (CASH-OUT) 25.

[0026] The cache storage section 24 monitors the data received by the data relay section 21 from the control units 11 to 14 via the communication line 16. The cache storage section 24 selects only a specific or specified data value or data point from the plurality of data points received from the data relay section 21 and writes the specific data point into the cache storage section 23 to store the specific data point.

[0027] The cache reading section 25 monitors the data received from the diagnostic tools 3 and 4 via the data relay section 21. The cache storing section 24 determines whether or not the specific diagnostic data item requested based on the data received from the data relay section 21 is stored in the cache storing section 23. The cache reading section 25 reads the specific data item requested by the diagnostic tools 3 and 4 and stored in the cache storing section 23 from the cache storing section 23. The cache reading section 25 transmits the read specific data item to the diagnostic tools 3 and 4 via the data relay section 21.

[0028] The specific data item stored in the cache storage section 23 can include only fixed and large-capacity specific diagnostic data included in the plurality of types of diagnostic data. That is, the control units 11 to 14 are configured to output the plurality of types of diagnostic data including the specific diagnostic data. However, the cache storage section 24 stores only the specific diagnostic data in the cache storage section 23. Consequently, the capacity of the cache storage section 23 is reduced. The specific diagnostic data is data that does not need to change over time. A typical example of this specific diagnostic data is history data recorded at a fixed point in time.Since only the fixed data has been stored in the cache memory section 23, the data stored in the cache memory section 23 can be used even if the time has elapsed.

[0029] The diagnostic tools 3 and 4 and the vehicle-side control system 2 constitute a data communication system. In the data communication system, diagnostic data obtained from the control units 11 to 14 is transmitted to the diagnostic tools. In the data communication system, as viewed from the diagnostic tools 3 and 4, the cache management section 22 and the cache storage section 23 are located at positions more proximal or closer to the diagnostic tools than the control units 11 to 14. The cache management section 22 and the cache storage section 23 temporarily store the diagnostic data and return the diagnostic data in response to a request. Therefore, as viewed from the diagnostic tools 3 and 4, the cache management section 22 and the cache storage section 23 can also be referred to as proxy data providers located at proximal positions.

[0030] As in Fig. 2, the cache memory section 23 stores the plurality of diagnostic data items DATA. The plurality of diagnostic data items DATA may have a plurality of index information items for specifying the plurality of diagnostic data items DATA. In the example shown in the drawing, diagnostic data 23c is specified with source information 23a indicating the control units serving as the generation source of the diagnostic data and service information 23b indicating the type of the diagnostic data. For example, freeze frame data (FFD) with the generation source ECU1 and the surface ID of 02 is stored in the cache memory section 23. Freeze frame data (FFD) with the generation source ECU2 and the service ID of 0A is stored in the cache memory section 23. ROB data (ROB) with the generation source ECU1 and the service ID of AB is stored in the cache memory section 23.In the cache memory section 23, service factor data (UOD) with the generation source ECU3 and the service ID of A4 is stored. The freeze frame data is a set of data points obtained by recording the vehicle conditions when abnormalities were detected in the control units. The freeze frame data includes information indicating the dates and times at which the abnormalities were detected, information indicating the types of abnormalities, signals indicating the operating conditions corresponding to the control units, signals from a plurality of sensors, signals on the communication line 16, etc.

[0031] The ROB data is a set of data points obtained by recording the vehicle states when events other than the anomaly were detected in the control units. The ROB data can also be referred to as a record of behavior and contains data recorded when the vehicle exhibits certain behavior patterns. For example, ROB data includes information representing the dates and times at which events were detected, information indicating the event types, signals indicating the operating states of corresponding control units, signals from the plurality of sensors, signals on the communication line 16, etc.

[0032] The service factor data is a set of data points obtained by recording the vehicle conditions when certain events are detected by the vehicle user. The service factor data includes information indicating the dates and times at which the events were detected, information indicating event types, signals indicating the operating states of corresponding control units, signals from the plurality of sensors, signals on the communication line 16, etc.

[0033] The freeze frame data, the ROB data, and the operation factor data are the diagnostic data items. The freeze frame data, the ROB data, and the operation factor data are also the specific diagnostic data items among the diagnostic data items that serve as storage destinations. These specific diagnostic data items have relatively large data capacities or data amounts among the data items conveyed via the communication line 16. Consequently, each of the specific data items is transmitted from the corresponding control unit via the communication line 16, which takes a relatively long specific time. Each of the specific diagnostic data items is a fixed data item and cannot be changed. However, a plurality of specific diagnostic data items may be generated according to the number of factors for which they are recorded.

[0034] Fig. 3 shows a transmission / reception process 140 performed by the control unit 15. The transmission / reception process 140 includes a relay process providing the data relay section 21, a storage process providing the cache storage section 24, and a read process providing the cache read section 25.

[0035] In step 141, the control unit 15 receives the request RQ from the diagnostic tools 3 and 4. In step 142, the control unit 15 determines whether or not the request RQ requests the specific diagnostic data serving as the storage process target. If the data requested by the request RQ is not the storage target, the transmission / reception process 140 proceeds to step S143.

[0036] In step 143, the control unit 15 transmits the request RQ to the targeted control unit, that is, the control unit that is the source of the data. For example, if the request RQ requests data from the control unit 11, the control unit 15 transmits the request RQ to the control unit 11 via the communication line 16. For example, if the request RQ requests data from the control unit 12, the control unit 15 transmits the request RQ to the control unit 11 via the communication line 16. The control unit 11 further transmits the request RQ to the control unit 12. In step 143, the control unit 15 establishes data exchange between different communication standards. For example, the control unit 15 converts the request RQ from the diagnostic tool 4 compliant with Ethernet (registered trademark) to the request RQ compliant with CAN and transmits the converted request RQ to the communication line 16.

[0037] In step 144, the control unit 15 determines whether or not response data has been received in response to the request RQ. If the response data is returned from the targeted control unit, the transmission / reception process 140 proceeds to step 145. If the response data is not returned from the targeted control unit, the transmission / reception process 140 proceeds to step 148.

[0038] In step 145, the control unit 15 determines whether or not the received response data is the storage target, that is, whether or not the received response data is the determined diagnostic data. If the response data is not the storage target, the transmission / reception process 140 proceeds to step 146. If the response data is the storage target, the transmission / reception process 140 proceeds to step 147.

[0039] In step 146, the control unit 15 transmits the received response data to the diagnostic tools 3 and 4. In step 146, the control unit 15 facilitates data exchange between different communication standards. For example, the control unit 15 converts the response data compliant with CAN into response data compliant with Ethernet (registered trademark) and transmits the converted response data to the communication line 5.

[0040] There are cases where the transmission / reception process 140 returns to step 144, and it takes a long time before the control unit 15 receives the response data. The in-vehicle control system 2 includes the plurality of control units 11 to 14. In addition, the communication paths and communication priorities in the in-vehicle control system 2 are complicated. For example, the control unit 11 can only return the response data via the communication line 16. However, the control unit 12 returns the response data via the control unit 11 and further via the communication line 16. Consequently, it may take a long time for the control unit 15 to receive the response data. Furthermore, the specific diagnosis data is relatively large in size or large in capacity. Consequently, it may take a long time to transmit the specific diagnosis data via the communication line 16.When the response data is the specific diagnosis data, it takes a long time for the control unit 15 to receive the response data.

[0041] Steps 148 and 149 provide a maintenance process in which, when it takes a long time before the response data is received, a delay notification response indicating the delay in data communication is transmitted to the diagnostic tools 3 and 4. In step 148, the control unit 15 determines whether or not the duration of step 144 exceeds a certain set time. Step 144 is repeated until the certain time is exceeded. If the certain time is exceeded, the transmission / reception process 140 proceeds to step 149. In step 149, the control unit 15 transmits the delay notification response DF to the diagnostic tools 3 and 4.

[0042] Steps 148 and 149 provide a delay notification response section for transmitting the delay notification response DF to the diagnostic tools 3 and 4 when the time for responding to the request from the diagnostic tools 3 and 4 exceeds the specified time. As a result, even if the response takes a long time, it is possible to deliver the delay notification response from the control unit 15 as the data output device without depending on the other control units 11 to 14.

[0043] The flow through steps 141, 142, 143, 145, and 146 provides the relay process for the diagnostic data that is not the storage destination. The relay process is for the diagnostic data that is different from the specified diagnostic data.

[0044] When the transmission / reception process 140 returns to step 142 and it is found that the data requested by the request RQ is the storage destination, the transmission / reception process 140 proceeds to step 150. In step 150, the control unit 15 determines whether or not the specific diagnostic data indicated by the request RQ has already been stored, that is, whether or not the specific diagnostic data indicated by the request RQ has been stored in the cache memory section 23. If the data requested by the request RQ is the storage destination and the data has not yet been stored, the transmission / reception process 140 proceeds to step 143. Thereafter, the above steps 143 to 145 are performed. When the transmission / reception process 140 proceeds from step 142 to step 150 to step 143, the response data is the storage destination. The process branches from step 145 to 147.

[0045] In step 147, the control unit 15 stores the received response data in the cache memory section 23. In other words, in step 147, the control unit 15 stores the received response data and thereby performs the caching process. Thereafter, the transmission / reception process 140 proceeds to step 146, where the received response data is transmitted to the diagnostic tools 3 and 4.

[0046] The flow through steps 141, 142, 150, 143, 145, 147, and 146 provides the relay process and the storage process when a specific diagnostic data item is first relayed. Steps 145 and 147 provide the cache storage section 24. In steps 145 and 147, the specific diagnostic data transmitted from the control units 11 to 14 in response to the request from the diagnostic tools 3 and 4 is received and stored in the cache storage section 23. Thus, the specific diagnostic data item is collected using the request from the diagnostic tools 3 and 4.

[0047] When the transmission / reception process 140 returns to step 150 and finds that the data requested by the request RQ is the storage destination and the data has already been stored, the transmission / reception process 140 proceeds to step 151. In step 151, the control unit 15 reads the specific diagnosis data requested and stored by the request RQ from the cache memory section 23. Thereafter, the transmission / reception process 140 proceeds to step 146, where the read data is transmitted to the diagnostic tools 3 and 4. That is, using the specific diagnosis data that has undergone the storage process, the specific diagnosis data is transmitted to the diagnostic tools 3 and 4. In this case, the control unit 5 responds to the request from the diagnostic tools 3 and 4 based on the specific diagnosis data that has been provisionally stored without performing the relay process.In other words, the control unit 15 responds to the request from the diagnostic tools 3 and 4 without transmitting the request RQ to the control units 11 to 14 as generation sources of the specific diagnostic data. That is, the control unit 15 responds to the request from the diagnostic tools 3 and 4 without accessing the control units 11 to 14 as generation sources.

[0048] The flow through steps 141, 142, 150, 151 and 146 provides a reading process and a response process when the stored specific diagnostic data is requested.

[0049] Fig. Figure 4 shows a response process 160 performed by each of the control units 11 to 14. In step 161, the control units 11 to 14 receive the request RQ, which is forwarded by the control unit 15. In step 162, the control units 11 to 15 transmit the response data to the control unit 15. The response data transmitted here is diagnostic data.

[0050] Fig. 5 shows an update process 170 performed by the control unit 15. The update process 170 includes a deletion process for deleting the specific diagnostic data stored in the cache memory section 23. The update process 170 also includes a retrieval process for retrieving data in the control unit as a generation source based on the specific diagnostic data stored in the cache memory section 23.

[0051] In step 171, the control unit 15 inputs various signals. The signals input here include command signals indicated by the on-vehicle control system 2 or the diagnostic tools 3 and 4, and status signals indicating the statuses of the plurality of control units 11 to 14. The command signals include a command signal for requesting deletion of the data stored in the cache memory section 23. The status signals include a signal indicating an initialization process in the control units 11 to 14 and a signal indicating an error in the control units 11 to 14.

[0052] In step 172, the control unit 15 determines whether or not the input signal requests deletion of the data from the cache memory section 23. If deletion of the data from the cache memory section 23 is requested, the update process 170 proceeds to step 173. In step 173, the control unit 15 deletes the determined diagnostic data stored in the cache memory section 23.

[0053] The step 173 after the step 172 provides the deletion section for deleting the specific diagnostic data stored in the cache memory section 23 in response to the request from the diagnostic tools 3 and 4. The configuration allows the specific diagnostic data stored in the cache memory section 23 to be deleted.

[0054] If deletion of the data from the cache memory section 23 is not requested in step 172, the update process 170 proceeds to step 174. In step 174, the control unit 15 determines whether or not the initialization process has been performed in any other control units 11 to 14. For example, if the power supply to the other control units 11 to 14 is temporarily interrupted, the initialization process can be performed. When the other control units 11 to 14 are initialized, the data stored in these control units 11 to 14 is deleted. In addition, in step 175, the control unit 15 determines whether or not any error has occurred in the other control units 11 to 14 and the data stored in these control units 11 to 14 has been destroyed. For example, the data may have been destroyed due to a failure in a storage device.If the initialization process is performed or such an error with data destruction occurs in the other control units 11 to 14, the update process 170 goes to step 176. If neither the initialization process nor an error has occurred, the update process 170 ends.

[0055] Step 173 following steps 174 or 175 provides a deletion section that deletes the specified diagnostic data stored in the cache memory section 23 when the specified diagnostic data is lost in the control units 11 to 14. With this configuration, it is possible to avoid mismatch between the original specified diagnostic data stored in the control units 11 to 14 and the specified diagnostic data stored in the cache memory section 23.

[0056] In step 176, the control unit 15 determines whether or not the retrieval process has been requested. The retrieval process is a process for regenerating the determined diagnostic data for storage in the control units 11 to 14 based on the determined diagnostic data stored in the cache memory section 23. Whether or not the retrieval process is requested can be set in advance in the control unit 15. Alternatively, whether or not the retrieval process is necessary can be input from the diagnostic tools 3 and 4. If the retrieval process is not necessary, the update process 170 proceeds to step 173. If the retrieval process is necessary, the update process 170 proceeds to step 177.

[0057] In step 177, the control unit 15 performs the retrieval or retrieval process. In the retrieval process, the control unit 15 transmits the specific diagnosis data stored in the cache memory section 23 to the targeted other control units 11 to 14. The targeted other control units 11 to 14 receive the specific diagnosis data and store the received specific diagnosis data. Thus, based on the stored specific diagnosis data as storage data, the specific diagnosis data can be retrieved or retrieved in the control units as the generation sources.

[0058] Step 177 provides a retrieval section for, when the specific diagnosis data values in the control units 11 to 14 are lost, retrieving the specific diagnosis data in the control units 11 to 14 based on the specific diagnosis data stored in the cache memory section 23. With this configuration, it is possible to retrieve the specific diagnosis data in the control units 11 to 14 using the specific diagnosis data stored in the cache memory section 23.

[0059] According to the present embodiment, the cache management section 22 and the cache storage section 23 constitute a storage function with respect to the specific data. In the storage or caching function, the specific data is provided without accessing the generation sources of the specific data. The caching function includes a stage at which the specific data is temporarily stored. The caching function also includes the stage at which it is determined that the specific data is requested. The caching function also includes the stage at which the request is responded to based on the specific data that has been temporarily stored without accessing the generation source of the specific data. By equipping the control unit 15 with the caching function, it is possible to provide the diagnosis data at high speed in response to the request from the diagnostic tools 3 and 4.

[0060] Additionally, the control unit 15 with the gateway function is capable of performing data communication with the diagnostic tool 4 in accordance with a communication standard different from the communication standard on the communication line 16. Furthermore, the control unit 15 can provide data communication with the diagnostic tool 3 and data communication with the diagnostic tool 4. By equipping the control unit 15 with the caching function, it is possible to deliver the diagnostic data at high speed without increasing the data traffic on the communication line 16.

[0061] The diagnostic tool 4 is connected to the on-vehicle control system 2 via the general-purpose communication line 5, such as the Internet. With such a configuration, a request can be input from the diagnostic tool 4 regardless of the vehicle's operating state. For example, even when the vehicle is in a running state, an arithmetic operation process in the on-vehicle control system 2 is subject to a high load, and the data traffic on the communication line 16 is heavy, a request is expected to be input from the diagnostic tool 4. However, in the present embodiment, the control unit 15 proximal to the diagnostic tool 4 (as viewed from the diagnostic tool 4) is equipped with the caching function.Consequently, a configuration that allows connection to the diagnostic tool 4 with high versatility can also provide the diagnostic data at high speed, while suppressing influences on the function of the vehicle-side control system 2. < Second embodiment >

[0062] In the above embodiment, when the specific diagnostic data to be used as the cache processing target is first passed, the cache management section 22 stores the specific diagnostic data in the cache storage section 23. That is, the cache management section 22 provides a collection section for passively collecting the specific diagnostic data. In addition to or instead of the collection section for passively collecting the specific diagnostic data in the above embodiment, the cache management section 22 may also provide or constitute a collection section that positively collects the specific diagnostic data to be used as the cache processing target.

[0063] Fig. Figure 6 shows a collection process 280 performed by the control unit 15. The collection process 280 provides the collection section.

[0064] In step 281, the control unit 15 requests transmission of the specific diagnostic data from the other control units 11 to 14. The other control units 11 to 14 perform the response process as described above to return the response data. In step 282, the control unit 15 determines whether or not the response data has been received from the other control units 11 to 14. If the response data has been received, the collection process 280 proceeds to step 283. In step 283, the control unit 15 stores the received specific diagnostic data in the cache memory section 23.

[0065] The control unit 15 is configured to perform step 281 by being triggered by a specific event. For example, the control unit 15 can be configured to perform step 281 for each work unit of the vehicle. A work or operation unit can be, for example, a trip. The operation unit can be assumed to be a time period between the time the vehicle's power supply is turned on and the time the vehicle's power supply is turned off.

[0066] The collection process 280 provides the cache storage section 24. The collection process 280 requests the transmission of the specific diagnostic data from the control units 11 to 14 without depending on the request from the diagnostic tools 3 and 4 and stores the received specific diagnostic data in the cache storage section 23. With this configuration, the specific diagnostic data is automatically collected.

[0067] With this configuration, the control unit 14 requests only the diagnostic service, in which the capacity of the response data exceeds a certain capacity, for each operating unit of the vehicle from the other control units 11 to 14. The control unit 15, which has received the response data, stores the response data in the cache memory section 23. Thereafter, when the above diagnostic service is requested from the diagnostic tools 3 and 5, the control unit 15 responds to the diagnostic tools 3 and 4 based on the data stored in the cache memory section 23 without requesting the diagnostic service from the control units 11 to 14. This achieves faster transmission of the diagnostic data. < Third embodiment >

[0068] In the above embodiment, specific diagnostic data to serve as the cache process target is collected in response to the request from the cache management section 22. In addition to or instead of performing the collection of the specific diagnostic data as in the above embodiment, the cache management section 22 may also provide or constitute a collection section based on push communication that receives and collects the specific diagnostic data forcibly transmitted from the drive units 11 to 14.

[0069] The Fig. 7 and Fig. 8 show a collection process 390 performed by the control unit 15 and the other control units 11 to 14, wherein Fig. 7 shows a transmission process performed by the other control units 11 to 14 and Fig. 8 shows a receiving process performed by the control unit 15. The collecting process 390 provides the collecting portion.

[0070] In step 391, the other control units 11 to 14 determine whether or not the specific diagnostic data is generated. If the specific diagnostic data, that is, data serving as a cache process target, is generated, the collection process 390 proceeds to step 392. In step 392, the other control units 11 to 14 transmit the generated specific diagnostic data to the control unit 15.

[0071] In step 393, the control unit 15 receives the data. In step 394, the control unit 15 determines whether or not the received data is the cache process target. If the received data is not the cache process target, the collection process 390 ends. If the received data is the cache process target, the collection process 390 proceeds to step 395. In step 395, the control unit 15 stores the received data, that is, the determined diagnostic data, in the cache memory section 23.

[0072] The collection process 390 provides the cache storage section 24. In the collection process 390, the specific diagnostic data transmitted from the control units 11 to 14 in response to a specific operation is received and stored in the cache storage section 23. With this configuration, the specific diagnostic data is automatically collected.

[0073] With this configuration, when diagnostic data with a capacity exceeding a certain capacity is generated, the other control units 11 to 14 forcibly transmit the diagnostic data to the control unit 15. The control unit 15 that has received the diagnostic data stores the received diagnostic data in the cache memory section 23. Thereafter, when the above diagnostic service is requested from the diagnostic tools 3 and 4, the control unit 15 responds to the diagnostic tools 3 and 4 based on the data stored in the cache memory section 23 without requesting the diagnostic service from the other control units 11 to 14. This increases the transmission speed of the diagnostic data. Thus, faster transmission of the diagnostic data is achieved. < Fourth Embodiment >

[0074] In the above embodiments, when it takes a long time to respond with the specific diagnostic data, the delay notification response is transmitted from the control unit 15. When the specific diagnostic data is requested from the diagnostic tools 3 and 4, instead of or in addition to the delay notification request after the elapse of a long time, a delay notification response may also be transmitted to the diagnostic tools 3 and 4 before a long time has elapsed.

[0075] In Fig.9, a transmission / reception process 440 has step 452 between steps 150 and 143. In step 452, the control unit 15 transmits a delay notification response to the diagnostic tools 3 and 4. Step 452 is provided after the transmission / reception process 440 branches to YES in step 142. Therefore, step 452 is performed when the specific diagnostic data is requested from the diagnostic tools 3 and 4. In addition, step 452 is before step 143. As a result, in step 452, the control unit 15 transmits the request signal RQ to the other control units 11 to 15, and the delay notification response is transmitted before the specific diagnostic data is requested. Step 452 provides a delay pre-notification response section.

[0076] In this configuration, if certain diagnostic data is requested and a response to it is likely to take a long time, it is possible to inform the diagnostic tools about the delay in the response before a long time has elapsed.

Claims

[1] A data output device (15) for a vehicle, which performs data communication with a diagnostic tool (3, 4) located outside the vehicle and which performs data communication with a vehicle-side control unit (11-14) which outputs certain diagnostic data in response to a request from the diagnostic tool (3, 4), the data output device (15) comprising: a cache memory section (23) for storing the determined diagnostic data; a cache storage section (24) for controlling the cache storage section (23) to store the determined diagnostic data output from the control unit (11-14); a cache reading section (25) for reading the determined diagnostic data in the cache memory section (23) and for responding to the diagnostic tool (3, 4) based on the determined diagnostic data when the request from the diagnostic tool (3, 4) requests the determined diagnostic data; and an erasing section (173) for erasing the determined diagnostic data in the cache memory section (23) when the determined diagnostic data is lost in the control unit (11-14). [2] Data output device (15) according to claim 1, wherein: the control unit (11-14) outputs a plurality of types of diagnostic data including the determined diagnostic data; and the cache storage section (24) controls the cache storage section (23) so that only the specific diagnostic data is stored. [3] Data output device (15) according to claim 2, wherein: the specific diagnostic data are fixed data. [4] Data output device (15) according to one of claims 1 to 3, further comprising: a data relay section (21) with a gateway function for relaying data between the diagnostic tool (3, 4) and the control unit (11-14), wherein: a communication standard of the diagnostic tool (3, 4) is different from a communication standard of the control unit (11-14). [5] Data output device (15) according to one of claims 1 to 4, further comprising: a deletion section (171, 172, 173) for deleting the determined diagnostic data in the cache memory section (23) in response to the request from the diagnostic tool (3, 4). [6] Data output device (15) according to one of claims 1 to 5, further comprising: a retrieval section (177) for retrieving the determined diagnostic data in the control unit (11-14) based on the determined diagnostic data in the cache memory section (23) when the determined diagnostic data in the control unit (11-14) is lost. [7] Data output device (15) according to one of claims 1 to 6, wherein: the cache storage section (24) receives the determined diagnostic data transmitted from the control unit (11-14) in response to the request from the diagnostic tool (3, 4) and controls the cache storage section (23) to store the determined diagnostic data. [8] Data output device (15) according to claim 7, further comprising: a delay pre-notification response section (452) for transmitting a response delay message to the diagnostic tool (3, 4) before the data output device (15) requests the specific diagnostic data to the control unit (11-14) when the diagnostic tool (3, 4) requests the specific diagnostic data. [9] Data output device (15) according to one of claims 1 to 8, further comprising: a delay notification response section (148, 149) for transmitting a response delay notification to the diagnostic tool (3, 4) when a response time to the request from the diagnostic tool (3, 4) exceeds a certain time. [10] Data output device (15) according to one of claims 1 to 9, wherein: the cache storage section (24) requests the control unit (11-14) to transmit the determined diagnostic data without depending on the request from the diagnostic tool (3, 4) and controls the cache storage section (23) to store the determined diagnostic data. [11] Data output device (15) according to one of claims 1 to 10, wherein: the cache storage section (24, 390) receives the determined diagnostic data transmitted from the control unit (11-14) in response to a determined operation and controls the cache storage section (23) to store the determined diagnostic data.

Images