Monitoring system for engine performance and failure prediction

CN114550337BActive Publication Date: 2026-06-02CATERPILLAR INC

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
CATERPILLAR INC
Filing Date
2021-11-10
Publication Date
2026-06-02

Smart Images

  • Figure CN114550337B_ABST
    Figure CN114550337B_ABST
Patent Text Reader

Abstract

In some implementations, a remote monitoring system can receive historical usage data associated with a plurality of engines, which are associated with a plurality of respective machines. The remote monitoring system can train an engine monitoring model to identify usage profiles indicative of potential failures by identifying operating ranges for operating parameters from operating profiles. The remote monitoring system can receive usage data from a machine, which includes measurements of operating parameters of an engine of the machine, and determine that the engine is configured to operate according to an operating profile. The remote monitoring system can predict that the engine is likely to fail within a certain time period based on determining that the engine is configured to operate according to the operating profile and based on the measurements and the operating ranges.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention generally relates to engine monitoring, and for example to a monitoring system for engine performance and fault prediction. Background Technology

[0002] Operating an engine (e.g., the engine of a powertrain) generally involves a trade-off between durability and performance. For example, an engine that is operated more aggressively to achieve higher performance is more likely to fail (or lose durability) at a faster rate than an engine that is operated less aggressively and / or with lower performance. Cumulative damage to the engine shortens its service life. In prior art, the engine can be continuously monitored via a model to determine its operating state and the corresponding state of the engine relative to model parameters. However, monitoring of damage becomes problematic when unpredictable actions and / or operations of the engine cause the model to be inaccurate regarding predictability or the determination of cumulative damage. Furthermore, such models can detect damage to the engine after the level of damage has reached a catastrophic level or a level that reduces the engine's service life.

[0003] Furthermore, in certain situations (e.g., certain types of weather events, specific location conditions, certain uses or operations, etc.), the operator may determine that the probability of a failure is acceptable. For example, the operator may expect to optimize performance in such situations (e.g., relative to preventing damage), thereby allowing the monitoring model to operate the engine based on optimized performance. However, similar to the above, certain unforeseen actions and / or operations of the engine may cause the model to be inaccurate relative to configuring the engine to operate for optimized performance, thereby reducing the effectiveness and / or efficiency of operations performed by the machine associated with the engine.

[0004] For example, U.S. Patent Application Publication No. 2019 / 131607 discloses a device for remote engine monitoring that can store and / or display data about the monitored engine characteristics, and / or send such data to a location removed from the engine. While this device allows for remote engine monitoring, it establishes a baseline standard operating range for each asset and can detect events outside the standard operating parameters for each asset.

[0005] The remote monitoring system of the present invention solves one or more of the above-mentioned problems and / or other problems in the art. Summary of the Invention

[0006] In some implementations, one method includes receiving historical usage data associated with multiple engines of an engine type, which are associated with multiple corresponding machines; training an engine monitoring model based on the historical usage data to identify usage profiles indicating potential failures of the engine type, wherein the usage profiles identify the operating range of operating parameters of the engine type based on operating profiles associated with operating one or more of the multiple engines; receiving usage data from the machines, the usage data including measurements of the operating parameters of the machines' engines; determining that the engines are configured to operate according to the operating profiles; predicting, based on the determination that the engines are configured to operate according to the operating profiles and based on the measurements and operating ranges, that the engines may fail within a certain time period; and performing actions associated with the machines.

[0007] In some implementations, a device includes one or more memories and one or more processors configured to: receive usage data associated with engines of a plurality of respective machines from an onboard engine monitoring system of a plurality of respective machines; determine, from the usage data, a subset of engines associated with the plurality of respective machines, configured to operate according to an operational profile; determine an operational range based on measurements of operational parameters associated with the usage of the engine subset, and from the usage data; receive measurements of operational parameters of the engines of a machine from an onboard engine monitoring system associated with a machine of the plurality of respective machines; determine a possible engine failure based on the measurements and the operational range; and perform actions associated with the machine.

[0008] In some implementations, a non-transitory computer-readable medium storing a set of instructions includes one or more instructions that, when executed by one or more processors of the device, cause the device to: receive notification from the machine's onboard engine monitoring system that measurements of the machine's engine operating parameters are outside the machine's operating range; determine from the notification that the engine is configured to operate according to an operating profile associated with the operating range; identify historical usage data associated with the engine based on historical usage data mapped in a data structure to identifiers associated with the engine; determine a measurement pattern associated with the operating parameters from the historical usage data; determine an optimal operating configuration based on the measurements, the measurement pattern, and other historical usage data associated with multiple other machines; and perform actions associated with the machine and the optimal operating configuration. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example implementation of the remote monitoring system described in this article.

[0010] Figure 2 This is a diagram of an example of the engine monitoring system described in this article.

[0011] Figure 3This is a flowchart of an example process associated with a monitoring system used for engine performance and fault prediction. Detailed Implementation

[0012] This invention relates to a remote monitoring system and / or an engine monitoring system applicable to any machine including engines controlled according to one or more operating profiles providing optimized control of the engine. For example, the machine may be a vehicle, compactor, paver, planer, grader, backhoe loader, wheel loader, harvester, excavator, automatic grader, skid-steer loader, tractor, bulldozer, generator, generator set, etc.

[0013] Figure 1 This is a diagram of Example 100 associated with the remote monitoring system described herein. (See diagram for example.) Figure 1 As shown, Example 100 includes N machines 102 (shown as 102-1 to 102-N, where N is an integer and N≥1) (referred to herein solely as "machine 102" and collectively as "machine 102"), each including a corresponding engine monitoring system 104 (shown as 104-1 to 104-N) (referred to herein solely as "engine monitoring system 104" and collectively as "engine monitoring system 104"). Figure 1 As further shown, Example 100 includes a remote monitoring system 106, which includes an engine monitoring model 108 and a maintenance management system 110. Figure 1 One or more of the example machines, devices, or components can communicate wirelessly via network 112 (e.g., a wireless communication network).

[0014] As described herein, engine monitoring system 104 may provide usage data 114 to remote monitoring system 106 via a network. Based on usage data 114 and one or more example processes described herein for predicting faults, remote monitoring system 106 may determine and / or transmit communications 116 (e.g., messages, notifications, instructions, and / or the like) to engine monitoring system 104 to prevent potential faults from occurring within a certain time period.

[0015] In Example 100, the remote monitoring system 106 may include data structures that map identifiers of machine 102 to corresponding operational profiles and / or usage patterns of machine 102. For example, an operational profile may identify a set or configuration of operational ranges for one or more operational parameters (such as engine speed, load, etc.). Additionally or alternatively, an operational profile may identify indicators of certain measurements (e.g., sensor measurements) and / or inferred physical indicators (e.g., measured temperature, measured pressure associated with certain components of the engine). Usage patterns may include information associated with certain events related to measuring and / or monitoring one or more operational parameters of the machine's engine. More specifically, usage patterns may include information and / or data in the form of histograms associated with the time at which operational parameters are measured and / or sensed at certain levels, and / or histograms associated with when or where operational parameters exceed certain thresholds (which can be dynamically evaluated). As described herein, the maintenance management system 110 may include one or more devices and / or platforms capable of facilitating the scheduling of maintenance services, ordering parts and / or materials for maintenance services, and / or providing maintenance services (e.g., to extend the service life of each engine of machine 102, and correspondingly extend the service life of each machine 102) based on received maintenance information 118 (e.g., in a maintenance request). The maintenance information 118 may include the required type of maintenance, replacement parts required for the maintenance service, the location of the maintenance service, etc.

[0016] Network 112 includes one or more wired and / or wireless networks. For example, network 112 may include cellular networks (e.g., fifth-generation (5G) networks, fourth-generation (4G) networks, Long Term Evolution (LTE) networks, third-generation (3G) networks, Code Division Multiple Access (CDMA) networks, etc.), Public Land Mobile Networks (PLMNs), Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks (MANs), telephone networks (e.g., Public Switched Telephone Networks (PSTN)), private networks, ad hoc networks, intranets, the Internet, fiber-optic networks, etc., and / or combinations of these or other types of networks. Network 112 enables communication between devices in environment 100.

[0017] The engine monitoring system 104 may include one or more devices on the onboard machine 102 and is configured to monitor the performance of the machine 102 by obtaining measurements of one or more operating parameters of the machine 102, as described herein at least in conjunction with Figure 2 The engine monitoring system 104 can transmit measurements as usage data of machine 102 to remote monitoring system 106, allowing remote monitoring system 106 to analyze usage data and / or predict engine-related faults of machine 102 based on measurements and / or historical usage data associated with machine 102 (and / or one or more groups of machines 102).

[0018] In this way, the remote monitoring system 106 can receive usage data associated with the engines of each machine 102, classify and / or sort the usage data (e.g., based on machine identifier, machine type, machine operating profile, etc.), and / or store the usage data in the data structure of the remote monitoring system 106. The remote monitoring system 106 can determine measurements associated with operating parameters when the engine operates according to the operating profile from the usage data (e.g., based on the engine's instruction settings in the usage data). The operating profile (or each individual operating profile configured for machine operation) can indicate settings associated with optimizing engine performance (e.g., maximizing power, torque, speed, responsiveness, etc.) (e.g., corresponding to operator preferences, default settings, etc.), settings optimizing engine lifespan (e.g., conserving engine resources, preventing drastic changes in operating parameters that could damage the engine, etc.), and / or settings balancing certain desired optimizations.

[0019] As described herein, the remote monitoring system 106 can determine the operating range based on measurements of operating parameters. Operating parameters may include the speed of engine components, the temperature of engine components, emission metrics associated with exhaust from the engine (e.g., metrics such as the condition of emission components of a filter, metrics of the amount of certain types of emission particles in the exhaust, etc.), or intake metrics associated with engine intake (e.g., intake pressure, intake temperature, etc.). The remote monitoring system 106 can analyze usage data from the machine 102 (e.g., received on the most recent set of days, weeks, months, years, etc.) to determine the operating range. In some implementations, the remote monitoring system 106 selects the most relevant set of usage data to determine the operating range of the operating parameters. For example, the remote monitoring system 106 may select usage data for the engine and / or machine 102 that includes measurements of the engine and / or machine 102 when the machine 102 is operating in the same area, location, site, etc. Alternatively, the remote monitoring system 106 may optionally use data, including measurements of the engine and / or machine 102 when performing operations of the same type as the received notifications or measurements.

[0020] like Figure 1As shown, the remote monitoring system 106 may include an engine monitoring model 108. The engine monitoring model 108 may include and / or utilize one or more types of machine learning models, such as one or more types of neural networks, one or more types of linear regression models, one or more types of supervised or unsupervised learning models, one or more types of classification models, one or more types of similarity models, one or more types of clustering models, etc. The remote monitoring system 106 (and / or another platform associated with the remote monitoring system 106) may train the engine monitoring model based on historical usage data associated with the machine 102 and / or received from one or more engine monitoring systems 104 (e.g., usage data received during training periods associated with the machine learning model). In some implementations, a product health database including historical data is used to train the remote monitoring system, identifying information associated with known historical faults and / or historical performance of operations augmented with corresponding measured or simulated operating parameter values.

[0021] Historical data can be used to train the engine monitoring model 108, which is associated with historical values ​​of one or more indicator metrics to identify the operating range of operating parameters (e.g., the expected range based on a specific operating profile of the engine). Such indicator metrics may include engine type, engine operating profile, engine usage (e.g., operating hours, load, etc.), engine utilization rate, engine manufacturing date or year, engine operating location, type of operation performed by machine 102, engine performance metrics (e.g., measured output speed, torque, power, etc.), etc. Indicator metrics may be associated with indications of potential engine malfunctions and / or potential engine performance deficiencies.

[0022] Using historical data and values ​​of one or more fault indication metrics as input to engine monitoring model 108, remote monitoring system 106 can determine the operating range (e.g., optimal operating range) of an engine (or engine type) based on usage data associated with the historical use of multiple machines. This allows remote monitoring system 106 to predict potential faults and / or when faults may occur (e.g., within a certain number of hours, days, weeks, etc.), as described herein. In some implementations, as described herein, remote monitoring system 106 can retrain engine monitoring model 108 by updating historical usage data to include valid or invalid results associated with input values ​​of one or more fault indication parameters.

[0023] Therefore, during operation, the remote monitoring system 106 can receive notifications from the engine monitoring system 104 of machine 102 regarding measurements of engine operating parameters outside the machine's operating range. In some implementations, the engine monitoring system 104 may utilize the operating range to detect potential engine malfunctions and / or insufficient engine performance, or to notify the remote monitoring system 106 when measurements of operating parameters are outside the operating range (e.g., based on the operating range received from the remote monitoring system 106). The engine monitoring system 104 may notify the remote monitoring system 106 after each detected measurement exceeding the operating range, or after a threshold amount of measurement exceeds the operating range (e.g., within a certain time period). Alternatively, the engine monitoring system 104 may notify the remote monitoring system 106 whenever the engine monitoring system 104 becomes communicatively connected to the remote monitoring system 106 (e.g., after establishing a connection to network 112, after becoming within the communication range of network 112, etc.). The engine monitoring system 104 may periodically send notifications based on a pre-configured schedule. In this scenario, the remote monitoring system 106 can determine the engine's operating profile (e.g., when measurements are outside the operating range). Based on the engine's operating profile, the remote monitoring system 106 can analyze usage data associated with the engine of machine 102 (e.g., usage data of engines operating under the same operating profile) to identify measurement patterns associated with operating parameters. For example, a measurement pattern can identify timing information associated with operating parameters outside the operating range (e.g., a timestamp when the operating parameter is measured outside the operating range, a time delay or duration between engine start and when the operating parameter is measured outside the operating range, etc.). In some implementations, the measurement pattern can be combined with one or more other measurement patterns for other operating parameters to generate or form the usage patterns described herein.

[0024] Based on measurement patterns and / or usage patterns associated with those patterns, remote monitoring system 106 can determine the probability (e.g., based on a scoring system, weighted average, etc.) that an engine (or a component of an engine) will fail within a threshold time period (e.g., a time period shorter than a regularly scheduled maintenance period). In this case, if the probability meets a threshold probability of failure (e.g., 50% or greater, 75% or greater, 90% or greater), remote monitoring system 106 can perform one or more actions to reduce the risk of failure and / or prevent failure, as described herein. In some implementations, if the duration between operating parameters outside the operating range of a particular operating profile of the engine is increasing, remote monitoring system 106 can identify a higher probability that the engine of machine 102 (or vice versa) will fail. For example, remote monitoring system 106 can determine the optimal operating configuration of the engine, which indicates one or more settings or operating ranges of certain operating parameters of the engine (e.g., including operating parameters associated with measurements provided by engine monitoring system 104 or other operating parameters of the engine).

[0025] The remote monitoring system 106 can provide optimal operating configurations to the engine monitoring system 104 (e.g., the engine monitoring system 104 that sends notifications) and / or to one or more other engine monitoring systems 104 associated with the machine 102 that provides the notification. In this way, the remote monitoring system 106 can determine the optimal operating configuration for the engine, identifying the settings of the engine's operating parameters and / or one or more other operating parameters, which reduces the probability of engine failure associated with operating parameters that are operating outside the operating range.

[0026] As described herein, remote monitoring system 106 can identify engine usage patterns from usage data. Usage patterns can indicate engine usage volume, utilization rate, usage type, etc. Based on the usage pattern and measurements (which may be the most recently received data point of the usage pattern), remote monitoring system 106 can determine a usage score representing the remaining operability duration of the engine. Based on the usage score, remote monitoring system 106 can perform actions to extend the service life of the engine of machine 102. For example, the remote monitoring system can use maintenance management system 110 to enable machine 102 to receive maintenance services associated with the engine, such as transporting machine 102 to a maintenance location managed by the maintenance management system by scheduling an appointment via the maintenance management system. Maintenance management system 110 may include one or more devices and / or platforms configured to facilitate and / or provide maintenance services for the engine of machine 102.

[0027] In some implementations, the remote monitoring system 106 can interact with one or more other systems of the machine 102. For example, based on a timeline for predicting potential or possible engine failures, the remote monitoring system 106 can transmit a message indicating that the engine may fail within a certain time period to the user interface of the machine 102 (e.g., at the operator station of the machine 102). Alternatively, the remote monitoring system 106 can provide information associated with optimal operating configurations (e.g., within messages and / or other communications that can be displayed or announced via the user interface of the machine 102). For autonomous vehicles or semi-autonomous machines, the remote monitoring system 106 can transmit engine control commands to the engine controller of the machine 102 to cause the engine controller to control the engine of the machine 102 according to the optimal operating configuration. Alternatively, the remote monitoring system 106 associated with the maintenance management system 110 can enable such autonomous vehicles to navigate to and / or toward repair facilities.

[0028] As mentioned above, providing Figure 1 As an example. Other examples may be related to... Figure 1 The descriptions are different.

[0029] Figure 2 This is a diagram of Example 200 associated with the engine monitoring system described herein. (See diagram 200.) Figure 2 As shown, Example 200 may include one or more engine controllers 210 (specifically referred to as "engine controller 210" and collectively as "engine controller 210"), one or more sensors 220 (specifically referred to as "sensor 220" and collectively as "sensor 220"), and an engine monitoring system 230. Figure 2 As shown, the engine monitoring system 230 may include a processor 232, a memory 234, an event detection module 240, and an operation overview module 250. The engine monitoring system 230, as described herein, is implemented in hardware via the processor 232 and / or the memory 234.

[0030] The engine controller 210 can be any type of device used by the machine 102 to control the operating parameters of the engine of the machine 102. For example, the engine controller 210 may include one or more actuators, switches, etc., capable of opening and / or closing valves within the engine, regulating the temperature within the engine (e.g., using a fan, cooling system, etc.), regulating the pressure within the engine, etc.

[0031] Engine controller 210 may be associated with one or more adjustable parameters, which may be optimized via an optimization process as described herein. For example, the values ​​of the adjustable parameters of engine controller 210 may represent or indicate settings of engine controller 210, such as actuator position, valve opening duration, valve position, engine operating temperature, compressed air and / or fuel pressure, etc.

[0032] Sensor 220 may include any type of sensor configured to measure the operating conditions of the engine. Sensor 220 may be a sensor system of machine 102 and / or a sensor of the engine of machine 102. For example, sensor 220 may include a temperature sensor (e.g., for detecting the temperature of air, exhaust, components, coolant, etc.), a position sensor (e.g., for detecting the position of valves, actuators, engine parts (e.g., pistons), etc.), a speed sensor (e.g., for detecting engine speed, machine speed, etc.), a pressure sensor (e.g., for detecting the compression of air or exhaust in the engine), an emission sensor (e.g., for detecting the emission level of the engine), etc.

[0033] As described herein, sensor 220 can be used to sense one or more operating parameters that can be used to determine the operating state of the engine and / or the usage profile associated with the engine. For example, the values ​​of the operating parameters of one or more sensors 220 can represent or indicate the measurements of sensor 220, such as temperature measured by a temperature sensor, timing of valve opening and / or closing measured by a position sensor, engine speed measured by a speed sensor, actuator position measured by a position sensor, emissions measured by an emissions sensor, etc.

[0034] Engine monitoring system 230 can be connected with Figure 1 The processor 232 is associated with the engine control module (ECM) of the machine 102. The processor 232 is implemented in hardware, firmware, and / or a combination of hardware and software. The processor 232 is a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or another type of processing unit. The processor 232 includes one or more processors that can be programmed to perform functions. The memory 234 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions used by the processor 232 (e.g., information and / or instructions associated with the event detection module 240, operation overview module 250, etc.).

[0035] The engine monitoring system 230 can also identify, acquire, and / or determine measurements of operating parameters associated with the engine, such as engine speed, fuel rate or quantity, injection timing, intake manifold temperature (IMAT), intake manifold pressure (IMAP), current intake valve actuation (IVA) termination, IVA timing, intake throttle position, injected air pressure, injected fuel pressure, torque delivered by the engine, total fuel injection quantity, exhaust pressure, cylinder ignition quantity, oxygen / fuel molar ratio, ambient temperature, ambient pressure (e.g., atmospheric pressure), mass flow rate through the particulate collection device, exhaust back pressure valve position, injection mode, coolant temperature, total intake air mass flow rate in multi-injection mode, residence time in multi-injection mode (e.g., time length between injections), etc.

[0036] Event detection module 240 is configured to identify that measurements of operating parameters are outside the operating range associated with operating parameters related to the engine's operating state. Operation profile module 250 can store and / or maintain the operating ranges of operating parameters for multiple different operating profiles of the engine. For example, a first operating range of a first operating profile designated for extending the service life of the engine of machine 102 may differ from a second operating range of a second operating profile designated for providing enhanced performance of the engine of machine 102. As a more specific example, an operation profile for extending engine service life may have a relatively lower engine component temperature range compared to an operation profile for enhancing engine performance (e.g., because higher temperatures achieved during relatively high performance are more likely to damage components and / or the engine). Operation profile module 250 can store timing information that identifies the periods of operation during which the engine operates according to different engine operating profiles. In some implementations, the operation profile module may be updated based on instructions and / or information received from remote monitoring system 106, as described herein (e.g., to change the operating range of one or more operating parameters).

[0037] The communication component 260 enables the engine monitoring system 230 to communicate with other devices, such as via wired and / or wireless connections. For example, the communication component 260 may include a receiver, transmitter, transceiver, modem, network interface card, antenna, etc.

[0038] User interface 270 may include one or more input components and / or one or more output components to facilitate interaction between the operator and the machine. User interface 270 enables engine monitoring system 230 to receive input, such as operator input and / or sensed input. For example, input components 250 may include a touchscreen, keyboard, keypad, mouse, buttons, microphone, switch, GPS component, etc. User interface 270 enables engine monitoring system 230 to provide output, such as via a display, speaker, and / or one or more light-emitting diodes.

[0039] As mentioned above, providing Figure 2 As an example. Other examples may be related to... Figure 2 The descriptions are different. Figure 2 The number and arrangement of the equipment shown are provided as an example. In fact, with... Figure 2 Compared to those shown, there may be additional equipment, fewer devices, different equipment, or devices arranged differently. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 2 The single device shown can be implemented as multiple distributed devices. Alternatively, Figure 2 The set of devices shown (e.g., one or more devices) can perform the actions described by [the following]. Figure 2 The other set of devices shown performs one or more functions.

[0040] Figure 3 This is a flowchart of an example process 300 associated with a monitoring system used for engine performance and fault prediction. In some implementations, Figure 3 One or more process frames can be executed by a remote monitoring system (e.g., remote monitoring system 106). In some implementations, Figure 3 One or more process frames may be executed by another device or a group of devices that are separate from or include the remote monitoring system, such as an engine monitoring system (e.g., engine monitoring system 104 and / or engine monitoring system 230).

[0041] like Figure 3 As shown, process 300 may include receiving historical usage data associated with multiple engines (block 310). For example, as described above, a remote monitoring system may receive historical usage data associated with multiple engines of a specific engine type, which are associated with multiple corresponding machines.

[0042] like Figure 3 As further shown, process 300 may include training an engine monitoring model to identify usage profiles indicating potential faults (box 320). For example, a remote monitoring system may train the engine monitoring model based on historical usage data to identify usage profiles indicating potential faults of an engine type, wherein the usage profile identifies the operating range of operating parameters for the engine type based on operating profiles associated with operating one or more of a plurality of engines, as described above.

[0043] The usage profile can identify the operating range of operating parameters for an engine type based on the operating profile associated with operating one or more of a plurality of engines. Operating parameters may include at least one of the following: engine component speeds, engine component temperatures, emission metrics associated with exhaust gas from the engine, or intake metrics associated with engine intake gas. The operating profile may be associated with at least one of settings that optimize engine performance metrics or settings that optimize engine lifespan.

[0044] like Figure 3 As further shown, process 300 may include receiving usage data from the machine, which includes measurements of operating parameters of the machine's engine (box 330). For example, as described above, a remote monitoring system may receive usage data from the machine, which includes measurements of operating parameters of the machine's engine. When the machine is in operation, usage data may be received from an onboard engine monitoring system.

[0045] like Figure 3 As further shown, process 300 may include determining that the engine is configured to operate according to an operational profile (block 340). For example, as described above, a remote monitoring system may determine that the engine is configured to operate according to an operational profile.

[0046] like Figure 3 As further shown, process 300 may include predicting engine failure within a certain time period based on measurements and operating range (box 350). For example, as described above, a remote monitoring system may predict engine failure within a certain time period based on determining that the engine is configured to operate according to an operating profile and based on measurements and operating range.

[0047] like Figure 3 As further shown, process 300 may include performing actions associated with the machine (box 360). For example, as described above, a remote monitoring system may perform actions associated with the machine. The remote monitoring system may send a notification to the machine's user interface indicating a possible engine failure.

[0048] The remote monitoring system can acquire confirmation information associated with identifying potential engine failure and retrain the engine monitoring model based on this confirmation information and usage data. Alternatively, the remote monitoring system can identify engine usage patterns from usage data. Based on usage patterns and measurements, the remote monitoring system can determine a usage score associated with the machine. The usage score can represent the remaining operational time of the engine. The remote monitoring system can determine if the usage score meets maintenance thresholds and / or warrant maintenance services associated with the engine.

[0049] Although Figure 3 The example box for process 300 is shown, but in some implementations, process 300 may include... Figure 3 The additional boxes, fewer boxes, different boxes, or boxes with different arrangements described in the text. Alternatively, two or more boxes of process 300 can be executed in parallel.

[0050] Industrial applicability

[0051] During operation, depending on the engine's usage characteristics (e.g., operating profile, usage pattern, usage type, etc.), the machine can be controlled to use the engine in multiple ways and / or in different ways, which cause wear and / or damage to the engine at different rates. While monitoring certain operating parameters related to the operating range can be used to detect potential faults, this pre-configured range may be inaccurate or become outdated during engine use.

[0052] As described herein, a remote monitoring system 106 is configured to acquire usage data from multiple machines 102 utilizing the same type of engine, determine the operating range of operating parameters based on the engine's operating profile during use, and perform one or more actions associated with predicting engine failures and / or reducing the risk of engine failure. In some implementations, the engine monitoring model may include a machine learning model and / or be associated with a machine learning model configured to identify one or more usage or measurement patterns associated with the engine that indicate a possible failure within a certain time period. The remote monitoring system can determine an optimal operating configuration to reduce the risk of failure and / or prevent failure within a certain time period. The remote monitoring system 106 can provide the optimal operating configuration to the machine 102 (e.g., via a user interface and / or control system) to allow the operator of the machine 102 to adjust the use of the machine 102 to prevent failures and / or enable the control system of the machine 102 to adjust the machine's operating parameters according to the settings of the optimal operating configuration.

[0053] Thus, one or more examples described herein provide improved accuracy in predicting faults and / or controlling the engine to prevent engine failure, thereby saving resources associated with damage to the engine (e.g., hardware resources associated with replacing engine components, reducing machine downtime, etc.).

[0054] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or can be derived from practice of the implementations. Furthermore, any implementations described herein can be combined unless the foregoing disclosure expressly provides for reasons why one or more implementations cannot be combined. Even if specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. While each dependent claim listed below may depend directly on only one claim, the disclosure of various implementations includes every dependent claim in combination with all other claims in the claim set.

[0055] As used in this article, depending on the context, satisfying the threshold can refer to a value that is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, etc., depending on the context.

[0056] As used herein, “a,” “an,” and “set” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items associated with the article “the” and may be used interchangeably with “the one or more.” Further, the phrase “based on” is intended to mean “at least partially based on,” unless otherwise explicitly stated. Moreover, as used herein, the term “or,” when used serially, is intended to be inclusive and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in combination with “any” or “only one”).

Claims

1. A method for predicting engine performance and faults, comprising: Receive historical usage data associated with multiple engines of the engine type, which are associated with multiple corresponding machines; The engine monitoring model is trained based on the historical usage data to identify usage profiles that indicate potential faults of the engine type. The usage profile identifies the operating range of the operating parameters for the engine type based on the operating profile associated with operating one or more of the plurality of engines; Receive usage data from the machine, which includes measurements of the operating parameters of the machine's engine; It is determined that the engine is configured to operate according to the operational overview; Based on the determination that the engine is configured to operate according to the operational profile and based on the measurements and the operational range, it is predicted that the engine may fail within a certain period of time; as well as Performing actions associated with the machine, including: The usage data identifies the engine's usage pattern; A usage score associated with the machine is determined based on the usage pattern and the measurement, wherein the usage score represents the remaining operational duration of the engine; Determine that the usage score meets the maintenance threshold; and Enables the machine to receive maintenance services associated with the engine.

2. The method according to claim 1, wherein the operating parameters include at least one of the following: The speed of the engine components; The temperature of the engine components; Emissions metrics associated with exhaust from the engine; or Intake measurements associated with the intake of the engine.

3. The method of claim 1, wherein the usage data is received from the onboard engine monitoring system during machine operation.

4. The method of claim 1, wherein the operational profile is associated with at least one of the following: Optimize the settings of the engine's performance metrics; or Optimize the settings for the engine's service life.

5. The method according to claim 1, wherein performing the action further comprises: Obtain confirmation information associated with determining that the engine may have failed; as well as The engine monitoring model is retrained based on the confirmation information and the usage data.

6. The method of claim 1, wherein performing the action comprises: Send a notification to the user interface of the machine that the engine may fail.

7. A device for predicting engine performance and faults, comprising: One or more memory units; as well as One or more processors, configured as follows: Receive usage data associated with the engines of the multiple corresponding machines from the airborne engine monitoring systems of the multiple corresponding machines; A subset of engines associated with the plurality of corresponding machines is determined from the usage data and configured to operate according to the operation profile; Measurements of operating parameters associated with the use of the subset of the engine are made for the operating parameters and the operating range is determined from the usage data; Measurements of the operating parameters of the engine of the machine are received from the airborne engine monitoring system associated with the machine of the plurality of respective machines; Based on the measurements and the operating range, it is determined that the engine may fail within a certain time period; as well as Perform actions associated with the machine; The one or more processors wherein the action is performed are configured to: The usage data identifies the engine's usage pattern; A usage score associated with the machine is determined based on the usage pattern and the measurement, wherein the usage score represents the remaining operational duration of the engine; Determine that the usage score meets the maintenance threshold; and Enables the machine to receive maintenance services associated with the engine.

8. The device according to claim 7, wherein the operating parameters include at least one of the following: The speed of the engine components; The temperature of the engine components; Emissions metrics associated with exhaust from the engine; or Intake measurements associated with the intake of the engine.

9. The device according to claim 7, wherein the airborne engine monitoring system is communicatively connected to the device via a wireless communication network.

10. The device of claim 7, wherein the one or more processors are configured to: The measurement was determined to be outside the operating range; Analyze usage data associated with the engine to identify measurement patterns associated with the operating parameters; The probability of engine failure is determined based on the measurement mode. as well as The engine is determined to be likely to fail based on the probability of meeting a threshold failure probability.

11. The device of claim 7, wherein the subset of engines is a first subset of engines, the operating profile is a first operating profile, and the operating range is a first operating range, and The second engine subset is associated with the second operating profile, and the second operating range of the operating parameters is determined based on the use of the second engine subset.

12. The device of claim 7, wherein the one or more processors are further configured to perform the action: The usage data identifies the engine's usage pattern; The optimal operating configuration of the engine is determined based on the usage pattern and the measurements; and Engine control commands are transmitted to the engine controller of the machine so that the engine controller controls the engine according to the optimal operating configuration.

13. A non-transitory computer-readable medium storing an instruction set, the instruction set comprising: One or more instructions, when executed by one or more processors of the device, cause the device to: Receive notification from the machine's onboard engine monitoring system that the measurement of the machine's engine operating parameters is outside the machine's operating range; The notification determines that the engine is configured to operate according to an operational profile associated with the operational scope; The historical usage data associated with the engine is identified based on historical usage data that is mapped in a data structure to identifiers associated with the engine; The measurement patterns associated with the operating parameters are determined from the historical usage data; The optimal operating configuration is determined based on the measurements, the measurement patterns, and other historical usage data associated with multiple other machines. as well as Perform actions associated with the machine and the optimal operating configuration, including: The usage data identifies the engine's usage pattern; A usage score associated with the machine is determined based on the usage pattern and the measurement, wherein the usage score represents the remaining operational duration of the engine; Determine that the usage score meets the maintenance threshold; and Enables the machine to receive maintenance services associated with the engine.

14. The non-transitory computer-readable medium of claim 13, wherein the operating parameters include at least one of the following: The speed of the engine components; The temperature of the engine components; Emissions metrics associated with exhaust from the engine; or Intake measurements associated with the intake of the engine.

15. The non-transitory computer-readable medium of claim 13, wherein the optimal operating configuration identifies the setting of one or more other operating parameters of the engine, which, in association with the operating parameters, reduces the probability of engine failure.

16. The non-transitory computer-readable medium of claim 13, wherein the operational profile is associated with at least one of the following: Optimize the settings of the engine's performance metrics; or Optimize the settings for the engine's service life.

17. The non-transitory computer-readable medium of claim 13, wherein the one or more instructions causing the device to perform the action cause the device to: Engine control commands are transmitted to the engine controller of the machine so that the engine controller controls the engine according to the optimal operating configuration.

18. The non-transitory computer-readable medium of claim 13, wherein the one or more instructions causing the device to perform the action cause the device to: A message instructing the optimal operating configuration is transmitted to the user interface of the machine.