Abnormal Sound Diagnostic System

Abstract

To allow a user to recognize that reliability of a diagnostic result of abnormal noise is high.SOLUTION: An abnormal noise diagnosis system includes an output unit that identifies a cause component being a cause of abnormal noise from sound of a detected diagnosis vehicle, extracts past abnormal noise data including abnormal generation component information identical to information on the identified cause component, and abnormal noise vehicle information identical or similar to vehicle information acquired in a vehicle information acquisition unit from an abnormal noise database stored in a data storage unit, and outputs the information on the cause component, and at least one of the abnormal noise vehicle information and data for the sound including abnormal noise included in the extracted past abnormal noise data.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an abnormal sound diagnosis system, and more particularly to an abnormal sound diagnosis system that diagnoses abnormal sounds generated in a vehicle. [Background technology]

[0002] Conventionally, as this type of abnormal sound diagnosis system, one that diagnoses abnormal sounds generated in a vehicle has been proposed (for example, see Patent Document 1). In this system, data on sounds generated from the vehicle is transmitted to an AI (artificial intelligence) server via a network. The AI ​​server diagnoses the cause of the abnormal sound based on the received sound data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] US Patent Application Publication No. 2019 / 0114849 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above-mentioned abnormal sound diagnosis system, the user of the vehicle being diagnosed (for example, the staff of the repair shop where the vehicle being diagnosed is taken) often does not understand the process of diagnosing the cause of the abnormal sound by the AI ​​server. Therefore, the user may perceive the AI ​​server's diagnosis result of the cause of the abnormal sound as low in credibility.

[0005] The main objective of the abnormal sound diagnosis system of the present invention is to make the user recognize that the abnormal sound diagnosis results are highly reliable. [Means for solving the problem]

[0006] The abnormal sound diagnosis system of the present invention employs the following means to achieve the above-mentioned main object.

[0007] The abnormal sound diagnosis system of the present invention comprises: An abnormal sound diagnosis system for diagnosing abnormal sounds occurring in a vehicle, comprising: a data storage unit that stores in an abnormal sound database abnormal sound data that associates abnormal sound generating part information as information on parts that caused abnormal sounds in abnormal sound generating vehicles that have generated abnormal sounds in the past, abnormal sound vehicle information as vehicle information on the abnormal sound generating vehicles, and sound data including abnormal sounds generated in the abnormal sound generating vehicles; an abnormal sound detection unit that detects sounds including abnormal sounds generated in a vehicle to be diagnosed; a vehicle information acquisition unit that acquires vehicle information regarding the vehicle to be diagnosed; an output unit which identifies a causative part causing an abnormal sound from the detected sound of the diagnosed vehicle, extracts from the abnormal sound database stored in the data storage unit past abnormal sound data which includes the abnormal sound generating part information identical to the identified causative part information and which includes the abnormal sound vehicle information which is identical or similar to the vehicle information acquired by the vehicle information acquisition unit, and outputs at least one of the abnormal sound vehicle information and the sound data including an abnormal sound contained in the extracted past abnormal sound data together with the causative part information; The gist of the invention is to provide the following:

[0008] In the abnormal sound diagnosis system of the present invention, the data storage unit stores abnormal sound data in an abnormal sound database that associates abnormal sound generating part information as information on a part that caused an abnormal sound in an abnormal sound generating vehicle in the past, abnormal sound vehicle information as vehicle information on the abnormal sound generating vehicle, and sound including the abnormal sound generated in the abnormal sound generating vehicle. The abnormal sound detection unit detects sound including the abnormal sound generated in the diagnosis vehicle that is the target for diagnosing abnormal sounds. The vehicle information acquisition unit acquires vehicle information related to the diagnosis vehicle. The output unit identifies the causative part that is causing the abnormal sound from the detected sound of the diagnosis vehicle, extracts past abnormal sound data from the abnormal sound database stored in the data storage unit that includes abnormal sound generating part information identical to the identified information on the causative part and includes abnormal sound vehicle information identical or similar to the vehicle information acquired by the vehicle information acquisition unit, and outputs at least one of the abnormal sound vehicle information and the data on the sound including the abnormal sound included in the extracted past abnormal sound data together with the causative part information. This allows the user to recognize at least one of the information on the causative part, vehicle information on vehicles in which abnormal noises caused by the same causative part have occurred in the past, and sounds including abnormal noises caused by the same causative part in the past. This allows the user to be convinced that abnormal noises caused by the same part have occurred in the past. As a result, the user can be made to recognize that the abnormal noise diagnosis results are highly reliable. Here, examples of "vehicle information" include the model of the power source, transmission, etc. installed in the vehicle. Therefore, examples of abnormal noise vehicle information similar to the vehicle information acquired by the vehicle information acquisition unit include that the model of the power source, transmission, etc. installed in the vehicle is similar, for example, if the power source is an engine, the number of cylinders of the engine is the same,

[0009] In such an abnormal sound diagnosis system of the present invention, the abnormal sound detection unit may be mounted on the vehicle, and the data storage unit, the vehicle information acquisition unit, and the output unit may be mounted on a diagnostic server capable of exchanging data with the vehicle via wired or wireless communication. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an outline of the configuration of an abnormal sound diagnosis system 20 according to an embodiment of the present invention. [Diagram 2] FIG. 2 is an explanatory diagram showing an example of vehicle processing, server processing, and terminal processing executed in the vehicle 22, the diagnostic server 30, and the diagnostic terminal 40 during abnormal sound diagnosis. [Diagram 3] 4 is a flowchart showing an example of a post-processing routine executed by the diagnostic terminal 40. [Figure 4] 13 is a flowchart showing an example of a post-processing routine of a modified example executed by the diagnostic terminal 40. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Next, a mode for carrying out the present invention will be described using examples. EXAMPLES

[0012] 1 is a diagram showing the outline of the configuration of an abnormal sound diagnosis system 20 according to one embodiment of the present invention. As shown in the figure, the abnormal sound diagnosis system 20 of the embodiment includes a vehicle 22, a diagnosis server 30, and a diagnosis terminal 40.

[0013] The vehicle 22 is configured as an automobile that runs by outputting power from an engine to a drive shaft connected to an axle via a transmission, and includes a microphone 24, a control device 26, and a dongle 28. The microphone 24 is built into the headrest of the seat on which the passenger sits, and detects sounds in the vehicle cabin. The control device 26 is configured as a general-purpose microcomputer centered on a CPU, and includes, in addition to the CPU, a ROM, a RAM, a flash memory, a storage device, an input / output port, a communication port, and the like. Signals detected by various sensors are input to the control device 26. Examples of the input signals include the engine speed from a speed sensor that detects the engine speed, the oil temperature from a temperature sensor that detects the temperature of the lubricating oil that lubricates the transmission, and the coolant temperature from a temperature sensor that detects the temperature of the coolant that cools the engine. Various signals are output from the control device 26. The dongle 28 is attached to a connection terminal (not shown) below the handle, and exchanges various data with the control device 26 via this connection terminal. Data input from the control device 26 to the dongle 28 includes, for example, the engine speed, the temperature of the transmission lubricating oil, and the engine coolant temperature. Sound data detected by the microphone 24 is input to the dongle 28 via wireless communication. The dongle 28 is connected to the diagnostic server 30 and the diagnostic terminal 40 via communication, and exchanges various data with the diagnostic server 30 and the diagnostic terminal 40.

[0014] The diagnostic server 30 is configured as a general-purpose microcomputer with a CPU at its core, and includes a ROM, a RAM, a flash memory, a storage device, an input / output port, a communication port, and the like in addition to the CPU. As described above, the diagnostic server 30 exchanges data with the dongle 28 of the vehicle 22 via wireless communication. The diagnostic server 30 collects various data from the vehicle 22 via the dongle 28 at predetermined time intervals. Examples of the collected data include engine speed, transmission lubricant oil temperature, engine coolant temperature, and sound data detected by the microphone 24. The diagnostic server 30 stores in the storage device an abnormal sound diagnosis program 32 for diagnosing the cause of an abnormal sound generated in the vehicle 22, and an abnormal sound database 34 that accumulates abnormal sound data of multiple vehicles. The abnormal sound data is data that associates abnormal sound generating part information as information on a part that caused an abnormal sound in an abnormal sound generating vehicle in the past, abnormal sound vehicle information as vehicle information on the abnormal sound generating vehicle, and sound data including an abnormal sound generated in the abnormal sound generating vehicle. The abnormal noise vehicle information may include the vehicle model and year, the type of engine and transmission installed, the temperature of the transmission lubricant oil when the abnormal noise occurred, the temperature of the cooling water when the abnormal noise occurred, the engine speed when the abnormal noise occurred, etc. The diagnostic server 30 exchanges various data with the diagnostic terminal 40 via communication.

[0015] The diagnostic terminal 40 is configured as a general-purpose microcomputer with a CPU at its core, and in addition to the CPU, is equipped with a ROM, a RAM, a flash memory, a storage device, a display device, an input / output port, a communication port, etc. The diagnostic terminal 40 exchanges various information with the dongle 28 of the vehicle 22, the diagnostic server 30, a manufacturer terminal 50 installed at the development manufacturer that developed the abnormal sound diagnosis program 32 installed in the diagnostic server 30, and a manufacturer terminal 52 installed at the manufacturer that manufactured the vehicle 22, via wired or wireless communication. The diagnostic terminal 40 displays the various information received from the dongle 28 and the diagnostic server 30 on the display device.

[0016] Next, the operation of the abnormal sound diagnosis system 20 configured as described above will be described, in particular the operation when diagnosing an abnormal sound generated in the vehicle 22 and the operation after processing based on the abnormal sound diagnosis. First, the operation when diagnosing an abnormal sound generated in the vehicle 22 will be described. Fig. 2 is an explanatory diagram showing an example of vehicle processing, server processing, and terminal processing executed in the vehicle 22, the diagnostic server 30, and the diagnostic terminal 40 when diagnosing an abnormal sound. The diagnostic processing is performed when the vehicle 22 enters a repair shop.

[0017] In the diagnostic process, first, the dongle 28 of the vehicle (vehicle to be diagnosed) 22 to be diagnosed for abnormal sounds detects voice data with the microphone 24 in the vehicle process, transmits the detected voice data to the diagnostic terminal 40, and also inputs vehicle information from the control device 26 and transmits it to the diagnostic server 30 (step S100). The voice data is detected while the vehicle (vehicle to be diagnosed) 22 is running on a vehicle test stand or on a road. Examples of vehicle information include the make and year of the vehicle, the type of engine and transmission installed, the temperature of the transmission lubricating oil when the abnormal sound occurs, the temperature of the cooling water when the abnormal sound occurs, the engine speed when the abnormal sound occurs, etc.

[0018] The diagnostic terminal 40 receives the voice data and the vehicle information through terminal processing, and transmits the received voice data and the vehicle information to the diagnostic server 30 (step S300).

[0019] The diagnostic server 30 acquires the voice data and vehicle information of the vehicle (vehicle to be diagnosed) 22 from the diagnostic terminal 40 through server processing (step S200), and identifies the causative part that is causing the abnormal sound from the acquired voice data (step S210). The causative part is identified by storing in ROM a database of frequency spectra for each part when the abnormal sound occurs that have been obtained in advance through experiments, analysis, etc., comparing the frequency spectrum of the acquired voice data with the frequency spectrum when the abnormal sound occurs stored in the database, identifying a frequency spectrum in the database that matches the frequency spectrum of the voice data or is similar enough to be considered to match, and identifying the part that corresponds to the identified frequency spectrum as the causative part.

[0020] The diagnostic server 30 extracts from the abnormal sound database 34 past abnormal sound data that is highly relevant to the abnormal sound caused by the causative part identified in step S210 (step S220). Highly relevant abnormal sound data can be abnormal sound data in which the abnormal sound generating part information is identical to the causative part information identified in step S210, and the abnormal sound vehicle information includes vehicle information that is identical or similar to the vehicle information acquired in step S200. Examples of similar vehicle information can include abnormal sound vehicle information that differs only in the model year but is the same in the rest, or that differs only in the model of the engine or transmission but is the same in the rest.

[0021] The diagnostic server 30 transmits (outputs) the information of the causative part identified in step S210 and the past abnormal sound data extracted in step S220 to the diagnostic terminal 40 (step S230). Then, the diagnostic server 30 creates abnormal sound data that associates the information of the causative part with the vehicle information of the vehicle (diagnosed vehicle) 22 and the sound data of the vehicle (diagnosed vehicle) 22, stores the created abnormal sound data in the abnormal sound database 34 (step S240), and ends the server processing.

[0022] The diagnostic terminal 40 acquires the causative part information and the past abnormal sound data from the diagnostic server 30 (step S310). Then, the acquired causative part information and the vehicle information of the past abnormal sound data are displayed on the display device, and the voice data included in the past abnormal sound data are played back (step S320), and the terminal processing ends. By displaying the causative part information and the vehicle information of the past abnormal sound data, and by playing back the voice data included in the past abnormal sound data, the user of the diagnostic terminal 40 can be made aware that a similar abnormal sound has occurred in the past in a vehicle equipped with the causative part, and the reliability of the abnormal sound diagnosis result is high.

[0023] Next, the operation after processing based on the abnormal sound diagnosis will be described. Fig. 3 is a flow chart showing an example of a post-processing routine executed by the diagnosis terminal 40. This routine is executed when a part identified as the causative part in the diagnosis processing of the vehicle (vehicle to be diagnosed) 22 in Fig. 2 is replaced at a repair shop or the like, and the result of an investigation as to whether the generation of abnormal sound in the vehicle (vehicle to be diagnosed) 22 has disappeared is input to the diagnosis terminal 40.

[0024] When the post-processing routine is executed, the diagnostic terminal 40 executes a process to determine whether or not the causative part has been correctly identified (step S400). The determination of whether or not the causative part has been correctly identified is performed by determining that the causative part has been correctly identified when the generation of abnormal noise in the vehicle (diagnosed vehicle) 22 has ceased after replacement of the causative part in the vehicle (diagnosed vehicle) 22, and by determining that the causative part has not been correctly identified when the abnormal noise is occurring. If the causative part has not been correctly identified, the post-processing routine is terminated.

[0025] If the causative part has been correctly identified in step S400, the accuracy rate of the abnormal sound diagnosis is calculated by adding a value of 1 to the number of times it was determined that the causative part was correctly identified in step S400 of previously executed post-processing routines, and dividing the result by the number of times abnormal sound diagnosis of that causative part was previously executed plus a value of 1 (step S410), and the calculated accuracy rate is sent to the manufacturer terminal 50 of the manufacturer that created the abnormal sound diagnosis program 32 (step S420). This allows the manufacturer that created the abnormal sound diagnosis program 32 to recognize the accuracy of the abnormal sound diagnosis of the abnormal sound diagnosis program 32.

[0026] Next, the abnormal noise occurrence count Nn is updated by incrementing it by a value of 1 as the number of abnormal noise occurrences for that causal part (the abnormal noise occurrence count Nn is incremented by a value of 1) (step S430), and it is determined whether the abnormal noise occurrence count Nn is equal to or greater than a threshold value Nth (step S440). The threshold value Nth is a threshold value for determining whether the abnormal noise determined for that causal part occurs frequently. If the abnormal noise occurrence count Nn is less than the threshold value Nth, the post-processing routine is terminated.

[0027] When the number of abnormal sound occurrences Nn is equal to or greater than the threshold value Nth in step S440, an alert notification informing the manufacturer terminal 52 that the causative part is frequently generating abnormal sounds (step S450), and the post-processing routine is terminated. This process allows the manufacturer of the vehicle 22 to be made aware that the causative part is frequently generating abnormal sounds.

[0028] In the abnormal sound diagnosis system 20 of the embodiment described above, the diagnostic server 30 stores abnormal sound data in the abnormal sound database 34, which associates abnormal sound generating part information as information on parts that caused abnormal sounds in the abnormal sound generating vehicle in the past, abnormal sound vehicle information as vehicle information on the abnormal sound generating vehicle, and data on sounds including abnormal sounds generated in the abnormal sound generating vehicle. The microphone 24 detects sounds including abnormal sounds generated in the vehicle (diagnosis vehicle) 22 as the target for diagnosing the abnormal sound. The diagnostic server 30 acquires vehicle information on the vehicle (diagnosis vehicle) 22, identifies the causative part that is causing the abnormal sound from the detected sound of the vehicle (diagnosis vehicle) 22, extracts past abnormal sound data from the stored abnormal sound database 34, which includes abnormal sound generating part information identical to the identified causative part information and includes abnormal sound vehicle information identical or similar to the acquired vehicle information, and transmits (outputs) the abnormal sound vehicle information included in the extracted past abnormal sound data together with the causative part information. This allows the user to recognize that the abnormal sound diagnosis result is highly reliable.

[0029] In the abnormal sound diagnosis system 20 of the embodiment, the extracted past abnormal sound data is transmitted (output) together with the causative part information in step S230 of the abnormal sound diagnosis processing in Fig. 2. However, since it is sufficient to transmit (output) at least one of the abnormal sound vehicle information and data on sounds including abnormal sounds from the extracted past abnormal sound data together with the causative part information, for example, it is also possible to transmit (output) only the data on sounds including abnormal sounds together with the causative part information.

[0030] In the abnormal sound diagnosis system 20 of the embodiment, vehicle processing is executed in the vehicle 22, server processing is executed in the diagnostic server 30, and terminal processing is executed in the diagnostic terminal 40. However, the present invention is not limited to the vehicle processing, server processing, and terminal processing being executed by the vehicle 22, diagnostic server 30, and diagnostic terminal 40, respectively, and it is sufficient that each of the vehicle processing, server processing, and terminal processing is executed by at least one of the vehicle 22, diagnostic server 30, and diagnostic terminal 40, such as executing server processing by the diagnostic terminal 40.

[0031] In the abnormal sound diagnosis system 20 of the embodiment, after the abnormal sound diagnosis is completed, the post-processing routine illustrated in Fig. 3 is executed. However, instead of the post-processing routine illustrated in Fig. 3, a modified post-processing routine illustrated in Fig. 4 may be executed. The post-processing routine in Fig. 4 executes the same processing as the post-processing routine in Fig. 3, except that steps S410 and S420 of the post-processing routine illustrated in Fig. 3 are not executed. In this way, it is possible to make the manufacturer of the vehicle 22 aware that the causative part is frequently generating abnormal sounds.

[0032] In the abnormal sound diagnosis system 20 of the embodiment, the vehicle 22 is configured as an automobile that runs by outputting power from an engine to a drive shaft connected to an axle via a transmission. However, the vehicle 22 may also be an electric automobile that runs on power from a motor, or a hybrid automobile that can run on power from both an engine and a motor.

[0033] In the abnormal sound diagnosis system 20 of the embodiment, the microphone 24 is built into the headrest of the seat. However, the microphone 24 may be attached to any position where it can detect abnormal sounds generated in the vehicle, for example, on the ceiling of the passenger compartment or in the engine room.

[0034] The correspondence between the main elements of the embodiment and the main elements of the invention described in the section on means for solving the problem will be described below. In the embodiment, the microphone 24 corresponds to the "abnormal sound detection unit", and the diagnostic server 30 corresponds to the "data storage unit", the "vehicle information acquisition unit", and the "output unit".

[0035] The correspondence between the main elements of the Examples and the main elements of the invention described in the Summary of the Problem column does not limit the elements of the invention described in the Summary of the Problem column, since the Examples are examples for specifically explaining the mode for implementing the invention described in the Summary of the Problem column. In other words, the interpretation of the invention described in the Summary of the Problem column should be based on the description in that column, and the Examples are merely a specific example of the invention described in the Summary of the Problem column.

[0036] Although the form for carrying out the present invention has been described above using examples, the present invention is not limited to these examples in any way, and it goes without saying that the present invention can be carried out in various forms without departing from the scope of the gist of the present invention. [Industrial Applicability]

[0037] The present invention can be used in the manufacturing industry of abnormal sound diagnosis systems. [Explanation of symbols]

[0038] 20 abnormal sound diagnosis system, 22 vehicle, 24 microphone, 26 control device, 28 dongle, 30 diagnostic server, 32 abnormal sound diagnosis program, 34 abnormal sound database, 40 diagnostic terminal, 50, 52 manufacturer terminal.

Claims

[Claim 1] An abnormal sound diagnosis system for diagnosing abnormal sounds occurring in a vehicle, comprising: a data storage unit that stores in an abnormal sound database abnormal sound data that associates abnormal sound generating part information as information on parts that caused abnormal sounds in abnormal sound generating vehicles that have generated abnormal sounds in the past, abnormal sound vehicle information as vehicle information on the abnormal sound generating vehicles, and sound data including abnormal sounds generated in the abnormal sound generating vehicles; an abnormal sound detection unit that detects sounds including abnormal sounds generated in a vehicle to be diagnosed; a vehicle information acquisition unit that acquires vehicle information regarding the vehicle to be diagnosed; an output unit which identifies a causative part causing an abnormal sound from the detected sound of the diagnosed vehicle, extracts from the abnormal sound database stored in the data storage unit past abnormal sound data which includes the abnormal sound generating part information identical to the identified causative part information and which includes the abnormal sound vehicle information which is identical or similar to the vehicle information acquired by the vehicle information acquisition unit, and outputs at least one of the abnormal sound vehicle information and the sound data including an abnormal sound contained in the extracted past abnormal sound data together with the causative part information; an alert sending unit that determines whether the causative part has been correctly identified, and when the causative part has been correctly identified, increases the number of abnormal sound occurrences by a value of 1 as the number of occurrences of abnormal sound in the causative part, and when the number of abnormal sound occurrences is equal to or greater than a threshold, sends an alert notification notifying that abnormal sounds are occurring frequently in the causative part; An abnormal sound diagnosis system comprising:

Images