JP2005346392A - High-speed access type fault diagnostic system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a data-transfer quantity by absorbing difference in support state of diagnostic items for each vehicle and realize high-speed access while ensuring reliability. <P>SOLUTION: A vehicle 10 is connected to a data center 30 via a communication medium 20. When communication between an ECU 11 and a fault diagnosis application server 31 via an ECU interface 12 is established, an address space request is transmitted from the fault diagnosis application server 31 to the ECU 11 to obtain an address space code, and consequently the address space code is recognized as the major-division address space information of the ECU 11. Then, the fault diagnosis application server 31 sequentially accesses all the accessible addresses corresponding to the space address codes, reads fault diagnosis data, stores the data in a memory, and stores only information on abnormal items in a database server 32. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a high-speed access type failure diagnosis system that reads diagnosis data for each failure diagnosis item stored in an in-vehicle computer system at high speed.

  A system of a vehicle such as an automobile is complicatedly electronically controlled, and when an abnormality occurs in the system, advanced knowledge and judgment are required to investigate the cause. For this reason, recently, it is indispensable for failure diagnosis unless the vehicle information is read by connecting the failure diagnosis device to an on-vehicle electronic device, and the read vehicle information is analyzed and stored in a database or the like. This can be useful for vehicle management.

  In general, the number of failure diagnosis items is enormous, and “support information” indicating which items are supported differs depending on the vehicle type and grade. Therefore, when reading vehicle diagnostic information, it is necessary to change the address for accessing the in-vehicle computer (in-vehicle electronic device) according to the “support information” for each vehicle type and grade. Becomes very cumbersome.

For this reason, in Patent Document 1, by first obtaining “support information” from the in-vehicle electronic control device by communication, it is possible to flexibly cope with various in-vehicle electronic control systems, and in the case of data exchange A failure diagnosis device that can reduce the burden is disclosed. Specifically, a common code for specifying data is fixed in advance between the in-vehicle electronic control device and the failure diagnosis device regardless of the difference in the system, and data is stored based on the common code. Thus, it is possible to know which data is supported by the in-vehicle electronic control device, and to prevent reading of unsupported data.
JP-A-10-10014

  However, as described above, the failure diagnosis items have an enormous number of items as compared with other vehicle parameters. Therefore, as disclosed in Patent Document 1, the “support information” is communicated from the in-vehicle electronic device. In the technology to obtain, first, the code for obtaining the address information for data storage must be read for a huge number of diagnostic items, which increases the total data transfer amount and takes communication time. is there. Further, when remote diagnosis is performed from a remote location, not only does it cause a packet drop, but the reliability is lowered, and the cost of the packet is also increased.

  The present invention has been made in view of the above circumstances, and absorbs differences in the support status of diagnostic items for each vehicle to reduce the amount of data transfer and to enable high-speed access while ensuring reliability. The object is to provide an access type fault diagnosis system.

  In order to achieve the above object, a first high-speed access type failure diagnosis system according to the present invention holds a code set in advance for an address space for each vehicle that allows access from an external system, An in-vehicle computer system that stores diagnosis data for each failure diagnosis item at each address, and an address space connected to the in-vehicle computer system and corresponding to the code acquired from the in-vehicle computer system, for each failure diagnosis item And a data collection system that reads the diagnostic data at a high speed.

  A second high-speed access type failure diagnosis system according to the present invention includes an in-vehicle computer system that stores diagnosis data for each failure diagnosis item at each address in an address space for each vehicle that allows access from an external system, and the above-described in-vehicle system. Connected to the computer system, upon request from an external system, accesses the address space of the in-vehicle computer system according to a code set in advance for the address space, reads the diagnostic data for each fault diagnosis item, and reads the diagnostic data An interface device that selects and transmits only abnormal values from the computer, and is connected to the in-vehicle computer system via the interface device. Only abnormal value of the diagnostic data, characterized by comprising a data acquisition system to read at high speed.

  The high-speed access type failure diagnosis system according to the present invention absorbs the difference in the support status of diagnostic items for each vehicle, reduces the data transfer amount, enables high-speed access while ensuring reliability, and reduces communication costs. In addition, the vehicle management cost can be reduced.

  Embodiments of the present invention will be described below with reference to the drawings. 1 to 5 relate to an embodiment of the present invention, FIG. 1 is a basic configuration diagram of a high-speed access type failure diagnosis system, FIG. 2 is an explanatory diagram showing an example of an address space code, and FIG. FIG. 4 is an explanatory diagram showing acquisition of fault diagnosis information, and FIG. 5 is an explanatory diagram showing data acquisition and storage.

  A high-speed access type failure diagnosis system (hereinafter simply referred to as “failure diagnosis system”) 1 shown in FIG. 1 is used as a data collection system via a communication medium 20 in an in-vehicle computer system mounted on a vehicle 10 such as an automobile. It is formed by connecting the data centers 30. As a connection by the communication medium 20, a direct connection cable, an arbitrary network, or a connection by wireless communication can be used. When the vehicle 10 and the data center 30 are connected via a network or wireless communication, Remote fault diagnosis is possible.

  The vehicle 10 includes an electronic control unit (ECU) 11 mainly composed of a microcomputer, which is representative of an in-vehicle computer system, interposed between an ECU 11 and an external system (data center 30). An ECU interface 12 is provided as an interface device that performs data transmission according to a communication protocol. Further, the data center 30 is provided with a failure diagnosis application server 31 for executing a failure diagnosis application for performing failure diagnosis by data communication with the vehicle 10 and a database server 32 for storing failure diagnosis data.

  The system mounted on the vehicle includes an engine control system that executes fuel injection control and ignition timing control, an AT (Automatic Transmission) control system that executes powertrain control for an automatic transmission, etc. Air-mix damper, air-conditioner control system that automatically controls the blower speed, air-conditioner compressor ON / OFF, etc., cruise control system that adjusts the throttle valve opening so that the running speed converges to the arbitrarily set vehicle speed , ABS (Anti lock Brake System) that controls the brake hydraulic pressure during braking to avoid wheel lock, and TCS (Traction Control System) that controls the driving force of the driving wheel according to the driving conditions to prevent idling of the driving wheel ), 4WS (Four Wheel steering System) that actively controls the rudder angle of the rear wheel according to the vehicle speed, etc. Thus, in this embodiment, the ECU 11 serves as a central system for controlling each system in a distributed manner and controlling one of a plurality of electronic control systems interconnected by an in-vehicle LAN or the like, or a plurality of control systems collectively. This will be explained as a representative.

  The ECU 11 provides control information (engine speed, throttle opening, etc.), IO information (light ON / OFF, wiper ON / OFF, etc.), diagnostic information (abnormal / normal, etc.) using an on-board self-diagnosis function. Stored in memory. In particular, the diagnosis information includes “0” indicating normality and “1” indicating abnormality for each diagnosis item without having “support information” indicating which of the enormous diagnosis items are supported. Bit data is recorded. In this case, unsupported diagnostic items are always stored with data “0” representing normality. This is based on the simple and clear principle that “the part that does not exist does not fail.” In failure diagnosis, it is important to know which item is abnormal, not “which item is normal”. Because there is.

  Addresses for storing such diagnostic information are accessed except for addresses that are allowed to be accessed from the outside, that is, addresses that cause malfunction of the in-vehicle system or return uncertainties. Is assigned to an address (accessible address) that does not adversely affect the in-vehicle system. Since this accessible address differs depending on the in-vehicle system (for example, it differs depending on the year of sale of the automobile), as shown in FIG. 2, the accessible address for storing diagnostic information is represented by code data called “address space code”. Express and each vehicle has its own address space code.

  That is, the address space code does not indicate whether or not the failure diagnosis item is supported, but indicates whether the address can be accessed, and each address in the address space indicated by the address space code. There is a one-to-one correspondence between each diagnosis item and failure diagnosis. On the data center 30 side, a table describing the relationship between the “address space code”, “accessible address”, and “diagnostic item” is held in the failure diagnosis application server 31, the database server 32, etc. By sequentially accessing all the addresses indicated by the read address space code, diagnostic information including unsupported for each diagnostic item can be acquired.

  For example, in the case of a vehicle having the address space code “0”, it is normal (including unsupported) or abnormal for each diagnostic item by sequentially accessing the addresses 0x0000 to 0x00FF and reading the data. I can know. In addition, in the case of a vehicle having the address space code “2”, normal access is performed for each diagnosis item by sequentially accessing the addresses 0x0000 to 0x01FF and the addresses 0x0210 to 0x02cF and reading the data. You can know whether it is abnormal (including unsupported) or abnormal.

  Next, an operation mode of the failure diagnosis system 1 using the above address space code will be described.

  First, the vehicle 10 is connected to the data center 30 via the communication medium 20. When communication between the ECU 11 and the failure diagnosis application server 31 via the ECU interface 12 is established, the failure diagnosis application server 31 of the data center 30 sends an address to the ECU 11 of the vehicle 10 as shown in FIG. Send a spatial request. Then, the ECU 11 receives the address space request and sends out the address space code of the own vehicle, and this address space code is recognized on the failure diagnosis application server 31 side as the large category address space information of the ECU 11.

  As shown in FIG. 4, the failure diagnosis application server 31 refers to the accessible address corresponding to the address space code, sequentially accesses all the addresses of this accessible address, reads out the failure diagnosis data, and stores it in the memory. At this time, the ECU 11 always returns data (normal value) for each failure diagnosis item corresponding to each address, even if it is not supported. The failure diagnosis application server 31 reads all diagnosis data of failure diagnosis items corresponding to individual addresses, and stores only the information of abnormal items in the database server 32.

  That is, as shown in FIG. 5, for example, in the vehicle types A and B, even if the accessible address space is the same, if the diagnostic items to be supported are different, there is no abnormality in the non-support items (the nonexistent portion does not fail) ), And small differences in the address space are absorbed. In the ECU data storage table of the database server 32, for the diagnosis item common to the address space, in the case of the vehicle type A, when the received diagnosis data are all normal values and there are no abnormal parts, information “no abnormality” is displayed. Only the abnormal item is stored in the vehicle type B. The other diagnostic items are implicitly treated as normal, and the number of items stored in the ECU data storage table is the most common abnormality that can occur in the vehicle type.

Considering the amount of data communication at this time, for example, for 100 vehicles of the same type (same vehicle type, same grade), there are 500 diagnostic items, 300 supported items, and the failure rate is almost zero. In the case of “No abnormality” is stored, and there are rarely one or two failures, the data communication amount in this embodiment can be expressed by the following equation (1), “Support information” The amount of data communication by the conventional failure diagnosis apparatus with “” read can be expressed by the following equation (2).
500 [items] × 100 [units] = 50000 [items] (1)
(500 [item] +300 [item]) × 100 [unit] = 80000 [item] (2)

  That is, when considering the data communication amount of only one vehicle, the failure diagnosis system 1 of this embodiment reads diagnosis data for all 500 items including unsupported, and the conventional failure diagnosis apparatus has 500 items of support information. Then, 300 items of diagnostic data based on the support information are read. Therefore, the difference between the two vehicles is not extremely large per vehicle, but when the number of vehicles increases, the amount of data communication can be reduced compared to the conventional failure diagnosis apparatus.

  In the above description, it is assumed that the ECU interface 12 has only a media conversion function according to the communication protocol of the communication medium 20, but the filter function is not limited to this media conversion function. By providing, the number of items stored in the database server 32 can be greatly reduced.

  That is, an accessible address corresponding to the address space code of the host vehicle is stored in the system on the vehicle 10 side, for example, in the ECU interface 12, and a data transmission request (address space request is sent to the ECU from the failure diagnosis application server 31). The ECU interface 12 sequentially accesses all the accessible addresses of the ECU 11 and reads the diagnostic data. Then, only the information of the abnormal item is selected from the read diagnosis data and transferred to the failure diagnosis application server 31. The abnormal item information is transferred to the fault application server 31 by setting the direct storage address of the ECU 10 or a pointer indicating the storage address in addition to the abnormal value itself.

The failure diagnosis application server 31 handles items other than abnormal items as implicitly normal. As described above, the database server 32 stores only information on abnormal items, and stores information “no abnormality” when there is no abnormal part. The amount of data communication and the number of items stored in the database in this case can be expressed by the following equation (3) by the filter function of the ECU interface 12, and the conventional data communication amount expressed by the above equation (2), Compared with the conventional number of stored items represented by the following equation (4), the amount of data communication and the number of stored items can be greatly reduced.
1 [item] × 100 [units] = 100 [items] (3)
300 [items] × 100 [units] = 30000 [items] (4)

  As described above, in the present embodiment, it is possible to absorb a small difference in failure diagnosis items for each vehicle only by a global classification called an address space code, and to reduce the data transfer amount of diagnosis. This enables high-speed communication while ensuring reliability, and can reduce vehicle management costs. Especially, when performing remote diagnosis from a remote location, packet drop can be effectively prevented, It is possible to improve reliability and reduce communication costs. Furthermore, by transferring only abnormal items and storing them in the database, it is possible to effectively reduce both communication costs and vehicle management costs.

Basic configuration of high-speed access type fault diagnosis system Explanatory drawing showing an example of address space code Explanatory drawing showing acquisition of address space code Explanatory drawing showing acquisition of failure diagnosis information Explanatory diagram showing how data is acquired and stored

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 High speed access type failure diagnosis system 10 Vehicle 11 Electronic controller 12 ECU interface 30 Data center 31 Failure diagnosis application server 32 Database server
Agent Patent Attorney Susumu Ito

Claims (4)

An in-vehicle computer system that stores a preset code for an address space for each vehicle that allows access from an external system, and stores diagnostic data for each fault diagnosis item in each address of the address space;
A data collection system connected to the in-vehicle computer system, accessing an address space corresponding to the code acquired from the in-vehicle computer system, and reading the diagnostic data for each fault diagnosis item at high speed. High-speed access type fault diagnosis system. An in-vehicle computer system that stores diagnosis data for each fault diagnosis item at each address in an address space for each vehicle that allows access from an external system;
Connected to the in-vehicle computer system, and in response to a request from an external system, accessed the in-vehicle computer system address space according to a code preset for the address space, and read and read the diagnostic data for each fault diagnosis item An interface device that selects and sends out only abnormal values from diagnostic data;
A data collection system that is connected to the in-vehicle computer system via the interface device, and that reads only an abnormal value among the diagnostic data for each failure diagnosis item stored in the in-vehicle computer system at a high speed in response to a request to the interface device And a high-speed access type fault diagnosis system. In the above data collection system,
3. The high-speed access according to claim 1, further comprising a database that stores only abnormal value items and handles other items as normal among the diagnosis data for each failure diagnosis item of the in-vehicle computer system. Type fault diagnosis system. In the above database,
4. The fast access failure diagnosis system according to claim 3, wherein when all of the diagnosis data for each failure diagnosis item of the in-vehicle computer system is normal, information indicating no abnormality is stored.

Images