Diagnostic equipment

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 a diagnostic device.

Background Art

[0002] There is an abnormality diagnosis system disclosed in Patent Document 1. 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 unit that determines the cause of a malfunction in the image processing device from the log data based on machine learning. Further, the abnormality diagnosis system further includes a setting unit that inputs work information for dealing with the malfunction. Then, the machine learning unit determines the cause of the malfunction from the log data and the work information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the above abnormality diagnosis system, a service technician inputs work information. Therefore, in the abnormality diagnosis system, it is necessary for the service technician to input the information, which takes time and effort.

[0005] One object of the disclosure is to provide a diagnostic device that can save the labor of the operator.

Means for Solving the Problems

[0006] The diagnostic device disclosed herein is a diagnostic device mounted on a vehicle together with electrically connected components and capable of acquiring diagnostic information correlated with a vehicle failure, a determination unit (S11, S11a) that determines whether or not a component has been replaced, If it is determined that a replacement has been performed, the system includes a storage unit (S12, S13, S12a, S13a, S15a, S16a) that stores the part information of the replaced part and diagnostic information acquired at least before it was determined that a replacement had been performed.

[0007] This allows the diagnostic device to automatically store diagnostic information before any parts are replaced. Therefore, the diagnostic device can store diagnostic information without requiring any manual intervention from a worker. Thus, the diagnostic device can reduce the workload for the worker.

[0008] The various embodiments disclosed in this specification employ different technical means to achieve their respective objectives. The claims and the reference numerals in parentheses in this section are illustrative in their correspondence with the embodiments described later 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 subsequent detailed description and the accompanying drawings. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram illustrating the schematic configuration of an in-vehicle system. [Figure 2] This flowchart shows the process of requesting and distributing connection codes by the master ECU. [Figure 3] This is a flowchart showing the transmission process of the master ECU. [Figure 4] This image shows an example of control data. [Figure 5] This is a flowchart showing the response processing of the slave ECU. [Figure 6] This is a flowchart showing the process of storing the connection code of a slave ECU. [Figure 7] This is an image diagram showing an example of a frame format. [Figure 8] This flowchart shows the request and distribution process of connection codes by the Starter ECU in the second embodiment. [Figure 9] This is a flowchart showing the process for determining whether to replace the wire harness in the second embodiment. [Figure 10] This is an image diagram showing an example of the frame format of the second embodiment. [Figure 11] This is an illustrative diagram showing an example of the terminal section of the second embodiment. [Modes for carrying out the invention]

[0010] In the following, several embodiments for implementing this disclosure will be described with reference to the drawings. In each embodiment, parts corresponding to matters described in a prior embodiment may be denoted by the same reference numerals, and redundant descriptions may be omitted. If only a part of the configuration is described in each embodiment, other parts of the configuration can be referred to and applied to other embodiments described in advance.

[0011] (First Embodiment) The master ECU 100 and the in-vehicle system 1000 including the master ECU 100 of the first embodiment will be described with reference to Figures 1 to 7. In this embodiment, an example is adopted in which a diagnostic device is applied to the master ECU 100. 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 slave ECUs 201 to 20n. ECU is an abbreviation for Electronic Control Unit.

[0012] In the drawings, the center is labeled CNT, the master ECU is labeled MECU, and the slave ECUs are labeled 1ECU or nECU. Additionally, the drawings label the microcontroller as MCU, the memory device as MMD, and the communication device as DCM.

[0013] <In-vehicle systems, center> As shown in FIG. 1, the in-vehicle system 1000 includes a master ECU 100, slave ECUs 201, 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, 20n are configured to be communicable via the communication line 30. The slave ECUs 201, 20n correspond to electronic control devices.

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

[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 communicable with the in-vehicle system 1000. Also, the center 10 is configured to be individually communicable with each in-vehicle system 1000 mounted on a plurality of vehicles. Therefore, the center 10 can receive various information from the plurality of in-vehicle systems 1000. The various information includes normal information and abnormal information as diagnostic information, identification information unique to each ECU, and the like. These information will be described in detail later.

[0016] The microcomputer 11 includes an arithmetic processing device such as a CPU, storage media such as a RAM and a ROM, an input / output device, and the like. 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 the antenna 14. The CPU is an abbreviation for Central Processing Unit. The RAM is an abbreviation for Random Access Memory. The 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 media or the memory device 12.

[0018] Furthermore, the microcontroller 11 performs machine learning on normal information, abnormal information, and identification information. The microcontroller 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 abnormal information. A faulty ECU can be considered a faulty part. Normal information, abnormal information, and identification information are input data for the machine learning that generates the fault diagnosis model. Therefore, the center 10 (microcontroller 11) collects diagnostic information and identification information from multiple in-vehicle systems 1000 in order to generate a fault diagnosis model. The input data may consist only of abnormal information and identification information.

[0019] Diagnostic information is information necessary for diagnosing vehicle malfunctions. Abnormal information can be considered diagnostic information for when the vehicle is malfunctioning. Normal information can be considered diagnostic information for when the vehicle is functioning normally. Identification information is information unique to each component. Identification information includes IDs (identification) and information composed of multiple bits. Identification information corresponds to component information. Components include ECUs and wire harnesses.

[0020] The center 10 and the multiple in-vehicle systems 1000 can be said to be part of a communication network. However, the in-vehicle systems 1000 do not necessarily have communication capabilities with the center 10. In this case, the master ECU 100 may perform machine learning.

[0021] <Slave ECU> As shown in Figure 1, the system includes a first slave ECU 201, a microcontroller 211, a memory device 221, and a communication device 231. It also includes an nth slave ECU 20n, a microcontroller 21n, a memory device 22n, and a communication device 23n. Various sensors and other devices are connected to slave ECUs 201 and 20n.

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

[0023] Thus, the first slave ECU 201 and the nth slave ECU 20n have similar hardware configurations. However, the processing operations of the microcontroller 211 and the microcontroller 21n differ between the first slave ECU 201 and the nth slave ECU 20n.

[0024] The microcontrollers 211 and 21n are configured so that when the vehicle's ignition switch is turned on, the arithmetic processing unit performs calculations at a predetermined execution timing. The arithmetic processing unit performs calculations using, for example, signals from sensors. The arithmetic processing unit then generates control data through these calculations. The arithmetic processing unit may also use the signals from the sensors themselves as control data. In this case, the generated control data is also used.

[0025] The generated control data is stored in memory devices 221 and 22n. Additionally, the slave ECUs 201 and 20n have their own IDs and connection codes stored in 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 ensure that multiple ECUs 100, 201, and 20n in the in-vehicle system 1000 have a common connection code. Therefore, multiple ECUs 100, 201, and 20n will have the same connection code. However, a replaced slave ECU 201 or 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 or not the slave ECUs 201 and 20n have been replaced by comparing its own connection code with the connection codes of the slave ECUs 201 and 20n. In other words, the connection code can be considered information for determining whether or not the slave ECUs 201 and 20n have been replaced. The connection code corresponds to replacement confirmation information.

[0028] Each arithmetic processing unit then transmits the generated control data via the communication devices 231 and 23n. When the microcontrollers 211 and 21n transmit the control data, they also transmit an ID that identifies them. Each arithmetic processing unit also transmits the control data, for example, at a predetermined transmission timing. Furthermore, each arithmetic processing unit transmits connection codes, IDs, etc., in response to requests from the master ECU 100. The communication devices 231 and 23n transmit the control data, IDs, connection codes, etc., in a predetermined frame format.

[0029] For example, microcontroller 211 generates and transmits control data s1 and s2. Control data s1 and s2 are stored in memory device 221. Meanwhile, microcontroller 21n generates and transmits control data n1, n2, and nn. Control data n1, n2, and nn are stored in memory device 22n.

[0030] Furthermore, as shown in Figure 4, the microcontroller 211 transmits the values ​​generated at each execution timing as control data s1 and s2. Similarly, the microcontroller 21n transmits the values ​​generated at each execution timing as control data n1, n2, and nn. Note that the microcontrollers 211 and 21n may also generate and transmit control data other than the control data described above.

[0031] If the slave ECU201,20n or the sensors connected to the slave ECU201,20n malfunction, some control data will show values ​​that are not normally obtainable. In other words, multiple control data contains data (information) necessary for diagnosing vehicle malfunctions. Such control data can be used to diagnose vehicle malfunctions. Examples of control data necessary for malfunction diagnosis include temperature, rotational speed, and rotational angle.

[0032] Here, the control data s1, s2, n1, n2, and nn described above are used as the control data necessary for diagnosis. Therefore, the control data s1, s2, n1, n2, and nn correspond to diagnostic information. Furthermore, each value of the control data s1, s2, n1, n2, and nn can also be said to correspond to diagnostic information. Unless otherwise specified below, control data will be assumed to represent diagnostic information.

[0033] Furthermore, the control data can be considered information related to the failure of the slave ECU201,20n. Also, failures of the slave ECU201,20n and the sensors connected to them are also considered vehicle failures. Therefore, the control data can be considered diagnostic information correlated with vehicle failures.

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

[0035] <Master ECU> As shown in Figure 1, the master ECU 100 comprises a microcontroller 110, a memory device 120, a communication device 130, and an antenna 140. The microcontroller 110 comprises an arithmetic processing unit such as a CPU, a storage medium such as RAM, and input / output devices. The memory device 120 comprises a storage medium such as ROM. The communication device 130 comprises a device that performs communication via a communication line 30 and a device that performs wireless communication via the 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 the communication line 30. In other words, the master ECU 100 is configured to communicate with the slave ECUs 201 and 20n. The microcontroller 110 is also configured to communicate wirelessly with the center 10 via the antenna 140.

[0037] In this embodiment, for convenience, the device that performs communication via the communication line 30 and the device that performs wireless communication via the antenna 140 are combined as the communication device 130. However, the master ECU 100 may have separate devices for the communication via the communication line 30 and the wireless communication via the antenna 140. Also, the memory device 120 may be built into the microcontroller 110.

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

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

[0040] For example, as shown in Figure 4, the microcontroller 110 transmits the values ​​generated at each execution timing as control data m1 and m2. The microcontroller 110 may also transmit control data other than the control data described above. In this case, control data m1 and m2 are diagnostic information generated by the microcontroller 110.

[0041] Furthermore, the microcontroller 110 can acquire control data, IDs, connection codes, etc., transmitted from the slave ECUs 201 and 20n via the communication device 130. In other words, when control data etc. is transmitted from the slave ECUs 201 and 20n to the communication line 30, the microcontroller 110 receives that control data etc. The received control data etc. is stored in the memory device 120. Furthermore, the microcontroller 110 transmits the control data etc. stored in the memory device 120 to the center 10 via the antenna 140.

[0042] As shown in Figure 4, the master ECU 100 stores the control data it generates and the control data generated by the slave ECUs 201 and 20n in the memory device 120. At this time, the master ECU 100 stores the value of each control data generated at predetermined intervals in the memory device 120. In other words, the master ECU 100 stores the value of each generated control data in the memory device 120 in chronological order.

[0043] Here, as an example, we adopt an example where values ​​are stored every 1 second. However, the interval for storing control data is not limited to 1 second. Furthermore, the master ECU 100 may also store each control data in the memory device 120 when an event occurs. Figure 4 shows, as an example, the values ​​of each control data at predetermined time intervals.

[0044] In this way, the master ECU 100 stores in the memory device 120 all the control data it generates, as well as all the control data generated by the slave ECUs 201 and 2n, that are necessary for diagnosis. All control data includes information other than that necessary for diagnosing vehicle malfunctions.

[0045] <Processing Actions> Here, we will explain the processing operation of each ECU using Figures 2 to 7. First, we will explain the processing operation of the master ECU 100 using Figures 2, 3, and 4.

[0046] Figure 2 is a flowchart showing the connection code request and distribution processes in the master ECU 100. The master ECU 100 starts the flowchart in Figure 2 when the vehicle's ignition switch is turned on. The flowchart in Figure 2 mainly represents the processes performed by the microcontroller 110. The connection code request process can also be considered a parts replacement determination process.

[0047] In step S10, a connection code is requested from each ECU via broadcast. The microcontroller 110 sends a request signal to the communication line 30 indicating a request for a connection code. This sends the request signal to all slave ECUs 201 and 20n connected to the communication line 30. All slave ECUs 201 and 20n respond to the request signal by sending their own connection code and ID to the communication line 30. As a result, the master ECU 100 receives the connection code and ID from all slave ECUs 201 and 20n. The processing operations of the slave ECUs 201 and 20n will be explained later.

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

[0049] Then, if the microcontroller 110 receives a connection code different from its own, it proceeds to step S12. In this case, the microcontroller 110 determines that the slave ECU that sent the different connection code has been replaced. In other words, the microcontroller 110 determines that the slave ECU that sent the different connection code is the replaced ECU. It can also be said that the slave ECU that sent the different connection code is the slave ECU that was replaced because it was the cause of the abnormal condition.

[0050] On the other hand, if the microcontroller 110 does not receive a connection code different from its own, it proceeds to step S13. In this case, the microcontroller 110 determines that none of the slave ECUs 201 and 20n have been replaced.

[0051] Thus, the master ECU 100 has a common connection code with the slave ECUs 201 and 20n included in the in-vehicle system 1000, making it easy to determine whether or not a part has been replaced.

[0052] In step S12, the slave ECU that sent a different connection code is stored as a new connected ECU (storage unit). If the microcontroller 110 determines that an exchange has occurred, it stores the ID of the exchanged slave ECU in the memory device 120. In this way, the microcontroller 110 stores the slave ECU that sent a different connection code as a new connected ECU.

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

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

[0055] Furthermore, it is preferable for the microcontroller 110 to classify control data before it is determined that a component has been replaced as an abnormal state and to classify and store control data after it is determined that a replacement has been performed as a normal state (storage unit). Control data classified as an abnormal state corresponds to abnormal information. Control data classified as a normal state corresponds to normal information.

[0056] This allows the master ECU 100 to treat control data as information associated with either an abnormal or normal state. Furthermore, the master ECU 100 can automatically distinguish between abnormal and normal control data without human intervention. Therefore, the master ECU 100 can prevent incorrect classification. In addition, the master ECU 100 can reduce the workload of the operator.

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

[0058] Next, Figure 3 is a flowchart showing the transmission process between the master ECU 100 and the center. The master ECU 100 starts the flowchart in Figure 3 at predetermined intervals while the ignition switch is ON. The flowchart in Figure 2 mainly shows the processes performed by the microcontroller 110.

[0059] In step S20, it is determined whether or not a component replacement has been performed. If the microcontroller 110 determined YES in step S11, it determines that a component replacement has been performed and proceeds to step S21. If the microcontroller 110 determined NO in step S11, it does not determine that a component replacement has been performed and terminates the flowchart in Figure 3.

[0060] In step S21, the control data and ID are sent to the center. The microcontroller 110 sends the ID stored in step S12 and the diagnostic data stored in step S13 to the center 10 via the antenna 140. In this way, the microcontroller 110 sends the ID and diagnostic data as input data for machine learning. The microcontroller 110 may also send the control data generated after determining in step S11 that a component replacement has been performed, as diagnostic data.

[0061] This allows the master ECU 100 to have the microcontroller 11 of the center 10 learn normal information, abnormal information, and identification information through machine learning. The microcontroller 11 learns by distinguishing between abnormal information and identification information and normal information. Through this, the microcontroller 11 can obtain the conditions under which a component should be replaced, training data for the component to be replaced, and training data for cases where it should not be replaced. Note that the machine learning may be performed by any of the microcontrollers 110, 211, or 21n. In this case, the microcontroller 110 stores the ID stored in step S12 and the diagnostic data stored in step S13 in a memory device accessible to the microcontroller.

[0062] Next, we will explain the response processing of the slave ECUs 200 and 20n using Figures 5, 6, and 7. Figure 5 is a flowchart showing the response processing of connection codes in the slave ECUs 200 and 20n. When the vehicle's ignition switch is turned on, the slave ECUs 200 and 20n start the flowchart in Figure 5. The flowchart in Figure 5 mainly represents the processing performed by the microcontrollers 211 and 21n.

[0063] In step S30, it is determined whether or not a request for a connection code has been received. When microcontrollers 211 and 21n receive a request signal transmitted from microcontroller 110, they determine that a request for a connection code has been received and proceed to step S31. If microcontrollers 211 and 21n do not receive a request signal transmitted from microcontroller 110, they do not determine that a request for a connection code has been received and repeatedly execute step S30.

[0064] In step S31, the stored connection code is responded to. Microcontroller 211 transmits the connection code stored in memory device 221 to communication line 30. Similarly, microcontroller 21n transmits the connection code stored in memory device 22n to communication line 30. At this time, microcontrollers 211 and 21n transmit the frame format shown in Figure 7. In other words, microcontrollers 211 and 21n transmit a frame format that includes an ID identifying themselves, in addition to the connection code which is part of the payload.

[0065] The microcontrollers 211 and 21n may execute the flowchart in Figure 5 at predetermined intervals while the ignition switch is ON. In this case, if the microcontrollers 211 and 21n determine NO in step S30, they terminate the flowchart in Figure 5.

[0066] Next, Figure 6 is a flowchart showing the storage process of connection codes in slave ECUs 200 and 20n. When the vehicle's ignition switch is turned on, the slave ECUs 200 and 20n start the flowchart shown in Figure 5. The flowchart in Figure 6 mainly shows the processing performed by microcontrollers 211 and 21n.

[0067] In step S40, it is determined whether or not a connection code has been received. If microcontrollers 211 and 21n receive a connection code transmitted from microcontroller 110, they proceed to step S41. If microcontrollers 211 and 21n do not receive a request signal transmitted from microcontroller 110, they repeatedly execute step S41.

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

[0069] The microcontrollers 211 and 21n may execute the flowchart in Figure 6 at predetermined intervals while the ignition switch is ON. In this case, if the microcontrollers 211 and 21n determine NO in step S40, they terminate the flowchart in Figure 6.

[0070] <Effects> As described above, the master ECU 100 can automatically store control data before the slave ECU is replaced. Therefore, the master ECU 100 can store control data without any intervention from the operator. Thus, the master ECU 100 can reduce the workload for the operator. In addition, the master ECU 100 can prevent data loss or input errors caused by operators forgetting to input data. In short, the master ECU 100 can store accurate data as control data necessary for diagnosis.

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

[0072] Preferred embodiments of the present disclosure have been described above. However, the present disclosure is not limited to the above embodiments, and various modifications are possible without departing from the spirit of the present disclosure. A second embodiment, as another form of the present disclosure, is described below. The above embodiments and the second embodiment can be implemented individually, or they can be implemented in combination as appropriate. The present disclosure can be implemented in various combinations, not limited to the combinations shown in the embodiments.

[0073] (Second Embodiment) The master ECU 100 and the in-vehicle system 1000 including the master ECU 100 of the second embodiment will be described using Figures 8 to 11. In this embodiment, the differences from the first embodiment will be mainly described. The configuration of the master ECU 100 and the in-vehicle system 1000 is the same as in the first embodiment. In this embodiment, the main differences from the first embodiment are the target components and processing content. In this embodiment, in addition to the slave ECU, a wire harness is used as a component.

[0074] First, the wire harness will be explained using Figures 9 and 11. The wire harness is electrically connected to the connectors of each ECU 100, 201, and 20n, for example. Each ECU 100, 201, and 20n may also have multiple connectors. Here, as an example, we will adopt an example with two connectors A and B. Therefore, each ECU 100, 201, and 20n may have three or more connectors. Each ECU 100, 201, and 20n may have a different number of connectors.

[0075] Figure 11 is an illustrative diagram showing the terminal section 40 of the wire harness. The terminal section 40 has multiple terminals and is electrically connected to a connector.

[0076] The terminal section 40 of the wire harness at the time of shipment is assumed to have, for example, the first terminal 41 connected to the ground voltage and the second terminal 42 connected to the ground voltage. On the other hand, the terminal section 40 of the replaced wire harness is assumed to have a different wiring configuration from the time of shipment, with the first terminal 41 connected to the battery voltage (12V) and the second terminal 42 connected to the ground voltage.

[0077] Note that "at the time of shipment" refers to the time when the in-vehicle system 1000 was shipped. Also, the wire harness at the time of shipment and the replaced wire harness are different wire harnesses. For convenience, the same symbols are assigned to the terminals of both wire harnesses.

[0078] Thus, wire harnesses with different wiring configurations will have different potential differences (voltages between terminals) at terminals 41 and 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. Note that the potential difference at the time of shipment can be considered a standard or reference value.

[0079] Therefore, each ECU 100, 201, and 20n uses the two terminals 41 and 42 of the terminal section 40 to determine whether the wire harness has been replaced. Each microcontroller 110, 211, and 21n determines whether the wire harness has been replaced based on the potential difference between terminals 41 and 42. In other words, each microcontroller 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] Each ECU 100, 201, and 20n starts the flowchart shown in Figure 9 when the ignition switch is turned on. Here, we will explain using the slave ECU 201 as an example.

[0081] In step S50, the system determines whether the voltage between terminals is above a threshold (harness determination unit). If the microcontroller 211 determines that the potential difference between terminals 41 and 42 is above the threshold, it assumes that the wire harness has been replaced and proceeds to step S51. If the microcontroller 211 does not determine that the potential difference between terminals 41 and 42 is above the threshold, it assumes that the wire harness has not been replaced and repeatedly executes step S50.

[0082] The threshold here is a value that allows you to determine whether or not the wire harness has been replaced based on the voltage between the terminals. The threshold is, for example, 6V. Note that if the microcontroller 211 determines NO in step S50, it may terminate the flowchart in Figure 9.

[0083] In step S51, the connection code is stored as indicating that the wire harness has been replaced. The microcontroller 211 stores information indicating that the wire harness has been replaced in its own connection code. In other words, the microcontroller 211 generates a connection code that includes information indicating that the wire harness has been replaced.

[0084] Here, we will explain the connection code. When the slave ECUs 201 and 20n transmit the connection code, they transmit the frame format shown in Figure 10. The connection code is divided into an upper 4-bit and a lower 4-bit. 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, and 20n of the in-vehicle system 1000.

[0085] The lower four bits contain information indicating whether or not the wire harness has been replaced. Each microcontroller 110, 211, and 21n updates the lower four bits of the connection code if it determines that the wire harness connected to it has been replaced. The lower four bits can be, for example, 0000 (initial value) to indicate that the wire harness has not been replaced, XX01 to indicate that the wire harness of connector A has been replaced, and XX10 to indicate that the wire harness of connector B has been replaced.

[0086] Thus, the lower four bits contain connector information indicating whether or not the wire harness has been replaced for each connector. The lower four bits can also be considered a code that identifies the component. In step S17a, which will be explained later, a connection code is distributed in which the lower four bits are 0000.

[0087] Note that the information indicating whether or not the wire harness has been replaced is not limited to the lower 4 bits. The information indicating whether or not the wire harness has been replaced can be included in part of the connection code. Furthermore, the 2 bits of XX may include information indicating the number of times it has been replaced or information indicating the type of wire harness that was replaced.

[0088] The lower four bits correspond to component information, indicating the component (wire harness). The connection code here can be considered replacement confirmation information that includes component information.

[0089] Here, using Figure 8, we will explain the request and distribution processes for connection codes in the master ECU 100. When the vehicle's ignition switch is turned on, the master ECU 100 starts the flowchart in Figure 8. The flowchart in Figure 8 mainly represents the processes performed by the microcontroller 110.

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

[0091] Then, if the microcontroller 110 receives a connection code whose upper four bits are different from its own connection code, it proceeds to step S12a. In this case, the microcontroller 110 determines that the slave ECU that sent a connection code with different upper four bits has been replaced. In other words, the microcontroller 110 determines that the slave ECU that sent a connection code with different upper four bits is the replaced ECU. It can also be said that the slave ECU that sent a connection code with different upper four bits is the slave ECU that was replaced because it was the cause of an abnormal condition.

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

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

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

[0095] The microcontroller 110 determines whether the lower four bits of the received connection code are 0000. If the microcontroller 110 does not determine that the lower four bits are 0000, it proceeds to step S15a. In this case, the microcontroller 110 determines that the wire harness has been replaced in the slave ECU that sent the connection code whose lower four bits are not 0000. The slave ECU that sent the connection code whose lower four bits are not 0000 is also referred to as the ECU whose wire harness was replaced or the relevant ECU.

[0096] On the other hand, if the microcontroller 110 does not determine that the lower 4 bits are 0000, it proceeds to step S16a. In this case, the microcontroller 110 determines that the wire harness has not been replaced in any of the slave ECUs 201 and 20n.

[0097] The microcontroller 110 may also execute step S14a with respect to its own connection code. In this case, if the microcontroller 110 does not determine that the lower 4 bits are 0000, it proceeds to step S15a. If the microcontroller 110 determines that the lower 4 bits are 0000, it proceeds to step S16a.

[0098] In this way, by having the lower 4 bits described above in the connection code, it is possible to identify the replaced wire harness.

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

[0100] In step S15a, the system stores that the wire harness of the relevant ECU has been replaced (storage unit). If the microcontroller 110 determines that the wire harness has been replaced, it stores the ID of the relevant ECU and the lower four bits associated with it in the memory device 120. In this way, the microcontroller 110 stores the slave ECU that sent a connection code whose lower four bits are not 0000 as the ECU whose wire harness has been replaced.

[0101] Step S16a is the same as step S13. Step S17a is the same as step S14.

[0102] In the second embodiment, the master ECU 100 executes the flowchart shown in Figure 3, similar to the first embodiment. If the microcontroller 110 determines NO in steps S11a and S14a, it determines that a part has been replaced and proceeds to step S21. In step S21, the microcontroller 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, in step S15a, the microcontroller 110 adds the ID of the corresponding ECU stored and the lower four bits and transmits them to the center 10 via the antenna 140. In this way, the microcontroller 110 transmits the ID, the lower four bits, and the diagnostic data as input data for machine learning.

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

[0104] This disclosure is described in accordance with embodiments, but it is understood that this disclosure is not limited to such embodiments or structures. This disclosure also includes various modifications and variations within the scope of equivalents. In addition, while various combinations and forms are shown in this disclosure, other combinations and forms that include one, more, or fewer of those elements also fall within the scope and idea of ​​this disclosure. [Explanation of symbols]

[0105] 10...Center, 11...Microcontroller, 12...Memory device, 13...Communication device, 14...Antenna, 100...Master ECU, 110...Microcontroller, 120...Memory device, 130...Communication device, 140...Antenna, 201...First slave ECU, 211...Microcontroller, 221...Memory device, 231...Communication device, 20n...nth slave ECU, 21n...Microcontroller, 22n...Memory device, 23n...Communication device, 40...Terminal section, 41...First terminal, 42...Second terminal

Claims

1. A diagnostic device mounted in a vehicle along with electrically connected components, capable of acquiring diagnostic information correlated with vehicle malfunctions, A determination unit (S11, S11a) that determines whether or not the aforementioned parts have been replaced, A diagnostic device comprising: a storage unit (S12, S13, S12a, S13a, S15a, S16a) that stores, when it is determined that a replacement has been performed, the part information of the replaced part and the diagnostic information acquired at least before it was determined that a replacement had been performed.

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

3. It is installed in the communication system together with an electronic control unit connected via a communication line, The system comprises a communication device that communicates with the electronic control device via the communication line, and a storage device that stores exchange 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 aforementioned replacement confirmation information includes the aforementioned parts information, The diagnostic device according to claim 3, wherein the determination unit determines that a part has been replaced if the part information of the replacement confirmation information received via the communication device does not match the part information of the replacement confirmation information stored in the storage device, and identifies the replaced part.

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

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

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

Images