System and method for aircraft thrust level model processing
By dynamically managing engine data between flight management computers and electronic engine controllers, the problems of low storage efficiency and error introduction of engine thrust level model data in the aircraft are solved, and more efficient and accurate thrust model management is achieved.
Patent Information
- Application Number
- CN202410360166.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-03-27
- Publication Date
- 2024-11-15
AI Technical Summary
Flight Management Computers (FMCs) in modern aircraft have the possibility of inefficiency in data storage and error introduction in performance management functions, especially due to inconsistencies caused by the replication storage of engine thrust level model (TRM) data.
By dynamically managing engine data between a flight management computer (FMC) and an electronic engine controller (EEC), only engine configuration-related data during the most recent flight is stored in the FMC, and a TRM table is obtained from the EEC when needed, performing error checks to ensure data consistency and accuracy.
Improves storage efficiency, reduces the possibility of errors, ensures the accuracy and consistency of the engine thrust model, and avoids data mismatch and manual update errors.
Smart Images

Figure CN118965552A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to determining thrust rating model data to be used by an aircraft. Background Art
[0002] The flight management computer (FMC) installed in modern aircraft performs various functions, such as navigation, guidance, flight planning, data link and performance management. For example, the performance management function of the FMC uses aircraft and engine models and optimization algorithms to generate a full flight state vertical profile consistent with the performance mode selected and within the flight plan constraints. The input to the performance management function includes, for example, fuel flow, total fuel, engine data and limitations, altitude, airspeed, Mach number, temperature, vertical speed, progress along the flight plan, and pilot input from the control display unit (CDU). Based on these inputs and the aircraft and engine models, the performance management function outputs information such as the results of the thrust limitation calculation (TLC), the target Mach value, the target calibrated airspeed (CAS) value, the target thrust value and the annunciation data to the crew. The performance management function can also use the aerodynamic and propulsion performance data stored in the performance database (PDB) to calculate the predicted flight profile and the associated trip prediction parameters, such as economic speed, optimal altitude, estimated arrival time and predicted fuel consumption.
[0003] To perform the various calculations for the performance management functions, the FMC uses a large set of data tables (Performance Data Refinement (PDR) tables). At least some of these data tables replicate data that is also stored at the electronic engine controller (EEC) of each engine of the aircraft. For example, one type of data used by the FMC is thrust rating model (TRM) data. TRM data for each engine of the aircraft is typically stored at the FMC and the EEC of the engine. This replicated data storage is inefficient and presents the potential for errors to be introduced if one set of tables is updated while another set of tables is not. Summary of the invention
[0004] In a specific implementation, a method includes: accessing, by one or more processors of a flight management computer (FMC) of an aircraft, first engine data from a non-volatile memory of the FMC. The method also includes performing, by the one or more processors, one or more error checking operations based at least on the first engine data to determine whether to select an engine thrust class for a thrust model of the aircraft based in part on a first engine class identifier associated with the first engine data.
[0005] In another specific implementation, an aircraft includes two or more engines and two or more electronic engine controllers (EECs). Each EEC is associated with a corresponding engine of the two or more engines. The aircraft also includes an FMC communicatively coupled to the two or more EECs. The FMC includes a non-volatile memory and one or more processors configured to access first engine data from the non-volatile memory. The one or more processors are further configured to perform one or more error checking operations based at least on the first engine data to determine whether to select an engine thrust level for a thrust model of the aircraft based in part on a first engine level identifier associated with the first engine data.
[0006] In another specific implementation, a non-transitory computer-readable medium stores instructions executable by one or more processors to cause the one or more processors to: access engine data associated with an engine of an aircraft from a non-volatile memory of an FMC. The instructions further cause the one or more processors to perform one or more error checking operations based at least on the engine data. The instructions also cause the one or more processors to select an engine thrust level for a thrust model of the aircraft. Based at least in part on a result of the one or more error checking operations, the engine thrust level is selected from the engine data accessed from the non-volatile memory or the engine data received from an EEC of the aircraft.
[0007] In another specific implementation, a method includes determining, by one or more processors of an FMC of an aircraft, between power-on of the FMC and a subsequent takeoff of the aircraft, a plurality of local thrust rating model (TRM) identifiers, including at least one local TRM identifier for each respective engine of a plurality of engines of the aircraft. The method also includes selecting, by the one or more processors of the FMC, hybrid thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers. The hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0008] In another specific implementation, an aircraft includes two or more engines and two or more EECs. Each EEC is associated with a respective one of the two or more engines. The aircraft also includes an FMC communicatively coupled to the two or more EECs. The FMC includes one or more processors configured to, between power-on of the FMC and subsequent takeoff of the aircraft, determine a plurality of local TRM identifiers, including at least one local TRM identifier for each respective engine of the two or more engines. The one or more processors are further configured to select hybrid thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers. The hybrid thrust model data is associated with a thrust model identifier common to the two or more engines.
[0009] In another specific implementation, a non-transitory computer-readable medium stores instructions executable by one or more processors to cause the one or more processors to determine, between power-on of an FMC of an aircraft and a subsequent takeoff of the aircraft, a plurality of local TRM identifiers, including at least one local TRM identifier for each respective engine of a plurality of engines of the aircraft. The instructions further cause the one or more processors to select hybrid thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers. The hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0010] The features, functions, and advantages described herein can be achieved independently in various implementations or may be combined in yet other implementations further details of which can be found with reference to the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is a diagram showing an embodiment of an aircraft according to a specific implementation of the present disclosure.
[0012] Figure 2 is a flow chart illustrating an embodiment of a method of dynamically determining thrust model data for an aircraft according to a specific implementation of the present disclosure.
[0013] Figure 3 It is shown that it can be used as Figure 2 A flowchart of an embodiment of a method of performing initialization of an aspect of the method.
[0014] Figure 4 , Figure 5 and Figure 6 It is shown that it can be used as Figure 2 A flowchart of an embodiment of a method of performing a down selection process in accordance with aspects of the method.
[0015] Figure 7 It is shown that it can be used as Figure 2 A flowchart of an embodiment of a method of performing grade processing of aspects of the method.
[0016] Figure 8 It is shown that it can be used as Figure 2 A flowchart of an embodiment of a method of performing a selection process is provided in accordance with an aspect of the method.
[0017] Fig. 9 It shows Figure 1 A flow chart of an embodiment of the life cycle of an aircraft.
[0018] Fig.10 yes Figure 1 A block diagram of a specific implementation method of an aircraft.
[0019] Fig.11 is a block diagram of a computing environment including a computing device configured to support various aspects of computer-implemented methods and computer-executable program instructions (or code) according to the present disclosure. DETAILED DESCRIPTION
[0020] The systems and methods disclosed herein reduce duplicate data storage in the FMC and EEC of an aircraft. Specifically, the FMC stores engine data related to the engine configuration during the most recent flight in non-volatile memory. Other TRM tables and engine data are stored in the EEC, but are not replicated in the FMC. One technical benefit of such a configuration is more efficient memory utilization because duplicate data is not stored in multiple locations. Another technical benefit is reducing the chance of errors due to one set of data (e.g., data stored at the EEC) being different from another set of data (e.g., data stored at the FMC). For example, as explained in detail below, when new engine data is needed at the FMC, the engine data is accessed from the EEC, thereby avoiding data mismatches.
[0021] In the disclosed system and method, engine data shared between the EEC and the TRM of the FMC is uploaded from the EEC to the FMC on demand. The FMC will retain a copy of the engine data from the EEC in the FMC non-volatile memory (NVM). During initialization, the integrity of the engine data stored in the NVM of the FMC is checked for internal consistency and consistency with the engine data stored at the EEC. For example, a cyclic redundancy check (CRC) or other error detection operation can be used to determine whether the engine data stored at the NVM should be used, or whether the data should be requested from one or more EECs. In normal operation, the engine data stored in the NVM of the FMC is expected to pass the data integrity check, in which case the FMC uses the engine data from the NVM for thrust model calculations during subsequent flights.
[0022] In abnormal operation, the engine data stored in the NVM of the FMC is expected to fail the data integrity check. For example, a CRC value calculated based on the engine data stored at the NVM of the FMC may not match the expected CRC value for the engine data, such as due to a bit flip caused by electromagnetic interference or other failure of the NVM. As another example, a CRC value calculated based on the engine data stored at the NVM of the FMC may not match a CRC value from one of the EECs, thereby indicating that the engine data stored at the NVM does not match the engine data stored at the EEC (e.g., due to an engine change). In such an abnormal situation, the FMC retrieves the engine data from one or more of the EECs, stores the retrieved engine data in the NVM, and uses the retrieved engine data for thrust model calculations during a subsequent flight.
[0023] Since the FMC retains engine data associated with the most recently detected configuration, when new engine data is retrieved from one or more of the EECs, the systems and methods disclosed herein dynamically downselect engine thrust levels that are compatible with all engines of the aircraft. The technical benefit of dynamically downselecting engine thrust levels that are compatible with all engines of the aircraft is that the chance of error is reduced. For example, in a system where the FMC copies all TRM data stored in the EEC, the downselection is performed manually and saved as a configuration setting. When one or more engines of the aircraft are replaced or significantly overhauled and updated, the configuration setting indicating engine thrust levels that are compatible with all engines should be manually updated. Dynamically performing operations to downselect compatible engine thrust levels for the engines of the aircraft avoids the possibility that manual updates are ignored or incorrectly performed.
[0024] The accompanying drawings and the following description illustrate specific exemplary embodiments. It should be understood that those skilled in the art will be able to design various arrangements that, although not explicitly described or shown herein, embody the principles described herein and are included within the scope of the claims that follow this specification. In addition, any embodiments described herein are intended to aid in understanding the principles of the present disclosure and are to be interpreted as not limiting. Therefore, the present disclosure is not limited to the specific embodiments or embodiments described below, but is defined by the claims and their equivalents.
[0025] Specific implementations are described herein with reference to the accompanying drawings. In the description, common features are represented by common reference numerals throughout the drawings. In some of the drawings, multiple embodiments of a particular type of feature are used. Although the features are physically and / or logically different, the same reference numerals are used for each, and different embodiments are distinguished by adding letters to the reference numerals. When features are referred to herein as a group or type (for example, when specific ones of the features are not mentioned), the reference numerals are used without distinguishing letters. However, when a specific feature among multiple features of the same type is referenced herein, the reference numeral is used with a distinguishing letter. For example, with reference to Figure 1 , multiple engines are shown and are associated with reference numerals 102A and 102B. When referring to a specific one of the engines, such as engine 102A, a distinguishing letter "A" is used. However, when referring to any one of the engines or referring to the engines as a group, reference numeral 102 is used without a distinguishing letter.
[0026] As used herein, various terms are used only for the purpose of describing specific implementations and are not intended to be limiting. For example, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Further, some features described herein are singular in some implementations and plural in other implementations. For illustration, Figure 1 Describes a method comprising one or more processors ( Figure 1 112), indicating that in some implementations, the flight management computer 110 includes a single processor 112, and in other implementations, the flight management computer 110 includes multiple processors 112. For ease of reference herein, such features are generally introduced as "one or more" features, and are subsequently referred to in the singular or optionally in the plural (as generally indicated by "(s)") unless aspects are being described that relate to multiple features.
[0027] The terms "comprise," "comprises," and "comprising" are used interchangeably with "include," "includes," or "including." Additionally, the term "wherein" is used interchangeably with the term "wherein." As used herein, "exemplary" indicates an embodiment, implementation, and / or aspect, and should not be construed as limiting or indicating a preference or preferred implementation. As used herein, ordinal terms (e.g., "first," "second," "third," etc.) used to modify an element (such as a structure, component, operation, etc.) do not, by themselves, indicate any priority or order of the element relative to another element, but merely distinguish the element from another element having the same name (but with respect to the use of the ordinal term). As used herein, the term "set" refers to a grouping of one or more elements, and the term "plurality" refers to a plurality of elements.
[0028] As used herein, "generate", "calculate", "use", "select", "access" and "determine" are interchangeable unless the context indicates otherwise. For example, "generate", "calculate" or "determine" a parameter (or signal) may refer to actively generating, calculating or determining the parameter (or signal) or may refer to using, selecting or accessing the parameter (or signal) that has been generated, such as by another component or device. As used herein, "connection" may include "communication connection", "electrical connection" or "physical connection", and may also (or alternatively) include any combination thereof. Two devices (or components) may be directly or indirectly connected (e.g., communicatively connected, electrically connected or physically connected) via one or more other devices, components, wires, buses, networks (e.g., wired networks, wireless networks, or combinations thereof), etc. Two electrically connected devices (or components) may be included in the same device or different devices, and may be connected via electronic devices, one or more connectors, or inductive coupling, as illustrative, non-limiting embodiments. In some implementations, two devices (or components) that are communicatively coupled (e.g., in electrical communication) may directly or indirectly send and receive electrical signals (digital or analog), for example, via one or more communicating wires, buses, networks, etc. As used herein, "directly coupled" is used to describe two devices that are coupled (e.g., communicatively coupled, electrically coupled, or physically coupled) without intermediary components.
[0029] Figure 1 is a diagram illustrating an embodiment of an aircraft 100 according to a specific implementation of the present disclosure. Figure 1 The aircraft 100 includes two or more engines 102, shown as a first engine 102A and a second engine 102B. Each engine 102 is connected to Figure 1104A and 104B. Each EEC 104 includes (e.g., stored in a local memory) engine data 106 associated with the engine 102 associated with the EEC 104. For example, the first EEC 104A stores engine data 106A associated with the first engine 102A, and the second EEC 104B stores engine data 106B associated with the second engine 102B. Various types of engine data are mentioned here, including engine data, engine rating identifiers, thrust rating identifiers, and thrust rating model identifiers. As used herein, "engine data" is used as an umbrella term that may include engine rating identifiers, thrust rating identifiers, thrust rating (rating) model identifiers, and possible other engine data. As used herein, the terms "engine rating identifier" and "thrust rating identifier" are synonymous, and the term "thrust rating model identifier" refers to uniquely defined rating data of an engine independent of the bill of materials (BOM) of the engine.
[0030] Aircraft 100 also includes a flight management computer (FMC) 110. Figure 1 In the illustrated embodiment, the FMC 110 includes one or more processors 112, non-volatile memory (NVM) 114, and random access memory (RAM) 116. In this context, the RAM 116 includes working memory and similar volatile memory of the FMC 110, such as cache memory, registers, etc. NVM includes any type of memory that retains stored information when power is removed, such as flash memory, electrically erasable programmable read-only memory (EEPROM), magnetoresistive memory (MRAM), and other types of non-volatile memory. The FMC 110 can communicate with each EEC 104 via one or more buses or other data connections of the aircraft 100.
[0031] exist Figure 1 In the illustrated embodiment, the NVM 114 includes (eg, stores) instructions 118 executable by the processor 112 and engine data 120. Figures 2 to 8As explained in detail, the engine data 120 stored by the NVM 114 generally corresponds to data used in the most recent flight of the aircraft 100; however, in certain circumstances the engine data 120 is updated to include the engine data 106 from one of the EECs 104. For example, if a technician realizes that the engine data 120 is incorrect, the technician may update the engine data 120 in the NVM 114. To illustrate, after changing one of the engines 102, the technician may update the engine data 120. In certain aspects, as further explained below, the FMC 110 operates at each startup as if the engine data 120 is suspect. Therefore, the FMC 110 performs various error checking operations at each startup to verify and validate or replace the engine data 120.
[0032] In contrast, the engine data 106 stored by the EEC 104 is known to be correct. The EEC 104 determines the engine data based on reading the configuration of a set of spark plugs in the associated engine 102. For example, the configuration of a set of spark plugs associated with the first engine 102A indicates the thrust rating identifier of the engine 102A. Similarly, the configuration of a set of spark plugs associated with the second engine 102B indicates the thrust rating identifier of the engine 102B. If one of the engines 102 is replaced (e.g., as part of routine maintenance of the aircraft 100), the new engine will have a set of spark plugs that can be configured to indicate a different thrust rating identifier, which the EEC 104 is able to sense and interpret to generate data indicating the thrust rating of the engine. The EECs 104A and 104B continuously, periodically, or occasionally sense the configuration of the spark plugs of the engines 102A and 102B, respectively, and interpret the configuration to determine the correct engine data 106 for each engine 102.
[0033] exist Figure 1In the illustrated embodiment, the instructions 118 stored at the NVM 114 of the FMC 110 include an engine data selector 122 and a thrust model 124. The thrust model 124 may be executed by the processor 112 to perform various performance-related calculations, such as lateral and vertical trajectories, estimated fuel burn at different waypoints, estimated weight at different waypoints, etc. As used herein, a "thrust model" is an aspect of a performance model used by the FMC 110. For example, the thrust model 124 includes, is included within, or corresponds to a performance model. In some implementations, the thrust model 124 is configured to receive input data, such as: fuel flow, total fuel, flap position, engine data and limitations, altitude, airspeed, Mach number, air temperature, vertical speed, progress along the flight plan and pilot input, and the engine data 120. In some implementations, the thrust model 124 is configured to process input data to produce output data, such as a target value for Mach number, calibrated airspeed and thrust for optimal control of the aircraft, and annunciation data to the crew. In other implementations, the thrust model 124 may receive more, less, or different input data and may generate more, less, or different output data.
[0034] The engine data selector 122 includes instructions executable by the processor 112 to select engine data to be used by the thrust model 124 from among the engine data 106A, 106B, and 120. In a particular aspect, the engine data selector 122 dynamically selects the engine data to be used by the thrust model 124 between power-on of the FMC 110 and a subsequent takeoff of the aircraft 100.
[0035] For example, during operation (e.g., during or after power-up of the FMC 110), the engine data selector 122 monitors sensor data from one or more sensors 130 to determine whether an engine data processing condition is satisfied. Typically, engine data processing is performed under circumstances where it is safe to change the engine data available to the FMC, and the engine data processing condition is specified to limit processing to such circumstances. For example, the engine data processing condition may be satisfied when the aircraft 100 is on the ground. In this embodiment, the engine data selector 122 may iteratively perform a series of operations while the aircraft 100 is on the ground until a termination condition is satisfied, wherein the termination condition is satisfied, for example, when engine data 120 for a thrust model 124 has been selected. In other embodiments, the engine data processing condition may be satisfied based on a sensed speed of the aircraft 100, a throttle position of the aircraft 100, or based on other settings, other sensor data, or pilot input. The iteratively performed series of operations are summarized below and referenced. Figures 2 to 8 Detailed description.
[0036] During the initialization process, the engine data selector 122 accesses the engine data 120 from the NVM 114 of the FMC 110. The engine data selector 122 performs one or more error checking operations based on the engine data 120 (and possibly other data) to determine whether to select an engine thrust class for the thrust model 124 based in part on the engine class identifier associated with the engine data 120. When the engine 102 is started, the EEC 104 begins sending data to the engine data selector 122, and the engine data selector 122 includes available data received from the EEC 104 during the initialization process. For example, during one or more early iterations of the operation of the engine data selector 122, only data stored in the NVM 114 may be available to the engine data selector 122. Thereafter, the engine 102A may be started, and the EEC 104A may begin sending data, such as the engine class identifier of the engine 102A, error checking data (e.g., cyclic redundancy check (CRC) data) associated with the engine data 106A, or a portion thereof, and the like. During this period, the engine data selector 122 may perform one or more iterations based on the data from the NVM 114 and the data sent by the EEC 104A. Later, the engine 102B may be started and the EEC 104B may begin sending data, such as an engine rating identifier for the engine 102B, error checking data (e.g., CRC data) associated with the engine data 106B or a portion thereof, etc. During this period, the engine data selector 122 may perform one or more iterations based on the data from the NVM 114, the data sent by the EEC 104A, and the data sent by the EEC 104B. Figure 1 In the illustrated embodiment, the aircraft 100 includes only two engines 102; however, in other implementations, the aircraft 100 includes more than two engines. In such implementations, these additional engines are also associated with EECs that transmit data when their respective engines are started, and the engine data selector 122 utilizes data from these EECs when the data becomes available.
[0037] The error checking operations performed by the engine data selector 122 may include, for example, calculating a CRC value for the engine data 120 stored in the NVM 114 and comparing the calculated CRC value to a CRC value previously determined and stored in the NVM 114. Comparing the calculated CRC value to the stored CRC value enables the engine data selector 122 to determine whether any changes have occurred to the engine data 120 since the engine data 120 was stored in the NVM 114. For example, if the NVM 114 is corrupted such that one or more bits of the engine data 120 have changed, the calculated CRC value should not match the stored CRC value, indicating that the engine data 120 is not authentic. In this case, the engine data selector 122 causes the engine data 120 to be erased, overwritten, or marked as invalid, and the engine data 120 is not used during the selection of the engine thrust level used by the thrust model 124.
[0038] If the calculated CRC value matches the stored CRC value, additional processing is performed to determine whether the engine data 120 in the NVM 114 matches the engine data 106 in one of the EECs 104. For example, when the EEC 104A transmits a CRC value associated with the engine data 106A, the engine data selector 122 compares the CRC value received from the EEC 104A with the CRC value for the engine 102A stored in the NVM 114. Similarly, when the EEC 104B transmits a CRC value associated with the engine data 106B, the engine data selector 122 compares the CRC value received from the EEC 104B with the CRC value for the engine 102B stored in the NVM 114. If the CRC value received from a particular EEC 104 does not match the CRC value for the corresponding engine 102 stored in the NVM 114, the engine data selector 122 causes at least a portion of the engine data 120 for that engine 102 to be erased, overwritten, or marked invalid, and at least a portion of the engine data 120 is not used during selection of the engine thrust level used by the thrust model 124.
[0039] If the CRC value received from a particular EEC 104 matches the CRC value of the corresponding engine 102 stored in the NVM 114, the engine data selector 122 waits for sufficient data to be received to begin operation to select an engine thrust class that is compatible with two or more engines 102. For example, the engine data selector 122 waits until at least two EECs 104 have reported thrust class identifiers for their respective engines 102 (e.g., until it has received a first thrust class identifier associated with engine 102A from EEC 104A and has received a second thrust class identifier associated with engine 102B from EEC 104B). The engine data selector 122 then proceeds to determine a class identifier based on the received thrust class identifiers (e.g., a single class identifier based on the first thrust class identifier from EEC 104A and the second thrust class identifier from EEC 104B). If the engine data 120 in the NVM 114 has passed the error checking operation, the engine data selector 122 may also consider the first engine class identifier from the NVM 114 in selecting a single class identifier.
[0040] In one specific aspect, determining, by the engine data selector 122, the single rating identifier includes determining a plurality of local thrust rating model (TRM) identifiers, including at least one local TRM identifier for each respective engine in the plurality of engines 102 of the aircraft 100, and selecting intermix thrust model data for use by the FMC 110 during flight of the aircraft 100 based on the plurality of local TRM identifiers. In this case, intermix thrust model data refers to specific engine data used by the thrust model 124 and compatible with all engines 102 of the aircraft 100. For example, the intermix thrust model data is associated with a thrust model identifier that is common to the engines 102 of the aircraft 100.
[0041] In a specific aspect, determining the plurality of local TRM identifiers includes accessing the FMC engine rating of the particular engine 102 from the NVM 114 and obtaining the EEC engine rating of the particular engine 102 from the EEC 104 associated with the particular engine. The engine data selector 122 may determine the local rating identifier of the particular engine based on the selected one of the FMC engine rating of the particular engine or the EEC engine rating of the particular engine. For example, the engine data 120 in the NVM 114 may include the FMC engine rating for each of the engines 102A and 102B of the aircraft 100. In addition, the engine data 106A of the EEC 104A may include the EEC engine rating of the engine 102A, and the engine data 106B of the EEC 104B may include the EEC engine rating of the engine 102B. In this embodiment, the engine data selector 122 may obtain the EEC engine rating of the engine 102A from the EEC 104A, and select from the EEC engine rating of the engine 102A and the FMC engine rating of the engine 102A as the local rating identifier of the engine 102A. Similarly, in this embodiment, the engine data selector 122 may obtain the EEC engine rating of the engine 102B from the EEC 104B, and select from the EEC engine rating of the engine 102B and the FMC engine rating of the engine 102B as the local rating identifier of the engine 102B.
[0042] In some implementations, based on a determination that the EEC engine level is valid, the EEC engine level of the particular engine (rather than the FMC engine level of the particular engine) is selected as the local level identifier. In such implementations, based on a determination that the EEC engine level is invalid and the FMC engine level is valid, the FMC engine level of the particular engine is selected as the local level identifier. In some such implementations, based on a determination that the EEC engine level of the particular engine is valid and the FMC engine level of the particular engine is invalid, the engine data selector 122 sets a flag (e.g., one or more data bits, signals, etc.) to indicate that changed engine data for the particular engine is detected.
[0043] After selecting a local rating identifier for each engine 102, the engine data selector 122 determines a local thrust rating model (TRM) identifier for each engine 102. In this context, the TRM identifier uniquely defines the rating data for the engine, regardless of the engine's bill of materials (BOM). Instead, the rating identifier includes both the rating data and information about the engine's BOM. For example, the local TRM identifier for each engine is determined based on mapping data that maps a rating identifier (e.g., a local rating identifier for each engine 102) to a TRM identifier.
[0044] The engine data selector 122 selects hybrid thrust model data based on the local TRM identifier. For example, in some implementations, a single local TRM identifier (e.g., a representative local TRM identifier from the local TRM identifiers of all engines 102 of the aircraft 100) is selected as a comparison object. In this embodiment, other local TRM identifiers are compared with the comparison object to identify the common level identifier as a single level identifier. For example, when the first local TRM identifier of the engine 102A is selected as the comparison object, the second local TRM identifier of the engine 102B is compared with the comparison object. Based on the determination that each of the multiple local TRM identifiers matches the representative local TRM identifier, a single local TRM identifier (e.g., a representative local TRM identifier) is designated as a common level identifier.
[0045] The engine data selector 122 provides the common class identifier to the thrust model 124 for use in subsequent flights of the aircraft. For example, the thrust model 124 performs one or more in-flight calculations based on the engine thrust class indicated by the common class identifier.
[0046] Figure 2 A flow chart of an embodiment of a method 200 for dynamically determining thrust model data for an aircraft according to a specific implementation of the present disclosure is shown. Figures 3 to 8 Shows Figure 2 Method 200 (including Figure 3-Figure 8 Each of the aspects described in the embodiments) can be performed by one or more processors executing instructions, such as by executing Figure 1 The instructions 118 are executed by the processor 112 of the FMC 110.
[0047] The method 200 begins at block 202 with the initialization of the FMC 110. For example, the method 200 may begin with a power-up or restart of the FMC 110 in preparation for flight.
[0048] At block 204, the method 200 includes accessing the level identifier from the NVM 114 of the FMC 110, if any such level identifier is available. For example, the level identifier may be stored in the NVM 114 as a component of (e.g., a data field of) the engine data 120. Any level identifiers stored at the NVM 114 are typically those retained by the NVM 114 from a previous flight of the aircraft 100.
[0049] At block 206, the method 200 begins periodic input / output (I / O) processing. Input processing of the periodic I / O processing includes, for example, receiving data from the EEC 104. Output processing of the periodic I / O processing includes, for example, providing engine thrust ratings to the thrust model 124 for use in performing in-flight calculations. In some cases, the output processing may also or alternatively include providing an alert to the crew of the aircraft 100 to indicate an error or failure condition, such as unavailable data from one or more EECs 104, incompatibility of the engine 102 (based on available thrust rating identifiers), failure of certain data to satisfy an error check, etc.
[0050] At block 208, the method 200 includes determining whether engine data processing can proceed, such as whether the aircraft 100 is on the ground or whether another engine data processing condition is satisfied. The periodic I / O processing continues iteratively until it is determined at block 208 that the engine data processing condition is no longer satisfied (e.g., the aircraft 100 is no longer on the ground), or until the periodic I / O processing is stopped due to a failure condition. Therefore, if it is determined at block 208 that engine data processing cannot proceed, the periodic I / O processing ends at block 210.
[0051] If it is determined at block 208 that engine data processing can proceed, the method 200 begins initialization processing at block 212. The initialization processing includes performing error checking on the engine data 120 from the NVM 114. The initialization processing also includes performing error checking on the data from the EEC 104 if any data has been received from the EEC 104. Figure 3 One specific embodiment of operations that may be performed as part of the initialization process is shown.
[0052] refer to Figure 3 , according to the specific implementation method, execute Figure 2The method 300 of initialization processing of the FMC 110 includes, at block 304, determining whether the engine data 120 and associated CRC data are available in the NVM 114 of the FMC 110. The CRC data used in the determination associated with block 304 is a CRC value previously calculated based on the engine data 120 and stored at the NVM 114. If the engine data 120 and associated CRC data are not available, the method 300 continues to block 306, where the engine data and CRC data (hereinafter referred to as "NVM CRC data" and "NVM engine data" to distinguish from similar values received from the EEC 104 in later operations) in the NVM 114 are cleared. Clearing the NVM CRC data and NVM engine data may include, for example, overwriting a portion of the NVM 114 allocated for storing those data, marking a portion of the NVM 114 allocated for storing those data as invalid or available, or other memory management operations that cause any NVM CRC data and NVM engine data (e.g., partial data or potentially corrupted data) to be unavailable for subsequent processing steps.
[0053] If the NVM engine data and the NVM CRC data are available, the method 300 continues to block 308 where it is determined whether any EEC 104 has sent a CRC check value. If the EEC 104 has provided a CRC check value for the particular engine 102, the method 300 includes determining, at block 312, whether the CRC check value for the particular engine 102 is equal to the NVM CRC value of the NVM CRC data for the particular engine 102. If the CRC check value for the particular engine 102 is not equal to the NVM CRC value for the particular engine 102, the method 300 continues to block 306 where the particular data (e.g., the NVM engine data and the NVM CRC data) of the NVM 114 is cleared.
[0054] Returning to block 308, if the EEC 104 of the particular engine 102 has not provided a CRC check value for the engine 102, the method 300 includes setting the CRC check value for the particular engine 102 equal to the NVM CRC value for the NVM data of the particular engine 102. The method 300 then continues to block 312 to determine whether the CRC check value for the particular engine 102 is equal to the NVM CRC value for the particular engine 102. The operations performed at block 310 ensure that the CRC check value for the particular engine 102 is equal to the NVM CRC value for the particular engine 102, so that the method 300 does not default to clearing the NVM CRC data and the engine data at block 306 when the CRC check value has not been received from the particular EEC. Instead, in this case, the initialization process ends at block 214 and can be repeated in subsequent iterations.
[0055] return Figure 2 After the initialization process ends at box 214, the method 200 includes determining at box 216 whether the level (or levels) stored in the NVM 114 as part of the engine data 120 is from one of the EECs 104. If it is determined at box 216 that the level (or levels) stored in the NVM 114 is not received from the EEC 104, the method 200 includes reporting a failure condition at box 218 and waiting for data from the EEC 104. In typical operation, the engine data 120 stored in the NVM 114 includes data received from the EEC 104; however, in some cases, the engine data 120 may be updated in other ways, such as manually as part of an engine maintenance operation.
[0056] The method 200 continues at block 220 to determine whether at least one thrust class identifier (thrust class ID) has been received from the EEC 104. The remaining operation of the method 200 is dependent upon receiving the thrust class ID from the EEC 104. Thus, if a thrust class ID has not been received from the EEC 104, the method 200 returns to block 208.
[0057] If at least one thrust class ID has been received from the EEC 104, the method 200 includes, at block 222, determining whether the count of thrust class IDs received from the EEC 104 is greater than one. If more than one thrust class ID has been received from the EEC 104, the method 200 includes determining whether the received thrust class IDs are compatible with each other (e.g., based on a compatibility matrix stored at the FMC 110) at block 224. If it is determined at block 224 that two or more of the thrust class IDs are not compatible with each other, the method 200 includes reporting a failure condition at block 226 and ending the periodic I / O processing at block 228.
[0058] If it is determined at block 224 that the thrust class IDs that have been received are compatible with each other, or if it is determined at block 222 that only one thrust class ID has been received, the method 200 includes starting a down-select process at block 230. The down-select process includes an operation of selecting hybrid thrust model data (e.g., a set of thrust model data that is compatible with all engines 102 of the aircraft 100). Since each engine 102 is capable of operating at various levels, the hybrid thrust model data may be considered the greatest common factor among the levels at which the engines are capable of operating (e.g., the highest performance common to all engines). Figure 4-Figure 6 Embodiments of operations that may be performed as part of the down-select process are described.
[0059] Figure 4A method 400 of determining a local thrust rating model (TRM) identifier (ID) for a group of engines is shown. Figure 4 , the method 400 is based on the FMC E(n) level ID 402 and the EEC E(n) level ID 404. The FMC E(n) level ID 402 includes an engine level identifier from the NVM 114 of the FMC 110. The EEC E(n) level ID 404 includes an engine level identifier received from the EEC 104. Each engine level identifier of the FMC E(n) level ID 402 is for a corresponding one of the engines 102 of the aircraft 100, as indicated by the index n. Likewise, each engine level identifier of the EEC E(n) level ID 404 is for a corresponding one of the engines 102 of the aircraft 100, as indicated by the index n. Each index n is an integer value assigned to uniquely identify one of the engines 102 of the aircraft. For example, the engine 102A may be assigned an index value n=1, and the engine 102B may be assigned an index value n=2. In this embodiment, FMC E(1) level ID 402 refers to the engine level identifier stored in NVM 114 for engine 102A, and EEC E(1) level ID 404 refers to the engine level identifier received from EEC 104A for the same engine (i.e., engine 102A). Similarly, FMC E(2) level ID 402 refers to the engine level identifier stored in NVM 114 for engine 102B, and EEC E(2) level ID 404 refers to the engine level identifier received from EEC 104B for the same engine (i.e., engine 102B). For aircraft 100 that include more than two engines 102, index values n greater than 2 are assigned to the other engines 102.
[0060] The method 400 includes a set of operations 406 for selecting a local engine class identifier (local E(n) class ID) 430 for each engine 102. Figure 4 In the illustrated embodiment, the operation 406 of selecting a local E(n) level ID 430 includes determining, for each engine, whether the EEC E(n) level ID 404 and the FMC E(n) level ID 402 are valid. Figure 4 In the illustrated embodiment, these determinations are shown as being performed sequentially in a particular order; however, it should be understood that these determinations may be performed in parallel or in a sequential order. Figure 4 The order shown in the figure is different from the order in which it is executed. Figure 4In the particular embodiment shown, the method 400 includes determining whether each EEC E(n) level ID 404 is valid at block 408 and then determining whether the corresponding FMC E(n) level ID 402 is valid at block 410 or block 420. In certain aspects, the FMC 110 may store a list of valid engine level identifiers for determining the validity of the EEC E(n) level ID 404 and the FMC E(n) level ID 402.
[0061] exist Figure 4 , for a particular engine E(n), if the EEC E(n) level ID 404 is valid and the corresponding FMC E(n) level ID 402 is also valid, the method 400 includes determining, at block 412, whether the FMC E(n) level ID 402 is equal to the EEC E(n) level ID 404. If the FMC E(n) level ID 402 is equal to the EEC E(n) level ID 404, then at block 414, the engine's local E(n) level ID 430 is set equal to the engine's EEC E(n) level ID 404. If the FMC E(n) level ID 402 is not equal to the EEC E(n) level ID 404, then at block 416, a flag is set to indicate that the engine's FMC E(n) level ID 402 has changed, and at block 418, the engine's local E(n) level ID 430 is set equal to the engine's EEC E(n) level ID 404.
[0062] exist Figure 4 , for a particular engine E(n), if the EEC E(n) level ID 404 is valid and the corresponding FMC E(n) level ID 402 is invalid, the method 400 includes setting a flag at box 416 to indicate that the FMC E(n) level ID 402 of the engine has changed, and setting the engine's local E(n) level ID 430 equal to the engine's EEC E(n) level ID 404 at box 418.
[0063] If the EEC E(n) level ID 404 for the particular engine E(n) is invalid and the corresponding FMC E(n) level ID 402 is valid, the method 400 includes, at block 422, setting the local E(n) level ID 430 for the engine equal to the FMC E(n) level ID 402 for the engine. If the EEC E(n) level ID 404 for the particular engine E(n) is invalid and the corresponding FMC E(n) level ID 402 is invalid, the method 400 includes, at block 424, setting the local E(n) level ID 430 for the engine to invalid.
[0064] After the local E(n) class ID 430 of the engine has been determined, the method 400 includes mapping the local E(n) class ID 430 to a corresponding local E(n)TRM ID 434 at block 432. The mapping may be performed via a lookup operation using mapping data that maps engine class identifiers to thrust model identifiers.
[0065] Figure 5 Method 500 is shown illustrating a specific embodiment of operation 502 for determining a single local TRM ID 520 for use as a comparison object in method 600. Operation 502 illustrates only one embodiment of an operation that may be used to select a local TRM ID 520 from among the local E(n)TRM IDs 434.
[0066] exist Figure 5 In operation 502, operation 504 includes determining whether an engine level change flag is set to true. For example, the engine level change flag may be initialized to a false value and in response to determining that the EEC E(n) level ID 404 of the engine is valid and the FMC E(n) level ID 402 is invalid, or in response to determining that the EEC E(n) level ID 404 of the engine is valid, the FMC E(n) level ID 402 of the engine is valid, and the FMC E(n) level ID 402 of the engine is not equal to the EEC E(n) level ID 404 of the engine, the engine level change flag may be initialized to a false value and ... engine level change flag is set to true. Figure 4 is changed to true at block 416 of .
[0067] exist Figure 5 In the example, if the engine level change flag is set to true, the method 500 includes: in box 506, selecting the default engine ( Figure 5 4 and 5. The local E(n)TRM ID 434 of the engine E(1) in FIG. 5 is selected as the local TRM ID 520 for comparison. If the engine level change flag is not set to true (e.g., false), operation 502 includes retrieving the FMC E(n) level ID 508 of the engine, and determining, at block 510, whether the FMC E(n) level ID 508 is valid. If the FMC E(n) level ID 508 is not valid, then at block 506, a default engine is selected as the local TRM ID 520 for comparison. If the FMC E(n) level ID 508 is valid, then method 500 includes, at block 512, mapping the FMC E(n) level ID 508 to a local E(n)TRM ID (e.g., using the mapping data used at block 432), and using the local E(n)TRM ID as the local TRM ID 520 for comparison.
[0068] Figure 6A specific embodiment of a method 600 of determining a thrust model class identifier (eg, a common TRM class ID) common to all engines is shown. The method 600 illustrates only one embodiment of operations that may be used to select a common TRM ID from a set of local E(n)TRM IDs.
[0069] exist Figure 6 , a placeholder variable (p) is initialized to zero at block 650, and a particular value of index n is set (during an initial iteration) or incremented (in subsequent iterations) at block 602. The method 600 also includes, at block 604, determining whether the local E(n)TRM ID of the engine corresponding to the current value of index n is valid. If the local E(n)TRM ID is not valid, the method 600 returns to block 602 and increments the value of index n.
[0070] If the local E(n)TRM ID is valid, the method 600 includes, at block 606, determining whether the local E(n)TRM ID is equal to the local TRM ID 520 (e.g., the previously selected comparison object). If the local E(n)TRM ID is equal to the local TRM ID 520, the method 600 includes, at block 608, setting the value of the placeholder variable p to the value of index n, and at block 610, determining whether all engines (e.g., each value of index n) have been checked.
[0071] If all engines have not been checked, the method 600 returns to block 602 and increments index n. If all engines have been checked, the method 600 includes determining whether the value of the placeholder variable p is zero at block 612. If the value of the placeholder variable p is equal to zero at block 612, this indicates that no engine meets the condition to reset the value of the placeholder variable p from zero to the index n of the engine (e.g., at block 608). Therefore, if the value of the placeholder variable p is equal to zero at block 612, the method 600 results in a failure indication at block 624, in which case the method 600 can end the periodic I / O processing (e.g., at block 228).
[0072] If the value of the placeholder variable p is not equal to zero at block 612 , the method 600 includes setting the common TRM level ID equal to E(p)TRM level ID (where the value of the placeholder variable p is used as an index to the specified engine) at block 614 .
[0073] Returning to block 606, if the local E(n)TRM ID is not equal to the local TRM ID 520, the method 600 includes, at block 620, identifying a set of allowed proxy (AP) E(n)TRM IDs associated with the local E(n)TRM ID for the particular engine in question. In this context, the AP E(n)TRM ID comprises a superset of the TRM IDs associated with the engine, of which the local E(n)TRM ID is a subset. The other TRM IDs of the AP E(n)TRM ID are associated with step-down (relative to a baseline value associated with the local E(n)TRM ID) performance conditions or step-up performance conditions in which the engine is capable of operating, but which are not default (e.g., optimal) performance conditions associated with the engine.
[0074] The method 600 includes, at block 622, determining whether any of the AP E(n)TRM IDs matches the local TRM ID 520. If one of the AP E(n)TRM IDs matches the local TRM ID 520, the method 600 proceeds to block 610. If none of the AP E(n)TRM IDs matches the local TRM ID 520, the method 600 includes, at block 638, determining whether all engines are associated with a local E(n)TRM ID that is equal to the AP E(n)TRM ID. If all engines are associated with a local E(n)TRM ID that is equal to the AP E(n)TRM ID, the method 600 includes, at block 640, setting the local TRM ID 520 equal to the local E(n)TRMID, and returning to block 608. If not all engines are associated with a local E(n)TRM ID that is equal to the AP E(n)TRM ID, then the method 600 results in a failure indication at block 642 (eg, because at least one engine does not have a compatible TRM ID).
[0075] return Figure 2 After the down selection process is completed at block 232, the method 200 includes starting level processing at block 234. Level processing includes operations to update the engine data 120 stored in the NVM 114 (if necessary) and various error checking operations. For example, if the NVM CRC data and the engine data 120 for a particular engine are cleared, then at block 234, the level processing may be performed. Figure 3 At block 306 , the new CRC data and engine data received from the EEC 104 of the engine 102 are stored to the NVM 114 as part of the level processing.
[0076] Figure 7A specific embodiment of a method 700 for performing rank processing is shown. Method 700 illustrates only one embodiment of operations that may be used for rank processing. The rank processing performed by method 700 may be performed at different times within method 200. For example, rank processing may be performed before down selection processing.
[0077] The method 700 includes a set of operations performed for each EEC E(n) Level ID that has been received when processing occurs. The operations of the method 700 include, at block 704, determining whether the FMC E(n) Level ID is available in the NVM 114. For example, if at block 306, the particular FMC E(n) Level ID is cleared from the NVM 114, then at the time the determination is made at block 704, the FMC E(n) Level ID will not be available. If the FMC E(n) Level ID is not available in the NVM 114, then the method 700 includes, at block 706, storing the E(n) Level ID from the EEC (i.e., the EEC E(n) Level ID) in the NVM 114 of the FMC 110. Thus, in this case, the EEC E(n) Level ID becomes the FMC E(n) Level ID.
[0078] If at block 704, the FMC E(n) level ID is available in the NVM 114, the method 700 includes determining whether the EECE(n) level ID is equal to the FMC E(n) level ID at block 708. If the EEC E(n) level ID is not equal to the FMC E(n) level ID, the method 700 proceeds to block 706 to store the EEC E(n) level ID as the FMC E(n) level ID. If the EEC E(n) level ID is equal to the FMC E(n) level ID, the method 700 includes determining whether the EEC E(n) CRC data is available at block 710.
[0079] If the EEC E(n)CRC data is not available at box 710, or if the EEC E(n) level ID has been stored as the FMC E(n) level ID at box 706, the method 700 includes requesting E(n)CRC data for the particular engine from the EEC at box 712 and requesting E(n)engine data for the particular engine from the EEC at box 714. The method 700 also includes calculating an E(n)CRC value based on the E(n)engine data received from the EEC at box 716, and determining whether the received E(n)CRC data matches the E(n)CRC value calculated based on the E(n)engine data received from the EEC at box 718. If the received E(n)CRC data does not match the E(n)CRC value calculated based on the E(n)engine data received from the EEC, the method 700 includes reporting a failure condition at box 720 and ending the periodic I / O processing at box 228.
[0080] If the received E(n)CRC data matches the E(n)CRC value calculated based on the E(n)engine data received from the EEC, or if the EEC E(n)CRC data is available at block 710, the method 700 includes determining whether all received level IDs have been processed at block 722. If all received level IDs have not been processed, the method 700 returns to block 704 to process other received level IDs. If all received level IDs have been processed, the method 700 completes level processing at block 236.
[0081] return Figure 2 After the level processing is completed at block 236, method 200 includes starting a selection process at block 238. The selection process includes the operation of selecting level information for subsequent use. Figure 8 A specific embodiment of a method 800 for performing a selection process is shown. The method 800 illustrates only one embodiment of operations that may be used for a selection process.
[0082] The method 800 includes, at block 802 , determining whether engine data from all EECs of the aircraft 100 has been received and checked. If engine data from all EECs of the aircraft 100 has been received and checked, the method 800 completes the selection process at block 240 .
[0083] If engine data from all EECs of the aircraft 100 has not yet been received and checked, the method 800 iterates by comparing the engine rankings associated with the engines 102 of the aircraft 100. Iterating the engine rankings includes, at box 804, setting index n equal to 1. The method 800 also includes, at box 806, determining whether the E(n) ranking ID is equal to the common ranking ID identified via the down selection process. If the E(n) ranking ID is not equal to the common ranking ID, the method 800 includes incrementing index n at box 808. The method 800 also includes, at box 810, determining whether data for all engines has been checked (e.g., whether the value of index n exceeds the count of engines N of the aircraft 100). If data for all engines has been checked, the method 800 includes reporting a failure condition due to an invalid down-mix selection at box 812. If data for all engines has not yet been checked, the method 800 returns to box 806.
[0084] At block 806, if the E(n) level ID is equal to the common level ID identified via the down-select process, the method 800 includes, at block 816, determining whether the E(n) CRC data for engine n is stored in the NVM 114 of the FMC 110. If the E(n) CRC data is stored in the NVM 114, the method 800 includes, at block 820, determining whether the FMC E(n) CRC data matches the EECE(n) CRC data.
[0085] If the FMC E(n)CRC data matches the EEC E(n)CRC data, or the E(n)CRC data for engine n is not stored in the NVM 114, the method 800 includes storing the E(n)CRC data and the engine data to the NVM 114 of the FMC 110 at block 818. At block 240, the method 800 completes the selection process based on a determination that the FMC E(n)CRC data matches the EEC E(n)CRC data or after storing the E(n)CRC data and the engine data at the NVM 114. Return to Figure 2 After the selection process is completed, at block 240 , method 200 returns to block 208 .
[0086] Fig. 9 It is shown that the Figure 1 Flowchart of method 900 for the life cycle of an aircraft of the FMC 110. During pre-production, exemplary method 900 includes: at 902, an aircraft (such as reference Figure 1 During the specification and design of the aircraft, method 900 may include specification and design of the FMC 110. Method 900 includes, at 904, material procurement, which may include obtaining materials for the FMC 110.
[0087] During production, method 900 includes component and subassembly manufacturing at 906, and system integration of the aircraft at 908. For example, method 900 may include component and subassembly manufacturing of the FMC 110 and system integration of the FMC 110. At 910, method 900 includes certification and delivery of the aircraft, and placing the aircraft in service at 912. Certification and delivery may include certification of the FMC 110 to place the FMC 110 in service. While in service with a customer, the aircraft may be scheduled for routine maintenance and service (which may also include modification, reconfiguration, refurbishment, etc.). At 914, method 900 includes performing maintenance and service on the aircraft, which may include performing maintenance and service on the FMC 110.
[0088] Each process of method 900 may be performed or implemented by a system integrator, a third party, and / or an operator (e.g., a customer). For the purposes of this specification, a system integrator may include, but is not limited to, any number of aircraft manufacturers and main system subcontractors; a third party may include, but is not limited to, any number of vendors, subcontractors, and suppliers; and an operator may be an airline, a leasing company, a military entity, a service organization, etc.
[0089] Aspects of the disclosure may be described in the context of vehicle embodiments. Figure 1 A specific embodiment of the aircraft 100 is Fig.10 Shown.
[0090] exist Fig.10 In the embodiment of the invention, aircraft 100 includes fuselage 1018 having multiple systems 1020 and interior 1022. Embodiments of multiple systems 1020 include one or more of propulsion system 1024, electrical system 1026, environmental system 1028, and hydraulic system 1030. Any number of other systems may be included. Fig.10 In the embodiment shown in , propulsion system 1024 includes engine 102 and EEC 104 . Fig.10 The system 1020 in the embodiment also includes Figure 1 FMC 110.
[0091] Fig.11 1 is a block diagram of a computing environment 1100 including a computing device 1110 configured to support various aspects of computer-implemented methods and computer-executable program instructions (or codes) according to the present disclosure. For example, the computing device 1110 or a portion thereof is configured to execute instructions to initiate, execute, or control the Figure 1-Figure 10 Describes one or more operations.
[0092] The computing device 1110 includes one or more processors 1120. The processor 1120 is configured to communicate with a system memory 1130, one or more storage devices 1140, one or more input / output interfaces 1150, one or more communication interfaces 1160, or any combination thereof. The system memory 1130 includes volatile memory devices (e.g., random access memory (RAM) devices), non-volatile memory devices (e.g., read-only memory (ROM) devices, programmable read-only memory, and flash memory), or both. The system memory 1130 stores an operating system 1132, which may include a basic input / output system for booting the computing device 1110 and a complete operating system that enables the computing device 1110 to interact with users, other programs, and other devices. The system memory 1130 stores system (program) data 1136, such as engine data 120.
[0093] System memory 1130 includes one or more application programs 1134 (eg, instruction sets) that can be executed by processor 1120. For example, one or more application programs 1134 include programs that can be executed by processor 1120 to start, control, or execute reference programs. Figure 1-Figure 10 For illustration, one or more application programs 1134 include instructions executable by processor 1120 to initiate, control, or perform one or more operations described with reference to engine data selector 122, thrust model 124, or a combination thereof.
[0094] One or more storage devices 1140 include non-volatile storage devices, such as magnetic disks, optical disks, or flash memory devices. In specific embodiments, storage devices 1140 include both removable and non-removable memory devices. Storage devices 1140 are configured to store operating systems, images of operating systems, applications (e.g., one or more applications 1134), and program data (e.g., program data 1136). In a particular aspect, system memory 1130, storage devices 1140, or both include tangible computer-readable media. In a specific aspect, one or more storage devices 1140 are external to computing device 1110.
[0095] One or more input / output interfaces 1150 enable computing device 1110 to communicate with one or more input / output devices 1170 to facilitate user interaction. For example, one or more input / output interfaces 1150 may include a display interface, an input interface, or both. For example, input / output interface 1150 is suitable for receiving input from a user, receiving input from another computing device, or a combination thereof. In some implementations, input / output interface 1150 conforms to one or more standard interface protocols, including a serial interface (e.g., a universal serial bus (USB) interface or an Institute of Electrical and Electronics Engineers (IEEE) interface standard), a parallel interface, a display adapter, an audio adapter, or a custom interface ("IEEE" is a registered trademark of the Institute of Electrical and Electronics Engineers of Piscataway, New Jersey). In some implementations, input / output device 1170 includes one or more user interface devices and displays, including some combination of buttons, keyboards, pointing devices, displays, speakers, microphones, touch screens, and other devices.
[0096] Processor 1120 is configured to communicate with device or controller 1180 via one or more communication interfaces 1160. For example, one or more communication interfaces 1160 may include a network interface. Device or controller 1180 may include, for example, EEC 104, one or more other devices, or any combination thereof.
[0097] In some implementations, a non-transitory computer-readable medium stores instructions that, when executed by one or more processors, cause the one or more processors to initiate, execute, or control operations to perform some or all of the functionality described above. For example, the instructions may be executed to implement Figure 1-Figure 11 In some implementations, Figure 1-Figure 11 Part or all of one or more of the operations or methods may be implemented by one or more processors (e.g., one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more digital signal processors (DSPs)) that execute instructions, by dedicated hardware circuits, or any combination thereof.
[0098] Particular aspects of the present disclosure are described in the following group of related embodiments:
[0099] Group 1A:
[0100] According to embodiment 1, a method includes: accessing, by one or more processors of a flight management computer (FMC) of an aircraft, first engine data from a non-volatile memory of the FMC; and performing, by the one or more processors, one or more error checking operations based at least on the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.
[0101] Embodiment 2 includes the method according to embodiment 1, wherein the one or more error checking operations include calculating a cyclic redundancy check (CRC) value based on the first engine data and comparing the calculated CRC value to a CRC value from a non-volatile memory of the FMC.
[0102] Embodiment 3 includes the method of embodiment 1 or embodiment 2, wherein the one or more error checking operations include comparing a CRC value received from an electronic engine controller (EEC) with a corresponding CRC value from a non-volatile memory of the FMC.
[0103] Embodiment 4 includes the method according to embodiment 3, and further includes clearing the first engine data from the non-volatile memory of the FMC based on results of the one or more error checking operations.
[0104] Embodiment 5 includes a method according to any one of Embodiments 1 to 4, and further includes receiving, at one or more processors of the FMC, a first thrust rating identifier associated with a first engine of the aircraft from a first EEC of the aircraft; receiving, at one or more processors of the FMC, a second thrust rating identifier associated with a second engine of the aircraft from a second EEC of the aircraft; and determining a single rating identifier based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.
[0105] Embodiment 6 includes a method according to embodiment 5, wherein determining the single rating identifier includes: determining a first local engine rating identifier for the first engine based on the first thrust rating identifier and the first engine rating identifier; mapping the first local engine rating identifier to a first local thrust rating model (TRM) identifier; determining a second local engine rating identifier for the second engine based on the second thrust rating identifier and a second engine rating identifier from a non-volatile memory of the FMC; mapping the second local engine rating identifier to a second local TRM identifier; designating the single local TRM identifier as a comparison object; and comparing the first local engine rating identifier, the second local engine rating identifier, or both with the comparison object to identify the common rating identifier as the single rating identifier.
[0106] Embodiment 7 includes the method of any one of Embodiments 1 to 6, and further includes receiving sensor data after the FMC is powered on, wherein the first engine data is accessed in response to the sensor data indicating that the aircraft is on the ground.
[0107] Embodiment 8 includes the method according to embodiment 7, and further includes performing one or more in-flight calculations based on the engine thrust level after selecting the engine thrust level for the thrust model of the aircraft.
[0108] Embodiment 9 includes the method of any of Embodiments 1 to 8, and further includes: accessing additional engine data for each of one or more additional engines of the aircraft from a non-volatile memory of the FMC; and performing, by the one or more processors, one or more additional error checking operations based on the additional engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on one or more engine rating identifiers associated with the additional engine data.
[0109] According to embodiment 10, a device (such as a line replaceable unit (LRU)) includes: a memory configured to store instructions; and a processor configured to execute the instructions to perform the method of any one of embodiments 1 to 9.
[0110] According to embodiment 11, a non-transitory computer-readable medium stores instructions, which, when executed by a processor, cause the processor to perform the method of any one of embodiments 1 to 9.
[0111] According to embodiment 12, an apparatus includes means for implementing the method of any one of embodiments 1 to 9.
[0112] According to Embodiment 13, an aircraft comprises two or more engines; two or more EECs, each EEC being associated with a respective engine of the two or more engines; and an FMC communicatively coupled to the two or more EECs, wherein the FMC comprises a non-volatile memory and one or more processors configured to access first engine data from the non-volatile memory; and performing one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust level for a thrust model of the aircraft based in part on a first engine level identifier associated with the first engine data.
[0113] Embodiment 14 includes an aircraft according to embodiment 13, wherein the one or more error checking operations include calculating a CRC value based on the first engine data and comparing the calculated CRC value to a CRC value from the non-volatile memory of the FMC.
[0114] Embodiment 15 includes an aircraft according to embodiment 13 or embodiment 14, wherein the one or more error checking operations include comparing a CRC value received from the EEC with a corresponding CRC value from a non-volatile memory of the FMC.
[0115] Embodiment 16 includes an aircraft according to embodiment 15, wherein the one or more processors are further configured to clear the first engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations.
[0116] Embodiment 17 includes an aircraft according to any of Embodiments 13 to 16, wherein the one or more processors are further configured to receive a first thrust rating identifier associated with a first engine of the aircraft from a first EEC of two or more EECs; receive a second thrust rating identifier associated with a second engine of the aircraft from a second EEC of the two or more EECs; and determine a single rating identifier based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.
[0117] Embodiment 18 includes an aircraft according to embodiment 17, wherein, to determine the single rating identifier, the one or more processors are configured to determine a first local engine rating identifier for a first engine based on a first thrust rating identifier and a first engine rating identifier; map the first local engine rating identifier to a first local TRM identifier; determine a second local engine rating identifier for a second engine based on a second thrust rating identifier and a second engine rating identifier from a non-volatile memory of the FMC; map the second local engine rating identifier to a second local TRM identifier; designate the single local TRM identifier as a comparison object; and compare the first local engine rating identifier, the second local engine rating identifier, or both with the comparison object to identify the common rating identifier as the single rating identifier.
[0118] Embodiment 19 includes an aircraft according to any of Embodiments 13 to 18, and further includes one or more sensors configured to generate sensor data indicating whether the aircraft is on the ground, wherein the one or more processors are configured to access engine data from the non-volatile memory and select an engine thrust level for the thrust model based on the sensor data indicating that the aircraft is on the ground.
[0119] Embodiment 20 includes the aircraft of embodiment 19, wherein the one or more processors are further configured to perform one or more in-flight calculations based on the engine thrust level after selecting the engine thrust level for the thrust model of the aircraft.
[0120] Embodiment 21 includes an aircraft according to any of Embodiments 13 to 20, wherein the one or more processors are further configured to access additional engine data for each additional engine of the two or more engines from the non-volatile memory; and perform one or more additional error checking operations based on the additional engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on one or more engine rating identifiers associated with the additional engine data.
[0121] According to embodiment 22, a non-transitory computer-readable medium stores instructions executable by one or more processors to cause the one or more processors to: access engine data associated with an engine of an aircraft from a non-volatile memory of an FMC; perform one or more error checking operations based at least on the engine data accessed from the non-volatile memory; and select an engine thrust level for a thrust model of the aircraft, wherein the engine thrust level is selected based at least in part on the engine data accessed from the non-volatile memory or the engine data received from an EEC of the aircraft based on a result of the one or more error checking operations.
[0122] Embodiment 23 includes a non-transitory computer-readable medium according to embodiment 22, wherein instructions are executable by one or more processors to cause the one or more processors to: determine a first local engine rating identifier for a first engine of the aircraft based on engine data from the FMC and a first thrust rating identifier received from a first EEC associated with the first engine; map the first local engine rating identifier to a first local TRM identifier; determine a second local engine rating identifier for a second engine of the aircraft based on engine data from the FMC and a second thrust rating identifier received from a second EEC associated with the second engine; map the second local engine rating identifier to a second local TRM identifier; designate a single local TRM identifier as a comparison object; perform a comparison of the first local engine rating identifier, the second local engine rating identifier, or both with the comparison object; and determine a single rating identifier based on the comparison.
[0123] According to embodiment 24, a method includes: between power-on of an FMC of an aircraft and a subsequent take-off of the aircraft: determining, by one or more processors of the FMC, a plurality of local TRM identifiers, including at least one local TRM identifier for each respective engine of a plurality of engines of the aircraft; and selecting, by the one or more processors of the FMC, hybrid thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers, wherein the hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0124] Embodiment 25 includes a method according to embodiment 24, wherein determining multiple local TRM identifiers includes: accessing an FMC engine rating of a specific engine among multiple engines from a non-volatile memory of the FMC; obtaining an EEC engine rating of the specific engine from an EEC associated with the specific engine; and determining a local rating identifier for the specific engine based on a selected one of the FMC engine rating of the specific engine or the EEC engine rating of the specific engine.
[0125] Embodiment 26 includes a method according to embodiment 25, wherein determining multiple local TRM identifiers includes: determining the local TRM identifier for the specific engine based on the local grade identifier of the specific engine and mapping data that maps the grade identifier to the TRM identifier.
[0126] Embodiment 27 includes a method according to embodiment 25 or embodiment 26, wherein determining a plurality of local TRM identifiers includes: based on a determination that the EEC engine grade is valid, selecting an EEC engine grade for a particular engine as the local grade identifier.
[0127] Embodiment 28 includes the method of any one of embodiments 25 to 27, wherein determining a plurality of local TRM identifiers includes selecting an FMC engine rating for a particular engine as the local rating identifier based on determining that the EEC engine rating is invalid and the FMC engine rating is valid.
[0128] Embodiment 29 includes the method of any of embodiments 25-28, and further includes setting a flag indicating that an engine data change for the specific engine is detected based on determining that the EEC engine rating for the specific engine is valid and the FMC engine rating for the specific engine is invalid.
[0129] Embodiment 30 includes the method according to any one of embodiments 24 to 29, wherein selecting the hybrid thrust model data includes determining a common level identifier based on a plurality of local TRM identifiers.
[0130] Embodiment 31 comprises a method according to embodiment 30, wherein determining the common level identifier comprises: selecting a representative local TRM identifier from a plurality of local TRM identifiers; and comparing each of the plurality of local TRM identifiers with the representative local TRM identifier.
[0131] Embodiment 32 comprises a method according to embodiment 31, wherein the representative local TRM identifier is designated as the common level identifier based on determining that each of the plurality of local TRM identifiers matches the representative local TRM identifier.
[0132] According to embodiment 33, a device (such as an LRU) includes: a memory configured to store instructions; and a processor configured to execute the instructions to perform the method as any one of embodiments 24 to 32.
[0133] According to embodiment 34, a non-transitory computer-readable medium stores instructions, which, when executed by a processor, cause the processor to perform any method of embodiment 24 to embodiment 32.
[0134] According to embodiment 35, an apparatus includes means for implementing the method of any one of embodiments 24 to 32.
[0135] According to embodiment 36, an aircraft comprises two or more engines; two or more EECs, wherein each EEC is associated with a respective one of the two or more engines; and an FMC communicatively coupled to the two or more EECs, wherein the FMC comprises one or more processors configured to, between power-on of the FMC and subsequent take-off of the aircraft: determine a plurality of local TRM identifiers, including at least one local TRM identifier for each respective one of the two or more engines; and based on the plurality of local TRM identifiers, select hybrid thrust model data for use by the FMC during flight of the aircraft, wherein the hybrid thrust model data is associated with a thrust model identifier common to the two or more engines.
[0136] Embodiment 37 includes an aircraft according to embodiment 36, wherein, to determine multiple local TRM identifiers, one or more processors are configured to access a first FMC engine level of a first engine of two or more engines from a non-volatile memory of the FMC; obtain a first EEC engine level of the first engine from a first EEC associated with the first engine; and determine a first local level identifier of the first engine based on a selected one of the first FMC engine level or the first EEC engine level.
[0137] Embodiment 38 includes an aircraft according to embodiment 36 or embodiment 37, wherein the one or more processors are configured to: determine a first local TRM identifier among a plurality of local TRM identifiers based on the first local level identifier and mapping data mapping the level identifier to the TRM identifier.
[0138] Embodiment 39 includes an aircraft according to Embodiment 38, wherein, to determine the first local TRM identifier, the one or more processors are configured to select the first EEC engine rating as the first local rating identifier based on determining that the first EEC engine rating is valid.
[0139] Embodiment 40 includes an aircraft according to embodiment 38 or embodiment 39, wherein, to determine the first local TRM identifier, the one or more processors are configured to select the first FMC engine rating as the first local rating identifier based on determining that the first EEC engine rating is invalid and the first FMC engine rating is valid.
[0140] Embodiment 41 includes an aircraft according to any one of Embodiments 37 to 40, wherein the one or more processors are further configured to: based on determining that the EEC engine rating of the specific engine is valid and the FMC engine rating of the specific engine is invalid, set a flag indicating that an engine data change for the specific engine is detected.
[0141] Embodiment 42 includes an aircraft according to any of Embodiments 36 to 41, wherein, to select the hybrid thrust model data, the one or more processors are configured to determine the common level identifier based on the plurality of local TRM identifiers.
[0142] Embodiment 43 includes an aircraft according to embodiment 42, wherein, to determine the common level identifier, the one or more processors are configured to: select a representative local TRM identifier from a plurality of local TRM identifiers; and compare each of the plurality of local TRM identifiers with the representative local TRM identifier.
[0143] Embodiment 44 includes an aircraft according to embodiment 43, wherein the one or more processors are configured to: designate the representative local TRM identifier as the common level identifier based on determining that each of the plurality of local TRM identifiers matches the representative local TRM identifier.
[0144] According to embodiment 45, a non-transitory computer readable medium stores instructions executable by one or more processors to cause the one or more processors to: between power-on of an FMC of an aircraft and a subsequent take-off of the aircraft: determine a plurality of local TRM identifiers, including at least one local TRM identifier for each respective engine of a plurality of engines of the aircraft; and based on the plurality of local TRM identifiers, select hybrid thrust model data for use by the FMC during flight of the aircraft, wherein the hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0145] Embodiment 46 includes a non-transitory computer-readable medium according to embodiment 45, wherein, to determine multiple local TRM identifiers, one or more processors are configured to access a first FMC engine level of a first engine of a plurality of engines from a non-volatile memory of the FMC; obtain a first EEC engine level of the first engine from a first EEC associated with the first engine; and determine a first local level identifier of the first engine based on a selected one of the first FMC engine level or the first EEC engine level.
[0146] Embodiment 47 comprises a non-transitory computer-readable medium according to embodiment 45 or embodiment 46, wherein one or more processors are configured to determine a first local TRM identifier among a plurality of local TRM identifiers based on a first local level identifier and mapping data that maps the level identifier to the TRM identifier.
[0147] Embodiment 48 includes a non-transitory computer readable medium according to embodiment 47, wherein, to determine the first local TRM identifier, the one or more processors are configured to select the first EEC engine grade as the first local grade identifier based on determining that the first EEC engine grade is valid.
[0148] Embodiment 49 includes a non-transitory computer readable medium according to embodiment 47 or embodiment 48, wherein, to determine the first local TRM identifier, one or more processors are configured to select the first FMC engine level as the first local level identifier based on determining that the first EEC engine level is invalid and the first FMC engine level is valid.
[0149] Embodiment 50 includes a non-transitory computer readable medium according to any of embodiments 46 to 49, wherein the one or more processors are further configured to set a flag indicating that an engine data change was detected based on determining that the EEC engine rating of the particular engine is valid and the FMC engine rating of the particular engine is invalid.
[0150] Embodiment 51 includes a non-transitory computer readable medium according to any one of embodiments 45 to 50, wherein, to select hybrid thrust model data, the one or more processors are configured to determine a common level identifier based on a plurality of local TRM identifiers.
[0151] Embodiment 52 comprises a non-transitory computer-readable medium according to embodiment 51, wherein, in order to determine a common level identifier, one or more processors are configured to: select a representative local TRM identifier from a plurality of local TRM identifiers; and compare each of the plurality of local TRM identifiers with the representative local TRM identifier.
[0152] Embodiment 53 includes a non-transitory computer-readable medium according to embodiment 52, wherein one or more processors are configured to: designate the representative local TRM identifier as a common level identifier based on determining that each of a plurality of local TRM identifiers matches the representative local TRM identifier.
[0153] Group 2B:
[0154] Embodiment 1. A method (200-800), comprising:
[0155] Between powering up a flight management computer (FMC) (110) of an aircraft (100) and subsequent takeoff of the aircraft:
[0156] determining (406), by one or more processors (112) of the FMC, a plurality of local thrust rating model (TRM) identifiers (430), including at least one local TRM identifier for each respective engine of a plurality of engines (102) of the aircraft; and
[0157] Hybrid thrust model data (the common TRM level ID of 614) is selected (614) by one or more processors of the FMC for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers, wherein the hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0158] Embodiment 2. The method according to embodiment 1, wherein determining a plurality of local TRM identifiers comprises:
[0159] accessing ( 204 ) an FMC engine rating for a particular engine of the plurality of engines from a non-volatile memory of the FMC;
[0160] obtaining ( 206 ) an electronic engine controller (EEC) engine rating for the particular engine from an EEC associated with the particular engine; and
[0161] A local rating identifier for the particular engine is determined ( 406 ) based on a selected one of the FMC engine rating for the particular engine or the EEC engine rating for the particular engine.
[0162] Embodiment 3. A method according to embodiment 2, wherein determining a plurality of local TRM identifiers comprises determining (432) a local TRM identifier for a specific engine based on a local grade identifier for the specific engine and mapping data that maps the grade identifier to a TRM identifier.
[0163] Embodiment 4. The method of embodiment 2, wherein determining a plurality of local TRM identifiers comprises: selecting (414, 418) an EEC engine rating of a particular engine as a local rating identifier based on determining that the EEC engine rating is valid.
[0164] Embodiment 5. The method of embodiment 2, wherein determining a plurality of local TRM identifiers comprises: selecting (422) the FMC engine rating of the particular engine as the local rating identifier based on determining that the EEC engine rating is invalid and the FMC engine rating is valid.
[0165] Embodiment 6. The method of embodiment 2 further comprises: based on determining that the EEC engine level is valid and the FMC engine level is invalid, setting (416) a flag indicating that an engine data change for the specific engine is detected.
[0166] Embodiment 7. The method of embodiment 1, wherein selecting hybrid model data comprises determining a common level identifier based on a plurality of local TRM identifiers.
[0167] Embodiment 8. The method according to embodiment 7, wherein determining the common level identifier comprises:
[0168] Selecting (502) a representative local TRM identifier from a plurality of local TRM identifiers; and
[0169] Each of the plurality of local TRM identifiers is compared to the representative local TRM identifier (606).
[0170] Embodiment 9. The method of embodiment 8, wherein the representative local TRM identifier is designated as the common level identifier based on determining that each of the plurality of local TRM identifiers matches the representative local TRM identifier.
[0171] Embodiment 10. An aircraft (100), comprising:
[0172] two or more engines (102);
[0173] two or more electronic engine controllers (EECs) (104), wherein each EEC is associated with a respective one of the two or more engines; and
[0174] A flight management computer (FMC) (110) communicatively coupled to the two or more EECs, wherein the FMC includes one or more processors (112) configured to, between power-up of the FMC and subsequent take-off of the aircraft:
[0175] determining (406) a plurality of local thrust rating model (TRM) identifiers (430), including at least one local TRM identifier for each respective engine of the two or more engines; and
[0176] Based on the plurality of local TRM identifiers, hybrid thrust model data is selected (614) for use by the FMC during flight of the aircraft, wherein the hybrid thrust model data is associated with a thrust model identifier that is common to two or more engines.
[0177] Embodiment 11. An aircraft according to embodiment 10, wherein, to determine a plurality of local TRM identifiers, the one or more processors are configured to:
[0178] accessing ( 204 ) a first FMC engine rating for a first engine of the two or more engines from a non-volatile memory of the FMC;
[0179] obtaining ( 206 ) a first EEC engine rating for the first engine from a first EEC associated with the first engine; and
[0180] A first local level identifier for the first engine is determined ( 406 ) based on the selected one of the first FMC engine level or the first EEC engine level.
[0181] Embodiment 12. An aircraft according to embodiment 11, wherein the one or more processors are configured to determine (432) a first local TRM identifier from among the plurality of local TRM identifiers based on the first local level identifier and mapping data mapping the level identifiers to the TRM identifiers.
[0182] Embodiment 13. An aircraft according to embodiment 12, wherein to determine the first local TRM identifier, the one or more processors are configured to select (414, 418) the first EEC engine rating as the first local rating identifier based on determining that the first EEC engine rating is valid.
[0183] Embodiment 14. An aircraft according to embodiment 12, wherein, to determine the first local TRM identifier, the one or more processors are configured to select (422) the first FMC engine rating as the first local rating identifier based on determining that the first EEC engine rating is invalid and the first FMC engine rating is valid.
[0184] Embodiment 15. An aircraft according to embodiment 11, wherein the one or more processors are further configured to: based on determining that the EEC engine rating of the specific engine is valid and the FMC engine rating of the specific engine is invalid, set (416) a flag indicating that an engine data change for the specific engine is detected.
[0185] Embodiment 16. The aircraft of embodiment 10, wherein, to select the hybrid thrust model data, the one or more processors are configured to determine a common level identifier based on a plurality of local TRM identifiers.
[0186] Embodiment 17. The aircraft of embodiment 16, wherein, to determine the common level identifier, the one or more processors are configured to:
[0187] Selecting (502) a representative local TRM identifier from a plurality of local TRM identifiers; and
[0188] Each of the plurality of local TRM identifiers is compared to the representative local TRM identifier (606).
[0189] Embodiment 18. The aircraft of Embodiment 17, wherein the one or more processors are configured to designate the representative local TRM identifier as the common level identifier based on determining that each of the plurality of local TRM identifiers matches the representative local TRM identifier.
[0190] Embodiment 19. A non-transitory computer readable medium (114) storing instructions executable by one or more processors (112) to cause the one or more processors to, between powering on a flight management computer (FMC) (110) of an aircraft (100) and a subsequent takeoff of the aircraft:
[0191] determining (406) a plurality of local thrust rating model (TRM) identifiers (430), including at least one local TRM identifier for each respective engine of a plurality of engines of the aircraft; and
[0192] Based on the plurality of local TRM identifiers, hybrid thrust model data is selected (614) for use by the FMC during flight of the aircraft, wherein the hybrid thrust model data is associated with a thrust model identifier common to the plurality of engines.
[0193] Embodiment 20. The non-transitory computer readable medium of embodiment 19, wherein, to determine the plurality of local TRM identifiers, the one or more processors are configured to:
[0194] accessing ( 204 ) a first FMC engine rating for a first engine of the plurality of engines from a non-volatile memory of the FMC;
[0195] obtaining ( 206 ) a first EEC engine rating for the first engine from a first EEC associated with the first engine; and
[0196] A first local level identifier for the first engine is determined ( 406 ) based on the selected one of the first FMC engine level or the first EEC engine level.
[0197] The illustrations of the embodiments described herein are intended to provide a general understanding of the structures of different implementations. These illustrations are not intended to serve as a complete description of all elements and features of the devices and systems utilizing the structures or methods described herein. After reviewing the present invention, many other implementations may be apparent to those skilled in the art. Other implementations may be utilized and derived from the present disclosure so that structural and logical replacements and changes may be made without departing from the scope of the present disclosure. For example, method operations may be performed in an order different from the order shown in the figure or one or more method operations may be omitted. Therefore, the present disclosure and the accompanying drawings are considered to be illustrative and not restrictive.
[0198] In addition, although specific embodiments have been shown and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar results may replace the specific implementation shown. This disclosure is intended to cover any and all subsequent adaptations or variations of different implementations. Combinations of the above implementations and other implementations not specifically described herein will be apparent to those skilled in the art upon reviewing this description.
[0199] Submit the abstract of the present disclosure, it should be understood that it is not used to explain or limit the scope or meaning of the embodiment. In addition, in the aforementioned specific implementation, for the purpose of streamlining the present disclosure, different features can be combined together or described in a single implementation. The above-mentioned embodiments illustrate but do not limit the present disclosure. It should also be understood that according to the principles of the present disclosure, many modifications and variations are possible. As reflected in the following embodiments, the subject matter claimed for protection may relate to features less than all features of any disclosed embodiment. Therefore, the scope of the present disclosure is limited by the attached embodiments and their equivalents.
Claims
1. A method (200) of determining data for a thrust model of an aircraft, comprising: Accessing (204) first engine data (120) from a non-volatile memory (114) of a flight management computer (110) of the aircraft (100) via one or more processors (112) of the flight management computer; as well as One or more error checking operations (300-600) are performed by the one or more processors based at least on the first engine data to determine whether to select an engine thrust class for a thrust model (124) for the aircraft based in part on a first engine class identifier associated with the first engine data.
2. The method according to claim 1, wherein: The one or more error checking operations include comparing (312) a cyclic redundancy check value received from an electronic engine controller (104) and a corresponding cyclic redundancy check value from the non-volatile memory of the flight management computer.
3. The method of claim 2, further comprising, based on results of the one or more error checking operations, clearing (306) the first engine data from the non-volatile memory of the flight management computer.
4. The method according to claim 1, further comprising: receiving (206) at the one or more processors of the flight management computer from a first electronic engine controller (104) of the aircraft a first thrust level identifier associated with a first engine (102) of the aircraft; receiving ( 206 ) at the one or more processors of the flight management computer from a second electronic engine controller of the aircraft a second thrust level identifier associated with a second engine of the aircraft; as well as A single rating identifier is determined (502) based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.
5. The method according to claim 4, wherein: Determining a single level identifier involves: determining ( 406 ) a first local engine rating identifier for the first engine based on the first thrust rating identifier and the first engine rating identifier; mapping (432) the first local engine rating identifier to a first local thrust rating model identifier; determining (406) a second local engine rating identifier for the second engine based on the second thrust rating identifier and a second engine rating identifier from the nonvolatile memory of the flight management computer; mapping (432) the second local engine rating identifier to a second local thrust rating model identifier; specifying (502) a single local thrust class model identifier as a comparison object; and The first local engine grade identifier, the second local engine grade identifier, or both are compared to the comparison object (614) to identify a common grade identifier as the single grade identifier.
6. The method of claim 1, further comprising, after the flight management computer is powered on, receiving (208) sensor data, wherein the first engine data is accessed in response to the sensor data indicating that an engine data processing condition is satisfied.
7. The method according to claim 6, further comprising: In response to performing one or more error checking operations to determine selecting the engine thrust level for the thrust model: selecting the engine thrust rating for use with the thrust model for the aircraft; and One or more in-flight calculations are performed based on the engine thrust level.
8. The method according to claim 1, further comprising: accessing from the non-volatile memory of the flight management computer additional engine data for each of one or more additional engines of the aircraft; as well as One or more additional error checking operations are performed, by the one or more processors, based on the additional engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the additional engine data.
9. An aircraft (100), comprising: two or more engines (102); two or more electronic engine controllers (104), wherein each electronic engine controller is associated with a respective one of the two or more engines; as well as a flight management computer (110) communicatively coupled to the two or more electronic engine controllers, wherein the flight management computer includes a non-volatile memory (114) and one or more processors (112), the one or more processors being configured to: accessing (204) first engine data from the non-volatile memory; as well as One or more error checking operations (300-600) are performed based at least on the first engine data to determine whether to select an engine thrust class for a thrust model for the aircraft based in part on a first engine class identifier associated with the first engine data.
10. The aircraft according to claim 9, wherein: The one or more error checking operations include comparing (312) a cyclic redundancy check value received from the electronic engine controller with a corresponding cyclic redundancy check value from the non-volatile memory of the flight management computer.
11. The aircraft according to claim 10, wherein: The one or more processors are further configured to clear (306) the first engine data from the non-volatile memory of the flight management computer based on results of the one or more error checking operations.
12. The aircraft according to claim 9, wherein: The one or more processors are further configured to: receiving (206) from a first electronic engine controller of the two or more electronic engine controllers a first thrust rating identifier associated with a first engine of the aircraft; receiving (206) from a second electronic engine controller of the two or more electronic engine controllers a second thrust level identifier associated with a second engine of the aircraft; as well as A single rating identifier is determined (502) based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.
13. The aircraft according to claim 12, wherein: To determine the single level identifier, the one or more processors are configured to: determining ( 406 ) a first local engine rating identifier for the first engine based on the first thrust rating identifier and the first engine rating identifier; mapping (432) the first local engine rating identifier to a first local thrust rating model identifier; determining (406) a second local engine rating identifier for the second engine based on the second thrust rating identifier and a second engine rating identifier from the nonvolatile memory of the flight management computer; mapping (432) the second local engine rating identifier to a second local thrust rating model identifier; specifying (502) a single local thrust class model identifier as a comparison object; as well as The first local engine grade identifier, the second local engine grade identifier, or both are compared to the comparison object (614) to identify a common grade identifier as the single grade identifier.
14. The aircraft of claim 9, further comprising: One or more sensors (130) configured to generate sensor data indicating whether an engine data processing condition is satisfied, wherein the one or more processors are configured to access engine data from the non-volatile memory and select the engine thrust level for the thrust model based on the sensor data indicating that the engine data processing condition is satisfied.
15. The aircraft according to claim 14, wherein: The one or more processors are further configured to, after selecting the engine thrust rating for the thrust model for the aircraft, perform one or more in-flight calculations based on the engine thrust rating.
16. The aircraft of claim 9, wherein: The one or more processors are further configured to: accessing from the non-volatile memory additional engine data for each additional engine of the two or more engines; and One or more further error checking operations are performed based on the further engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the further engine data.
17. A non-transitory computer readable medium (114) storing instructions executable by one or more processors (112) to cause the one or more processors to: accessing (204) engine data (120) associated with an engine of the aircraft from a non-volatile memory of a flight management computer (110); performing one or more error checking operations (300-600) based at least on the engine data accessed from the non-volatile memory; and An engine thrust level is selected (806) for use with a thrust model (124) for the aircraft, wherein the engine thrust level is selected based at least in part on the engine data accessed from the non-volatile memory or received from an electronic engine controller of the aircraft based on the results of the one or more error checking operations.
18. The non-transitory computer readable medium of claim 17, wherein: The one or more error checking operations include comparing (312) a cyclic redundancy check value received from an electronic engine controller with a corresponding cyclic redundancy check value from the non-volatile memory of the flight management computer.
19. The non-transitory computer readable medium of claim 18, wherein: The instructions are executable by the one or more processors to cause the one or more processors to clear (306) the engine data from the non-volatile memory of the flight management computer based on results of the one or more error checking operations.
20. The non-transitory computer readable medium of claim 17, wherein: The instructions are executable by the one or more processors to cause the one or more processors to: determining ( 406 ) a first local engine rating identifier for a first engine of the aircraft based on the engine data from the flight management computer and a first thrust rating identifier received from a first electronic engine controller associated with the first engine of the aircraft; mapping (432) the first local engine rating identifier to a first local thrust rating model identifier; determining ( 406 ) a second local engine rating identifier for a second engine of the aircraft based on the engine data from the flight management computer and a second thrust rating identifier received from a second electronic engine controller associated with the second engine of the aircraft; mapping (432) the second local engine rating identifier to a second local thrust rating model identifier; specifying (506) a single local thrust class model identifier as a comparison object; performing a comparison of the first local engine rating identifier, the second local engine rating identifier, or both with the comparison object (600); and A single level identifier is determined (614) based on the comparison.
