Vehicle diagnostic device, vehicle diagnostic system and vehicle diagnostic program

Abstract

A vehicle diagnostic device mounted on a vehicle features: a diagnostic section (9b) configured to perform a diagnosis from a diagnostic target (5, 6) in accordance with a diagnostic scenario defined by a diagnostic application (S1), and a diagnostic scenario determination section (9c) that is configured to determine (S7) whether the diagnostic scenario used by the diagnostic section (9b) for diagnosis is appropriate, where: The diagnostic section (9b) performs a diagnosis in accordance with a diagnostic scenario defined by a new diagnostic application that is different from a current diagnostic application, in response (S12) to the fact that the diagnostic scenario determination section (9c) specifies (S7) that a diagnostic scenario used in the current diagnosis is not appropriate. the diagnostic section (9b) uses a Detailed Diagnostic Application as the new diagnostic application and performs a detailed diagnosis in accordance with a Detailed Diagnostic Scenario defined by the Detailed Diagnostic Application in response (S12) to the fact that a Periodic Diagnostic Application is used as the current diagnostic application, wherein the Periodic Diagnostic Application periodically receives a diagnostic code from the diagnostic target (5, 6) and analyzes the received diagnostic code in order to diagnose it, and the diagnostic scenario determination section (9c) specifies (S7) that a periodic diagnostic scenario defined by the periodic diagnostic application is not appropriate due to a mismatch of treatment for a detected fault, and wherein the diagnostic scenario determination section (9c) compares an operation log from the diagnostic target (5, 6) after the diagnostic section (9b) has performed the detailed diagnosis with a regular operation log and determines (S7) whether the diagnostic scenario used by the diagnostic section (9b) in the diagnosis is appropriate, or The diagnostic scenario determination section (9c) compares diagnostic execution data generated when the diagnostic section (9b) has performed the detailed diagnosis with regular diagnostic execution data and determines whether the diagnostic scenario used by the diagnostic section (9b) in the diagnosis is appropriate.

Description

Technical area

[0001] The present disclosure relates to a vehicle diagnostic apparatus, a vehicle diagnostic system and a vehicle diagnostic program. State of the art

[0002] For example, an electronic control unit that controls an engine or transmission of an automobile can execute a diagnostic application, perform a diagnosis according to a diagnostic scenario defined by the diagnostic application, detect a failure or defect, and treat the detected defect (see JP 2003 - 19 931 A).

[0003] DE 103 19 493 A1 discloses a diagnostic / prediction system for monitoring the wiring of a vehicle, wherein each operating component has a specific target operating state and generates signals. A data acquisition memory in the vehicle stores samples of these signals in a circulating buffer. An analyzer in the vehicle responds to the electrical signals to detect a triggering event indicating at least one potential deviation of an operating component from its target operating state. Upon the occurrence of the event, some samples are sent to a data center, which classifies them according to the target and fault operating states.

[0004] DE 11 2012 001 923 T5 discloses a flowchart for an algorithm for detecting a fault in a vehicle. If the fault is known internally, an existing solution to mitigate the fault is applied. Otherwise, a solution is sought through communication with a server agent and, if available, applied.

[0005] Document DE 10 2017 100 380 A1 discloses a system for enabling relatively robust control of diagnostic test execution in vehicles. A server generates models of the execution of a diagnostic test over time, depending on vehicle operating conditions, from information from one or more vehicles to identify conditions under which successful execution of the diagnostic tests can be expected. As a result, execution messages are generated based on the models and any required conditions. Summary of the invention

[0006] Even if the diagnosis is performed, there may be cases where it is difficult to detect and treat the error, failure, or defect. There may be cases where it is questionable whether the diagnostic scenario used for the diagnosis was appropriate. Therefore, a mechanism for determining whether a diagnostic scenario used for the diagnosis was appropriate and, if not, rerunning the diagnosis according to a new diagnostic scenario may be required.

[0007] It is an object of the present disclosure to provide a vehicle diagnostic apparatus, a vehicle diagnostic system, a vehicle diagnostic, and a vehicle diagnostic program that can perform a diagnosis appropriately by repeatedly performing a diagnosis according to a new diagnostic scenario when a diagnostic scenario used for the diagnosis is not appropriate. This object is achieved by the features of the independent claims. Advantageous further developments emerge from the subclaims.

[0008] According to one aspect of the present disclosure, a diagnosis section performs a diagnosis of a diagnosis target in accordance with a diagnosis scenario defined by a diagnosis application. A diagnosis scenario determination section determines whether the diagnosis scenario used in the diagnosis by the diagnosis section was appropriate. The diagnosis section performs a diagnosis in accordance with a diagnosis scenario defined by a new diagnosis application different from the current diagnosis application in response to the diagnosis scenario determination section specifying that the diagnosis scenario used in the current diagnosis is not appropriate. It may be possible to properly perform the diagnosis by repeatedly performing the diagnosis according to a new diagnosis scenario if the diagnosis scenario used for the diagnosis is not appropriate. Short description of the drawings

[0009] The above and other objects, features, and advantages of the present disclosure will become more apparent from the following detailed description made with reference to the accompanying drawings. In the drawings: is Fig. 1 is a functional block diagram showing an embodiment, is Fig. 2 a diagram showing a database of a diagnostic result, is Fig. 3 a flowchart (part 1) showing a diagnostic process, and is Fig. 4 a flowchart (part 2) illustrating a diagnostic process. Description of embodiments

[0010] An embodiment will be described with reference to the drawings.

[0011] A vehicle diagnostic system 1 includes an electronic control unit (ECU) 2 for vehicle management mounted within a vehicle and a server 3 located in a communication network. The ECU 2 for vehicle management is hereinafter referred to as a vehicle management ECU and corresponds to a vehicle diagnostic apparatus. The vehicle management ECU 2 is connected to a communication bus 4 in the vehicle. The communication bus 4 is connected to the ECUs 5 and 6 (corresponding to diagnosis targets) and an on-board communication device 7. The vehicle management ECU 2 has a function of managing the ECUs 5 and 6. One of the functions is a function of diagnosing the ECUs 5 and 6.

[0012] The communication bus 4 is, for example, a multimedia communication bus, a power train communication bus, a body communication bus, or the like. The communication bus 4 corresponds to, for example, CAN (Controller Area Network, registered trademark), LIN (Local Interconnect Network, registered trademark), CXPI (Clock Extension Peripheral Interface, registered trademark), FlexRay (registered trademark), MOST (Media Oriented Systems Transport, registered trademark), or the like. The ECUs 5 and 6 correspond to, for example, an engine ECU and an internal combustion engine ECU for controlling the engine and the internal combustion engine.Internal combustion engine, a transmission ECU for controlling an automatic transmission, a brake ECU for controlling a brake, a steering ECU for controlling a steering system, a navigation ECU for controlling navigation, an ETC ECU that controls communication with an electronic toll system, a door ECU that controls locking / unlocking of doors, a meter ECU that controls display of meter elements, an air conditioning ECU that controls an air conditioning system, a window ECU that controls opening and closing of windows, or the like. The number of communication buses and the number of ECUs to be managed by the vehicle management ECU 2 are not limited to the illustrated configuration.

[0013] The on-board communication device 7 transmits and receives data to and from the server 3 and a user terminal 8 when the on-board communication device 7 is wirelessly connected to the server 3 and the user-portable user terminal 8 via a wide-area communication network. The user terminal 8 is, for example, a smartphone or a tablet terminal.

[0014] The vehicle management ECU 2 includes a microcomputer 9. The microcomputer 9 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read-Only Memory), and an I / O (Input / Output) port. The microcomputer 9 executes a computer program (including a vehicle diagnostic program) stored in the non-transitory tangible storage medium, performs processing according to the computer program, and controls the overall operation of the vehicle management ECU 2.The microcomputer 9 includes a diagnostic application storage section 9a, a diagnostic section 9b, a diagnostic scenario determination section 9c, a diagnostic application request section 9d, a diagnostic application acquisition section 9e, and a diagnostic result data notification section 9f as functions related to diagnosis obtained by software or the like. Diagnosis includes determining and detecting whether a failure has occurred, analyzing the detected failure, and taking action for the analyzed failure.

[0015] The diagnostic application storage section 9a stores, as the diagnostic applications, a periodic diagnosis application, an examination information collection application, a unique pattern collection application, a follow-up observation application, a detailed diagnosis application, and a cause identification diagnosis application. The periodic diagnosis application periodically receives a diagnostic code from the ECUs 5 and 6 and analyzes the obtained diagnostic code to diagnose it.The investigation information collection application collects investigation information to be used in a case where periodic diagnosis is not appropriate. The unique pattern collection application collects a unique pattern, such as a sudden change in a numerical value. In this case, the numerical value includes, for example, a numerical value specified by a signal acquired from a vehicle, such as an engine speed, a temperature, and a pressure. The follow-up observation application observes the progress after the diagnosis section 9b performs the periodic diagnosis, the detailed diagnosis, and the cause identification diagnosis described later. The detailed diagnosis application diagnoses the details of the detected failure.Defect in a case where the diagnostic section 9b performs periodic diagnosis, but the measure for the detected error, failure, or defect is not adapted (has no compatibility). The cause identification diagnostic application diagnoses an undetected cause identification of the error, failure, or defect in a case where the diagnostic section 9b performs periodic diagnosis, but the error, failure, or defect is not detected.

[0016] In the present embodiment, a configuration in which the diagnostic application storage section 9a is provided within the vehicle management ECU 2 is illustrated. However, the diagnostic application storage section 9a may be provided outside the vehicle management ECU 2. For example, a storage device corresponding to the diagnostic application storage section 9a may be provided in another ECU or a dedicated storage medium connected to the vehicle management ECU 2 via the communication bus 4. Then, the microcomputer 9 can each time acquire a diagnostic application stored in another ECU or a dedicated storage device. Further, a plurality of storage units corresponding to the diagnostic application storage unit 9a may be provided, and the diagnostic applications may be stored distributed throughout the vehicle.

[0017] The diagnostic section 9b executes the diagnostic application stored in the diagnostic application storage section 9a and performs diagnosis of the ECUs 5 and 6 that are diagnosis targets according to a diagnosis scenario defined by the diagnostic application. That is, when the diagnostic section 9b executes the diagnostic application, the diagnostic section 9b transmits and receives data related to the diagnosis to and from the ECUs 5 and 6 to be diagnosed via the communication bus 4 to perform diagnosis of the ECUs 5 and 6.

[0018] The diagnosis scenario determining section 9c determines whether the diagnosis scenario used for diagnosis by the diagnosis section 9b is appropriate. In this case, the diagnosis scenario determining section 9c determines whether the diagnosis scenario is appropriate, for example, by comparing the operation logs of the ECUs 5 and 6 after the diagnosis unit 9b performs the diagnosis with a predetermined regular operation log, by comparing the diagnosis execution data generated at the time the diagnosis section 9b performs the diagnosis with predetermined regular diagnosis execution data, by determining a predetermined operation by the user after the diagnosis section 9b performs the diagnosis, or the like. The predetermined operationFor example, user operation corresponds to a case where the user operates a "matching key" in the user terminal 8 by determining that the diagnosis scenario is matched, and a case where the user operates an "unmatching key" by determining that the diagnosis scenario is not matched.

[0019] The diagnosis scenario determining section 9c quantifies the degree of agreement between the operation logs of the ECUs 5 and 6 after the diagnosis section 9b performs the diagnosis and a regular operation log, and identifies the diagnosis scenario as appropriate when the value indicating the degree of agreement is within a predetermined range. Or, if the numerical value indicating the degree of agreement is outside the predetermined range, the diagnosis scenario is determined as inappropriate. The diagnosis scenario determining section 9c quantifies, for example, the degree of agreement between the diagnosis execution data generated when the diagnosis section 9b performs the diagnosis and regular diagnosis execution data.If the numerical value indicating the degree of matching is within a predetermined range, the diagnosis scenario determining section 9c specifies that the diagnosis scenario is matching. Or, if the numerical value indicating the degree of matching is outside the predetermined range, the diagnosis scenario determining section 9c specifies that the diagnosis scenario is not matching. For example, in the case of a configuration in which the user determines whether the diagnosis result is normal and the user operates the user terminal 8, the diagnosis scenario determining section 9c specifies that the diagnosis scenario is matching in response to the user determining that the diagnosis scenario is matching and the user operating the user terminal 8, and the on-board communication device 7 receiving a matching confirmation signal transmitted from the user terminal 8.On the other hand, if the user determines that the diagnosis scenario is inappropriate, and the user operates the user terminal 8, and the on-board communication device 7 receives an inappropriate confirmation signal transmitted from the user terminal 8, it is determined that the diagnosis scenario is inappropriate. As a case where the user determines whether the diagnosis result is normal, for example, it is assumed that the user determines that the diagnosis result is normal when the user does not feel uncomfortable with the diagnosis result, and that the user determines that the diagnosis result is abnormal when the user feels any discomfort.

[0020] For example, when a diagnostic application request event occurs due to execution of an instruction from a vehicle diagnostic program, user operation, self-determination, or the like, the diagnostic application request section 9d transmits a diagnostic application request command to the onboard communication device 7 via the communication bus 4. By transmitting, the diagnostic application request signal is transmitted from the onboard communication device 7 to the server 3, and the diagnostic application is requested from the server 3. When the diagnostic application transmitted from the server 3 is received by the onboard communication device 7 and the diagnostic application is received from the onboard device 7 via the communication bus 4, the diagnostic application acquisition section 9e obtains the diagnostic application from the server 3.The diagnosis result data notification section 9f transmits a diagnosis result data notification command to the on-board communication device 7 via the communication bus 4. Accordingly, the diagnosis result data notification section 9f causes the on-board communication device 7 to transmit the diagnosis result data containing the diagnosis result to the server 3 or the user terminal 8, and notifies the server 3 or the user terminal 8 of the diagnosis result data.

[0021] The server 3 includes a microcomputer 10 and a diagnosis result database 11. The microcomputer 10 includes a CPU, a RAM, a ROM, an I / O port, and the like. The microcomputer 10 executes a computer program stored in a non-transitory tangible storage medium, performs processing according to the computer program, and controls the overall operation of the server 3. The microcomputer 10 includes a diagnosis application storage section 10a and a data management section 10b as functions related to diagnosis realized by software or the like.

[0022] The diagnostic application storage section 10a stores a follow-up observation application, a detailed diagnosis application, and a cause identification diagnosis application. When the diagnostic application request signal transmitted from the on-board communication device 7 is received, the microcomputer 10 transmits the diagnostic application specified by the diagnostic application request signal to the on-board communication device 7. Among the diagnostic applications stored in the diagnostic application storage section 9a, Fig. 1, the follow-up observation application, the detailed diagnosis application, and the cause identification diagnosis application may not be included in the manufacturing stage of the vehicle management ECU 2, and may be transferred from the server 3 to the vehicle management ECU 2 after shipment of the product. Alternatively, the follow-up observation application, the detailed diagnosis application, and the cause identification diagnosis application may be included in the manufacturing stage of the vehicle management ECU 2.

[0023] Similarly, if the server 3 is configured to store the periodic diagnosis application, the examination information collection application, and the unique pattern collection application, the server 3 may include the periodic diagnosis application, the examination information collection application, and the unique pattern collection application stored in the diagnosis application storage section 9a shown in Fig. 1, are stored, which do not have to be included in the production stage of the vehicle management ECU 2 and which can be transferred from the server 3 to the vehicle management ECU 2 after the product has been shipped, transported, or shipped, or which can be installed in the production stage of the management ECU 2. Which diagnostic application is included in the production stage of the vehicle management ECU 2 or whether it is managed by the server 3 can be designed in any way. For example, a diagnostic application that is useful for a diagnosis target based on past results can be included in the production stage of the vehicle management ECU 2. Since the storage capacity of the diagnostic application storage section 9a is finite,is limited, a diagnostic application that has been useful for a diagnostic target based on past results may be given high priority, and the high-priority diagnostic application may be included in the manufacturing stage of the vehicle management ECU 2.

[0024] Upon receiving the diagnosis result data transmitted from the on-board communication device 7, the data management section 10b stores the diagnosis result specified by the diagnosis result data in the diagnosis result database 11 as a history. As shown in Fig. 2, the diagnosis result data transmitted from the on-board communication device 7 to the server 3 includes a vehicle ID capable of specifying a vehicle type, a quality, a manufacturing time, a diagnosis time capable of specifying the time at which the diagnosis was performed in the past, a diagnosis application used in the diagnosis, and information about a diagnosis result performed according to the diagnosis scenario defined by the diagnosis application.

[0025] Upon receiving the diagnostic result data transmitted from the on-board communication device 7, the user terminal 8 displays and outputs a diagnostic result specified by the diagnostic result data. Displaying and outputting the diagnostic result by the user terminal 8 allows the user to determine whether the diagnostic scenario is appropriate, as described above. The user terminal 8 can display the status, such as "before diagnosis," "during diagnosis," or "after diagnosis," by receiving status information, for example, before, during, or after diagnosis from the on-board communication device 7.

[0026] Next, the functionality of the above configuration will be explained with reference to Fig. 3 and Fig.4. Here, the microcomputer 9 uses the periodic diagnosis application as a primary diagnosis application to be executed first, and executes a secondary diagnosis when the primary diagnosis scenario defined by the primary diagnosis application is inappropriate. A case where the detailed diagnosis application or the cause identification diagnosis application is used as the secondary diagnosis application will be described.

[0027] In the vehicle management ECU 2, when the diagnosis process is started, the microprocessor 9 executes the periodic diagnosis application and performs a periodic diagnosis according to a periodic diagnosis scenario defined by the periodic diagnosis application (S1, corresponding to a current diagnosis procedure). When the microcomputer 9 performs the periodic diagnosis, the microcomputer 9 causes the on-board communication device 7 to transmit the diagnosis result data containing the periodic diagnosis result to the server 3 or the user terminal 8, and the server 3 or the user terminal 8 notifies the diagnosis result data of the periodic diagnosis. The microcomputer 9 determines whether a failure has been detected in the result of the periodic diagnosis based on the periodic diagnosis (S2). When the microcomputer 9 determines that the failureIf a defect has been detected in the result of the periodic diagnosis (S2: YES), the microcomputer 9 analyzes the detected error or failure or defect (S3). The microcomputer 9 determines whether a treatment method has been specified for the error or failure or defect (S4). The microcomputer 9 can analyze the detected defect alone or analyze it in cooperation with the server 3. The microcomputer 9 can cause the server 3 to analyze the error or failure or defect alone by transmitting the content of the error or failure or defect to the server 3.

[0028] If the microcomputer 9 determines that the treatment method for the failure has been identified by analyzing the failure (S4: YES), the microcomputer 9 performs treatment for the failure according to the identified treatment method (S5). The microcomputer 9 observes the progress after performing the treatment for the failure (S6) and determines whether the periodic diagnosis scenario is appropriate (S7, corresponding to a diagnosis scenario determination procedure). In this case, the microcomputer 9 determines whether the periodic diagnosis scenario is appropriate by comparing the operation logs of the ECUs 5 and 6 after performing the periodic diagnosis with a predetermined regular operation log.a predetermined regular operation record, by comparing the diagnosis execution data generated at the time of performing the periodic diagnosis with predetermined regular diagnosis execution data, by determining a predetermined operation by the user after performing the periodic diagnosis, or the like.

[0029] The microcomputer 9 determines that the periodic diagnosis scenario was appropriate (S7: YES) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the periodic diagnosis and the regular operation log being within a certain range, the numerical value indicating the degree of agreement between the diagnosis execution data generated when the periodic diagnosis is performed and the regular diagnosis execution data being within a certain range, the on-board communication device 7 receiving the appropriate confirmation signal transmitted from the user terminal 8 after the user determines that the periodic diagnosis scenario was appropriate to operate the user terminal 8, or the like.Diagnostic processing ends.

[0030] The microcomputer 9 determines that the periodic diagnosis scenario is not appropriate (S7: NO) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the periodic diagnosis and the regular operation log being outside the specified range, the numerical value indicating the degree of agreement between the diagnosis execution data generated when performing the periodic diagnosis and the regular diagnosis execution data being outside the predetermined range, the on-board communication device 7 receiving the inappropriate confirmation signal transmitted from the user terminal 8 after the user determines that the periodic diagnosis scenario is not appropriate and operates the user terminal 8, or the like.In this case, it is determined whether the error, failure or defect can be analyzed again (S8).

[0031] If the microcomputer 9 determines that the error or failure or defect can be analyzed again (S8: YES), the microcomputer 9 analyzes the error or failure or defect again (S9). The microcomputer 9 determines again whether the treatment method for the error or failure or defect is specified (S10). If the microcomputer 9 determines that the error or failure or defect cannot be analyzed again (S8: NO), the microcomputer 9 specifies that the detected error or failure or defect is to be treated by repair at a point of sale (S11), and this ends the diagnosis processing. If the microcomputer 9 determines that the treatment method for the error or failure or defect has not been specified (S4: NO), the microcomputer 9 also analyzes the error or failure or defect again (S9). In this case, the microcomputer 9 determines again whether the treatment method for the error or failure or defect is specified.Failure or defect has been specified (S10).

[0032] If the microcomputer 9 determines that the treatment method for the failure has been specified by re-analyzing the failure (S10: YES), the microcomputer 9 executes the detailed diagnosis application and performs the detailed diagnosis according to the detailed diagnosis scenario defined in the detailed diagnosis application (S12, according to a new diagnosis procedure). In this case, if the microcomputer 9 saves the detailed diagnosis application, the microcomputer 9 executes the saved detailed diagnosis application. If a plurality of detailed diagnosis applications are saved, the microcomputer 9 selects an optimal detailed diagnosis application from the plurality of detailed diagnosis applications according to the specified treatment method and executes the selected detailed diagnosis application.If the microcomputer 9 does not store the detailed diagnosis application, the microcomputer 9 requests the detailed diagnosis application from the server 3 by transmitting a diagnosis application request signal from the on-board communication device 7 to the server 3.

[0033] When the diagnostic application request signal is received, the server 3 searches the diagnostic result database 11 using the diagnostic result data received from the transmission source of the diagnostic application request signal and selects an optimal diagnostic application from the plurality of detailed diagnostic applications. For example, if the detailed diagnostic application differs depending on the vehicle type, quality, production time, or the like, the server 3 specifies the vehicle type, quality, production time, or the like of the transmission source of the diagnostic application request signal from the vehicle ID. Then, the server 3 specifies a detailed diagnostic application to be transmitted to a vehicle similar to the transmission source of the diagnostic application request signal and the vehicle whose diagnosis result is normal.The server 3 transmits the specified detailed diagnosis application. For example, the server 3 may acquire examination information from the vehicle management ECU 2, analyze the acquired examination information to generate a detailed diagnosis application, and select the generated detailed diagnosis application as the optimal detailed diagnosis application.

[0034] When the on-board communication device 7 receives the detailed diagnosis application transmitted from the server 3 and the diagnosis application is received from the on-board communication device 7 through the communication bus 4, the microcomputer 9 receives the detailed diagnosis application transmitted from the server 3 and executes the acquired detailed diagnosis application.

[0035] The microcomputer 9 executes the periodic diagnosis application as the primary diagnosis application. If the microcomputer 9 specifies that the periodic diagnosis scenario is not suitable due to a mismatch of treatment for the detected error or failure or defect, and specifies the treatment method for the error or failure or defect, the microcomputer 9 executes the detailed diagnosis application as the secondary diagnosis application to perform the detailed diagnosis.

[0036] When the detailed diagnosis application is executed and the detailed diagnosis is performed, the microcomputer 9 observes the progress after performing the detailed diagnosis (S13) and determines whether the detailed diagnosis scenario is appropriate (S14). In this case, the microcomputer 9 determines whether the detailed diagnosis scenario is appropriate by comparing the operation logs of the ECUs 5 and 6 after performing the detailed diagnosis with a predetermined regular operation log, by comparing the diagnosis execution data generated at the time of performing the detailed diagnosis with predetermined regular diagnosis execution data, by determining the predetermined operation by the user after performing the detailed diagnosis, or the like.

[0037] The microcomputer 9 determines that the detailed diagnosis scenario is appropriate (S14: YES) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the detailed diagnosis and the regular operation log.of the regular operation record is within the predetermined range, that the numerical value indicating the degree of match between the diagnosis execution data generated at the time of performing the detailed diagnosis and the regular diagnosis execution data is within the predetermined range, that the on-board communication device 7 receives the matching confirmation signal transmitted from the user terminal 8 after the user determines that the detailed diagnosis scenario is matching and operates the user terminal 8, or the like, and ends the diagnosis processing.

[0038] The microcomputer 9 determines that the detailed diagnosis scenario is not suitable (S14: NO) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the detailed diagnosis and the regular operation log being outside the predetermined range, the numerical value indicating the degree of agreement between the diagnosis execution data generated at the time of performing the detailed diagnosis and the regular diagnosis execution data being outside the predetermined range, the on-board communication device 7 receiving an inappropriate confirmation signal transmitted from the user terminal 8 after the user determines that the detailed diagnosis scenario is not suitable and operates the user terminal 8, or the like.In this case, it is determined whether the error or failure or defect can be re-analyzed according to the result of the follow-up observation (S15).

[0039] If the microcomputer 9 determines that the failure can be reanalyzed (S15: YES), the microcomputer 9 returns to step S9 and repeatedly executes the processing of step S9 and subsequent steps. In this case, the microcomputer 9 executes a new detailed diagnosis application, different from the previous detailed diagnosis application, to diagnose the detailed diagnosis. If the microcomputer 9 determines that the failure cannot be reanalyzed (S15: NO), the microcomputer 9 specifies that the detected failure should be handled by a sales outlet repair (S11), and terminates the diagnosis processing.

[0040] If the microcomputer 9 determines that no failure has been detected in the periodic diagnosis result by the periodic diagnosis (S2: NO), the microcomputer 9 determines whether the user has performed a diagnosis instruction operation for the cause identification diagnosis (S16). If the microcomputer 9 determines that the user has performed the diagnosis instruction operation for the cause identification diagnosis (S16: YES), the microcomputer 9 transmits the diagnosis application request signal from the on-board communication device 7 to the server 3 according to the content of the diagnosis instruction operation, and requests that the cause identification diagnosis application be performed at the server 3 (S17).

[0041] Upon receiving the diagnostic application request signal, the server 3 searches the diagnostic result database 11 using the diagnostic result data received from the transmission source of the diagnostic application request signal and selects the optimal diagnostic application from the plurality of cause identification diagnostic applications. For example, if the cause identification diagnostic application differs depending on the vehicle type, quality, production time, or the like, the server 3 specifies the vehicle type, quality, production time, or the like from the transmission source of the diagnostic application request signal from the vehicle ID.Then, the server 3 specifies the cause-identification diagnostic application to be transmitted to a vehicle similar to the transmission source of the diagnosis application request signal and the vehicle whose diagnosis result is normal, and transmits the specified cause-identification diagnostic application to the vehicle. The server 3 can select an optimal cause-identification diagnostic application using the diagnosis instruction operation specified by the diagnosis application request signal. The server 3 can select an optimal cause-identification diagnostic application through a procedure other than searching the diagnosis result database 11. That is, the server 3 can search the diagnosis result database 11 as a method for selecting an optimal cause-identification diagnostic application.

[0042] When the on-board communication device 7 receives the cause identification diagnosis application transmitted from the server 3 and the diagnosis application is received from the on-board communication device 7 through the communication bus 4, the microcomputer 9 acquires the cause identification diagnosis application from the server 3, executes the acquired cause identification diagnosis application, and performs the cause identification diagnosis according to the cause identification diagnosis scenario defined by the cause identification diagnosis application (S18, corresponding to a new diagnosis procedure).

[0043] The microcomputer 9 executes the cause identification diagnosis application as the secondary application and executes the cause identification diagnosis in a case where the microcomputer 9 executes the periodic diagnosis application as the primary diagnosis application to perform the periodic diagnosis, but the microcomputer 9 specifies that the periodic diagnosis scenario is not appropriate due to non-detection of the failure and specifies that the user has performed the diagnosis instruction operation.

[0044] The microcomputer 9 monitors the progress after the execution of the cause identification diagnosis (S19) and determines whether the cause identification diagnosis scenario is appropriate (S20). In this case, the microcomputer 9 determines whether the cause identification diagnosis scenario is appropriate by comparing the operation logs of the ECUs 5 and 6 after performing the cause identification diagnosis with a predetermined regular operation log, by comparing the diagnosis execution data generated at the time of performing the cause identification diagnosis with predetermined regular diagnosis execution data, by determining a predetermined operation by the user after performing the cause identification diagnosis, or the like.

[0045] The microcomputer 9 determines that the cause identification diagnosis scenario is appropriate (S20: YES) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the cause identification diagnosis and the regular operation log being within the predetermined range, the numerical value indicating the degree of agreement between the diagnosis execution data generated at the time of performing the cause identification diagnosis and the regular diagnosis execution data being within the predetermined range, the on-board communication device 7 receiving the appropriate confirmation signal transmitted from the user terminal 8 after the user determines that the cause identification diagnosis scenario is appropriate and operates the user terminal 8, or the like, and ends the diagnosis processing.

[0046] The microcomputer 9 determines that the cause identification diagnosis scenario is not appropriate (S20: NO) in response to the numerical value indicating the degree of agreement between the operation logs of the ECUs 5 and 6 after performing the cause identification diagnosis and the regular log being outside a predetermined range, the numerical value indicating the degree of agreement between the diagnosis execution data generated at the time of performing the cause identification diagnosis and the regular diagnosis execution data being outside a predetermined range, the on-board communication device 7 receiving an inappropriate confirmation signal transmitted from the user terminal 8 after the user determines that the cause identification diagnosis scenario is not appropriate and operates the user terminal 8, or the like.In this case, the microcomputer 9 specifies that non-detection of the error or failure or defect is to be handled by repair at a point of sale (S11), and terminates the diagnosis processing.

[0047] If the microcomputer 9 determines that the user is not performing the diagnosis instruction operation for cause identification diagnosis (S16: NO), the microcomputer 9 determines whether the unique pattern has been detected (S21). If the microcomputer 9 determines that the unique pattern has been detected (S21: YES), the microcomputer 9 executes the unique pattern collection application and performs the unique pattern collection according to the unique pattern collection scenario defined by the unique pattern collection application (S22). The microcomputer 9 analyzes the collected unique pattern (S23) and determines whether a treatment method for the unique pattern has been specified (S24). The microcomputer 9 can analyze the collected strange pattern alone or in cooperation with the server 3.

[0048] If the microcomputer 9 determines that the treatment method for the unique pattern has been specified (S24: YES), the microcomputer 9 executes step S18 and subsequent steps according to the treatment method for the specified unique pattern. If the microcomputer 9 determines that the treatment method for the unique pattern has not been specified (S24: NO), the microcomputer 9 specifies that non-detection of the failure will be treated by repair at a point of sale (S11), and terminates the diagnosis processing.

[0049] As described above, the microcomputer 9 executes the cause identification diagnosis application as a secondary diagnosis application to perform the cause identification diagnosis in response to the microcomputer 9 executing the periodic diagnosis application as the primary diagnosis application to perform the periodic diagnosis, specifies that the periodic diagnosis scenario is not appropriate due to non-detection of the failure, detects the unique pattern, and specifies the treatment method for the unique pattern.

[0050] If the microcomputer 9 determines that the unique pattern has not been detected (S21: NO), the microcomputer 9 determines whether the elapsed time from the start of the periodic diagnosis has reached a predetermined time (S25). If the microcomputer 9 determines that the elapsed time from the start of the periodic diagnosis has not reached the predetermined time (S25: NO), the microcomputer 9 again selects the unique pattern collection application (S26), returns to step S2, and repeats the processing of step S2 and the subsequent steps. If the microcomputer 9 determines that the elapsed time from the start of the periodic diagnosis has reached the predetermined time (S25: YES), the microcomputer 9 again selects the periodic diagnosis application (S27), returns to the above-described step S1, and repeats the processing of step S1 and the subsequent steps.

[0051] The embodiment described above can provide effects as follows.

[0052] In the vehicle management ECU 2, in a case where the periodic diagnosis application is executed as the primary diagnosis application to perform periodic diagnosis and it is determined that the periodic diagnosis scenario is not appropriate, the detailed diagnosis application is executed as the secondary diagnosis application to perform detailed diagnosis, or the cause identification diagnosis application is executed as the secondary diagnosis application to perform cause identification diagnosis. It may be possible to properly perform diagnosis by repeatedly performing diagnosis according to a new detailed diagnosis scenario or a new cause identification diagnosis scenario in a case where the periodic diagnosis scenario used for periodic diagnosis is not appropriate.

[0053] It may be possible to properly handle a case where a treatment for the detected error, failure, or defect is not used by running the detailed diagnosis application to perform detailed diagnosis. It may be possible to properly handle a case where the error, failure, or defect is not detected by running the cause identification diagnosis application to perform cause identification diagnosis.

[0054] Diagnosis is performed according to the diagnosis scenario defined by the diagnosis application stored in the diagnosis application storage section 9a. For example, a diagnosis application that is used relatively frequently may be stored in advance in the diagnosis application storage section 9a. This may make it possible to omit a procedure for acquiring the diagnosis application that is used relatively frequently by the server 3. Even if a malfunction occurs in data communication with the server 3, it may be possible to cope with the situation.

[0055] The diagnostic application requests the server 3, and the diagnosis is performed according to the diagnostic scenario defined by the diagnostic application acquired from the server 3. For example, it may be possible to effectively utilize the storage area of ​​the diagnostic application storage section 9a by obtaining a diagnostic application that is relatively rarely used from the server 3 without being stored in the diagnostic application storage section 9a in advance.

[0056] The diagnosis section 9b can perform the diagnosis according to the diagnosis scenario defined by the diagnosis application stored in the server 3 by performing data communication with the server 3 without acquiring the diagnosis application from the server 3.

[0057] The operation logs of ECUs 5 and 6 after performing the diagnosis are compared with the regular operation logs to determine whether the diagnostic scenario used for the diagnosis is appropriate. For example, by determining the degree of agreement between the operation logs of ECUs 5 and 6 after performing the diagnosis and the regular operation log, it may be possible to easily determine whether the diagnostic scenario used for the diagnosis is appropriate without requiring user input.

[0058] The diagnostic execution data generated at the time of performing the diagnosis is compared with the regular diagnostic execution data to determine whether the diagnostic scenario used for the diagnosis is appropriate. For example, by determining the degree of correspondence between the diagnostic execution data generated at the time of performing the diagnosis and the regular diagnostic execution data, it may be possible to easily determine whether the diagnostic scenario used for the diagnosis is appropriate without requiring the user to make a determination.

[0059] The predetermined operation or actuation by the user after performing the diagnosis is determined to determine whether the diagnostic scenario used for the diagnosis is appropriate. The user can determine whether the diagnostic scenario used for the diagnosis is appropriate.

[0060] An authentication technique may be used when receiving a diagnostic application from the server 3. Using the authentication technology, it may be possible to execute a formal diagnostic application to perform the diagnosis.

[0061] The diagnostic result database can store data that contains information in addition to the vehicle ID, the diagnostic time, the diagnostic application, and the diagnostic result.

[0062] By using a plurality of servers each managed by a plurality of management organizations instead of using one server 3 managed by one management organization, it may be possible to improve diagnosis accuracy and promote competitiveness of developing diagnosis applications.

[0063] The evaluation by rechecking can be used for a diagnostic application managed by server 3. Thus, the evaluation by rechecking can be used as a selection criterion when selecting a diagnostic application.

[0064] Before using the diagnostic application or before obtaining the diagnostic application from the server 3, the user may be able to confirm with the user terminal 8 or the like that the diagnostic application is being used or obtained from the server 3.

[0065] In the server 3, a diagnostic result from one vehicle can be extended to other vehicles of the same vehicle type. In other words, information about the accuracy of the diagnosis in a vehicle, information about the diagnostic application being used, and the like can be extended to other vehicles of the same type.

Claims

[1] Vehicle diagnostic apparatus mounted on a vehicle, comprising: a diagnostic section (9b) configured to perform a diagnosis of a diagnostic target (5, 6) in accordance with a diagnostic scenario defined by a diagnostic application (S1), and a diagnosis scenario determining section (9c) configured to determine (S7) whether the diagnosis scenario used by the diagnosis section (9b) for the diagnosis is appropriate, where: the diagnosis section (9b) performs a diagnosis in accordance with a diagnosis scenario defined by a new diagnosis application that is different from a current diagnosis application in response to the diagnosis scenario determination section (9c) specifying (S7) that a diagnosis scenario used in the current diagnosis is not appropriate, the diagnosis section (9b) uses a detailed diagnosis application as the new diagnosis application and performs a detailed diagnosis in accordance with a detailed diagnosis scenario defined by the detailed diagnosis application in response (S12) to a periodic diagnosis application being used as the current diagnosis application, wherein the periodic diagnosis application periodically receives a diagnostic code from the diagnosis target (5, 6) and analyzes the received diagnostic code to diagnose it, and the diagnosis scenario determining section (9c) specifies (S7) that a periodic diagnosis scenario defined by the periodic diagnosis application is not suitable due to a mismatch of a treatment for a detected error, and wherein the diagnosis scenario determination section (9c) compares an operation log from the diagnosis target (5, 6) after the diagnosis section (9b) has performed the detailed diagnosis with a regular operation log and determines (S7) whether the diagnosis scenario used by the diagnosis section (9b) in the diagnosis is appropriate, or the diagnosis scenario determining section (9c) compares diagnosis execution data generated when the diagnosis section (9b) has performed the detailed diagnosis with regular diagnosis execution data and determines whether the diagnosis scenario used by the diagnosis section (9b) in the diagnosis is appropriate. [2] A vehicle diagnostic apparatus according to claim 1, wherein: the diagnosis section uses a cause identification diagnosis application as the new diagnosis application and performs cause identification diagnosis in accordance with a cause identification diagnosis scenario defined by the cause identification diagnosis application in response to a periodic diagnosis application being used as the current diagnosis application and the diagnosis scenario determination section specifying that a periodic diagnosis scenario defined by the periodic diagnosis application is not appropriate due to non-detection of a fault. [3] A vehicle diagnostic apparatus according to claim 1 or 2, further comprising: a diagnostic application storage section (9a) configured to store in advance a diagnostic application that is used relatively frequently, where: the diagnosis section performs the diagnosis of the diagnosis target in accordance with the diagnosis scenario defined by the diagnosis application stored in the diagnosis application storage section. [4] A vehicle diagnostic apparatus according to claim 1 or 2, further comprising: a diagnostic application request section (9d) configured to request a diagnostic application that is used relatively rarely without being stored in advance in the diagnostic application storage section (9a) from a server (3), and a diagnostic application acquiring section (9e) configured to acquire the diagnostic application, which is used relatively rarely, from the server (3) without being stored in advance in the diagnostic application storage section (9a), where: the diagnosis section performs the diagnosis of the diagnosis target in accordance with the diagnosis scenario defined by the diagnosis application obtained from the server by the diagnosis application. [5] A vehicle diagnostic apparatus according to claim 4, further comprising: a diagnostic result data notification section (9f) configured to notify the server of diagnostic result data containing a diagnostic result by the diagnostic section, where: the diagnostic application acquiring section acquires a diagnostic application selected by the server in accordance with the diagnosis result data from a plurality of diagnostic applications stored in the server. [6] A vehicle diagnostic apparatus according to any one of claims 1 to 5, wherein: the diagnosis scenario determination section determines a predetermined operation by a user after the diagnosis section performs the diagnosis, and determines whether the diagnosis scenario used by the diagnosis section in the diagnosis is appropriate. [7] Vehicle diagnostic system comprising: a vehicle diagnostic apparatus mounted on a vehicle and containing: a diagnostic section (9b) configured to perform a diagnosis of a diagnostic target (5, 6) in accordance with a diagnostic scenario defined by a diagnostic application (S1), and a diagnosis scenario determining section (9c) configured to determine (S7) whether the diagnosis scenario used by the diagnosis section (9b) for the diagnosis is appropriate, wherein the diagnosis section (9b) performs a diagnosis in accordance with a diagnosis scenario defined by a new diagnosis application that is different from a current diagnosis application in response to the diagnosis scenario determination section (9c) specifying (S7) that a diagnosis scenario used in the current diagnosis is not appropriate, and a server (3) configured to transmit the diagnostic application to the vehicle diagnostic device, wherein the diagnosis section (9b) uses a detailed diagnosis application as the new diagnosis application and performs a detailed diagnosis in accordance with a detailed diagnosis scenario defined by the detailed diagnosis application in response (S12) to a periodic diagnosis application being used as the current diagnosis application, wherein the periodic diagnosis application periodically receives a diagnostic code from the diagnosis target (5, 6) and analyzes the received diagnostic code to diagnose it, and the diagnosis scenario determining section (9c) specifies (S7) that a periodic diagnosis scenario defined by the periodic diagnosis application is not suitable due to a mismatch of a treatment for a detected error, and wherein the diagnosis scenario determination section (9c) compares an operation log from the diagnosis target (5, 6) after the diagnosis section (9b) has performed the detailed diagnosis with a regular operation log and determines (S7) whether the diagnosis scenario used by the diagnosis section (9b) in the diagnosis is appropriate, or the diagnosis scenario determining section (9c) compares diagnosis execution data generated when the diagnosis section (9b) has performed the detailed diagnosis with regular diagnosis execution data and determines whether the diagnosis scenario used by the diagnosis section (9b) in the diagnosis is appropriate. [8] Vehicle diagnostic system according to claim 7, wherein: The vehicle diagnostic device contains: a diagnostic application request section (9d) configured to request a diagnostic application from the server, a diagnostic application obtaining section (9e) configured to obtain the diagnostic application from the server, and a diagnostic result data notification section (9f) configured to notify the server of diagnostic result data containing a diagnostic result by the diagnostic section, the server stores a variety of diagnostic applications, wherein the server selects any one of the diagnostic applications in accordance with the diagnostic result data from the plurality of diagnostic applications in response to the vehicle diagnostic apparatus notifying the diagnostic result data, and wherein the server transmits the selected diagnostic application to the vehicle diagnostic device. [9] Vehicle diagnostic program that causes a microcomputer to be a diagnostic target (5, 6) to perform: a current diagnostic procedure that performs a diagnosis of the diagnostic target (5, 6) in accordance with a diagnostic scenario defined by a current diagnostic application (S1), a diagnosis scenario determination procedure that determines (S7) whether the diagnosis scenario is suitable by the current diagnosis procedure, and a new diagnostic procedure that performs a diagnosis in accordance with a diagnostic scenario defined by a new diagnostic scenario that is different from the current diagnostic application in response (S12) to the diagnostic scenario not being suitable by the current diagnostic procedure, Using a detailed diagnosis application as the new diagnosis application and performing (S12) a detailed diagnosis in accordance with a detailed diagnosis scenario defined by the detailed diagnosis application in response to a periodic diagnosis application being used as the current diagnosis application, wherein the periodic diagnosis application periodically receives a diagnostic code from the diagnosis target (5, 6) and analyzes the received diagnostic code to diagnose it, Specifying (S7) that a periodic diagnosis scenario defined by the periodic diagnosis application is not appropriate due to a mismatch of a treatment for a detected error, and Comparing an operation log of the diagnosis target (5, 6) after performing the detailed diagnosis with a regular operation log and determining (S7) whether the diagnosis scenario used in the diagnosis is appropriate, or Comparing diagnostic execution data generated after performing the detailed diagnosis with regular diagnostic execution data and determining whether the diagnostic scenario used in the diagnosis is appropriate. [10] A non-transitory computer-readable storage medium storing the vehicle diagnostic program according to claim 9.

Images