CN111240871B - Method and device for reporting engine fault - Google Patents
Method and device for reporting engine fault Download PDFInfo
- Publication number
- CN111240871B CN111240871B CN201911399202.7A CN201911399202A CN111240871B CN 111240871 B CN111240871 B CN 111240871B CN 201911399202 A CN201911399202 A CN 201911399202A CN 111240871 B CN111240871 B CN 111240871B
- Authority
- CN
- China
- Prior art keywords
- fault
- code
- slave
- state
- fault code
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0775—Content or structure details of the error report, e.g. specific table structure, specific error fields
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
- Y02T10/00—Road transport of goods or passengers
- Y02T10/10—Internal combustion engine [ICE] based vehicles
- Y02T10/40—Engine management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Small-Scale Networks (AREA)
Abstract
The invention discloses a method and a device for reporting engine faults, wherein the method comprises the following steps: when a fault sending instruction is detected, reading a stored fault code from a fault memory and sending the stored fault code to a CAN bus; for each calibration group, judging whether the read fault code contains a main fault code or not, wherein the first element of the group is the main fault code, and the fault codes except the first element are slave fault codes associated with the main fault code; if yes, the slave fault code contained in the packet is acquired and sent to the CAN bus. When the triggering condition of the fault sending instruction is detected, besides the fault codes stored in the fault memory, the slave fault codes associated with the master fault codes stored in the fault memory are also reported, and some slave fault codes may be stored in the fault memory, and some slave fault codes are likely to be not in the fault memory, so that in order to ensure timeliness and comprehensiveness of fault report, all associated slave fault codes need to be reported.
Description
Technical Field
The invention relates to the technical field of fault diagnosis, in particular to an engine fault reporting method and device.
Background
At present, engine fault diagnosis is realized through judgment of sensor signals. Due to various reasons such as sensor precision, induction blind areas or interference or distortion of signals, related fault diagnosis of the engine can have certain diagnosis errors in actual operation, so that partial faults cannot be timely reported, timeliness of fault report is affected, and timely identification of faults and timely reading of fault codes are affected.
Disclosure of Invention
The invention aims at providing an engine fault reporting method and device aiming at the defects of the prior art, and the aim is achieved through the following technical scheme.
The first aspect of the invention provides an engine fault reporting method, which comprises the following steps:
when a fault sending instruction is detected, reading a stored fault code from a fault memory and sending the stored fault code to a Controller Area Network (CAN) bus;
judging whether a main fault code contained in each calibration group exists in the read fault codes or not according to each calibration group, wherein a first element of the calibration group is the main fault code, and other fault codes except the first element are slave fault codes associated with the main fault code;
if yes, the slave fault code contained in the packet is acquired and sent to the CAN bus.
A second aspect of the present invention proposes an engine failure reporting method, the method comprising:
judging whether the fault state code of the main fault code contained in each calibration grouping is a fault report state or not according to each calibration grouping; the first element of the calibration group is a master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
if yes, the fault state code is obtained from the calibration packet and is a slave fault code in an unreported state, the obtained slave fault code is stored in a fault memory, and when a fault code reading request and/or a periodical fault code sending request are received, the fault code stored in the fault memory is sent to a controller area network CAN bus.
A third aspect of the present invention proposes an engine failure reporting apparatus, the apparatus comprising:
the reading module is used for reading the stored fault code from the fault memory when the fault sending instruction is detected;
the first sending module is used for sending the read fault code to the CAN bus;
the judging module is used for judging whether the main fault code contained in the calibration grouping exists in the read fault codes according to each calibration grouping, wherein the first element of the calibration grouping is the main fault code, and the fault codes except the first element are the auxiliary fault codes related to the main fault code;
and the second sending module is used for acquiring the slave fault code contained in the packet and sending the slave fault code to the CAN bus when the judgment is yes.
A fourth aspect of the present invention proposes an engine failure reporting apparatus, the apparatus comprising:
the judging module is used for judging whether the fault state code of the main fault code contained in each calibration grouping is a fault report state or not according to each calibration grouping; the first element of the calibration group is a master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
and the storage module is used for acquiring the slave fault code with the fault state code being the unreported state from the calibration packet when judging that the fault state code is the unreported state, and storing the acquired slave fault code into the fault memory so as to send the fault code stored in the fault memory to the controller area network CAN bus when receiving a fault code reading request and/or a periodical fault code sending request.
In the embodiment of the invention, when the ECU detects the triggering condition of the fault sending instruction, besides the fault codes stored in the fault memory, the ECU also reports the slave fault codes associated with the master fault codes stored in the fault memory, and some slave fault codes are possibly not in the fault memory, so that all the associated slave fault codes are required to be reported in order to ensure timeliness and comprehensiveness of fault report.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a flow chart illustrating an embodiment of an engine fault notification method according to an exemplary embodiment of the present invention;
FIG. 2 is a flow chart illustrating another engine fault notification method according to an exemplary embodiment of the present invention;
fig. 3 is a hardware configuration diagram of an ECU according to an exemplary embodiment of the present invention;
FIG. 4 is a flow chart illustrating an embodiment of an engine fault notification apparatus according to an exemplary embodiment of the present invention;
fig. 5 is a flow chart illustrating another embodiment of an engine fault notification apparatus according to an exemplary embodiment of the present invention.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of apparatus and methods consistent with aspects of the invention as detailed in the accompanying claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the invention. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
For fault diagnosis of an engine, certain diagnosis errors exist due to reasons such as sensor precision, induction dead zones or interference or distortion of signals, and the like.
The engine fault reporting method according to the present invention will be described in detail with reference to specific examples.
Fig. 1 is a flowchart of an embodiment of an engine fault reporting method according to an exemplary embodiment of the present invention, which may be applied to an ECU, as shown in fig. 1, and includes the steps of:
step 101: when a fault sending instruction is detected, the stored fault code is read from the fault memory and sent to the CAN bus.
The fault memory is used for storing the diagnosed fault code, the ECU locally reports the fault code stored in the fault memory periodically, and the fault code stored in the fault memory can be reported by an external fault code reading request.
It follows that the trigger condition of the fault send instruction may include receiving a fault code read request and/or periodically sending a fault code request.
In the present invention, the CAN (Controller Area Network ) bus is connected with the CAN instrument, but of course, when performing fault elimination or reading fault codes, CAN communication equipment (such as a universal diagnostic apparatus) CAN also be connected to the CAN bus to send a fault code reading request to the ECU.
Step 102: and judging whether the main fault code contained in each calibration group exists in the read fault codes according to each calibration group.
Before step 102 is performed, groups may be preset, where the first element of each group is a master fault code, and the fault codes other than the first element are slave fault codes associated with the master fault code.
The number of the calibratable fault codes in each group can be set according to actual requirements.
For example, as shown in table 1, the packet includes three failure codes (the first element failure code 1 is the master failure code, and the remaining two element failure codes 2 and 3 are slave failure codes of failure code 1.
| Main fault | From faults | From faults |
| Fault code 1 | Fault code 2 | Fault code 3 |
TABLE 1
For another example, as shown in table 2, the packet includes three fault codes, the first element fault code 100 is the master fault code, and the remaining two element fault codes 112, 213 are the slaves of the fault code 100.
TABLE 2
Step 103: and when the judgment is yes, the slave fault code contained in the packet is acquired and sent to the CAN bus.
It should be noted that, after performing step 103, the fault status code of the slave fault code may also be modified to implement intervention of the slave fault code. The modification procedure may be: judging whether the fault state code of each slave fault code is a fault report state or not according to each slave fault code, if not, modifying the fault state code of the slave fault code into the fault report state, and storing the slave fault code into the fault memory.
Wherein, in the ECU, each fault code corresponds to a fault state code, and the fault state code generally comprises 8 Bit bits.
Alternatively, the fault status may be represented by the first and second Bit1Bit0, or the fourth Bit4 in the fault status code.
Namely, bit1Bit0 indicates the occurrence degree of the fault, and when "00" indicates that the fault is not diagnosed, and when "10" indicates that the fault is diagnosed; bit4 represents a fault report state, and represents fault report when "1" and fault cure when "0";
as can be seen from the above description, the fault report state refers to that Bit4 in the fault state code is 1, or Bit1Bit0 in the fault state code is 10.
Therefore, modifying the fault status code to the fault report status is to set Bit4 to 1 and Bit1 to Bit0 to 10
Thus, the engine fault reporting process shown in the figure 1 is completed, the problem that partial faults cannot be reported due to diagnosis errors can be effectively solved through the process shown in the figure 1, and timeliness and comprehensiveness of fault identification are improved.
Based on the embodiment shown in fig. 1, when the ECU detects the triggering condition of the fault sending instruction, besides the fault codes stored in the fault memory, the ECU also reports the slave fault codes associated with the master fault codes stored in the fault memory, and some of the slave fault codes may be stored in the fault memory, and some of the slave fault codes may not be in the fault memory, so in order to ensure timeliness and comprehensiveness of fault report, all the associated slave fault codes need to be reported.
Fig. 2 is a flowchart of an embodiment of another engine fault reporting method according to an exemplary embodiment of the present invention, which is also applied to an ECU on the basis of the embodiment shown in fig. 1, and as shown in fig. 2, the engine fault reporting method includes the following steps:
step 201: and judging whether the fault state code of the main fault code contained in each calibration group is a fault report state or not according to each calibration group.
The fault status code in step 103 may be that Bit4 is "1" or Bit1Bit0 is "10".
The first element of each calibration packet is a master fault code and the other fault codes than the first element are slave fault codes associated with the master fault code.
Step 202: and when judging that the fault code is in the unreported state, acquiring the fault code from the calibration packet, storing the acquired slave fault code into a fault memory, and sending the fault code stored in the fault memory to a CAN bus when receiving a fault code reading request and/or periodically sending the fault code request.
After the slave fault code whose fault state code is not reported is obtained from the calibration packet, the fault state code of the obtained slave fault code may be modified to be a reported state.
For the process from step 201 to step 202, reference may be made to the related description of the embodiment shown in fig. 1, which is not repeated.
Based on the embodiment shown in fig. 1, the ECU detects the failure reporting state of the master failure code in each packet in real time, and when a certain master failure code is in the failure reporting state, all the slave failure codes associated with the master failure code are stored in the failure memory, so that when a failure code reading request and/or a periodical failure code sending request are received, the failure code stored in the failure memory is sent to the controller area network CAN bus, and therefore timeliness and comprehensiveness of failure reporting CAN be ensured.
Fig. 3 is a hardware configuration diagram of an ECU according to an exemplary embodiment of the present invention, the ECU including: a communication interface 301, a processor 302, a machine-readable storage medium 303, and a bus 304; wherein the communication interface 301, the processor 302 and the machine-readable storage medium 303 perform communication with each other via a bus 304. The processor 302 may perform the engine fault reporting method described above by reading and executing machine executable instructions in the machine readable storage medium 303 corresponding to the control logic of the engine fault reporting method, the details of which are described above with reference to the above embodiments and will not be discussed again here.
The machine-readable storage medium 303 of the present invention may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: volatile memory, nonvolatile memory, or similar storage medium. In particular, the machine-readable storage medium 303 may be RAM (Radom Access Memory, random access memory), flash memory, a storage drive (e.g., hard drive), any type of storage disk (e.g., optical disk, DVD, etc.), or a similar storage medium, or a combination thereof.
The invention also provides an embodiment of the engine fault reporting device corresponding to the embodiment of the engine fault reporting method.
Fig. 4 is a flowchart showing an embodiment of an engine-failure warning apparatus according to an exemplary embodiment of the present invention, which may be applied to an ECU, as shown in fig. 4, the engine-failure warning apparatus including:
a reading module 410, configured to read the stored fault code from the fault memory when the fault sending instruction is detected;
a first transmitting module 420, configured to transmit the read fault code to the CAN bus;
a judging module 430, configured to judge, for each calibration packet, whether a master fault code included in the calibration packet exists in the read fault codes, where a first element of the calibration packet is the master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
and the second sending module 440 is configured to, when the determination is yes, obtain a slave fault code included in the packet and send the slave fault code to the CAN bus.
In an alternative implementation, the apparatus includes (not shown in fig. 4):
a state code modifying module, configured to determine, for each slave fault code, whether the fault state code of the slave fault code is a fault report state after the second sending module 440 obtains the slave fault code included in the packet and sends the slave fault code to the CAN bus; if not, modifying the fault state code of the slave fault code into a fault report state, and storing the slave fault code into the fault memory.
In an alternative implementation, the triggering condition of the fault sending instruction includes receiving a fault code reading request and/or periodically sending a fault code request.
Fig. 5 is a flowchart of an embodiment of another engine-failure warning device according to an exemplary embodiment of the present invention, which may be applied to an ECU, and which includes:
a judging module 510, configured to judge, for each calibration packet, whether a fault status code of a main fault code included in the calibration packet is a fault report status; the first element of the calibration group is a master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
and the storing module 520 is configured to, when the determination is yes, obtain a slave fault code whose fault status code is not reported from the calibration packet, store the obtained slave fault code into the fault memory, and send the fault code stored in the fault memory to the CAN bus when a fault code reading request and/or a periodic fault code sending request are received.
In an alternative implementation, the apparatus further comprises (not shown in fig. 5):
the state code modifying module is configured to modify the obtained fault state code of the slave fault code into the reported state after the storing module 520 obtains the slave fault code of the fault state code into the non-reported state from the calibration packet.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present invention. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the invention.
Claims (6)
1. An engine fault reporting method, the method comprising:
when a fault sending instruction is detected, reading a stored fault code from a fault memory and sending the stored fault code to a Controller Area Network (CAN) bus;
judging whether a main fault code contained in each calibration group exists in the read fault codes or not according to each calibration group, wherein a first element of the calibration group is the main fault code, and other fault codes except the first element are slave fault codes associated with the main fault code;
if yes, the slave fault code contained in the packet is obtained and sent to the CAN bus;
judging whether the fault state code of each slave fault code is a fault report state or not according to each slave fault code;
if not, modifying the fault state code of the slave fault code into a fault report state, and storing the slave fault code into the fault memory.
2. The method of claim 1, wherein the trigger condition of the fault send instruction comprises receiving a fault code read request and/or periodically sending a fault code request.
3. An engine fault reporting method, the method comprising:
judging whether the fault state code of the main fault code contained in each calibration grouping is a fault report state or not according to each calibration grouping; the first element of the calibration group is a master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
if yes, acquiring a fault state code from the calibration packet to be a slave fault code in an unreported state, storing the acquired slave fault code into a fault memory, and transmitting the fault code stored in the fault memory to a Controller Area Network (CAN) bus when a fault code reading request and/or a periodical fault code transmitting request are received;
and modifying the acquired fault state code of the slave fault code into a reported state.
4. An engine fault reporting apparatus, the apparatus comprising:
the reading module is used for reading the stored fault code from the fault memory when the fault sending instruction is detected;
the first sending module is used for sending the read fault code to a Controller Area Network (CAN) bus;
the judging module is used for judging whether the main fault code contained in the calibration grouping exists in the read fault codes according to each calibration grouping, wherein the first element of the calibration grouping is the main fault code, and the fault codes except the first element are the auxiliary fault codes related to the main fault code;
the second sending module is used for acquiring the slave fault code contained in the packet and sending the slave fault code to the CAN bus when the judgment is yes;
the state code modification module is used for judging whether the fault state code of each slave fault code is a fault report state or not according to each slave fault code; if not, modifying the fault state code of the slave fault code into a fault report state, and storing the slave fault code into the fault memory.
5. The apparatus of claim 4, wherein the trigger condition of the fault send instruction comprises receiving a fault code read request and/or periodically sending a fault code request.
6. An engine fault reporting apparatus, the apparatus comprising:
the judging module is used for judging whether the fault state code of the main fault code contained in each calibration grouping is a fault report state or not according to each calibration grouping; the first element of the calibration group is a master fault code, and other fault codes except the first element are slave fault codes associated with the master fault code;
the storage module is used for acquiring a slave fault code with a fault state code which is not reported from the calibration packet when judging that the fault state code is yes, and storing the acquired slave fault code into a fault memory so as to send the fault code stored in the fault memory to a Controller Area Network (CAN) bus when receiving a fault code reading request and/or a periodical fault code sending request;
and the state code modifying module is used for modifying the fault state code of the acquired slave fault code into the reported state after the storing module acquires the slave fault code with the fault state code being the non-reported state from the calibration packet.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911399202.7A CN111240871B (en) | 2019-12-30 | 2019-12-30 | Method and device for reporting engine fault |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911399202.7A CN111240871B (en) | 2019-12-30 | 2019-12-30 | Method and device for reporting engine fault |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111240871A CN111240871A (en) | 2020-06-05 |
| CN111240871B true CN111240871B (en) | 2023-07-18 |
Family
ID=70874112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911399202.7A Active CN111240871B (en) | 2019-12-30 | 2019-12-30 | Method and device for reporting engine fault |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240871B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101590918A (en) * | 2009-06-19 | 2009-12-02 | 上海微小卫星工程中心 | Method for automatic fault diagnosis of satellite and diagnostic system thereof |
| CN101814114A (en) * | 2010-01-07 | 2010-08-25 | 北京航空航天大学 | Method for performing fault diagnosis by using model conversion |
| CN102111508A (en) * | 2009-12-23 | 2011-06-29 | 中国移动通信集团设计院有限公司 | Fault processing method and system as well as fault scheduling equipment |
| CN105015565A (en) * | 2015-07-31 | 2015-11-04 | 株洲南车时代电气股份有限公司 | Automatic train fault information display method |
| CN106557083A (en) * | 2015-09-26 | 2017-04-05 | 广州汽车集团股份有限公司 | The DTC recording method of vehicle electrically controlling unit and vehicle electrically controlling unit |
| WO2018086256A1 (en) * | 2016-11-14 | 2018-05-17 | 深圳市元征科技股份有限公司 | Automobile fault diagnostic method and device |
| CN108074045A (en) * | 2018-01-30 | 2018-05-25 | 上海交通大学 | The vulnerability analysis of Wind turbines complete machine and fault sequencing method and electric terminal |
| CN110086664A (en) * | 2019-04-24 | 2019-08-02 | 新华三技术有限公司 | A kind of access device fault handling method and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007249441A (en) * | 2006-03-15 | 2007-09-27 | Hitachi Ltd | Virtualization system and failure coping method |
| KR100898339B1 (en) * | 2007-10-05 | 2009-05-20 | 한국전자통신연구원 | Autonomous fault processing system in home network environments and operation method thereof |
| CN101242309B (en) * | 2008-03-19 | 2011-12-07 | 中兴通讯股份有限公司 | A failure form processing method |
| CN101428595A (en) * | 2008-12-17 | 2009-05-13 | 厦门金龙联合汽车工业有限公司 | Bus line type passenger car fault alarm apparatus and method |
| CN202166714U (en) * | 2011-06-14 | 2012-03-14 | 天津市电力公司 | Overhead intelligent fault indicator |
| CN104243192B (en) * | 2013-06-17 | 2017-11-10 | 北京神州泰岳软件股份有限公司 | Fault handling method and system |
-
2019
- 2019-12-30 CN CN201911399202.7A patent/CN111240871B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101590918A (en) * | 2009-06-19 | 2009-12-02 | 上海微小卫星工程中心 | Method for automatic fault diagnosis of satellite and diagnostic system thereof |
| CN102111508A (en) * | 2009-12-23 | 2011-06-29 | 中国移动通信集团设计院有限公司 | Fault processing method and system as well as fault scheduling equipment |
| CN101814114A (en) * | 2010-01-07 | 2010-08-25 | 北京航空航天大学 | Method for performing fault diagnosis by using model conversion |
| CN105015565A (en) * | 2015-07-31 | 2015-11-04 | 株洲南车时代电气股份有限公司 | Automatic train fault information display method |
| CN106557083A (en) * | 2015-09-26 | 2017-04-05 | 广州汽车集团股份有限公司 | The DTC recording method of vehicle electrically controlling unit and vehicle electrically controlling unit |
| WO2018086256A1 (en) * | 2016-11-14 | 2018-05-17 | 深圳市元征科技股份有限公司 | Automobile fault diagnostic method and device |
| CN108074045A (en) * | 2018-01-30 | 2018-05-25 | 上海交通大学 | The vulnerability analysis of Wind turbines complete machine and fault sequencing method and electric terminal |
| CN110086664A (en) * | 2019-04-24 | 2019-08-02 | 新华三技术有限公司 | A kind of access device fault handling method and device |
Non-Patent Citations (2)
| Title |
|---|
| 一种基于多源信息的电网故障分析方法;陈祥文;王英英;李勇;李敏;黄勇;;电气应用(第01期);全文 * |
| 基于车载平台的ABS/ASR故障诊断系统开发;裴晓飞;刘昭度;齐志权;叶阳;;汽车技术(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111240871A (en) | 2020-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101575547B1 (en) | The error variance detection method of can communication system and the can communication system | |
| CN101739306A (en) | Method for processing data errors, and device and system for checking and correcting data errors | |
| KR20140116492A (en) | System and method for providing diagnostic fault information | |
| KR20080100247A (en) | Air conditioner and address setting method in air conditioner | |
| CN104282342A (en) | Flash memory device, memory controller and control method of flash memory | |
| US10088827B2 (en) | Numerical control device acquiring alarm information from connected IO unit | |
| CN111966287B (en) | Data storage method, electronic device and storage medium | |
| CN115352227B (en) | Tire identification method and identification device thereof, and tire identification method based on antenna | |
| CN110888763A (en) | Disk fault diagnosis method and device, terminal equipment and computer storage medium | |
| CN111240871B (en) | Method and device for reporting engine fault | |
| CN110471816B (en) | Data management method and device for solid state disk | |
| US11327842B2 (en) | Backing up a software update of a control device of transport vehicle | |
| US9499174B2 (en) | Method and apparatus for isolating a fault-active controller in a controller area network | |
| CN104718111B (en) | For exchanging the data in motor vehicles to run the method and apparatus of actuator | |
| US20080294805A1 (en) | Method of acquiring status information of i/o units | |
| CN102413004B (en) | Fault injection method and device | |
| US10317471B2 (en) | Battery communication diagnosis method | |
| US20170017559A1 (en) | System and method of monitoring a serial bus | |
| US8543879B2 (en) | Method and apparatus for correction of digitally transmitted information | |
| KR102444246B1 (en) | Manager device and method for detecting a failure of a tractor, and a non-transitory computer-readable recording medium including the same | |
| CN105721233A (en) | Website survival detection method, apparatus and system | |
| US11248990B2 (en) | Monitoring terminal, robot, and product testing method | |
| CN110471818B (en) | Method, device and equipment for marking error physical address of flash memory | |
| US8738221B2 (en) | Methods and systems for securing vehicle data | |
| US10097370B2 (en) | Method and system for programming a sensor network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |