Flexible Engine Monitoring

Abstract

The systems, methods, computer-readable media, vehicles, and engines provided herein include or implement flexible engine monitoring features. In one aspect, a user-modifiable file containing selected parameters is uploaded to a vehicle having a propulsion system (e.g., an engine). Without modifying the reporting software or any other software, a computing device associated with the engine generates a list of parameter reports including the selected parameters. During operation, the parameter values of the selected parameters are recorded. In another aspect, a data query is transmitted to an aircraft while in flight. The data query includes a user-modifiable file that contains the selected parameters for which parameter values are to be recorded. Without modifying the reporting software or any other software, a computing device associated with the engine generates a list of parameter reports including the selected parameters. The recorded parameter values of the selected parameters are transmitted in flight to a remote station. In yet another aspect, a vehicle receives a data communication including a user-modifiable file that contains data indicating a target condition and one or more selected parameters for which parameter values are to be recorded when the target condition is met. Without modifying the reporting software or any other software, a computing device associated with the engine of the vehicle generates a list of parameter reports including the selected parameters. When the condition is met, the parameter values of the selected parameters are recorded.

Description

Technical Field

[0001] The subject matter of the present disclosure generally relates to monitoring and communicating engine data, and more particularly, to monitoring and communicating engine data of an aircraft engine. Background Art

[0002] An aircraft may include one or more engines for propulsion. Each engine may have one or more associated electronic engine controllers (EECs). The EEC may serve as a control unit of a full-authority digital engine control (FADEC) system. In particular, the EEC may control its corresponding engine during operation and may record continuous engine operation data (CEOD) related to the associated engine and aircraft. The recorded CEOD file may contain a detailed record of the engine conditions during operation. Specifically, the CEOD file may contain recorded values or settings of various parameters (such as fuel flow rate, ambient temperature, and pressures and temperatures at various stations of the engine).

[0003] Traditionally, there have been more than 10,000 parameters in a FADEC system. However, due to cost reasons among other reasons, typically only 300 - 400 parameters are included in the CEOD file. In some cases, it may be desirable to record additional parameters in addition to the 300 - 400 baseline parameters. For example, a field event may occur where the engine performs in an unexpected manner. In such a case, in order to further investigate the cause of the unexpected behavior, it may be desirable to record parameters in addition to the baseline parameters so that the root cause of the unexpected behavior can be attempted to be determined. Additionally, it may also be desirable to change the time or frequency of capturing existing baseline parameters or subsets thereof. For example, it may be desirable to change the data capture rate of some or all of the baseline parameters when a predetermined condition is met. In the past, FADEC parameters have been fixed in the software code of the FADEC system. Therefore, updating the CEOD parameter list has proven to be challenging, costly, and time-consuming, for example due to the lengthy certification process of the software code. In fact, even the most streamlined software release process for implementing minor changes to FADEC parameters typically takes more than a month to complete.

[0004] Accordingly, improved methods, systems, and engines that address one or more of the above challenges would be useful. Summary of the Invention

[0005] Aspects and advantages of embodiments of the present disclosure will be set forth in part in the following description, or may be learned from the description, or may be learned by practicing the embodiments.

[0006] In one aspect, a vehicle is provided. The vehicle includes a propulsion system, one or more sensors, and a computing system having one or more memory devices and one or more processors. The one or more processors are configured to receive a user-modifiable file that includes data indicating one or more selected parameters to be recorded. The one or more processors are further configured to generate a parameter report list including the one or more selected parameters by executing reporting software on at least one of the one or more processors without modifying the reporting software. Additionally, the one or more processors are configured to receive sensor data from the one or more sensors. Further, the one or more processors are configured to record parameter values of the one or more selected parameters in the generated parameter report list at least in part based on the received sensor data.

[0007] In another aspect, an aircraft is provided. The aircraft includes an engine, one or more sensors, and a computing system having one or more memory devices and one or more processors communicatively coupled to the one or more memory devices. The one or more processors are configured to: receive a data query transmitted to the aircraft while the aircraft is performing a mission, the data query including a user-modifiable file that includes data indicating one or more selected parameters for which parameter values are to be recorded during the mission; generate a parameter report list including the one or more selected parameters by executing reporting software without modifying the reporting software; receive sensor data from the one or more sensors; and while the aircraft is performing the mission, record parameter values of the one or more selected parameters in the generated parameter report list at least in part based on the received data.

[0008] In yet another aspect, a vehicle is provided. The vehicle includes a propulsion system, one or more sensors, and a computing system having one or more memory devices and one or more processors communicatively coupled to the one or more memory devices. The one or more processors are configured to: receive a data communication including a user-modifiable file that includes data indicating target conditions and one or more selected parameters for which parameter values are to be recorded when the target conditions are met; generate a parameter report list including the one or more selected parameters by executing reporting software on at least one of the one or more processors without modifying the reporting software; receive sensor data from the one or more sensors; determine whether the target conditions are met at least in part based on the received sensor data; and when it is determined that the target conditions are met, record parameter values of the one or more selected parameters in the generated parameter report list at least in part based on the received sensor data.

[0009] Other example aspects of the present disclosure relate to systems, methods, aircraft, engines, controllers, devices, and non-transitory computer-readable media for recording and communicating engine data. Variations and modifications can be made to these example aspects of the present disclosure.

[0010] These and other features, aspects, and advantages of the various embodiments will be better understood with reference to the following description and the appended claims. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the related principles. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A detailed discussion of embodiments for those of ordinary skill in the art is set forth in the specification with reference to the accompanying drawings, in which:

[0012] Figure 1 A schematic diagram of a data acquisition system according to an example embodiment of the present disclosure is provided;

[0013] Figure 2 There is provided Figure 1 a schematic cross-sectional view of a gas turbine engine of an aircraft of the data acquisition system;

[0014] Figure 3 There is provided Figure 1 a schematic diagram of a communication unit of an aircraft of;

[0015] Figure 4 A flowchart of an example method for monitoring an engine according to an example embodiment of the present disclosure is provided;

[0016] Figure 5 There is provided a system configured to implement the Figure 4 method;

[0017] Figure 6 There is provided a schematic block diagram depicting a user-modifiable file stored in one or more memory devices of a computing system of an aircraft of Figure 1 ;

[0018] Figure 7 There is provided a Figure 1 computing device of an aircraft that generates a list of parameter reports;

[0019] Figure 8 There is provided a schematic diagram of a computing device of a vehicle propulsion system that generates a list of parameter reports, in which one or more parameter settings are changed;

[0020] Figure 9 There is provided a schematic diagram of a computing device of a vehicle propulsion system that generates a list of parameter reports;

[0021] Figure 10A flowchart of an example method of querying a FADEC system, recording parameter values associated with selected parameters included in the query, and transmitting the recorded data in accordance with example embodiments of the present disclosure is provided;

[0022] Figure 11 A system configured to implement Figure 10 the method is provided;

[0023] Figure 12 A schematic block diagram of a user-modifiable file depicting a data query stored in one or more memory devices of an aircraft's computing system is provided;

[0024] Figure 13 A schematic diagram of a computing device associated with an aircraft's engine that generates a parameter report list is provided;

[0025] Figure 14 A schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list, in which one or more parameter settings are changed, is provided;

[0026] Figure 15 A schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list is provided;

[0027] Figure 16 A flowchart of an example method of monitoring selected parameters when one or more target conditions are met in accordance with example embodiments of the present disclosure is provided;

[0028] Figure 17 A system configured to implement Figure 16 the method is provided;

[0029] Figure 18 A schematic block diagram of a user-modifiable file depicting data communication stored in one or more memory devices of an aircraft's computing system is provided;

[0030] Figure 19 A schematic diagram of a computing device associated with an aircraft's engine that generates a parameter report list is provided;

[0031] Figure 20 A schematic diagram of a computing device associated with an aircraft engine that depicts receiving multiple data communications in accordance with example embodiments of the present disclosure, each data communication having a target condition and an associated selected parameter, and recording the parameter value of the selected parameter when the target condition is met is provided;

[0032] Figure 21 A schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list, in which one or more parameter settings are changed, is provided;

[0033] Figure 22 Schematic diagram of a computing device of a vehicle propulsion system for generating a list of parameter reports;

[0034] Figure 23 Schematic diagram of a computing system for implementing one or more aspects of the present disclosure according to an exemplary embodiment of the present disclosure; and

[0035] Figure 24 An exemplary vehicle according to an exemplary embodiment of the present disclosure is provided. Detailed Description

[0036] Reference will now be made in detail to the embodiments, one or more examples of which are illustrated in the accompanying drawings. Each example is provided for the purpose of explaining the embodiments and not limiting the embodiments. In fact, it will be apparent to those skilled in the art that various modifications and variations can be made to the present disclosure without departing from the scope of the subject matter. For example, features shown or described as part of one embodiment can be used with another embodiment to yield yet another embodiment. Accordingly, the present disclosure is intended to cover such modifications and variations that fall within the scope of the appended claims and their equivalents.

[0037] As used in the specification and the appended claims, unless the context clearly dictates otherwise, the singular forms "a", "an" and "the" include plural forms. The term "about" when used in conjunction with a numerical value means within 25% of the stated amount.

[0038] Exemplary aspects of the present disclosure relate to systems, methods, vehicles, engines, controllers, computing devices, non-transitory computer-readable media for flexibly monitoring an engine (e.g., an aircraft gas turbine engine). Such a flexible engine monitoring system, method, vehicle, engine, controller, computing device, and non-transitory computer-readable media provide a flexible way to select parameters, record parameter values of the selected parameters, and communicate the recorded parameter values (e.g., communicate to a remote station). Compared to conventional techniques in the art, the flexible engine monitoring aspects described herein provide improvements in selecting parameters, recording parameter values of the selected parameters, and communicating the recorded parameter values.

[0039] On the one hand, multiple selected parameters can be added to a parameter report list stored in a computing device associated with the engine of a vehicle, so that the parameter values of the selected parameters can be recorded during engine operation. The user modifiable file can be uploaded to the aircraft, and the selected parameters are added to the parameter report list. The user modifiable file can be modified by a suitable entity (such as but not limited to the vehicle or aircraft operator, leasing entity, airframe manufacturer, or propulsion system or engine manufacturer). In some embodiments, a parameter report list is created using the selected parameters. The values of the selected parameters can be recorded during the next engine power cycle, the next power-on of the computing device, or immediately after the user modifiable file is uploaded. In addition to other parameter settings associated with the selected parameters, the data sampling rate of the selected parameters can also be customized. This can be done for one engine or an entire fleet. It is worth noting that when adding the selected parameters to the parameter report list, the reporting software and any other engine software are not modified. Thus, although new parameters are added to the parameter report list, no lengthy certification process is required.

[0040] On the other hand, an entity (such as an airline operator or an engine monitoring center) can transmit an in-flight parameter data query to the aircraft. The data query can include a user modifiable file that includes a list of one or more defined or selected parameters for which parameter values will be recorded by a computing device associated with the engine during engine operation (such as during the same flight in which the data query is received at the aircraft). The user modifiable file can also include various parameter settings associated with the selected parameters, such as the time period or recording window of interest (during which the parameter values of the selected parameters will be recorded), and the data sampling rate or frequency at which the parameter values will be recorded. The user modifiable file can be modified by a suitable entity (such as but not limited to the vehicle or aircraft operator, leasing entity, airframe manufacturer, or propulsion system or engine manufacturer). The reporting software that can be executed by a computing device associated with the engine (such as an engine controller) can access the user modifiable file and can generate a parameter report list using the selected parameters and their associated parameter settings. The parameter report list can also include baseline parameters, which are parameters for which values are typically recorded during normal engine operation. Some baseline and / or selected parameters (such as altitude, GPS coordinates) may help the user to adapt to flight and environmental conditions.

[0041] It should be noted that when adding the selected parameters to the parameter report list, neither the reporting software nor any other engine software is modified. In this way, among other benefits, a lengthy certification process is not required despite the addition of new parameters to the parameter report list. The parameter values of the parameters in the generated parameter report list can be recorded within their respective recording windows and recorded at their specified data sampling rates. The recorded values can be compiled into a query response file. The query response file can be transmitted to a remote station for analysis. For example, the remote station can be an engine monitoring station. The remote station can analyze the recorded parameter values associated with the selected parameters and can send additional data queries to the aircraft to further monitor the engine and / or request monitoring of other parameters. Thus, in-flight parameter data queries for an aircraft or other vehicle allow for real-time or near-real-time parameter queries.

[0042] In some embodiments, a computing device associated with the engine is configured to record the parameter values of all possible parameters or at least more parameters than baseline parameters. In such an embodiment, an entity can transmit an in-flight parameter data query to the aircraft. The data query can include a user-modifiable file that includes a list of one or more selected parameters, and the parameter values to be recorded for the selected parameters are compiled into a query response file at least partially based on a preselected past time window. The past time window can indicate the time period during which the recorded parameter values of the selected parameters will be compiled into the query response file. The past time window is a time period that has already occurred. Thus, the parameter data query transmitted to the vehicle can be a "look-back" request. This can allow an entity that has discovered unexpected engine behavior to "look back" at the parameter values of the selected parameters recorded during the past time window, which can be selected as the time period corresponding to the unexpected engine behavior, to better understand the engine conditions during the unexpected behavior.

[0043] Reporting software executable by a computing device associated with an engine, such as an engine controller, can access user-modifiable files and can generate a parameter report list using selected parameters. The parameter report list can also include baseline parameters, which are parameters for which values are typically recorded during normal engine operation. Notably, the reporting software and any other engine software are not modified when adding the selected parameters to the parameter report list. In this way, among other benefits, a lengthy certification process is not required despite adding new parameters to the parameter report list. Parameter values of the parameters in the generated parameter report list recorded during a past time period can be compiled into a query response file. The query response file can be transmitted to a remote station for analysis. For example, the remote station can be an engine monitoring station. The remote station can analyze the recorded parameter values associated with the selected parameters and can send additional data queries to the aircraft to further monitor the engine and / or request compilation of other parameter values recorded during other past time periods.

[0044] In a further aspect, a computing device associated with an engine can self-select parameter values to be recorded during engine operation based on one or more target conditions. That is, when a specific target condition is met, parameter values associated with self-selected parameters can be recorded. A data communication containing the user-modifiable file can be transmitted to the vehicle. The user-modifiable file includes the target conditions and the selected parameters for which parameter values will be recorded by the computing device associated with the engine when the target conditions are met (i.e., when the target conditions are true). The target conditions can be defined as any target condition or set of target conditions. For example, among other possible target conditions, the target condition can be triggered or met when the aircraft is flying in a specific geographical area, when the aircraft experiences an abnormally high FADEC temperature, and / or when the aircraft has marginal performing sensors or actuators. The user-modifiable file can also include various parameter settings associated with the selected parameters, such as the data sampling rate at which the parameter values of the selected parameters will be recorded when the target conditions are met. The user-modifiable file can be modified by a suitable entity, such as but not limited to the vehicle or aircraft operator, a leasing entity, an airframe manufacturer, or a propulsion system or engine manufacturer. Reporting software executable by a computing device associated with the engine can access the user-modifiable file and can generate a parameter report list using the selected parameters and their associated parameter settings. The parameter report list can also include baseline parameters, which are parameters for which values are typically recorded during normal engine operation. Notably, the reporting software and any other engine software are not modified when generating the parameter report list. In this way, among other benefits, a lengthy certification process is not required.

[0045] During operation, a computing device associated with an engine can monitor the operation and environmental conditions of the engine and / or a vehicle on which the engine is installed based on received data (e.g., engine sensor data, vehicle data, environmental data, etc.). The computing device associated with the engine can determine whether a target condition is met based on the received data. When the target condition is met, the parameter values of the parameters in the generated list of parameter reports can be recorded at their specified data sampling rate. The recorded values can be compiled into a recorded data file. The recorded data file can be transmitted to a remote station for analysis. For example, the remote station can be an engine monitoring station. The remote station can analyze the recorded parameter values associated with the selected parameters and can send further data communications to the aircraft to further monitor the engine and / or request monitoring of other parameters when a specific target condition is met. The data communications can be pushed to multiple engines in a fleet. By allowing the computing device associated with the engine to self-select which parameter values to record based on set target conditions, the parameter values can be recorded intelligently and efficiently only by those engines in the fleet that meet the target conditions. Among other benefits, this provides a significantly faster way to record specific parameters when a fleet of engines meets a target condition and also avoids the cost of satellite data or other expensive additional data that would be generated if the engines did not experience the identified target condition.

[0046] Figure 1 A schematic diagram of an example data acquisition system 100 in accordance with an example embodiment of the present disclosure is provided. As shown, system 100 includes a vehicle, which in this embodiment is an aircraft or a flying vehicle 110. Although the flying vehicle 110 is depicted as a fixed-wing aircraft, in other example embodiments, the flying vehicle 110 can be a rotary-wing aircraft, a smaller fixed-wing aircraft, an air-land hybrid vehicle, an unmanned aerial vehicle, or some other type of flying vehicle. Additionally, the subject matter of the present disclosure can be applied to other types of vehicles, including but not limited to land-based vehicles, amphibious vehicles, boats or ships, spacecraft, some combination thereof, etc.

[0047] As Figure 1As shown, the aircraft 110 includes: a fuselage 112; a propulsion system including one or more engines 114; and a cockpit 116. The cockpit 116 may include a flight panel having various instruments and flight displays. The engines 114 provide propulsion and / or on-board power generation for the aircraft 110. The engines 114 may be gas turbine engines. Example gas turbine engines include jet turbine engines, turboprop engines, turbofan engines, unducted fan engines, turboshaft engines, or any other suitable engine, including piston or reciprocating engines. Additionally, the subject matter of the present disclosure may be applicable to other types of engines, including but not limited to rocket engines, reciprocating engines, regenerative heat engines, etc. Further, the subject matter of the present disclosure may be applied to other types of vehicle propulsion systems, such as an electric propulsion system including one or more electric motors and one or more thrusters (e.g., propellers) for generating thrust, and a hybrid electric propulsion system utilizing one or more engines, one or more electric motors, and in some embodiments one or more thrusters for generating thrust.

[0048] The aircraft 110 includes a computing system 115 having one or more memory devices and one or more processors. The one or more memory devices and the one or more processors may be embodied in one or more computing devices 118 associated with the propulsion system. For example, as Figure 1 shown, the aircraft 110 includes at least one computing device 118 associated with each engine 114. In some embodiments, multiple computing devices may be associated with each engine 114. In other embodiments, a single computing device may be associated with the engine 114. The one or more computing devices 118 may include reporting logic embodied in reporting software. In this manner, as will be described herein, the one or more computing devices 118 may receive sensor data and record parameter values of selected parameters based on the received sensor data.

[0049] One or more of the computing devices 118 can be part of a Full Authority Digital Engine Control (FADEC) system. The FADEC system can dynamically control the operation of the engine 114 and requires minimal (if any) supervision from the pilot. The computing device 118 can include FADEC control logic as well as the FADEC reporting logic described above. In some embodiments, the computing device 118 can include an Electronic Engine Controller (EEC) mounted to their respective engines 118. Additionally, in some embodiments, one or more computing devices 118 associated with the engine 114 can include a non-EEC control box, such as an Engine Monitoring Unit (EMU) or an aircraft-mounted box. In other embodiments, the computing device 118 associated with the engine 114 or the vehicle propulsion system can include a distributed control system having a central controller and a plurality of distributed controllers communicatively coupled to the central controller.

[0050] The aircraft 110 includes an avionics bay 120 that houses one or more avionics systems. Examples of avionics systems include communication systems, navigation systems, weather systems, radar systems, air traffic systems, terrain warning systems, and the like. In some embodiments, the avionics system can include a positioning system or communicate with a positioning system. The positioning system can include a Global Positioning System (GPS), an inertial reference system, and the like. For this embodiment, the vehicle interface unit 122 of the aircraft 110 is positioned within the avionics bay 120. The vehicle interface unit 122, which is an engine interface unit in this embodiment, interfaces the computing device 118 with various vehicle systems 160 or aircraft systems in this embodiment. Example vehicle systems 160 include, but are not limited to, a flight management system, a display system, a flight control system, a digital control system, a throttle system, an inertial reference system, a flight instrument system, an auxiliary power system, a fuel monitoring system, an engine vibration monitoring system, a communication system, a flap control system, a landing system, a navigation system, a fuel control system, and other systems. Each avionics system can include one or more computing devices.

[0051] The computing device 118 and the vehicle interface unit 122 are communicatively coupled or connected via a data communication link 124. The data communication link 124 can be any suitable type of data link, including but not limited to a serial data bus, an Ethernet link, a wireless communication link, etc. Various parameters recorded by the computing device 118 can be transmitted from the computing device 118 to the vehicle interface unit 122 via the data communication link 124, for example, so that such information can be utilized by the vehicle system 160 of the aircraft 110. For example, the parameters can include fan speed, core speed, thrust level input, engine response to thrust level input, vibration, flameout, fuel consumption, ignition status, anti-icing capability, fuel filter status, fuel valve status, oil filter status, and other parameters.

[0052] The aircraft 110 can include one or more communication units for communicating with remote stations external to the aircraft 110 (e.g., other vehicles, entities, devices, naval stations, another air station, space station, etc.). For this embodiment, the aircraft 110 includes a communication unit 125 mounted to or within the fuselage 112. In some embodiments, the communication unit 125 can be mounted within the avionics bay 120. For example, the communication unit 125 can be directly communicatively coupled to the vehicle interface unit 122 as Figure 1 shown. Generally, the communication unit 125 can communicate data to the remote station using one or more wired and / or wireless communication links. As an example, the communication unit 125 can provide an Aircraft Communication Addressing and Reporting System (ACARS) for the aircraft 110 for transmitting and receiving ACARS transmissions. As another example, one or more computing devices 118 can record data related to one or more engines 114 (or more generally, the propulsion system) and / or the aircraft 110, and can communicate (e.g., transmit, send, push, etc.) the data to the communication unit 125 via the data communication link 124. The communication unit 125 can then communicate the data to the remote station via, for example, the antenna of the communication unit 125. The communication unit 125 can include one or more computing devices, each having one or more processing devices and one or more memory devices communicatively coupled to its transmission device.

[0053] In some embodiments, additionally or alternatively, one or more communication units can be mounted to the engine 114. As Figure 1As shown, a wireless communication unit (WCU) 126 can be mounted to each engine 114. The WCU 126 can be communicatively coupled to their respective or associated computing devices 118, for example, via a suitable wired or wireless connection. One or more computing devices 118 can record data related to one or more engines 114 (or more generally, the propulsion system) and / or the aircraft 110, and can communicate (e.g., transmit, send, push, etc.) the data to one or more WCUs 126. One or more WCUs 126 can communicate the data to a remote station via, for example, an antenna positioned and configured within a nacelle 50 ( Figure 2 ) that encloses at least a portion of the engine 114. One or more WCUs 126 can be located within the nacelle 50 ( Figure 2 ) or at another location on the aircraft 100. Additionally, antennas for transmitting and receiving communications can be positioned at other locations. For example, an antenna can be mounted to the fuselage 112 of the aircraft 110. The WCU 126 can include one or more computing devices, each having one or more processing devices and one or more memory devices communicatively coupled to its transmission device.

[0054] Generally, during operation, the computing device 118 can record sensed, calculated, and / or predicted values of various parameters associated with the engine 114 (or more generally, the propulsion system) and / or the aircraft 110. That is, the computing device 118 can record data associated with the propulsion system and / or the aircraft 110 on which the engine 114 is installed. In embodiments where the propulsion system of the aircraft 110 is a hybrid electric or electric propulsion system, parameter values associated with the electric motor and / or other electrical devices and components can also be recorded. For example, one or more parameter values associated with an electric motor operably coupled to the engine can be recorded, such as voltage, current, etc., associated with the electric motor. Additionally, parameter values associated with the propulsion system of the aircraft 110 can be captured not only during engine operation but also before engine startup and / or after engine shutdown. This allows data to be captured in relation to engine startup and engine shutdown, respectively. The recorded data can be routed to the communication 125 and / or the WCU 126 mounted to the engine 114. For example, the recorded data can be routed via a data communication link 124.

[0055] As described above, the communication units 125, 126 can communicate (e.g., transmit, send, push, etc.) data to a remote station. For this embodiment, the remote station is a ground station 150. However, in other embodiments, the remote station can be any suitable station located away from the aircraft 110. The communication units 125, 126 can communicate data automatically or upon a manual request. The communication units 125, 126 can communicate data wirelessly and / or via a suitable wired connection.

[0056] Any suitable wireless technology and / or protocol can be used for wireless communication of data. For example, communication units 125, 126 can perform wireless communication using peer-to-peer communication, network communication, UHF, VHF, cellular-based communication, satellite-based communication, etc. For example, as Figure 1 shown, communication units 125, 126 can communicate with ground station 150 via satellite communication (SATCOM) using one or more satellites 152 through VHF technology and / or UHF technology. As a further example, Wi-Fi, cellular, etc. can be used to send / receive wireless communication, especially when the aircraft 110 is on the ground or close to the ground. Any or all such networks can be used to transfer data from the aircraft 110 to the ground station 150 and vice versa. In some cases, communication unit 125 and / or WCU 126 can communicate with a remote station using a wired communication link as described above. For example, the wired communication link can be coupled to one or more of communication units 125, 126 or directly coupled to one or more of computing devices 118. In other embodiments, data recorded during flight can be stored on one or more removable memory devices of communication units 125, 126 and / or ECC 118. To access the recorded data, the memory device can be removed from the aircraft 110 after flight and downloaded or otherwise accessed by a remote computing device.

[0057] Ground station 150 can include one or more transceivers. For example, one or more ground transceivers can include satellite antenna 154C, cellular tower 154B, and / or wireless access point (WAP) 154A, as Figure 1 shown. Ground station 150 can also include one or more remote computing devices 156 communicatively coupled to one or more transceivers 154A, 154B, and / or 154C. Ground transceivers 154A, 154B, and / or 154C are operable to receive data transmitted by aircraft 110 via wireless communication. The data communication can be routed to ground computing device 156. Ground computing device 156 is operable to receive the data communication. Ground computing device 156 can then perform various operations, such as data analysis, scheduled maintenance and / or repair of engines and / or aircraft components, etc. As Figure 1 further shown, ground station 150 can include a wired access point 158. The wired access point 158 provides one or more wired communication links to which communication units (e.g., communication units 125 and / or WCU 126) of the aircraft 110 can be connected so that data can be transferred between communication units 125, 126 of the aircraft 110 and ground computing device 156. For example, the wired access point 158 can be used to provide a wired download of post-flight recorded data.

[0058] Figure 2Provided is a schematic cross-sectional view of one of the engines 114 of an aircraft 110 in accordance with an exemplary embodiment of the present disclosure. For Figure 1 the illustrated embodiment, the engine 114 is configured as a gas turbine engine, or specifically a high bypass turbofan jet engine 114, referred to herein as the "turbofan engine 114". The turbofan engine 114 defines an axial direction A (extending parallel to the provided axial or longitudinal centerline 13 for reference), a radial direction R, and a circumferential direction (not shown) extending around or about the longitudinal centerline 13. Figure 2 The turbofan engine 114 includes a fan section 14 and a core turbofan engine 16 disposed downstream of the fan section 14. The depicted core turbofan engine 16 includes a substantially tubular outer casing 18 that defines an annular inlet 20. The outer casing 18 surrounds in a serial flow relationship, and the core turbofan engine 16 includes, in serial flow relationship: a compressor section that includes a booster or low pressure (LP) compressor 22 and a high pressure (HP) compressor 24; a combustion section 26; a turbine section that includes a high pressure (HP) turbine 28 and a low pressure (LP) turbine 30; and an exhaust nozzle section 32. A high pressure (HP) shaft or spool 34 drivingly connects the HP turbine 28 to the HP compressor 24. A low pressure (LP) shaft or spool 36 drivingly connects the LP turbine 30 to the LP compressor 22. Thus, during operation of the turbofan engine 114, both the LP shaft 36 and the HP shaft 34 are rotating components that rotate about the axial direction A.

[0059] Still referring to

[0060] the embodiment of Figure 2 the fan section 14 includes a fan 38 having a plurality of fan blades 40 that are coupled to a disk 42 in a spaced-apart manner. As shown, the fan blades 40 generally extend radially outward from the disk 42. Each fan blade 40 is rotatable relative to the disk 42 about a pitch axis P by operably coupling the fan blade 40 to a suitable pitch mechanism 44, which is configured to collectively and uniformly change the pitch of the fan blades 40. The fan blades 40, the disk 42, and the pitch mechanism 44 are rotatable together about the longitudinal axis 13 via the LP shaft 36 across a power gearbox 46. The power gearbox 46 includes a plurality of gears for adjusting the rotational speed of the fan 38 relative to the LP shaft 36 to a more efficient rotational fan speed. More specifically, the fan section includes a fan shaft that is rotatable via the LP shaft 36 across the power gearbox 46. Thus, the fan shaft can also be considered a rotating component and is similarly supported by one or more bearings.

[0061] Still referring to Figure 2In an exemplary embodiment, the disk 42 is covered by a rotatable front hub 48 that is aerodynamically shaped to facilitate the flow of air through the plurality of fan blades 40. Additionally, the exemplary fan section 14 includes an annular fan casing or nacelle 50 that circumferentially surrounds at least a portion of the fan 38 and / or the core turbine engine 16. The exemplary nacelle 50 is supported relative to the core turbine engine 16 by a plurality of circumferentially spaced outlet guide vanes 52. Further, a downstream section 54 of the nacelle 50 extends over an outer portion of the core turbine engine 16 to define a bypass air flow path 56 therebetween. The computing device 118 and the communicatively coupled WCU 126 are shown mounted to the nacelle 50.

[0062] During operation of the turbofan engine 114, a quantity of air 58 enters the turbofan engine through the nacelle 50 and / or the associated inlet 60 of the fan section 14. As the quantity of air 58 passes through the fan blades 40, a first portion of the air 58, as indicated by arrow 62, is directed or guided into the bypass air flow path 56, and a second portion of the air 58, as indicated by arrow 64, is directed or guided into the core air flow path, or more specifically, into the LP compressor 22. The ratio between the first portion of air 62 and the second portion of air 64 is commonly referred to as the bypass ratio. As the second portion of air 64 is directed through the high-pressure (HP) compressor 24 and into the combustion section 26, the pressure of the second portion of air 64 is then increased, where in the combustion section 26, the second portion of air 64 is mixed with fuel and burned to provide combustion gases 66.

[0063] The combustion gases 66 are directed through the HP turbine 28, where a portion of the thermal energy and / or kinetic energy from the combustion gases 66 is extracted via successive stages of HP turbine stator vanes 68 coupled to the outer casing 18 and HP turbine rotor blades 70 coupled to the HP shaft or spool 34, thus causing the HP shaft or spool 34 to rotate and thereby support the operation of the HP compressor 24. The combustion gases 66 are then directed through the LP turbine 30, where a second portion of the thermal energy and kinetic energy is extracted from the combustion gases 66 via successive stages of LP turbine stator vanes 72 coupled to the outer casing 18 and LP turbine rotor blades 74 coupled to the LP shaft or spool 36, thus causing the LP shaft or spool 36 to rotate and thereby support the operation of the LP compressor 22 and / or the rotation of the fan 38.

[0064] The combustion gas 66 is then directed through the jet exhaust nozzle section 32 of the core turbine engine 16 to provide propulsion thrust. At the same time, as the first portion of air 62 is directed through the bypass air flow path 56 before being exhausted from the fan nozzle exhaust section 76 of the turbofan engine, the pressure of the first portion of air 62 increases significantly, also providing propulsion thrust. The HP turbine 28, the LP turbine 30, and the jet exhaust nozzle section 32 at least partially define a hot gas path 78 for guiding the combustion gas 66 through the core turbine engine 16.

[0065] However, it should be understood that Figure 2 the exemplary turbofan engine 114 depicted in is provided only as an example, and in other exemplary embodiments, the turbofan engine 114 may have any other suitable configuration. It should also be understood that in other exemplary embodiments, aspects of the present disclosure may be incorporated into any other suitable gas turbine engine or other propulsion engine. For example, in other exemplary embodiments, aspects of the present disclosure may be incorporated into, for example, a turboprop engine, a turboshaft engine, an unducted fan engine, or a turbojet engine. Additionally, in other embodiments, aspects of the present disclosure may be incorporated into any other suitable turbine, including but not limited to a steam turbine, a turboshaft, a centrifugal compressor, and / or a turbocharger.

[0066] Figure 3 There is provided a schematic diagram of one of the communication units 125, 126 of an Figure 1 aircraft 110 or an Figure 2 engine 114 according to an example embodiment of the present disclosure. As shown, the communication units 125, 126 may communicate with one or more computing devices 118 through a suitable interface 128. In some embodiments, the interface 128 may be, for example, a Telecommunications Industry Association (TIA) TIA - 485 interface 128 or an ARINC 664 interface.

[0067] In some embodiments, communication units 125, 126 and computing device 118 may communicate via connection 130 with, for example, interface 128. Connection 130 may accommodate other interfaces, such as an Ethernet connection, a wireless connection, or other interfaces. Connection 130 may be a wired connection, such as an Ethernet connection. Connection 130 may be a wireless connection, such as a Bluetooth connection. Communication units 125, 126 may transmit addressing (e.g., memory location, bit size, etc.) information and / or acknowledgments 132 to computing device 118 via connection 130. Communication units 125, 126 may receive data 134 from computing device 118 via connection 130 and may store the data in one or more memory devices or memory locations. Data 134 may include recorded values or settings of various parameters (e.g., thrust level input, engine response to thrust level input, vibration, flameout, fuel consumption, ignition status, N1 rotation, N2 rotation, N3 rotation, rotor speed, anti-icing capability, temperature, pressure, vibration, actuator position, fuel filter status, fuel valve status, oil filter status, etc.).

[0068] Communication units 125, 126 may be configured to communicate data 135 via antenna 136 over a wireless network at a predetermined time or when one or more trigger conditions (e.g., a trigger condition based on a signal indicating that the aircraft is on or near the ground) occur, and the data 135 may include all or some portion of data 134. In some embodiments, data 135 is an encrypted version of data 134 or a subset thereof. Additionally, in some embodiments, antenna 136 may be integrated into communication units 125, 126. Communication units 125, 126 may include a radio frequency (RF) interface 138. Antenna 136 may communicate with RF interface 138 via RF cable 140. In some embodiments, antenna 136 may be placed in the cabin of the aircraft. The cabin of the aircraft may be made of conductive material, which may impede reception and transmission. In some embodiments, antenna 136 may be a directional antenna that is directed near one or more gaps in the cabin to allow antenna 136 to communicate directionally outside the cabin when the aircraft lands or when other trigger conditions occur.

[0069] In some embodiments, communication units 125, 126 may include an interface for communicating with portable device 142. Portable device 142 may be implemented, for example, on a laptop computer, a tablet computer, a mobile device, or other suitable computing device. The interface may be, for example, a general stream encapsulation (GSE) interface 144 or other suitable interface. Maintenance personnel may use portable device 142 to calibrate, troubleshoot, initialize, test, etc., communication units 125, 126.

[0070] Communication units 125, 126 may communicate using wireless communication. Any suitable wireless technology and / or protocol may be used to perform the wireless communication. For example, peer-to-peer communication, network communication, cellular-based communication, satellite-based communication, etc. may be used to perform the wireless communication. As another example, Wi-Fi, Bluetooth, ZigBee, etc. may be used to perform the wireless communication. Communication units 125, 126 may also be configured to communicate using wired communication and / or to transfer or exchange recorded data using a removable memory device.

[0071] Update the parameter list with the selected parameters

[0072] Now generally referring to Figure 1 , 4 , 5, 6, and 7, example ways will now be provided in which additional or different parameters may be specified for recording. In particular, example ways will be provided in which selected non-baseline parameters may be specified for recording (i.e., added to the parameter report list). As described above, in some cases, it may also be desirable to record the values and / or settings of FADEC parameters in addition to the values and / or settings associated with the baseline parameters. By adding non-baseline parameters to the parameter report list, the values and / or settings associated with the non-baseline parameters may be recorded. Figure 4 A flowchart of an example method (300) for monitoring and communicating engine data of an engine is provided. For example, the engine may be one or more of the engines 114 of the aircraft 110 Figure 1 . It should be understood that the exemplary method (300) may be modified, adapted, extended, rearranged, and / or omitted in various ways without departing from the scope of the present subject matter. Figure 5 A schematic diagram of a system 100 for implementing the method (300) is provided. Figure 6 A schematic block diagram is provided depicting a user-modifiable file stored in one or more memory devices of a computing system of an aircraft Figure 1 . Figure 7 A schematic diagram of a computing device of an aircraft for generating a parameter report list is provided Figure 1 .

[0073] At (302), an on-site event may occur. For example, Figure 1One or more of the engines 114 of the aircraft 110 may experience unexpected behavior or performance during operation. For example, one or more of the engines 114 of the aircraft 110 may experience an unexpected engine shutdown during flight. As another example, one or more of the engines 114 of the aircraft 110 may experience unexpected behavior during startup or acceleration of the engine 114. As yet another example, one or more of the engines 114 of the aircraft 110 may experience unexpected behavior during takeoff or during the climb phase of flight. As a further example, one or more of the engines 114 of the aircraft 110 may experience unexpected behavior in a particular geographic region or near some naturally occurring event (such as a volcanic eruption or sandstorm).

[0074] In some embodiments, a recorded value and / or setting associated with a parameter of a downloaded data file may be compared with a model parameter value and / or setting for a given engine condition to determine whether one or more of the engines 114 has experienced unexpected behavior during operation. In other embodiments, the pilot or crew of the aircraft 110 may observe the unexpected performance of one or more of the engines 114. In further embodiments, one or more of the engines 114 may be determined to have experienced unexpected behavior in other suitable ways.

[0075] At (304), the method (300) includes determining one or more conditions associated with an in-field event. For example, a data file associated with a flight in which one or more of the engines 114 experienced unexpected behavior may be downloaded to one or more remote computing devices 156. The one or more remote computing devices 156 may perform an analysis on a recorded value and / or setting associated with a baseline parameter, and at least in part based on the recorded value and / or setting of the baseline parameter, the one or more remote computing devices 156 may determine one or more conditions associated with the in-field event. For example, the one or more remote computing devices 156 may determine altitude, external ambient temperature, airspeed, exhaust temperature, fuel flow rate, and / or other recorded parameter values and / or settings that provide a snapshot of the conditions of one or more of the engines 114 before, during, and / or after the in-field event. Based on the determined conditions associated with the in-field event, as will be explained below, one or more non-baseline parameters may be selected for recording for future flights or engine operations.

[0076] At (306), method (300) includes selecting one or more non-baseline parameters to record. For example, in some embodiments, one or more non-baseline parameters can be selected at least in part based on determined conditions of an in-flight event. In other words, one or more non-baseline parameters can be selected at least in part based on logged data indicative of the operating conditions and performance of one or more engines 114 before, during, and after an in-flight event for future flights or engine operations. For example, non-baseline parameters can include, but are not limited to, various calculated values (such as efficiency, pressure ratio, margin, etc.), as well as temperature, pressure, velocity, mass flow, etc. at or along a particular station of engine 114 that are not captured by the baseline parameters. For example, it may be desirable to record the pressure at the exit of the LP compressor 22 (commonly referred to as engine station 2.5). One or more remote computing devices 156 can select non-baseline parameters to record during the next flight or cycle. In some embodiments, one or more remote computing devices 156 can automatically select non-baseline parameters at least in part based on determined conditions of an in-flight event.

[0077] In some embodiments, for other reasons (i.e., not in response to an in-flight event), it may be desirable to record non-baseline parameters. For example, it may be desirable to conduct a study or investigation of the health of one or more components of engine 114 to provide additional data for the study. Thus, it will be understood that non-baseline parameters need not be selected for recording in response to or based on an in-flight event or determined conditions associated with an in-flight event.

[0078] At (308), method (300) includes generating a user-modifiable file. As used herein and in the appended claims, generating a file means creating a new file or modifying or updating an existing file. As an example, with specific reference to Figure 5 , one or more remote computing devices 156 of remote station 150 can generate a user-modifiable file 170. For this embodiment, user-modifiable file 170 includes a header 172 and a payload 174. Header 172 includes data (such as metadata), such as but not limited to, password information, timestamp, version or release number of user-modifiable file 170, checksum information, and any other useful information.

[0079] As Figure 6As shown, the payload 174 of the user-modifiable file 170 that can be modified by the user includes data 175. The data 175 of the payload 174 can include a list of selected parameters, and the list of selected parameters includes, for example, one or more selected parameters 176 to be recorded during engine operation. As described above, the selected parameters 176 can be non-baseline parameters. In some embodiments, the selected parameters 176 can be any optional parameters. The selected parameters 176 can be represented or defined on the user-modifiable file 170 in any suitable manner. For example, each selected parameter 176 can be represented or defined by a memory address or location in which the selected parameter 176 is stored on or indexed by one or more memory devices of the computing system 115 ( Figure 1 ) of the aircraft 110 ( Figure 1 ). In this way, as will be explained below, the selected parameters 176 can be effectively mapped to the optional parameters of the parameter list stored on one or more memory devices (such as one or more of the computing devices 118).

[0080] The data of the user-modifiable file 170 can also include one or more parameter settings associated with one or more selected parameters 176. For example, as Figure 6 shown, one or more parameter settings associated with one or more selected parameters 176 can include a data sampling rate 171, which indicates the rate or frequency at which the parameter values of one or more selected parameters 176 are to be recorded, for example, by the computing device 118 of the FADEC system. The data sampling rate can be any suitable rate, including, for example, once per second, three times per second, twenty times per second, etc. One or more parameter settings associated with one or more selected parameters 176 can also include a recording cutoff 173, which indicates when the parameter values of one or more selected parameters 176 will no longer be recorded, for example, by the computing device 118 of the FADEC system. For Figure 6 embodiments, the list of selected parameters of the data 175 includes a first selected parameter S-P1, a second selected parameter S-P2, a third selected parameter S-P3, and so on up to an Nth selected parameter S-PN. As shown in the figure, the first selected parameter S-P1 has an associated data sampling rate DSR1 and a recording cutoff RE1, the second selected parameter S-P2 has an associated data sampling rate DSR2 and a recording cutoff RE2, the third selected parameter S-P3 has an associated data sampling rate DSR3 and a recording cutoff RE3, and so on, such that the Nth selected parameter S-PN has an associated data sampling rate DSRN and a recording cutoff REN. The data sampling rates 171 can be the same or different. Similarly, the recording cutoffs can be the same or different. It should be understood that the data of the user-modifiable file 170 can include other parameter settings associated with one or more selected parameters 176.

[0081] At (310), method (300) includes receiving a generated user-modifiable file. For example, as Figure 5 shown, the generated user-modifiable file 170 can be transmitted to the aircraft 110. The user-modifiable file 170 can be transmitted in any suitable manner (e.g., by any of the transmission techniques described herein). One or more of the communication units 125, 126 can receive a data transmission from one or more transceivers 154 of the remote station 150. The data transmission can include the user-modifiable file 170. The communication units 125, 126 can receive the user-modifiable file 170 via wireless communication, via a wired connection, and / or via a manual transfer (e.g., by connecting a removable storage device to a computing device of the aircraft 110). Upon receiving the data transmission, the communication units 125, 126 can route the user-modifiable file 170 to one or more processing devices of the computing system 115 of the aircraft 110. One or more processing devices of the computing system 115 can receive the user-modifiable file 170 and, as will be explained below, can then store the user-modifiable file 170. In other example embodiments, a data transmission including the generated user-modifiable file 170 can be transmitted directly to the computing device 118.

[0082] At (312), method (300) includes storing the received user-modifiable file in one or more memory devices of a carrier's computing system. For example, Figure 6 a schematic block diagram depicting the user-modifiable file 170 stored in one or more memory devices 146 of the computing system 115 of the aircraft 110 is provided. In some embodiments, the one or more memory devices 146 storing the user-modifiable file 170 can be one or more memory devices of one or more computing devices 118. Thus, the user-modifiable file 170 can be routed to one or more of the computing devices 118. The computing device 118 can receive and store the user-modifiable file 170, e.g., stored in one or more of its memory devices.

[0083] In other embodiments, the user modifiable file 170 can be routed to and stored in one or more computing devices on the aircraft 110 other than the computing device 118. As an example, the user modifiable file 170 can be routed to, received by, and stored in one or more computing devices located within the avionics bay 120. In other embodiments, the user modifiable file 170 can be routed to and received by and stored on one or more memory devices of the communication units 125, 126. Additionally, in some embodiments, the memory location storing the user modifiable file 170 is a dedicated memory location configured to store only the user modifiable file 170. In this way, the content of the user modifiable file 170 can be more easily found, accessed, and read, for example, by the engine reporting software executed by the computing device 118.

[0084] In some embodiments, the data transfer and / or the user modifiable file 170 is encrypted. In such embodiments, one or more of the communication units 125, 126 can decrypt the received data transfer and / or the user modifiable file 170. The decrypted user modifiable file 170 can then be routed to the computing device 118 of the FADEC system or some other computing device of the aircraft 110 as described above. In some embodiments, the user modifiable file 170 is decrypted by the computing device 118 or by some other intermediate computing device rather than the communication units 125, 126.

[0085] At (314), the method (300) can include performing a compatibility check on the content of the user modifiable file. For example, once the user modifiable file 170 is received at (310) and subsequently stored at (312), the computing device 118 of the aircraft 110 and / or other computing devices can determine the integrity and / or compatibility of the content of the user modifiable file 170 with the hardware, software, firmware, etc. of the computing device 118. In one aspect of performing the compatibility check at (314), the computing device and / or the computing device 118 can determine whether the user modifiable file 170 was successfully uploaded by performing one or more data integrity operations (e.g., cyclic redundancy check, checksum check, encrypted checksum and digital signature, etc.). In some embodiments, if the user modifiable file 170 fails the data integrity operation, the user modifiable file 170 can be ignored. On the other hand, if the user modifiable file 170 passes the data integrity operation, the computing device and / or the computing device 118 can proceed to (316). In some embodiments, (314) can be performed before (312). In some other embodiments, (314) can be performed before and after performing (312).

[0086] At (316), method (300) includes specifying parameters to be recorded without modifying reporting software by reporting software executed on at least one of one or more computing devices (e.g., computing device 118) of an aircraft, where the parameters to be recorded include one or more selected parameters. In some embodiments, specifying the parameters to be recorded includes generating a parameter report list, where the parameters on the parameter report list specify the parameters to be recorded. The parameter report list may contain or include one or more selected parameters noted in user-modifiable file 170 and one or more baseline parameters 178. For example, one or more of computing devices 118 may generate or modify parameter report list 180 that contains one or more selected parameters 176 received as part of user-modifiable file 170 and one or more baseline parameters 178. That is, computing device 118 may generate a list of parameters to be recorded by computing device 118. As previously described, as used herein and in the appended claims, generating a file means creating a new file or modifying or updating an existing file. Thus, in some embodiments, computing device 118 may create a new parameter record list that contains baseline parameters 178 and selected parameters 176. In other embodiments, computing device 118 may modify or update an existing parameter list that contains baseline parameters 178 and selected parameters 176.

[0087] Figure 7 A schematic block diagram of one computing device 118 that generates parameter report list 180 is provided. As shown, reporting software 190 (e.g., engine reporting software in this embodiment) may be executed by one or more processing devices of computing device 118. In particular, reporting software 190 includes instructions that cause one or more processing devices of computing device 118 to generate parameter report list 180 when executed by one or more processors. Additionally, as will be explained below, e.g., during engine operation, reporting software 190 includes instructions that cause one or more processing devices of computing device 118 to record values associated with the parameters in parameter report list 180 when executed.

[0088] As Figure 7 shown, computing device 118 includes parameter list 185, which includes parameters that computing device 118 may record. Parameter list 185 may contain any suitable number of parameters. For this embodiment, parameter list 185 includes baseline parameters 178 and optional parameters 179, where optional parameters 179 may be non-baseline parameters. In some embodiments, e.g., during engine operation, baseline parameters 178 are always recorded by computing device 118, and optional non-baseline parameters generally are not recorded by computing device 118. In some embodiments, parameter list 185 is fixed within reporting software 190 and may only be modified by changing the source code of reporting software 190. For Figure 7In an embodiment, the baseline parameters 178 include a first baseline parameter BP1, a second baseline parameter BP2, a third baseline parameter BP3, and so on up to an Nth baseline parameter BPN. The optional non-baseline parameters 179 include a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, and so on up to an Nth optional parameter SPN.

[0089] To generate the parameter report list 180, the reporting software 190 accesses and reads the user-modifiable file 170 when executed. In particular, the reporting software 190 first accesses the user-modifiable file 170 stored on one or more memory devices 146 of the computing system 115. Once accessed, the reporting software 190 reads the selected parameters 176 contained in the user-modifiable file 170 when executed. In some embodiments, the reporting software 190 may access and read but not write to the user-modifiable file 170. This can prevent unintentional modification of the user-modifiable file 170. As described above, the selected parameters 176 may be represented or defined in any suitable manner (e.g., by a memory address indicating the location where the optional parameter is indexed on the computing system 115). For Figure 7 the embodiment, the selected parameters 176 contained in the user-modifiable file 170 include a first selected parameter S-P1 and a third selected parameter S-P3.

[0090] Once the reporting software 190 accesses and reads the user-modifiable file 170, the reporting software 190 maps the selected parameters 176 contained in the user-modifiable file 170 to the optional non-baseline parameters 179 when executed. In Figure 7 an example embodiment, the first selected parameter S-P1 corresponds to the first optional parameter SP1, while the third selected parameter S-P3 corresponds to the third optional parameter SP3. For example, the first selected parameter S-P1 may represent the memory location where the first optional parameter SP1 is stored on the computing device 118, and the third selected parameter S-P3 may represent the memory location where the third optional parameter SP3 is stored on the computing device 118. Thus, the reporting software 190 maps the first selected parameter S-P1 to the first optional parameter SP1 and the third selected parameter S-P3 to the third optional parameter SP3 when executed. The mapped parameters are specified by the reporting software 190 to be included on the report parameter list 180.

[0091] For example, in Figure 7In it, the first optional parameter SPl and the third optional parameter SP3 of the mapping are specified to be included in the generated or modified parameter report list 180. As a result, the generated or modified parameter report list 180 includes the baseline parameters 178 (including BP1, BP2, BP3, and BPN) and the selected parameters 176 (including SP1 and SP3). In the case where the selected parameters 176 included in the user-modifiable file 170 cannot be mapped to the optional non-baseline parameters 179, the selected parameters 176 included in the user-modifiable file 170 can be ignored by the reporting software 190. In addition, an error notification can be generated, for example, by executing the reporting software 190, and the error notification can be provided to the user.

[0092] In addition, when generating the parameter report list 180, one or more parameter settings associated with the selected parameters can be included in the generated or modified parameter report list 180. As an example, the data sampling rate or frequency for recording the values of the selected parameters can be linked to the selected parameters in the generated or modified parameter report list 180. As another example, a deadline indicating the time and / or date when the parameter values of the selected parameters should stop being recorded can be linked to the selected parameters in the generated or modified parameter report list 180. It should be understood that other parameter settings can be linked to the selected parameters 176 in the generated or modified parameter report list 180.

[0093] It is worth noting that when generating the parameter report list 180, the reporting software 190 and any other engine software are not changed, altered, or otherwise modified. That is, when executed, the reporting software 190 can read the selected parameters 176 from the uploaded user-modifiable file 170, map the selected parameters 176 to the optional parameters of the parameter list 185, and specify the mapped parameters to be included in the parameter report list 180 together with the baseline parameters 178 without changing, altering, or otherwise modifying the reporting software 190 or any other engine software. In this way, among other benefits, parameters can be added and / or removed from the parameter report list 180 without the need for a lengthy software code certification process. The user-modifiable file 170 can be available in multiple flights or missions, resent each flight, or stored in a memory location that is not part of the engine control software, such that the user-modifiable file 170 can be reread each time the reporting logic or the reporting software 190 is executed.

[0094] At (318), return to Figure 1 、 4 and 5, once the parameter report list 180 is generated at (316), the method (300) includes operating the propulsion system. For example, the propulsion system can include one or more engines, such as Figure 2Turbofan engine 114. When the engine operates and generates thrust for propelling the aircraft 110, the computing device 118 may record data related to the engine 114 and the aircraft 110. In other embodiments, the propulsion system may include both an engine and an electric motor, such as for driving a fan or a propeller. In other embodiments, the propulsion system may include one or more electric motors operably coupled to one or more fans or propellers for propulsion. In such embodiments, data related to the electric motor and / or other electrical components associated with the propulsion system may be recorded.

[0095] At (320), as the engine operates, method (300) includes receiving sensor data from one or more sensors. For example, the computing device 118 may receive one or more sensor outputs from one or more engine sensors 210. The one or more sensors 210 may sense or measure values of parameters related to the engine 114 (such as fan speed, core speed, temperature at various stations along the core air flow path, etc.). Signals from the sensors 210 may be routed to the computing device 118 and processed. Then, the computing device 118 may calculate or predict values of other parameters (such as exhaust temperature, mass flow rate at various stations of the engine 114, remaining stall margin, etc.). Additionally, in some implementations, the computing device 118 may receive sensor data from one or more vehicle sensors 212 located on the aircraft 110. The sensor outputs received from the one or more vehicle sensors 212 may be received as part of the vehicle data transmitted from the vehicle interface unit 122 to the computing device 118 (e.g., via the data communication link 124( Figure 1 ))). Additionally, engine data including sensed and calculated values of certain engine parameters may be transmitted to the vehicle interface unit 122 and ultimately to one or more vehicle systems 160.

[0096] At (322), method (300) includes recording engine operation data. For example, the reporting software 190, when executed by the computing device 118, may record parameter values of one or more parameters in the generated parameter report list 180 at least partially based on the received sensor data. For example, the sensed, calculated, and / or predicted parameter values of engine and / or aircraft parameters (including the baseline parameters 178 and the selected parameters 176) may be compiled into a data file 200 as shown Figure 5 in. The computing device 118, particularly one or more processors of the computing device 118 that execute the instructions of the reporting software 190, may continuously or rollingly write to the data file 200 when recording data or at a predetermined interval (e.g., every 15 milliseconds, every 25 milliseconds, or per second).

[0097] As Figure 5As best shown, the data file 200 includes a header 202 and a payload 204. The header 202 includes data (e.g., metadata) indicating, but not limited to, cryptographic information, a timestamp, a version or release number of the user-modifiable file 170 for specifying parameters to be recorded, checksum information, a communication log, an error log, etc., and other information. The payload 204 of the data file 200 includes recorded values of the parameters listed in the generated parameter report list 180, including the recorded selected parameter values 206 associated with the selected parameters 176 and the recorded baseline parameter values 208 associated with the baseline parameters 178. For example, the data file 200 can be a binary machine-readable file. As another example, in addition to being machine-readable, the data file 200 can also be a human-readable file. As yet another example, the data file 200 can be partially human-readable and partially binary machine-readable. Additionally, it should be understood that Figure 5 the data file 200 depicted in Figure 5 is only an example, and in other exemplary embodiments, the data file 200 can have other configurations. For example, in some embodiments, the data file 200 may not include a header 202.

[0098] In some embodiments, one or more processors of the computing system 115 are configured to record data using the generated parameter report list 180 and the received sensor data after the propulsion system is started or begins a subsequent power cycle. That is, the uploaded user-modifiable file may only be available or activated for use after the propulsion system is started or begins a subsequent power cycle. In such an embodiment, for example, one or more processors of the computing system 115 can cause the propulsion system to start. For example, one or more processors of the computing device 118 can cause the engine to start, i.e., begin operation. At startup, one or more processors of the computing system 115 can determine whether the user-modifiable file has been uploaded to the aircraft 110, or in other words, one or more processors of the computing system 115 can determine whether the user-modifiable file has been received.

[0099] In yet another embodiment, one or more processors of the computing system 115 are configured to record data using the generated parameter report list 180 and the received sensor data upon a subsequent power-on of the computing device 118. That is, the uploaded user-modifiable file may only be available or activated for use after a subsequent power-on of the computing device 118. It is noted that the power-on of the computing device 118 can occur before the propulsion system is started. In this way, data can be recorded before and during the startup of the propulsion system. Additionally, data recording can continue after the propulsion system is shut down. Thus, in some embodiments, data can be recorded throughout the time the computing device 118 is powered on, regardless of whether the propulsion system is on or off.

[0100] When one or more processors (e.g., of one or more computing devices) determine that a user-modifiable file has been received, the method (300) proceeds from (312) to (322). Specifically, the method (300) continues by specifying, without modifying the reporting software 190, the parameters to be recorded by the reporting software 190 executed on at least one of the one or more computing devices of the computing system 115, and then recording engine operation data for parameters included at least in the user-modifiable file 170, for example. When one or more processors (e.g., of one or more computing devices) determine that a user-modifiable file has not been received, the recorded data may include only data or parameter values associated with the baseline parameters 178. When one or more processors determine that an existing user-modifiable file is still stored in a dedicated memory location and has not expired, the recorded data may include data or parameter values associated with the baseline parameters, as well as parameter values associated with selected parameters within the existing user-modifiable file.

[0101] At (324), the method (300) includes providing a data file. For example, the data file 200 may be transmitted or otherwise downloaded to other sources in a variety of suitable ways. For example, the data file 200 may be wirelessly transmitted via one or more of the communication devices 125, 126 to, for example, a ground station 150, another aircraft or vehicle, etc. For example, the data file 200 may be wirelessly transmitted in flight via SATCOM and / or air-to-ground (ATG) technology. As another example, the data file 200 may be wirelessly transmitted after flight via a cellular, Wi-Fi, and / or Bluetooth network. In other embodiments, the data file 200 may be transmitted via a wired connection. In some embodiments, the data file 200 may be transmitted as a single file or may be parsed and sent in parts or data packets. The data file 200 may then be reconstructed, for example, by the remote computing device 156. Additionally, if the data file 200 is encrypted, the data file 200 may be decrypted. The reconstructed and decrypted data file 200 may be used, for example, by the remote computing device 156 for visualization, analysis, archiving, etc. Additionally or alternatively, the data file 200 may be transmitted via one or more wired connections to, for example, a portable device 142 ( Figure 3 ). The access terminal may be implemented, for example, on a laptop computer, a tablet computer, a mobile device, or other suitable computing device. A maintenance professional may use the portable device 142 to retrieve the data file 200.

[0102] Advantageously, by adding or updating the parameter report list in the manner described herein, non-baseline parameters (or more generally, optional parameters) can be added to the FADEC parameter report list and monitored faster than in the prior art in response to in-field or engine events. In particular, in accordance with the inventive aspects of the present disclosure, new or updated FADEC parameters can be monitored in response to in-field events on the order of hours or days rather than weeks or months. This can be achieved at least in part by uploading a user-modifiable file to the aircraft, which can be accessed and read by reporting software associated with generating and recording data during engine operation. The reporting software can specify new FADEC parameters for recording without modifying the reporting software. In this way, the inventive aspects of the present disclosure provide the flexibility to modify the parameters being captured without software changes, which eliminates the need for a lengthy software code re-certification process. Additionally, the inventive aspects of the present disclosure described herein leverage the existing FADEC architecture, which separates lower-level functions from higher critical functions, including engine control software.

[0103] In addition, the user-modifiable file 170 can be pushed or otherwise sent to an aircraft and / or engine identified as having experienced an abnormal or unexpected engine operation, or being scheduled or predicted to operate under defined conditions of an in-field event. For example, in some embodiments, the method (300) includes identifying one or more carriers or engines scheduled to operate under defined conditions of an in-field event. For example, the remote computing device 156 can identify each carrier and / or engine scheduled to operate under defined conditions of an in-field event, for example, based on flight plan information. In some embodiments, the method (300) includes identifying one or more carriers or engines that have experienced an abnormal or unexpected engine operation. Additionally, in such embodiments, the method (300) further includes sending the generated user-modifiable file 170 to one or more of the identified one or more carriers or engines scheduled to operate under defined conditions of an in-field event and / or that have experienced an abnormal or unexpected engine operation. That is, the generated user-modifiable file 170 can be pushed or otherwise provided to each carrier and / or engine that is to or is predicted to operate under defined conditions of an in-field event or has experienced an abnormal or unexpected engine operation. In this way, the analysis can be performed, for example, by the remote computing device 156 using data recorded from multiple engines that have been subjected to defined conditions of an in-field event and / or have experienced an abnormal or unexpected engine operation associated with certain operating conditions.

[0104] In some embodiments, it may be desirable to change the parameter settings (e.g., data sampling rate) of one or more parameters stored in a parameter list fixed within the reporting software. By way of example, Figure 8Schematic illustration of a computing device of a vehicle propulsion system that generates a parameter report list 180 in which one or more parameter settings are changed. For this embodiment, the computing device may be computing device 118 and the vehicle propulsion system may be engine 114 of aircraft 110( Figure 1 ). The computing system 115 has one or more memory devices and one or more processors.

[0105] Reference Figure 8 , one or more processors are configured to receive a user-modifiable file 170 containing data 175, the data 175 including parameter settings 188 associated with selected parameters 176. For example, the user-modifiable file 170 may be received from a communication unit (e.g., communication unit 125 or 126; Figure 1 ). The communication unit may receive the user-modifiable file 170 from a remote station via data transfer. In this example, the user-modifiable file 170 includes selected parameters 176, the selected parameters 176 including a first selected parameter S-BP1 and a second selected parameter S-BP2. The user-modifiable file 170 also includes parameter settings 188 associated with the selected parameters 176. For example, a first parameter setting PS1 is associated with the first selected parameter S-BP1, while a second parameter setting PS2 is associated with the second selected parameter S-BP2. The first and second parameter settings PS1, PS2 may represent any suitable parameter settings, such as a data sampling rate.

[0106] One or more processors are configured to access and read the user-modifiable file 170 such that they can link or map the parameter settings 188 associated with the selected parameters 176 to the parameters of parameter list 185 by executing report software 190 on at least one of the one or more processors (e.g., of computing device 118). That is, each parameter setting associated with a selected parameter of the user-modifiable file 170 is linked or mapped to a parameter of parameter list 185. For example, in this example, the first selected parameter S-BP1 corresponds to a first baseline parameter BP1 having an associated default or current first parameter setting DPS1. The second selected parameter S-BP2 corresponds to a second baseline parameter BP2 having an associated default or current second parameter setting DPS2. Thus, the first selected parameter S-BP1 is mapped to the first baseline parameter BP1, and thus, the first parameter setting PS1 is mapped to the first baseline parameter BP1 of parameter list 185. Similarly, the second selected parameter S-BP2 is mapped to the second baseline parameter BP2, and thus, the second parameter setting PS2 is mapped to the second baseline parameter BP2 of parameter list 185.

[0107] One or more processors are configured to generate a parameter report list 180 that includes parameters and parameter settings mapped thereto by executing reporting software 190 on at least one of the one or more processors (e.g., of computing device 118). Notably, the reporting software 190 is not modified during mapping and generation. In other words, the reporting software 190 is not modified when mapping parameter settings 188 to parameters within the parameter list 185 and is not modified when generating the parameter report list 180. For Figure 8 the example shown, the parameter report list 180 is generated by the executed reporting software 190 such that the first baseline parameter BP1 has a first parameter setting PS1 (instead of the first default parameter setting DPS1), and such that the second baseline parameter BP2 has a second parameter setting PS2 (instead of the second default parameter setting DPS2). As shown, the parameter settings 188 for the third baseline parameter BP3 and all other parameters within the parameter report list 180 remain unchanged.

[0108] After generating the parameter report list 180, one or more processors are configured to receive sensor data from one or more sensors (e.g., engine sensors, aircraft sensors, etc.). Additionally, one or more processors are configured to record the parameter values of the parameters 178 (and in some cases, the selected parameters 176) in the generated parameter report list 180 based at least in part on the received sensor data and their respective parameter settings 188 (including the parameter settings (e.g., PS1 and PS2) mapped to their respective parameters 178).

[0109] One or more processors may generate a data file by executing the reporting software 190, the data file including the parameter values recorded for one or more of the parameters in the generated parameter report list 180. One or more processors may also provide the data file. One or more processors may cause a communication unit (e.g., Figure 1 communication unit 125 of Figure 1 to transmit at least a portion of the data file to a remote station (e.g.,

[0110] In some embodiments, the parameter report list 180 is only activated upon a subsequent startup of the propulsion system. In such embodiments, one or more processors are configured to record parameter values of one or more parameters of the generated parameter report list 180 based at least in part on sensor data received upon a subsequent startup of the propulsion system. In other embodiments, the parameter report list 180 is only activated upon a subsequent power-up of the computing device 118. In such embodiments, one or more processors are configured to record parameter values of one or more parameters of the generated parameter report list 180 based at least in part on sensor data received upon a subsequent power-up of the computing device 118.

[0111] In addition, although various embodiments of the system 100 and method (300) have been described herein in which the parameter list 185 differentiates between baseline and non-baseline parameters, in some embodiments, the parameter list 185 does not differentiate between baseline and non-baseline parameters. In such embodiments, all possible parameters of the parameter list 185 can be selected and specified to be included in the generated parameter report list 180.

[0112] As an example, Figure 9 a schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list is provided. For this embodiment, the computing device can be the computing device 118 and the vehicle propulsion system can be the engine 114 of the aircraft 110 ( Figure 1 ). The computing system 115 has one or more memory devices and one or more processors, which are configured to receive a user-modifiable file 170 containing data 175 that indicates one or more selected parameters 176 to be recorded, for example, during operation of the propulsion system. In some embodiments, the data 175 of the user-modifiable file 170 indicates the one or more selected parameters 176 to be recorded by representing each of the one or more selected parameters with a memory address. In particular, the memory addresses representing the one or more selected parameters 176 to be recorded can each indicate a memory location (e.g., a memory location on one or more memory devices of the computing device 118) where the one or more selected parameters 176 are stored on one or more memory devices of the computing system 115. In other embodiments, the data 175 of the user-modifiable file 170 can indicate the one or more selected parameters 176 to be recorded by other designations (e.g., by a parameter name defined in a report or control software, by a portion of a parameter name defined in a report or control software, by a particular nomenclature or code defined in a report or control software, by a parameter position within a parameter list, etc.).

[0113] One or more processors are also configured to generate a parameter report list 180 that includes one or more selected parameters 176 by executing reporting software 190 on at least one of the one or more processors without modifying the reporting software 190. In some embodiments, when generating the parameter report list 180, the one or more processors are configured to read a user-modifiable file 170 that contains data 175 that indicates one or more selected parameters 176 to be recorded. For example, one or more processors of the computing device 118 may access and read the user-modifiable file 170 stored in one or more memory devices 146 (e.g., of a computing device of the computing system 115). In some embodiments, the one or more memory devices 146 are components of the computing device 118. The received user-modifiable file 170 may be stored in a dedicated memory location. For Figure 9 the illustrated embodiment, the selected parameters 176 included within the data 175 of the user-modifiable file 170 include a first selected parameter S-P1 and a third selected parameter S-P3.

[0114] After reading the user-modifiable file 170, when generating the parameter report list 180, the one or more processors are configured to map the one or more selected parameters 176 to optional parameters 181 of a parameter list 185 fixed within the reporting software 190. For Figure 9 the illustrated embodiment, the parameter list 185 includes a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, and so on up to an Nth optional parameter SPN. As depicted, the one or more processors map the selected parameters 176 (the first selected parameter S-P1 and the second selected parameter S-P2 in this example) to their respective optional parameters 181 (the first optional parameter SP1 and the third optional parameter SP3 in this example) within the parameter list 185. Thus, the optional parameters 181 within the parameter list 185 that are mapped to the one or more selected parameters 176 are designated to be included in the parameter report list 180.

[0115] In some embodiments, the data 175 of the user-modifiable file 170 contains one or more parameter settings associated with the one or more selected parameters 176. As an example, one or more parameter settings associated with the one or more selected parameters include a data sampling rate that indicates the rate at which parameter values of the one or more selected parameters are to be recorded. As another example, one or more parameter settings associated with the one or more selected parameters include a recording cutoff that indicates when parameter values of the one or more selected parameters will no longer be recorded. The parameter settings may be linked to their associated optional parameters 181 and included in the parameter report list 180.

[0116] Once the parameter report list 180 is generated, one or more processors are further configured to receive sensor data from one or more sensors (e.g., engine sensors, aircraft sensors, etc.). Additionally, one or more processors are configured to record parameter values of one or more selected parameters 176 in the generated parameter report list 180 based at least in part on the received sensor data. One or more processors may generate a data file by executing reporting software 190, the data file including the parameter values recorded for one or more selected parameters in the generated parameter report list 180. One or more processors may also provide the data file. One or more processors may cause a communication unit (e.g., Figure 1 the communication unit 125) to transmit at least a portion of the data file to a remote station (e.g., Figure 1 the remote station 150). For example, the remote station may be a ground station or a second vehicle.

[0117] In some embodiments, the parameter report list 180 is only activated upon a subsequent startup of the propulsion system. In such embodiments, one or more processors are configured to record parameter values of one or more selected parameters 176 in the generated parameter report list 180 based at least in part on the sensor data received upon a subsequent startup of the propulsion system. In other embodiments, the parameter report list 180 is only activated upon a subsequent power-up of the computing device 118. In such embodiments, one or more processors are configured to record parameter values of one or more selected parameters 176 in the generated parameter report list 180 based at least in part on the sensor data received upon a subsequent power-up of the computing device 118.

[0118] Updating a parameter list with selected parameters and transmitting engine data during flight

[0119] Now generally referring to Figure 1 、 10 、11, 12, and 13, example ways in which the FADEC system may be queried during flight or on the ground to record selected FADEC parameter values within a particular recording window will now be provided. Additionally, example ways in which the FADEC system may transmit the recorded FADEC parameter values will be provided. In certain cases, as described above, an in-field event may occur where the engine experiences abnormal or unexpected behavior. It may be desirable to obtain engine data immediately or quickly in response to the in-field event. For example, it may be desirable to immediately begin recording certain FADEC parameter values in response to an in-flight engine flameout and restart. In other cases, it may be desirable to query the FADEC system during a mission to "look back" and compile parameter values that have been recorded during a preselected past time window. The systems and methods described herein implement such functionality. Figure 10A flowchart of an example method (400) is provided for querying a FADEC system, recording parameter values associated with selected parameters included in the query, and transmitting the recorded data to, for example, a remote station. For example, the FADEC system may be associated with one or more engines (such as one or more engines 114 of an aircraft 110 such as Figure 1 ). It should be understood that the exemplary method (400) may be modified, adapted, extended, rearranged, and / or omitted in various ways without departing from the scope of the present subject matter. Figure 11 A schematic diagram of a system 500 configured to implement method (400) is provided. Figure 12 A schematic block diagram of a user-modifiable file depicting a data query stored in one or more memory devices of a vehicle's computing system is provided. Figure 13 A schematic diagram of a computing device associated with an engine of a vehicle that generates a list of parameter reports is provided.

[0120] At (402), an on-site event may occur. For example, Figure 1 one or more of the engines 114 of an aircraft 110 such as

[0121] may experience abnormal or unexpected behavior during operation. For example, one or more of the engines 114 of the aircraft 110 may experience an unexpected engine shutdown or flameout during flight and may then restart or attempt to restart. As another example, one or more of the engines 114 of the aircraft 110 may experience unexpected behavior during takeoff or during the climb phase of flight. As a further example, one or more of the engines 114 of the aircraft 110 may experience unexpected behavior in a particular geographic region or near some naturally occurring event (such as a volcanic eruption or sandstorm). Thus, an on-site event may occur when one or more engines experience abnormal or unexpected behavior during operation or when certain predefined events occur (such as an engine being near an area or point of interest). Figure 11 At (404), method (400) includes generating, by one or more remote computing devices, a data query that includes a user-modifiable file that includes one or more selected parameters. For example, as

[0122] shown, one or more remote computing devices 156 of a remote station 150 may generate a data query 508 that includes a user-modifiable file 510. The user-modifiable file 510 of the data query 508 may include a header 512 and a payload 514. The header 512 includes data (such as metadata) that indicates, but is not limited to, password information, a timestamp, a query version or release number indicating the version of the data query 508, checksum information, and other useful information. Figure 12As shown, the payload 514 of the user-modifiable file 510 includes data 515. The data 515 of the payload 514 may include a list of selected parameters, which contains one or more selected parameters 516 to be recorded, for example, during the current flight or engine cycle. That is, one or more selected parameters 516 of the user-modifiable file 510 are FADEC parameters, and the computing device 118 records the parameter values of the FADEC parameters during engine operation. The selected parameter 516 can be any optional FADEC parameter. In some embodiments, the selected parameter 516 can be a non-baseline parameter. The selected parameter 516 can be represented or defined on the user-modifiable file 510 in any suitable manner. For example, each selected parameter 516 can be represented or defined by the user-modifiable file 510 as the selected parameter 516 is stored on or indexed to a memory address or location in one or more memory devices of the computing system 115 ( Figure 1 ) of the aircraft 110 ( Figure 1 ). In this way, as will be explained below, the selected parameter 516 can be effectively mapped or mapped to the optional parameter of the parameter list stored on one or more memory devices (such as one or more of the computing devices 118).

[0123] The data 515 of the user-modifiable file 510 may also include one or more parameter settings associated with one or more selected parameters 516. For example, as Figure 12 shown, one or more parameter settings associated with one or more selected parameters 516 may include a data sampling rate 520, which indicates the rate or frequency at which the parameter values of one or more selected parameters 516 will be recorded by the computing device 118 of the FADEC system, for example. The data sampling rate 520 can be any suitable rate, including, for example, once per second, three times per second, twenty times per second, etc. One or more parameter settings associated with one or more selected parameters 516 may also include a recording window 518, which indicates when the parameter values of one or more selected parameters 516 will be recorded by the computing device 118 of the FADEC system, for example. That is, the recording window 518 indicates the time period during which the computing device 118 is to record the selected parameter values 536 associated with their respective selected parameters 516. In some embodiments, the computing device 118 only records one or more selected parameter values 536 associated with one or more selected parameters 516 of the data query 508 during their respective recording windows 518.

[0124] For Figure 12In an embodiment, the selected parameter list of data 515 includes a first selected parameter S-P1, a second selected parameter S-P2, a third selected parameter S-P3, and so on up to an Nth selected parameter S-PN. As shown, the first selected parameter S-P1 has an associated data sampling rate DSR1 and a recording window RW1, the second selected parameter S-P2 has an associated data sampling rate DSR2 and a recording window RW2, the third selected parameter S-P3 has an associated data sampling rate DSR3 and a recording window RW3, and so on such that the Nth selected parameter S-PN has an associated data sampling rate DSRN and a recording window RWN. For each selected parameter 516, the data sampling rate 520 can be the same or can be different. Similarly, for each selected parameter 516, the recording window 518 can be the same or can be different. The recording windows RW1, RW2, RW3, RWN each indicate the time period for which the parameter values of their respective selected parameters are to be recorded. It should be understood that the data 515 of the user-modifiable file 510 can include other parameter settings associated with one or more selected parameters 516.

[0125] The data 515 of the user-modifiable file 510 can also include a transmission rate 522, which indicates the frequency or interval at which the query response file 530 ( Figure 11 ) will be transmitted, for example, from the aircraft 110 to the remote station 150. In some embodiments, the transmission rate 522 provided in the data query 508 can set the transmission rate such that the query response file 530 is transmitted after all the recorded parameter values (i.e., the recorded selected parameter values 536, and in some embodiments, the recorded baseline parameter values 538) are recorded during their respective recording windows 518 and compiled into the query response file 530. Advantageously, in such embodiments, the transmission from the aircraft 110 to the remote station 150 is minimized, and thus the data usage and transmission costs are minimized.

[0126] In some embodiments, as described above, the data query 508 that includes the user-modifiable file 510 is generated by one or more remote computing devices 156, and the user-modifiable file 510 includes one or more selected parameters 516, a recording window 518 associated with the selected parameters 516, and a data sampling rate 520 associated with the selected parameters 516. For example, in some exemplary embodiments, the remote station 150 can be an engine monitoring station. The engine monitoring station can be located on the ground or on another vehicle. For example, the engine monitoring station can monitor a fleet of aircraft (e.g., including Figure 1engines of a fleet of engines 114 of the aircraft 110. During engine operation, the transceiver 154 of the remote station 150 or the engine monitoring station in this example can receive communications from the aircraft 110 and / or the engines 114 (e.g., from one or more of the communication units 125, 126), the communications indicating that one or more of the engines 114 has experienced an abnormal or unexpected engine behavior relative to an expected or baseline engine behavior (e.g., determined by a model taking into account the operating and / or environmental conditions in which the aircraft 110 and / or the engines 114 are operating), or more generally, that an in-field event has occurred.

[0127] For example, the computing device 118 can generate an in-flight or in-mission failure in response to the unexpected behavior, and the communication can indicate the type of in-flight failure. The received communications can be routed to one or more remote computing devices 156 for processing and data analysis. At least partially based on the received communications, one or more remote computing devices 156 can select or define selected parameters 516, one or more recording windows 518 or time periods of interest associated with the selected parameters 516, a data sampling rate 520 associated with the selected parameters 516, and a transmission rate 522, and can accordingly generate a data query 508 that includes a user-modifiable file 510. That is, the user-modifiable file 510 of the generated data query can include the defined selected parameters 516, recording windows 518, data sampling rate 520, and transmission rate 522. As an example, one or more remote computing devices 156 can define the selected parameters 516, recording windows 518, data sampling rate 520, and transmission rate 522 at least partially based on the in-flight failure or failure code.

[0128] One or more remote computing devices 156 may define selected parameters 516, a recording window 518, a data sampling rate 520, and a transmission rate 522 in response to an in-field event. For example, computing device 118 and / or remote computing devices 156 may determine conditions of the in-field event, the type of the in-field event, etc., and based on the determined conditions, in-field event type, etc., one or more remote computing devices 156 may define selected parameters 516, a recording window 518, a data sampling rate 520, and a transmission rate 522 to generate a data query 508. A pilot or crew member may also detect abnormal or unexpected engine behavior based on an observation of engine 114 or flight panel instruments. For example, the crew member may send a communication indicating the unexpected engine behavior to an engine monitoring station (or remote station 150), and based on the communication, one or more remote computing devices 156 may define selected parameters 516, a recording window 518, a data sampling rate 520, and a transmission rate 522 to generate a data query 508 that includes a user-modifiable file 510. In some embodiments, selected parameters 516, a recording window 518, a data sampling rate 520, and a data transmission rate 522 may be defined for other suitable reasons (e.g., to conduct a study or investigation of the health of one or more components of engine 114).

[0129] In some further embodiments, one or more remote computing devices 156 may define selected parameters 516, a recording window 518, a data sampling rate 520, and a transmission rate 522 without receiving a communication from aircraft 110. For example, if an engine monitoring station (e.g., remote station 150) determines that aircraft 110 is operating in a particular area or near a point of interest, one or more remote computing devices 156 may define or select selected parameters 516, a recording window 518, a data sampling rate 520, and / or a transmission rate 522 and may generate a data query that includes a user-modifiable file accordingly. As an example scenario, aircraft 110 may be taking off from a particular high-altitude airport, and the engines of one or more aircraft that took off from the high-altitude airport before aircraft 110 may have experienced and reported abnormal engine operation. One or more remote computing devices 156 may define selected parameters 516, a recording window 518, a data sampling rate 520, and / or a transmission rate 522 based on communications received from aircraft that took off from the high-altitude airport before aircraft 110 to better understand engine conditions during takeoff from the high-altitude airport.

[0130] At (406), method (400) includes transmitting / receiving a data query that includes a user-modifiable file. The generated data query 508 that includes the user-modifiable file 510 can be transmitted to the aircraft 110 in any suitable manner (e.g., via any of the transmission techniques described herein). When the aircraft 110 is performing a mission (i.e., a flight between a starting point and a destination), the data query 508 can be transmitted to the aircraft 110, or more specifically, to the FADEC system of the aircraft 110. For example, when the aircraft 110 is in the air, near an airport, or over the ocean, the data query 508 can be transmitted to the aircraft 110. For example, when the aircraft 110 is performing a mission, the transceiver 154 of the remote station 150 can transmit the data query 508 to the aircraft 110. As Figure 11 shown, one or more of the communication units 125, 126 can receive the data query 508 from one or more of the transceivers 154 of the remote station 150. In some embodiments, the data query 508 is encrypted and one or more of the communication units 125, 126 can decrypt the received data query 508. The decrypted data query 508 can then be routed to the computing device 118 of the FADEC system or some other computing device on the aircraft 110. Thus, the computing device 118 and / or some other computing device on the aircraft 110 can receive the generated data query 508. In some embodiments, the data query 508 is decrypted by the computing device 118 or by some other intermediate computing device rather than the communication units 125, 126.

[0131] At (408), method (400) includes storing the user-modifiable file of the received data query in one or more memory devices of the carrier's computing system. For example, Figure 12 a schematic block diagram depicting the user-modifiable file 510 stored in one or more memory devices 146 of the computing system 115 of the aircraft 110 is provided. In some embodiments, the one or more memory devices 146 that store the user-modifiable file 510 can be one or more memory devices of one or more of the computing devices 118. Thus, the user-modifiable file 510 can be routed to one or more of the computing devices 118. The computing device 118 can receive the user-modifiable file 510 and store the user-modifiable file 510 in, for example, one or more of its memory devices.

[0132] In other embodiments, the user-modifiable file 508 of the data query may be routed to and stored in one or more computing devices on the aircraft 110 other than the computing device 118. As an example, the user-modifiable file 510 may be routed to, received by, and stored in one or more computing devices located within the avionics bay 120. In other embodiments, the user-modifiable file 510 may be routed to and received by and stored on one or more memory devices of the communication units 125, 126. Additionally, in some embodiments, the memory location storing the user-modifiable file 510 is a dedicated memory location configured to store only the user-modifiable file 510. In this way, the content of the user-modifiable file 510 can be more easily found, accessed, and read by, for example, the engine reporting software executed by the computing device 118.

[0133] At (410), the method (400) may include performing a compatibility check on the content of the data query, and more specifically, on the content of the user-modifiable file of the data query. For example, once the user-modifiable file 510 is transmitted and received at (406) and then stored at (408), the computing device 118 and / or other computing devices of the aircraft 110 may determine the integrity and / or compatibility of the content of the user-modifiable file 510 with the hardware, software, firmware, etc. of the computing device 118. In one aspect of performing the compatibility check at (410), the computing device and / or the computing device 118 may determine whether the user-modifiable file 510 has been successfully uploaded or transmitted to the aircraft 110 by performing one or more data integrity operations (such as cyclic redundancy check, checksum check, cryptographic check, and digital signature, etc.). In some embodiments, if the user-modifiable file 510 fails the data integrity operation, the user-modifiable file 510 may be ignored. On the other hand, if the user-modifiable file 510 passes the data integrity operation, the computing device and / or the computing device 118 may proceed to (412).

[0134] At (412), method (400) includes specifying parameters to be recorded by reporting software executed on at least one of one or more computing devices (e.g., computing device 118) of an aircraft without modifying the reporting software, where the parameters to be recorded include one or more selected parameters of a user-modifiable file included within a received data query. In some embodiments, specifying the parameters to be recorded includes generating a parameter report list, where the parameters on the parameter report list specify parameters to be recorded, e.g., by computing device 118. The parameter report list may include or incorporate one or more selected parameters noted in user-modifiable file 510, and in some embodiments, one or more baseline parameters 525. For example, one or more of computing devices 118 may generate or modify parameter report list 580 that includes one or more selected parameters 516 received as part of user-modifiable file 510 and one or more baseline parameters 525. That is, computing device 118 may generate a list of parameters to be recorded by computing device 118. A plurality of baseline parameters 525 may be fixed within the reporting software of the FADEC system. Additionally, as noted previously, as used herein and in the appended claims, generating a file means creating a new file or modifying or updating an existing file. Thus, in some embodiments, computing device 118 may create a new parameter record list that includes baseline parameters 525 and selected parameters 516. In other embodiments, computing device 118 may modify or update an existing parameter list that includes baseline parameters 525 and selected parameters 516.

[0135] Figure 13 A schematic block diagram of one computing device 118 that generates parameter report list 580 is provided. As shown, reporting software 590 (e.g., engine reporting software in the present embodiment) may be executed by one or more processing devices of computing device 118. In particular, reporting software 590 includes instructions that, when executed by one or more processors, cause one or more processing devices of computing device 118 to generate parameter report list 580. Additionally, as will be explained below, e.g., during engine operation, reporting software 590 includes instructions that, when executed, cause one or more processing devices of computing device 118 to record values associated with the parameters in parameter report list 580.

[0136] As Figure 13As shown, the computing device 118 includes a parameter list 585 that includes parameters for which the computing device 118 can record parameter values. The parameter list 585 can contain any suitable number of parameters. For this embodiment, the parameter list 585 includes a baseline parameter 525 and an optional parameter 529, and the optional parameter 529 can be a non-baseline parameter. In some implementations, for example, during engine operation, the baseline parameter 525 is always recorded by the computing device 118, and the optional non-baseline parameter 529 is generally not recorded by the computing device 118 unless the computing device 118 is otherwise instructed to do so. In some embodiments, the parameter list 585 is fixed within the reporting software 590 and can only be modified by changing the source code of the reporting software 590. For Figure 13 this embodiment, the baseline parameter 525 includes a first baseline parameter BP1, a second baseline parameter BP2, a third baseline parameter BP3, and so on up to an Nth baseline parameter BPN. The optional non-baseline parameter 529 includes a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, a fourth optional parameter SP4, and so on up to an Nth optional parameter SPN.

[0137] To generate the parameter report list 580, the reporting software 590 accesses and reads the user-modifiable file 510 when executed. Specifically, the reporting software 590 first accesses the user-modifiable file 510 stored on one or more memory devices 146 of the computing system 115. Once accessed, the reporting software 590 reads the selected parameters 516 contained in the user-modifiable file 510 when executed. In some implementations, the reporting software 590 can access and read but not write to the user-modifiable file 510. This can prevent unintentional modification of the user-modifiable file 510. As described above, the selected parameters 516 can be represented or defined in any suitable manner (e.g., by a memory address indicating the location where the optional parameter 529 is indexed on the computing system 115). For Figure 13 this embodiment, the selected parameters 516 contained in the user-modifiable file 510 include a first selected parameter S-P1 and a fourth selected parameter S-P4.

[0138] Once the reporting software 590 accesses and reads the user-modifiable file 510, the reporting software 590 maps the selected parameters 516 contained in the user-modifiable file 510 to the optional non-baseline parameter 529 when executed. In Figure 13In an example embodiment, the first selected parameter S-P1 corresponds to the first optional parameter SP1, and the fourth selected parameter S-P4 corresponds to the fourth optional parameter SP4. For example, the first selected parameter S-P1 may represent the memory location of the first optional parameter SP1 stored on the computing device 118, and the fourth selected parameter S-P4 may represent the memory location of the fourth optional parameter SP4 stored on the computing device 118. Thus, when executed, the reporting software 590 maps the first selected parameter S-P1 to the first optional parameter SP1 and maps the fourth selected parameter S-P4 to the fourth optional parameter SP4. The mapped parameters are specified by the reporting software 590 to be included in the reporting parameter list 580.

[0139] For example, in Figure 13 the mapped first optional parameter SPl and fourth optional parameter SP4 are specified to be included in the generated or modified parameter report list 580. As a result, the generated or modified parameter report list 580 includes the baseline parameters 525 and the selected parameters 516. The baseline parameters 525 include BP1, BP2, BP3, up to the Nth or BPN baseline parameter, and the selected parameters 516 include SP1 and SP4. In the case where the selected parameters 516 included in the user-modifiable file 510 cannot be mapped to the optional non-baseline parameters 529, the selected parameters 516 included in the user-modifiable file 510 may be ignored by the reporting software 590. Additionally, an error notification may be generated, for example, by executing the reporting software 590, and the error notification may be provided to the user, and the error notification may indicate that one or more of the selected parameters 516 of the user-modifiable file 510 included in the data query 508 cannot be mapped to any of the optional parameters 529 of the parameter list 585.

[0140] Further, when generating the parameter report list 580, one or more parameter settings associated with the selected parameters may be included in the generated or modified parameter report list 580. As an example, the data sampling rate or frequency at which the values of the selected parameters are to be recorded may be linked to the selected parameters in the generated or modified parameter report list 580. As another example, a recording window indicating the time period for which the parameter values of the selected parameters are to be recorded may be linked to the selected parameters in the generated or modified parameter report list 580. It should be understood that other parameter settings may be linked to the selected parameters 516 in the generated or modified parameter report list 580.

[0141] It should be noted that when generating the parameter report list 580, the reporting software 590 and any other engine software are not changed, altered, or otherwise modified. That is, when executed, the reporting software 590 can read the selected parameters 516 from the uploaded user-modifiable file 510, map the selected parameters 516 to the optional parameters 529 of the parameter list 585, and specify the mapped parameters to be included in the parameter report list 580 together with the baseline parameters 525 without changing, altering, or otherwise modifying the reporting software 590 or any other engine software. In this way, among other benefits, parameters can be added and / or removed from the parameter report list 580 without the need for a lengthy software code certification process.

[0142] At (414), the method (400) includes receiving sensor data from one or more sensors. For example, as Figure 11 shown, the computing device 118 can receive sensor data from one or more engine sensors 210. The one or more sensors 210 can sense or measure values of parameters related to the engine 114 (such as fan speed, core speed, temperature at various stations along the core air flow path, etc.). Signals from the sensors 210 can be routed to the computing device 118 and processed. Then, the computing device 118 can calculate or predict values of other parameters (such as exhaust temperature, mass flow rate at various stations of the engine 114, remaining stall margin, etc.). Additionally, in some embodiments, the computing device 118 can receive sensor data from one or more vehicle sensors 212 located on the aircraft 110. The sensor output received from the one or more vehicle sensors 212 can be received as part of the vehicle data transmitted from the vehicle interface unit 122 to the computing device 118 (e.g., via the data communication link 124( Figure 1 ))). Additionally, engine data including sensed and calculated values of certain engine parameters can be transmitted to the vehicle interface unit 122 and ultimately to one or more vehicle systems 160. For example, engine data indicating the thrust output of the engine 114 can be displayed on a display device located within the cockpit 116.

[0143] At (416), the method (400) includes recording engine operation data. For example, when executed by the computing device 118, the reporting software 590 can record the parameter values of one or more parameters in the generated parameter report list 580 based at least in part on the sensor data received when the aircraft 110 performs a mission (e.g., a flight mission). For example, the sensed, calculated, and / or predicted parameter values of engine and / or aircraft parameters including the baseline parameters 525 and the selected parameters 516 can be recorded and compiled into as Figure 11The query response file 530 shown. The computing device 118, particularly one or more processors of the computing device 118 that execute the instructions of the reporting software 590, may write to the query response file 530 continuously or in a rolling manner when recording data or at a predetermined interval (e.g., every 15 milliseconds, every 25 milliseconds, or per second). The parameter values 536 of the selected parameters 516 may be recorded by the computing device 118 within their respective recording windows 518 and at their respective data sampling rates 520 specified in the data query 508. Similarly, the parameter values 538 of the baseline parameters 525 may be recorded by the computing device 118 at their respective data sampling rates specified in the reporting software 590( Figure 13 ). The parameter values 536, 538 may be sensed, computed, and / or predicted values based on, for example, the sensor data received at (414).

[0144] As Figure 11 best shown, the query response file 530 includes a header 532 and a payload 534. The header 532 includes data (e.g., metadata) indicating but not limited to cryptographic information, timestamps, user-modifiable files 510 for specifying the parameters to be recorded, and / or the version or release number of the received data query 508, checksum information, communication logs, error logs, etc., and other information. The payload 534 of the query response file 530 includes the recorded values of the parameters listed in the generated parameter report list 580, including the recorded selected parameter values 536 associated with the selected parameters 516 and the recorded baseline parameter values 538 associated with the baseline parameters 525. For example, the query response file 530 may be a binary machine-readable file.

[0145] In some embodiments, one or more processors of the computing system 115 are configured to record data in response to a data query 508 during in-flight or the current operating cycle of the engine 114, using the generated parameter report list 580 and the received sensor data. In other words, the parameter values of the selected parameters may be recorded by the computing device 118 that executes the reporting software 580 within the target time period or conditions when the received data query 508 is received. The data query 508 may be received when the aircraft 110 is in the air, on the ground, near an airport, over the ocean, etc. In this way, the selected parameters of interest may be communicated to the FADEC system during the operation of the engine 114, and the parameter values of the selected FADEC parameters may be recorded in real time or near real time in response to the received transmitted data query 508.

[0146] When one or more processors (e.g., of one or more computing devices) determine that a user-modifiable file 510 has been received, method (400) proceeds from (408) to (416). Specifically, method (400) continues to record parameters specified by reporting software 590 executed on at least one of one or more computing devices of computing system 115 without modifying reporting software 590, and then records engine operating data for parameters included, for example, in user-modifiable file 510. The recorded engine operating data, including the recorded selected parameter values 536 and the recorded baseline parameter values 538, are compiled into a query response file 530. When one or more processors (e.g., of one or more computing devices) determine that a user-modifiable file 510 has not been received or that a recording window 518 associated with selected parameters 516 has expired or the process for running them, reporting software 590 executed on at least one of one or more computing devices of computing system 115 may record parameter values of baseline parameters 525 for each normal operation. Reporting software 590 may generate or compile a query response file 530 when executed.

[0147] In some embodiments, reporting software 590 may generate or compile a query response file 530 when executed, the query response file 530 including only the recorded selected parameter values of the selected parameters included in user-modifiable file 510 of data query 508. In such embodiments, simultaneously, reporting software 590 may generate a data file including the recorded baseline parameter values of baseline parameters when executed. In this way, the generation of a data file including parameter values of baseline parameters recorded regardless of whether a data query is received and the generation of a query response file including parameter values of specific query parameters may coexist and function simultaneously.

[0148] At (418), method (400) includes transmitting the query response file. For example, query response file 530 may be transmitted or otherwise downloaded from aircraft 110 to remote station 150 using any of the techniques described herein. For example, query response file 530 may be wirelessly transmitted via one or more of communication units 125, 126 to, for example, ground station 150, another aircraft or vehicle, etc. As another example, query response file 530 may be wirelessly transmitted in flight via SATCOM and / or air-to-ground (ATG) techniques. As yet another example, when on the ground or near the ground (i.e., when within the wireless range of a particular wireless network), query response file 530 may be wirelessly transmitted via cellular, Wi-Fi, and / or Bluetooth networks.

[0149] As described above, the payload 514 of the user-modifiable file 510 may include a transmission rate 522 that indicates the frequency at which the query response file 530 or a portion thereof will be transmitted, for example, from the aircraft 110 to the remote station 150. In some embodiments, the transmission rate 522 provided in the data query 508 may set the transmission rate such that the query response file 530 is transmitted after all the recorded parameter values (i.e., the recorded selected parameter values 536, and in some embodiments, the recorded baseline parameter values 538) have been recorded during the recording window 518 (e.g., the global recording window or when the recording window has expired) and compiled into the query response file 530. Advantageously, in such embodiments, the transmission from the aircraft 110 to the remote station 150 is minimized, and thus data usage and transmission costs are minimized.

[0150] In some embodiments, the transmission rate 522 provided in the data query 508 may set the transmission rate such that the query response file 530 is transmitted in parts or as a series of data file packets. As an example, the transmission rate 522 provided in the data query 508 may set the transmission rate such that the query response file 530 is transmitted at a predetermined interval. For example, the query response file 530 may be transmitted every second, every 5 seconds, every 15 seconds, etc. In this way, one or more remote computing devices 156 at the engine monitoring station (e.g., the remote station 150) may analyze the engine operation of the engine 114 in real-time or near real-time using the recorded parameter values 536, 538 associated with the selected parameter 516 and the baseline parameter 525, respectively. As another example, the transmission rate 522 provided in the data query 508 may set the transmission rate such that the query response file 530 is transmitted when a trigger condition (such as a file size threshold) occurs. Parts or data file packets of the query response file 530 may be reconstructed into a complete file by the remote computing device 156, for example. Additionally, if the query response file 530 is encrypted, the query response file 530 may be decrypted by the remote computing device 156. The reconstructed and decrypted query response file 530 may be used by the remote computing device 156 for visualization, analysis, archiving, etc., for example.

[0151] In some cases, it may be desirable to stop recording the parameter values of the selected parameters defined in the user-modifiable file 510 for upload and transmit the recorded selected parameter values to the remote station via the query response file 530 before the recording window associated with the selected parameters expires. In such a case, a second data query may be transmitted to the vehicle 110. The second data query may be received by a computing device (e.g., one or more of the computing devices 118) associated with the engine of the vehicle 110. The second data query may include a user-modifiable file that, when accessed and read, may cause the computing device to stop recording the parameter values of the selected parameters and cause them to be transmitted.

[0152] In addition, in some embodiments, a computing device associated with one or more of the engines 114 is configured to record parameter values of all possible parameters or at least more parameters than baseline parameters. In such an embodiment, an entity may transmit an in-flight or in-operation parameter data query 508 to the vehicle 110, such as an aircraft. The parameter data query 508 may include a user-modifiable file 510 that includes a list of one or more selected parameters 516 for which the recorded parameter values are compiled into a query response file 530 at least partially based on a preselected past time window. The past time window may indicate the time period during which the recorded parameter values of the selected parameters 516 are compiled into the query response file 530. The past time window is a time period that has occurred. Thus, the parameter data query 508 transmitted to the vehicle may be a "look-back" request. This may allow an entity that has discovered unexpected engine behavior to "look back" at the parameter values of the selected parameters 516 recorded during the past time window, which may be selected to correspond to the time period of the unexpected engine behavior, to better understand the condition of the engine during the unexpected behavior.

[0153] Reporting software 590, which may be executed by a computing device (such as computing device 118) associated with one or more of the engines 114, may access the user-modifiable file 510 and may generate a parameter report list 580 using the selected parameters 516. The parameter report list 580 may also include baseline parameters 525, which are parameters for which recorded values are typically maintained regardless of whether a data query is received. Notably, the reporting software 590 and any other engine software are not modified when the selected parameters 516 are added to the parameter report list 580. In this way, among other benefits, a lengthy certification process is not required despite adding new parameters to the parameter report list 580. The parameter values of the parameters in the generated parameter report list 580 recorded during a past time period may be compiled into the query response file 530. The query response file 530 may be transmitted to a remote station 150 for analysis. The remote station 150 or its remote computing device 156 may analyze the recorded selected parameter values 536 associated with the selected parameters 516 and may send additional data queries to the vehicle 110 to further monitor the engine 114 and / or request that other parameter values be recorded for other past time periods.

[0154] The above-described system 500 and method (400) are capable of performing in-flight or in-operation FADEC parameter queries. This can allow an engine monitoring center to query the FADEC system on an aircraft during flight or more generally during operation to obtain data from specified parameters. The recorded parameter values of the specified parameters can then be transmitted to one or more remote stations, for example for analysis. Thus, the system 500 and method (400) provide many advantages. For example, since the reporting software executed by the computing device 118 is not modified, in-flight or in-operation FADEC parameter queries can increase the speed at which the parameter report list can be updated, for example from weeks or months to minutes. Additionally, since data queries can be sent to the aircraft or other vehicle to immediately request the parameter values of selected parameters for a particular engine in the fleet when needed, ground-based analysis and / or engineering teams can optimize operating costs by obtaining real-time or near-real-time data. Furthermore, in-flight or in-operation FADEC parameter queries allow the engine monitoring station to precisely target data requests for a particular engine, time window, and parameter list. Additionally, the aircraft and / or other vehicles in the fleet may remain in service for a longer period or, conversely, may be serviced earlier to avoid possible out-of-station ground aircraft (AOG) events.

[0155] In some embodiments of the system 500 or method (400), it may be desirable to change the parameter settings (e.g., data sampling rate or recording window) of one or more parameters stored in a parameter list fixed within the reporting software. By way of example, Figure 14 A schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list 580 in which one or more parameter settings are changed is provided. The computing device can be one of the computing devices 118, and the vehicle propulsion system can be the engine 114 of the aircraft 110( Figure 1 ). The computing system 115 has one or more memory devices and one or more processors.

[0156] Referring to Figure 14 , one or more processors are configured to receive a user-modifiable file 510 containing data 515, the data 515 including parameter settings 526 associated with respective selected parameters 516. For example, the user-modifiable file 510 can be received from a communication unit (e.g., communication unit 125 or 126; Figure 1 ). The communication unit can receive the user-modifiable file 510 via a data query (e.g., data query 508; Figure 11)Receive the user-modifiable file 510 from the remote station. In this example, the user-modifiable file 510 includes selected parameters 516, and the selected parameters 516 include a first selected parameter S-BP1 and a third selected parameter S-BP3. The user-modifiable file 510 also includes parameter settings 526 associated with the selected parameters 516. For example, a first parameter setting PS1 is associated with the first selected parameter S-BP1, and a third parameter setting PS3 is associated with the third selected parameter S-BP3. The first and third parameter settings PS1, PS3 can represent any suitable parameter settings, such as a data sampling rate or a recording window.

[0157] One or more processors of the computing device 118 are configured to access and read the user-modifiable file 510 by executing reporting software 590 on at least one of the one or more processors (e.g., of the computing device 118). Once the user-modifiable file 510 is accessed and read, one or more processors of the computing device 118 are configured to link or map the parameter settings 526 of the user-modifiable file 510 to the parameters of the parameter list 585. That is, each parameter setting associated with the selected parameters of the user-modifiable file 510 is linked or mapped to the parameters of the parameter list 585. Each baseline parameter 525 of the master parameter list 585 has one or more associated default or current parameter settings 588. In Figure 14 the depicted example, the first selected parameter S-BP1 of the user-modifiable file 510 corresponds to a first baseline parameter BP1 having an associated default or current first parameter setting DPS1. The third selected parameter S-BP3 of the user-modifiable file 510 corresponds to a third baseline parameter BP3 having an associated default or current third parameter setting DPS3. Thus, the first selected parameter S-BP1 of the user-modifiable file 510 is mapped to the first baseline parameter BP1 of the parameter list 585, and thus, the first parameter setting PS1 is mapped to the first baseline parameter BP1 of the parameter list 585. Similarly, the third selected parameter S-BP3 of the user-modifiable file 510 is mapped to the third baseline parameter BP3 of the parameter list 585, and thus, the third parameter setting PS3 is mapped to the third baseline parameter BP3 of the parameter list 585.

[0158] One or more processors are configured to generate a parameter report list 580 by executing reporting software 590 on at least one of the one or more processors (e.g., of the computing device 118), and the parameter report list 580 contains the parameters and their associated parameter settings mapped thereto. It is noted that the reporting software 590 is not modified during mapping and generation. In other words, the reporting software 590 is not modified when executed to map the parameter settings 526 to the parameters within the parameter list 585, and is not modified when generating the parameter report list 580. ForFigure 14 In the example shown, the parameter report list 580 is generated by the executed reporting software 590 such that the first baseline parameter BP1 has a first parameter setting PS1 (instead of the first default parameter setting DPS1), and such that the third baseline parameter BP3 has a third parameter setting PS3 (instead of the third default parameter setting DPS3). As shown, the parameter settings 526 of the second baseline parameter BP2 and all other parameters within the parameter report list 580 remain unchanged.

[0159] After generating the parameter report list 580, one or more processors are configured to receive sensor data from one or more sensors (e.g., engine sensors, vehicle sensors, etc.). Additionally, one or more processors are configured to record the parameter values of the parameters 525 (and in some cases, the selected parameters 516) in the generated parameter report list 580 based at least in part on the received sensor data and their respective parameter settings 526 (including the parameter settings mapped to their respective parameters 525 (e.g., PS1 and PS3)).

[0160] One or more processors may generate a query response file 530 ( Figure 11 ) by executing the reporting software 590, the query response file 530 including the parameter values recorded for one or more parameters in the generated parameter report list 580. One or more processors may also route the query response file 530 to, for example, a communication unit. In particular, one or more processors may cause a communication unit (e.g., Figure 1 communication unit 125) to transmit at least a portion of the data query file 530 to a remote station (e.g., Figure 1 remote station 150). For example, the remote station may be a ground station or a second vehicle. The data query file 530 may be transmitted to the remote station during the same flight or engine operation cycle in which the initial data query was received.

[0161] While various embodiments have been described herein in which the parameter list 585 differentiates between baseline and non-baseline parameters, in some implementations of the system 500 and method (400), the parameter list 585 does not differentiate between baseline and non-baseline parameters. In such embodiments, all possible parameters of the parameter list 585 may be selected and specified to be included in the generated parameter report list 580.

[0162] As an example, Figure 15 a schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list is provided. For this embodiment, the computing device may be the computing device 118 and the vehicle propulsion system may be the vehicle 110 ( Figure 1) the engine 114. The computing system 115 has one or more memory devices and one or more processors configured to receive a user-modifiable file 510 containing data 515 that indicates one or more selected parameters 516 to be recorded, for example, during operation of the propulsion system. In some embodiments, the data 515 of the user-modifiable file 510 (received as part of the data query 508; Figure 11 ) indicates one or more selected parameters 516 to be recorded by representing each of the one or more selected parameters with a memory address or an address structure. In particular, the memory addresses representing the one or more selected parameters 516 to be recorded may each indicate a memory location on one or more memory devices of the computing system 115 (e.g., a memory location on one or more memory devices of the computing device 118) where the one or more selected parameters 516 are stored. In other embodiments, the data 515 of the user-modifiable file 510 may indicate the one or more selected parameters 516 to be recorded by other designations (e.g., by a parameter name defined in a report or control software, by a part of a parameter name defined in a report or control software, by a specific nomenclature or code defined in a report or control software, by a parameter position in a parameter list, etc.).

[0163] The one or more processors are also configured to generate a parameter report list 580 containing the one or more selected parameters 516 by executing reporting software 590 on at least one of the one or more processors without modifying the reporting software 590. In some embodiments, when generating the parameter report list 580 by executing the reporting software 590 on at least one of the one or more processors, the one or more processors are configured to read the user-modifiable file 510 containing the data 515 that indicates the one or more selected parameters 516 to be recorded. For example, one or more processors of the computing device 118 may access and read the user-modifiable file 510 stored in one or more memory devices 146 of the computing device of the computing system 115, for example. In some embodiments, the one or more memory devices 146 are components of the computing device 118. In other embodiments, the one or more memory devices 146 are components of some other computing device on the aircraft 110. The received user-modifiable file 510 may be stored in a dedicated memory location. For Figure 15 the illustrated embodiment, the selected parameters 516 included in the data 515 of the user-modifiable file 510 include a first selected parameter S-P1, a second selected parameter S-P2, and a third selected parameter S-P3.

[0164] After reading the user-modifiable file 510, when generating the parameter report list 580, one or more processors are configured to map one or more selected parameters 516 to the optional parameters 582 of the parameter list 585 fixed within the reporting software 590. For Figure 15 In an embodiment, the parameter list 585 includes a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, and so on up to an Nth optional parameter SPN. As depicted, one or more processors map the selected parameters 516 (the first selected parameter S-P1, the second selected parameter S-P2, and the third selected parameter S-P3 in this example) to their respective optional parameters 582 of the parameter list 585 (the first optional parameter SP1, the second optional parameter SP2, and the third optional parameter SP3 in this example). Thus, the optional parameters 582 of the parameter list 585 mapped to one or more selected parameters 516 are designated to be included in the parameter report list 580.

[0165] In some implementations, the data 515 of the user-modifiable file 510 includes one or more parameter settings associated with one or more selected parameters 516. As an example, one or more parameter settings associated with one or more selected parameters include a data sampling rate that indicates the rate at which parameter values of one or more selected parameters are recorded. As another example, one or more parameter settings associated with one or more selected parameters include a recording window that indicates when parameter values of one or more selected parameters are recorded. The parameter settings can be linked to their associated optional parameters 582 and included in the parameter report list 580.

[0166] Once the parameter report list 580 is generated, one or more processors are further configured to receive sensor data from one or more sensors (e.g., engine sensors, aircraft sensors, etc.). Additionally, one or more processors are configured to record the parameter values of one or more selected parameters 516 in the generated parameter report list 580 based at least in part on the received sensor data. One or more processors can generate a query response file by executing the reporting software 590, the query response file including the parameter values recorded for one or more selected parameters in the generated parameter report list 580. One or more processors can also provide the query response file. For example, one or more processors can cause a communication unit (e.g., Figure 1 the communication unit 125 of Figure 1 to communicate at least a portion of the query response file to a remote station (e.g.,

[0167] FADEC Selectable Parameters Reported in Response to Target Operating Conditions

[0168] Many aircraft or vehicle engine problems occur only in a subset of the engine group. In some cases, it may be difficult to identify each engine in a fleet that experiences abnormal or unexpected behavior in response to an in-field event or a specific operating condition. For example, it may be difficult to identify each engine in a fleet that may be subject to certain in-field events such as high ground temperatures, increased volcanic ash levels, increased dust or sand levels, or takeoff at high altitude. It may also be difficult to identify each engine in a fleet that experiences unexpected behavior in response to certain operating conditions such as when the exhaust gas temperature reaches a threshold within a predefined range. Additionally, it may be difficult to identify each engine in a fleet that experiences problems during an operation or flight phase such as during engine start-up, the climb phase of a flight, or a step climb.

[0169] In some cases, recording only the FADEC baseline parameters may not be sufficient to correctly observe and analyze abnormal or unexpected engine operation. Thus, in such cases, it may be desirable to record selected non-baseline FADEC parameters in addition to the baseline parameters. In particular, when a specific target condition is met, it may be desirable to record selected non-baseline FADEC parameters. As will be described more fully below, systems, methods, aircraft, engines, controllers, devices, and non-transitory computer-readable media for recording and communicating engine data are provided herein that allow entities (e.g., airframe manufacturers, airlines, engine manufacturers, etc.) to upload or transmit a user-modifiable file that includes a set of target conditions and selected parameters for each aircraft or vehicle in a fleet or a designated subset thereof. A computing device may monitor the operating conditions of an engine and / or an aircraft on which the engine is installed, and when the target condition is met, the computing device may record parameter values associated with one or more selected FADEC parameters. When the target condition is no longer met, the computing device may stop recording the parameter values associated with the selected parameters. By allowing the computing device to self-identify the target conditions, data usage is minimized while maintaining the ability to quickly identify the correct subset of aircraft engines that are subject to in-field events or operating conditions that result in abnormal or unexpected behavior.

[0170] Now generally referring to Figure 1 、 16 、17, 18, and 19, example ways in which a computing device associated with an engine may self-select parameters to record in response to meeting one or more target conditions will now be provided. Figure 16 A flowchart of an example method (600) for monitoring an engine and communicating engine data is provided. For example, the engine may be Figure 1One or more of the engines 114 of the aircraft 110. It should be understood that the exemplary method (600) can be modified, adapted, extended, rearranged, and / or omitted in various ways without departing from the scope of the present subject matter. Figure 17 A schematic diagram of a system 700 configured to implement the method (600) is provided. Figure 18 A schematic block diagram depicting a user-modifiable file of data communications stored in one or more memory devices of a vehicle's computing system is provided. Figure 19 A schematic diagram of a computing device associated with an engine of a vehicle that generates a list of parameter reports is provided.

[0171] At (602), the method (600) includes generating, by one or more remote computing devices, a data communication that includes a user-modifiable file that includes one or more target conditions and one or more selected parameters to be recorded when one, some, or all of the one or more target conditions are met. For example, as Figure 17 shown, one or more remote computing devices 156 of the remote station 150 can generate a data communication 708 that includes a user-modifiable file 710. In some embodiments, as will be explained herein, when a target condition is met, the computing device 118 records only the parameter values associated with the selected parameters of the data communication; thus, the pressure on processing resources and data usage can be minimized.

[0172] The user-modifiable file 710 of the data communication 708 can include a header 712 and a payload 714. The header 712 includes data (e.g., metadata) indicating, but not limited to, cryptographic information, a timestamp, a version or release number of the data communication 708, checksum information, and other useful information. The payload 714 of the user-modifiable file 710 includes data 715( Figure 18 ). The data 715 of the payload 714 can include target conditions 716 and one or more selected parameters 718 to be recorded when one, some, or all of the target conditions 716 are met.

[0173] The target condition 716 can be any condition, constraint, and / or setting for which it is desired to record certain FADEC parameters (e.g., one or more selected parameters 718). The target condition 716 can be an algorithm that sets forth a set of rules, settings, and / or conditions that, when met, trigger the computing device 118 to record the value of the selected parameter 718. For example, the target condition algorithm can be executed by reporting software on one or more processors or logic units of the computing device. Example target conditions 716 are provided below.

[0174] In some embodiments, the target condition 716 can include a defined geographic region. As an example, the defined geographic region can be defined as the area within five hundred (500) kilometers (≈310 miles) of a landmark (e.g., an active volcano). As another example, the defined geographic region can be an area defined by multiple vertices. For example, the defined geographic region can be defined by vertices located at: Bermuda; San Juan, Puerto Rico; and Miami, Florida, USA. In other embodiments, the target condition 716 can be multiple defined geographic regions.

[0175] In some embodiments, the target condition 716 can be a threshold or multiple thresholds. As an example, the threshold can be a predetermined exhaust temperature of the engine 114. As another example, the threshold can be a predetermined altitude. As a further example, for a rotorcraft or other vehicle capable of performing a hover maneuver, the threshold can be a hover time. In some embodiments, the target condition 716 is a pre-defined range. As an example, the pre-defined range can be an altitude range, such as 8,000 - 10,000 meters. As another example, the pre-defined range can be a compressor discharge pressure range. As a further example, the pre-defined range can be an external or ambient temperature range. As another example, the pre-defined range can be a throttle setting range.

[0176] In addition, in some embodiments, the target condition 716 can include a rate of change of a sensed and / or calculated value. As an example, the rate of change of the sensed and / or calculated value can be a fuel rate of change of a burner in one of the engines 114 of the vehicle 110. As another example, the rate of change of the sensed and / or calculated value can be a temperature rate of change at a burner in one of the engines 114.

[0177] In some embodiments, the target condition 716 can be the flight phase of the vehicle to which the engine 114 provides propulsion. As an example, the flight phase can be taxiing from the airport apron to the runway, takeoff, climb, cruise, descent, and / or landing. In some embodiments, the target condition 716 can be the operating mode of the engine. For example, the operating mode can be start, transient, or steady-state operation. In some further embodiments, the target condition 716 can be a set of pre-defined operating conditions of the engine 114 and / or the vehicle 110. For example, the set of pre-defined operating conditions can include a combination of one or more of the example target conditions described herein.

[0178] As described above, the data 715 of the user-modifiable file 710 includes one or more selected parameters 718. The one or more selected parameters 718 of the user-modifiable file 710 are FADEC parameters. For example, when one or more target conditions are met, the computing device 118 will record the parameter value for the FADEC parameter. The selected parameter 718 may be associated with one or more target conditions 716. In this way, when the target condition 716 is met, the parameter value of the selected parameter 718 associated with the met target condition may be recorded by the computing device 118.

[0179] In some embodiments, the selected parameter 718 may be one or more non-baseline parameters, e.g., one or more parameters that are not typically recorded during normal engine operation. In some embodiments, the selected parameter 718 may be any optional FADEC parameter. The selected parameter 718 may be represented or defined on the user-modifiable file 710 in any suitable manner. For example, each selected parameter 718 may be represented or defined by the user-modifiable file 710 as a memory address or location at which the selected parameter 718 is stored on one or more memory devices of the computing system 115 ( Figure 1 ) of the aircraft 110 ( Figure 1 ) or is indexed on the one or more memory devices. In this way, as will be explained below, the selected parameter 718 may be effectively mapped or mapped to an optional parameter of a parameter list stored on one or more memory devices, such as in the computing device 118.

[0180] The data 715 of the user-modifiable file 710 may also include one or more parameter settings associated with the one or more selected parameters 718. For example, as Figure 18 shown, the one or more parameter settings associated with the one or more selected parameters 718 may include one or more data sampling rates 720, which indicate, for example, the rate or frequency at which the computing device 118 of the FADEC system is to record the parameter values of the one or more selected parameters 718. The data sampling rate 720 may be any suitable rate, including, for example, once per second, three times per second, twenty times per second, etc. The data 715 may also include other parameter settings associated with the one or more selected parameters 176.

[0181] For Figure 18In an embodiment, the data 715 of the user-modifiable file 710 includes two target conditions 716, including a first target condition TC1 and a second target condition TC2. The first target condition TC1 can be a set of related conditions or a single condition or constraint. Similarly, the second target condition TC2 can be a set of related conditions or a single condition or constraint. The selected parameters 718 associated with the first target condition TC1 include a first selected parameter S-P1, a second selected parameter S-P2, and a third selected parameter S-P3. The first selected parameter S-P1 has an associated data sampling rate DSR1, the second selected parameter S-P2 has an associated data sampling rate DSR2, and the third selected parameter S-P3 has an associated data sampling rate DSR3. The data sampling rate 720 of the selected parameters 718 associated with the first target condition TC1 can be the same or different for each selected parameter 718. The selected parameters 718 associated with the second target condition TC2 include the first selected parameter S-P1 and a fourth selected parameter S-P4. The first selected parameter S-P1 has an associated data sampling rate DSR1, and the fourth selected parameter S-P4 has an associated data sampling rate DSR4. The data sampling rate 720 of the selected parameters 718 associated with the second target condition TC2 can be the same or different for each selected parameter 718. It should be noted that a selected parameter can be associated with more than one target condition. In this example, the first selected parameter S-P1 is associated with both the first and second target conditions TC1 and TC2. It should be understood that the data 715 of the user-modifiable file 710 can include other parameter settings associated with one or more selected parameters 718, as well as other target conditions and associated selected parameters and settings.

[0182] The data 715 of the user-modifiable file 710 can also include a transmission rate 722, which indicates the frequency or interval at which the recorded data file 730 ( Figure 17 ) will be transmitted, for example, from the aircraft 110 to the remote station 150. The recorded data file 730 can include the recorded selected parameter values 738, and in some embodiments, the recorded baseline parameter values 736. In some embodiments, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transmitted after the target condition is no longer met. In some embodiments, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transmitted after a predetermined time (e.g., five seconds) when the target condition is no longer met. Additionally or alternatively, in other embodiments, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transmitted when a trigger condition (e.g., a file size threshold) occurs.

[0183] In some embodiments, as described above, the data communication 708 that includes the user-modifiable file 710 is generated by one or more remote computing devices 156. The user-modifiable file 710 includes target conditions 716, selected parameters 718, and associated parameter settings. For example, in some example embodiments, the remote station 150 can be an engine monitoring station. The engine monitoring station can be located on the ground or on another vehicle. The engine monitoring station can monitor the engines of a fleet of aircraft (e.g., a fleet of aircraft 110 including Figure 1 engines 114 of the aircraft 110). The data communication 708 that includes the user-modifiable file 710 can be generated in response to an on-site event or the detection of abnormal or unexpected behavior of one or more engines of the fleet. The parameters included in the user-modifiable file 710 can be selected based on the reported on-site events. However, it should be understood that the parameters included in the user-modifiable file 710 can be selected based on any suitable criteria and / or for any reason.

[0184] For example, a computing device associated with the engines of the fleet can generate a fault communication in response to unexpected behavior, and the fault communication can indicate the type of fault or problem experienced by the engine. The received fault communication can be routed to one or more remote computing devices 156 for processing and data analysis. At least in part based on the received fault communication, one or more remote computing devices 156 can select or define the target conditions 716, the selected parameters 718 and their associated parameter settings, and the transmission rate 722, and can accordingly generate the data communication 708 that includes the user-modifiable file 710. In some embodiments, the target conditions 716, the selected parameters 718 and their associated parameter settings, and the transmission rate 722 can be defined in the user-modifiable file 710 for other suitable reasons (e.g., to study or investigate the health of one or more components of the engine 114).

[0185] At (604), the method (600) includes transmitting / receiving a data communication that includes a user-modifiable file. The data communication 708 that is generated and includes the user-modifiable file 710 can be transmitted to the aircraft 110 in any suitable manner (e.g., by any one of the transmission techniques described herein). For example, when the aircraft 110 is in the air, near an airport, parked at an airport, or over the ocean, the data communication 708 can be transmitted to the aircraft 110. As an example, the transceiver 154 of the remote station 150 can transmit the data communication 708 to the aircraft 110. As Figure 17 shown, one or more of the communication units 125, 126 can receive the data communication 708 from one or more transceivers 154 of the remote station 150. In some cases, the aircraft 110 can receive the data communication 708 when the engine 114 is not operating.

[0186] In some embodiments, data communication 708 is encrypted and one or more of communication units 125, 126 may decrypt the received data communication 708. The decrypted data communication 708 may then be routed to computing device 118 of the FADEC system or some other computing device on aircraft 110. Thus, computing device 118 and / or some other computing device on aircraft 110 may receive the generated data communication 708. In some embodiments, data communication 708 is decrypted by computing device 118 or by some other intermediate computing device rather than communication units 125, 126.

[0187] In addition, in some embodiments, data communication 708 may be transmitted to and received by each engine and / or aircraft in a fleet. In other embodiments, data communication 708 may be transmitted to and received by a specified number of engines and / or aircraft in a fleet. One advantage of pushing data communication 708 to all or a portion of the aircraft in a fleet is that no specific knowledge is required regarding whether a particular engine or aircraft in the fleet is experiencing or will suffer from an abnormal or unexpected engine operation.

[0188] At (606), method (600) includes storing a user-modifiable file of the received data communication in one or more memory devices of a computing system of a vehicle. For example, Figure 18 A schematic block diagram is provided depicting a user-modifiable file 710 stored in one or more memory devices 146 of computing system 115 of aircraft 110. In some embodiments, the one or more memory devices 146 storing user-modifiable file 710 may be one or more memory devices of one or more computing devices 118. Thus, user-modifiable file 710 may be routed to one or more of computing devices 118. Computing device 118 may receive user-modifiable file 710 and store user-modifiable file 710 in, for example, one or more of its memory devices.

[0189] In other embodiments, a user-modifiable file 710 of data communication 708 may be routed to and stored in one or more computing devices on aircraft 110 other than computing device 118. As an example, the user-modifiable file 710 may be routed to and received and stored by one or more computing devices located within avionics bay 120. In other embodiments, the user-modifiable file 710 may be routed to and received and stored on one or more memory devices of communication units 125, 126. Additionally, in some embodiments, the memory location storing the user-modifiable file 710 is a dedicated memory location configured to store only the user-modifiable file 710. In this way, the content of the user-modifiable file 710 may be more easily found, accessed, and read, for example, by the engine reporting software executed by computing device 118.

[0190] At (608), method (600) may include performing a compatibility check on the content of the data communication, and more specifically, on the content of the user-modifiable file of the data communication. For example, once the user-modifiable file 710 is transmitted and received at (604) and then stored at (606), computing device 118 and / or other computing devices of aircraft 110 may determine the integrity of the content of the user-modifiable file 710, and / or the compatibility of the content of the user-modifiable file 710 with the hardware, software, firmware, etc. of computing device 118 and / or other computing devices of aircraft 110. In one aspect of performing the compatibility check at (608), the computing device and / or computing device 118 may determine whether the user-modifiable file 710 has been successfully uploaded or transmitted to aircraft 110 by performing one or more data integrity operations (such as cyclic redundancy check, checksum check, cryptographic check, and digital signature, etc.). In some embodiments, if the user-modifiable file 710 fails the data integrity operation, the user-modifiable file 710 may be ignored. On the other hand, if the user-modifiable file 710 passes the data integrity operation, the computing device and / or computing device 118 may proceed to (610).

[0191] At (610), method (600) includes specifying parameters to be recorded without modifying reporting software by reporting software executed on at least one of one or more computing devices (e.g., computing device 118) of an aircraft, where the parameters to be recorded include one or more selected parameters of a user-modifiable file included in the received data communication. In some embodiments, specifying the parameters to be recorded includes generating a parameter report list, where parameters on the parameter report list specify, when associated target conditions are met, parameters to be recorded by, for example, computing device 118. The parameter report list can include or contain one or more selected parameters noted in user-modifiable file 710 and, in some embodiments, one or more baseline parameters 725. For example, one or more of computing devices 118 can generate or modify parameter report list 780 that includes one or more selected parameters 718 received as part of user-modifiable file 710 and one or more baseline parameters 725. That is, for example when target condition 716 is met, computing device 118 can generate a list of parameters to be recorded by computing device 118. A plurality of baseline parameters 725 can be fixed within the reporting software of the FADEC system. Additionally, as previously mentioned, as used herein and in the appended claims, generating a file means creating a new file or modifying or updating an existing file. Thus, in some embodiments, computing device 118 can create a new parameter record list that includes baseline parameters 725 and selected parameters 718. In other embodiments, computing device 118 can modify or update an existing parameter list that includes baseline parameters 725 and selected parameters 718.

[0192] Figure 19 A schematic block diagram of one computing device 118 that generates parameter report list 780 is provided. As shown, reporting software 790 (e.g., engine reporting software in this embodiment) can be executed by one or more processing devices of computing device 118. In particular, reporting software 790 includes instructions that, when executed by one or more processors, cause one or more processing devices of computing device 118 to generate parameter report list 780. Additionally, as will be explained below, for example during engine operation and when target condition 716 is met, reporting software 790 includes instructions that, when executed, cause one or more processing devices of computing device 118 to record values associated with the parameters in parameter report list 780.

[0193] As Figure 19As shown, the computing device 118 includes a parameter list 785 that includes parameters that the computing device 118 can record. The parameter list 785 or the master parameter list can be stored on one or more memory devices of the computing device 118. The parameter list 785 can contain any suitable number of parameters. For this embodiment, the parameter list 785 includes a baseline parameter 725 and an optional parameter 729, and the optional parameter 729 can be a non-baseline parameter. In some embodiments, such as during engine operation, the baseline parameter 725 is always recorded by the computing device 118, and the optional non-baseline parameter 729 is generally not recorded by the computing device 118 unless the computing device 118 is otherwise instructed to do so. In some embodiments, the parameter list 785 is fixed within a reporting software 790 executable by one or more processors of the computing device 118 and can only be modified by changing the source code of the reporting software 790. For Figure 19 the embodiment, the baseline parameter 725 includes a first baseline parameter BP1, a second baseline parameter BP2, a third baseline parameter BP3, and so on up to an Nth baseline parameter BPN. The optional non-baseline parameter 729 includes a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, and so on up to an Nth optional parameter SPN.

[0194] To generate the parameter report list 780, the reporting software 790 accesses and reads a user-modifiable file 710 when executed. In particular, the reporting software 790 first accesses the user-modifiable file 710 stored on one or more memory devices 146 of the computing system 115. Once accessed, the reporting software 790 reads the selected parameters 718 contained within the user-modifiable file 710 when executed. In some embodiments, the reporting software 790 can access and read but not write to the user-modifiable file 710. This can prevent inadvertent modification of the user-modifiable file 710. As described above, the selected parameters 718 can be represented or defined in any suitable manner (e.g., by a memory address indicating the location where the optional parameter 729 is indexed on the computing system 115). For Figure 19 the embodiment, the selected parameters 718 contained within the user-modifiable file 710 include a first selected parameter S-P1, a second selected parameter S-P2, and a third selected parameter S-P3.

[0195] Once the reporting software 790 accesses and reads the user-modifiable file 710, the reporting software 790 maps the selected parameters 718 contained within the user-modifiable file 710 to the optional non-baseline parameters 729 when executed. In Figure 19In an example embodiment, a first selected parameter S-P1 corresponds to a first optional parameter SP1, a second selected parameter S-P2 corresponds to a second optional parameter SP2, and a third selected parameter S-P3 corresponds to a third optional parameter SP3. For example, the first selected parameter S-P1 may represent a memory location on the computing device 118 where the first optional parameter SP1 is stored, the second selected parameter S-P2 may represent a memory location on the computing device 118 where the second optional parameter SP2 is stored, and the third selected parameter S-P3 may represent a memory location on the computing device 118 where the third optional parameter SP3 is stored. Thus, when executed, the reporting software 790 maps the first selected parameter S-P1 to the first optional parameter SP1, the second selected parameter S-P2 to the second optional parameter SP2, and the third selected parameter S-P3 to the third optional parameter SP3. The mapped parameters are specified by the reporting software 790 to be included on the reporting parameter list 780.

[0196] For example, in Figure 19 the mapped first optional parameter SPl, second optional parameter SP2, and third optional parameter SP3 are specified to be included in the generated or modified parameter report list 780. As a result, the generated or modified parameter report list 780 includes baseline parameters 725 and selected parameters 718, where the baseline parameters 725 include BP1, BP2, BP3, up to the Nth or BPN baseline parameter, and the selected parameters 718 include SP1, SP2, and SP3. In the case where a selected parameter 718 included in the user modifiable file 710 cannot be mapped to an optional non-baseline parameter 729, the selected parameter 718 included in the user modifiable file 710 may be ignored by the reporting software 790. Additionally, an error notification may be generated, for example, by executing the reporting software 790, and the error notification may be provided to the user, and the error notification may indicate that one or more of the selected parameters 718 of the user modifiable file 710 included in the data communication 708 cannot be mapped to any of the optional parameters 729 of the parameter list 785.

[0197] Furthermore, when generating the parameter report list 780, one or more parameter settings associated with the selected parameters may be included in the generated or modified parameter report list 780. As an example, the data sampling rate or frequency at which the value of the selected parameter is to be recorded may be linked to the selected parameter in the generated or modified parameter report list 780. It should be understood that other parameter settings may be linked to the selected parameters 718 in the generated or modified parameter report list 780.

[0198] It should be noted that when generating the parameter report list 780, the reporting software 790 and any other engine software are not changed, altered, or otherwise modified. That is, when executed, the reporting software 790 can read the selected parameters 718 from the uploaded user-modifiable file 710, map the selected parameters 718 to the optional parameters 729 of the parameter list 785, and specify the mapped parameters to be included in the parameter report list 780 together with the baseline parameters 725, without changing, altering, or otherwise modifying the reporting software 790 or any other engine software. In this way, among other benefits, parameters can be added and / or removed from the parameter report list 780 without the need for a lengthy software code certification process.

[0199] In some embodiments, particularly where the user-modifiable file 710 includes multiple sets of target conditions and associated selected parameters, such as Figure 19 in the case of the embodiment of Figure 19 multiple parameter report lists can be generated. For example, in Figure 18 the parameter report list 780 is shown to be generated using the selected parameters 718 associated with the first target condition TC1. The parameter report list generated using the selected parameters 718 associated with the first target condition TC1 is denoted as 780-TC1. The same process described above can be used to generate a parameter report list for the selected parameters 718 associated with the second target condition TC2. For example, the selected parameters 718 associated with the second target condition TC2 can be Figure 18 those depicted in

[0200] and described above. The parameter report list generated using the selected parameters 718 associated with the second target condition TC2 is denoted as 780-TC2. Thus, one or more memory devices of the computing device 118 can store multiple generated parameter report lists. As will be further explained below, parameter values can be recorded for one or more of the parameters in the parameter report list depending on whether the target condition associated with the parameter report list is met. In some embodiments, when the target condition is not met, the computing device 118 can record the parameter values of the baseline parameters 725 of the parameter list 785.

[0200] At (612), the method (600) includes receiving sensor data from one or more sensors. For example, as Figure 17As shown, the computing device 118 can receive sensor data from one or more engine sensors 210. One or more sensors 210 can sense or measure values of parameters related to the engine 114 (such as fan speed, core speed, temperature at various stations along the core air flow path, etc.). Signals from the sensors 210 can be routed to and processed by the computing device 118. Then, the computing device 118 can calculate or predict values of other parameters (such as exhaust temperature, mass flow rate at various stations of the engine 114, remaining stall margin, etc.). Additionally, in some embodiments, the computing device 118 can receive sensor data from one or more vehicle sensors 212 positioned on the aircraft 110. The sensor output received from the one or more vehicle sensors 212 can be received as part of the vehicle data transmitted from the vehicle interface unit 122 to the computing device 118 (e.g., via the data communication link 124( Figure 1 ))). Additionally, engine data including sensed and calculated values of certain engine parameters can be transmitted to the vehicle interface unit 122 and ultimately to one or more vehicle systems 160. For example, engine data indicating the thrust output of the engine 114 can be displayed on a display device located within the cockpit 116.

[0201] At (614), the method (600) includes determining whether a target condition is met based at least in part on the received sensor data. For example, the computing device 118 can use the received sensor data to determine whether the target condition 716 is met. The computing device 118 can use sensed and / or calculated values to determine whether the target condition 716 is met. The sensor data can be received from one or more engine sensors 210 and / or one or more vehicle or aircraft sensors 212 as described above.

[0202] As an example, as described above, the target condition can be a defined geographic region. In such an embodiment, the computing device 118 can receive carrier data indicative of the geographic location of the aircraft 110 and thus the geographic location of the engine 114 mounted to the aircraft 110. For example, one of the carrier systems 160 can include a navigation system equipped with GPS. The GPS can provide the computing device 118 with aircraft position information, such as coordinates. The computing device 118 can determine whether the aircraft 110 and its associated engine 114 are within the defined geographic region. In this example, when the aircraft 110 and thus the engine 114 are operating within the defined geographic region, the computing device 118 determines that the target condition 716 is satisfied. As will be explained below at (616), when the target condition 716 is satisfied, in this example when the aircraft 110 and the engine 114 are operating within the defined geographic region, the computing device 118 is configured to record the parameter values of one or more selected parameters 716 compiled in the parameter report list 780. When the aircraft 110 and the engine 114 are not operating within the defined geographic region, the computing device 118 determines that the target condition 716 is not satisfied. Accordingly, the computing device 118 does not record the parameter values of one or more selected parameters 716. In some embodiments, when the target condition 716 is not satisfied, the computing device 118 can record the parameter values of the baseline parameters 725 within the parameter list 785.

[0203] As another example, the target condition can be a threshold. In such an embodiment, when determining at (614) whether the target condition is satisfied at least in part based on the received sensor data, the computing device 118 is configured to determine whether the threshold is exceeded at least in part based on the received sensor data. For example, one or more sensor outputs received from the engine sensors 210 and / or the aircraft sensors 212 can be used by the computing device 118 to determine whether the threshold is exceeded. The sensor outputs can be used directly and / or values can be calculated and / or predicted based on the sensor outputs. To determine whether the threshold is exceeded, the computing device 118 can compare the sensed / calculated / predicted value based on one or more sensor outputs with the threshold. For example, the computing device 118 can compare the calculated exhaust temperature of the engine 114 with an exhaust temperature threshold. In this example, when the threshold is exceeded, the computing device 118 determines that the target condition 716 is satisfied, and accordingly the computing device 118 is configured to record the parameter values of one or more selected parameters 718. When the threshold is not exceeded, the computing device 118 determines that the target condition 716 is not satisfied, and accordingly the computing device 118 is configured not to record the parameter values of one or more selected parameters 718. As used herein, the term "exceeded" in the context of a threshold can mean a value greater than the threshold or a value less than the threshold.

[0204] As yet another example, the target condition can be a pre-defined range. In such an embodiment, when determining whether the target condition is met at (614) based at least in part on one or more sensor outputs, the computing device 118 is configured to determine whether the sensed / computed / predicted value is within the pre-defined range. The sensed / computed / predicted value can be based on the received sensor data. For example, one or more sensor outputs received from the engine sensors 210 and / or the aircraft sensors 212 can be used by the computing device 118 to determine whether the sensed / computed / predicted value is within the pre-defined range. The sensor output can be used directly and / or a value can be computed or predicted based on the sensor output. For example, as one example, to determine whether the target condition is met, the computing device 118 can compare the sensed / computed / predicted compressor discharge pressure to a pre-defined pressure range. When the sensed / computed / predicted value is within the pre-defined range, the computing device 118 determines that the target condition 716 is met, and thus the computing device 118 is configured to record the parameter values of one or more selected parameters 718. When the parameter value is not within the pre-defined range, the computing device 118 determines that the target condition 716 is not met, and thus the computing device 118 is configured not to record the parameter values of one or more selected parameters 718. In some embodiments, the pre-defined range can be a discontinuous pre-defined range.

[0205] As another example, the target condition can be the rate of change of a set / sensed / computed / predicted value. In such an embodiment, when determining whether the target condition is met at (614) based at least in part on the received sensor data, the computing device 118 is configured to determine whether the rate of change of the sensed / computed / predicted value has exceeded a pre-defined rate of change. For example, if the sensed / computed / predicted rate of change of the fuel to the burner of the engine 114 exceeds the pre-defined rate of change of the fuel to the burner, the computing device 118 can determine that the rate of change of the fuel to the burner exceeds the pre-defined rate of change of the fuel to the burner. When the rate of change of the sensed / computed / predicted value has exceeded the pre-defined rate of change, the computing device 118 determines that the target condition 716 is met, and the computing device 118 is configured to record the values of one or more selected parameters 718. When the rate of change of the sensed / computed / predicted value has not exceeded the pre-defined rate of change, the computing device 118 determines that the target condition 716 is not met, and thus the computing device 118 is configured not to record one or more selected parameters 718. As used herein, "exceeds" in the context of a rate of change can mean a rate having a greater rate of change than the pre-defined rate or a rate having a slower rate of change than the pre-defined rate.

[0206] At (616), method (600) includes recording parameter values of parameters of a generated parameter report list when a target condition is met. For example, when it is determined at (614) by computing device 118 that target condition 716 is met, reporting software 790, when executed by computing device 118, can record parameter values of one or more parameters in generated parameter report list 780 at least in part based on the received sensor data. For example, sensed, computed, and / or predicted parameter values of engine and / or aircraft parameters (including parameter values of baseline parameter 725 and selected parameter 718) can be recorded and compiled into a recorded data file 730 as shown in Figure 17 . Computing device 118, in particular one or more processors of computing device 118 that execute instructions of reporting software 790, can continuously or rollingly write sensed, computed, and / or predicted parameter values to the recorded data file 730 as the data is recorded or at a predetermined interval (such as every 15 milliseconds, every 25 milliseconds, or per second). Parameter values 738 of selected parameter 718 can be recorded by computing device 118 at their respective data sampling rates 720 specified in data communication 708 ( Figure 18 ). Similarly, parameter values 736 of baseline parameter 725 can be recorded by computing device 118 at their respective data sampling rates specified, for example, in reporting software 790 ( Figure 19 ). The recorded parameter values 738, 736 can be sensed, computed, and / or predicted values based on the received sensor data. Reporting software 790, when executed by one or more processors of computing device 118, can generate or compile a recorded data file 730 that includes the recorded parameter values 736, 738.

[0207] As Figure 17 best shown, the recorded data file 730 includes a header 732 and a payload 734. The header 732 includes data (such as metadata) that identifies or indicates, but is not limited to, cryptographic information, a timestamp, a user-modifiable file 710 for specifying parameters for which parameter values are to be recorded when a defined target condition is met, and / or a version or release number of the received data communication 708, checksum information, a communication log, an error log, and other information. The payload 734 of the recorded data file 730 includes recorded values of parameters listed in generated parameter report list 780, including recorded selected parameter values 738 associated with selected parameter 718 and recorded baseline parameter values 736 associated with baseline parameter 725. For example, the recorded data file 730 can be a binary machine-readable file.

[0208] When it is determined at (614) that the target condition 716 is not met, the computing device 118 is configured not to record the parameter values of one or more selected parameters 718. However, the computing device 118 may continue to record the parameter values associated with the baseline parameter 725. In this way, one or more selected parameters 718 are selectively recorded based on whether the target condition is met, and the baseline parameter 725 is recorded regardless of whether the target condition 716 is met. That is, by executing the reporting software 790, the computing device 118 is configured to record the parameter values of the baseline parameter 725 fixed within the reporting software 790, regardless of whether the target condition 716 is met.

[0209] Advantageously, when the engine 114 does not experience the identified target condition, the computing device 118 does not record additional parameter values of the selected parameters 718, which avoids satellite costs or other expensive data transmission costs (when such data is not needed or not desired for analysis). In this way, when the target condition 718 is not met, a file with the parameter values of the baseline parameter can be generated, and when the target condition 718 is met, a recorded data file 730 containing the parameter values of the selected parameters (and in some embodiments, the parameter values of the baseline parameter) can be generated. In some embodiments, the file with the parameter values of the baseline parameter and the recorded data file 730 can coexist and function simultaneously.

[0210] The computing device 118 may continue to monitor whether the target condition 716 is met. In some embodiments, the reporting software 790, when executed by one or more processors of the computing device 118, may record the parameter values of the selected parameters 718 only when the target condition 716 is met, and may generate or compile a recorded data file 730 containing the recorded selected parameter values 738 (and in some embodiments, the recorded baseline parameter values 736). In some embodiments, the reporting software 790, when executed by one or more processors of the computing device 118, may record the parameter values of the selected parameters 718 within a predetermined recording time after an initial determination that the target condition 716 is met. That is, in such embodiments, if it is determined at (614) that the target condition 716 is met, the reporting software 790, when executed by one or more processors of the computing device 118, may record the parameter values of the selected parameters 718 (and in some embodiments, the baseline parameter) within a predetermined recording time (e.g., five minutes), regardless of whether the target condition 716 is met throughout the predetermined recording time. When the predetermined recording time has passed or expired, the computing device 118 may stop recording the parameter values of the selected parameters 718.

[0211] At (618), method (600) includes providing a recorded data file. For example, the recorded data file 730 can be downloaded or otherwise transferred to other sources in a variety of suitable ways. As an example, the recorded data file 730 can be wirelessly transferred from the aircraft 110 via one or more of the communication units 125, 126 to, for example, a ground station 150, another aircraft, or a vehicle. In some embodiments, the recorded data file 730 can be wirelessly transferred in flight via SATCOM and / or air-to-ground (ATG) technology. As another example, the recorded data file 730 can be wirelessly transferred via a cellular, Wi-Fi, and / or Bluetooth network. In other embodiments, the recorded data file 730 can be transferred via a wired connection to, for example, a portable device 142( Figure 3 ). The portable device 142 can be implemented on, for example, a laptop computer, a tablet computer, a mobile device, or other suitable computing device. Maintenance professionals can use the portable device 142 to retrieve the recorded data file 730. In some embodiments, the recorded data file 730 can be encrypted by a computing device on the aircraft 110. For example, the recorded data file 730 can be encrypted by the computing device 118 and / or one or more of the communication units 125, 126 before being transferred from the aircraft 110.

[0212] In some embodiments, the recorded data file 730 can be transferred to another source according to the transmission rate 722 provided in the data communication 708. As described above, the user-modifiable file 710 of the data transmission 708 can include the transmission rate 722, which indicates the frequency at which the recorded data file 730 or a portion thereof, for example, is to be transferred from the aircraft 110 to the remote station 150. In some embodiments, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transferred immediately after the target condition 716 is no longer met. In some embodiments, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transferred while the target condition 716 is still met.

[0213] In some embodiments, the recorded data file 730 can be transferred as a single file, or it can be parsed and sent in parts or as data packets. For example, in some embodiments, the recorded data file 730 is transferred in parts or as a series of data file packets at a predetermined interval. For example, when the target condition 716 is met and the computing device 118 is actively recording parameter values and compiling them into the recorded data file 730, the recorded data file 730 can be transferred every second, every 5 seconds, every 15 seconds, etc. In this way, one or more remote computing devices 156 of the remote station 150 (e.g., the engine monitoring station) can utilize the recorded parameter values 736, 738 to analyze the engine operation of the engine 114 in real time or near real time. As another example, the transmission rate 722 provided in the data communication 708 can set the transmission rate such that the recorded data file 730 is transferred when a trigger condition such as a file size threshold occurs. Parts of the recorded data file 730 or data file packets can be reconstructed into a complete file by the remote computing device 156, for example. The reconstructed and decrypted recorded data file 730 can be used by the remote computing device 156 for visualization, analysis, archiving, etc., for example.

[0214] In some embodiments, when a trigger or target condition is met, the computing device 118 is configured to generate a notification indicating that the target condition has been met. The notification can be transmitted from the aircraft 110 to, for example, the remote station. For example, one or more of the communication units 125, 126 can be used to transmit the notification to the remote station 150. By receiving a notification of when a particular engine meets a target condition, the specific engine conditions during the time the target condition is met can be analyzed in real time, and if needed, further data communication can be transmitted to the aircraft 110 with instructions for expanding or narrowing the range of parameter values to be recorded.

[0215] For example, in some embodiments, the computing device 118 can receive multiple data communications, each having a target condition and an associated selected parameter for which parameter values will be recorded when the target condition is met. The reporting software 790, when executed by one or more processors of the computing device 118, can generate multiple parameter report lists based on the received data communications in the manner described above, for example. Each of the generated parameter report lists can be stored on one or more memory devices of the computing device 118. When the target condition associated with a parameter report list is met, multiple parameter report lists can be activated at once. The recorded parameter values of the parameters of the activated parameter report lists can be compiled into the same or different recorded data files. When compiled into the same recorded data file, the recorded parameter values can be marked with identification information, for example, identifying its associated target condition and / or its associated data communication.

[0216] For example, Figure 20A schematic diagram depicting a computing device 118 associated with an aircraft engine that receives multiple data communications is provided. Each data communication has a target condition and an associated selected parameter, and when the target condition is met, a parameter value will be recorded for the selected parameter. In particular, for Figure 20 the illustrated embodiment, the computing device 118 receives a first data communication 708A that includes a first set of target conditions 716A and a first selected parameter 718A. When the first set of target conditions 716A is met, the computing device 118 will record the parameter value associated with the first selected parameter 718A. The computing device 118 also receives a second data communication 708B that includes a second set of target conditions 716B and a second selected parameter 718B. When the second set of target conditions 716B is met, the parameter value associated with the second selected parameter 718B will be recorded. The computing device 118 also receives a third data communication 708C that includes a third set of target conditions 716C and a third selected parameter 718C. When the third set of target conditions 716C is met, the parameter value associated with the third selected parameter 718C will be recorded. The first selected parameter 718A, the second selected parameter 718B, and the third selected parameter 718C may include separate or overlapping parameters for which parameter values are to be recorded. The data communications 708A, 708B, 708C may be received simultaneously or at different times. The data communications 708A, 708B, 708C may also include parameter settings associated with their respective selected parameters.

[0217] Report software 790, when executed by one or more processors of the computing device 118, can generate multiple parameter report lists based on the received data communications 708A, 708B, 708C in the manner described above, for example. As Figure 20 shown, a first parameter report list 780A is generated using the target conditions and selected parameters included in a user-modifiable file of the first data communication 708A, a second parameter report list 780B is generated using the target conditions and selected parameters included in a user-modifiable file of the second data communication 708B, and a third parameter report list 780C is generated using the target conditions and selected parameters included in a user-modifiable file of the third data communication 708C. The parameter report lists 780A, 780B, 780C are generated by one or more processors of the computing device 118 that execute the report software 790.

[0218] Each of the generated parameter report lists 780A, 780B, 780C can be stored on one or more memory devices of the computing device 118. One or more of the parameter report lists 780A, 780B, 780C can be activated when their associated target conditions are met. As described above, the parameter values recorded for the parameters of the activated parameter report list can be compiled into the same or different recorded data files. When compiled into the same recorded data file, the recorded parameter values can be tagged with identification information such as that identifying their associated target condition and / or their associated data communication. For example, the reporting software 790 can organize the parameter values in the recorded data file 730 according to their associated target conditions. In this way, the engine operating data can be more easily processed and analyzed.

[0219] When the target condition associated with one of the activated parameter report lists is no longer met or a predetermined reporting time has elapsed, the parameter report list can be deactivated by the reporting software 790 executed on the computing device 118. When the parameter report list becomes deactivated, the computing device 118 no longer records the parameter values of the parameters of the parameter report list.

[0220] Advantageously, by allowing the computing device associated with the engine to self-select which parameter values to record when set target conditions are met, the parameter values can be intelligently and efficiently recorded only by those engines in the fleet that meet the target conditions. Compared to conventional techniques, this provides a significantly faster way to record specific parameters when a fleet of engines meets a target condition and avoids the cost of having the entire fleet continuously report data when only a few engines are experiencing a particular problem. Additionally, using the target condition method, there is no need to know which engines or aircraft need to be monitored or which engines meet the target conditions. The data communication can be pushed or propagated to the entire fleet or a subset thereof, and only those engines that meet the target conditions need to report back the parameter values of the selected parameters. Among other benefits, the cost of satellites or other expensive additional data for engines that do not experience the identified target conditions can be avoided. Additionally, it is noted that the parameter report list for which parameter values are recorded when the target conditions are met can be generated without modifying the reporting software or, more generally, any engine software, which eliminates the need for a lengthy software code re-certification process.

[0221] Since the parameters to be recorded are updated with a sufficiently fast turnaround time, the parameters to be recorded can be modified over periods of days or weeks when the problem is better understood. Multiple iterations of the user-modifiable file can be transferred to the vehicle as needed. The user-modifiable file can be updated while being analyzed and improved outside the engine. A user-modifiable file can be generated to include any number of selected parameters chosen from a defined set of FADEC parameters (about 10,000 in total). Once the user-modifiable file and the selected parameters to be recorded are no longer needed, they can be phased out.

[0222] In some embodiments of the system 700 or method (600), when certain target conditions are met, it may be desirable to change the parameter settings (e.g., data sampling rate) of one or more parameters stored in a parameter list fixed within the reporting software. By way of example, Figure 21 A schematic illustration of a computing device of a vehicle propulsion system that generates a parameter report list 780 in which one or more parameter settings are changed is provided. The computing device can be the computing device 118 and the vehicle propulsion system can be the engine 114 of the aircraft 110 ( Figure 1 ). The computing system 115 has one or more memory devices and one or more processors.

[0223] Reference Figure 21 , one or more processors are configured to receive a user-modifiable file 710 containing data 715, the data 715 including parameter settings 726 associated with respective selected parameters 718. The selected parameters 718 and the associated parameter settings 726 are associated with target conditions 716 (e.g., a first set of target conditions TC1). For example, the user-modifiable file 710 can be received from a communication unit (e.g., communication unit 125 or 126; Figure 1 ). The communication unit can receive the user-modifiable file 710 from a remote station via a data communication (e.g., data communication 708; Figure 17 ). In this example, the user-modifiable file 710 includes selected parameters 718, the selected parameters 718 including a first selected parameter S-BP1 and a third selected parameter S-BP3. The user-modifiable file 710 also includes parameter settings 726 associated with the selected parameters 718. For example, a first parameter setting PS1 is associated with the first selected parameter S-BP1, while a third parameter setting PS3 is associated with the third selected parameter S-BP3. The first and third parameter settings PS1, PS3 can represent any suitable parameter settings, such as a data sampling rate.

[0224] One or more processors of computing device 118 are configured to access and read user-modifiable file 710 by executing reporting software 790 on at least one of the one or more processors (e.g., of computing device 118). Once user-modifiable file 710 is accessed and read, one or more processors of computing device 118 are configured to link or map parameter settings 726 of user-modifiable file 710 to parameters of parameter list 785. That is, each parameter setting associated with a selected parameter of user-modifiable file 710 is linked or mapped to a parameter of parameter list 785. Each baseline parameter 725 of master parameter list 785 has one or more associated default or current parameter settings 788. In Figure 21 the depicted example, a first selected parameter S-BP1 of user-modifiable file 710 corresponds to a first baseline parameter BP1 having an associated default or current first parameter setting DPS1. A third selected parameter S-BP3 of user-modifiable file 710 corresponds to a third baseline parameter BP3 having an associated default or current third parameter setting DPS3. Thus, the first selected parameter S-BP1 of user-modifiable file 710 is mapped to the first baseline parameter BP1 of parameter list 785, and thus, the first parameter setting PS1 is mapped to the first baseline parameter BP1 of parameter list 785. Similarly, the third selected parameter S-BP3 of user-modifiable file 710 is mapped to the third baseline parameter BP3 of parameter list 785, and thus, the third parameter setting PS3 is mapped to the third baseline parameter BP3 of parameter list 785.

[0225] One or more processors are configured to generate a parameter report list 780 that includes parameters and their associated parameter settings mapped thereto by executing reporting software 790 on at least one of the one or more processors (e.g., of computing device 118). Notably, reporting software 790 is not modified during mapping and generation. In other words, reporting software 790 is not modified when executed to map parameter settings 726 to parameters within parameter list 785 and is not modified when generating parameter report list 780. For Figure 21 the example shown, parameter report list 780 is generated by executed reporting software 790 such that the first baseline parameter BP1 has the first parameter setting PS1 (instead of the first default parameter setting DPS1), and such that the third baseline parameter BP3 has the third parameter setting PS3 (instead of the third default parameter setting DPS3). As shown, parameter settings 726 of the second baseline parameter BP2 and all other parameters within parameter report list 780 remain unchanged.

[0226] After generating the parameter report list 780, one or more processors are configured to receive sensor data from one or more sensors (e.g., engine sensors, aircraft sensors, etc.). Additionally, when a target condition 716 (e.g., target condition TC1) is met, one or more processors are configured to record the parameter values of the parameters 725 (and in some cases the selected parameters 718) in the generated parameter report list 780, at least in part based on the received sensor data and their respective parameter settings 726, including the parameter settings mapped to their respective parameters 725 (e.g., PS1 and PS3).

[0227] One or more processors may generate a recorded data file 730 by executing reporting software 790 ( Figure 17 ), the recorded data file 730 including the parameter values recorded for one or more parameters in the generated parameter report list 780. One or more processors may also route the recorded data file 730 to, for example, a communication unit. In particular, one or more processors may cause a communication unit (e.g., Figure 1 communication unit 125) to transmit at least a portion of the recorded data file 730 to a remote station (e.g., Figure 1 remote station 150). For example, the remote station may be a ground station or a second vehicle. The recorded data file 730 may be transmitted to the remote station during the same flight or engine operation cycle in which the data communication is received, or at a later time (e.g., when the aircraft 110 is parked at an airport).

[0228] Although various embodiments have been described herein in which the parameter list 785 differentiates between baseline and non-baseline parameters, in some implementations of the system 700 and method (600), the parameter list 785 does not differentiate between baseline and non-baseline parameters. In such embodiments, all possible parameters of the parameter list 785 may be selected and specified to be included in the generated parameter report list 780.

[0229] As an example, Figure 22 a schematic diagram of a computing device of a vehicle propulsion system that generates a parameter report list is provided. For this embodiment, the computing device may be the computing device 118 and the vehicle propulsion system may be the engine 114 of the aircraft 110 ( Figure 1 ). The computing system 115 has one or more memory devices and one or more processors, which are configured to receive a user-modifiable file 710 containing data 715 that indicates one or more selected parameters 718 for which parameter values are to be recorded when a target condition 716 is met. In some implementations, the data 715 of the user-modifiable file 710 (received as part of a data communication 708; Figure 17)When a target condition is met, one or more selected parameters 718 for which values are to be recorded are indicated by representing each of the one or more selected parameters with a memory address or an address structure. In particular, the memory addresses representing the one or more selected parameters 718 to be recorded may each indicate a memory location on one or more memory devices of the computing system 115 (e.g., a memory location on one or more memory devices of the computing device 118) where the one or more selected parameters 718 are stored. In other embodiments, data 715 in the user-modifiable file 710 may indicate the one or more selected parameters 718 to be recorded by other designations (e.g., by a parameter name defined in a reporting or control software, by a part of a parameter name defined in a reporting or control software, by a specific nomenclature or code defined in a reporting or control software, by a parameter position in a parameter list, etc.).

[0230] One or more processors are also configured to generate a parameter report list 780 that includes one or more selected parameters 718 by executing reporting software 790 on at least one of the one or more processors without modifying the reporting software 790. In some embodiments, when generating the parameter report list 780 by executing the reporting software 790 on at least one of the one or more processors, the one or more processors are configured to read the user-modifiable file 710 that contains data 715 indicating the one or more selected parameters 718 for which parameter values are to be recorded when one or more target conditions 716 are met. For example, one or more processors of the computing device 118 may access and read the user-modifiable file 710 stored in one or more memory devices 146 of a computing device of the computing system 115, for instance. In some embodiments, the one or more memory devices 146 are components of the computing device 118. In other embodiments, the one or more memory devices 146 are components of some other computing device on the aircraft 110. The received user-modifiable file 710 may be stored in a dedicated memory location. For Figure 22 In the illustrated embodiment, the selected parameters 718 included in the data 715 of the user-modifiable file 710 include a first selected parameter S-P1, a second selected parameter S-P2, and a third selected parameter S-P3. The selected parameters S-P1, S-P2, and S-P3 are associated with a set of target conditions 716.

[0231] After reading the user-modifiable file 710, when generating the parameter report list 780, the one or more processors are configured to map the one or more selected parameters 718 to optional parameters 782 of a parameter list 785 fixed within the reporting software 790. For Figure 22In an embodiment, the parameter list 785 includes a first optional parameter SP1, a second optional parameter SP2, a third optional parameter SP3, and so on up to an Nth optional parameter SPN. As depicted, one or more processors map the selected parameters 718 (the first selected parameter S-P1, the second selected parameter S-P2, and the third selected parameter S-P3 in this example) to their respective optional parameters 782 of the parameter list 785 (the first optional parameter SP1, the second optional parameter SP2, and the third optional parameter SP3 in this example). Thus, the optional parameters 782 of the parameter list 785 that are mapped to one or more selected parameters 718 are designated to be included in the parameter report list 780.

[0232] In some implementations, the data 715 of the user-modifiable file 710 includes one or more parameter settings associated with one or more selected parameters 718. As an example, one or more parameter settings associated with one or more selected parameters include a data sampling rate that indicates the rate at which parameter values of one or more selected parameters are to be recorded when a target condition 716 is met. The parameter settings can be linked to their associated optional parameters 782 and included in the parameter report list 780.

[0233] Once the parameter report list 780 is generated, one or more processors are further configured to receive sensor data from one or more sensors (e.g., engine sensors, aircraft sensors, etc.). Additionally, when the target condition 716 is met or a predetermined recording time has elapsed, one or more processors are configured to record the parameter values of one or more selected parameters 718 in the generated parameter report list 780 based at least in part on the received sensor data and according to their respective parameter settings. One or more processors can generate a recorded data file by executing reporting software 790, the recorded data file including the parameter values recorded for one or more selected parameters in the generated parameter report list 780. One or more processors can also provide the recorded data file. For example, one or more processors can cause a communication unit (e.g., Figure 1 the communication unit 125) to transmit at least a portion of the recorded data file to a remote station (e.g., Figure 1 the remote station 150). For example, the remote station can be a ground station or a second vehicle. The recorded data file can be transmitted to the remote station during the same flight or engine operation cycle in which the data communication is received or at a later time (e.g., when the aircraft 110 is parked).

[0234] Figure 23FIG. 800 is a block diagram of an example computing system that can be used to implement the methods and systems described herein in accordance with example embodiments of the present disclosure. Computing system 800 is one example of a suitable computing system for implementing the controller / compute elements described herein. Computing device 118, ground computing device 156, other on-board computing devices, the computing units of communication units 125, 126, and other computing devices and / or controllers shown herein can be constructed and operated in a manner similar to computing system 800.

[0235] As Figure 23 shown, computing system 800 can include one or more computing devices 802. The one or more computing devices 802 can include one or more processors 804 and one or more memory devices 806. The one or more processors 804 can include any suitable processing device, such as a microprocessor, a microcontroller, an integrated circuit, a logic device, or other suitable processing device. The one or more memory devices 806 can include one or more computer-readable media, including but not limited to non-transitory computer-readable media, RAM, ROM, hard disk drives, flash drives, and other memory devices.

[0236] The one or more memory devices 806 can store information accessible by the one or more processors 804, including computer-readable instructions 808 executable by the one or more processors 804. The instructions 808 can be any set of instructions that cause the one or more processors 804 to perform operations when executed by the one or more processors 804. The instructions 808 can be software written in any suitable programming language or can be implemented in hardware. In some embodiments, the instructions 808 can be executed by the one or more processors 804 to cause the one or more processors 804 to perform operations.

[0237] Memory device 806 can also store data 810 accessible by processor 804. For example, data 810 can include sensor data, a global list of FADEC parameters, model data, logic data, etc., as described herein. In accordance with example embodiments of the present disclosure, data 810 can include one or more tables, functions, algorithms, models, equations, etc.

[0238] The one or more computing devices 802 can also include a communication interface 812 for communicating, for example, with other components of the system. The communication interface 812 can include any suitable components for interfacing with one or more networks, including, for example, transmitters, receivers, ports, controllers, antennas, or other suitable components.

[0239] Figure 24An example vehicle 900 in accordance with example embodiments of the present disclosure is provided. The systems and methods of the present disclosure may be implemented on an aircraft, helicopter, automobile, ship, submarine, amphibious vehicle, train, unmanned aerial vehicle or drone, and / or on any other suitable vehicle as well as on stationary industrial turbines, for example, for power generation. Although the present disclosure is described herein with reference to aircraft implementations, this is for illustrative purposes only and not limiting. Those of ordinary skill in the art will understand that the systems and methods of the present disclosure may be implemented on other vehicles without departing from the scope of the present disclosure.

[0240] The techniques discussed herein refer to computer-based systems, actions taken by computer-based systems, information sent to computer-based systems, and information from computer-based systems. Those of ordinary skill in the art will recognize that the inherent flexibility of computer-based systems permits a wide variety of possible configurations, combinations, and divisions of tasks and functionality among and within components. For example, the processes discussed herein may be implemented using a single computing device or multiple computing devices working in combination. Databases, memories, instructions, and applications may be implemented on a single system or distributed across multiple systems. The distributed components may operate sequentially or in parallel.

[0241] Although specific features of various embodiments may be shown in some figures and not in others, this is merely for convenience. In accordance with the principles of the present disclosure, any feature of any figure may be referenced and / or claimed in combination with any feature of any other figure.

[0242] This written description uses examples to disclose the invention, including the best mode, and also enables any person skilled in the art to practice the invention, including making and using any device or system and performing any incorporated method. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to fall within the scope of the claims if they include structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ in substance from the literal language of the claims.

[0243] Further aspects of the invention are provided by the subject matter of the following clauses:

[0244] 1. A method for monitoring an engine of a vehicle, the method comprising: when the engine is operating, receiving, by one or more processors, a data query including a user-modifiable file, the user-modifiable file including data indicating at least one of: a target condition and one or more selected parameters for which parameter values are to be recorded; specifying, without modifying the reporting software, the parameters to be recorded by executing reporting software on at least one of the one or more processors, wherein the parameters to be recorded include the one or more selected parameters; mapping, by executing the reporting software, parameter settings associated with the selected parameters to parameters in a parameter report list fixed within the reporting software; and generating, without modifying the reporting software, by executing the reporting software, at least one of: the parameter report list including at least one of the parameters, the parameter settings mapped to the parameters, and one or more baseline parameters.

[0245] 2. The method according to any of the preceding items, further comprising: receiving, by executing the reporting software, sensor data from one or more sensors of the vehicle; determining, by the one or more processors, at least partially based on the received sensor data, whether the target condition is met; recording, by executing the reporting software, the selected parameter values of the one or more selected parameters and the baseline parameter values of the one or more baseline parameters in the generated parameter report list at least partially based on the received sensor data and the parameter settings mapped to the parameters; and compiling, by executing the reporting software, the parameter values of the one or more selected parameters, the recorded selected parameter values, and the recorded baseline parameter values included in the generated parameter report list into a query response file.

[0246] 3. The method according to any of the preceding items, further comprising: transmitting at least a portion of the query response file to a remote station.

[0247] 4. The method according to any of the preceding items, wherein when the target condition is met, the parameter values are recorded by a computing device associated with the engine during a past time window for compilation into the query response file.

[0248] 5. The method according to any of the preceding items, wherein the parameter values are recorded during operation of the propulsion system.

[0249] 6. The method according to any of the preceding items, wherein the data query is received when the vehicle is performing a mission.

[0250] 7. The method according to any of the preceding items, wherein the one or more processors are located on the vehicle.

[0251] 8. According to the method described in any of the preceding clauses, wherein the vehicle is an aircraft.

[0252] 9. According to the method described in any of the preceding clauses, wherein the data query is received when the vehicle is on the ground.

[0253] 10. A vehicle, comprising: a propulsion system; one or more sensors; a computing system having one or more memory devices and one or more processors, the computing system being configured to: receive a data query from a user-modifiable file, the user-modifiable file including data indicating target conditions and one or more selected parameters, for which parameter values are to be recorded when the target conditions are met; and generate a parameter report list including one or more baseline parameters and the one or more selected parameters by executing reporting software on at least one of the one or more processors without modifying the reporting software.

[0254] 11. According to the vehicle described in any of the preceding clauses, wherein the computing system is further configured to: receive sensor data from the one or more sensors; determine whether the target conditions are met at least in part based on the received sensor data; and when it is determined that the target conditions are met, record the parameter values of the one or more selected parameters and the one or more baseline parameters in the generated parameter report list at least in part based on the received sensor data.

[0255] 12. According to the vehicle described in any of the preceding clauses, wherein the computing system is further configured to: by executing reporting software, compile the parameter values of the one or more selected parameters included in the generated parameter report list, the recorded selected parameter values, and the recorded baseline parameter values into a query response file.

[0256] 13. According to the vehicle described in any of the preceding clauses, wherein the computing system is further configured to transmit at least a portion of the query response file to a remote station.

[0257] 14. According to the vehicle described in any of the preceding clauses, wherein when the target conditions are met, the parameter values are recorded by a computing device associated with an engine within the vehicle during a past time window for compilation into the query response file.

[0258] 15. According to the vehicle described in any of the preceding clauses, wherein the parameter values are recorded during operation of the propulsion system.

[0259] 16. According to the vehicle described in any of the preceding clauses, wherein the data query is received when the vehicle is performing a mission.

[0260] 17. A vehicle according to any of the preceding clauses, wherein the data query is received by one or more processors located on the vehicle.

[0261] 18. A vehicle according to any of the preceding clauses, wherein the vehicle is an aircraft.

[0262] 19. A vehicle according to any of the preceding clauses, wherein the receipt of the data query occurs when the vehicle is on the ground.

[0263] 20. An engine for a vehicle, comprising: one or more sensors; an engine controller communicatively coupled to the one or more sensors, the engine controller having one or more memory devices and one or more processing devices, the one or more memory devices storing computer-readable reporting software executable by the one or more processing devices to perform operations, the engine controller being configured to: receive data from a user-modifiable file received at the vehicle, the data including target conditions and one or more selected parameters for which parameter values are to be recorded by the engine controller when the target conditions are met; generate a parameter report list including the one or more selected parameters without modifying the computer-readable reporting software; receive sensor data from one or more sensors located on the vehicle; determine whether the target conditions are met at least in part based on the received sensor data; and when the target conditions are met, record the parameter values associated with the one or more selected parameters in the generated parameter report list.

Claims

1. A method for monitoring an engine of a vehicle, characterized in that, the method comprises: when the engine is operating, receiving, by one or more processors, a data query comprising a user-modifiable file uploaded from a remote station, the user-modifiable file being capable of being modified by a suitable entity at the remote station, the user-modifiable file comprising data indicating at least one of: a target condition and one or more selected parameters for which parameter values are to be recorded; specifying, by the reporting software, the parameters to be recorded without modifying the reporting software, based on the one or more selected parameters accessed from the user-modifiable file by the reporting software executed on at least one of the one or more processors, wherein the parameters to be recorded comprise the one or more selected parameters; mapping, by executing the reporting software, the parameter settings associated with the selected parameters to parameters in a parameter report list fixed within the reporting software; generating, without modifying the reporting software, by executing the reporting software, at least one of: the parameter report list comprising the parameters, the parameter settings mapped to the parameters, and one or more baseline parameters; recording, by executing the reporting software, the parameter values of one or more parameters associated with the parameter report list; and sending the recorded parameter values to the remote station, wherein the recorded parameter values comprise the parameter values of the one or more selected parameters.

2. The method according to claim 1, characterized in that, further comprising: receiving, by executing the reporting software, sensor data from one or more sensors of the vehicle; determining, by the one or more processors, at least partially based on the received sensor data, whether the target condition is met; recording, by executing the reporting software, the selected parameter values of the one or more selected parameters and the baseline parameter values of the one or more baseline parameters in the generated parameter report list, at least partially based on the received sensor data and the parameter settings mapped to the parameters; and compiling, by executing the reporting software, the parameter values of the one or more parameters comprised in the generated parameter report list into a query response file, the parameter values comprising the recorded selected parameter values and the recorded baseline parameter values.

3. The method according to claim 2, characterized in that, further comprising: transmitting at least a portion of the query response file to the remote station.

4. The method according to claim 2, characterized in that, wherein when the target condition is met, the parameter values are to be recorded by a computing device associated with the engine during a past time window for compilation into the query response file.

5. The method according to claim 2, characterized in that, wherein the parameter values are recorded during operation of the propulsion system.

6. The method according to claim 1, characterized in that, wherein the data query is received when the vehicle is performing a mission.

7. The method according to claim 1, characterized in that, wherein the one or more processors are located on the vehicle.

8. The method according to claim 1, wherein, wherein the vehicle is an aircraft.

9. The method according to claim 1, wherein, wherein the data query is received when the vehicle is on the ground.

10. A vehicle, wherein, comprising: a propulsion system; one or more sensors; a computing system having one or more memory devices and one or more processors, the computing system being configured to: receive a data query from a user-modifiable file uploaded from a remote station, the user-modifiable file being modifiable by a suitable entity at the remote station, the user-modifiable file including data indicating a target condition and one or more selected parameters, and parameter values to be recorded for the one or more selected parameters when the target condition is met; generate a parameter report list including one or more baseline parameters and the one or more selected parameters by executing the reporting software on at least one of the one or more processors, based on the one or more selected parameters accessed from the user-modifiable file by the reporting software executed on at least one of the one or more processors, without modifying the reporting software; record the parameter values of one or more parameters associated with the parameter report list by executing the reporting software on at least one of the one or more processors; and send the recorded parameter values to the remote station, wherein the recorded parameter values include the parameter values of the one or more selected parameters.

11. The vehicle according to claim 10, wherein, wherein the computing system is further configured to: receive sensor data from the one or more sensors; determine whether the target condition is met at least in part based on the received sensor data; when it is determined that the target condition is met, record the selected parameter values of the one or more selected parameters and the baseline parameter values of the one or more baseline parameters in the generated parameter report list at least in part based on the received sensor data.

12. The vehicle according to claim 11, wherein, wherein the computing system is further configured to: compile the parameter values of the one or more parameters included in the generated parameter report list into a query response file by executing the reporting software, the parameter values including the recorded selected parameter values and the recorded baseline parameter values.

13. The vehicle according to claim 12, wherein, wherein the computing system is further configured to transmit at least a portion of the query response file to the remote station.

14. The vehicle according to claim 12, wherein, wherein when the target condition is met, the parameter values will be recorded by a computing device associated with an engine within the vehicle during a past time window for compilation into the query response file.

15. The vehicle according to claim 11, wherein, The parameter values are recorded during the operation of the propulsion system.

16. The vehicle according to claim 10, wherein, the data query is received while the vehicle is performing a mission.

17. The vehicle according to claim 10, wherein, the data query is received by one or more processors located on the vehicle.

18. The vehicle according to claim 10, wherein, the vehicle is an aircraft.

19. The vehicle according to claim 10, wherein, the reception of the data query occurs when the vehicle is on the ground.

20. An engine for a vehicle, wherein, comprising: one or more sensors; an engine controller communicatively coupled to the one or more sensors, the engine controller having one or more memory devices and one or more processing devices, the one or more memory devices storing computer-readable reporting software executable by the one or more processing devices for operation, the engine controller being configured to: receive data from a user-modifiable file received at the vehicle, the user-modifiable file being uploaded to the vehicle from a remote station, the user-modifiable file being modifiable by a suitable entity at the remote station, the data including target conditions and one or more selected parameters, and when the target conditions are met, the engine controller is to record parameter values for the one or more selected parameters; generate a parameter report list including the one or more selected parameters without modifying the computer-readable reporting software, based on the one or more selected parameters accessed from the user-modifiable file by the one or more processing devices executing the computer-readable reporting software; receive sensor data from one or more sensors located on the vehicle; determine whether the target conditions are met, at least in part based on the received sensor data; when the target conditions are met, record the parameter values associated with the one or more selected parameters in the generated parameter report list; and send the recorded parameter values to the remote station.

Images