Diagnostic device

Abstract

To provide a diagnostic device capable of eliminating time and labor of an operator.SOLUTION: A master ECU is mounted on a vehicle together with an electrically connected slave ECU, and is configured to be capable of acquiring control data correlated to a vehicle failure. In a step S11, a microcomputer of the master ECU determines whether or not the slave ECU has been exchanged depending on whether or not to receive different connection codes. In steps S12 and S13, when having determined that the slave ECU has been exchanged, the microcomputer stores an ID of the exchanged slave ECU and control data acquired at least before it has been determined that it has been exchanged.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to diagnostic devices. [Background technology]

[0002] Patent Document 1 discloses an abnormality diagnosis system. The abnormality diagnosis system includes an image processing device having a storage unit that stores information related to control as log data, and a machine learning means that determines the cause of a malfunction in the image processing device from the log data based on machine learning. The abnormality diagnosis system further includes a setting means that inputs work information on the operation performed to address the malfunction. The machine learning means then determines the cause of the malfunction from the log data and the work information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-92715 Summary of the Invention [Problem to be solved by the invention]

[0004] In the above-mentioned abnormality diagnosis system, the serviceman inputs the work information, which requires the serviceman to take the trouble of inputting the information.

[0005] One disclosed object is to provide a diagnostic device that can reduce the labor of an operator. [Means for solving the problem]

[0006] The diagnostic device disclosed herein comprises: A diagnostic device that is mounted on a vehicle together with an electrically connected component and is capable of acquiring diagnostic information correlated with a fault in the vehicle, A determination unit (S11, S11a) that determines whether or not a part has been replaced; The system is provided with a memory unit (S12, S13, S12a, S13a, S15a, S16a) that stores, when it is determined that a replacement has been performed, part information of the replaced part and at least diagnostic information obtained before it is determined that the replacement has been performed.

[0007] This allows the diagnostic device to automatically store the diagnostic information before the part is replaced. Therefore, the diagnostic device can store the diagnostic information without the intervention of an operator. Therefore, the diagnostic device can save the operator time and effort.

[0008] The aspects disclosed in this specification adopt different technical means to achieve their respective objectives. The claims and the parenthetical symbols described in this section are illustrative of the corresponding relationship with the embodiments described below, and are not intended to limit the technical scope. The objectives, features, and effects disclosed in this specification will become clearer by referring to the following detailed description and the attached drawings. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a schematic configuration of an in-vehicle system; [Diagram 2] 10 is a flowchart showing a process of requesting and distributing a connection code by a master ECU. [Diagram 3] 13 is a flowchart showing a transmission process of a master ECU. [Figure 4] 13 is an image showing an example of control data. [Diagram 5] 13 is a flowchart showing a response process of a slave ECU. [Figure 6] 6 is a flowchart showing a process for storing a connection code of a slave ECU. [Figure 7] FIG. 1 is a conceptual diagram showing an example of a frame format. [Figure 8] 13 is a flowchart showing a process of requesting and distributing a connection code by a master ECU in the second embodiment; [Figure 9] 10 is a flowchart showing a process of determining whether or not to replace a wire harness according to a second embodiment. [Figure 10] FIG. 11 is a conceptual diagram illustrating an example of a frame format according to the second embodiment. [Figure 11] FIG. 11 is a conceptual diagram showing an example of a terminal portion according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, several embodiments for carrying out the present disclosure will be described with reference to the drawings. In each embodiment, the same reference numerals may be used to designate parts corresponding to matters described in the preceding embodiment, and duplicated descriptions may be omitted. In each embodiment, when only a part of the configuration is described, the other parts of the configuration may be applied by referring to the other embodiment described previously.

[0011] (First embodiment) 1 to 7, a master ECU 100 of the first embodiment and an in-vehicle system 1000 including the master ECU 100 will be described. In this embodiment, an example is adopted in which a diagnostic device is applied to the master ECU 100. Also, in this embodiment, an example is adopted in which a communication system is applied to the in-vehicle system 1000. However, the diagnostic device can also be applied to the slave ECUs 201 to 20n. ECU is an abbreviation for Electronic Control Unit.

[0012] In the drawings, the center is written as CNT, the master ECU as MECU, and the slave ECU as 1ECU or nECU. Also, in the drawings, the microcomputer is written as MCU, the memory device as MMD, and the communication device as DCM.

[0013] <In-vehicle systems, centers> 1, the in-vehicle system 1000 includes a master ECU 100, slave ECUs 201 and 20n, and a communication line 30. The in-vehicle system 1000 is mounted on a vehicle. The master ECU 100 and the slave ECUs 201 and 20n are configured to be able to communicate with each other via the communication line 30. The slave ECUs 201 and 20n correspond to electronic control devices.

[0014] The in-vehicle system 1000 is configured to be capable of wireless communication with a center 10 provided outside the vehicle. In this embodiment, a configuration in which the master ECU 100 communicates with the center 10 is employed as an example.

[0015] The center 10 includes a server including a microcomputer 11 and a memory device 12, a communication device 13, and an antenna 14. The center 10 is configured to be able to communicate with the in-vehicle system 1000. The center 10 is also configured to be able to communicate individually with each of the in-vehicle systems 1000 mounted in a plurality of vehicles. Thus, the center 10 can receive various types of information from the plurality of in-vehicle systems 1000. The various types of information include normal information and abnormal information as diagnostic information, and identification information unique to each ECU. These types of information will be explained in detail later.

[0016] The microcomputer 11 includes an arithmetic processing device such as a CPU, storage media such as RAM and ROM, and input / output devices. The memory device 12 is a hard disk or the like having a larger capacity than the storage media in the microcomputer 11. The communication device 13 is a device that performs wireless communication via an antenna 14. CPU is an abbreviation for Central Processing Unit. RAM is an abbreviation for Random Access Memory. ROM is an abbreviation for Read Only Memory.

[0017] The microcomputer 11 receives diagnostic information and the like from each in-vehicle system 1000 via the communication device 13 and the antenna 14. The received diagnostic information and the like are stored in the storage medium or memory device 12.

[0018] Furthermore, the microcomputer 11 performs machine learning of the normal information, abnormality information, and identification information. The microcomputer 11 generates a fault diagnosis model by performing machine learning. The fault diagnosis model is a machine learning model for identifying a faulty ECU from the abnormality information. The faulty ECU can be said to be a faulty part. The normal information, abnormality information, and identification information are input data for machine learning to generate the fault diagnosis model. Therefore, the center 10 (microcomputer 11) collects diagnosis information and identification information from multiple in-vehicle systems 1000 to generate the fault diagnosis model. The input data may be only the abnormality information and identification information.

[0019] The diagnostic information is information necessary for diagnosing vehicle faults. The abnormality information can also be said to be diagnostic information when the vehicle is abnormal. The normality information can also be said to be diagnostic information when the vehicle is normal. The identification information is information unique to each part. The identification information is, for example, an ID (identification) or information composed of multiple bits. The identification information corresponds to part information. Furthermore, parts include an ECU and a wire harness.

[0020] It can be said that the center 10 and the multiple in-vehicle systems 1000 are included in a communication network. However, the in-vehicle systems 1000 do not necessarily have a communication function with the center 10. In this case, the master ECU 100 may perform machine learning.

[0021] <Slave ECU> 1, the ECU 201 includes a first slave ECU 201, a microcomputer 211, a memory device 221, and a communication device 231. The ECU 20n includes an n-th slave ECU 20n, a microcomputer 21n, a memory device 22n, and a communication device 23n. The slave ECUs 201 and 20n are connected to various sensors and the like.

[0022] The microcomputers 211, 21n include an arithmetic processing unit such as a CPU, a storage medium such as a RAM, an input / output device, etc. The memory devices 221, 22n include a storage medium such as a ROM. The communication devices 231, 23n are devices that perform communication via the communication line 30. The memory devices 221, 22n may be built into the microcomputers 211, 21n.

[0023] In this way, the first slave ECU 201 and the n-th slave ECU 20n have similar hardware configurations. However, the first slave ECU 201 and the n-th slave ECU 20n differ from each other in the processing operation of the microcomputer 211 and the processing operation of the microcomputer 21n.

[0024] The microcomputers 211, 21n are configured such that when the ignition switch of the vehicle is turned on, the arithmetic processing device performs arithmetic processing at a predetermined execution timing. The arithmetic processing device performs arithmetic processing using, for example, a signal from a sensor. The arithmetic processing device generates control data by performing the arithmetic processing. Note that the arithmetic processing device may use the signal itself from the sensor as control data. In this case, the control data is also considered to be generated control data.

[0025] The generated control data is stored in the memory devices 221 and 22n. The slave ECUs 201 and 20n also store their own IDs, connection codes, and the like in the memory devices 221 and 22n.

[0026] The connection code is distributed from the master ECU 100 to the slave ECUs 201 and 20n. This is to hold a common connection code among the multiple ECUs 100, 201, and 20n in the in-vehicle system 1000. Therefore, the multiple ECUs 100, 201, and 20n have the same connection code. However, the replaced slave ECUs 201 and 20n will have a different connection code from the master ECU 100 until the connection code is distributed.

[0027] Therefore, the master ECU 100 can determine whether the slave ECUs 201, 20n have been replaced by comparing its own connection code with the connection codes of the slave ECUs 201, 20n. In other words, the connection code can be said to be information for determining whether the slave ECUs 201, 20n have been replaced. The connection code corresponds to replacement confirmation information.

[0028] Then, each arithmetic processing device transmits the generated control data via the communication device 231, 23n. When transmitting control data, the microcomputers 211, 21n transmit the control data together with an ID that identifies the microcomputer. Also, each arithmetic processing device transmits the control data, for example, at a predetermined transmission timing. Furthermore, each arithmetic processing device transmits a connection code, an ID, etc. in response to a request from the master ECU 100. The communication device 231, 23n transmits the control data, the ID, the connection code, etc. in a predetermined frame format.

[0029] For example, the microcomputer 211 generates and transmits control data s1 and s2. The control data s1 and s2 are stored in the memory device 221. On the other hand, the microcomputer 21n generates and transmits control data n1, n2, and nn. The control data n1, n2, and nn are stored in the memory device 22n.

[0030] 4, the microcomputer 211 transmits values ​​generated at each execution timing as the control data s1 and s2. Similarly, the microcomputer 21n transmits values ​​generated at each execution timing as the control data n1, n2, and nn. Note that the microcomputers 211 and 21n may generate and transmit control data other than the above control data.

[0031] When the slave ECUs 201, 20n and sensors connected to the slave ECUs 201, 20n fail, some of the control data may take values ​​that would not be possible under normal circumstances. In other words, the multiple control data include data (information) necessary for vehicle fault diagnosis. Vehicle faults can be diagnosed using such control data. Examples of the control data necessary for fault diagnosis include temperature, rotation speed, and rotation angle.

[0032] Here, the above control data s1, s2, n1, n2, nn are adopted as the control data required for diagnosis. Therefore, the control data s1, s2, n1, n2, nn correspond to diagnostic information. It can also be said that each value of the control data s1, s2, n1, n2, nn corresponds to diagnostic information. Unless otherwise specified below, control data refers to diagnostic information.

[0033] The control data can be said to be information related to a failure of the slave ECUs 201 and 20n. Furthermore, failures of the slave ECUs 201 and 20n and sensors connected to the slave ECUs 201 and 20n are also failures of the vehicle. Therefore, the control data can be said to be diagnostic information correlated with failures of the vehicle.

[0034] In this embodiment, two slave ECUs 201, 20n are used as communication partners of the master ECU 100. However, the present disclosure is not limited to this. The communication partners of the master ECU 100 may be one electronic control device or three or more electronic control devices.

[0035] <Master ECU> 1, the master ECU 100 includes a microcomputer 110, a memory device 120, a communication device 130, and an antenna 140. The microcomputer 110 includes an arithmetic processing device such as a CPU, a storage medium such as a RAM, an input / output device, and the like. The memory device 120 includes a storage medium such as a ROM. The communication device 130 includes a device that performs communication via a communication line 30, and a device that performs wireless communication via an antenna 140. The memory device 120 corresponds to a storage device.

[0036] The master ECU 100 is electrically connected to the slave ECUs 201 and 20n as components via a communication line 30. That is, the master ECU 100 is configured to be able to communicate with the slave ECUs 201 and 20n. The microcomputer 110 is also configured to be able to wirelessly communicate with the center 10 via an antenna 140.

[0037] In this embodiment, for convenience, a device that performs communication via the communication line 30 and a device that performs wireless communication via the antenna 140 are collectively referred to as the communication device 130. However, the master ECU 100 may include a device that performs communication via the communication line 30 and a device that performs wireless communication via the antenna 140 as separate devices. In addition, the memory device 120 may be built into the microcomputer 110.

[0038] The master ECU 100 has the same hardware configuration as the slave ECUs 201 and 20n. However, the microcomputer 110 has a different processing operation from the microcomputers 211 and 21n.

[0039] The microcomputer 110, like the microcomputers 211 and 21n, generates control data and transmits the generated control data to the communication line 30 via the communication device 130. It can also be said that the microcomputer 110 acquires the control data by itself. The generated control data is stored in the memory device 120.

[0040] 4, the microcomputer 110 transmits values ​​generated at each execution timing as the control data m1 and m2. The microcomputer 110 may transmit control data other than the above control data. Here, the control data m1 and m2 are diagnostic information generated by the microcomputer 110.

[0041] Furthermore, the microcomputer 110 can acquire the control data, ID, connection code, and the like transmitted from the slave ECUs 201, 20n by the communication device 130. That is, when the control data, and the like are transmitted from the slave ECUs 201, 20n to the communication line 30, the microcomputer 110 receives the control data, and the like. The received control data, and the like are stored in the memory device 120. Furthermore, the microcomputer 110 transmits the control data, and the like stored in the memory device 120 to the center 10 via the antenna 140.

[0042] 4, the master ECU 100 stores the control data generated by itself and the control data generated by the slave ECUs 201, 20n in the memory device 120. At this time, the master ECU 100 stores the values ​​of each piece of control data generated at predetermined time intervals in the memory device 120. In other words, the master ECU 100 stores the values ​​of each piece of generated control data in chronological order in the memory device 120.

[0043] Here, as an example, a case where a value is stored every 1 second is adopted. However, the interval at which the control data is stored is not limited to 1 second. Furthermore, the master ECU 100 may store each control data in the memory device 120 when an event occurs. Note that, as an example, FIG. 4 shows the value of each control data at each predetermined time.

[0044] In this manner, the master ECU 100 stores diagnostic information required for diagnosis from all control data generated by itself and all control data generated by the slave ECUs 201, 2n in the memory device 120. All control data includes information other than that required for vehicle fault diagnosis.

[0045] <Processing Operation> Here, the processing operation of each ECU will be described with reference to Fig. 2 to Fig. 7. First, the processing operation of the master ECU 100 will be described with reference to Figs.

[0046] Fig. 2 is a flowchart showing a connection code request process and a distribution process in the master ECU 100. When the ignition switch of the vehicle is turned on, the master ECU 100 starts the flowchart of Fig. 2. The flowchart of Fig. 2 is a process mainly performed by the microcomputer 110. The connection code request process can also be considered as a part replacement determination process.

[0047] In step S10, a connection code is requested from each ECU by broadcast. The microcomputer 110 transmits a request signal indicating a request for a connection code to the communication line 30. As a result, the request signal is transmitted to all slave ECUs 201, 20n connected to the communication line 30. In response to the request signal, all slave ECUs 201, 20n transmit their own connection codes and IDs to the communication line 30. Therefore, the master ECU 100 receives the connection codes and IDs from all slave ECUs 201, 20n. The processing operations of the slave ECUs 201, 20n will be described later.

[0048] In step S11, it is determined whether or not a different connection code has been received (determination unit). The microcomputer 110 compares its own connection code with the received connection code. By comparing the connection codes, the microcomputer 110 determines whether or not the slave ECUs 201, 20n have been replaced. In other words, the microcomputer 110 determines whether or not a part has been replaced.

[0049] If the microcomputer 110 receives a connection code different from its own connection code, the process proceeds to step S12. In this case, the microcomputer 110 determines that the slave ECU that transmitted the different connection code has been replaced. In other words, the microcomputer 110 determines that the slave ECU that transmitted the different connection code is the replaced ECU. The slave ECU that transmitted the different connection code can also be said to be the slave ECU that was replaced due to the cause of the abnormal state.

[0050] On the other hand, if the microcomputer 110 has not received a connection code different from its own connection code, the microcomputer 110 proceeds to step S13. In this case, the microcomputer 110 determines that all of the slave ECUs 201, 20n have not been replaced.

[0051] In this way, the master ECU 100 has a common connection code with the slave ECUs 201, 20n included in the in-vehicle system 1000, and thus can easily determine whether or not a part has been replaced.

[0052] In step S12, the slave ECU that transmitted the different connection code is stored as a newly connected ECU (storage unit). When the microcomputer 110 determines that a replacement has been performed, the microcomputer 110 stores the ID of the replaced slave ECU in the memory device 120. In this way, the microcomputer 110 stores the slave ECU that transmitted the different connection code as a newly connected ECU.

[0053] In step S13, the control data is stored (storage unit). The microcomputer 110 stores at least a part of the control data stored in the memory device 120 in the memory device 120 as diagnostic data to be used for diagnosis. The diagnostic data is control data for a predetermined period stored in the memory device 120. The diagnostic data may also be all of the control data stored in the memory device 120. The diagnostic data is a part of the input data for machine learning.

[0054] Furthermore, the microcomputer 110 may also store, as diagnostic data, in the memory device 120, the control data generated after it is determined in step S11 that part replacement has been performed. That is, the microcomputer 110 stores, as diagnostic data, in the memory device 120, the control data generated after step S11 and the control data generated by the slave ECUs 201, 20n after step S11. In this manner, the microcomputer 110 may store, in the memory device 120, the values ​​of the control data before part replacement and the values ​​of the control data after part replacement. Note that step S13 may be executed after step S14 is executed.

[0055] Moreover, the microcomputer 110 preferably classifies the control data before it is determined that the part has been replaced as an abnormal state, and classifies the control data after it is determined that the part has been replaced as a normal state and stores them (storage unit). The control data classified as an abnormal state corresponds to abnormal information. The control data classified as a normal state corresponds to normal information.

[0056] This allows the master ECU 100 to handle the control data as information associated with either an abnormal state or a normal state. Furthermore, the master ECU 100 can automatically distinguish between control data in an abnormal state and control data in a normal state without the intervention of an operator. This prevents the master ECU 100 from making a mistaken distinction. Furthermore, the master ECU 100 can save the operator time and effort.

[0057] In step S14, the connection code is broadcast to each ECU. The microcomputer 110 broadcasts the connection code to each ECU. The microcomputer 110 transmits the connection code to the communication line 30. As a result, the connection code is transmitted to all of the slave ECUs 201, 20n connected to the communication line 30. Thus, the multiple ECUs 100, 201, 20n of the in-vehicle system 1000 have a common connection code.

[0058] Next, Fig. 3 is a flowchart showing a transmission process between the master ECU 100 and the center. The master ECU 100 starts the process of the flowchart of Fig. 3 at predetermined time intervals while the ignition switch is on. The process of the flowchart of Fig. 2 is mainly performed by the microcomputer 110.

[0059] In step S20, it is determined whether or not a part has been replaced. If the microcomputer 110 determines YES in step S11, it determines that a part has been replaced and proceeds to step S21. If the microcomputer 110 determines NO in step S11, it does not determine that a part has been replaced and ends the flowchart of FIG.

[0060] In step S21, the control data and the ID are transmitted to the center. The microcomputer 110 transmits the ID stored in step S12 and the diagnostic data stored in step S13 to the center 10 via the antenna 140. In this manner, the microcomputer 110 transmits the ID and the diagnostic data as input data for machine learning. The microcomputer 110 may also transmit, as diagnostic data, the control data generated after determining in step S11 that part replacement has been performed.

[0061] This allows the master ECU 100 to allow the microcomputer 11 of the center 10 to machine-learn normal information, abnormal information, and identification information. The microcomputer 11 performs machine learning by distinguishing between abnormal information and identification information, and normal information. This allows the microcomputer 11 to obtain a state in which a part should be replaced, training data for parts that should be replaced, and training data for cases in which the part should not be replaced. Note that the machine learning may be performed by any of the microcomputers 110, 211, and 21n. In this case, the microcomputer 110 stores the ID stored in step S12 and the diagnostic data stored in step S13 in a memory device that the microcomputer can refer to.

[0062] Next, the response process of the slave ECU 200, 20n will be described with reference to Fig. 5, Fig. 6, and Fig. 7. Fig. 5 is a flowchart showing the response process of the connection code in the slave ECU 200, 20n. The slave ECU 200, 20n starts the flowchart of Fig. 5 when the ignition switch of the vehicle is turned on. The flowchart of Fig. 5 is a process mainly performed by the microcomputers 211, 21n.

[0063] In step S30, it is determined whether or not a request for a connection code has been received. When the microcomputer 211, 21n receives a request signal transmitted from the microcomputer 110, it determines that a request for a connection code has been received and proceeds to step S31. On the other hand, when the microcomputer 211, 21n does not receive a request signal transmitted from the microcomputer 110, it does not determine that a request for a connection code has been received and repeats step S30.

[0064] In step S31, the microcomputer 211 responds with the stored connection code. The microcomputer 211 transmits the connection code stored in the memory device 221 to the communication line 30. Similarly, the microcomputer 21n transmits the connection code stored in the memory device 22n to the communication line 30. At this time, the microcomputers 211 and 21n transmit the frame format shown in Fig. 7. That is, the microcomputers 211 and 21n transmit a frame format including an ID indicating the microcomputers themselves in addition to the connection code that is part of the payload.

[0065] 5 at predetermined time intervals while the ignition switch is on. In this case, if the microcomputer 211, 21n makes a NO determination in step S30, the microcomputer 211, 21n ends the flowchart in FIG.

[0066] Next, Fig. 6 is a flowchart showing a process of storing a connection code in the slave ECU 200, 20n. When the ignition switch of the vehicle is turned on, the slave ECU 200, 20n starts the process of the flowchart of Fig. 5. The process of the flowchart of Fig. 6 is mainly performed by the microcomputers 211, 21n.

[0067] In step S40, it is determined whether or not a connection code has been received. When the microcomputer 211, 21n receives the connection code transmitted from the microcomputer 110, the process proceeds to step S41. When the microcomputer 211, 21n does not receive the request signal transmitted from the microcomputer 110, the microcomputer 211, 21n repeatedly executes step S41.

[0068] In step S41, the received connection code is stored. The microcomputer 211 stores the received connection code in the memory device 221. Similarly, the microcomputer 21n stores the received connection code in the memory device 22n. At this time, the microcomputers 211 and 21n overwrite the connection code stored in the memory devices 221 and 22n with the received connection code.

[0069] 6 at predetermined time intervals while the ignition switch is on. In this case, if the microcomputer 211, 21n makes a NO determination in step S40, the microcomputer 211, 21n ends the flowchart in FIG.

[0070] <Effects> As described above, the master ECU 100 can automatically store the control data before the replacement of the slave ECU. Therefore, the master ECU 100 can store the control data without the intervention of an operator. Therefore, the master ECU 100 can save the operator's time and effort. Furthermore, the master ECU 100 can prevent data deficiencies and input errors caused by an operator forgetting to input data. In other words, the master ECU 100 can store accurate data as the control data required for diagnosis.

[0071] Furthermore, the master ECU 100 transmits the accurate data as input data for machine learning to the center 10. Therefore, the master ECU 100 can improve the accuracy of the machine learning model. Also, the center 10 can generate a machine learning model with improved accuracy.

[0072] The above describes the preferred embodiment of the present disclosure. However, the present disclosure is not limited to the above embodiment, and various modifications are possible within the scope of the present disclosure. Below, the second embodiment will be described as another embodiment of the present disclosure. The above embodiment and the second embodiment can be implemented alone, but can also be implemented in appropriate combination. The present disclosure is not limited to the combinations shown in the embodiments, and can be implemented in various combinations.

[0073] Second embodiment A master ECU 100 according to the second embodiment and an in-vehicle system 1000 including the master ECU 100 will be described with reference to Figs. 8 to 11. In this embodiment, differences from the first embodiment will be mainly described. The configurations of the master ECU 100 and the in-vehicle system 1000 are similar to those of the first embodiment. In this embodiment, differences from the first embodiment are mainly in the target parts and the processing contents. In this embodiment, a wire harness is adopted as a part in addition to a slave ECU.

[0074] First, the wire harness will be described with reference to Fig. 9 and Fig. 11. The wire harness is electrically connected to the connectors of each of the ECUs 100, 201, 20n, for example. Each of the ECUs 100, 201, 20n may have a plurality of connectors. Here, an example in which two connectors A and B are provided is adopted as an example. Thus, each of the ECUs 100, 201, 20n may have three or more connectors. Each of the ECUs 100, 201, 20n may have a different number of connectors.

[0075] 11 is a conceptual diagram showing a terminal portion 40 of a wire harness. The terminal portion 40 includes a plurality of terminals and is electrically connected to a connector.

[0076] Regarding the terminal section 40 of the wire harness at the time of shipment, for example, the first terminal 41 is set to ground voltage and the second terminal 42 is set to ground voltage. On the other hand, the terminal section 40 of the replaced wire harness has wiring different from that at the time of shipment, with the first terminal 41 being set to battery voltage (12 V) and the second terminal 42 being set to ground voltage.

[0077] Note that the time of shipment refers to the time of shipment of the in-vehicle system 1000. The wire harness at the time of shipment and the replaced wire harness are different wire harnesses. For convenience, the same reference numerals are given to the terminal portions of both wire harnesses.

[0078] In this way, wire harnesses with different wiring have different potential differences (voltage between terminals) between terminals 41, 42 in terminal section 40. For example, the potential difference at the time of shipment is 0V. On the other hand, the potential difference after replacement is 12V. In this way, when a wire harness is replaced, the electrical characteristics (potential difference) between multiple terminals connected to the connector change. The potential difference at the time of shipment can be considered as a standard value or a reference value.

[0079] Therefore, each of the ECUs 100, 201, and 20n uses two terminals 41 and 42 of the terminal unit 40 to determine whether the wire harness has been replaced. Each of the microcomputers 110, 211, and 21n determines whether the wire harness has been replaced based on the potential difference between the terminals 41 and 42. In other words, each of the microcomputers 110, 211, and 21n can confirm whether the wire harness has been replaced by determining whether the wiring is different based on the potential difference.

[0080] When an ignition switch is turned on, each of the ECUs 100, 201, and 20n starts the flow chart shown in Fig. 9. Here, the slave ECU 201 will be used as an example for explanation.

[0081] In step S50, it is determined whether the voltage between the terminals is equal to or greater than a threshold (harness determination unit). If the microcomputer 211 determines that the potential difference between the terminals 41, 42 is equal to or greater than the threshold, it determines that the wire harness has been replaced and proceeds to step S51. If the microcomputer 211 does not determine that the potential difference between the terminals 41, 42 is equal to or greater than the threshold, it determines that the wire harness has not been replaced and repeats step S50.

[0082] The threshold value here is a value that allows determination of whether or not the wire harness has been replaced based on the inter-terminal voltage. The threshold value is, for example, 6 V. If the microcomputer 211 makes a NO determination in step S50, the flow chart of FIG. 9 may be terminated.

[0083] In step S51, the microcomputer 211 stores in the connection code that the wire harness has been replaced. In other words, the microcomputer 211 generates a connection code including information indicating that the wire harness has been replaced.

[0084] Here, the connection code will be described. When transmitting a connection code, the slave ECUs 201, 20n transmit a frame format shown in Fig. 10. The connection code is divided into upper 4 bits and lower 4 bits. The upper 4 bits are the same as the connection code in the first embodiment. In other words, the upper 4 bits are common to the ECUs 100, 201, 20n of the in-vehicle system 1000.

[0085] The lower four bits are assigned information indicating whether the wire harness has been replaced. When each microcomputer 110, 211, 21n determines that the wire harness connected to itself has been replaced, it updates the lower four bits of the connection code. For example, the lower four bits may be 0000 (initial value) as information indicating that the wire harness has not been replaced, XX01 as information indicating that the wire harness of connector A has been replaced, and XX10 as information indicating that the wire harness of connector B has been replaced.

[0086] In this way, the lower 4 bits contain connector information that indicates whether the wire harness has been replaced for each connector. The lower 4 bits can also be considered a code that identifies the part. In step S17a, which will be described later, a connection code whose lower 4 bits are 0000 is delivered.

[0087] The information indicating whether the wire harness has been replaced is not limited to the lowest 4 bits. The information indicating whether the wire harness has been replaced may be included as part of the connection code. The 2 bits of XX may be assigned information indicating the number of times the wire harness has been replaced or information indicating the type of the replaced wire harness.

[0088] The lower 4 bits correspond to part information that indicates the part (wire harness). The connection code here can be considered as replacement confirmation information that includes part information.

[0089] Here, the connection code request process and distribution process in the master ECU 100 will be described with reference to Fig. 8. When the ignition switch of the vehicle is turned on, the master ECU 100 starts the flowchart of Fig. 8. The flowchart of Fig. 8 is a process that is mainly performed by the microcomputer 110.

[0090] Step S10a is the same as step S10. In step S11a, it is determined whether or not the upper four bits of the connection codes match (determination section). The microcomputer 110 compares the upper four bits of its own connection code with the upper four bits of the received connection code. By comparing the upper four bits, the microcomputer 110 determines whether or not the slave ECUs 201, 20n have been replaced.

[0091] Then, if the microcomputer 110 receives a connection code whose upper four bits are different from its own connection code, the microcomputer 110 proceeds to step S12a. In this case, the microcomputer 110 determines that the slave ECU that transmitted the connection code whose upper four bits are different has been replaced. In other words, the microcomputer 110 determines that the slave ECU that transmitted the connection code whose upper four bits are different is the replaced ECU. The slave ECU that transmitted the connection code whose upper four bits are different can also be said to be the slave ECU that was replaced due to the cause of the abnormal state.

[0092] On the other hand, if the microcomputer 110 does not receive a connection code whose upper 4 bits are different from its own connection code, the microcomputer 110 proceeds to step S13a. The microcomputer 110 determines that none of the slave ECUs 201, 20n have been replaced. In this way, by sharing a partially common connection code with all the ECUs 100, 201, 20, it is possible to easily determine whether or not a part has been replaced.

[0093] Step S12a is the same as step S12. Step S13a is the same as step S13.

[0094] In step S14a, it is determined whether the lower 4 bits of the connection code are a predetermined value (determination section). This is to determine whether the wire harness has been replaced. The predetermined value here is the initial value 0000.

[0095] The microcomputer 110 determines whether the lowest four bits of the received connection code are 0000. If the microcomputer 110 determines that the lowest four bits are not 0000, the process proceeds to step S15a. In this case, the microcomputer 110 determines that the wire harness has been replaced in the slave ECU that transmitted the connection code whose lowest four bits are not 0000. The slave ECU that transmitted the connection code whose lowest four bits are not 0000 is also referred to as the ECU whose wire harness has been replaced or the ECU in question.

[0096] On the other hand, the microcomputer 110 proceeds to step S16a if it has not determined that the lower four bits are 0000. In this case, the microcomputer 110 determines that the wire harnesses have not been replaced in all of the slave ECUs 201, 20n.

[0097] The microcomputer 110 may execute step S14a for its own connection code. In this case, if the microcomputer 110 does not determine that the lower four bits are 0000, the microcomputer 110 proceeds to step S15a. If the microcomputer 110 determines that the lower four bits are 0000, the microcomputer 110 proceeds to step S16a.

[0098] In this way, by having the above-mentioned four lower bits in the connection code, the replaced wire harness can be identified.

[0099] In the present embodiment, as an example, the lower 4 bits are used, which include connector information indicating whether or not the wire harness has been replaced for each connector. Therefore, when the microcomputer 110 determines that the wire harness has been replaced, it may determine which of the multiple connectors the replaced wire harness was connected to based on the lower 4 bits. This allows the connector to which the replaced wire harness is connected to be identified.

[0100] In step S15a, the wire harness of the corresponding ECU is stored as having been replaced (storage unit). When the microcomputer 110 determines that the wire harness has been replaced, it associates the ID of the corresponding ECU with the lowest 4 bits and stores them in the memory device 120. In this way, the microcomputer 110 stores the slave ECU that has transmitted a connection code whose lowest 4 bits are not 0000 as an ECU whose wire harness has been replaced.

[0101] Step S16a is similar to step S13. Step S17a is similar to step S14.

[0102] The master ECU 100 of the second embodiment executes the flowchart shown in FIG. 3, similarly to the first embodiment. When the microcomputer 110 judges NO in steps S11a and S14a, it judges that a part has been replaced, and proceeds to step S21. In step S21, the microcomputer 110 transmits the ID stored in step S12a and the diagnostic data stored in steps S13a and S16a to the center 10 via the antenna 140. Furthermore, the microcomputer 110 adds the ID of the corresponding ECU stored in step S15a and the lower four bits, and transmits the result to the center 10 via the antenna 140. In this way, the microcomputer 110 transmits the ID, the lower four bits, and the diagnostic data as input data for machine learning.

[0103] The second embodiment can achieve the same effects as the first embodiment.

[0104] Although the present disclosure has been described based on the embodiment, it is understood that the present disclosure is not limited to the embodiment or structure. The present disclosure also encompasses various modifications and modifications within the equivalent range. In addition, although various combinations and forms are shown in the present disclosure, other combinations and forms including only one element, more than one element, or less than one element are also within the scope and concept of the present disclosure. [Explanation of symbols]

[0105] 10...center, 11...microcomputer, 12...memory device, 13...communication device, 14...antenna, 100...master ECU, 110...microcomputer, 120...memory device, 130...communication device, 140...antenna, 201...first slave ECU, 211...microcomputer, 221...memory device, 231...communication device, 20n...nth slave ECU, 21n...microcomputer, 22n...memory device, 23n...communication device, 40...terminal portion, 41...first terminal, 42...second terminal

Claims

1. A diagnostic device that is mounted on a vehicle together with an electrically connected component and is capable of acquiring diagnostic information correlated with a fault in the vehicle, A determination unit (S11, S11a) that determines whether or not the part has been replaced; A diagnostic device comprising: a memory unit (S12, S13, S12a, S13a, S15a, S16a) that stores, when it is determined that a replacement has been performed, part information of the replaced part and at least the diagnostic information obtained before it is determined that the replacement has been performed.

2. The diagnostic device according to claim 1 , wherein the memory unit classifies the diagnostic information before it is determined that the replacement has been performed as an abnormal state, and classifies and stores the diagnostic information after it is determined that the replacement has been performed as a normal state.

3. a communication system with an electronic control device connected via a communication line; a communication device that communicates with the electronic control device via the communication line; and a storage device that stores replacement confirmation information common to the electronic control device, The diagnostic device according to claim 2 , wherein the determination unit determines that the part has been replaced when the replacement confirmation information received via the communication device does not match the replacement confirmation information stored in the storage device.

4. The replacement confirmation information includes the part information, 4. The diagnostic device according to claim 3, wherein the determination unit determines that a part has been replaced when the part information in the replacement confirmation information received via the communication device does not match the part information in the replacement confirmation information stored in the storage device, and identifies the replaced part.

5. A connector is provided to electrically connect a plurality of terminals of the wire harness, 5. The diagnostic device according to claim 4, further comprising a harness determination unit (S51) that determines that the wire harness having the plurality of terminals has been replaced when a change occurs in electrical characteristics between the plurality of terminals connected to the connector.

6. The part information includes connector information indicating whether the wire harness has been replaced for each connector, 6. The diagnostic device according to claim 5, wherein the determination unit determines that the wire harness, which is the part, has been replaced when the part information in the replacement confirmation information received via the communication device does not match the part information in the replacement confirmation information stored in the storage device, and identifies to which of the multiple connectors the replaced wire harness was connected.

7. The diagnostic device according to claim 2 or 5, wherein the diagnostic information classified into the abnormal state, the part information of the replaced part, and the diagnostic information classified into the normal state are used as input data for machine learning to generate a fault diagnosis model.

Images