JP2000266642A - Vehicle diagnosis system and method therefor, vehicle diagnosing apparatus, vehicle-mounted electronic control device, and record medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make diagnosable vehicles without replacing cartridge by considering the difference in manufacture year and type of a vehicle even when sensors and actuators mounted onto the vehicle are different due to the difference of the manufacture year and type of the vehicle. SOLUTION: In the vehicle diagnosis system, data of a diagnosis item not supported among data of at least one or more diagnosis items included in vehicle information to be sent to a failure diagnosis tool 4 from an engine controller 2 is made a specific fixed value, and moreover, data of supported diagnosis items is set to be a value other than a specific fixed value. The vehicle information is thus constituted, thereby, judgment on the support/non support is made possible by only data values transmitted from the engine controller 2 to the failure diagnosis tool 4 without using a ROM which described support state information corresponding to type and manufacture year of the vehicle, and the like.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a vehicle diagnostic system and method for diagnosing the operating conditions of sensors and actuators by obtaining input / output signals and the like from an electronic control unit mounted on a vehicle, and the system. The present invention relates to a vehicle diagnostic device and an on-vehicle electronic control device used for a computer, and a recording medium storing a program for realizing these functions by software.

[0002]

2. Description of the Related Art Vehicle engines, transmissions,
ABS (Anti-lock Brake System), A / B (Air Bag
), EPS (Electronic Power steering), and the like, target control is performed by an on-vehicle electronic control unit (ECU). This in-vehicle electronic control device generally has a self-diagnosis function. If any failure occurs in each system, a multifunction indicator lamp (MIL) is turned on or blinks to indicate that the failure has occurred. Notify the driver.

[0003] However, it is not easy to determine what, how much, and how much failure has occurred simply by turning on or off the MIL. Therefore, at a dealer's service site or the like, in order to grasp the failure state in more detail, a failure diagnosis code (such as a failure diagnosis code defined in the SAEJ2012 standard: Diagnostic Trouble Code) and vehicle information (for example, an engine control device) are provided. In such a case, a vehicle diagnostic device for acquiring engine speed, vehicle speed, and the like from the on-vehicle electronic control device is indispensable.

In general, sensors mounted on a vehicle,
Actuators are different for each vehicle model and model. Therefore, it is necessary to prepare a vehicle diagnostic device for each vehicle type and vehicle type, which is inconvenient because of lack of versatility. Therefore, ROs storing diagnostic programs corresponding to the year and type of each vehicle are stored.
A storage means such as M is built in the memory cartridge, and the memory cartridge is freely exchangeable with respect to the main body of the vehicle diagnostic apparatus according to the year or type of the vehicle to be diagnosed.
2. Description of the Related Art A vehicle diagnostic apparatus has been developed which enables communication with on-vehicle electronic control apparatuses of all models and models using one vehicle diagnostic apparatus body. FIG. 8 is a block diagram showing an example of the system configuration.

[0005] In FIG. 8, a support data acquisition unit 102 provided on the vehicle diagnostic device side has a vehicle information input unit 10.
Based on the model and vehicle type information of the vehicle to be diagnosed input from 4, the support status storage unit 103 stores support status information indicating the mounting status of sensors and actuators for each model or vehicle type. Support status information to be read, and the on-board electronic control unit (EC
U) Identify the vehicle information supported by 101 and request its output. ECU 101 outputs only the requested vehicle information to support data acquisition unit 102.
Thus, the vehicle diagnosis is performed based on the vehicle information obtained by the support data acquisition unit 102.

[0006]

However, in the above-described method of making different memory cartridges for each vehicle type and each year, the man-hours required for developing various types of cartridges (specification specification creation, program creation, etc.) become excessively large. There was a problem that the cost was enormous. Further, when the memory cartridge is updated by the introduction of a new vehicle type or the like, it is necessary to include all the information of the old model and the vehicle type in the cartridge, and there is a problem that a huge ROM capacity is required.

Further, in order to obtain only the vehicle information supported by the on-vehicle electronic control unit, as shown in FIG. 8, a program constituting a support status storage unit 103 and a vehicle information input unit 104 on the vehicle diagnostic device side. And the vehicle-mounted electronic control device 101 requires a program that outputs only the supported vehicle information in response to a request from the support data acquisition unit 102, which causes a problem that the program becomes complicated. Was.

SUMMARY OF THE INVENTION The present invention has been made to solve such a problem, and it is an object of the present invention to accurately diagnose vehicles of different models and models without using a large number of memory cartridges and complicated programs. With the goal.

[0009]

A vehicle diagnostic system according to the present invention is a vehicle diagnostic system for performing a vehicle diagnosis by obtaining vehicle information on at least one or more diagnostic items from an on-vehicle electronic control unit. The data of the non-corresponding diagnosis item among the at least one or more diagnosis items is set to a specific fixed value, and the data of the corresponding diagnosis item is set to a value other than the specific fixed value, and the vehicle information is set to a value other than the specific fixed value. It is characterized by comprising.

[0010] In another aspect of the present invention, the on-vehicle electronic control device includes data transmission means for transmitting all the data of each diagnostic item in the vehicle information, and the on-vehicle electronic control device comprises: A data receiving means for receiving the vehicle information transmitted from the apparatus, and a correspondence or non-correspondence of each diagnosis item based on whether a data value of each diagnosis item constituting the received vehicle information is the specific fixed value or not. And a correspondence / non-correspondence determination means for determining

In another aspect of the present invention, the vehicle diagnostic device includes a display unit for displaying a physical quantity obtained by converting the vehicle information for each diagnostic item, and the display unit displays a physical quantity corresponding to each of the diagnostic items. Only the physical quantities of the diagnostic items determined to be present are displayed.

Further, the vehicle diagnosis method of the present invention is a vehicle diagnosis method in which a vehicle diagnosis device performs a vehicle diagnosis by obtaining vehicle information on at least one or more diagnosis items from a vehicle-mounted electronic control device. The vehicle information to be sent from the control device to the vehicle diagnostic device is set such that the data of the non-corresponding diagnostic item among the at least one or more diagnostic items is a specific fixed value, and the data of the corresponding diagnostic item is the It is characterized in that it is configured as a value other than a specific fixed value.

In another aspect of the present invention, the vehicle diagnosis by the vehicle diagnosis device is performed by determining whether a data value of each diagnosis item included in the vehicle information transmitted from the on-vehicle electronic control device is the specific fixed value. A correspondence / non-correspondence determination step of determining correspondence or non-correspondence of each diagnostic item based on the diagnostic data, and a data value of the diagnosis item determined to be compatible in the correspondence / non-correspondence determination step, It has a physical quantity conversion step of performing a process of converting to a physical quantity based on a conversion formula predetermined for each item, and a display step of displaying the physical quantity converted in the physical quantity conversion step.

Further, the vehicle diagnostic apparatus of the present invention is used by being connected to an on-vehicle electronic control device, and performs vehicle diagnosis by obtaining vehicle information on at least one or more diagnostic items from the on-vehicle electronic control device. A device,
Correspondence / non-correspondence determination for determining correspondence or non-correspondence of each diagnostic item based on whether the data value of each diagnostic item constituting the vehicle information sent from the on-vehicle electronic control device is a specific fixed value or not. It is characterized by comprising means.

Further, the on-vehicle electronic control device of the present invention is a vehicle-mounted electronic control device having a function of digitizing a value detected for at least one or more diagnostic items and outputting it as vehicle information. Among the above diagnosis items, the data of the non-corresponding diagnosis item is set as a specific fixed value, and the vehicle information is output as the data of the corresponding diagnosis item as a value other than the specific fixed value. And

Further, the computer-readable recording medium of the present invention has a function of digitizing a value detected for at least one or more diagnostic items and outputting the digitized value as vehicle information. A program for realizing a function of causing a computer to output data of a non-corresponding diagnostic item as a specific fixed value and output data of a corresponding diagnostic item as a value other than the specific fixed value. It is characterized by.

According to another aspect of the present invention, when a vehicle diagnosis is performed by obtaining vehicle information relating to at least one or more diagnostic items from the on-vehicle electronic control unit, the data value of each diagnostic item constituting the vehicle information is determined. A program for causing a computer to realize a function of determining correspondence or non-correspondence of each diagnostic item based on whether or not the value is a specific fixed value is recorded.

According to the present invention configured as described above, the data value in the vehicle information transmitted from the on-vehicle electronic control unit is set to a specific fixed value for an unsupported diagnostic item and is supported. Since the diagnosis item is a value other than the specific fixed value, it is possible to determine the correspondence or non-correspondence only with the data value transmitted from the vehicle-mounted electronic control device to the vehicle diagnosis device.

[0019]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. In the following embodiments, an on-vehicle electronic control device (engine controller) will be described as an example of a vehicle-mounted electronic control device.

FIG. 1 is a block diagram showing a functional configuration of a vehicle diagnostic system according to the present embodiment, FIG. 2 is a diagram showing an overall configuration of the vehicle diagnostic system according to the present embodiment, and FIG. A time chart showing a communication timing with the failure diagnosis tool 4 which is a device;
FIG.
It is a figure showing the example of composition of the vehicle information sent to.

When diagnosing a vehicle at the final inspection step of vehicle production or at a service site such as a dealer factory, as shown in FIG. 2, an engine controller (vehicle electronic control unit) mounted on the vehicle 1 of the vehicle, as shown in FIG. 2 and a failure diagnostic tool 4 with a memory cartridge 3 in which a vehicle diagnostic program is stored, are connected by a serial communication line 6 via a connector 5. Then, the engine controller 2 and the failure diagnosis tool 4 exchange data via the communication line 6 to diagnose failures of engine parts, various sensors, actuators, switches, and the like.

That is, as shown in FIG. 3, when a request to acquire engine-related data is first given from the failure diagnosis tool 4 to the engine controller 2, the engine controller 2 responds to the request as shown in Table 1 below. The values of various parameters such as the engine speed and the vehicle speed are returned to the failure diagnosis tool 4 within a predetermined time t.

[0023]

[Table 1]

As shown in FIG. 4, data returned as a response from the engine controller 2 to the failure diagnosis tool 4 (the same applies to a request from the failure diagnosis tool 4) includes information such as the ID of the engine controller 2 and the data length. Including the header bytes and 1 byte each for each of the parameters No. 1 to No. 30 shown in Table 1.
A data byte containing 0 bytes of engine related data;
It consists of a packet consisting of an error detection byte. The header byte, the data byte, and the error detection byte are all composed of hexadecimal byte data, and one byte is represented by $ 00 to $ FF ($ indicates hexadecimal), that is, when expressed in decimal. 0-255
Take values up to.

In this embodiment, the engine controller 2
The value of the data byte sent from the controller is set to {00 to {} for the parameters supported by the engine controller 2.
FE, and unsupported parameters and parameters for future expansion (Reserved) of No. 8 to No. 30 in Table 1 are fixed to $ FF. In the physical quantity conversion formula described later in this case, the minimum value of the tolerance (resolution) is 1/254 of the maximum value of the physical quantity. That is, for example, a physical quantity conversion formula for expressing 0 to 100% is [Data] × 100
/ 254 [%].

Next, a specific functional configuration of the engine controller 2 and the failure diagnosis tool 4 will be described with reference to FIG. FIG. 1A shows an engine controller 2.
FIG. 1B shows a functional configuration of the failure diagnosis tool 4. In FIG. 1A, a vehicle information detecting unit 11 of the engine controller 2 includes sensors 14,
Based on input / output signals of the actuators 15 and switches (not shown), measured values of various parameters shown in Table 1 are detected. The detected measured value may be sent to the data conversion unit 12 in real time, or may be sent to the data conversion unit 12 after being temporarily stored in a memory in a list format as shown in Table 1.

The data conversion unit 12 includes a vehicle information detection unit 11
A conversion formula (for example, in the case of an engine rotation speed, a conversion value for converting the measurement value (analog value such as voltage, pulse number, temperature, etc.)
Detected engine speed [rpm] x 254/1000
0), it is converted to any one of the digital values of $ 00 to $ FE expressed in hexadecimal. At this time, for a parameter that does not include the corresponding sensors 14 and actuators 15, etc., the byte data corresponding to the parameter is $ FF. The data transmission unit 13 transmits the packet data including the 30-byte vehicle information (engine-related data) converted by the data conversion unit 12 via the communication line 6 and the connector 5 in response to a request from the failure diagnosis tool 4. Serial transmission to the failure diagnosis tool 4 is performed.

On the other hand, the failure diagnosis tool 4 shown in FIG.
The data receiving unit 21 receives the packet data transmitted from the engine controller 2. The support / non-support determination unit 22 determines which parameters of the 30-byte engine-related data included in the packet data are supported by the engine controller 2 and which parameters are not supported. In this embodiment,
Looking at the values of the parameters constituting the data byte, if the value is any one of $ 00 to $ FE, it is determined that the parameter is supported, and if it is $ FF, the parameter is not supported. I do.

The physical quantity conversion unit 23 determines the parameters (values other than FF) that are determined to be supported by the support / non-support determination unit 22 as follows:
The value described in hexadecimal number of 00 to $ FE is converted into a value suitable for the actual physical quantity (engine speed, vehicle speed, etc.) of each parameter. At that time, the physical quantity conversion information storage unit 2
4 according to a physical quantity conversion formula (physical quantity conversion formula shown in Table 2) stored in advance for each parameter (for example, in the case of an engine speed, a parameter value × 10000/2)
54), a data value conversion process is performed. Then, the converted value is displayed on the display unit 25. The physical quantity conversion information storage unit 24 is provided in the memory cartridge 3 of FIG. 1 and stores data such as units in addition to the above-described physical quantity conversion formula.

The operator may determine whether there is a failure by checking the display on the display unit 25 or by storing standard data in the failure diagnosis tool 4 and comparing it with the data. May be used to automatically detect a failure location.

FIG. 7 is a flowchart showing the operation of the failure diagnosis tool 4 shown in FIG. 1B. 7, first, in step S1, 30 bytes of engine-related data constituting a data byte in a received packet are stored in a reception buffer of the data reception unit 21. And
In step S2, the value of the counter n indicating the number of data in the data byte is initialized to "0", and then in step S3, the value of the counter n is increased by one, and the value in step S4 is increased.
Proceed to.

In step S4, it is determined whether or not the value of the n-th data is $ FF, and the other value, that is, $ 00
If it is any one of .about..DELTA.FE, the process proceeds to step S5, and among the physical quantity conversion formulas prepared for each parameter, the n-th data value is converted to the parameter using the physical quantity conversion formula corresponding to the n-th parameter. Is converted into a physical quantity X suitable for. Then, after displaying the converted physical quantity X in step S6, it is determined in step S7 whether or not the value of the counter n is "30". If not, the process returns to step S3 to return the value of the counter n to "30". The same processing is repeated until the time is reached (see Table 1).

On the other hand, if it is determined in step S4 that the value of the n-th data is $ FF, step S5
Then, the process jumps to the process of step S7 without performing the process of step S6. As described above, the data value is ＄
If the parameter is FF, the parameter is not supported or is undefined for future expansion. Therefore, no data is displayed on the display unit 25 in this case.

[0034] Hereinafter, the O ₂ sensor there models A of (the detected value of the O ₂ sensor is a maximum value) and, the model B of the O ₂ without sensors is compared as an example.

In the case of a vehicle type A having an O ₂ sensor (see Table 2), the state of each parameter (detected value of a sensor or the like taken into the engine controller 2) is represented by: engine speed = 1020 [rpm], vehicle speed = 0 [miles / h], the engine cooling water temperature = 80 [° C.], throttle opening = 5.9 [%], the atmospheric pressure = 100 [kPaA], O ₂ sensor output = 5.0 [V], the battery voltage = If it is 14 [V], the contents of the data byte are as shown in FIG.

[0036]

[Table 2]

As shown in FIG. 5A, the output of the O ₂ sensor is 5.0 [V] at the maximum, but the data to be transmitted (the sixth byte of the data byte) is ＄
FE (5.0 [V] × 254/5).

On the other hand, in the case of the vehicle type B without the O ₂ sensor (see Table 3), if the other parameter states are the same as those of the vehicle type A except for the output of the O ₂ sensor, the contents of the data bytes are as follows: FIG. 5B is obtained. In this case, the data value of the sixth byte of the data bytes corresponding to the O ₂ sensor output that is not supported is $ FF. Note that the minimum and maximum values shown in Tables 2 and 3 indicate the range of values that can be displayed by the failure diagnosis tool 4.

[0039]

[Table 3]

As described above, in the case of the vehicle type A, the data value of the sixth byte constituting the data byte is ＄ FE indicating the maximum value of the output of the O ₂ sensor. (＄ FE × 5/254 [V]) and displayed on the display unit 25. On the other hand, in the case of car type B,
Since the data value of the sixth byte is $ FF, it is determined that the parameter is not supported or undefined, and the display on the display unit 25 is not performed.

As described above, according to the vehicle diagnosis system of the present embodiment, each parameter is supported in the vehicle 1 to be diagnosed based on only the data value of the data byte transmitted from the engine controller 2 to the failure diagnosis tool 4. Can be easily determined. By not displaying the unsupported items, erroneous diagnosis of a dealer or the like can be prevented. For the parameters that are not supported, a display indicating that the parameter is not supported may be displayed on the display unit 25.

On the other hand, if $ 00- $ FF is assigned to the value of the data byte transmitted as the value of each parameter from the engine controller 2 and the data value of the unsupported parameter is $ FF, the vehicle types A and Tables 4 and 5 show the parameter list of the vehicle type B, respectively. Here, the maximum value and the physical quantity conversion formula are different from those in Tables 2 and 3 described above.

[0043]

[Table 4]

[0044]

[Table 5]

In this case, the value of each parameter (detected value of a sensor or the like incorporated in the engine controller 2)
Are in the same state as the examples of Tables 2 and 3, the contents of the data bytes for the vehicle type A and the vehicle type B are respectively shown in FIG.
(A) and FIG. 6 (b). As is clear from FIG. 6, although the vehicle type A supports the O ₂ sensor output, and the vehicle type B does not support the output, the sixth byte of the data byte is both $ FF and Has become.

Therefore, it is not possible to discriminate whether the value of $ FF indicates the maximum value of the supported parameter or the parameter is not supported, just by looking at the contents of the data byte. Therefore, in this case, as shown in FIG. 8, the support status storage unit 103 that stores in advance what parameters are supported according to the vehicle year and vehicle type, A vehicle information input unit 104 for inputting a vehicle type is required.

As is apparent from the above description, according to the vehicle diagnosis system of the present embodiment, the support status of each diagnosis item in the diagnosis target vehicle 1 is grasped based on the vehicle type and year information, and the vehicle is supported. There is no need to incorporate in the system a complicated program that configures the support data acquisition unit 102, the support status storage unit 103, and the vehicle information input unit 104 shown in FIG. Even if a parameter such as a new sensor output by a new technology is added to the byte for future expansion, even the conversion formula is stored in the physical quantity conversion information storage unit 24 in the memory cartridge 3 shown in FIG. If this is the case, there is no need to perform other programming and data storage in the memory.

Further, since the support state of each parameter can be determined only from the vehicle information regardless of the type and year of the vehicle 1 to be diagnosed, a large number of memory cartridges 3 corresponding to the type and year of the vehicle 1 are prepared. There is no need, and the same cartridge 3 (ROM content) can be used for many vehicle types and years. Therefore, the labor (man-hours) and cost for memory cartridge development can be significantly reduced. Further, since the support status information itself is unnecessary, even when updating the cartridge, it is not necessary to include the information of the old model and the information of the vehicle type, and the ROM capacity of the memory cartridge 3 can be reduced.

Further, each parameter number is assigned by dividing the vehicle information into a number of bytes, and if a bit corresponding to each parameter number has a flag, the engine controller 2 and the engine controller 2 The data processing program in the failure diagnosis tool 4 can be simplified, and the data processing time can be reduced by suppressing an increase in the number of data bytes of vehicle information.

Note that the vehicle diagnostic system according to the present embodiment shown in FIG. 1 is actually a CPU or MPU, RO
A program that is configured by a computer system including an M and a RAM, and realizes the above-described functions,
M or ROM. In addition, it is also possible to externally supply the program to the vehicle diagnostic system of the present embodiment, and realize the functions by the operation of the supplied program.

In this case, means for supplying the program, for example, a recording medium storing the program,
The present invention is constituted. As a recording medium for storing the above program, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a DVD, a magnetic tape, a nonvolatile memory card, and the like can be used in addition to the RAM and the ROM.

Further, the functions of the above-described embodiments are realized not only by the computer executing the supplied program, but also by the operating system (OS) or other application software running on the computer. Such a program is also included in the embodiments of the present invention when the functions of the above-described embodiments are implemented in cooperation with the computer.

It should be noted that each of the above-described embodiments is merely an example of embodying the present invention, and the technical scope of the present invention is not interpreted in a limited manner. . That is, the present invention can be embodied in various forms without departing from the spirit or main features thereof.

For example, in the above embodiment, the data byte has a data length of 30 bytes, but is not limited to this. The fixed value used for the unsupported parameter is not limited to $ FF. In addition to the on-board electronic control unit for the engine (engine controller 2), the on-board electronic control unit for automatic transmission (AT) control unit, traction control (TCL) control unit and various systems such as ABS, A / B, and EPS The same applies to the device.

Further, the vehicle diagnosis device is not limited to the failure diagnosis tool 4 dedicated to failure diagnosis, but may be various devices capable of obtaining vehicle information from a vehicle and grasping the state of the vehicle. The diagnostic program may be stored in the built-in memory or various external memories without using the program. Further, the vehicle information may be failure data indicating a failure or various data and codes relating to the vehicle.

[0056]

According to the present invention, as described above, at least one
Since the data of the non-corresponding diagnostic items among the one or more diagnostic items is set to a specific fixed value, and the data of the corresponding diagnostic items is configured as a value other than the specific fixed value, the vehicle information is configured. Correspondence / non-correspondence can be determined only by the data value of the information, and the vehicle diagnostic device is supported based only on the vehicle information obtained from the on-vehicle electronic control device, regardless of the type and year of the vehicle to be diagnosed. The vehicle diagnosis can be accurately performed by judging the data of the diagnosis item which is being used. Therefore, it is not necessary to create a large number of memory cartridges according to the model and model of the vehicle, and the support status is confirmed based on the model and model information, and only the supported data is sent to the on-board electronic control unit. Since a complicated program for requesting the memory cartridge is not required, the time (man-hours) and cost required for developing the memory cartridge can be significantly reduced, and the vehicle diagnosis program can be simplified. Also, when updating the vehicle diagnosis program, it is not necessary to include information of an old model or information of a vehicle type, so that the memory capacity required for the vehicle diagnosis program can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a main functional configuration of a vehicle diagnostic system according to the present invention.

FIG. 2 is a diagram illustrating an overall configuration of a vehicle diagnosis system according to the present embodiment.

FIG. 3 is a time chart showing communication timing between the engine controller and the failure diagnosis tool according to the embodiment.

FIG. 4 is a diagram showing a configuration example of vehicle information sent from the engine controller of the embodiment to the failure diagnosis tool.

[5] O ₂ with respect to models B models A and O ₂ without sensors there sensor is a diagram showing an example of a data byte to be sent in case of applying the present embodiment.

[6] For O ₂ models B models A and O ₂ without sensors there sensor is a diagram showing an example of a data byte to be sent in case of applying other methods.

FIG. 7 is a flowchart illustrating an operation of the failure diagnosis tool according to the embodiment.

FIG. 8 is a block diagram showing a functional configuration of a conventional failure diagnosis tool.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Vehicle 2 Engine controller 3 Memory cartridge 4 Failure diagnosis tool 5 Connector 6 Communication line 11 Vehicle information detection unit 12 Data conversion unit 13 Data transmission unit 14 Sensors 15 Actuators 21 Data reception unit 22 Support / non-support determination unit 23 Physical quantity conversion Unit 24 physical quantity conversion information storage unit 25 display unit

Claims (9)

[Claims] 1. A vehicle diagnostic system for diagnosing a vehicle by a vehicle diagnostic device obtaining vehicle information on at least one or more diagnostic items from an on-vehicle electronic control device, wherein the at least one diagnostic item includes: A vehicle diagnostic system wherein the vehicle information is configured such that the data of the non-corresponding diagnostic item is a specific fixed value and the data of the corresponding diagnostic item is a value other than the specific fixed value. 2. The on-vehicle electronic control device includes data transmission means for transmitting all data of each diagnostic item included in the vehicle information, and the vehicle diagnostic device includes: Data receiving means for receiving information; and correspondence / non-compliance for determining correspondence or non-correspondence of each diagnosis item based on whether or not the data value of each diagnosis item constituting the received vehicle information is the specific fixed value or not. The vehicle diagnosis system according to claim 1, further comprising a correspondence determination unit. 3. The vehicle diagnostic apparatus according to claim 1, further comprising a display unit that displays a physical quantity obtained by converting the vehicle information for each diagnostic item, wherein the correspondence / non-correspondence determination unit determines that the vehicle information corresponds. The vehicle diagnostic system according to claim 2, wherein only the physical quantity of the item is displayed. 4. A vehicle diagnosis method in which a vehicle diagnosis device performs vehicle diagnosis by obtaining vehicle information on at least one or more diagnosis items from an on-vehicle electronic control device. In the vehicle information to be sent, among the at least one or more diagnostic items, the data of the non-corresponding diagnostic item is set as a specific fixed value, and the data of the corresponding diagnostic item is set as a value other than the specific fixed value. A vehicle diagnostic method, comprising: 5. The vehicle diagnosis in the vehicle diagnosis device is performed based on whether a data value of each diagnosis item included in the vehicle information sent from the on-vehicle electronic control device is the specific fixed value or not. A correspondence / non-correspondence determination step of determining correspondence or non-correspondence of an item, and a data value of a diagnosis item determined to be compatible in the correspondence / non-correspondence determination step are predetermined for each diagnosis item. The vehicle diagnostic method according to claim 4, further comprising: a physical quantity conversion step of performing a process of converting the physical quantity into a physical quantity based on the conversion formula; and a display step of displaying the physical quantity converted in the physical quantity conversion step. . 6. Used in connection with a vehicle-mounted electronic control device,
A vehicle diagnostic device for performing vehicle diagnosis by obtaining vehicle information on at least one or more diagnostic items from the on-vehicle electronic control device, wherein each diagnostic item constituting the vehicle information sent from the on-vehicle electronic control device A vehicle diagnostic apparatus comprising: a correspondence / non-correspondence determination unit that determines correspondence or non-correspondence of each diagnostic item based on whether or not the data value is a specific fixed value. 7. An on-vehicle electronic control device having a function of digitizing a value detected for at least one or more diagnostic items and outputting the digitized value as vehicle information, wherein at least one of the at least one diagnostic item is not supported. The vehicle-mounted electronic control device according to claim 1, wherein the data of the diagnosis item is set as a specific fixed value, and the vehicle information is output as data of the corresponding diagnosis item as a value other than the specific fixed value. 8. A function of digitizing a value detected for at least one or more diagnostic items and outputting the digitized value as vehicle information, wherein data of a non-corresponding diagnostic item among the at least one or more diagnostic items is stored. A computer-readable recording medium having recorded thereon a program for causing a computer to have a function of outputting data of a corresponding diagnosis item as a value other than the specific fixed value as well as a specific fixed value. 9. When performing vehicle diagnosis by obtaining vehicle information on at least one or more diagnostic items from the on-vehicle electronic control device, the data value of each diagnostic item constituting the vehicle information is a specific fixed value. A computer-readable recording medium on which is recorded a program for causing a computer to realize a function of determining correspondence or non-correspondence of each diagnostic item based on the program.