WO2005103630A1 - 診断装置およびその方法 - Google Patents
診断装置およびその方法 Download PDFInfo
- Publication number
- WO2005103630A1 WO2005103630A1 PCT/JP2004/005931 JP2004005931W WO2005103630A1 WO 2005103630 A1 WO2005103630 A1 WO 2005103630A1 JP 2004005931 W JP2004005931 W JP 2004005931W WO 2005103630 A1 WO2005103630 A1 WO 2005103630A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- diagnostic
- measurement
- diagnosis
- state
- measured value
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D1/00—Measuring arrangements giving results other than momentary value of variable, of general application
- G01D1/18—Measuring arrangements giving results other than momentary value of variable, of general application with arrangements for signalling that a predetermined value of an unspecified parameter has been exceeded
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
Definitions
- the present invention relates to a diagnostic apparatus and method for diagnosing and monitoring the operation and state change of a measurement target based on a measurement value obtained from the measurement target.
- Patent Document 1 discloses a method for detecting a failure in a control system using an operation model.
- Patent Document 1 cannot be applied to such devices.
- Patent Document 1 Japanese Patent Application Laid-Open No. 57-417080 Disclosure of the Invention
- the present invention has been made in view of the above-described background, and has as its object to provide a diagnostic apparatus and a diagnostic method capable of diagnosing and monitoring changes in the operation Z state of a diagnosis target without using an operation model. I do.
- Another object of the present invention is to provide a diagnostic device and a diagnostic method which can be easily applied to diagnosis of a subject having a large individual difference, such as a small number of diagnostic targets to be produced and diagnostic targets under development. .
- a diagnostic apparatus comprises: a validity determination unit configured to determine whether a measurement value obtained by measuring a measurement target over time is valid; Each time is determined to be legitimate, using a measured value determined to be legitimate, a reference generating means for generating a diagnostic reference used for diagnosis of the measurement object, Diagnostic means for diagnosing the measurement target based on the generated diagnostic criteria.
- the measurement object transitions between a plurality of states, and a state determination unit that determines which state the measurement object is in using the measured value determined to be valid.
- the criterion creating means generates the diagnostic criterion according to the state of the measurement target.
- the measurement object transitions between a plurality of states, and a state determination unit that determines which state the measurement object is in using the measured value determined to be valid. Further, the diagnosis means diagnoses the measurement target according to the state of the measurement target.
- the validity determining means includes a measurement value obtained at a timing other than a predetermined timing, a measurement value inevitably including an error when measuring the measurement target, and a value outside a preset range. The measured value, or any combination of any one or more of these, is judged to be valid.
- the criterion generating unit statistically processes the measurement values of the type to create the diagnostic criterion.
- the diagnostic means determines that the measurement target is normal when the measured value is within a predetermined range from a central value of the measured value obtained by the statistical processing.
- the diagnosing means is configured such that, when the measured value takes a value out of a predetermined range from a central value of the measured value, a predetermined number of times or more, and a predetermined frequency or more, or Except for any of the cases, the measurement target is determined to be normal.
- a transport means including a component to be measured, and a method for determining whether or not a measured value obtained by measuring the measured object over time is valid.
- the diagnostic method according to the present invention determines whether or not a measured value obtained by measuring the measurement object over time is valid, and every time the measured value is determined to be valid, _
- the program according to the present invention includes a validity determining step of determining whether a measured value obtained by measuring a measurement target over time is valid, and determining that the measured value is valid. Each time, using the measured value determined to be valid, a reference generating step of generating a diagnostic criterion used for diagnosing the measurement target, and diagnosing the measurement target based on the generated diagnostic criterion. A diagnostic step for performing the procedure is executed overnight.
- a diagnostic object can be diagnosed without using an operation model.
- the diagnostic apparatus and the method according to the present invention can be easily applied to diagnosis and monitoring of a large number of individual differences, such as a small number of diagnostic targets to be produced and diagnostic targets under development.
- FIG. 1 is a diagram showing an operation diagnosis system according to the present invention.
- FIG. 2 is a diagram illustrating a hardware configuration of the data collection device and the operation diagnosis device shown in FIG.
- FIG. 3 is a diagram showing a data collection program that operates on the data collection device shown in FIGS. 1 and 2.
- FIG. 4 is a diagram showing a first operation diagnosis program that operates on the operation diagnosis device shown in FIGS. 1 and 2.
- FIG. 5 is a diagram illustrating a state of the engine (FIG. 1).
- FIG. 6 is a flowchart illustrating the operation (S10) of the state management unit of the first operation diagnostic program shown in FIG.
- FIG. 7 is a diagram illustrating the timing of measured value data to be diagnosed. _
- FIG. 8 is a first diagram exemplifying diagnostic reference data generated by the statistical processing unit shown in FIG.
- FIG. 9 is a second diagram illustrating the diagnostic reference data generated by the statistical processing unit shown in FIG.
- FIG. 10 is a flowchart showing the overall operation (S14) of the operation diagnosis system when there is no transition between states in the engine (FIG. 1).
- FIG. 11 is a flowchart showing the overall operation (S18) of the operation diagnosis system when there is a transition between states in the engine (FIG. 1).
- FIG. 12 is a diagram showing a configuration of a second operation diagnostic program executed in the operation diagnostic device shown in FIGS. 1 and 2 instead of the first operation diagnostic program shown in FIG.
- FIG. 13 is a flowchart illustrating the operation (S20) of the state management unit in the second operation diagnostic program shown in FIG.
- FIG. 14 is a flowchart showing the overall operation (S24) of the operation diagnosis system when there is no transition between substates in each of the operation diagnosis units (FIG. 12) of the second operation diagnosis program.
- FIG. 15 is a flowchart showing the overall operation (S28) of the operation diagnosis system when a transition between states occurs in each of the operation diagnosis units (FIG. 12) of the second operation diagnosis program. is there.
- FIG. 1 is a diagram showing an operation diagnosis system 1 according to the present invention.
- the operation diagnosis system 1 is composed of a data collection device 3 and an operation diagnosis device 4 connected via a wired or wireless data transmission line 22.
- the operation diagnostic system 1 can be applied to various transportation machines by attaching sensors to components such as engines, such as aircraft and ships, in addition to automobiles. Therefore, a specific example is given in which the operation diagnosis system 1 is applied to an automobile.
- the operation diagnosis system 1 is used to diagnose whether individual products operate normally, whether or not the production of a desired chemical compound is successful, automatic monitoring of inpatients in the medical field, etc.
- Automatic operation diagnosis Z It can be applied to various applications that require automatic state monitoring, but for the sake of clarification and clarification of the description, the operation diagnosis system 1 A specific example is applied to a diagnosis.
- the operation diagnosis system 1 is mounted on various parts of the engine 26 of the vehicle 20 to be diagnosed by these components, for example, and the rotation speed, the torque, the temperature, the fuel consumption, and the exhaust gas of the engine 24 are mounted. Process the measured values obtained from each of one or more sensors 24 that measure the temperature and components of the gas, and diagnose the operation of the engine 26.
- FIG. 2 is a diagram illustrating a hardware configuration of the data collection device 3 and the operation diagnosis device 4 shown in FIG.
- the data collection device 3 and the operation diagnosis device 4 include a main body 100 including a CPU 102 and a memory 104, and input / output devices 106 such as an LCD display device and a keypad. It comprises a communication device 110 for performing mutual communication via the data transmission path 22 and a recording device 112 such as an HDD device and a CD device.
- the data collection device 3 includes a sensor interface (sensor IF) 1 1 that provides an interface function between the sensors 24 attached to the engine 26 (FIG. 1) and the main body 100. 6 is added.
- sensor IF sensor interface
- the data collection device 3 and the operation diagnosis device 4 have a configuration as a computer to which necessary functions such as an intercommunication function via the data transmission path 22 are added.
- FIG. 3 is a diagram showing a data collection program 30 that operates on the data collection device 3 shown in FIGS.
- the data collection program 30 includes a sensor control unit 300 and a communication control unit 302.
- the data collection program 30 is, for example, supplied to the data collection device 3 via the storage medium 114, loaded into the memory 104, and executed (the same applies to the following programs).
- the data collection program 30 controls the sensors 24 attached to the engine 26 periodically and in response to polling from the operation diagnostic device 4 to perform measurement. Read the value.
- the sensor control unit 300 transmits the read measurement value as measurement value data to the operation diagnostic device 4 via the communication control unit 302 and the data transmission path 22.
- the communication control unit 302 performs control required for communication with the operation diagnostic device 4.
- FIG. 4 is a diagram showing a first operation diagnostic program 40 that operates on the operation diagnostic device 4 shown in FIGS. 1 and 2.
- the operation diagnostic program 40 includes a communication control unit 400, a measured value data management unit 402, a measured value database (measured value DB) 404, a state management unit 406, Filter section 408, diagnosis target data management section 412, diagnosis target DB 414, diagnosis section 416, statistical processing section 424, diagnosis result DB 424, output filter section 426, and user Interface part (UI part) It consists of 428.
- Each of the filter unit 408, the operation diagnostic device 418, and the statistical processing unit 420 has a filter mode # 1 corresponding to states # 1 to #n described later with reference to FIG. _
- a plurality of components such as the filter modes 410-1 to 410-n may be abbreviated as the filter mode 410 or the like.
- n simply indicates an integer of 1 or more (n is not always the same number).
- the operation diagnostic program 40 processes the measured value data sent from the data collection device 3 by these components, and diagnoses the operation of the engine 26 (FIG. 1) and the like.
- the communication control unit 400 controls communication with the data collection device 3.
- the measured value data management unit 402 receives the measured value data from the data collection device 3, stores the measured value data in the measured value DB 404, and manages the data.
- the measured value data management unit 402 outputs the measured value data stored in the measured value DB 404 to the state management unit 406 and the filter unit 408 as necessary.
- FIG. 5 is a diagram illustrating a state of the engine 26 (FIG. 1).
- the state management unit 406 determines which state (state) the engine 26 is in as shown in FIG. 5, and according to the state of the engine 26, the filter mode 410 of the filter unit 408 and the diagnosis mode of the diagnosis unit 416. 418 and the statistical processing mode 422 of the statistical processing unit 420 are switched.
- the engine 26 when the engine 26 is operating on the automobile 20, the engine 26 has a plurality of states (states;! To n; idling, low-speed driving, high-speed driving, and deceleration). n ⁇ 2).
- the state determined by the state management unit 406 is a state for diagnosis only, and does not always match the state of the engine 26. _
- the state management unit 406 determines whether the operation of the engine 26 is in any of these states based on the measurement value data from the data collection device 3.
- the state management unit 406 determines the operation conditions (the filter mode 410, the diagnostic mode 418, and the statistical processing mode) set for the operation state of the engine 26 obtained as a result of the determination.
- the filter section 408, the diagnostic section 416, and the statistical processing section 420 are controlled so that the processing is performed in 422).
- the state management unit 4 06 determines that the operation of the engine 26 remains in the same state, and does not change the operating conditions of the filter unit 408, the diagnostic unit 416, and the statistical processing unit 420.
- the state management unit 406 determines that the operation of the engine 26 has transitioned to another state, The operating conditions of the filter unit 408, the diagnostic unit 416, and the statistical processing unit 420 are changed so that processing is performed under the operating conditions set for the state after the transition.
- the state management unit 406 When the operation of the engine 26 is in another state and the new measured value data satisfies the transition condition (return condition) to the original state, the state management unit 406 The filter unit 408, the diagnostic unit 416, and the statistical processing are performed so that the operation of the engine 26 is determined to have transitioned to the original state, and processing is performed under the operating conditions set for the original state. Change the operating conditions of part 420.
- FIG. 6 is a flowchart illustrating the operation (S10) of the state management unit 406 in the first operation diagnosis program 40 shown in FIG.
- the operation of the state management unit 406 will be further described using the case shown in FIG. 6 as a specific example.
- step 100 the state management unit 406 determines whether or not to end the processing. -
- the state management unit 406 proceeds to the process of S102 except when ending the process.
- step 102 the state management unit 406 determines whether the measured value data from the data collection device 3 is in a transition condition to state 1 (for example, an idling state) (for example, when the rotation speed and torque of the It is determined whether or not the following is satisfied.
- state 1 for example, an idling state
- the state management unit 406 proceeds to the process of S104 when the measured value data from the data collection device 3 satisfies the transition condition to the state 1, and otherwise performs the process of S118. Proceed to.
- step 104 the state management unit 406 determines that the engine 26 is in the state 1, and sets the filter unit 408, the diagnosis unit 416, and the statistical processing unit 420 to the operation condition (filter mode Set to 410-1, diagnostic mode 418-1, and statistical processing mode 422-1).
- step 106 the state management unit 406 determines whether the measured value data from the data collection device 3 is in the transition condition to the state 2 (for example, the state during low-speed running) (for example, the rotation speed of the engine 26). And the torque becomes a value within a predetermined range).
- the state management unit 406 determines whether the measured value data from the data collection device 3 is in the transition condition to the state 2 (for example, the state during low-speed running) (for example, the rotation speed of the engine 26). And the torque becomes a value within a predetermined range).
- the state management unit 406 proceeds to the process of S108 when the measured value data from the data collection device 3 satisfies the condition for transition to the state 2, and otherwise proceeds to the process of S110.
- step 108 the state management unit 406 determines that the engine 26 is in the state 2, and sets the filter unit 408, the diagnosis unit 416, and the statistics processing unit 420 to the operation conditions of the state 2 (filter mode 410 — Set to 2, diagnostic mode 418-2 and statistical processing mode 422-2).
- step 1 10 the state management unit 406 transmits the measurement value data from the data collection device 3 to the transition condition (for example, the engine (The number of rotations and torque of 26 become values within the specified range.)
- the state management unit 406 proceeds to the processing of S112 when the measured value data from the data collection device 3 satisfies the transition condition to the state 3, and otherwise sets the value to S11. The process returns to 104.
- step 1 1 2 the state management section 406 determines that the engine 26 is in the state 3, and the filter section 408, the diagnosis section 416, and the statistics processing section 4 Set 20 to the operating conditions of state 3 (filter mode 4 10-3, diagnostic mode 4 18-3, and statistical processing mode 4 2 2-3).
- step 114 the state management unit 406 determines whether the measured value data from the data collection device 3 is in the transition condition to the state 4 (for example, the state during deceleration) (for example, , The engine speed and torque of the engine 26 tend to decrease).
- step S118 If the measured value data from the data collection unit 3 satisfies the condition for transition to state 4, the state management unit 4 06 proceeds to step S118. It returns to the process of 6.
- step 1 16 the state management section 4 06
- the state management unit 406 returns to the processing of S108 when the processing of S114 is performed subsequent to the processing of S108, otherwise returns to the processing of S112. You.
- step 118 the state management unit 406 determines that the engine 26 is in the state 4, and the filter unit 408, the diagnosis unit 416, and the statistical processing.
- Set section 420 to the operating conditions of state 4 (filter mode 410-10, diagnostic mode 418-8-4, and statistical processing mode 422-4).
- the filter section 408 (FIG. 4) is a filter mode 410 set for each operation state of the engine 26 under the control of the state management section 406, and the measured value data is stored in the filter section 408. A filtering process is performed on the measured data input from step 2.
- the filter unit 408 outputs measured value data that satisfies the filter mode 4 10 to the diagnosis target data management unit 4 12 as diagnosis target data used for diagnosis.
- the filter section 408 may use a different filter mode 410 for each state, or may use a common filter mode 410 for multiple states. Yes (same for diagnostic mode 418 and statistical processing mode 422).
- filter mode 4 10 filtering condition
- FIG. 7 is a diagram exemplifying the timing of measurement value data to be diagnosed.
- the timing of the measured value data shown in (4) is calculated by the statistical processing when the state management unit 406 detects a transition of the operation state of the engine 26 at a certain timing.
- the part 420 and the diagnostic part 416 do not use the measured value data of that cycle as the object of statistical processing and diagnosis, and measure the subsequent m cycle (m ⁇ l) or the latest m cycle thereafter. Indicates that the value data is subject to statistical processing and diagnosis.
- the cycle here refers to various periods that can be identified in the data collection device 3 and the operation diagnosis device 4, such as the period in which the vehicle 20 travels on a circuit course, in addition to the measurement period by the data collection device 3. Is included.
- the filter section 408 stores the measured value data of the type to be diagnosed in that state according to the filter mode 410 set for each state of the engine 26, In this case, the measured value data obtained at a predetermined timing, not the measured value data generated by the sensors 24 in which the failure has occurred, which is within the range determined as above, is set as the diagnosis target data.
- the diagnosis target data management unit 412 receives the diagnosis target data input from the filter unit 408, stores it in the diagnosis target DB 414, and manages it.
- the diagnosis target data management unit 412 outputs the diagnosis target data stored in the diagnosis target DB 414 to the diagnosis unit 416 and the statistical processing unit 420.
- the statistical processing unit 420 is a statistical processing mode 422 set for each operation state of the engine 26 under the control of the state management unit 406, and is input from the diagnosis target data management unit 412. Statistical processing is performed on the data to be diagnosed, and diagnostic reference data for each operation state of the engine 26 is generated and output to the diagnostic unit 416.
- FIGS. 8 and 9 are first and second diagrams illustrating diagnostic reference data generated by the statistical processing unit 420 shown in FIG.
- the statistical processing unit 420 changes two or more types of diagnosis target data (for example, engine speed and temperature) or changes over time according to the conditions set for each state of the engine 26. Statistical processing is performed on one or more types of data to be diagnosed (for example, the number of rotations), and the center value shown by the solid line in FIG.
- the statistical processing unit 420 sets an error range with respect to the obtained center value according to the condition set for each state of the engine 26 as shown by a dotted line in FIG.
- the statistical processing unit 420 outputs the center and the error range shown in FIG. 8 to the diagnostic unit 416 as diagnostic reference data.
- the statistical processing unit 420 may, for example, assume that even if the specified cycle (for example, m; FIG. 7) has passed, if the number of data to be diagnosed is not as many as possible for statistical processing, For example, if the engine 26 is in a special state and the filter unit 408 does not include most of the measured values in the diagnosis, wait for a sufficient number of data to be collected. And perform statistical processing.
- the specified cycle for example, m; FIG. 7
- the diagnostic unit 416 uses the diagnostic reference data (FIGS. 8 and 9) input from the statistical processing unit 420 in a diagnostic mode 418 set for each operation state of the engine 26 under the control of the state management unit 406.
- the diagnosis target data input from the diagnosis target data management unit 412 is diagnosed, and the diagnosis result is stored in the diagnosis result DB 424 and managed.
- the diagnosis unit 416 outputs the diagnosis result stored in the diagnosis result DB 424 to the 111 unit 428.
- the diagnostic unit 416 determines that the number of times or frequency of the data to be diagnosed is out of the normal range indicated by the diagnostic reference data, the operation of the engine 26 is set to (not successful). Normal) Whether an abnormality is diagnosed is set for each operating state of the engine 26.
- the diagnosis unit 416 compares the data to be diagnosed with the diagnostic reference data, and sets the data to be diagnosed out of the error range indicated by the diagnostic reference data (FIGS. 8, 9) for each state. When the number of times or frequency is reached, it is determined that the operation of the engine 26 is abnormal.
- the output filter unit 426 further performs a filtering process on the diagnostic result output from the diagnostic unit 416, and outputs the result to the 111 unit 428.
- the diagnostic result is determined to be correct and is output to the UI unit 428.
- this diagnostic result is determined to be correct and is output to the UI unit 428.
- the 111 unit 428 displays, on the input / output device 106 (FIG. 2), the result of the filtering process input from the output filter unit 426, and shows it to the user.
- the UI unit 428 also receives a user operation on the input / output device 106, controls the operation of each component of the operation diagnostic program 40, or Make settings for mode 410, diagnostic mode 418 and statistical processing mode 422.
- FIG. 10 is a flowchart showing the overall operation (S14) of the operation diagnostic system 1 when there is no transition between states in the engine 26 (FIG. 1).
- step 140 the data collection device 3 starts collecting various measurement values of the engine 26 (FIG. 1), and sequentially transmits the measurement data to the operation diagnostic device 4 as measurement value data.
- step 142 the measured value data management unit 402 (FIG. 4) of the operation diagnosis program 40 determines whether or not new measured value data has been input.
- the operation diagnostic program 40 proceeds to the process of S144 when new measurement value data is input, and otherwise, stays in the process of S12.
- step 144 the filter unit 408 performs a filtering process on the input measurement value data.
- step 146 the diagnosis target data management unit 412 determines whether the new measurement value data has been adopted as the diagnosis target data.
- the operation diagnosis program 40 proceeds to the process of S148 when the new measured value data is adopted as the data to be diagnosed, and otherwise proceeds to the process of S156.
- step 148 the statistical processing section 420 updates the diagnostic reference data (FIGS. 8 and 9) using the new diagnosis target data.
- the diagnosis unit 416 diagnoses the data to be diagnosed based on the diagnostic reference data and sets conditions for detecting an abnormality.
- the data to be diagnosed is out of the range of the forbidden criterion data at a predetermined number of times and frequency
- the operation diagnosis program 40 diagnoses the data to be diagnosed and proceeds to the processing of S154 when the condition for detecting an abnormality is satisfied, and otherwise proceeds to the processing of S156.
- step 154 the diagnostic unit 416 determines, via the UI unit 428 and the input / output device 106 (FIG. 2), that an abnormality has occurred in the engine 26 and, as appropriate, the diagnostic results and measured value data. And the data to be diagnosed are displayed to the user.
- step 156 the UI unit 428 determines whether to end the diagnosis.
- the operation diagnosis program 40 When the operation diagnosis program 40 does not end the diagnosis, the operation diagnosis program 40 returns to the processing of S142.
- FIG. 11 is a flowchart showing the overall operation (S18) of the operation diagnostic system 1 when the engine 26 (FIG. 1) has a transition between states.
- step 180 the state management unit 406 determines whether or not a transition between states (FIGS. 5 and 6) has occurred in the engine 26.
- the operation diagnosis program 40 proceeds to the process of S182 when a transition between states (FIGS. 5 and 6) occurs in the engine 26, and proceeds to the process of S182 otherwise.
- step 182 the state management unit 406 sets the filter unit 408, the diagnosis unit 416, and the statistics processing unit 420 to the conditions (the filter mode 410, the diagnosis mode 418, and the statistics mode) set for the transition destination state. Set to perform processing in processing mode 422).
- step 18 4 the filter section 408 performs a filtering process on the input new measured value data in accordance with the set filter mode 410.
- step 1886 the statistical processing section 420 generates a diagnostic reference data in accordance with the set statistical processing mode 422.
- step 1888 the diagnosis section 416 diagnoses the diagnosis target data according to the set diagnosis mode 418.
- the operation diagnosis device 4 In order to realize operation diagnosis in parallel for each of a plurality of states, the operation diagnosis device 4 (FIGS. 1 and 2) replaces the first operation diagnosis program 40 (FIG. 4) with the second The operation diagnosis program 50 is executed.
- FIG. 12 shows a configuration of a second operation diagnosis program 50 executed in place of the first operation diagnosis program 40 shown in FIG. 4 in the operation diagnosis device 4 shown in FIGS. 1 and 2.
- FIG. 12 shows a configuration of a second operation diagnosis program 50 executed in place of the first operation diagnosis program 40 shown in FIG. 4 in the operation diagnosis device 4 shown in FIGS. 1 and 2.
- FIG. 12 shows a configuration of a second operation diagnosis program 50 executed in place of the first operation diagnosis program 40 shown in FIG. 4 in the operation diagnosis device 4 shown in FIGS. 1 and 2.
- the operation diagnosis program 50 is, for example, a target of operation diagnosis such as each state of the engine 26 shown in FIG. 5 or a state defined separately for operation diagnosis. It is provided for each of the following states, and is composed of an operation diagnostic section 52-:! ⁇ 52-n that operates in parallel, and a UI section 428.
- the operation diagnostic section 52 is a communication control section 400, a measurement value data management section 402, a measurement value measurement value DB 404, a state management section 406, a filter section 408, and a diagnosis target. It is composed of a data management unit 4 12, a diagnosis target DB 4 14, a diagnosis unit 4 16, a statistical processing unit 4 20, a diagnosis result DB 4 24 and an output filter unit 4 26.
- the operation diagnosis program 50 processes the measurement value data sent from the data collection device 3 and performs operation diagnosis in parallel for a plurality of states.
- the operation diagnosis unit 52 basically includes a plurality of diagnosis modes and a plurality of diagnosis modes in the diagnosis unit 416 and the statistical processing unit 420. A plurality of statistical processing modes are not set, and the operating conditions of the diagnostic section 416 and the statistical processing section 420 are not changed.
- n sub-states are further defined for the operation diagnosis of each state, and the filter section 408 includes a filter mode # 1 ( 4 1 0—1) to #n (4 1 0—n) are set, and the state manager 406 manages the state transition between these sub-states.
- each of the plurality of operation diagnosis units 52 that can operate in parallel can perform operation diagnosis for each state, different substates, Further, contradictory substates can be defined, and the operation diagnosis of the engine 26 can be performed in a fine and flexible manner.
- FIG. 13 is a flowchart illustrating the operation (S 20) of the state management unit 40 ⁇ in the second operation diagnosis program 50 shown in FIG.
- the state management unit 4006 determines which of the above-described substates the engine 26 or the like is in based on the measured value data from the data collection device 3,
- the filter mode 410 of the filter section 408 is switched according to the state of the engine 26 or the like.
- the operation of the state management unit 406 will be further described using the case shown in FIG. 13 as a specific example.
- step 200 the state management unit 406 determines whether or not to end the processing.
- the state management unit 406 proceeds to the processing of S202 except when ending the processing.
- step 202 the state management unit 406 determines whether the measured value data from the data collection device 3 satisfies the transition condition to the substate 1.
- the state management unit 406 proceeds to the process of S204 when the measured value data from the data collection device 3 satisfies the transition condition to the substate 1, and otherwise proceeds to the process of S202. stay.
- step 204 the state management unit 406 determines that the engine 26 and the like are in the substate 1, and sets the filter unit 408 to the operating condition (substate 1) of the substate 1. Set the filter mode to 4 1 0— 1).
- step 206 the state management unit 406 determines whether the measured value data from the data collection device 3 satisfies the condition for transition to the substate 2.
- the state management unit 406 proceeds to the processing of S 208 when the measured value data from the data collection device 3 satisfies the transition condition to the sub-state 2, and otherwise, proceeds to S 200. Stay in step 6.
- the state management unit 406 determines that the engine 26 and the like are in the substate 2, and sets the filter unit 408 to the operation condition of the substate 2 (filter mode 410-2).
- the state management unit 406 similarly determines a transition condition to a substate and performs a process associated with transition to each substate.
- step 210 the state management unit 406 determines whether the measured value data from the data collection device 3 satisfies the condition for transition to the substate n.
- the state management unit 406 proceeds to the process of S212 when the measurement value data from the data collection device 3 satisfies the transition condition to the sub-state n, and otherwise returns to the process of S210.
- step 212 the state management unit 406 determines that the engine 26 is in the state n, and sets the fill section 408 to the operation condition of the state n (fill mode 410-11).
- the filter unit 408 (FIG. 12) filters the measurement data input from the measurement data management unit 402 in the filter mode 410 set for each sub-state such as the engine 26, under the control of the state management unit 406. To process.
- the filter unit 408 outputs the measured value data satisfying the filter mode 410 to the diagnosis target data management unit 412 as diagnosis target data used for diagnosis.
- the statistical processing unit 420 statistically processes the data to be diagnosed input from the diagnosis object data management unit 412, generates diagnostic reference data (FIGS. 8, 9) for each operating state of the engine 26, and Output to 416.
- the diagnosis unit 416 diagnoses the diagnosis target data input from the diagnosis target data management unit 412 using the diagnostic reference data (FIGS. 8 and 9) input from the statistical processing unit 420, and compares the diagnosis result with the diagnosis result DB. Stored in 424 and managed.
- diagnosis unit 416 outputs the diagnosis result stored in the diagnosis result DB 424 to the output filter unit 426.
- FIG. 14 shows the overall operation (S24) of the operation diagnosis system 1 when there is no transition between substates in each of the operation diagnosis units 52 (FIG. 12) of the second operation diagnosis program 50. It is a flowchart.
- step 240 the data collection device 3 starts collecting various measured values of the engine 26 (FIG. 1) and sequentially transmits the measured data to the operation diagnostic device 4 as measured value data.
- step 242 the measured value data management unit 402 (FIG. 4) of each of the operation diagnosis units 52 of the operation diagnosis program 50 determines whether or not a new measured value data has been input.
- step 244 the filter unit 408 performs a filtering process on the input measurement value data.
- step 246 the diagnosis target data management unit 412 determines whether or not the new measured value data has been adopted as the diagnosis target data.
- the operation diagnosis unit 52 proceeds to the process of S248 when the new measured value data is adopted as the data to be diagnosed, and otherwise proceeds to the process of S256.
- step 248 the statistical processing unit 420 updates the diagnostic reference data (FIGS. 8 and 9) using the new data to be diagnosed.
- Steps 250 and 252 the diagnosis unit 416 diagnoses the diagnosis target data based on the diagnosis reference data and determines whether or not a condition for detecting an abnormality is satisfied.
- the operation diagnosis unit 52 diagnoses the data to be diagnosed, and proceeds to the process of S254 when the condition for detecting an abnormality is satisfied, and otherwise proceeds to the process of S256.
- step 254 the diagnostic unit 416, via the 111 unit 428 and the input / output device 106 (FIG. 2), reports that an abnormality has occurred in the engine 26 and, as appropriate, diagnoses and measured data. And the data to be diagnosed are displayed to the user.
- step 256 111 unit 428 determines whether or not to end the diagnosis.
- the operation diagnosis unit 52 When not ending the diagnosis, the operation diagnosis unit 52 returns to the process of S242. Next, the overall operation of the operation diagnosis system 1 when a transition between substates occurs in each of the operation diagnosis units 52 (FIG. 12) will be described.
- FIG. 15 shows the overall operation (S28) of the operation diagnosis system 1 when a transition between states occurs in each of the operation diagnosis units 52 (FIG. 12) of the second operation diagnosis program 50. It is a flowchart.
- step 280 the state management unit 406 of each operation diagnosis unit 52 determines whether a transition between substates has occurred.
- the operation diagnosis unit 52 proceeds to the process of S282 when a transition between substates occurs, and otherwise proceeds to the process of S282.
- step 282 the state management unit 406 sets the filter unit 408 to perform processing under the condition (filter mode 410) set for the transition destination sub-step! ⁇ .
- step 284 the filter unit 408 performs a filtering process on the input new measured value data according to the set filter mode 410.
- step 286 the statistical processing unit 420 generates diagnostic reference data using the new measurement value.
- step 288 the diagnosis unit 416 diagnoses the diagnosis target data using the generated diagnosis reference data.
- the present invention can be used for diagnosing and monitoring a change in operation or state of a measurement target based on a measurement value obtained from the measurement target.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Testing Of Engines (AREA)
- Testing And Monitoring For Control Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2004/005931 WO2005103630A1 (ja) | 2004-04-23 | 2004-04-23 | 診断装置およびその方法 |
DE112004002834T DE112004002834B4 (de) | 2004-04-23 | 2004-04-23 | Diagnosevorrichtung und -verfahren |
JP2006512465A JPWO2005103630A1 (ja) | 2004-04-23 | 2004-04-23 | 診断装置およびその方法 |
US10/599,529 US7881837B2 (en) | 2004-04-23 | 2004-04-23 | Diagnostic apparatus and method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2004/005931 WO2005103630A1 (ja) | 2004-04-23 | 2004-04-23 | 診断装置およびその方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005103630A1 true WO2005103630A1 (ja) | 2005-11-03 |
Family
ID=35197084
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/005931 WO2005103630A1 (ja) | 2004-04-23 | 2004-04-23 | 診断装置およびその方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US7881837B2 (ja) |
JP (1) | JPWO2005103630A1 (ja) |
DE (1) | DE112004002834B4 (ja) |
WO (1) | WO2005103630A1 (ja) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8380385B2 (en) * | 2008-11-12 | 2013-02-19 | The Boeing Company | System and method for determining electronic logbook observed defect fix effectiveness |
DE102011008736A1 (de) * | 2011-01-17 | 2012-07-19 | Andreas Stihl Ag & Co. Kg | Verfahren zur Schadensdiagnose bei einem handgeführten Arbeitsgerät |
JP7017851B2 (ja) | 2016-12-01 | 2022-02-09 | 住友重機械工業株式会社 | 故障診断システムおよび処理ユニット |
DE102018121270B4 (de) * | 2018-08-31 | 2023-12-21 | Volkswagen Aktiengesellschaft | Diagnoseverfahren, Diagnosesystem und Kraftfahrzeug |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07103055A (ja) * | 1993-09-30 | 1995-04-18 | Fuji Heavy Ind Ltd | エンジンの定常運転判別方法 |
JPH08254447A (ja) * | 1995-03-16 | 1996-10-01 | Toshiba Corp | プラント診断装置 |
JPH11118593A (ja) * | 1997-10-15 | 1999-04-30 | Toshiba Corp | プラント異常監視装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3841089A1 (de) * | 1988-12-07 | 1990-06-13 | Bosch Gmbh Robert | Verfahren zur auswertung eines sensorsignals |
JP2926917B2 (ja) * | 1990-07-06 | 1999-07-28 | 日産自動車株式会社 | 車両の異常診断装置 |
JP3610148B2 (ja) * | 1995-02-20 | 2005-01-12 | セイコーエプソン株式会社 | 周期・周波数計測装置 |
DE19910336A1 (de) * | 1999-03-09 | 2000-09-21 | Porsche Ag | Verfahren zur Überprüfung der Funktion von Katalysatoren in Brennkraftmaschinen |
DE19933924A1 (de) | 1999-04-29 | 2000-11-02 | Loher Ag | Mikrosystem zur lokalen Zustandsüberwachung und Zustandsdiagnose von Maschinen, Anlagen und/oder Baugruppen, insbesondere von Antriebssystemen |
US6701237B2 (en) * | 2001-08-01 | 2004-03-02 | Delphi Technologies, Inc. | Vehicle speed diagnostic algorithm for four-wheel steering systems |
DE10141557A1 (de) * | 2001-08-24 | 2003-03-06 | Knick Elektronische Mesgeraete | Verfahren zur Überwachung der Messung von Prozessgrößen bei wiederkehrenden Chargen-Prozessen |
ITTO20030999A1 (it) * | 2003-12-12 | 2005-06-13 | Fiat Ricerche | Metodo di attivazione della rigenerazione di un filtro del particolato in base ad una stima della quantita' di particolato accumulata nel filtro del particolato. |
-
2004
- 2004-04-23 WO PCT/JP2004/005931 patent/WO2005103630A1/ja active Application Filing
- 2004-04-23 DE DE112004002834T patent/DE112004002834B4/de not_active Expired - Lifetime
- 2004-04-23 JP JP2006512465A patent/JPWO2005103630A1/ja not_active Withdrawn
- 2004-04-23 US US10/599,529 patent/US7881837B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07103055A (ja) * | 1993-09-30 | 1995-04-18 | Fuji Heavy Ind Ltd | エンジンの定常運転判別方法 |
JPH08254447A (ja) * | 1995-03-16 | 1996-10-01 | Toshiba Corp | プラント診断装置 |
JPH11118593A (ja) * | 1997-10-15 | 1999-04-30 | Toshiba Corp | プラント異常監視装置 |
Also Published As
Publication number | Publication date |
---|---|
DE112004002834B4 (de) | 2012-12-06 |
DE112004002834T5 (de) | 2008-03-27 |
JPWO2005103630A1 (ja) | 2008-07-31 |
US7881837B2 (en) | 2011-02-01 |
US20070276559A1 (en) | 2007-11-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5296068B2 (ja) | センサ合理性診断 | |
US9014918B2 (en) | Health monitoring systems and techniques for vehicle systems | |
WO2011118250A1 (ja) | Dpfの再生制御装置、再生制御方法、および再生支援システム | |
JP2006053016A (ja) | 車両故障診断装置および車載端末 | |
JP6313146B2 (ja) | パティキュレートフィルタの故障診断方法及び装置 | |
JP2007327392A (ja) | Pmトラッパの故障検出システム | |
US8468808B2 (en) | Optimization of active regeneration triggers based on ambient and vehicle operating conditions | |
KR20160066601A (ko) | 인터쿨러 열화 진단 방법 | |
JP2009215926A (ja) | ディーゼルエンジン監視システム、及び監視方法 | |
JP3932514B2 (ja) | 車両の燃料レベルセンサーのノイズ故障検出方法 | |
CN110100158A (zh) | 旋转机的状态监视系统、旋转机的状态监视方法、程序以及存储介质 | |
US8874309B2 (en) | Method for acquiring information | |
JP2011189788A (ja) | 故障予兆診断装置及び方法 | |
CN106593645A (zh) | 一种车载节气门积碳监测系统 | |
Nanjundaswamy et al. | Advanced RF particulate filter sensing and controls for efficient aftertreatment management and reduced fuel consumption | |
WO2005103630A1 (ja) | 診断装置およびその方法 | |
US20210390801A1 (en) | Abnormality cause determining device, vehicular control device, and vehicular control system | |
CN108035789A (zh) | 汽油车多级三元催化器性能在线监测系统和方法 | |
CN102102565B (zh) | 在内燃发动机运转过程中进行“车上”故障诊断的方法和装置 | |
CN117171921A (zh) | 柴油颗粒物尾气净化装置健康状态评估处理方法和装置 | |
JP6414802B2 (ja) | ディーゼルエンジンのエンジンオイル劣化診断装置 | |
JP2023155219A (ja) | システム内の欠陥を識別するための方法 | |
JP2006502469A (ja) | 自動車ドライブトレインの部品の監視及び故障診断のための方法 | |
JP2021139341A (ja) | 燃料性状診断装置 | |
JP2004011869A (ja) | 自動変速機用油温センサの機能診断方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
ENP | Entry into the national phase |
Ref document number: 2006512465 Country of ref document: JP Kind code of ref document: A |
|
DPEN | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006512465 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10599529 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1120040028345 Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase | ||
WWP | Wipo information: published in national office |
Ref document number: 10599529 Country of ref document: US |
|
RET | De translation (de og part 6b) |
Ref document number: 112004002834 Country of ref document: DE Date of ref document: 20080327 Kind code of ref document: P |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8607 |