Fault diagnosis system
The fault diagnosis system enhances vehicle fault diagnosis accuracy by establishing appropriate data ranges and using simulation to match actual and virtual driving results, addressing misdiagnosis issues caused by manufacturing variations.
Patent Information
- Application Number
- JP2020150675
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-09-08
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2040-09-08
AI Technical Summary
Existing vehicle fault diagnosis systems are prone to misdiagnosis due to individual differences among vehicles resulting from manufacturing variations.
A fault diagnosis system that utilizes driving environment data, including driving operation and external environment data, to determine appropriate ranges for actual driving results, employs a vehicle simulation model to simulate vehicle operations, and identifies failure parts by matching virtual driving results with actual results.
Improves the accuracy of vehicle fault diagnosis by reducing misdiagnosis and identifying specific failure parts through statistical analysis and simulation.
Smart Images

Figure 0007587374000001 
Figure 0007587374000002 
Figure 0007587374000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a fault diagnosis system. [Background technology]
[0002] For example, Patent Document 1 discloses a fault diagnosis device that diagnoses a fault that occurs in a vehicle. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2006-349429 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, there are individual differences between vehicles due to manufacturing reasons, and therefore, when diagnosing a fault in a vehicle, an erroneous diagnosis may be made depending on the vehicle.
[0005] SUMMARY OF THE PRESENT EMBODIMENTS Accordingly, an object of the present invention is to provide a fault diagnosis system capable of improving the accuracy of fault diagnosis for a vehicle. [Means for solving the problem]
[0006] In order to solve the above problems, a fault diagnosis system according to one embodiment of the present invention includes a data acquisition unit that acquires driving environment data including at least driving operation data indicating driving operations for a target vehicle that is the subject of fault diagnosis, and actual driving result data indicating actual driving results based on the driving environment data, in association with each other; an appropriate range setting unit that derives an appropriate range of the actual driving results based on the driving environment data for a vehicle of the same model as the target vehicle; and a fault judgment unit that judges whether or not the target vehicle has a fault by judging whether or not the actual driving result data is within the appropriate range. a vehicle simulation model that simulates the operation of a vehicle on a computer; and a faulty part identification unit that, when it is determined by the fault determination unit that the target vehicle has a fault, repeats the process of performing a simulation using driving environment data as input data for the vehicle simulation model to derive virtual driving result data that shows a virtual driving result, while changing parameters of the vehicle simulation model, and, when the virtual driving result data matches the actual driving result data, identifies a part of the vehicle simulation model related to the changed parameters as a faulty part. Equipped with. Effect of the Invention
[0008] According to the present invention, it is possible to improve the accuracy of vehicle fault diagnosis. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a schematic diagram showing the configuration of a fault diagnosis system according to this embodiment. [Diagram 2] FIG. 2 is a diagram for explaining the appropriate range of actual driving result data and the determination of the presence or absence of a malfunction. FIG. 2A shows an example of actual driving result data of another vehicle. FIG. 2B shows an example of the appropriate range. FIG. 2C shows an example of actual driving result data of a target vehicle. [Diagram 3] FIG. 3 is a flowchart illustrating the flow of processing the data received from the vehicle. [Figure 4] FIG. 4 is a flowchart illustrating the flow of operations of the failure determination unit. [Diagram 5] FIG. 5 is a diagram for explaining the vehicle simulation model. [Figure 6] Fig. 6 is a diagram explaining the relationship between the vehicle simulation model and vehicle failure. Fig. 6A and Fig. 6B show the relationship between the actual driving result data and the hypothetical driving result data when the target vehicle has no failure. Fig. 6C and Fig. 6D show the relationship between the actual driving result data and the hypothetical driving result data when the target vehicle has a failure. [Figure 7] 7A and 7B are diagrams for explaining the relationship between a vehicle simulation model and identification of a faulty part. FIG. 7A and FIG. 7B show an example of a process for identifying a faulty part. FIG. 7C and FIG. 7D show an example in which a faulty part is identified. [Figure 8] FIG. 8 is a flowchart illustrating the flow of operations of the failed part identifying unit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings. The dimensions, materials, and other specific numerical values shown in the embodiment are merely examples for facilitating understanding of the invention, and do not limit the present invention unless otherwise specified. In this specification and drawings, elements having substantially the same functions and configurations are given the same reference numerals to avoid repeated explanations, and elements not directly related to the present invention are not shown.
[0011] FIG. 1 is a schematic diagram showing the configuration of a fault diagnosis system 1 according to this embodiment. The fault diagnosis system 1 includes a plurality of vehicles 10 and a management server 12. The vehicles 10 may be engine vehicles, electric vehicles, or hybrid vehicles. In FIG. 1, four vehicles 10a, 10b, 10c, and 10d are illustrated as the plurality of vehicles 10. Hereinafter, the vehicles 10a, 10b, 10c, and 10d may be collectively referred to as vehicles 10. The number of vehicles 10 is not limited to four, and may be two, three, five, or more, as long as it is more than one.
[0012] The fault diagnosis system 1 performs fault diagnosis to determine whether a specific vehicle 10 among a plurality of vehicles 10 has a fault. Hereinafter, the vehicle 10 that is the subject of the fault diagnosis may be referred to as the target vehicle. Also, vehicles other than the target vehicle, i.e., vehicles that are not the subject of the fault diagnosis, may be simply referred to as other vehicles. For example, in FIG. 1, the target vehicle is vehicle 10a, and the other vehicles are vehicles 10b, 10c, and 10d. Note that the target vehicle is not limited to vehicle 10a, and may be arbitrarily selected from the plurality of vehicles 10.
[0013] The vehicle 10 includes a vehicle control unit 20 and a vehicle communication unit 22. The vehicle control unit 20 is configured from a semiconductor integrated circuit including a central processing unit, a ROM in which programs and the like are stored, a RAM as a work area, and the like.
[0014] The vehicle control unit 20 acquires data indicating driving operations such as acceleration, deceleration, and steering of the vehicle through an accelerator sensor, a brake sensor, a shift sensor, a steering angle sensor, and the like (not shown). The vehicle control unit 20 also acquires data indicating the vehicle exterior environment through various detection devices such as a radar, an infrared sensor, a camera, and a temperature sensor. The vehicle exterior environment may be various elements that affect the driving of the vehicle, such as gradient, road surface condition, weather, wind direction, wind speed, outside temperature, and air pressure.
[0015] Hereinafter, data indicating driving operations may be referred to as driving operation data. Data indicating the vehicle exterior environment may be referred to as vehicle exterior environment data. Driving operation data and vehicle exterior environment data may be collectively referred to as driving environment data. The driving environment data may include at least the driving operation data, and the vehicle exterior environment data may be omitted.
[0016] The vehicle control unit 20 controls the entire vehicle 10, such as driving, braking, or steering, based on the driving environment data. The vehicle control unit 20 can also acquire data indicating actual driving results through various sensors, such as a rotation speed sensor (not shown). Hereinafter, data indicating actual driving results may be referred to as actual driving result data. Examples of actual driving result data include, for example, the rotation speed of the wheels, the speed of the vehicle 10, or the acceleration of the vehicle 10. The actual driving result data may also be an intermediate output result of the vehicle 10, such as the engine rotation speed. The vehicle control unit 20 associates the driving environment data with the actual driving result data acquired based on the driving environment data.
[0017] The vehicle communication unit 22 is capable of wireless communication with communication devices outside the vehicle, such as the management server 12. The vehicle control unit 20 periodically transmits the driving environment data, the actual driving result data, and the vehicle identification data to the management server 12 via the vehicle communication unit 22. The vehicle identification data is data that can identify the vehicle. The vehicle identification data includes vehicle type data that indicates the model of the vehicle.
[0018] The management server 12 is installed, for example, by an administrator of the fault diagnosis system 1. The management server 12 includes a server communication unit 30, a data storage unit 32, a server control unit 34, and a vehicle simulation model 36. The server communication unit 30 is capable of wireless communication with, for example, each of the multiple vehicles 10. The data storage unit 32 is composed of a non-volatile storage element.
[0019] The server control unit 34 is composed of a semiconductor integrated circuit including a central processing unit, a ROM in which programs and the like are stored, a RAM as a work area, etc. The server control unit 34 functions as a data acquisition unit 40, an appropriate range setting unit 42, a failure determination unit 44, and a failed part identification unit 46 by executing the programs.
[0020] The data acquisition unit 40 acquires, in association with each other, the driving environment data, the actual driving result data, and the vehicle identification data transmitted from each vehicle 10 via the server communication unit 30. The data acquisition unit 40 acquires, in association with each other, the driving environment data and the actual driving result data based on the driving environment data for all vehicles 10 including the target vehicle. The data acquisition unit 40 stores the acquired driving environment data, the actual driving result data, and the vehicle identification data in the data storage unit 32.
[0021] The appropriate range setting unit 42 derives an appropriate range of the actual driving result data for each driving environment data based on the driving environment data and actual driving result data of one or more vehicles. The appropriate range setting unit 42 updates the appropriate range each time the driving environment data and actual driving result data are acquired. The appropriate range of the actual driving result data becomes a criterion for determining whether or not the target vehicle has a malfunction. The appropriate range will be described in detail later.
[0022] The malfunction determination unit 44 determines whether or not the target vehicle has a malfunction by determining whether or not the actual driving result data of the target vehicle is within an appropriate range. The malfunction determination unit 44 will be described in detail later.
[0023] When it is determined that the target vehicle has a fault, the faulty part identifying unit 46 identifies the faulty part by using the vehicle simulation model 36. The vehicle simulation model 36 is software that simulates the operation of the vehicle 10 on a computer. The vehicle simulation model 36 is stored in a storage medium (not shown). The vehicle simulation model 36 is executed by hardware such as the server control unit 34, thereby simulating the operation of the vehicle 10. The vehicle simulation model 36 and the faulty part identifying unit 46 will be described in detail later.
[0024] FIG. 2 is a diagram for explaining the appropriate range of actual driving result data and determining whether or not there is a malfunction. FIG. 2A shows an example of actual driving result data of another vehicle. In FIG. 2A, solid line A10b shows the actual driving result data of vehicle 10b, solid line A10c shows the actual driving result data of vehicle 10c, and solid line A10d shows the actual driving result data of vehicle 10d. FIG. 2B shows an example of the appropriate range. FIG. 2C shows an example of actual driving result data of a target vehicle. In FIG. 2A to FIG. 2C, as an example of actual driving result data, the time progression of engine rotation speed at engine start is shown.
[0025] The data acquisition unit 40 classifies the driving environment data and actual driving result data acquired from the vehicle 10 by vehicle type of the vehicle 10, and sequentially stores the data in the data storage unit 32. The data acquisition unit 40 also classifies the acquired driving environment data and actual driving result data by situation, and sequentially stores the data in the data storage unit 32.
[0026] A situation indicates a situation where a malfunction is likely to occur, such as when the engine is started or when the vehicle is traveling at a constant low speed. A situation is set in advance for each type of vehicle 10 by an administrator of the management server 12 or the like. A predetermined condition indicating a representative example of the traveling environment data is associated with each set situation. This predetermined condition serves as a judgment criterion for distinguishing the traveling environment data for each situation. When the acquired traveling environment data satisfies the above-mentioned predetermined condition, the data acquisition unit 40 classifies the traveling environment data and the actual traveling result data for a predetermined time range that satisfies the predetermined condition into a situation corresponding to the predetermined condition.
[0027] 2A shows an example of actual driving result data associated with driving environment data at engine start for vehicles 10a, 10b, and 10c of the same vehicle type as the target vehicle. In FIG. 2A, the actual driving result data at engine start is shown for vehicles 10a, 10b, and 10c at the same time. As shown in FIG. 2A, the actual driving result data of multiple vehicles 10 show similar trends because the vehicles 10 have the same vehicle type and driving environment data.
[0028] The appropriate range setting unit 42 performs statistical processing on a plurality of actual driving result data having common vehicle type and driving environment data to derive an appropriate range for the actual driving result data. The appropriate range setting unit 42 derives an appropriate range for the actual driving result data for each vehicle type and driving environment data. The dashed line A20a in FIG. 2B shows an example of an upper limit value of the appropriate range, and the dashed line A20b shows an example of a lower limit value of the appropriate range. The appropriate range is an area sandwiched between the dashed lines A20a and A20b. For example, the appropriate range setting unit 42 may set the value obtained by adding 3σ to the average value of the plurality of actual driving result data as the upper limit value of the appropriate range, and the value obtained by subtracting 3σ from the average value as the lower limit value of the appropriate range. σ indicates the standard deviation.
[0029] The upper and lower limits of the appropriate range may be derived by any method other than the addition and subtraction of 3σ based on the average value. The appropriate range setting unit 42 may change the value of 3σ to, for example, 2σ or 4σ for each vehicle model or driving environment data, to make the width of the appropriate range different for each vehicle model or driving environment data.
[0030] As shown in FIG. 2C, the failure determination unit 44 compares the actual driving result data associated with the driving environment data of a predetermined situation, such as when starting the engine, of the target vehicle, as illustrated by the solid line A10a, with the appropriate range of the actual driving result data based on the driving environment data of the same situation. If the actual driving result data of the target vehicle is included in the appropriate range data, the failure determination unit 44 determines that the target vehicle has no failure. On the other hand, if at least a part of the actual driving result data of the target vehicle falls outside the appropriate range within a predetermined time range corresponding to the situation, the failure determination unit 44 determines that the target vehicle has a failure. In the example of FIG. 2C, the actual driving result data of the target vehicle has a part that exceeds the upper limit value of the appropriate range, so the failure determination unit 44 determines that the target vehicle has a failure.
[0031] 3 is a flowchart illustrating the flow of processing data received from the vehicles 10. When the data acquisition unit 40 receives the driving environment data and the actual driving result data from any of the vehicles 10, the data acquisition unit 40 performs the series of processes shown in FIG.
[0032] First, the data acquisition unit 40 classifies the received driving environment data and actual driving result data by vehicle type based on the vehicle type data received together with the driving environment data and actual driving result data (S100).
[0033] Next, the data acquisition unit 40 classifies the received driving environment data and actual driving result data for each driving environment data of a predetermined situation (S110). Specifically, the data acquisition unit 40 classifies the driving environment data by determining for each predetermined condition whether the driving environment data satisfies a predetermined condition for each situation.
[0034] Next, the data acquisition unit 40 stores the driving environment data and the actual driving result data in the data storage unit 32 for each of the classified vehicle types and driving environment data (S120).
[0035] Next, the appropriate range setting unit 42 derives an appropriate range of the actual driving result data for the classified vehicle type and driving environment data (S130). Specifically, the appropriate range setting unit 42 reads out a plurality of actual driving result data associated with the classified vehicle type and driving environment data, performs statistical processing, and derives an appropriate range. Next, the appropriate range setting unit 42 stores the derived appropriate range in the data storage unit 32, and updates the appropriate range (S140).
[0036] Fig. 4 is a flowchart explaining the flow of operations of the failure determination unit 44. For example, the administrator of the management server 12 sets the vehicle 10 for which a failure diagnosis is to be performed as a target vehicle, and issues an instruction to start the failure diagnosis to the server control unit 34. Upon receiving the instruction to start the diagnosis, the failure determination unit 44 carries out the series of processes shown in Fig. 4.
[0037] First, the failure determination unit 44 reads out actual driving result data for each driving environment data of a predetermined situation in the target vehicle from the data storage unit 32 (S200). The failure determination unit 44 is not limited to reading out the actual driving result data from the data storage unit 32, and may perform subsequent processing using actual driving result data newly acquired from the target vehicle.
[0038] Next, the malfunction determination unit 44 reads out the appropriate range for each driving environment data of a predetermined situation for the same vehicle model as the target vehicle from the data storage unit 32 (S210). Next, the malfunction determination unit 44 determines whether the actual driving result data of the target vehicle is included in the appropriate range for the same vehicle model and driving environment data as the target vehicle (S220).
[0039] If the actual driving result data is within the appropriate range, that is, if the actual driving result data does not deviate from the appropriate range (NO in S220), the malfunction judgment unit 44 determines that the target vehicle has no malfunction and notifies the user that there is no malfunction (S230). On the other hand, if the actual driving result data deviates from the appropriate range (YES in S230), the malfunction judgment unit 44 determines that the target vehicle has a malfunction and notifies the user that there is a malfunction (S240). The malfunction judgment unit 44 may, for example, display the presence or absence of a malfunction on a display (not shown) of the management server 12.
[0040] FIG. 5 is a diagram for explaining the vehicle simulation model 36. The vehicle simulation model 36 includes models that simulate each function of the vehicle 10, such as an engine model, a transmission model, or a hybrid model. The models that simulate each function include either or both of a control model and a plant model. The control model is software similar to a control program used in the actual vehicle 10. The plant model is software that simulates a physical phenomenon or a mechanism, such as the operation of an actuator. The vehicle simulation model 36 may be created by machine learning using driving environment data as input sample data and actual driving result data as output sample data.
[0041] The vehicle simulation model 36 receives driving environment data of the vehicle 10 as input data. As described above, the driving environment data includes driving operation data indicating driving operations and vehicle exterior environment data indicating the vehicle exterior environment. When the driving environment data is input, the vehicle simulation model 36 internally simulates each function and outputs virtual driving result data indicating a virtual driving result.
[0042] In addition, various parameters are set in the vehicle simulation model 36. The parameters are data that are used directly or indirectly in the process of deriving the virtual driving result data from the driving environment data. The parameters may be variables that change depending on the driving environment data, or may be constants that are unique to the vehicle 10. Examples of the parameters include a throttle opening, an engine ignition timing, a fuel injection amount, an EGR flow rate, or a clutch friction coefficient.
[0043] The parameters are associated with specific parts of the vehicle 10 depending on the specific parameter type. Hereinafter, the parts of the vehicle 10 associated with the parameters may be referred to as parameter-related parts. Note that a plurality of parameter-related parts may be associated with one type of parameter.
[0044] The parameter-related parts are the elements that configure the vehicle 10, such as mechanisms, parts, components, members, circuits, or software. For example, if the parameter is a clutch friction coefficient, the parameter-related part is a clutch. For example, if the parameter is engine ignition timing, the parameter-related part is a spark plug.
[0045] Fig. 6 is a diagram for explaining the relationship between the vehicle simulation model 36 and a fault in the vehicle 10. Fig. 6A and Fig. 6B show the relationship between the actual driving result data and the hypothetical driving result data when the target vehicle has no fault. Fig. 6C and Fig. 6D show the relationship between the actual driving result data and the hypothetical driving result data when the target vehicle has a fault.
[0046] 6A, the vehicle simulation model 36 simulates a vehicle 10 that is free of any faults, i.e., a normal vehicle 10. In this state, the parameters of the vehicle simulation model 36 have normal values. Since the normal parameters are reflected in the driving environment data, the vehicle simulation model 36 outputs normal virtual driving result data.
[0047] If the target vehicle has no malfunction, the actual driving result data actually acquired from the target vehicle should have normal values. Therefore, if the driving environment data actually given to the target vehicle and the driving environment data input to the vehicle simulation model are the same, the virtual driving result data and the actual driving result data will match, as shown in FIG. 6A.
[0048] For example, as shown in FIG. 6B, for the driving environment data at the time of engine start, the actual driving result data of a normal target vehicle indicated by a solid line B10 matches the virtual driving result data indicated by a dashed line C10.
[0049] Incidentally, the agreement between the virtual driving result data and the actual driving result data may be such that there is a difference within a predetermined range that allows measurement errors in the actual vehicle 10 or calculation errors in the vehicle simulation model 36 to be tolerated.
[0050] The vehicle simulation model 36 in FIG. 6C has normal parameter values, and outputs normal virtual driving result data, similar to the vehicle simulation model 36 in FIG. 6A. However, in FIG. 6C, it is assumed that the target vehicle has a malfunction. In this case, the actual driving result data actually acquired from the target vehicle should be different from the normal data. For this reason, even if the driving environment data actually given to the target vehicle and the driving environment data input to the vehicle simulation model 36 are the same, the virtual driving result data and the actual driving result data do not match, as shown in FIG. 6C.
[0051] For example, as shown in FIG. 6D, for the driving environment data at engine start, the actual driving result data of a target vehicle with a fault, indicated by a solid line A10a, does not match the normal hypothetical driving result data, indicated by a dashed line C10.
[0052] Considering these, if the virtual driving result data can be made to match the actual driving result data of a target vehicle having a fault, the target vehicle having a fault can be simulated by the vehicle simulation model 36. Then, as will be described later, it becomes possible to identify the faulty part of the target vehicle having a fault.
[0053] Fig. 7 is a diagram for explaining the relationship between the vehicle simulation model 36 and identification of a faulty part. Fig. 7A and Fig. 7B show an example of a process for identifying a faulty part. Fig. 7C and Fig. 7D show an example in which a faulty part is identified. In Fig. 7A to Fig. 7D, the driving environment data input to the vehicle simulation model 36 is assumed to be the same as the driving environment data actually given to a target vehicle having a fault.
[0054] 7A, the failure part identification unit 46 intentionally changes any parameter of the vehicle simulation model 36 from the normal state. Changing the parameter corresponds to making the vehicle simulation model 36 simulate a state of the vehicle 10 that is different from the normal state. Then, the vehicle simulation model 36 outputs virtual running result data that reflects the changed parameters. The virtual running result data that reflects the changed parameters indicates values that are different from the normal virtual running result data.
[0055] The faulty part identification unit 46 judges whether the virtual driving result data after changing the parameters matches the actual driving result data of the target vehicle having a fault. The dashed line C20 in Fig. 7B shows an example of the virtual driving result data after changing an arbitrary parameter. In Fig. 7B, even though the arbitrary parameter has been changed, the virtual driving result data shown by the dashed line C20 still does not match the actual driving result data shown by the solid line A10a.
[0056] Therefore, the faulty part identifying unit 46 further changes the parameters as shown in Fig. 7C. The faulty part identifying unit 46 may also change other parameters. If the parameters are further changed, the virtual running result data also changes further. Then, the faulty part identifying unit 46 again determines whether the virtual running result data after the parameters are changed matches the actual running result data of the target vehicle having a fault.
[0057] As shown in Fig. 7C, it is assumed that the virtual driving result data after changing the parameters matches the actual driving result data. For example, as shown in Fig. 7D, it is assumed that the virtual driving result data shown by the dashed line C30 matches the actual driving result data shown by the solid line A10a. In this case, the vehicle simulation model 36 can be considered to be simulating a target vehicle having a malfunction. In this case, the changed parameters of the vehicle simulation model 36 correspond to parameters that have changed due to the malfunction.
[0058] Therefore, the faulty part identifying unit 46 repeats the process of changing the parameters of the vehicle simulation model 36 and deriving the virtual running result data until the virtual running result data matches the actual running result data of the target vehicle. Then, the faulty part identifying unit 46 identifies the part of the vehicle simulation model 36 related to the changed parameters when the virtual running result data matches the actual running result data of the target vehicle as the faulty part.
[0059] The agreement between the virtual driving result data and the actual driving result data may be such that there is a difference within a predetermined range that allows for measurement errors in the target vehicle or calculation errors in the vehicle simulation model 36, for example.
[0060] The failure part identification unit 46 may determine that the virtual driving result data and the actual driving result data match when the transition of the absolute value of the value obtained by subtracting the actual driving result data from the virtual driving result data falls within a predetermined range. The failure part identification unit 46 may also determine that the virtual driving result data and the actual driving result data match when the square mean value of the value obtained by subtracting the actual driving result data from the virtual driving result data, averaged over a predetermined time range, is less than a predetermined value.
[0061] In the fault diagnosis system 1, a large number of test cases are set in advance in the server control unit 34. A test case is set for each possible fault mode. The type and amount of change of parameters to be changed in the vehicle simulation model 36 are associated with each test case.
[0062] The faulty part identification unit 46 determines the priority order of the test cases based on the actual driving result data in which it is determined that there is a fault and the driving environment data on which the data is based. For example, the faulty part identification unit 46 roughly classifies the fault of the target vehicle into major categories such as a drive system fault, a steering system fault, or an electrical system fault, based on the driving environment data. For example, in the case of driving environment data at the time of engine start, the faulty part identification unit 46 classifies the fault as a drive system fault.
[0063] A plurality of medium-sized items are associated with the large-sized items. For example, a drivetrain failure is associated with a transmission failure, a gear failure, a torque fluctuation failure, etc. The faulty part identification unit 46 analyzes the actual driving result data in which a failure is determined to exist, and classifies the failure of the target vehicle by the medium-sized item.
[0064] For example, when the faulty part identification unit 46 estimates that there is a mismatch in the rotation speed of each part from the power source to the axle in the actual driving result data of the target vehicle, it classifies it as a transmission failure. Also, when the faulty part identification unit 46 estimates that there is no transmission failure and that there is a rotation fluctuation before and after the speed change mechanism, it classifies it as a gear shift failure. Also, when the faulty part identification unit 46 estimates that there is neither a transmission failure nor a gear shift failure, it classifies it as a torque fluctuation failure.
[0065] A plurality of small items are associated with the medium item. For example, a torque fluctuation fault is associated with throttle, ignition, fuel, EGR, variable valve timing, and the like. The faulty part identification unit 46 compares the change rate of the physical quantity in the actual driving result data of the target vehicle with the change rate that can physically occur in the small items. The faulty part identification unit 46 prioritizes the small items in the order in which the change rate in the small items is closest to the change rate in the target vehicle.
[0066] For example, the rate of change of a physical quantity in the actual driving result data of the target vehicle is the rate of change of the rotation speed, which is 3500 rpm / sec. The rate of change of the rotation speed caused by the change in generated torque related to the throttle is 1000 rpm / sec. The rate of change of the rotation speed related to the ignition is 4000 rpm / sec. The rate of change of the rotation speed related to the fuel is 2500 rpm / sec. The rate of change of the rotation speed related to the EGR is 2000 rpm / sec. The rate of change of the rotation speed related to the variable valve timing is 1000 rpm / sec. In this example, the failure part identification unit 46 determines the priority order in the following order: ignition, fuel, EGR, variable valve timing, and throttle.
[0067] These small items are associated with test cases. That is, the failure part identification unit 46 prioritizes the small items, and as a result, determines the priority of the test cases. In the above example, the failure part identification unit 46 assigns the highest priority to the test case for ignition.
[0068] The faulty part identifying unit 46 executes the test cases in order of priority. Specifically, the faulty part identifying unit 46 changes the parameters indicated by the test cases with the highest priority in the vehicle simulation model 36. For example, the faulty part identifying unit 46 changes the ignition timing, which is a parameter indicated by the test case for ignition. This allows the faulty part identifying unit 46 to identify the faulty part earlier than in a mode in which the parameters are changed randomly.
[0069] Fig. 8 is a flowchart illustrating the flow of operations of the faulty part identification unit 46. When the fault determination unit 44 determines that the target vehicle has a fault, the faulty part identification unit 46 performs a series of processes in Fig. 8.
[0070] First, the faulty part identification unit 46 determines the priority of the test cases based on the actual driving result data in which it is determined that there is a fault and the driving environment data on which the data is based (S300). Next, the faulty part identification unit 46 determines the test case with the highest priority as the test case to be executed (S310). Next, the faulty part identification unit 46 changes the parameters in the vehicle simulation model 36 that correspond to the test case determined in step S310 (S320).
[0071] Next, the failure part identification unit 46 inputs the driving environment data of the target vehicle to the vehicle simulation model 36 in a state in which the parameters have been changed in step S320, and derives virtual driving result data (S330). Next, the failure part identification unit 46 determines whether the driving environment data of the target vehicle matches the derived virtual driving result data (S340).
[0072] If the driving environment data of the target vehicle matches the virtual driving result data (YES in S340), the faulty part identifying unit 46 identifies the part related to the parameter changed in step S320 as the faulty part (S350), and ends the series of processes.
[0073] If the driving environment data of the target vehicle does not match the virtual driving result data (NO in S340), the faulty part identification unit 46 judges whether the test case being executed is to end (S360). If the test case being executed is not to end (NO in S360), the faulty part identification unit 46 returns to step S320 and further changes the parameters (S320).
[0074] When the test case being executed is to end (YES in S360), the faulty part identification unit 46 judges whether or not there is a next test case (S370). When there is a next test case (YES in S370), the faulty part identification unit 46 returns to the process of step S310 and determines the test case with the next highest priority as the test case to be executed (S310).
[0075] If there is no next test case (NO in S370), the faulty part identifying section 46 notifies the user that the faulty part could not be identified (S370), and ends the series of processes.
[0076] As described above, the optimum range setting unit 42 of the fault diagnosis system 1 according to this embodiment derives an optimum range of the actual driving results based on the driving environment data for a vehicle of the same model as the target vehicle. The fault determination unit 44 then determines whether or not the target vehicle has a fault by determining whether or not the actual driving result data of the target vehicle is within the optimum range. In the fault diagnosis system 1 according to this embodiment, if the actual driving result data of the target vehicle falls within the optimum range, it is not determined that the target vehicle has a fault, so that erroneous diagnosis of a fault can be suppressed even if there are individual differences due to the manufacture of the vehicle 10.
[0077] Therefore, according to the fault diagnosis system 1 of the present embodiment, the accuracy of fault diagnosis of the vehicle 10 can be improved.
[0078] Furthermore, when it is determined that the target vehicle has a fault, the faulty part identifying unit 46 of the fault diagnosis system 1 of this embodiment repeatedly derives the virtual running result data while changing the parameters of the vehicle simulation model. Then, when the virtual running result matches the actual running result data, the faulty part identifying unit 46 identifies the part of the vehicle simulation model related to the changed parameters as the faulty part.
[0079] Therefore, the fault diagnosis system 1 of the present embodiment can specify not only the presence or absence of a fault but also the failed part, thereby making it possible to further improve the accuracy of fault diagnosis.
[0080] In the present embodiment, the appropriate range setting unit 42 sequentially derives the appropriate range each time the driving environment data and the actual driving result data are acquired from any of the vehicles 10. However, the appropriate range setting unit 42 may omit deriving the appropriate range when the driving environment data and the actual driving result data are acquired, and derive the appropriate range when an instruction to start a fault diagnosis is received.
[0081] In addition, the appropriate range setting unit 42 of this embodiment derives the appropriate range for each vehicle type and driving environment data for all vehicles 10 including the target vehicle. Since the population for deriving the appropriate range is large, the appropriate range can be derived with high accuracy even if the actual driving result data of the target vehicle is reflected in the derivation of the appropriate range. Furthermore, when the target vehicle is known in advance, the appropriate range setting unit 42 may derive the appropriate range for each vehicle type and driving environment data for vehicles other than the target vehicle.
[0082] Although the embodiment of the present invention has been described above with reference to the attached drawings, it goes without saying that the present invention is not limited to such an embodiment. It is clear that a person skilled in the art can think of various modified or altered examples within the scope of the claims, and it is understood that such examples also naturally belong to the technical scope of the present invention. [Explanation of symbols]
[0083] 1. Fault diagnosis system 10, 10a, 10b, 10c, 10d Vehicles 36 Vehicle Simulation Model 40 Data Acquisition Section 42 Appropriate range setting section 44 Failure determination section 46 Failure part identification part
Claims
[Claim 1] A data acquisition unit that acquires driving environment data including at least driving operation data indicating driving operations of a target vehicle that is a target of a fault diagnosis, and actual driving result data indicating an actual driving result based on the driving environment data, in association with each other; an appropriate range setting unit that derives an appropriate range of an actual driving result based on the driving environment data for a vehicle of the same model as the target vehicle; a failure determination unit that determines whether or not the actual driving result data is within the appropriate range to determine whether or not the target vehicle has a failure; A vehicle simulation model that simulates the operation of a vehicle on a computer; a fault part identification unit which, when it is determined by the fault determination unit that the target vehicle has a fault, performs a simulation using the driving environment data as input data for the vehicle simulation model to derive virtual driving result data showing a virtual driving result, while changing parameters of the vehicle simulation model, and identifies a part of the vehicle simulation model related to the changed parameters when the virtual driving result data coincides with the actual driving result data as a fault part; A fault diagnosis system comprising:
Citation Information
Patent Citations
Trouble diagnosing device
JP2006349429A
Remote failure diagnostic system
JP2008001233A
Failure diagnosis device for vehicle
JP2010137644A
Correction value generation apparatus, fault diagnosis apparatus, correction value generation program, and fault diagnosis program
JP2015158421A
Telecommunication system for vehicle
JP2017216580A
