Method and system for intelligent and continuous engine operation monitoring
By using processors and memory in the engine monitoring system, dynamically adjusting the data sampling rate and threshold, the problem that the EMU is not configured for intelligent and continuous detection is solved, intelligent and continuous engine monitoring is achieved, and data transmission and maintenance efficiency is optimized. .
Patent Information
- Application Number
- CN202210414976.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-09-05
- Filing Date
- 2019-09-02
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2039-09-02
Smart Images

Figure CN114624028B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with application number 201910823027.3 filed on September 2, 2019 and invention name “Method and system for intelligent and continuous engine operation monitoring”. Technical Field
[0002] The present invention relates to a method and system for intelligent and continuous engine operation monitoring. Background Art
[0003] The engine control unit (ECU) and associated engine monitoring functions, or engine monitoring units (EMUs), typically collect and send data to the aircraft's primary control system to allow maintenance personnel to make decisions, or to allow other systems communicatively coupled to the engine to make decisions. EMUs may also refer to actual units or engine monitoring functions within an ECU.
[0004] Whether it is the ECU or the EMU, there is a lot of data inside the engine; this data is not transmitted to other systems. This data is generated by the operation of the engine, and they can contain important information that can provide insight into the status and usage of the engine. Therefore, this data can provide useful life cycle management insights, help prevent failures and extend time on wing.
[0005] As non-limiting examples, these data may include internal engine sensor measurements or subsystem calculated states, such as the internal temperature of a combustion chamber. Furthermore, the values of these data may be parameterized, for example they may depend on the specific state of one or more engine subsystems. Currently, typical EMUs are not configured for intelligent and continuous engine monitoring. While they can record engine internal data, they do not do so in a way that maintenance personnel can easily gain correct insights into the engine's past operation and health. Therefore, with a typical EMU, engineers must decide what to store and what not to store given size and communication constraints. Summary of the invention
[0006] In view of the above problems, there is a need for intelligent and continuous engine monitoring that allows an EMU to measure key internal engine parameters and record the measurement data in such a way as to easily provide insights to maintenance personnel. In addition, given that internal engine data can be very large in nature, there is a need for an EMU that can appropriately mitigate the data size vs. data relevance tradeoff. The embodiments described herein help solve or mitigate the aforementioned problems and other problems unique to engine monitoring.
[0007] For example, one embodiment provides a system for monitoring an engine. The system includes a processor. The system also includes a memory, the memory including instructions that, when executed by the processor, cause the processor to perform certain operations. The operations may include receiving a first data set and a second data set. The first data set is sampled at a first rate, and the second data is sampled at a second rate, wherein the first rate is different from the second rate.
[0008] The operations further include determining whether an event that has occurred in the engine has occurred a predetermined number of times based on the number of occurrences of the first data set or the second data set. The operations further include recording the first data set as output in response to the number of occurrences exceeding the predetermined number, and recording the second data set as output otherwise.
[0009] Another embodiment provides a system for monitoring an engine. The system includes a processor and a memory, the memory including instructions that, when executed by the processor, cause the processor to perform certain operations. The operations may include calculating a ratio of a fast recording process to a slow recording process and adjusting the size of an output file based on the ratio.
[0010] Another embodiment provides a method for monitoring an engine. The method includes receiving, by a system communicatively coupled to the engine, a first data set and a second data set. The first data set is sampled at a first rate and the second data set is sampled at a second rate, wherein the first rate is different from the second rate. The method further includes determining, by the system, whether an event that has occurred in the engine has occurred a predetermined number of times based on a number of occurrences of the first data set or the second data set. Additionally, the method includes recording, by the system as an output, the first data set in response to the number of occurrences exceeding a predetermined number of times. Additionally, the method includes recording, by the system as an output, the second data set in response to the number of occurrences not exceeding a predetermined number of times. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 A system according to one embodiment is shown.
[0012] Figure 2 A method according to one embodiment is shown.
[0013] Figure 3 A system according to one embodiment is shown.
[0014] The accompanying drawings are for the purpose of illustrating preferred embodiments and should not be construed as limiting the present disclosure. The novel aspects of the present disclosure should be apparent to one of ordinary skill in the art in view of the following possible description of the drawings. This detailed description uses numerical and letter designations to refer to features in the accompanying drawings. The same or similar designations in the drawings and description have been used to refer to the same or similar parts of the embodiments. DETAILED DESCRIPTION
[0015] The illustrative embodiments may take the form of various components and arrangements of components. Illustrative embodiments are shown in the accompanying drawings, and the same reference numerals may indicate corresponding or similar parts in the various drawings throughout the drawings. The drawings are only used for the purpose of illustrating the embodiments and should not be construed as limiting the present disclosure. The novel aspects of the present disclosure should be apparent to one of ordinary skill in the relevant art in view of the possible description of the drawings below.
[0016] Typically, a non-limiting embodiment of the teaching of features in the present disclosure may be a variable rate monitoring system. This exemplary system reduces the recording speed during low-interest intervals of steady state and engine operation, and it responds to events and transients in operation by recording at a faster rate. The triggering and threshold values for implementing this rate switching may be adjustable (statically or dynamically) to accommodate different constraints on output file size, i.e., the amount of data output by the EMU. In addition, another feature may be a review subsystem that backfills the interval of fast recording before an event when an event is detected. In one example, an exemplary system may self-adjust threshold values to maintain file size constraints during unusual activity or eventful flight.
[0017] The exemplary embodiment may include various features or subsets of features that allow for intelligent and continuous engine monitoring. For example, but not limited to, the embodiment includes hardware configured to record time-varying parameters as time series data. Another feature of the hardware may be the ability to change the frequency of recording parameters, and the frequency may depend on changes in the underlying data (e.g., the magnitude of the rate of change). Another capability may be the ability to adapt sensitivity to changes by statically or dynamically adjusting thresholds.
[0018] Furthermore, another feature of the hardware can be the ability to capture high frequencies during transients and events. The hardware can assign a hierarchy to events, placing limits on the number of events at a given layer and on the total number of events. The limit on the number of events per layer can be adjusted. Furthermore, the list of recorded parameters can be categorized under various groups, each of which can have its own set of triggers, trigger events or sensitivity thresholds.
[0019] The hardware can be configured to provide a look-back feature so that when a condition triggers the fast recording option, a predetermined time interval prior to the trigger is retroactively placed in the file, giving a certain amount of pre-trigger high speed data. For example, a buffer of 30 seconds of high speed data can be maintained during slow recording. Then, when an event occurs, the most recent 30 seconds of slow data can be overwritten by the fast buffer and recording from that point onwards proceeds at a faster rate for a predetermined amount of time associated with the event.
[0020] Thresholds (for event and transient sensitivity) can be automatically adjusted so that the resulting file size (in MB / hour) tends to a predetermined value. This can be measured in terms of the ratio of fast to slow recordings. For example, if a lot of transient activity or many events are recorded at a high rate, so that the file size exceeds some desired MB / hour, the threshold can be self-adjusted to trigger less fast recording until the file size returns to normal.
[0021] Without loss of generality, embodiments may use a variety of numeric representations in addition to standard floating point, fixed point, and bit-packed formats, including parameter-specific n-bit fixed point similar to (but not limited to) the 717 / 767 format, or other space-efficient formats.
[0022] Figure 1 An intelligent monitoring system 100 is shown according to an embodiment. The system 100 includes an intelligent monitoring module 138 configured to perform one or more tasks associated with monitoring of an engine. For example, upon receiving input data from an aircraft and / or engine control module 102, the intelligent monitoring module 138 may perform one or more tasks including, but not limited to: variable rate data logging, event detection and classification, threshold processing, dynamic threshold adjustment, file size monitoring, and output formatting.
[0023] The input data may be, for example but not limited to, analog data obtained from analog sensors associated with the engine or other aircraft subsystems. The input data may include discrete data from one or more sensors associated with the engine or other aircraft subsystems. In addition, the input data may include digital data from a digital bus of the engine's EMU.
[0024] The intelligent monitoring module 138 can output the results of one or more tasks to the output module 104 outside the engine. The output module 104 can include an external memory 120 from which data can be retrieved by one or more means during or upon completion of the flight. For example, retrieval from the external memory 120 can be accomplished using the wireless transmission module 106, the wired transmission module 108, or by removing the removable data storage medium 110 from the external memory 120.
[0025] Similarly, the intelligent monitoring module 138 can output the results of one or more tasks to the internal memory 118, which is located inside the engine or one of its related subsystems, such as the EMU. During the flight or at the completion of the flight, the data can be extracted from the internal memory 118 using one or more means. For example, the extraction from the internal memory 118 can be achieved using the wireless transmission module 116, the wired transmission module 114, or by removing the removable data storage medium 112 from the internal memory 118.
[0026] Having described the input and output hardware and functionality of the smart monitoring module 138, the hardware and functionality within the smart monitoring module 138 is now described. Upon receiving input data from the module 102, the smart monitoring module 138 may process the input data at the input processing module 126 located therein. Processing at this stage may include formatting the data according to a predetermined format suitable for subsequent modules of the smart monitoring module 138.
[0027] In addition, the input processing module 126 can extract input engineering values from the input data. The input data is then routed to the operation and monitoring module 128, which can be programmed according to one or more functions associated with the monitoring of the engine. These functions, for example but not limited to, can include looking at the rate of change of data provided by a particular engine sensor. Another non-limiting function can include comparing the input data to a predetermined threshold to see if the input data is below or above the predetermined threshold. In addition, the operation and monitoring module 128 can output a calculated engineering value based on the input data as a result of its pre-programmed functions.
[0028] The input engineering values from the input processing module 126 and the calculated engineering values from the operation and monitoring module 128 are packaged together at the aggregation module 130, the output of which is then fed to the fast data buffer 134 and the slow data buffer 132. The respective rates of each of these buffers may be predetermined, or they may be dynamically set or adjusted based on thresholds set in the operation and monitoring module 128. Each data buffer outputs a stream to the smart monitoring processor 124, which performs one or more tasks that intelligently determine the contents of the smart data stream 136 that is routed to the external memory 120 and / or the internal memory 118.
[0029] Figure 2 A possible embodiment is shown. Figure 1 The smart monitoring processor 124 mentioned in the above. The smart monitoring processor 124 is an application-specific processor that is configured to perform the smart monitoring functions described herein. In one possible embodiment, the smart monitoring processor 124 is configured to perform the Figure 2 A set of instructions consistent with the method 200 shown in FIG.
[0030] The method 200 begins at start block 202 by first checking whether an event (e.g., an abnormal reading in the measurement data) is detected. When an event is detected (yes at decision block 204), decision block 210 checks whether the data from the slow data buffer 132 includes a number of occurrences of the event that exceeds a predetermined maximum value. In the event that the data from the slow data buffer 132 does not include the expected number of occurrences, the method 200 continues to decision block 212, where the same number of events check is performed on the data from the fast data buffer 134.
[0031] When the data from the fast data buffer 134 does not include the expected number of occurrences (no at decision block 212), the method 200 includes performing a fast record operation in addition to a review feature (block 214), which includes parsing the data buffer by a predetermined length to record data before the detected event occurred. The method 200 then moves to a calculation block (block 218) where a ratio of a moving average of a fast to slow record ratio is calculated, the slow record data from the slow record function (block 208) of the method 200. The moving average of the ratio is then used to adjust the different trigger thresholds (block 216).
[0032] When the operation at decision block 204 is no, the method 200 moves to decision block 206 where it is determined whether fast or slow recording is triggered (yes or no, respectively, at decision block 206). Additionally, when the number of occurrences exceeds the maximum number of occurrences, the method 200 moves from decision block 210 (yes) and performs slow recording at block 208. Similarly, when the number of occurrences exceeds the maximum number of occurrences, the method 200 moves from decision block 212 (yes) and performs slow recording at block 208. The method 200 dynamically and continuously outputs the intelligent data stream at block 216.
[0033] Figure 3 A system 300 is depicted that includes an application specific processor 314 configured to perform tasks specific to intelligent and continuous data logging from an aircraft engine. The processor 314 has a specific structure 8 imparted by instructions stored in the memory 302 and / or instructions 318 accessible by the processor 314 from the memory 320. The memory 320 may be co-located with the processor 314, or it may be located elsewhere and communicatively coupled to the processor 314, for example, via a communication interface 316.
[0034] System 300 may be a stand-alone programmable system, or it may be a programmable module located in a larger system. For example, system 300 may be part of an EMU. Processor 314 may include one or more hardware and / or software components configured to acquire, decode, execute, store, analyze, distribute, evaluate, and / or classify information.
[0035] In addition, processor 314 may include an input / output module (I / O module 312), which may be configured to ingest data related to a single asset or a group of assets. Processor 314 may include one or more processing devices or cores (not shown). In some embodiments, processor 314 may be a plurality of processors, each having one or more cores. Processor 314 may be configured to execute instructions taken from memory 302 (i.e., taken from one of memory block 304, memory block 306, memory block 308, and memory block 310).
[0036] Furthermore, without loss of generality, memory 320 and / or storage 302 may include volatile or nonvolatile, magnetic, semiconductor, tape, optical, removable, non-removable, read-only, random access, or any type of non-transitory computer-readable computer media. Memory 320 may be configured to record data processed, recorded, or collected during operation of processor 314. The data may be time-stamped, location-stamped, registered, indexed, or organized in a variety of ways consistent with data storage practices. Memory 320 and / or storage 302 may include programs and / or other information that processor 314 may use to perform tasks consistent with the tasks described herein.
[0037] For example, the processor 314 can be configured by instructions from the memory block 306, the memory block 308, and the memory block 310 to perform operation threshold adjustment, fast recording, and slow recording, respectively. Upon receiving input from the slow data buffer 132 and the fast data buffer 134, the processor 314 can execute the above instructions from the memory blocks 306, 308, and 310, and output a file containing the intelligent data stream 136 via the output 322.
[0038] In general, the embodiments described herein allow for intelligent and continuous logging of engine operating data in the EMU. In such applications, there is a trade-off in file size; i.e., more parameters, logged at higher speeds, resulting in larger data files. Conversely, operators want to minimize the maintenance burden (for manual data retrieval) or minimize the time / cost of wireless transmission at the door or in flight. The embodiments herein help to address or mitigate these issues.
[0039] Those skilled in the relevant art will appreciate that various modifications and adaptations of the above embodiments may be configured without departing from the scope and spirit of the present disclosure. Therefore, it should be understood that within the scope of the appended claims, the exemplary features described herein may be implemented in a manner other than that specifically described herein.
[0040] Further aspects of the invention are provided by the subject matter of the following clauses:
[0041] 1. A system for monitoring an engine, the system comprising: a processor; a memory, the memory comprising instructions, when the instructions are executed by the processor, causing the processor to perform operations, the operations comprising: receiving a first data set and a second data set, the first data set having been sampled at a first rate, the second data set having been sampled at a second rate, the first rate and the second rate being different; determining whether an event that has occurred in the engine has occurred a predetermined number of times based on a number of occurrences in the first data set or the second data set; in response to the number of occurrences exceeding the predetermined number of times, recording the first data set as an output; in response to the number of occurrences not exceeding the predetermined number of times, recording the second data set as the output.
[0042] 2. A system according to any preceding clause, wherein the first rate is lower than the second rate.
[0043] 3. A system according to any preceding clause, wherein the first data set and the second data set are retrieved from a slow data buffer and a fast data buffer, respectively.
[0044] 4. A system according to any preceding clause, wherein the output is a smart data stream, the smart data stream comprising a portion having data, the data having more than one sampling rate.
[0045] 5. A system according to any preceding clause, wherein the output is a file.
[0046] 6. A system according to any preceding clause, wherein the operations further comprise calculating a ratio of fast to slow records.
[0047] 7. A system according to any preceding clause, wherein the operations further comprise calculating a moving average of the ratio.
[0048] 8. The system of any preceding clause, wherein said operations further comprise adjusting an output file size based on said moving average of said ratio.
[0049] 9. A system according to any preceding clause, wherein the operations further comprise updating a threshold value.
[0050] 10. A system for monitoring an engine, the system comprising: a processor; a memory, the memory comprising instructions, which, when executed by the processor, cause the processor to perform operations, the operations comprising: calculating a ratio of a fast record processing time to a slow record processing time; and adjusting an output file size growth rate based on the ratio.
[0051] 11. A system according to any preceding clause, wherein when said ratio is greater than a threshold, said output file size growth rate is reduced.
[0052] 12. A system according to any preceding clause, wherein when said ratio is less than a threshold, said output file size growth rate is increased.
[0053] 13. The system of any preceding clause, wherein the operations further comprise determining whether a parameter from an input data stream has exceeded a threshold.
[0054] 14. The system of any preceding clause, wherein the operations further comprise performing one of the fast recording process and the slow recording process based on the parameter exceeding the threshold.
[0055] 15. A system according to any of the preceding clauses, further comprising adjusting a parameter threshold based on the ratio.
[0056] 16. A method for monitoring an engine, the method comprising: receiving a first data set and a second data set by a system communicatively coupled to the engine, the first data set having been sampled at a first rate, the second data set having been sampled at a second rate, the first rate and the second rate being different; determining by the system whether an event that has occurred in the engine has occurred a predetermined number of times based on the number of occurrences in the first data set or the second data set; in response to the number of occurrences exceeding the predetermined number of times, recording by the system the first data set as an output; in response to the number of occurrences not exceeding the predetermined number of times, recording by the system the second data set as the output.
[0057] 17. A system according to any preceding clause, wherein said first rate is lower than said second rate.
[0058] 18. A system according to any preceding clause, wherein the output is a smart data stream, the smart data stream comprising a portion having data, the data having more than one sampling rate.
[0059] 19. A system according to any preceding clause, wherein the output is a file.
[0060] 20. A system according to any preceding clause, wherein the operations further comprise calculating a ratio of fast to slow records.
Claims
1. A system for monitoring an engine, characterized in that: include: processor; and A memory, the memory comprising instructions, which, when executed by the processor, cause the processor to perform operations, the operations comprising: Calculate the ratio of fast data record processing time to slow data record processing time; and Adjusts the output file size growth rate according to the stated ratio.
2. The system according to claim 1, characterized in that When the ratio is greater than a threshold, the growth rate of the output file size is reduced.
3. The system according to claim 1, characterized in that When the ratio is below a threshold, the growth rate of the output file size is increased.
4. The system according to claim 1, characterized in that The operations further include determining whether a parameter from the input data stream has exceeded a parameter threshold.
5. The system according to claim 4, characterized in that The operations further include performing one of the fast data recording process and the slow data recording process based on the parameter exceeding the parameter threshold.
6. The system according to claim 1, characterized in that Further comprising adjusting a parameter threshold based on the ratio.
7. A method for monitoring an engine, characterized in that: include: Calculate the ratio of fast data record processing time to slow data record processing time; and Adjusts the output file size growth rate according to the stated ratio.
8. The method according to claim 7, characterized in that When the ratio is greater than a threshold, the growth rate of the output file size is reduced.
9. The method according to claim 7, characterized in that: When the ratio is below a threshold, the growth rate of the output file size is increased.
10. The method according to claim 7, characterized in that Further included is determining whether a parameter from the input data stream has exceeded a parameter threshold.
11. The method according to claim 10, characterized in that Further comprising performing one of the fast data recording process and the slow data recording process based on the parameter exceeding the parameter threshold.
12. The method according to claim 7, characterized in that Further comprising adjusting a parameter threshold based on the ratio.
