CN106155035A - Method for diagnosing faults based on maintenance class data and fault diagnosis system - Google Patents
Method for diagnosing faults based on maintenance class data and fault diagnosis system Download PDFInfo
- Publication number
- CN106155035A CN106155035A CN201510154810.7A CN201510154810A CN106155035A CN 106155035 A CN106155035 A CN 106155035A CN 201510154810 A CN201510154810 A CN 201510154810A CN 106155035 A CN106155035 A CN 106155035A
- Authority
- CN
- China
- Prior art keywords
- troubleshooting
- fault
- failure cause
- fault message
- failure
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
Method for diagnosing faults based on maintenance class data and fault diagnosis system, the invention provides a kind of method for diagnosing faults, including: i. receives at least one fault message；Ii. based at least one fault message, determine at least one corresponding failure cause, and at least one failure cause is ranked up；Iii. sequence based at least one failure cause fixed, determines troubleshooting flow process.By using technical scheme, the efficiency of airplane fault diagnosis can be improved, reduce the flight delay brought because of fault diagnosis and aircraft maintenance cost can be effectively reduced.
Description
Technical field
The present invention generally relates to aircraft field, more specifically, relate to a kind of based on
The method for diagnosing faults of maintenance class data and fault diagnosis system.
Background technology
Along with the development of aeronautical technology, the contact of each system of aircraft is increasingly tightr, therefore
Barrier also becomes increasingly complex and is difficult to judge, it is many that any one fault is likely to relate to other
Individual system cisco unity malfunction.Method for diagnosing faults based on maintenance class handbook is airplane fault
One of important means of diagnostic method, also one of important method being by health control.
Fault Isolation Manual is planemaker's design feature according to aircraft, and each user
It is aggregated into planemaker, the most again to airline according to the fault that its aircraft possessed occurs
The procedure manual of the partial fault method for removing provided, is the high level overview about maintenance knowledge.
Make full use of handbook, the troubleshooting programming system of staff, troubleshooting work can be made to have chapter
Can follow.
Therefore, a kind of fault diagnosis system that can determine failure cause as early as possible is needed badly.
Summary of the invention
For problem above, the invention provides a kind of based on data base, it is possible to determine as early as possible
The fault diagnosis system of failure cause, thus the troubleshooting of necessity can be taked to arrange when airplane fault
Execute and fix a breakdown, it is ensured that the safe operation of aircraft.
According to the first aspect of the invention, it is provided that a kind of method for diagnosing faults, including i.
Receive at least one fault message；Ii. based on described at least one fault message, it is right with it to determine
At least one failure cause answered, and at least one failure cause described is ranked up；iii.
Sequence based on fixed at least one failure cause described, determines troubleshooting flow process.
Preferably, described step ii also includes: based on described at least one fault message with
And the fault case of correspondence, history troubleshooting statistic record and fault principle, determine described in extremely
A few failure cause
Preferably, described step ii also includes: when the number of described fault message is more than one
During bar, compare the failure cause corresponding with described fault message, and determine described failure cause
Degree of overlapping and/or danger classes, based on described degree of overlapping and/or danger classes to described fault
Reason is ranked up and determines corresponding troubleshooting flow process.
Preferably, when single failure information correspondence single failure reason, based on described maintenance
Data in data base carry out troubleshooting to this failure cause；If troubleshooting is unsuccessful, then based on institute
State fault case corresponding to fault message and/or fault principle to determine failure cause and corresponding
Troubleshooting flow process.
Preferably, when the corresponding multiple failure cause of single described fault message, to described many
Individual failure cause carries out troubleshooting successively, or according to by fault case corresponding to described fault message,
The troubleshooting Optimizing Flow that history troubleshooting statistic record and fault principle determine is to carry out troubleshooting；If
Troubleshooting is unsuccessful, then according to based on other fault case corresponding to described fault message and/or
Fault principle determines failure cause and corresponding troubleshooting flow process.
Preferably, described troubleshooting Optimizing Flow is determined by following steps: to described fault message
Corresponding fault case, history troubleshooting statistic record and fault principle give different power respectively
Weight, it is then determined that the failure cause corresponding with described fault message and corresponding troubleshooting flow process.
Preferably, described fault case, history troubleshooting statistic record and the weight of fault principle
It is respectively 0.3,0.5 and 0.2.
Preferably, if troubleshooting is successful, it is determined that described failure cause, and record and this event
The information that barrier reason is associated.
The invention allows for a kind of fault diagnosis system, including: input module, it is used for connecing
Receive at least one fault message；Data memory module is corresponding with fault message for storage
Failure cause and corresponding troubleshooting method；Failure analysis module, leads to described input module
Letter connects, and it is configured to based on described at least one fault message, determines the most at least
One failure cause, and at least one failure cause described is ranked up, to determine troubleshooting
Flow process.
Preferably, described failure analysis module is also configured to based on described at least one
Fault case, history troubleshooting statistic record and the fault principle that fault message is corresponding, determines institute
State at least one failure cause
Preferably, described failure analysis module is also configured to when the number of described fault message
When mesh is more than one, compares the failure cause corresponding with described fault message, and determine described
The degree of overlapping of failure cause and/or danger classes, based on described degree of overlapping and/or danger classes pair
Described failure cause is ranked up.
Preferably, if described fault message only corresponding fault in Maintenance plan
During reason, based on the data in described Maintenance plan, this failure cause is carried out troubleshooting；If
Article one, described fault message is in Maintenance plan during corresponding multiple failure cause, to described many
Individual failure cause carries out troubleshooting successively, or based on by fault case corresponding to described fault message,
History troubleshooting statistic record and fault principle determine troubleshooting Optimizing Flow, and carry out troubleshooting；If
Troubleshooting is unsuccessful, then come based on fault case corresponding to described fault message and/or fault principle
Determine failure cause and corresponding troubleshooting flow process.
Preferably, described troubleshooting Optimizing Flow is determined by following steps: to described fault message
Corresponding fault case, history troubleshooting statistic record and fault principle give different power respectively
Weight, it is then determined that the failure cause corresponding with described fault message and corresponding troubleshooting flow process.
By using technical scheme, can have following Advantageous Effects: 1.
Improve the efficiency of airplane fault diagnosis；2. reduce the flight brought because of fault diagnosis to be delayed；3.
Aircraft maintenance cost can be effectively reduced.
Accompanying drawing explanation
By the description of the detailed description of the invention with reference to the present invention given by drawings below it
After, be better understood with the present invention, and other objects of the present invention, details, feature and
Advantage will become apparent from.In the accompanying drawings:
Fig. 1 is the configuration diagram of the fault diagnosis according to the embodiment of the present invention；
Fig. 2 shows the first the troubleshooting flow process according to the embodiment of the present invention；
Fig. 3 shows the second troubleshooting flow process according to the embodiment of the present invention.
Detailed description of the invention
The present invention proposes to set up fault diagnosis system based on servicing manual, so that safeguarding
Personnel quickly confirm to produce the possible cause of fault, to reducing maintenance cost, improve operation effect
Rate has important effect.In troubleshooting maintenance work, there may be multiple fault simultaneously etc.
Wait to investigate, and these faults are if being caused by a certain common cause, common for this
The troubleshooting of reason, it will be greatly improved troubleshooting efficiency.
Fig. 1 is the configuration diagram of the fault diagnosis according to the embodiment of the present invention.
Fault diagnosis system 10 includes: input module 11, for receiving at least one fault letter
Breath；Data memory module 12, for storing the failure cause corresponding with fault message and phase
The troubleshooting method answered；Failure analysis module 13, communicates to connect with input module, and it is configured
For based at least one fault message, determine at least one failure cause corresponding, and to extremely
A few failure cause is ranked up, to determine troubleshooting flow process.
When input module 11 receives fault message, failure analysis module 13 will be according to fault
Corresponding relation between information and failure cause processes.Such as, connect when input module 11
When receiving a plurality of fault message, failure analysis module 13 can be former to the fault of input fault information
Because comparing analysis, such as, failure cause and danger classes to input fault compare
Relatively analyze, finally draw each fault in all failure causes have reason degree of overlapping order and
And preventive maintenance, then prompting user can by the failure cause troubleshooting of degree of overlapping order,
Or troubleshooting is preferentially carried out by high-grade fault.
When single fault message is carried out troubleshooting, typically there is two following situations:
The first: single failure information correspondence single failure reason
Article one, the corresponding failure cause of fault message is better simply a kind of feelings in troubleshooting work
Condition, at this moment failure analysis module 13 can directly store according in data memory module 12
The troubleshooting flow process corresponding to this failure cause carry out troubleshooting.If troubleshooting failure, then fault is divided
Analysis module 13 determines other corresponding with this fault message according to fault principle, fault case
Failure cause, and be ranked up according to probability, and then carry out troubleshooting again.
Fig. 2 shows the first the troubleshooting flow process according to the embodiment of the present invention.
First, determine single failure correspondence single failure reason (step S21), be then based on
In data memory module 12, the corresponding troubleshooting flow process of storage (such as, derives from servicing manual
Mantenance data etc.) carry out troubleshooting (step S22)；Judge the most successful (step of troubleshooting
S23), if success, then export diagnostic result (step S24), i.e. output and show that fault sets
Standby information, and record the relevant information (step S25) of troubleshooting, such as recorded history row
Therefore in statistic record.
If in step S22 troubleshooting failure, then failure analysis module 13 according to fault principle,
Fault case determines other failure cause corresponding with this fault message, and according to possible
Property be ranked up (step S27), and then referring again to other handbooks of data module carry out troubleshooting (step
Rapid S28)；Judge that troubleshooting is the most successful (step S29), if success, then perform step
S24, output shows the information of faulty equipment, and records the relevant information (step S25) of troubleshooting,
Until terminating (step S26).
The second: the corresponding multiple failure causes of fault message
Article one, there are most feelings during being troubleshooting in the corresponding multiple failure causes of fault message
Condition, can take two ways: one is directly by mantenance data troubleshooting in this case,
Additionally can also be with reference to according to based on fault case, fault principle, history troubleshooting statistic record
Determine Optimizing Flow, carry out troubleshooting the most again.Without fixing a breakdown, can be further
The other reasons listed with reference to fault principle, fault case, inquires about other handbooks the most one by one
Troubleshooting, until failture evacuation.
Fig. 3 shows the second troubleshooting flow process according to the embodiment of the present invention.
First, the corresponding multiple failure causes (step S301) of single failure, then base are determined
Corresponding troubleshooting flow process (such as, the servicing manual data of storage in data memory module 12
Etc.) carry out troubleshooting (step S302)；Judge that troubleshooting is the most successful (step S303),
If success, then export diagnostic result (step S304), i.e. output and show the letter of faulty equipment
Breath, and record the relevant information (step S305) of troubleshooting.
Equally, step S310 can also be performed after step S301, i.e. determine troubleshooting optimization
Flow process, refers again to this Optimizing Flow and performs troubleshooting (S311), then same in step S303
Middle judge troubleshooting whether success.
Here to how determining that the process that troubleshooting Optimizing Flow is carried out is illustrated.For specific
Fault message, the data in data memory module 12 may provide multiple possible cause,
Troubleshooting flow process will investigate these reasons one by one, position fault.In order to be quickly found out failure cause,
Failure analysis module 13 is based on history troubleshooting statistic record, (similar) fault case, fault
Principle, determines whole failure causes, and any of the above reference result is provided whole
Failure cause carries out information fusion and weighted analysis, so that it is determined that specific fault reason causes event
Barrier possibility occurrence (fusion index) also carries out integrated ordered by this probability, and then realizes
Being accurately positioned of failure cause, finally provides troubleshooting Optimizing Flow.By with this Optimizing Flow
Carry out troubleshooting, the troubleshooting time can be shortened.
When analyzing fault message based on fault case, two kinds of fault diagnosis modes of fault principle
Time, for same fault message, the diagnostic result that two kinds of diagnostic modes are given may be not to the utmost
Identical, mainly can show that obtained failure cause is in content and probability size order
There is any discrepancy, for this situation, needs former to provided fault according to the feature of information source
Cause and sort order thereof distribute different weights, in conjunction with conventional statistical result, are given
Good troubleshooting scheme.
The computational methods of weighted analysis here are as follows:
The case of statistics number+0.3 × i of the convergence analysis index=0.5 × i of failure cause i time
The principle number of times of number+0.2 × i
The convergence analysis index of fusion index=reason i of reason i/all reason convergence analysis
Index sum
Here, the weight of fault case, history troubleshooting statistic record and fault principle is respectively
0.3,0.5 and 0.2.
The numerical value of the fusion index of each reason is the biggest, shows that this reason causes this fault
Probability is the biggest, needs urgent the eliminating.
If troubleshooting failure in step s 302, then failure analysis module 13 is former according to fault
Manage, fault case determines other failure cause corresponding with this fault message, and according to
Probability is ranked up (step S307), and then carries out referring again to other handbooks of data module
Troubleshooting (step S308)；Judge that troubleshooting is the most successful (step S309), if success, then
Performing step S304, output shows the information of faulty equipment, and records the relevant information of troubleshooting
(step S305), until terminating (step S306).
Data in aforesaid data memory module 12 be derived from the relevant servicing manual of aircraft,
Fault case, history troubleshooting statistic record etc..Such as, for the number from servicing manual
According to, fault can be indicated by failure code with failure code as major key, and is number of faults
Each attribute is added, including section number information, failure-description belonging to fault according to the fault in storehouse
Information, fault harm class information, fault reason information etc..Therefore, when user is based on upper
When the diagnostic system stated obtains failure cause, the flow process of troubleshooting can be obtained rapidly.
The invention allows for a kind of method for diagnosing faults, including: i. receives at least one fault
Information；Ii. based on this at least one fault message, determine that at least one corresponding fault is former
Cause, and this at least one failure cause is ranked up；Iii. based on fixed this at least one
The sequence of individual failure cause, determines troubleshooting flow process.
Such as, when receiving a plurality of fault message, failure analysis module 13 is to input fault
The failure cause of information compares analysis, such as, and failure cause and the danger to input fault
Danger grade compares analysis.
Now, for step ii, comprising: when the number of this fault message is more than one,
Relatively more corresponding with this fault message failure cause, and determine this failure cause degree of overlapping and/
Or danger classes, based on this degree of overlapping and/or danger classes, this failure cause is ranked up
And determine corresponding troubleshooting flow process.Then, user can need with the fault of degree of overlapping order
Reason troubleshooting, or troubleshooting is preferentially carried out by high-grade fault.
When single failure information correspondence single failure reason, based in this Maintenance plan
Data carry out troubleshooting to this failure cause；If troubleshooting is unsuccessful, then based on this fault message pair
The fault case answered and/or fault principle are to determine failure cause and corresponding troubleshooting flow process.
Preferably, when the corresponding multiple failure cause of this fault message single, to the plurality of event
Barrier reason carries out troubleshooting successively, or according to by fault case corresponding to this fault message, history
The troubleshooting Optimizing Flow that troubleshooting statistic record and fault principle determine is to carry out troubleshooting；If troubleshooting
Unsuccessful, then former according to other the fault case corresponding based on this fault message and/or fault
Reason determines failure cause and corresponding troubleshooting flow process.
By using technical scheme, can have a following Advantageous Effects:
1. improve the efficiency of airplane fault diagnosis
The troubleshooting work of airline is carried out mainly in accordance with troubleshooting handbook.At present and aeronautical maintenance
Relevant handbook has tens of kinds, and also to consult substantial amounts of engineering while consulting handbook
File, this is to being brought bigger difficulty according to the troubleshooting of handbook, and the present invention is by with handbook being
Basis, takes into account the historical statistical data of system, and combines with other method for diagnosing faults,
Applied mathematics instrument, it is achieved high-grade intelligent diagnose, can effectively solve tradition handbook troubleshooting and
Case troubleshooting mode is time-consumingly grown, workload is big and the inaccurate situation of fault location, and aviation is public
Department service engineer can quickly position failure cause, improves troubleshooting efficiency.
2. reduce the flight brought because of fault diagnosis to be delayed
The present invention can help airline maintenance personnel to judge to produce the possible cause of fault, soon
Speed navigates to corresponding fault isolation routine, further according to isolating program validation and fixing a breakdown,
Thus improve accuracy and the work efficiency of troubleshooting, the boat of airline can be improved greatly
Class's percent of punctuality.
3. can be effectively reduced aircraft maintenance cost
Maintenance level and troubleshooting efficiency is provided certainly to have one that is saving maintenance cost
Effect approach.The present invention can find fault solution party quickly and accurately by handbook chained technology
Case, thus improve troubleshooting efficiency relatively low under tradition troubleshooting mode, reach substantially to reduce aircraft
Safeguard and the purpose of operation cost.
The above description of the disclosure is for making any those of ordinary skill of this area be capable of
Or the use present invention.To those skilled in the art, the various amendments of the disclosure
Will be apparent from, and general principle defined herein can also be without departing from this
Other deformation it is applied in the case of bright spirit and scope.Therefore, the present invention is not
Be limited to example as herein described and design, but with principle disclosed herein and novel features
The widest scope consistent.
Claims (13)
1. a method for diagnosing faults, including:
I. at least one fault message is received；
Ii. based on described at least one fault message, determine at least one corresponding failure cause, and at least one failure cause described is ranked up；
Iii. sequence based on fixed at least one failure cause described, determines troubleshooting flow process.
2. the method for claim 1, it is characterised in that also include in described step ii:
Based on described at least one fault message and the fault case of its correspondence, history troubleshooting statistic record and fault principle, determine at least one failure cause described.
3. the method for claim 1, it is characterised in that also include in described step ii:
When the number of described fault message is more than one, the failure cause the most corresponding with described fault message, and determine degree of overlapping and/or the danger classes of described failure cause, based on described degree of overlapping and/or danger classes described failure cause it is ranked up and determines corresponding troubleshooting flow process.
4. the method for claim 1, it is characterised in that when single failure information correspondence single failure reason, based on the data in described Maintenance plan, this failure cause is carried out troubleshooting；
If troubleshooting is unsuccessful, then determine failure cause and corresponding troubleshooting flow process based on fault case corresponding to described fault message and/or fault principle.
5. the method for claim 1, it is characterised in that when the corresponding multiple failure cause of single described fault message,
The plurality of failure cause is carried out successively troubleshooting, or carries out troubleshooting according to the troubleshooting Optimizing Flow determined by fault case, history troubleshooting statistic record and the fault principle that described fault message is corresponding；
If troubleshooting is unsuccessful, then determine failure cause and corresponding troubleshooting flow process according to other the fault case corresponding based on described fault message and/or fault principle.
6. method as claimed in claim 5, it is characterised in that described troubleshooting Optimizing Flow is determined by following steps:
Different weights is given respectively to fault case, history troubleshooting statistic record and the fault principle that described fault message is corresponding, it is then determined that the failure cause corresponding with described fault message and corresponding troubleshooting flow process.
7. method as claimed in claim 6, it is characterised in that the weight of described fault case, history troubleshooting statistic record and fault principle is respectively 0.3,0.5 and 0.2.
8. the method for claim 1, it is characterised in that
If troubleshooting success, it is determined that described failure cause, and record the information being associated with this failure cause.
9. a fault diagnosis system, including:
Input module, for receiving at least one fault message；
Data memory module, for storing the failure cause corresponding with fault message and corresponding troubleshooting method；
Failure analysis module, communicates to connect with described input module, and it is configured to based on described at least one fault message, determines at least one failure cause corresponding, and is ranked up at least one failure cause described, to determine troubleshooting flow process.
10. system as claimed in claim 9, it is characterised in that described failure analysis module is also configured to
Based on the fault case corresponding with described at least one fault message, history troubleshooting statistic record and fault principle, determine at least one failure cause described.
11. systems as claimed in claim 9, it is characterised in that described failure analysis module is also configured to
When the number of described fault message is more than one, compare the failure cause corresponding with described fault message, and determine degree of overlapping and/or the danger classes of described failure cause, based on described degree of overlapping and/or danger classes, described failure cause is ranked up.
12. systems as claimed in claim 9, it is characterised in that
If one described fault message is in Maintenance plan during an only corresponding failure cause, based on the data in described Maintenance plan, this failure cause is carried out troubleshooting；
If one described fault message is in Maintenance plan during corresponding multiple failure cause, the plurality of failure cause is carried out successively troubleshooting, or determine troubleshooting Optimizing Flow based on by fault case, history troubleshooting statistic record and the fault principle that described fault message is corresponding, and carry out troubleshooting；
If troubleshooting is unsuccessful, then determine failure cause and corresponding troubleshooting flow process based on fault case corresponding to described fault message and/or fault principle.
13. systems as claimed in claim 12, it is characterised in that described troubleshooting Optimizing Flow is determined by following steps:
Different weights is given respectively to fault case, history troubleshooting statistic record and the fault principle that described fault message is corresponding, it is then determined that the failure cause corresponding with described fault message and corresponding troubleshooting flow process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510154810.7A CN106155035B (en) | 2015-04-02 | 2015-04-02 | Method for diagnosing faults and fault diagnosis system based on repair class data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510154810.7A CN106155035B (en) | 2015-04-02 | 2015-04-02 | Method for diagnosing faults and fault diagnosis system based on repair class data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106155035A true CN106155035A (en) | 2016-11-23 |
| CN106155035B CN106155035B (en) | 2018-09-07 |
Family
ID=57338463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510154810.7A Active CN106155035B (en) | 2015-04-02 | 2015-04-02 | Method for diagnosing faults and fault diagnosis system based on repair class data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106155035B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789243A (en) * | 2016-12-22 | 2017-05-31 | 烟台东方纵横科技股份有限公司 | A kind of IT operational systems with intelligent trouble analytic function |
| CN107516414A (en) * | 2017-08-21 | 2017-12-26 | 中国电力科学研究院 | A kind of power information acquisition system Analysis on Fault Diagnosis method and system |
| CN107590541A (en) * | 2017-08-04 | 2018-01-16 | 国网浙江省电力公司 | A kind of field treatment method of load data collection success rate low defect |
| CN109284841A (en) * | 2018-11-16 | 2019-01-29 | 四川长虹电器股份有限公司 | Household electrical appliances fault diagnosis system based on history mantenance data |
| CN109558220A (en) * | 2017-09-26 | 2019-04-02 | 北京摩拜科技有限公司 | A kind of management method and equipment of fault car |
| CN109592525A (en) * | 2018-12-07 | 2019-04-09 | 上海辛格林纳新时达电机有限公司 | Elevator frequency converter fault diagnosis system and method |
| CN110221592A (en) * | 2019-05-30 | 2019-09-10 | 北京博锐尚格节能技术股份有限公司 | Build functional failure of electromechanical diagnostic method, apparatus and system |
| CN112241162A (en) * | 2020-10-28 | 2021-01-19 | 中国商用飞机有限责任公司 | Maintenance system and maintenance method for processing airplane fault |
| CN112432786A (en) * | 2020-12-11 | 2021-03-02 | 湖北航天技术研究院特种车辆技术中心 | Fault diagnosis method and device for hydraulic automatic transmission |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6785636B1 (en) * | 1999-05-14 | 2004-08-31 | Siemens Corporate Research, Inc. | Fault diagnosis in a complex system, such as a nuclear plant, using probabilistic reasoning |
| CN102012697A (en) * | 2010-09-21 | 2011-04-13 | 三一重工股份有限公司 | Engineering machinery and intelligent fault treatment method and system thereof |
| CN102819239B (en) * | 2011-06-08 | 2014-09-17 | 同济大学 | Intelligent fault diagnosis method of numerical control machine tool |
| CN103914058B (en) * | 2012-12-29 | 2018-08-28 | 上海可鲁***软件有限公司 | The fault diagnosis and alarm method and system of a kind of oil-gas pipeline industrial control equipment remote monitoring system |
| CN104077483A (en) * | 2014-06-27 | 2014-10-01 | 南京理工大学 | Determining method of overall influence degrees of failure modes and failure causes of urban rail vehicle components |
-
2015
- 2015-04-02 CN CN201510154810.7A patent/CN106155035B/en active Active
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789243A (en) * | 2016-12-22 | 2017-05-31 | 烟台东方纵横科技股份有限公司 | A kind of IT operational systems with intelligent trouble analytic function |
| CN106789243B (en) * | 2016-12-22 | 2019-06-14 | 烟台东方纵横科技股份有限公司 | A kind of IT operational system with intelligent trouble analytic function |
| CN107590541A (en) * | 2017-08-04 | 2018-01-16 | 国网浙江省电力公司 | A kind of field treatment method of load data collection success rate low defect |
| CN107516414A (en) * | 2017-08-21 | 2017-12-26 | 中国电力科学研究院 | A kind of power information acquisition system Analysis on Fault Diagnosis method and system |
| CN109558220A (en) * | 2017-09-26 | 2019-04-02 | 北京摩拜科技有限公司 | A kind of management method and equipment of fault car |
| CN109558220B (en) * | 2017-09-26 | 2021-02-05 | 汉海信息技术(上海)有限公司 | Management method and equipment for fault vehicle |
| CN109284841A (en) * | 2018-11-16 | 2019-01-29 | 四川长虹电器股份有限公司 | Household electrical appliances fault diagnosis system based on history mantenance data |
| CN109592525A (en) * | 2018-12-07 | 2019-04-09 | 上海辛格林纳新时达电机有限公司 | Elevator frequency converter fault diagnosis system and method |
| CN110221592A (en) * | 2019-05-30 | 2019-09-10 | 北京博锐尚格节能技术股份有限公司 | Build functional failure of electromechanical diagnostic method, apparatus and system |
| CN112241162A (en) * | 2020-10-28 | 2021-01-19 | 中国商用飞机有限责任公司 | Maintenance system and maintenance method for processing airplane fault |
| CN112432786A (en) * | 2020-12-11 | 2021-03-02 | 湖北航天技术研究院特种车辆技术中心 | Fault diagnosis method and device for hydraulic automatic transmission |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106155035B (en) | 2018-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106155035A (en) | Method for diagnosing faults based on maintenance class data and fault diagnosis system | |
| KR20210019564A (en) | Operation maintenance system and method | |
| CN106209405B (en) | Method for diagnosing faults and device | |
| CN105764081B (en) | Method, base station, network management system and system for detecting communication link | |
| CN102998996A (en) | Airborne real-time fault diagnosis method | |
| US20080183406A1 (en) | Online IED Fault Diagnosis Device and Method for Substation Automation System Based on IEC61850 | |
| CN105116870B (en) | Fault analysis method, device and system of air conditioning unit | |
| CN103473710A (en) | Graded handling method for faults of centralized operation and maintenance systems | |
| CN106646030A (en) | Power grid fault diagnosis method and device based on multiple data sources and expert rule base | |
| CN105629962A (en) | Failure diagnosis method for high-speed railway train control equipment radio block center (RBC) system | |
| CN109501834A (en) | A kind of point machine failure prediction method and device | |
| TWI731146B (en) | Aircraft malfunction handling system, method for handling aircraft malfunction, and computer equipment using thereof | |
| CN103941240B (en) | A kind of detection method of the extension set detecting device that communicates based on radar system | |
| CN108053041B (en) | Secondary system abnormity identification and anti-misoperation system and method under multi-association scene of transformer substation | |
| US20110150162A1 (en) | Automated periodic surveillance testing method and apparatus in digital reactor protection system | |
| JP2642438B2 (en) | Plant equipment maintenance management support device | |
| CN106341322A (en) | Link switching method and system | |
| CN106897779A (en) | A kind of processing method of data center's operational system event | |
| CN106651198A (en) | Power grid accident auxiliary processing method and system | |
| JP2017062730A (en) | Abnormality diagnosis system | |
| CN112000558A (en) | Method for generating automatic test case of rail transit signal system | |
| CN109167684A (en) | A kind of communication network status failure monitoring system and repair method | |
| CN102281103A (en) | Optical network multi-fault recovering method based on fuzzy set calculation | |
| CN106875015B (en) | A kind of airplane fault diagnostic method and system | |
| CN117194154A (en) | APM full-link monitoring system and method based on micro-service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |