JP6310331B2 - Data collection apparatus and data collection method for vehicle diagnosis - Google Patents

Description

  The present invention relates to a data collection device and a data collection method for vehicle diagnosis.

  When an abnormal symptom occurs during driving of a vehicle, the driver is informed by a warning such as turning on a warning light provided on the instrument panel. When a user brings a vehicle to a dealer or a maintenance shop with an abnormal symptom or a warning associated therewith, the vehicle is diagnosed or repaired there.

  An operator (technician or the like) in charge of repair connects a fault diagnosis machine to an electronic control device (hereinafter referred to as “ECU”) of a faulty vehicle and reads information such as a fault code at the time of fault stored in the ECU. Thus, it is possible to identify an abnormal system (an electric circuit in which an abnormality has occurred) relatively easily. This type of failure diagnosis machine is widely used, and is described in Patent Document 1, for example.

  However, although there are many complaints of abnormal symptoms from the user, there is no record of the fault code, and even if the technician in charge of repair does not reproduce it even if it tries to reproduce according to the complaint, repair is difficult (so-called difficult problem In case of repair).

  For such difficult problem repair, for example, a large-capacity storage device as described in Patent Document 2 and Patent Document 3 is temporarily attached to the ECU of the target vehicle, and the user is driven for several days. Get it. Then, data necessary for failure diagnosis (operation parameter data) is collected in a storage device, and the collected data is examined by a failure diagnosing device or a failure analysis device, thereby making a detailed diagnosis.

  In Patent Document 2, since data is collected and output automatically, on / off operation of the ignition key switch 51 and on / off operation of the USB power supply by connecting to a personal computer are detected to collect and output data (summary). In Patent Document 2, which control data is selected and collected is set in the data collection unit 15 in advance by the setting unit 18 as setting means. The setting unit 18 includes an input operation unit, and a model table 19 is prepared in advance for setting work in the setting unit 18. When the operator inputs the vehicle model of the vehicle data collection device 1 from the input operation unit of the setting unit 18, the type (parameter ID) of control data to be collected stored in the model table 19 in a group is stored. The data is read by the setting unit 18 and set in the data collecting unit 15 ([0034]).

  In Patent Document 3, an operator inputs data collection conditions ([0052]). The data collection conditions here may include vehicle type, model, destination, specifications, network type, input channel number used by the data collection device 18, and baud rate of the target network 24 ([0057]). . Further, the data collection conditions include the contents (items) of the operation parameter data D, the ECU 20 that requests the data D (target ECU 20 tar), the time for continuously acquiring the data D (continuous data acquisition time), the data D A period for performing continuous acquisition (continuous data acquisition period) and a total time for data D collection (data collection total time) may be included ([0058]).

JP 05-172703 A JP 2008-070133 A JP 2013-170986 A

  As described above, in Patent Documents 2 and 3, an operator needs to set the type of operation parameter data to be collected. For this reason, there is a concern that such setting work may take a great amount of man-hours, and there is a concern that the setting contents may be incorrect due to human error.

  The present invention takes the above-described circumstances into consideration, and provides a vehicle diagnostic data collection device and data collection method capable of at least one of reducing man-hours for data collection settings and preventing erroneous data collection settings. The purpose is to provide.

A data collection device for vehicle diagnosis according to the present invention provides a data request signal for requesting operation parameter data indicating an operation state of each part of a vehicle in a state in which the vehicle collection network having a plurality of ECUs is detachably connected from the outside. Transmitting to the target ECU that is at least one of the plurality of ECUs, receiving the operation parameter data corresponding to the data request signal, and storing the data in a data storage unit;
The data collection device includes:
A type setting unit for setting the type of the target ECU based on an input from an operator ;
A data item storage unit that stores items of the operation parameter data that can be output by each of the plurality of ECUs in association with identification information of the plurality of ECUs;
Query the identity of the mounted ECU on the vehicle for each type of the target ECU set by the type setting unit identifies the mounted ECU that has received the identification information as the target ECU, it is identified as the target ECU an item of the operating parameter data the mounting ECU can output, a collection item setting unit that sets as a collection item is read from the data item storage unit based on the identification information of the mounted ECU, corresponding to the collection item A data collection management unit that transmits the data request signal for requesting the operation parameter data to the target ECU, receives the operation parameter data corresponding to the data request signal, and stores the data in the data storage unit. It is characterized by that.

  According to the present invention, since the data collection device performs at least a part of the setting of the collection item, it is possible to reduce the man-hours of the worker accompanying the setting of the collection item. In addition, since the mounted ECU notified from the vehicle is identified as the target ECU and the item corresponding to the target ECU is set as the collection item, it is possible to prevent an operator's human error due to the setting of the collection item. It becomes possible.

A data collection device for vehicle diagnosis according to the present invention provides a data request signal for requesting operation parameter data indicating an operation state of each part of a vehicle in a state in which the vehicle collection network having a plurality of ECUs is detachably connected from the outside. Transmitting to the target ECU that is at least one of the plurality of ECUs, receiving the operation parameter data corresponding to the data request signal, and storing the data in a data storage unit;
The data collection device includes:
A type setting unit for setting the type of the target ECU;
A data item storage unit that stores items of the operation parameter data that can be output by each of the plurality of ECUs in association with identification information of the plurality of ECUs;
For each type of the target ECU set by the type setting unit, the vehicle is inquired about the presence or absence of the mounted ECU, the mounted ECU is identified as the target ECU, and the mounted ECU identified as the target ECU can output the An item of operation parameter data is read from the data item storage unit based on identification information of the mounted ECU and set as a collection item, and the data requesting the operation parameter data corresponding to the collection item A data collection management unit for transmitting a request signal to the target ECU, receiving the operation parameter data corresponding to the data request signal, and storing the operation parameter data in the data storage unit;
With
The collection item setting unit is provided with the presence or absence of the on-board ECU for each type of the target ECU set by the type setting unit in response to an initial ON operation of a start switch in a state where the data collection device is connected to the vehicle. To the vehicle to set the collection item,
Subsequently, the data collection management unit starts transmission of the data request signal and storage of the operation parameter data on the condition that the start switch is turned off and then turned on again. Also good.

  Thereby, at least a part of the setting of the collection item and the start of collection of the operation parameter data can be performed by connecting the data collection device to the in-vehicle network and operating the start switch. Therefore, the operator can perform at least a part of the collection item setting and the start of operation parameter data collection with a simple operation.

  When the connection of the data collection device to the in-vehicle network is once released, the target ECU of the target ECU set by the type setting unit in response to the first-on operation of the start switch after connecting to the new in-vehicle network. A new collection item may be set by inquiring the new in-vehicle network about the presence or absence of the mounted ECU for each type. Accordingly, the diagnosis target vehicle can be easily changed by removing the data collection device from a certain vehicle (first vehicle) and replacing it with another vehicle (second vehicle).

  The connection between the data collection device and the in-vehicle network may be made via a data link connector of the vehicle, and the data collection device may be activated by power supplied from an in-vehicle power source via the data link connector. . Thereby, the starting timing of the data collection device can be set at the time of connection to the data link connector. Accordingly, the data collection device can be restarted with the attachment / detachment of the data link connector for changing the diagnosis target vehicle, and the data collection device can be easily operated even after the change of the diagnosis target vehicle. Become.

  The type setting unit may integrate a plurality of vehicle types and classify ECUs mounted on each vehicle type according to type for each function. As a result, it is possible to reduce the calculation load in the data collection device and the number of man-hours associated with the operator while reducing the input burden on the operator or preventing an input error.

A data collection method for vehicle diagnosis according to the present invention includes a data request signal for requesting operation parameter data indicating an operation state of each part of a vehicle in a state in which the vehicle is detachably connected to an in-vehicle network having a plurality of ECUs. Using a data collection device that transmits to at least one of the plurality of ECUs, receives the operating parameter data corresponding to the data request signal, and stores it in a storage unit,
The data collection device includes:
A type setting process for setting the type of the target ECU based on an input from an operator ;
A storage process for storing the operation parameter data items that can be output by each of the plurality of ECUs in the storage unit in association with identification information of the plurality of ECUs,
Query the identity of the mounted ECU on the vehicle for each type of the target ECU set by the type setting processing to recognize the mounting ECU that has received the identification information as the target ECU, it is identified as the target ECU a collection item setting process of setting a collection item is read from the storage unit based on the mounting ECU items of the operational parameter data that can be output, the identification information of the mounted ECU,
Data collection for transmitting the data request signal requesting the operation parameter data corresponding to the collection item to the target ECU, receiving the operation parameter data corresponding to the data request signal, and storing the data in the storage unit And processing.

  According to the present invention, it is possible to reduce the man-hour required for data collection setting and / or to prevent erroneous data collection setting.

It is a block diagram showing a schematic structure of a diagnostic system including a data collection device concerning one embodiment of the present invention. It is a figure which shows the various functions which a diagnostic machine main body and the said data collection device have. It is a flowchart which shows an example of the operation | work of the operator for the failure diagnosis in the said embodiment, and the whole flow of a process of a vehicle, an external diagnostic machine, and a server. It is a figure explaining the data item used in the operation | work and process of FIG. It is a flowchart which shows an example of a worker's work as advance preparation for collection of operation parameter data, and processing of the diagnostic machine body and the data collection device. It is a figure which shows an example of the input screen at the time of inputting data collection conditions in the said embodiment. It is a figure which shows an example of the various information (Identification information (ID) etc. of target ECU) according to the kind of diagnostic object part or target ECU. It is a flowchart which shows an example of the operation | work of the said operator at the time of the collection of the said operation parameter data, and the process of the said data collection device. 10 is a flowchart of the initial setting process in the embodiment (details of S24 in FIG. 8). It is a flowchart which shows an example of the operation | work of the said operator after the collection of the said operation parameter data, and the process of the said data collection device. It is a figure which shows an example of the display screen of the said diagnostic machine main body which displays the comparison result of a collection item and an output possible item. It is a flowchart of the process of the operator and the process of the diagnostic machine main body accompanying the determination of the abnormality ECU in the embodiment.

A. One Embodiment [1. Constitution]
(1-1. Overall configuration)
FIG. 1 is a block diagram showing a schematic configuration of a diagnostic system 10 (hereinafter also referred to as “system 10”) including a data collection device 18 according to an embodiment of the present invention. The system 10 includes a vehicle 12 as a diagnosis target, an external diagnosis device 14 that performs failure diagnosis of the vehicle 12 from the outside of the vehicle 12, and a server 15 that provides information on the vehicle 12 to the external diagnosis device 14. The external diagnostic machine 14 includes a diagnostic machine main body 16 (hereinafter also referred to as “main body 16”) and a data collection device 18 (data logger).

(1-2. Vehicle 12)
The vehicle 12 of the present embodiment is an automatic four-wheeled vehicle as a hybrid vehicle having a drive engine and a travel motor (both not shown). Alternatively, the vehicle 12 may be a vehicle such as a gasoline vehicle, an electric vehicle (battery vehicle), a fuel cell vehicle, or the like that does not have a traveling motor and has only an engine, and is a vehicle such as a motorcycle or an automatic tricycle. May be.

  The vehicle 12 is a plurality of electronic control devices 20a to 20i (hereinafter referred to as “first to ninth ECUs 20a to 20i” or “ECUs 20a to 20i”, collectively referred to as “ECU20”) for controlling the vehicle 12, and a gateway. 22 and a low voltage battery 24 (hereinafter also referred to as “battery 24”). In FIG. 1, only nine ECUs 20a to 20i are shown for easy understanding, but other ECUs 20 may be provided. The number of ECUs 20 can be 2 to several hundreds, for example.

  Examples of the ECU 20 include an engine ECU, a motor ECU, a transmission ECU, a vehicle behavior stability ECU (hereinafter referred to as “VSA ECU”), an anti-lock brake system ECU (hereinafter referred to as “ABS ECU”), and an electric power steering ECU. (Hereinafter referred to as “EPS ECU”), battery ECU, meter ECU, air conditioner ECU (hereinafter referred to as “air conditioner ECU”), auxiliary restraint system ECU (hereinafter referred to as “SRS ECU”), immobilizer ECU, and the like. Can do.

  The engine ECU controls the output of an engine (not shown). The motor ECU controls the output of a travel motor (not shown). The transmission ECU controls a transmission (not shown). The VSA ECU executes vehicle behavior stability (Vehicle Stability Assist) control. The ABS ECU performs antilock brake control. The EPS ECU executes steering assist control. The battery ECU controls charging / discharging of a high voltage battery or a low voltage battery 24 (not shown). The meter ECU controls a meter display device (not shown) provided on an instrument panel (not shown). The air conditioner ECU controls an air conditioner (not shown). The SRS ECU controls an airbag system (not shown). The immobilizer ECU controls an immobilizer device and a smart key system (not shown).

  Each ECU 20 includes an input / output unit 26, a calculation unit 28, and a storage unit 30. In FIG. 1, only the first ECU 20 a shows the input / output unit 26, the calculation unit 28, and the storage unit 30, and the internal configurations of the other ECUs 20 b to 20 i are omitted.

  The first to sixth ECUs 20a to 20f are connected via a communication bus 36a and constitute an in-vehicle network 34a (hereinafter also referred to as “network 34a”). The network 34a in the present embodiment is a CAN (Controller Area Network), in particular, a so-called high-speed communication CAN (hereinafter referred to as “high-speed CAN”) as defined in ISO11898. The seventh to ninth ECUs 20g to 20i are connected via a communication bus 36b and constitute an in-vehicle network 34b (hereinafter also referred to as “network 34b”). The network 34b in the present embodiment is a CAN, in particular, a so-called low-speed communication CAN (hereinafter referred to as “low-speed CAN”) as defined in ISO11519. Alternatively, the present invention can be applied to other networks such as LIN (Local Interconnect Network), FlexRay, and K line. Hereinafter, the networks 34 a and 34 b are collectively referred to as the in-vehicle network 34 or the network 34.

  The communication bus 36a and the power line 37 from the battery 24 are connected to a data link connector 38 provided in the vehicle interior (for example, a part of an instrument panel (not shown)).

  In FIG. 1, the power line 37 from the battery 24 is connected only to the connector 38, but the battery 24 is, for example, a 12V battery, and each component (for example, ECUs 20 a to 20 i) of the low voltage system of the vehicle 12. ) Also supply power.

  Further, all ECUs 20 mounted on the vehicle 12 are supplied with power via an ignition switch 40 (hereinafter referred to as “IGSW 40”), and the ECU 20 includes a case where the IGSW 40 is off. In some cases, the battery 24 may continue to be activated by receiving power supply. In this case, it is set to continue the operation different from when the IGSW 40 is on.

(1-3. External diagnostic machine 14)
As described above, the external diagnostic machine 14 includes the diagnostic machine body 16 and the data collection device 18.

(1-3-1. Diagnostic machine body 16)
(1-3-1. Overview)
The diagnostic machine body 16 performs various settings (operation settings, etc.) of the data collection device 18 and analyzes the operation parameter data D (hereinafter also referred to as “data D”) collected by the data collection device 18 to perform failure diagnosis. Do. Other diagnosis may be performed instead of the failure diagnosis (details will be described later).

  As shown in FIG. 1, the main body 16 includes an input / output unit 50, a calculation unit 52, a storage unit 54, a display unit 56, and a connector 58.

  The main body 16 can be composed of, for example, a commercially available notebook personal computer, tablet computer, or smartphone. The main body 16 is not necessarily composed of a single housing, and may be composed of, for example, a personal computer as a main body and a slave unit (relay device) as an interface with the data collection device 18.

(1-3-1-2. Various functions of the calculation unit 52)
FIG. 2 is a diagram illustrating various functions of the diagnostic machine body 16 and the data collection device 18. As shown in FIG. 2, the diagnostic machine main body 16 has a collection condition setting function 60, a data collection device communication function 62, and a data analysis function 64. Each function 60, 62, 64 is realized by the arithmetic unit 52 executing a program stored in the storage unit 54, and the like.

  The collection condition setting function 60 sets a data collection condition that is a condition (for example, an acquisition target item of the data D, an acquisition period, etc.) for the data collection device 18 to collect the data D.

  The data collection device communication function 62 is a function related to communication with the data collection device 18. The communication function 62 includes a collection condition transmission function 66 that transmits data collection conditions to the data collection device 18 and a collected data read function 68 that reads data D from the data collection device 18.

  The data analysis function 64 performs data analysis for failure diagnosis using the data D acquired from the data collection device 18. The data analysis function 64 functions as an abnormality determination unit that determines an ECU 20 in which an abnormality has occurred (hereinafter also referred to as “abnormal ECU 20mal”). The data analysis function 64 also communicates with the server 15 and functions as a mounted ECU specifying unit that specifies the ECU 20 mounted on the vehicle 12 (hereinafter also referred to as “mounted ECU 20ins”). When the mounted ECU 20ins is specified, a vehicle identification number (hereinafter referred to as “VIN”) of the vehicle 12 is used (details will be described later).

(1-3-1-3. Storage Unit 54)
The storage unit 54 (FIG. 1) stores various programs and various databases for executing the functions 60, 62, and 64. The database includes a data item database 70 (hereinafter referred to as “data item DB 70” or “DB 70”). In the DB 70, items of data D that can be collected by the data collection device 18 (hereinafter also referred to as “data items Idata”) are stored. The DB 70 classifies the data item Idata based on the type of the vehicle 12 corresponding to the drive source. As a kind of vehicle 12 according to a drive source, a gasoline car, a diesel car, a hybrid car, an electric car, etc. can be included, for example.

(1-3-2. Data collection device 18)
(1-3-2-1. Overview)
The data collection device 18 collects operation parameter data D in the vehicle 12. As shown in FIG. 1, the data collection device 18 includes an input / output unit 80, a calculation unit 82, a storage unit 84, a display unit 86, a capacitor 88, a communication line 90, a power line 92, and a connector 94. The connector 94 is, for example, a USB connector.

(1-3-2-2. Various functions of the calculation unit 82)
As shown in FIG. 2, the data collection device 18 has a main body communication function 100 and a data collection function 102. The functions 100 and 102 are realized by the arithmetic unit 82 executing the program stored in the storage unit 84 and the like. The main body communication function 100 is a function related to communication with the diagnostic machine main body 16, and the data collection function 102 is a function related to collection of data D with the vehicle 12.

  The main body communication function 100 has a collection condition reading function 104 and a collection data transmission function 106. The collection condition reading function 104 is a function for reading from the diagnostic machine body 16 a condition (data collection condition) for the data collection device 18 to collect the data D. The collected data transmission function 106 is a function for transmitting the data D collected by the data collection device 18 to the diagnostic machine main body 16.

  The data collection function 102 includes a request signal specifying function 108, a data request function 110, and a data reception / storage function 112. The request signal specifying function 108 is a function for specifying a data request signal Sreq for requesting the vehicle 12 to transmit data D. The data request function 110 is a function for requesting data D of a specific item by transmitting a data request signal Sreq to the ECU 20 (hereinafter referred to as “target ECU 20 tar”) that is a target for requesting the data D. The data reception / storage function 112 is a function that receives the data D output from the target ECU 20tar in response to the data request signal Sreq and stores it in the storage unit 84 (data storage unit).

(1-3-2-2. Storage unit 84)
The storage unit 84 stores various programs and various databases for executing the functions 100 and 102. The database includes a data item database 120 (hereinafter referred to as “data item DB 120”, “item DB 120”, or “DB 120”). Similar to the DB 70 of the main body 16, items of the operation parameter data D (data items Idata) that can be collected by the data collection device 18 are accumulated in the DB 120 of the data collection device 18. However, the data items Idata stored in the DB 120 are only those received from the main body 16. In other words, the data item Idata stored in the DB 120 is a part of the data item Idata stored in the DB 70. The DB 120 functions as a data item storage unit.

(1-3-4-2. Capacitor 88)
The capacitor 88 is charged with power from the battery 24 and supplies power into the data collection device 18 when the connector 94 is removed from the connector 38.

  In FIG. 1, the power line 92 from the connector 94 is connected only to the capacitor 88, but the power line 92 is also connected to other parts (for example, the calculation unit 82) in addition to the capacitor 88. For this reason, the electric power from the battery 24 or the capacitor 88 is also supplied to the other parts.

(1-4. Server 15)
The server 15 provides various information of the vehicle 12 to the external diagnostic machine 14 in response to a request from the external diagnostic machine 14. The server 15 includes an input / output unit, a calculation unit, a storage unit, and a display unit (all not shown). As shown in FIG. 1, the server 15 includes a vehicle database 130 (hereinafter referred to as “vehicle DB 130”) that stores various types of information related to the vehicle 12. The vehicle DB 130 is included in the storage unit.

[2. Contents of operation parameter data D]
The operation parameter data D in the present embodiment is used for failure diagnosis of the vehicle 12 and can include, for example, the following.

  For example, when it is desired to diagnose the driving state of the vehicle 12 (related to the engine and the travel motor), the engine ECU and the motor ECU are designated and data D to be acquired is acquired.

  In this case, the data D acquired from the engine ECU includes, for example, the engine based on the vehicle speed detected by a vehicle speed sensor (not shown), the temperature of engine coolant detected by a temperature sensor (not shown), and the crank angle detected by a crank angle sensor (not shown). The engine speed calculated by the ECU, the intake pressure detected by an intake pressure sensor (not shown), and various set values in the engine ECU are included.

  The data D acquired from the motor ECU includes, for example, the motor rotation number calculated by the motor ECU based on an output from a resolver (not shown), the remaining capacity of the high voltage battery for the drive motor, and various set values of the motor ECU.

[3. Fault diagnosis]
Next, various operations and processes related to failure diagnosis in the present embodiment will be described.
(3-1. Overall flow)
FIG. 3 is a flowchart showing an example of the overall flow of the worker's work for failure diagnosis and the processing of the vehicle 12, the external diagnostic device 14, and the server 15 in the present embodiment. FIG. 4 is a diagram for explaining the data item Idata used in the operation and processing of FIG.

  Steps S1 and S2 in FIG. 3 are processes in the preliminary preparation stage, and steps S3 to S6 are processes in the stage of actually collecting the data D by connecting the data collection device 18 to the vehicle 12. Steps S <b> 7 to S <b> 9 are processes at a stage where the data collection device 18 is removed from the vehicle 12 after the data D is collected and the cause of the failure is analyzed.

  In step S1, the external diagnostic machine 14 (main body 16 and data collection device 18) uses the type of the vehicle 12 related to the drive source (hereinafter also referred to as “vehicle type Cv” or “type Cv”) and the ECU 20 related to the diagnosis target part. The type (hereinafter also referred to as “ECU type Cecu” or “type Cecu”) is set based on the input from the operator.

  The vehicle types Cv that can be selected include, for example, gasoline vehicles, diesel vehicles, and hybrid vehicles. The ECU types Cecu that can be designated as acquisition targets include, for example, a large number of ECUs such as an engine ECU, a motor ECU, and a transmission ECU.

  In step S 2, the external diagnostic machine 14 extracts data items corresponding to the types Cv and Cecu (hereinafter referred to as “collection item candidates Iop”) from the data items Idata included in the data item DB 70 of the main body 16. The data is stored in the data item DB 120 of the data collection device 18 (see FIG. 4). Thereby, the collection item candidate Iop corresponding to the types Cv and Cecu is specified.

  In subsequent steps S <b> 3 to S <b> 6, data D is actually collected using the data collection device 18 attached to the vehicle 12. That is, in step S <b> 3, the data collection device 18 acquires VIN from the vehicle 12.

  In step S4, the data collection device 18 selects the ECU 20 (that is, the target ECU 20tar) that is actually mounted on the diagnosis target vehicle 12 among the plurality of ECUs 20 that belong to the ECU type Cecu set in advance preparation (S1). ) Identification information (ID) is specified. At this time, the data collection device 18 specifies the ID of each of the plurality of ECUs 20 belonging to the ECU type Cecu, and inquires of each ECU 20 by communication which ECU 20 having the ID is mounted on the vehicle 12. Hereinafter, the ID of the ECU 20 (target ECU 20tar) actually mounted on the vehicle 12 is also referred to as “IDins”.

  In step S5, the data collection device 18 corresponds to the IDins specified as the ECU 20 (mounted ECU 20ins) mounted in step S4 among the collection item candidates Iop extracted (or stored) in the advance preparation (S2). Items equipped in the ECU 20 are set as items of data D to be actually collected (hereinafter referred to as “collected items Idet”) (see FIG. 4). As a result, the actual collection item Idet can be automatically set corresponding to the mounted ECU 20ins.

  In step S6, the data collection device 18 collects the driving parameter data D from the vehicle 12 for the collection item Idet set in step S5. The collection period of the data D is usually about one week. However, when diagnosing a cause of failure that is difficult to identify, it may take a long time.

  When the collection of the data D is completed, in steps S7 to S9, the data D collected by the data collection device 18 is read into the main body 16 of the external diagnostic machine 14, and the cause of the failure is analyzed. First, in step S7, the main body 16 of the external diagnostic machine 14 uses the ID of the ECU 20 (that is, the target ECU 20tar) corresponding to the VIN acquired at the time of collecting the data D (S3) and the outputable item Iout (hereinafter “collected scheduled item Iex”). ").

  In the present embodiment, the server 15 that can be connected in the Internet environment is provided with a vehicle DB 130 that stores ECU-equipped data for each vehicle 12 in association with VIN. After acquiring the VIN from the data collection device 18, the main body 16 notifies the server 15 of the VIN. The server 15 reads out the IDvin of the ECU 20 corresponding to the notified VIN (that is, the target ECU 20tar) and the outputtable item Iout from the vehicle DB 130 and notifies the main body 16 (in the following description, the target ECU 20tar corresponding to the VIN) Is also referred to as IDvin.).

  In step S8, the main body 16 acquires the IDins (S4) acquired by the data collection device 18 from the vehicle 12 and the collection item Idet (S5) based on the IDins and the IDvin acquired from the server 15 and the output possible item Iout (S7). Compare (see FIG. 4).

  In step S9, the main body 16 outputs the comparison result in step S8. When the collection item Idet actually collected from the vehicle 12 is insufficient with respect to the output possible item Iout corresponding to the mounted ECU 20ins confirmed by the VIN of the vehicle 12, there is a communication abnormality with respect to the insufficient collection item Idet. It can be determined that a failure has occurred in the target ECU 20tar. Further, if the collection item Idet and the output possible item Iout are the same, there is no communication abnormality between the data collection device 18 and each target ECU 20tar. Therefore, the worker performs a diagnostic work based on the data D collected by the data collecting device 18 and then read into the diagnostic machine main body 16.

(3-2. Advance preparation)
(3-2-1. Overall flow of advance preparation)
FIG. 5 is a flowchart showing an example of a worker's work as a preliminary preparation for collecting the operation parameter data D and processing of the diagnostic machine main body 16 and the data collection device 18. The contents of FIG. 5 show steps S1 and S2 of FIG. 3 in more detail. In step S <b> 11 of FIG. 5, an operator (technician or the like) connects the connector 94 of the data collection device 18 to the connector 58 of the diagnostic machine main body 16.

  In step S <b> 12, the operator operates the input / output unit 50 (mouse, keyboard, etc.) of the diagnostic machine main body 16 to start diagnostic software used for collecting the operation parameter data D. Accordingly, the diagnostic machine main body 16 displays a display screen 200 (hereinafter also referred to as “input screen 200”) (for example, FIG. 6) related to the collection of the data D on the display unit 56. The order of steps S11 and S12 may be reversed.

  In step S13, the worker inputs data collection conditions by inputting to the display screen 200 (details will be described later).

  In step S <b> 14, the worker requests establishment of communication between the diagnostic machine main body 16 and the data collection device 18 by an input via the display screen 200. The main body 16 (data collection device communication function 62) that has received the request establishes communication with the data collection device 18. Note that the order of steps S13 and S14 may be reversed.

  In step S <b> 15, the worker requests the main body 16 to change the data collection condition of the data collection device 18 by an input via the display screen 200. The main body 16 (collection condition transmission function 66) that has received the request changes the data collection condition of the data collection device 18 to the one input in step S13. That is, the main body 16 transmits a new data collection condition to the data collection device 18, and the data collection device 18 (collection condition reading function 104) sets the received data collection condition as a new data collection condition.

  In step S <b> 16, the worker requests that communication between the diagnostic machine main body 16 and the data collection device 18 be disconnected by an input via the display screen 200. The main body 16 (data collection device communication function 62) having received the request disconnects communication with the data collection device 18.

  In step S <b> 17, the operator removes the connector 94 of the data collection device 18 from the connector 58 of the diagnostic machine main body 16.

(3-2-2. Data collection conditions)
(3-2-2-1. Overview of data collection conditions)
The data collection conditions input in step S13 in FIG. 5 include, for example, network types {CAN, LIN, FlexRay, K line, etc., and if there are multiple CANs (high speed CAN, low speed CAN, etc.) }, Including the bus usage rate for interrupting and resuming data collection and the type (or diagnosis target part) of the target ECU 20tar. In addition, the contents described in Patent Document 3 (for example, time for continuously acquiring data D (continuous data acquisition time), period for continuously acquiring data D (continuous data acquisition period), or data The total time for collecting D (total time for data collection)) may be specified.

  Furthermore, as described in relation to steps S1 and S2 in FIG. 3, the data collection conditions input in step S13 in FIG. 5 include the type of vehicle 12 (vehicle type Cv) related to the drive source and the diagnosis target region. The type of ECU 20 (ECU type Cecu) is included.

  The calculation unit 52 extracts the data item Idata corresponding to the input types Cv and Cecu from the data item DB 70 and sets it as a part of the data collection condition to be transmitted to the data collection device 18.

  The ECU type Cecu is a type of the ECU 20 that outputs data D corresponding to the cause of failure estimated based on the failure symptom heard from the user. As will be described in detail later with reference to FIG. 7, there are a plurality of ECUs 20 included in the ECU type Cecu, but there is only one ECU 20 included in the ECU type Cecu in a specific vehicle 12. Therefore, the data item Idata extracted based on the input type Cecu corresponds to all items of data D that can be acquired by the plurality of ECUs 20 included in the input type Cecu (see FIG. 4).

(3-2-2-2. Executable file)
When an operator inputs data collection conditions in the diagnostic machine main body 16, a program (execution file Fexe) executed by the data collection device 18 is generated. The execution file Fexe here takes the form of a file package generated for each type Cv of the vehicle 12 related to the drive source.

The file package includes the following files.
(A) Program file for acquiring VIN (VIN acquisition file Fvin), and (b) Program file for acquiring data D from the ECUs 20a to 20i of the networks 34a and 34b (data acquisition file Fdata)

  The VIN acquisition file Fvin can be set for each of the networks 34a and 34b. For example, the file Fvin used in the network 34a which is a high-speed CAN is set as “VIN.unt”. The extension “unt” is used as an extension of a file (program) for acquiring the VIN.

  The data acquisition file Fdata can be set for each part to be diagnosed or for each type Cecu of the ECU 20 to which the target ECU 20tar belongs. When a plurality of diagnosis target parts are set, a plurality of data acquisition files Fdata are set. For example, when the transmission is a diagnosis target part (in other words, when the transmission ECU is selected as the ECU type Cecu), the file Fdata is set as “MISSION.mam”. The extension “mam” is used as an extension of a file (program) for acquiring the data D. The extension for the file Fdata is changed for each of the networks 34a and 34b.

  By separating the VIN acquisition file Fvin and the data acquisition file Fdata, it is possible to exclude the ECU 20 (for example, the ECU 20a) storing the VIN from the target of the data acquisition file Fdata.

  The type of the execution file Fexe (file package) is set on a specific input screen. Specifically, the setting is made on an input screen (not shown) displayed when “model information / setting file management” is selected in a hardware setting selection unit 204 (FIG. 6) of the input screen 200 described later.

(3-2-2-3. Input of data collection conditions)
(3-2-23-1. Overview of Input Screen 200)
FIG. 6 is a diagram illustrating an example of the input screen 200 when inputting data collection conditions. FIG. 7 is a diagram illustrating an example of various types of information (such as identification information (ID) of the target ECU 20tar) according to the type of the diagnosis target region or the type (type Cecu) of the ECU 20 to which the target ECU 20tar belongs. In FIG. 7, a CNG vehicle means a compressed natural gas vehicle, and FFV means a flexible-fuel vehicle.

  When inputting the data collection conditions, first, the type Cv (gasoline vehicle / CNG vehicle / FFV, hybrid vehicle, etc.) of the vehicle 12 related to the drive source is specified (input). Then, an input screen 200 as shown in FIG. 6 is displayed by a user operation.

  As shown in FIG. 6, the input screen 200 includes menu selection buttons 202a to 202c, a hardware setting selection unit 204, a data collection condition input unit 206, a condition input button 208, a connection button 210, and a data read button. 212.

(3-2-2-3-2. Menu selection buttons 202a to 202c)
The menu selection buttons 202a to 202c are buttons for selecting a plurality of menus (“hardware setting”, “hardware management”, and “defect analysis”). In the present embodiment, when inputting the data collection condition of the data collection device 18, the button 202a (hardware setting) is selected. Further, when data analysis (S55 in FIG. 10) described later is performed, the button 202c (defect analysis) is selected.

(3-2-2-3-3. Hardware Setting Selection Unit 204)
A hardware setting selection unit 204 (hereinafter also referred to as a “selection unit 204”) is used to select hardware setting options such as input channel (CH) setting and output channel setting by a pointer (not shown). It is a part. The selection unit 204 may be scrollable in accordance with the display data size (the same applies to the data collection condition input unit 206 and the like).

(3-2-2-3-4. Data collection condition input unit 206)
The data collection condition input unit 206 (hereinafter also referred to as “input unit 206”) is a part that displays an input field according to the option selected by the selection unit 204. In the example of FIG. 6, the selection unit 204 shows a case where the high-speed CAN (that is, the network 34a) is selected as the output channel setting. In addition to or instead of this, the setting can be made for another network (for example, the network 34b which is a low-speed CAN).

  As shown in FIG. 6, the input unit 206 includes a message output setting field 220, a file name input field 222, a transmission condition display field 224, a transmission stop condition input field 226, a transmission resumption condition input field 228, an ECU. A setting file input field 230, a read button 232, a save button 234, an ECU selection button 236, ECU setting display fields 238a to 238e, and a reset button 240 are provided.

  The message output setting column 220 is a column for setting whether or not to display a guidance message on the display unit 86 of the data collection device 18. The file name input field 222 is a field for inputting the name of the execution file Fexe (file package). The transmission condition display column 224 is a column for displaying a condition for the data collection device 18 to start transmitting the data request signal Sreq (in other words, a condition for starting the collection of the data D).

  The transmission stop condition input field 226 is a field for displaying a condition (bus usage rate threshold) under which the data collection device 18 interrupts transmission of the data request signal Sreq when data D is being collected. The transmission resumption condition input column 228 is a column for displaying a condition (bus utilization threshold) at which the data collection device 18 resumes transmission of the data request signal Sreq when transmission of the data request signal Sreq is interrupted.

  The ECU setting file input field 230 is a field for text input of the data acquisition file Fdata. The read button 232 is a button for reading the file Fdata input in the input field 230. When the button 232 is pressed, the file Fdata input in the input field 230 is displayed in any of the available ECU setting display fields 238a to 238e. The save button 234 is a button for saving the selection content in the input unit 206.

  The ECU selection button 236 is a button for inputting a diagnosis target part (or ECU type Cecu). When the button 236 is pressed, options for the data acquisition file Fdata are displayed, and a specific data acquisition file Fdata can be selected from the options. In the present embodiment, the input or selection of the data acquisition file Fdata has a meaning as the input or selection of the ECU type Cecu.

  The ECU setting display fields 238a to 238e display the data acquisition file Fdata (that is, the ECU type Cecu or the diagnosis target part). The reset button 240 is a button for resetting the file Fdata displayed in the display fields 238a to 238e.

(3-2-2-3-5. Condition input button 208, connection button 210, and data reading button 212)
The condition input button 208 is a button for displaying a part (for example, the data collection condition input unit 206) for inputting the data collection condition. The connection button 210 is a button for establishing communication between the main body 16 and the data collection device 18 and causing the data collection device 18 to output the data collection conditions input by the main body 16. The data reading button 212 is a button for causing the main body 16 to read the data D collected by the data collecting device 18.

(3-2-2-4. Type of ECU 20tar Cecu)
As described above, the input screen 200 of FIG. 6 includes the ECU selection button 236 for inputting the ECU type Cecu and the ECU setting display fields 238a to 238e for displaying the type Cecu. When the processing capability of the data collection device 18 and each of the ECUs 20a to 20i is relatively high, it is conceivable to collect the data D from the data collection device 18 for all the ECUs 20 of the vehicle 12.

  However, if communication between the data collection device 18 and each ECU 20 is increased, the amount of communication in the networks 34a and 34b becomes enormous, and communication in the networks 34a and 34b may not be performed normally. Therefore, in the present embodiment, in order to obtain data D about a part (diagnosis target part) that may cause the trouble symptom that the customer claims about the vehicle 12, the number of identifiable target ECUs 20tar is set to the network 34a, Limit according to the type of 34b. For example, when the number of ECUs 20a to 20f included in the network 34a (high-speed CAN) is 15, the number of target ECUs 20tar that can be specified for the network 34a can be limited to any value of 3 to 10. The same applies to the network 34b (low speed CAN) and the like.

  For example, in the case of a gasoline car, a CNG car or an FFV, the diagnosis target part is, for example, an engine, a transmission, a shift lever, an electric power steering (EPS) mechanism, a reaction force pedal mechanism, an active control mount (ACM). ) Mechanism, automatic cruise control (ACC) mechanism, meters, electric parking and brake mechanism, acoustic vehicle alert system (AVAS), supplemental restraint system (SRS) and automatic seat belt tightening device All or part may be included. In addition, in the case of a hybrid vehicle or an electric vehicle, one or a plurality of travel motors and a battery may be included in addition to or instead of the diagnosis target portion such as a gasoline vehicle.

  In general, in the vehicle 12, one or a plurality of diagnosis target parts are often controlled by one ECU 20. For this reason, the diagnosis target part is specified by specifying the ECU type Cecu.

  In the present embodiment, the ECU type Cecu is specified by the file name of the data D. For example, when the engine ECU is selected as the ECU type Cecu, the file “Gasoline & CNG.mam” or “Diesel.mam” is selected (see FIG. 7).

  Even if the ECU type Cecu is the same, there may be a plurality of IDs of the target ECU 20tar depending on the vehicle type. For example, in FIG. 7, regarding the transmission ECU, “0E”, “1D”, and “1E” exist as IDs of the target ECU 20tar. 0E indicates that the engine ECU and the transmission ECU are arranged in the same case (in other words, the engine ECU and the transmission ECU are integrally configured). 1D indicates, for example, an automatic transmission (AT). 1E indicates that, for example, an engine ECU and a transmission ECU are provided separately.

  In this embodiment, when the ECU type Cecu is selected, all the output possible items Iout for each of the plurality of ECUs 20 corresponding to the type Cecu are stored in the data collection device 18 for each ID of the ECU 20. The output possible item Iout is an item of the operation parameter data D that can be output by the ECU 20. Hereinafter, the output possible item Iout selected and stored in the preliminary preparation stage is referred to as a collection item candidate Iop.

  Various information shown in FIG. 7 (in other words, a method for specifying and using the ECU type Cecu) will be described together with the description of the flowcharts of FIGS. 8 and 9.

(3-3. Work and processing when collecting operation parameter data D)
(3-3-1. Overall flow when collecting operation parameter data D)
FIG. 8 is a flowchart illustrating an example of the work of the worker and the processing of the data collection device 18 when the operation parameter data D is collected. The content of FIG. 8 shows steps S3 to S6 of FIG. 3 in more detail. The calculation unit 82 executes the processing of the data collection device 18 in FIG. 8 and FIGS. Further, when diagnosing a cause of failure that is difficult to identify, the data D is collected over a relatively long period (for example, 1 to 2 weeks).

  In step S <b> 21 of FIG. 8, an operator (technician or the like) connects the connector 94 of the data collection device 18 to the data link connector 38 of the vehicle 12. No special switch is provided in the power lines 37 and 92 from the battery 24 to the data collection device 18 (however, it is preferable to provide a fuse). For this reason, when the connectors 38 and 94 are connected, the power from the battery 24 of the vehicle 12 is supplied to the data collection device 18 and the data collection device 18 is activated (step S22). At this time, the electric power from the battery 24 is charged in the capacitor 88 of the data collection device 18, and the data collection device 18 can continue to operate for a certain period of time even when the connector 94 is removed.

  The data collection device 18 may be provided with a recording enable / disable switch (not shown) so that the operator can select whether the data collection device 18 can record data by operating the switch. In addition, a power supply capable of operating the data collection device 18 for a long time may be provided in the data collection device 18 itself.

  The data collection device 18 performs initialization when power is supplied for the first time after the connector 94 is connected. The initialization here newly creates a save file Fsave of the data D. That is, when the connector 94 is detached and then reconnected, a new saved file Fsave is created. Thereby, the operator can switch the vehicle 12 to be diagnosed only by inserting and removing the connector 94. In this case, each save file Fsave is newly created.

  In step S23 of FIG. 8, the data collection device 18 determines whether or not the IGSW 40 is turned on. This determination is performed by receiving a notification from the first ECU 20a via the network 34a. If the IGSW 40 is not on (S23: NO), step S23 is repeated.

  When the IGSW 40 is turned on (S23: YES), the other ECUs 20b to 20i are activated together with the first ECU 20a. At this time, the data collection device 18 establishes communication with each of the ECUs 20a to 20i. Note that any one of the ECUs 20a to 20i (for example, the one corresponding to the immobilizer ECU) is activated when the IGSW 40 comes to the position of the accessory (ACC).

  In step S24, the data collection device 18 (request signal specifying function 108) executes an initial setting process. In the initial setting process, an item of data D (outputtable item Iout) that can be output in each target ECU 20tar is confirmed, and an item of data D that the data collection device 18 acquires from the target ECU 20tar (hereinafter referred to as “collection item Idet”). As the output possible item Iout. The initial setting process is executed when the data collection device 18 is initialized (S22). For this reason, a new initial setting process is not executed until the data collection device 18 is removed from the vehicle 12. Details of the initial setting process will be described later with reference to FIG.

  In subsequent step S25, the data collection device 18 causes the display unit 86 to display a request for the operator to turn off the IGSW 40. If the IGSW 40 remains on (S26: NO), the process returns to step S25 to continue the request. When the IGSW 40 is turned off (S26: YES), in step S27, the data collection device 18 causes the display unit 86 to display a request for the operator to turn on (re-turn on) the IGSW 40. If the IGSW 40 remains off (S28: NO), the process returns to step S27 to continue the request. When the IGSW 40 is turned on (S28: YES), in step S29, the data collection device 18 executes a data collection process.

  In the data collection process, a data request signal Sreq is transmitted from the data collection device 18 to each target ECU 20tar. The data request signal Sreq is specified by the request signal specifying function 108 and transmitted by the data request function 110. The target ECU 20tar that has received the data request signal Sreq returns the data D requested by the data request signal Sreq to the data collection device 18. The data reception / storage function 112 of the data collection device 18 receives the data D from each target ECU 20tar and stores it in the storage unit 84 (data storage unit). For example, the details of the data collection process described in Patent Document 3 can be used.

  In step S30, the data collection device 18 determines whether or not the IGSW 40 is turned off. If the IGSW 40 remains on (S30: NO), the process returns to step S29, and the data collection device 18 continues the data collection process. When the IGSW 40 is turned off (S30: YES), the vehicle 12 is stopped, but the connectors 38 and 94 remain connected. For this reason, the power supply from the battery 24 is continued to the data collection device 18. In this case, the process proceeds to step S31.

  In step S31, the data collection device 18 determines whether or not the connector 94 has been removed. This determination is performed, for example, by monitoring the signal output on the communication line 90 connected to the communication buses 36a and 36b.

  When the connector 94 is not removed (S31: NO), in step S32, the data collection device 18 determines whether or not the IGSW 40 is turned on. If the IGSW 40 remains off (S32: NO), the process returns to step S31. When the IGSW 40 is turned on (S32: YES), the process returns to step S29, and the data collection device 18 resumes the data collection process. Therefore, if the IGSW 40 is on while the connectors 38 and 94 are continuously connected (S32: YES), the data collection device 18 collects the data D (S29).

  At this time, the collection item Idet set in the initial setting process (S24) is used. If the IGSW 40 is off while the connectors 38 and 94 are continuously connected (S30: YES), the data collection device 18 stops collecting the data D and enters a standby state (or sleep state).

  Returning to step S31, when the connector 94 is removed (S31: YES), the power supply from the battery 24 to the data collection device 18 is terminated. In this case, in step S33, the data collection device 18 executes an end process. In the end processing, processing such as storing the data D acquired so far in the storage file Fsave is performed. Electric power for executing the termination process is supplied from the capacitor 88. Further, the storage of the data D in the storage file Fsave can be performed during the data collection process (S29).

  Even when the connector 94 is removed without turning off the IGSW 40, the data collection device 18 may similarly execute the termination process (S33).

(3-3-2. Initial setting process)
FIG. 9 is a flowchart of the initial setting process in this embodiment (details of S24 in FIG. 8). In step S41, the data collection device 18 acquires VIN from a specific ECU 20 (for example, ECU 20a) via the network 34. At this time, the data collection device 18 (arithmetic unit 82) executes the VIN acquisition file Fvin (for example, “VIN.unt”).

  Specifically, the data collection device 18 outputs a VIN output request command Sreqvin to the network 34 (for example, the network 34a) designated by the file Fvin. Each of the ECUs 20a to 20f that has received the command Sreqvin checks whether or not it stores VIN. Then, the ECU 20 storing the VIN transmits the VIN to the data collection device 18. In the present embodiment, there is only one ECU 20 that stores VIN. When the ECU 20 storing the VIN can be specified in advance, the data collection device 18 may request the VIN from the ECU 20.

  The acquired VIN is used for data analysis (S55 in FIG. 10). That is, the data collection device 18 stores the acquired VIN in the storage unit 84 and outputs it to the diagnostic machine body 16 later.

  In step S42, the data collection device 18 specifies the ID (that is, IDins) of the target ECU 20tar. As described above, in the present embodiment, even if the ECU type Cecu is specified, the ECU 20 included in the type Cecu may differ depending on the vehicle 12. For example, in the example of FIG. 7, regarding the transmission ECU, there are three ID candidates “0E”, “1D”, and “1E”. Therefore, the data collection device 18 specifies IDins of the transmission ECU actually mounted on the vehicle 12 using these three IDs.

  That is, the data collection device 18 transmits one response command including three IDs as destinations. Then, the data collection device 18 sets the ID of the target ECU 20tar that has responded within a predetermined time as IDins. The network 34b can be returned from the gateway 22 even when the ECU 20 is designated as the destination. When no reply is received from the target ECU 20tar of any ID within the predetermined time, the data collection device 18 stores in the storage unit 84 that no reply has been received for any candidate ID.

  As can be seen from FIG. 7, in this embodiment, the candidate ID of the target ECU 20tar is common regardless of the type of the vehicle 12 (gasoline vehicle or the like). In other words, the ID candidates for the target ECU 20tar are classified for each diagnosis target part (or for each ECU type Cecu). When there are a plurality of diagnosis target parts, the ID of the target ECU 20tar is specified for each diagnosis target part.

  In step S43, the data collection device 18 specifies the output possible item Iout of each target ECU 20tar corresponding to IDins specified in step S42. As described above, when the ECU type Cecu is selected in advance preparation (FIG. 3), all the output possible items Iout of the plurality of ECUs 20 corresponding to the type Cecu are all collected item candidates Iop for each ID of the ECU 20. It is stored in the data collection device 18. For this reason, it becomes possible to identify the output possible item Iout of the target ECU 20tar based on the identified IDins. The output possible item Iout is an item of the operation parameter data D that can be output by the target ECU 20tar.

  In step S44, the data collection device 18 sets a collection item Idet by excluding items other than the output possible item Iout specified in step S43 from the collection item candidates Iop stored in the storage unit 84. The collection item Idet is an item of data D that is actually collected by the data collection device 18 in the data collection process (S29 in FIG. 8). Therefore, an item that is included in the collection item candidate Iop but is not included in the outputable item Iout is not set in the collection item Idet.

  In step S44, the output possible item Iout is set as it is as the collection item Idet. Further, when focusing on the setting of the collection item Idet, the output possible item Iout can be used as it is as the collection item Idet.

(3-4. Work and processing after collection of operation parameter data D)
(3-4-1. Overall flow)
FIG. 10 is a flowchart showing an example of the work of the worker after the collection of the operation parameter data D and the processing of the data collection device 18. In step S <b> 51, an operator (technician or the like) connects the connector 94 of the data collection device 18 to the connector 58 of the diagnostic machine main body 16.

  In step S <b> 52, the operator operates the input / output unit 50 (mouse, keyboard, etc.) of the diagnostic machine main body 16 to start diagnostic software used for acquiring the operation parameter data D. Accordingly, the diagnostic machine main body 16 displays a display screen 300 (hereinafter also referred to as “diagnosis screen 300” or “screen 300”) (FIG. 11) related to acquisition of data D on the display unit 56. The order of steps S51 and S52 may be reversed.

  In step S <b> 53, the worker requests establishment of communication between the diagnostic machine body 16 and the data collection device 18 by an input via the display screen 300. The main body 16 (data collection device communication function 62) that has received the request establishes communication with the data collection device 18.

  In step S <b> 54, the operator requests the diagnostic machine main body 16 to acquire the collected operation parameter data D from the data collection device 18 by input via the display screen 300. This request is made, for example, via the data reading button 212 (FIG. 6). The main body 16 (collected data reading function 68) that has received the request requests the data collecting device 18 to transmit the collected operation parameter data D. In response to the request, the data collection device 18 (collected data transmission function 106) transmits the collected operation parameter data D (including VIN and the collection item Idet) to the main body 16. The main body 16 (collected data read function 68) that has received the data D from the data collection device 18 stores the data D in the storage unit 54.

  In step S55, the operator operates the display screen 300 of the main body 16 to analyze the operation parameter data D and identify the cause of the failure. The analysis here includes determination of the ECU 20 (abnormal ECU 20mal) in which an abnormality has occurred. The processing on the external diagnostic machine 14 side in the determination of the abnormality ECU 20mal is mainly performed by the data analysis function 64 of the diagnostic machine body 16.

  In the data analysis in step S55, it is also possible to perform analysis using VIN. Specifically, the ECU type Cecu is included in the data collection conditions set in preparation (S13, S15 in FIG. 5). Further, at the time of data collection, one response command including a plurality of IDs as destinations is transmitted to identify the ID of the target ECU 20tar (S42 in FIG. 9, FIG. 7). At this time, if there is no reply from the target ECU 20tar of any ID within the predetermined time, the data collection device 18 stores in the storage unit 84 that no reply has been received for any ID candidate.

  Thus, when there is no reply for any candidate ID, it cannot be confirmed whether the vehicle 12 is not actually equipped with the type of ECU 20 or whether there is no reply due to a failure of the ECU 20.

  Thus, in the present embodiment, information of the ECU 20 mounted on the diagnosis target vehicle 12 (hereinafter referred to as “diagnosis target vehicle 12tar”) is specified via the VIN. Then, whether the type of ECU 20 is actually mounted on the diagnosis target vehicle 12tar or whether the type of ECU 20 is mounted on the diagnosis target vehicle 12tar but there is no response due to a failure is confirmed. Can do.

  In order to perform the confirmation as described above, the worker specifies the type of the ECU 20 mounted on the diagnosis target vehicle 12tar based on the VIN. Specifically, the operator requests the server 15 to request information on the ECU 20 (hereinafter referred to as “mounted ECU 20 ins”) mounted on the diagnosis target vehicle 12 tar (hereinafter “mounted”) from the server 15 via a display screen (not shown). ECU information request Riecu "or" Request Riecu "). The diagnostic machine body 16 to which the request Riecu is input outputs the request Riecu and the VIN of the diagnosis target vehicle 12tar to the server 15. The server 15 that has received the requests Riecu and VIN outputs information on the mounted ECU 20ins corresponding to the received VIN.

  The diagnostic machine body 16 that has received the information on the mounted ECU 20ins highlights the output possible item Iout of the ECU 20 for which the data D is not collected even though it is included in the mounted ECU 20ins.

(3-4-2. Display at diagnosis)
FIG. 11 shows an example of the display screen 300 of the main body 16 that displays the comparison result between the collection item Idet and the outputtable item Iout. The screen 300 includes a detail display unit 302.

  The detail display unit 302 is a part for displaying details of the data D acquired from the data collection device 18. The detail display unit 302 includes a transmission period column 310, a category column 312, a data item column 314, an explanation column 316, a unit column 318, and a check column 320.

  The data item Idata displayed on the detail display unit 302 is both the collection item candidate Iop and the collection item Idet. Both the collection item candidate Iop and the collection item Idet can be acquired from the data collection device 18. Alternatively, the collection item candidate Iop can be specified based on the VIN acquired from the data collection device 18 and the file name of the data acquisition file Fdata using the data item DB 70 or the vehicle DB 130.

  The transmission cycle column 310 is a column that displays the transmission cycle of the data request signal Sreq by the data collection device 18. The category column 312 is a column that displays the category of the vehicle 12. In FIG. 11, the type (vehicle type Cv) of the vehicle 12 related to the drive source is used as the category.

  The data item column 314 is a column for displaying the data item Idata. The explanation column 316 is a column for displaying the explanation of the data item Idata displayed in the data item column 314. The unit column 318 is a column that displays the unit of the data D.

  The check column 320 is a column in which the collection item Idet (the item of the data D actually acquired by the data collection device 18) exists among the outputable items Iout, and the item in which the collection item Idet does not exist is not checked. . This check can be performed using the output from the data collection device 18 (comparison result of the collection item Idet and the outputable item Iout). Alternatively, the calculation unit 52 of the main body 16 can check by comparing the collected item Idet and the output possible item Iout.

  As described above, in step S44 of FIG. 9, the output possible item Iout is set as it is as the collection item Idet. There is a possibility that the output possible item Iout transmitted from the target ECU 20tar or the gateway 22 is missing. In such a case, the missing item may be the cause of the malfunction symptom.

  Therefore, the operator can identify the missing output possible item Iout by confirming the display content of the check column 320 and use it for failure diagnosis. That is, the operator determines that an abnormality has occurred in the data item Idata that is not checked in the check column 320 even though it is displayed as the outputtable item Iout (in other words, the data It is possible to determine that an abnormality has occurred in the ECU 20 that should output the data D of the item Idata). Hereinafter, the ECU 20 in which such an abnormality has occurred is also referred to as an abnormality ECU 20mal.

  The main body 16 may highlight the missing items as described above. As the highlighting here, for example, a change in color, an increase in luminance, or blinking of characters or background can be used. In addition to or instead of this, the missing item and the cause of failure assumed in relation to this are combined and stored in the storage unit 54 as a database, and the cause of failure corresponding to the missing item is displayed or externally output. May be.

(3-4-3. Determination of Abnormal ECU 20mal)
FIG. 12 is a flowchart of the worker's work accompanying the determination of the abnormality ECU 20mal and the processing of the diagnostic machine main body 16. The processing of the diagnostic machine main body 16 in FIG. In step S61, when the operator instructs the start of diagnosis, the main body 16 specifies the ID (IDvin) of the ECU 20 (that is, the target ECU 20tar) corresponding to the VIN acquired when the data D is collected and the output possible item Iout. .

  In step S62, the diagnostic machine main body 16 acquires the IDins (S4) acquired by the data collection device 18 from the vehicle 12, the collection item Idet (S5) based on the IDins, the IDvin corresponding to VIN, and the output possible item Iout (S7). Are compared (see FIG. 4).

  When all the IDins and the collection items Idet match all the IDvins and the outputable items Iout (S63: YES), in step S64, the main body 16 determines that the target ECU 20tar is normal. Display.

  When a part of IDins and a part of IDvin do not match, or a part of the collection item Idet and a part of the outputable item Iout do not match (S63: NO), in step S65, the main body 16 determines that the target ECU 20tar Judged to be abnormal. In this case, the main body 16 highlights on the screen 300 the IDvin that does not have a pair of IDins or the outputable item Iout that does not have a pair of collection items Idet.

[4. Effects of this embodiment]
As described above, according to the present embodiment, since the data collection device 18 performs at least a part of the setting of the collection item Idet (S5 in FIG. 3 and S44 in FIG. 9), the worker accompanying the setting of the collection item Idet It becomes possible to reduce the man-hours. Further, the mounted ECU 20ins notified from the vehicle 12 is identified as the target ECU 20tar (S4 in FIG. 3 and S42 in FIG. 9), and the output possible item Iout corresponding to the target ECU 20tar is set as the collection item Idet (FIG. 3). S5, S44 of FIG. 9). For this reason, it becomes possible to prevent an operator's artificial mistake accompanying the setting of the collection item Idet.

  In the present embodiment, the request signal specifying function 108 (collection item setting unit) of the data collection device 18 performs an initial ON operation of the IGSW 40 (start switch) in a state where the data collection device 18 is connected to the vehicle 12 (S23 in FIG. 8). : YES), the vehicle 12 is inquired about the presence or absence of the mounted ECU 20ins for each ECU type Cecu (type of the target ECU 20tar) set in the diagnostic machine main body 16 (type setting unit) (S24 in FIG. 8, FIG. 9). S42) The collection item Idet is set (S5 in FIG. 3, S44 in FIG. 9). Furthermore, the data request function 110 and the data reception / storage function 112 (data collection management unit) of the data collection device 18 are on condition that an IGSW 40 off operation and a subsequent re-on operation have been performed (S26 in FIG. 8). YES → S28: YES), transmission of the data request signal Sreq and storage of the data D are started.

  According to the above, at least a part of the setting of the collection item Idet and the collection start of the operation parameter data D can be performed by connecting the data collection device 18 to the in-vehicle networks 34a and 34b and operating the IGSW 40 (start switch). Yes (FIGS. 8 and 9). Therefore, the operator can perform at least a part of the setting of the collection item Idet and the collection start of the data D with a simple operation.

  In this embodiment, when the connection of the data collection device 18 to the in-vehicle networks 34a and 34b is once released (S31: YES in FIG. 8), the connection of the IGSW 40 to the new in-vehicle networks 34a and 34b (S21). A new target ECU 20tar is set in response to the first ON operation (S23: YES) (S24 in FIG. 8, S42 in FIG. 9). Following this, the request signal specifying function 108 (collection item setting unit) sets a new collection item Idet (S24 in FIG. 8, S44 in FIG. 9).

  Thus, the diagnosis target vehicle 12tar can be easily changed by removing the data collection device 18 from a certain vehicle 12 (first vehicle) and replacing it with another vehicle 12 (second vehicle).

  In the present embodiment, the connection between the data collection device 18 and the in-vehicle networks 34a and 34b is made through the connection between the connector 94 of the data collection device 18 and the data link connector 38 of the vehicle 12 (FIG. 1). Further, the data collection device 18 is activated by power supplied from the battery 24 (vehicle power source) via the connector 94 and the data link connector 38 (S22 in FIG. 8).

  Thereby, the start timing of the data collection device 18 can be set at the time of connection to the data link connector 38. Therefore, the data collection device 18 can be restarted with the attachment / detachment of the connector 94 to / from the data link connector 38 for changing the diagnosis target vehicle 12tar, and the data collection device 18 is changed even after the change of the diagnosis target vehicle 12tar. It can be easily operated.

  In the present embodiment, the diagnostic machine main body 16 (type setting unit) sets the ECU type Cecu classified according to the type of the vehicle 12 related to the drive source in accordance with the operator's input (S1 in FIG. 3, FIG. 7). reference). It can be said that the type of the vehicle 12 related to the drive source here is obtained by integrating a plurality of vehicle types and classifying the ECU 20 mounted on each vehicle type as a type for each function.

  The operator can easily determine the type Cv (gasoline vehicle, diesel vehicle, hybrid vehicle, etc.) of the vehicle 12 related to the drive source. On the other hand, the items of the driving parameter data D are greatly different depending on the type Cv of the vehicle 12. In the present embodiment, the operator (user) specifies the vehicle type Cv, and the data collection device 18 uses the collection item candidate Iop included in the range corresponding to the type Cv specified by the operator (S1 in FIG. 3). , S2, S4, S5). As a result, it is possible to reduce the calculation load in the data collection device 18 and the number of man-hours associated with the operator while reducing the input burden on the operator or preventing an input error.

B. Modifications It should be noted that the present invention is not limited to the above-described embodiment, and it is needless to say that various configurations can be adopted based on the description of the present specification. For example, the following configuration can be adopted.

[1. Applicable to]
In the above embodiment, the external diagnostic device 14 is used for the vehicle 12, but is not limited to this, for example, a stand-alone device including a local network to which a plurality of ECUs 20 are connected (for example, a moving object such as a ship or an aircraft, It can also be used in various manufacturing apparatuses.

[2. Vehicle 12]
In the above embodiment, CAN is used as the in-vehicle networks 34a and 34b. However, the present invention is not limited to this, and a network such as a LIN, FlexRay, K line, or the like may be used.

  The above embodiment has been described on the assumption that the IGSW 40 is a rotary switch. However, the IGSW 40 may be a switch provided in the diagnosis target vehicle 12tar for actual data collection, such as a push type. The IGSW 40 means an ignition switch in a narrow sense and is used in the vehicle 12 having an engine. However, here, the IGSW 40 means an activation switch of the vehicle 12, and the same method is used even when the vehicle 12 is an EV. It is available at.

[3. External diagnostic machine 14]
(3-1. Diagnostic purpose)
In the above embodiment, the external diagnostic device 14 performs a failure diagnosis of the vehicle 12, but from the viewpoint of collecting the operating parameter data D by the data collection device 18, it performs other vehicle diagnosis. Also good. For example, the external diagnostic device 14 performs a health diagnosis for confirming the deterioration state or operation state of each in-vehicle device, and a driving skill diagnosis for diagnosing a driver's driving skill (for example, accelerator operation, brake operation). Also good. For this reason, the operation parameter data D is not limited to data intended for failure diagnosis, but may be data used for other diagnosis.

(3-2. Diagnostic machine body 16)
In the said embodiment, although the diagnostic machine main body 16 was comprised from the commercially available notebook type personal computer, the tablet type computer, or the smart phone, for example, it was set as the single thing, It does not restrict to this. For example, the main body 16 may be composed of a personal computer as the main body and a slave unit (repeater) as an interface with the data collection device 18.

  In the above embodiment, the diagnostic software used in the diagnostic machine main body 16 is recorded in the storage unit 54 in advance, but is not limited thereto. For example, the diagnostic software may be downloaded from the outside (for example, an external server capable of communicating via a public network) or executed by a so-called ASP (Application Service Provider) type that does not involve downloading.

(3-3. Data Collection Device 18)
(3-3-1. Configuration)
In the above embodiment, the data collection device 18 is configured separately from the diagnostic machine main body 16 (FIG. 1), but the function of the data collection device 18 may be provided in the main body 16.

  In the above embodiment, the communication between the diagnostic machine main body 16 and the data collection device 18 and the communication between the vehicle 12 and the data collection device 18 are both wired communication (FIG. 1), but partly wireless. It is also possible to communicate via communication. For example, the diagnostic machine body 16 and the data collection device 18 can be wirelessly communicated. Alternatively, the vehicle 12 may be provided with a wireless communication device (not shown) connected to the in-vehicle networks 34a and 34b. In this case, it is possible to perform wireless communication between the data collection device 18 and the wireless communication device, and the data collection device 18 can communicate with each ECU 20 via the wireless communication device.

(3-3-2. Startup conditions)
In the above embodiment, when the connector 94 is connected to the data link connector 38, the data collection device 18 is automatically activated (S22 in FIG. 8). However, for example, from the viewpoint of starting the data collection device 18, the present invention is not limited to this. For example, a start switch (not shown) may be provided in the data collection device 18, and the data collection device 18 may be turned on when an operator operates the start switch. In addition, a power supply capable of operating the data collection device 18 for a long time may be provided in the data collection device 18 itself.

(3-3-3. Data collection conditions)
In the above-described embodiment, the conditions for starting the collection of data D (S29 in FIG. 8) are on, off, and re-on of the IGSW 40 (S23, S26, S28). However, for example, from the viewpoint of confirming the output possible item Iout and setting the collection item Idet, the present invention is not limited to this. For example, the disclosure condition for collecting the data D may be that the position of the IGSW 40 is moved to the accessory (ACC) after the IGSW 40 is turned on and off. That is, some ECUs 20 are activated when the position of the IGSW 40 is turned on, and some are activated when the position is ACC. Therefore, the start of data collection itself may be started when the position of the IGSW 40 changes from OFF to ACC.

12 ... Vehicle 16 ... Diagnostic machine body (Type setting section)
18 ... Data collection device 20a-20i ... ECU
20 ins ... mounted ECU 20 tar ... target ECU
24 ... Low voltage battery (on-vehicle power source) 34a, 34b ... In-vehicle network 38 ... Data link connector 40 ... IGSW (start switch)
84 ... Storage unit (data storage unit) 94 ... Connector 108 ... Request signal specifying function (collection item setting unit)
110 ... Data request function (part of the data collection manager)
112 ... Data reception / storage function (part of data collection management unit)
120: Data item DB (data item storage unit)
Cv ... Vehicle type Cecu ... ECU type D ... Operating parameter data Idet ... Collecting item Iop ... Collecting item candidate Iout ... Output possible item Sreq ... Data request signal

Claims (6)

A data request signal for requesting operating parameter data indicating an operating state of each part of the vehicle in a state in which it is detachably connected from the outside to an in-vehicle network having a plurality of electronic control units (hereinafter referred to as “ECU”). Vehicle diagnosis that is transmitted to a target electronic control device (hereinafter referred to as “target ECU”) that is at least one of the ECUs, receives the driving parameter data corresponding to the data request signal, and stores it in a data storage unit Data collection device for
The data collection device includes:
A type setting unit for setting the type of the target ECU based on an input from an operator ;
A data item storage unit that stores items of the operation parameter data that can be output by each of the plurality of ECUs in association with identification information of the plurality of ECUs;
Query the identity of the mounted ECU on the vehicle for each type of the target ECU set by the type setting unit identifies the mounted ECU that has received the identification information as the target ECU, it is identified as the target ECU and collecting item setting unit that sets as a collection item is read from the data item storage section on the basis of the items of the mounting ECU said operating parameter data that can be output, the identification information of the mounted ECU,
Data for transmitting the data request signal for requesting the operation parameter data corresponding to the collection item to the target ECU, receiving the operation parameter data corresponding to the data request signal, and storing the data in the data storage unit A data collection device comprising: a collection management unit. A data request signal for requesting operating parameter data indicating an operating state of each part of the vehicle in a state in which it is detachably connected from the outside to an in-vehicle network having a plurality of electronic control units (hereinafter referred to as “ECU”). Vehicle diagnosis that is transmitted to a target electronic control device (hereinafter referred to as “target ECU”) that is at least one of the ECUs, receives the driving parameter data corresponding to the data request signal, and stores it in a data storage unit Data collection device for
The data collection device includes:
A type setting unit for setting the type of the target ECU;
A data item storage unit that stores items of the operation parameter data that can be output by each of the plurality of ECUs in association with identification information of the plurality of ECUs;
For each type of the target ECU set by the type setting unit, the vehicle is inquired about the presence or absence of the mounted ECU, the mounted ECU is identified as the target ECU, and the mounted ECU identified as the target ECU can output the A collection item setting unit that reads the operation parameter data items from the data item storage unit based on the identification information of the mounted ECU and sets the items as collection items;
Data for transmitting the data request signal for requesting the operation parameter data corresponding to the collection item to the target ECU, receiving the operation parameter data corresponding to the data request signal, and storing the data in the data storage unit Collection management department
With
The collection item setting unit is provided with the presence or absence of the on-board ECU for each type of the target ECU set by the type setting unit in response to an initial ON operation of a start switch in a state where the data collection device is connected to the vehicle. To the vehicle to set the collection item,
Subsequently, the data collection management unit starts transmission of the data request signal and storage of the operation parameter data on condition that the start switch is turned off and then turned on again. A data collection device characterized by. The data collection device according to claim 2,
When the connection of the data collection device to the in-vehicle network is once released, the target ECU of the target ECU set by the type setting unit in response to the first-on operation of the start switch after connecting to the new in-vehicle network. A data collection device characterized in that, for each type, the new in-vehicle network is inquired about the presence or absence of the mounted ECU, and a new collection item is set. In the data collection device according to any one of claims 1 to 3,
The connection between the data collection device and the in-vehicle network is performed via a data link connector of the vehicle,
The data collection device is activated by power supplied from an in-vehicle power source via the data link connector. In the data collection device according to any one of claims 1 to 4,
The data collection device characterized in that the type setting unit integrates a plurality of vehicle types and classifies ECUs mounted on the vehicle types according to types for each function. A data request signal for requesting operating parameter data indicating an operating state of each part of the vehicle in a state in which it is detachably connected from the outside to an in-vehicle network having a plurality of electronic control units (hereinafter referred to as “ECU”). A data collecting device that transmits to the target electronic control device (hereinafter referred to as “target ECU”) that is at least one of the ECUs, receives the operating parameter data corresponding to the data request signal, and stores it in the storage unit A data collection method for vehicle diagnosis using
The data collection device includes:
A type setting process for setting the type of the target ECU based on an input from an operator ;
A storage process for storing the operation parameter data items that can be output by each of the plurality of ECUs in the storage unit in association with identification information of the plurality of ECUs,
Query the identity of the mounted ECU on the vehicle for each type of the target ECU set by the type setting processing to identify the mounted ECU that has received the identification information as the target ECU, it is identified as the target ECU a collection item setting process of setting a collection item is read from the storage unit based on the mounting ECU items of the operational parameter data that can be output, the identification information of the mounted ECU,
Data collection for transmitting the data request signal requesting the operation parameter data corresponding to the collection item to the target ECU, receiving the operation parameter data corresponding to the data request signal, and storing the data in the storage unit A data collection method comprising: processing.

Images