Failure pre-experience control device for vehicle and failure pre-experience control method for vehicle

Abstract

To improve reliability of a driver with respect to detection of a sign of a failure.SOLUTION: A failure pre-experience control device 1 for a vehicle includes: a failure sign detection unit 102 that predicts a failure of the vehicle based on traveling data of the vehicle; a user command input unit that determines whether or not pre-experience of an event that occurs in the vehicle when the predicted failure occurs can be performed; a service environment determination unit 202 that determines whether or not the vehicle is in environment in which the pre-experience can be performed; and a control signal value control unit 401 that performs the pre-experience in a case where a failure of the vehicle is predicted, there is a request to allow the pre-experience to be performed, and the vehicle is in environment in which the pre-experience can be performed.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vehicle pre-failure experience control device and a vehicle pre-failure experience control method.

Background Art

[0002] For example, Patent Document 1 discloses a vehicle failure warning device having a failure response database in which information indicating failure contents and failure response methods is associated with each combination of received vehicle state signals and vehicle abnormality signals. When a failure occurs in the vehicle, the failure warning device of Patent Document 1 converts the failure contents and failure response methods of the vehicle into voice data and outputs the voice data to warn the driver.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in Patent Document 1, when an abnormality is not felt by the driver in the driver's cab at the time when a failure is detected, there is a problem that the reliability of the driver with respect to the information that a failure has occurred in the vehicle is low.

[0005] That is, when there is no abnormal event in the vehicle at the time when a vehicle failure or a sign of a failure is detected, the reliability of the driver with respect to the information that a vehicle failure or a sign of a failure has been detected may be low. Therefore, there is room for further improvement in order to increase the reliability of the driver with respect to the detection of a vehicle failure or a sign of a failure.

Means for Solving the Problems

[0006] Therefore, the pre-experience control for vehicle failures of the present invention has a requirement that enables the implementation of a pre-experience of events that occur in the vehicle when a predicted vehicle failure occurs, and when there is a vehicle in an environment where the above pre-experience can be implemented, the above pre-experience is implemented.

Advantages of the Invention

[0007] According to the present invention, by pre-experiencing the events that occur in the vehicle when a predicted failure occurs, it is possible to improve the driver's reliability regarding the future occurrence of the predicted vehicle failure.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Modes for Carrying Out the Invention

[0009] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0010] FIG. 1 is a functional block diagram of a vehicle pre-failure experience control device 1 according to a first embodiment of the present invention. The pre-failure experience control device 1 is, for example, a control device of a vehicle equipped with an internal combustion engine (not shown).

[0011] When there is a request to enable the implementation of a pre-failure experience of a predicted vehicle failure and the vehicle is in an environment where the pre-failure experience (failure experience) and the playback of a video related to the failure (failure explanation video) can be performed, the pre-failure experience control device 1 performs the pre-failure experience and the playback of the video related to the failure.

[0012] The pre-failure experience control device 1 uses, for example, a well-known digital computer equipped with a CPU, ROM, RAM, and input / output interfaces, and is mounted on the vehicle.

[0013] The pre-failure experience control device 1 includes a failure prediction system 100, a failure experience service system 200, a user interface 300, and an engine control system 400. The failure prediction system 100, the failure experience service system 200, the user interface 300, and the engine control system 400 are in-vehicle systems mounted on the vehicle.

[0014] The failure prediction system 100 includes a data analysis unit 101, a failure omen detection unit 102, an abnormal vibration / abnormal noise detection unit 103, and a first communication unit 104.

[0015] The data analysis unit 101 analyzes the output signals output from various sensors installed in each part of the vehicle. That is, the data analysis unit 101 analyzes the driving data acquired by various sensors during the driving of the vehicle. The various sensors are, for example, an air-fuel ratio sensor capable of detecting the air-fuel ratio in the exhaust of the internal combustion engine, a crank angle sensor capable of detecting the rotation of the crankshaft of the internal combustion engine, a cooling water temperature sensor capable of detecting the cooling water temperature of the internal combustion engine, an air flow meter for detecting the intake air amount of the internal combustion engine, and the like.

[0016] The fault prediction detection unit 102 predicts a fault by detecting a fault prediction using the output signals from a single or multiple sensors. That is, the fault prediction detection unit 102 detects a fault prediction using the analysis result of the data analysis unit 101 that uses the output signals of multiple sensors. The fault prediction detection unit 102, for example, compares the analysis result of the data analysis unit 101 with a corresponding predetermined threshold value to detect a fault prediction. The fault prediction detection unit 102 can identify the component (faulty component) in which the predicted fault will occur. The fault prediction detection unit 102 can, for example, predict a fault in the fuel injection valve of the internal combustion engine using the analysis result of the data analysis unit 101 that uses the output signals of the air-fuel ratio sensor and the crank angle sensor. The fault prediction detection unit 102 can, for example, predict a fault in the ignition coil of the internal combustion engine using the analysis result of the data analysis unit 101 that uses the output signals of the crank angle sensor, the cooling water temperature sensor, the air-fuel ratio sensor, and the air flow meter. In addition, the fault prediction detection unit 102 can determine whether the repair or replacement of the component with a fault prediction has been performed. The fault prediction detection unit 102, for example, determines that a repair has been made when the abnormality level is improved by the analysis result of the data analysis unit 101 after performing a prior experience or after playing a video of information related to the fault, or when the abnormality level based on the analysis result of the data analysis unit 101 is reset during the repair response.

[0017] The abnormal vibration and abnormal noise detection unit 103 has, for example, various sensors capable of detecting vibration and a microphone or the like capable of detecting the sound emitted by the vehicle. The abnormal vibration and abnormal noise detection unit 103 can detect the vibration of the vehicle and the sound emitted by the vehicle, and monitors in real time the abnormal vibration and abnormal noise generated during driving. That is, the abnormal vibration and abnormal noise detection unit 103 can detect the abnormal vibration and abnormal noise generated due to the failure to repair or replace the parts corresponding to the predicted failure.

[0018] Note that the abnormal vibration and abnormal noise detection unit 103 may detect the abnormal vibration and abnormal noise generated during driving by using the analysis result of the data analysis unit 101 used by the failure prediction detection unit 102. That is, the abnormal vibration and abnormal noise detection unit 103 may be considered to have detected abnormal vibration and abnormal noise when the degree of abnormality detected by the failure prediction detection unit 102 increases. Specifically, for example, by comparing the analysis result of the data analysis unit 101 with a threshold different from the threshold used by the failure prediction detection unit 102, the occurrence of abnormal vibration and abnormal noise may be detected.

[0019] When the failure of the vehicle is predicted, the first communication unit 104 transmits information about the predicted failure to the failure experience service system 200, the user interface 300, and the engine control system 400.

[0020] The failure experience service system 200 includes a self-vehicle position acquisition unit 201, a service environment determination unit 202, an experienceable location guidance unit 203, a failure explanation video database 204, an abnormal noise database 205, and a second communication unit 206.

[0021] The self-vehicle position acquisition unit 201 can acquire the position information of the vehicle at the current time. The self-vehicle position acquisition unit 201 may, for example, acquire three-dimensional position information on the earth based on signals from GPS satellites.

[0022] The service environment determination unit 202 determines whether it is possible to experience a predicted failure in advance or play a video related to the predicted failure at the current location based on the current location of the vehicle and the current state of the vehicle (whether it is in a driving state or a stopped state). For example, when the vehicle is stopped in a safe place such as a parking lot, the service environment determination unit 202 determines that it is possible to experience a predicted failure in advance or play a video related to the predicted failure. For example, when the vehicle is in motion or temporarily stopped at an intersection, the service environment determination unit 202 determines that it is not possible to experience a predicted failure in advance or play a video related to the predicted failure. That is, the service environment determination unit 202 corresponds to an executable determination unit that determines whether the vehicle is in an environment where it is possible to experience a predicted failure in advance or play a video related to the predicted failure.

[0023] The experienceable location guidance unit 203 searches for a route to a location where it is possible to experience a predicted failure in advance or play a video using, for example, an in-vehicle car navigation system, and provides it to the driver. That is, when the service environment determination unit 202 determines that it is not possible to experience a predicted failure in advance or play a video related to the predicted failure at the current location, the experienceable location guidance unit 203 calculates a route to guide the vehicle from the current location to a location where it is possible to experience a predicted failure in advance or play a video.

[0024] The failure explanation video database 204 is a database of videos in which information on the cause of a failure and the events that occur in the vehicle when the failure occurs are converted into video data for each failure of the vehicle. The failure explanation video database 204 stores information on the cause of the failure and the events that occur in the vehicle when the failure occurs. In addition, the failure explanation video database 204 can make the vehicle in the video the same vehicle type as the own vehicle when converting the video data according to the vehicle type information.

[0025] The abnormal sound database 205 is a database that digitizes the abnormal sounds generated at the time of a vehicle failure for each vehicle failure. In the abnormal sound database 205, information on events occurring in the vehicle when a failure occurs, specifically, the abnormal sounds generated at the time of failure digitized by vehicle type, is stored.

[0026] Note that the failure explanation video database 204 and the abnormal sound database 205 may be provided, for example, on a cloud outside the vehicle and accessed from the vehicle side as needed for use on the vehicle.

[0027] The second communication unit 206 transmits the vehicle type information of the vehicle input from the user command input unit 302 (described later) of the user interface 300 to the failure explanation video database 204 and the abnormal sound database 205. Also, the second communication unit 206 can receive information regarding the predicted failure via the first communication unit 104 and instructions from the driver of the vehicle input to the user command input unit 302 (described later) of the user interface 300. When the vehicle is in an environment where a prior experience of the failure predicted by the service environment determination unit 202 or the playback of a video regarding the predicted failure can be performed, the second communication unit 206 outputs this fact to the user interface 300 to notify the driver.

[0028] The user interface 300 includes a vehicle information notification unit 301, a user command input unit 302, and a third communication unit 303.

[0029] The vehicle information notification unit 301 notifies various information to the driver of the vehicle. For example, it can notify the determination result of the service environment determination unit 202. Also, the vehicle information notification unit 301 can play back a video regarding the predicted failure and play back the abnormal sound generated when the predicted failure occurs. When the vehicle information notification unit 301 plays back the video of the failure explanation video database 204 or the abnormal sound of the abnormal sound database 205, it receives the data via the second communication unit 206.

[0030] The user command input unit 302 is capable of receiving instructions from the driver of the vehicle. The user command input unit 302 can, for example, receive inputs regarding whether to perform a pre-experience of a failure, whether to play a video related to a predicted failure, and the vehicle type of the vehicle. That is, the user command input unit 302 corresponds to an execution availability determination unit that determines the availability of a pre-experience for allowing the vehicle to experience in advance an event that will occur when a predicted failure occurs.

[0031] The vehicle information notification unit 301 and the user command input unit 302 are, for example, touch panel monitors used in a car navigation system.

[0032] The third communication unit 303 transmits the user command input from the user command input unit 302 to the second communication unit 206 of the failure experience service system 200. Further, the third communication unit 303 is capable of receiving information regarding a predicted failure from the first communication unit 104, as well as a failure explanation video and abnormal sound data from the second communication unit 206.

[0033] The engine control system 400 is capable of controlling the internal combustion engine mounted on the vehicle, and includes a control signal value control unit 401, a control signal value database 402, and a fourth communication unit 403.

[0034] The control signal value control unit 401 controls the internal combustion engine based on various control signals stored in the control signal value database 402. The control signal value control unit 401 corresponds to the pre-experience execution unit. When performing a pre-experience of a failure, for example, it changes the control signal value of the corresponding component to a predetermined control signal value for experience and then controls it. The control signal value for experience corresponds to a failure value and is the control signal value used when performing a pre-experience of a failure. By using the control signal value for experience, it is possible to pseudo-generate an event that occurs when a predicted failure occurs. The control signal value for experience is set for each predicted failure. When the control signal value control unit 401 does not perform a pre-experience of a failure (normal time), it controls the component to be controlled using the normal control signal value set according to the operating state. That is, when the control signal value control unit 401 does not perform a pre-experience of a failure (normal time), it controls the internal combustion engine according to the operating state.

[0035] The control signal value database 402 stores the normal control signal value of the internal combustion engine and the control signal value for experience used when performing a pre-experience of a failure.

[0036] The fourth communication unit 403 is capable of receiving information about the predicted failure from the first communication unit 104. Also, the fourth communication unit 403 is capable of receiving an instruction from the driver of the vehicle input to the user command input unit 302 of the user interface 300 via the second communication unit 206 of the failure experience service system 200. Note that the fourth communication unit 403 may directly receive an instruction from the driver of the vehicle input to the user command input unit 302 of the user interface 300 from the third communication unit 303.

[0037] When the failure prediction system 100 detects a sign of failure, such a pre-failure experience control device 1 transmits the fact that the sign of failure has been detected and the content of the predicted failure to the user interface 300. When a failure is predicted, the user interface 300 displays a screen as shown in FIG. 2 on the vehicle information notification unit 301 and notifies the driver. The user interface 300 transmits an instruction from the driver input to the user instruction input unit 302 to the failure experience service system 200. FIG. 2 is an explanatory diagram showing an example of a screen displayed on the vehicle information notification unit 301 when a sign of failure is detected in the pre-failure experience control device 1 of the first embodiment. As shown in FIG. 2, in addition to the options of "Yes" and "No", an option to postpone the answer may be noted.

[0038] When a failure is predicted, the failure experience service system 200 acquires the position of the vehicle from the own vehicle position acquisition unit 201 and determines whether it is possible to perform a pre-failure experience of the predicted failure at the current position or play a video related to the predicted failure. When the failure experience service system 200 determines that it is not possible to perform a pre-failure experience of the predicted failure at the current position or play a video related to the predicted failure, the experienceable location guidance unit 203 guides the vehicle to a location where a pre-failure experience of the failure or a video related to the failure can be played. When performing a pre-failure experience of the predicted failure, the engine control system 400 controls the component corresponding to the predicted failure using the control signal value for experience and makes the driver experience the predicted failure pseudo.

[0039] When the failure event of the predicted failure is only abnormal noise, the driver inputs the vehicle type of the own vehicle to the user instruction input unit 302, and the abnormal noise when the predicted failure occurs in the own vehicle is searched from the abnormal noise database 205. When the failure event of the predicted failure is only abnormal noise, the control of the failure target component by the control signal value for experience may be omitted.

[0040] In addition, when the abnormal vibration / abnormal noise detection unit 103 detects abnormal vibration or abnormal noise, the pre-failure experience control device 1 outputs a notification prompting the driver to repair the failed component to the vehicle information notification unit 301.

[0041] Figure 3 is a flowchart showing the flow of processing performed by the pre-failure experience control device 1 of the first embodiment described above.

[0042] In step S1, the output signals output from various in-vehicle sensors during vehicle travel are analyzed. That is, in step S1, the travel data of the traveling vehicle is analyzed. Step S1 is a process performed by the data analysis unit 101.

[0043] In step S2, it is determined whether or not a sign of a failure has been detected from the result of analyzing the travel data. If it is determined in step S2 that a sign of a failure has been detected, the process proceeds to step S3. If it is determined in step S2 that no sign of a failure has been detected, the process returns to step S1 and the analysis of the travel data is continued. Step S2 is a process performed by the failure sign detection unit 102.

[0044] In step S3, the predicted failure is notified to the driver. Also, in step S3, the driver is notified of whether or not it is possible to perform a pre-failure experience of the predicted failure. Step S3 is a process performed by the vehicle information notification unit 301. When the driver is notified in step S3, the process proceeds from step S3 to step S4.

[0045] In step S4, it is determined whether or not to perform a pre-failure experience (failure experience) of the predicted failure. If it is determined in step S4 to perform a pre-failure experience of the predicted failure, the process proceeds to step S5. If it is determined in step S4 not to perform a pre-failure experience of the predicted failure, the process proceeds to step S6. Whether or not to perform a pre-failure experience of the predicted failure is determined by the driver inputting to the user command input unit 302. That is, step S4 is a process performed by the user command input unit 302. In addition, when notified of whether or not it is possible to perform a pre-failure experience of the predicted failure, if no input regarding approval or disapproval is received from the driver to the user command input unit 302 even after a predetermined time has elapsed, it may be determined that no pre-failure experience of the predicted failure is performed.

[0046] In step S5, it is determined whether the vehicle is in an environment where a pre-experience can be carried out. If it is determined in step S5 that the vehicle is in an environment where a pre-experience can be carried out, the process proceeds to step S7. If it is determined in step S5 that the vehicle is not in an environment where a pre-experience can be carried out, the process proceeds to step S8. Step S5 is a process performed by the service environment determination unit 202.

[0047] In step S7, a pre-experience of the predicted failure is carried out. If the event that occurs when the predicted failure occurs is only abnormal noise, it may be sufficient to reproduce the corresponding abnormal noise based on the information from the abnormal noise database 205. Step S7 is a process performed by the control signal value control unit 401 and the failure experience service system 200. When the pre-experience of the predicted failure is carried out in step S7, the process proceeds from step S7 to step S9.

[0048] In step S8, the vehicle is guided to a place where a pre-experience can be carried out. Step S8 is a process performed by the experienceable location guidance unit 203.

[0049] In step S9, it is determined whether any action has been taken regarding the failed part. If it is determined in step S9 that actions such as repair or replacement of the failed part have been taken, the current routine ends. If it is determined in step S9 that no action has been taken regarding the failed part, the process proceeds to step S10. Step S9 is performed by the failure omen detection unit 102.

[0050] In step S10, when detecting the occurrence of abnormal vibration or abnormal noise caused by the failure, a notification prompting the driver to take actions such as repair is sent. That is, in step S10, for example, after carrying out the pre-experience of the predicted failure, a notification prompting the repair of the predicted failure is sent to the driver. Step S10 is a process performed by the abnormal vibration / abnormal noise detection unit 103.

[0051] In step S6, it is determined whether to play the video related to the predicted failure. If it is determined in step S6 to play the video related to the predicted failure, the process proceeds to step S11. If it is determined in step S6 not to play the video related to the predicted failure, the process proceeds to step S9. Whether to play the video related to the predicted failure is determined by the driver inputting to the user command input unit 302. Note that when notified about whether to play the video related to the predicted failure, if no input regarding approval or disapproval is received from the driver to the user command input unit 302 even after a preset predetermined time has elapsed, it may be determined that the video related to the predicted failure will not be played.

[0052] In step S11, it is determined whether the environment is suitable for playing the video related to the predicted failure. If it is determined in step S11 that the environment is suitable for playing the video related to the predicted failure, the process proceeds to step S12. If it is determined in step S11 that the environment is not suitable for playing the video related to the predicted failure, the process proceeds to step S13. Step S11 is a process performed by the service environment determination unit 202.

[0053] In step S12, the vehicle model is selected. The selection of the vehicle model is implemented (realized), for example, by the driver inputting information related to the vehicle model to the user command input unit 302. Step S12 is a process performed by the user command input unit 302. Note that in a scenario where vehicle model selection is required, if no input regarding the vehicle model is received from the driver to the user command input unit 302 even after a preset predetermined time has elapsed, the initial set vehicle model may be selected. When the vehicle model is selected in step S12, the process proceeds to step S14.

[0054] In step S13, the vehicle is guided to a place where the video (viewing) related to the predicted failure can be played. Step S13 is a process performed by the experienceable location guidance unit 203.

[0055] In step S14, a video related to the predicted failure is played. The vehicle appearing in this played video is of the same vehicle type as the host vehicle. Also, the sound related to the failure used in this played video may be one that occurs in a vehicle of the same vehicle type as the host vehicle. When the video related to the failure predicted in step S14 is played, the process proceeds to step S9. Step S14 is a process performed by the failure experience service system 200.

[0056] The failure pre-experience control device 1 of the first embodiment described above can enable the driver to pseudo-experience in advance the events that occur when the predicted failure occurs in the vehicle when a sign of the vehicle's failure is detected. That is, when a sign of the vehicle's failure is detected, the driver of the vehicle can pseudo-experience in advance the vibration or abnormal noise that occurs in the vehicle when the predicted failure occurs.

[0057] Thereby, the failure pre-experience control device 1 of the first embodiment described above can improve the driver's reliability with respect to the predicted vehicle failure and can promote the driver's response (repair response) to the predicted vehicle failure.

[0058] The failure pre-experience control device 1 of the first embodiment can play a video related to the predicted failure on the vehicle information notification unit 301. That is, the failure pre-experience control device 1 of the first embodiment can output information related to the cause of the predicted failure and the events that occur in the vehicle when the predicted failure occurs in the form of a video.

[0059] Therefore, it becomes easy for the driver to understand the cause of the predicted vehicle failure and the events that occur in the vehicle when the predicted failure occurs.

[0060] The pre-failure experience control device 1 of the first embodiment can issue a notice to prompt the driver to repair the predicted failure after the pre-failure experience of the predicted failure is implemented. Therefore, before the predicted failure occurs, the driver is prompted to repair or replace the parts corresponding to the predicted failure. That is, the pre-failure experience control device 1 of the first embodiment can suppress the occurrence of a pre-predicted failure during driving.

[0061] Hereinafter, other embodiments of the present invention will be described. The same components as those in the above-described embodiment are denoted by the same reference numerals, and redundant descriptions are omitted.

[0062] The second embodiment of the present invention will be described. The pre-failure experience control device 2 of the second embodiment estimates the driving distance (drivable distance) until the predicted failure occurs and notifies the driver of the estimated drivable distance.

[0063] FIG. 4 is a functional block diagram of the pre-failure experience control device 2 of the vehicle in the second embodiment of the present invention. The pre-failure experience control device 2 of the second embodiment has substantially the same configuration as the pre-failure experience control device 1 of the first embodiment described above. However, as shown in FIG. 4, the failure prediction system 100 has a drivable distance prediction unit 105.

[0064] The drivable distance prediction unit 105 predicts (calculates) the drivable distance until the failure caused by the detected sign of the failure (predicted failure) occurs from the time when the sign of the failure is detected. The drivable distance until the predicted failure occurs is predicted using, for example, the analysis result of the data analysis unit 101.

[0065] And the pre-failure experience control device 2 of the second embodiment can reproduce the abnormality (abnormal vibration or abnormal noise) caused by the predicted failure step by step based on the drivable distance. That is, the pre-failure experience control device 2 of the second embodiment can reproduce the abnormality caused by the predicted failure that occurs during the process of traveling the drivable distance until the predicted failure occurs step by step according to the driving distance from the current time.

[0066] Specifically, the pre-failure experience control device 2 of the second embodiment can reproduce abnormal vibrations and abnormal noises caused by predicted failures at three levels of weak, medium, and strong, and can notify the driver of the range of driving distances where weak, medium, and strong abnormal vibrations and abnormal noises are likely to occur. Note that the strong-level abnormal vibrations and abnormal noises may be, for example, the abnormal vibrations and abnormal noises when a predicted failure occurs.

[0067] That is, the pre-failure experience control device 2 of the second embodiment has a plurality of control signal values for experience for each failure so that the control signal value database 402 can reproduce the abnormalities caused by the predicted failures step by step. Specifically, when the control signal value database 402 of the second embodiment reproduces abnormal vibrations and abnormal noises caused by predicted failures at three levels of weak, medium, and strong, it has control signal values for experience corresponding to the three levels of weak, medium, and strong.

[0068] The pre-failure experience control device 2 of the second embodiment notifies the driver by displaying a screen as shown in FIG. 5 on the vehicle information notification unit 301. FIG. 5 is an explanatory diagram showing an example of the screen displayed on the vehicle information notification unit 301 when experiencing the pre-failure of the predicted failure in the pre-failure experience control device 2 of the second embodiment.

[0069] FIG. 6 is a flowchart showing the flow of processing performed by the pre-failure experience control device 2 of the second embodiment.

[0070] The flowchart of FIG. 6 showing the flow of processing performed by the pre-failure experience control device 2 of the second embodiment is substantially the same as the flowchart showing the flow of processing performed by the pre-failure experience control device 1 of the first embodiment shown in FIG. 3, but includes a step S21 of predicting the driving distance (remaining driving distance) until a predicted failure occurs, a step S22 of predicting the driving distance intervals of vibrations at each level, and a step S23 of updating the driving distance until a predicted failure occurs.

[0071] Step S21 is a step that proceeds prior to step S3 when a sign of failure is detected in step S2, and predicts the travelable distance until the predicted failure occurs.

[0072] Step S22 is a step that proceeds prior to step S7 when it is determined in step S5 that the vehicle can perform a pre-failure experience, and predicts the travel distance intervals in which weak-level abnormalities, medium-level abnormalities, and high-level abnormalities occur due to the predicted failure.

[0073] Step S23 is a step that proceeds prior to step S10 when it is determined in step S9 that there is no corresponding measure for the failed component, and updates the travelable distance based on the analysis result of the data analysis unit 101. The travelable distance updated in step S23 is notified to the driver in accordance with the notice prompting the repair of the predicted failure predicted in step S10.

[0074] And the pre-failure experience control device 2 of the second embodiment reproduces step by step the abnormal vibration and abnormal noise caused by the predicted failure that occur until the predicted failure occurs in step S7.

[0075] Such a pre-failure experience control device 2 of the second embodiment can achieve substantially the same operational effects as the pre-failure experience control device 1 of the first embodiment described above.

[0076] In addition, since the pre-failure experience control device 2 of the second embodiment can reproduce step by step the abnormality caused by the predicted failure based on the travelable distance, the reliability of the driver with respect to the predicted failure can be further improved.

[0077] In addition, since the pre-failure experience control device 2 of the second embodiment can predict the remaining driving distance until a predicted failure occurs and notify the driver, the driver can specifically grasp at what timing the predicted failure will occur. Therefore, the pre-failure experience control device 2 of the second embodiment can encourage the driver's response (repair response) to the predicted vehicle failure before the predicted vehicle failure occurs.

[0078] In addition, since the pre-failure experience control device 2 of the second embodiment outputs a notice prompting the repair of the predicted failure to the driver and updates and outputs the remaining driving distance to the driver, the driver's reliability regarding the future occurrence of the predicted vehicle failure can be further improved.

[0079] Note that the pre-failure experience control device 2 of the second embodiment may use the remaining driving distance until the predicted predicted failure occurs to estimate the remaining usable time of the part where the predicted failure will occur, and inform the driver of the estimated remaining usable time together with the remaining driving distance.

[0080] The third embodiment of the present invention will be described with reference to FIGS. 7 to 9. When a vehicle failure is predicted, the pre-failure experience control device 3 of the third embodiment guides the vehicle to a location where a vehicle capable of experiencing the predicted failure is installed, enabling the pre-failure experience of the predicted failure outside the own vehicle.

[0081] FIG. 7 is a functional block diagram of the pre-failure experience control device 3 of the vehicle in the third embodiment of the present invention.

[0082] The pre-failure experience control device 3 of the third embodiment has substantially the same configuration as the pre-failure experience control device 1 of the first embodiment described above. However, as shown in FIG. 7, the failure prediction system 100 has a remaining driving distance prediction unit 105, the failure experience service system 200 has an experience designated location database 207, and further newly includes a vehicle data analysis system 500 as an external vehicle system.

[0083] The travelable distance prediction unit 105 is the same as that of the second embodiment.

[0084] The experience designated location database 207 stores information such as a prior experience service provider who can provide a vehicle for conducting a prior experience of a predicted failure, the address (experience designated location) of the prior experience service provider, the vehicle model of the vehicle that the prior experience service provider can provide, and the like. The prior experience service provider is, for example, an automobile dealership. The address of the prior experience service provider is, for example, the location of the automobile dealership. As a result, the experienceable location guidance unit 203 can guide (induce) the own vehicle to, for example, the nearest prior experience service provider from the current location. Specifically, the failure prior experience control device 3 of the third embodiment displays, on the vehicle information notification unit 301, a screen as shown in FIG. 8, showing a plurality of prior experience service providers near the current location of the vehicle and the distance from the current location of each prior experience service provider, and allows the driver to select a failure experience service provider for conducting a prior experience. Note that the distance to the location of the failure experience service provider that becomes a candidate when allowing the driver to select is shorter than the travelable distance until the predicted failure occurs.

[0085] FIG. 8 is an explanatory diagram showing an example of a screen displayed on the vehicle information notification unit 301 when selecting a prior experience service provider in the failure prior experience control device 3 of the third embodiment. As shown in FIG. 8, the failure prior experience control device 3 of the third embodiment can notify the driver of a plurality of prior experience service providers near the current location of the vehicle and the distance from the current location of each prior experience service provider.

[0086] The vehicle data analysis system 500 includes a second data analysis unit 501, a second control signal value control unit 502, and a fifth communication unit 503. The vehicle data analysis system 500 can receive various data at the fifth communication unit 503 via the first communication unit 104 of the in-vehicle failure prediction system 100. The various data are, for example, vehicle travel data, the travelable distance until a predicted failure occurs, and the control signal value for experience used when conducting a prior experience of the failure. Note that the vehicle data analysis system 500 may receive various data via a plurality of communication units among the first communication unit 104, the second communication unit 206, the third communication unit 303, and the fourth communication unit 403.

[0087] The second data analysis unit 501 extracts the control signal value for experience of the host vehicle for which a failure is predicted and the normal control signal value of the host vehicle for which a failure is predicted.

[0088] The second control signal value control unit 502 can change the control signal of the internal combustion engine to the control signal for experience in the vehicle for experience capable of performing the prior experience. When it is confirmed that the driver of the vehicle for which a failure is predicted boards the vehicle for experience, the second control signal value control unit 502 changes the control signal of the internal combustion engine to the control signal for experience at a predetermined timing to start the prior experience. The start timing of the prior experience is, for example, the timing when an instruction to start the prior experience is input from the touch panel of the car navigation system of the vehicle for experience after starting the internal combustion engine of the vehicle for experience.

[0089] FIG. 9 is a flowchart showing the flow of processing performed by the failure prior experience control device 2 of the third embodiment.

[0090] The flowchart of FIG. 9 showing the flow of processing performed by the failure prior experience control device 3 of the third embodiment is substantially the same as the flowchart showing the flow of processing performed by the failure prior experience control device 1 of the first embodiment shown in FIG. 3, but includes a step S21 of predicting the travel distance (remaining travel distance) until the predicted failure occurs, a step S23 of updating the travel distance until the predicted failure occurs, a step S31 of the driver selecting whether to perform the prior experience of the failure in the host vehicle or in the vehicle for experience, and steps S32 to S35 which are the processing when performing the prior experience of the failure in the vehicle for experience.

[0091] Step S21 is a step that proceeds before step S3 when a sign of a failure is detected in step S2, and predicts the travelable distance until the predicted failure occurs.

[0092] Step S23 is a step that proceeds prior to step S10 when it is determined that there is no corresponding measure for the component that failed in step S9, and updates the travelable distance from the analysis result of the data analysis unit 101. The travelable distance updated in step S23 is notified to the driver in accordance with the notification for prompting the repair of the predicted failure made to the driver in step S10.

[0093] Step S31 is a step that proceeds prior to step S5 when it is determined to perform a prior experience of the failure predicted in step S4, and determines whether to perform the prior experience with the own vehicle or with the above-described experience vehicle. If it is determined in step S31 to perform the prior experience with the own vehicle, the process proceeds to step S5. If it is determined in step S31 to perform the prior experience with the above-described experience vehicle, the process proceeds to step S32.

[0094] In step S32, the address (experience designated location) of the failure experience service provider, which is the location for performing the prior experience of the predicted failure, is selected. The travel distance to the address (experience designated location) of the failure experience service provider selected in step S32 is shorter than the travelable distance until the predicted failure occurs.

[0095] In step S33, the own vehicle is guided to the address (experience designated location) of the failure experience service provider selected in step S32, for example, using a car navigation system.

[0096] In step S34, at the address (experience designated location) of the selected failure experience service provider, an external system owned by the failure experience service provider is connected to the in-vehicle system of the vehicle (own vehicle) in which the failure was predicted. The external system owned by the failure experience service provider is, for example, the internal system of the above-described experience vehicle.

[0097] In step S35, driving data and the like of the vehicle (own vehicle) for which a failure has been predicted are transmitted to the vehicle data analysis system 500, which is an external system owned by the failure experience service provider. Then, a pre-experience of the failure is carried out in the above-mentioned experience vehicle. When the pre-experience of the failure in the above-mentioned experience vehicle is completed, the process proceeds to step S9.

[0098] That is, when it is selected in step S31 to conduct a pre-experience of the failure in the above-mentioned experience vehicle, the process proceeds in the order of step S32, step S33, step S34, and step S35, and a pre-experience of the failure is carried out in the above-mentioned experience vehicle.

[0099] Such a failure pre-experience control device 3 of the third embodiment can achieve substantially the same operational effects as the failure pre-experience control device 1 of the first embodiment described above.

[0100] In addition, among drivers, there may be some who do not favorably think of causing vibrations or the like in their own vehicles when a predicted failure occurs. However, the failure pre-experience control device 3 of the third embodiment enables experiencing the events that occur in the vehicle when a predicted failure occurs, even when the driver does not desire a pre-experience in their own vehicle.

[0101] In addition, the failure pre-experience control device 3 of the third embodiment guides the driver to a designated experience location where a pre-experience of the failure can be carried out based on the remaining driving distance until a predicted failure occurs. Therefore, the driver can safely pre-experience the events that occur in the vehicle when a predicted failure occurs.

[0102] As described above, specific embodiments of the present invention have been explained. However, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit thereof.

[0103] In each of the above-described embodiments, for example, when experiencing a pre-experience corresponding to a predicted failure, even if a sign of the failure corresponding to the pre-experienced failure is detected, or even if a notification prompting the implementation of the pre-experience is not provided to the driver.

[0104] In each of the above-described embodiments, viewing of a video (failure explanation video) that visualizes information on the prior experience of a predicted failure, the cause of the predicted failure, and the events that occur in the vehicle when the predicted failure occurs may be omitted according to the driver's intention. In other words, in each of the above-described embodiments, for example, in step S4 of FIGS. 3, 6, and 9, an option of "skip" may be provided in addition to the options of "Yes" and "No", and the driver may directly proceed from step S4 to step S13 in FIGS. 3, 6, and 9 according to the driver's intention.

[0105] Each of the above-described embodiments relates to a failure pre-experience control device and a failure pre-experience control method.

Explanation of Signs

[0106] 1... Failure pre-experience control device 2... Failure pre-experience control device 3... Failure pre-experience control device 100... Failure prediction system 101... Data analysis unit 102... Failure omen detection unit 103... Abnormal vibration and abnormal noise detection unit 104... First communication unit 105... Travelable distance prediction unit 200... Failure experience service system 201... Own vehicle position acquisition unit 202... Service environment judgment unit 203... Experienceable location guidance unit 204... Failure explanation video database 205... Abnormal noise database 206... Second communication unit 207... Experience designated location database 300... User interface 301... Vehicle information notification unit 302... User command input unit 303... Third communication unit 400... Engine control system 401…Control Signal Value Control Unit 402…Control Signal Value Database 403…Fourth Communication Unit 500…Vehicle Data Analysis and Analysis System 501…Second Data Analysis Unit 502…Second Control Signal Value Control Unit 503…Fifth Communication Unit

Claims

1. A failure sign detection unit that predicts a vehicle failure based on the vehicle's driving data; An execution feasibility determination unit that determines whether it is possible to perform a prior experience of an event that occurs in the vehicle when the predicted failure occurs; An execution possibility determination unit that determines whether there is a vehicle in an environment where the prior experience can be performed; A prior experience execution unit that performs the prior experience when a vehicle failure is predicted, there is a request to permit the execution of the prior experience, and there is a vehicle in an environment where the prior experience can be performed. A vehicle failure prior experience control device characterized by having.

2. The prior experience is characterized in that the control signal value of the target component of the predicted failure is changed to a predetermined failure value to pseudo-generate an event that occurs when the predicted failure occurs. The vehicle failure prior experience control device according to claim 1.

3. The event that occurs in the vehicle when the predicted failure occurs is vibration or abnormal noise. The vehicle failure prior experience control device according to claim 1.

4. When there is a request to deny the execution of the prior experience when a vehicle failure is predicted, or when there is no request to permit or deny the execution of the prior experience even after a predetermined time has elapsed since the vehicle failure was predicted, the cause of the predicted failure and the information regarding the event that occurs in the vehicle when the predicted failure occurs are output as an image. The vehicle failure prior experience control device according to claim 1.

5. The vehicle in the image is the same vehicle type as the own vehicle, and the sound in the information regarding the event that occurs in the vehicle when the predicted failure occurs is the one that occurs in the same vehicle type as the own vehicle. The vehicle failure prior experience control device according to claim 4.

6. After the execution of the prior experience, a notification prompting the repair of the predicted failure is output. The vehicle failure prior experience control device according to claim 1.

7. Calculate the remaining driving distance until the predicted failure occurs, and gradually reproduce the abnormality caused by the predicted failure that occurs during the process of driving the remaining driving distance. The vehicle failure prior experience control device according to any one of claims 1 to 5.

8. After detecting the abnormality caused by the predicted failure that occurs during the process of driving the remaining driving distance, a notification prompting the repair of the predicted failure is output, and the remaining driving distance is updated and output. The vehicle failure prior experience control device according to claim 7.

9. The vehicle pre-failure experience control device according to claim 7, characterized in that guidance to an experience designated location where the preset pre-experience can be implemented is performed based on the above-mentioned travelable distance.

10. The vehicle pre-failure experience control device according to claim 9, characterized in that the experience designated location is the location of a store that can provide the above-mentioned pre-experience with a vehicle other than the own vehicle.

11. There is a request to enable the implementation of a pre-experience of an event that occurs in a vehicle when a vehicle failure is predicted and the predicted failure occurs. When the vehicle is in an environment where the above-mentioned pre-experience can be implemented, the vehicle pre-failure experience control method characterized by implementing the above-mentioned pre-experience.

Images