Patent Description:
Embodiments of the present disclosure are directed to a system according to claim <NUM>. Preferred embodiments are defined in the appended dependent claims <NUM> to <NUM>.

Exemplary embodiments of the present disclosure, not encompassed by the wording of the wording of the appended claims, are directed to a method. In one embodiment, the method includes receiving, by a processor, a signal from an avionics sensor. In another embodiment, the method includes storing, by the processor, a portion of the signal in a memory. In another embodiment, the method includes causing, by the processor, a flight display to display an image. In another embodiment, the image includes a linear scale, a pointer and a plurality of data points. In another embodiment, the linear scale includes an axis. In another embodiment, the pointer is positioned on the axis based on the signal received to the processor. In another embodiment, the plurality of data points positioned and oriented relative to the axis to indicate the portion of the signal stored in the memory.

Further, unless expressly stated to the contrary, "or" refers to an inclusive or and not to an exclusive "or".

Embodiments of the concepts disclosed herein are directed generally to a system for providing historical information to an aircraft pilot or crew via images displayed on a flight display. As will be appreciated, the images described herein may provide for enhanced situational awareness and simplified guidance for quickly and efficiently understanding an aircraft's condition regarding historical information. The historical information may be received from a sensor as a signal. All or some portion of the signal may be stored in a memory. The signal may be selectively stored based on a desired storage period between measurements to be displayed. The stored sensor measurements may then be displayed adjacent to a scale (e.g., a linear scale; a curvilinear scale) on the flight display. By the stored sensor measurements being displayed adjacent to the scale, pilot comprehension of trends associated with the scale may be greatly accelerated. The oldest stored measurement may then be replaced with the newest measurements, for reducing memory requirements.

Referring now to <FIG>, a system <NUM> is described, in accordance with one or more embodiments of the present disclosure. The system <NUM> may be embodied as an aircraft control center (or cockpit).

The system <NUM> includes one or more flight displays <NUM> and one or more user interface (UI) elements <NUM>. The flight displays <NUM> may be implemented using any of a variety of display technologies, including CRT, LCD, organic LED, dot matrix display, and others. The flight displays <NUM> may be navigation (NAV) displays, primary flight displays (PFD), a head-up display, electronic flight bag displays, tablets or tablet computers, synthetic vision system displays, head-up displays (HUDs) with or without a projector, a head-worn display, wearable displays, watches, and so on. The flight displays <NUM> may be used to provide information to the flight crew, thereby increasing the flight crew's visual range and enhancing their decision-making abilities. The flight displays <NUM> may be configured to function as, for example, a primary flight display (PFD) used to display altitude, airspeed, vertical speed, navigation and traffic collision avoidance system (TCAS) advisories; a crew alert system (CAS) configured to provide alerts to the flight crew; a multi-function display used to display navigation maps, weather radar, electronic charts, TCAS traffic, aircraft maintenance data and electronic checklists, manuals, and procedures; an engine indicating and crew-alerting system (EICAS) display used to display critical engine and system status data, and so on. Other types and functions of the flight displays <NUM> are contemplated and will be apparent to those skilled in the art. According to various exemplary embodiments of the inventive concepts disclosed herein, at least one of the flight displays <NUM> may be configured to provide a rendered image as described further herein. The flight display <NUM> may then update the image according to a refresh rate of the flight display <NUM>.

In some embodiments, the flight displays <NUM> update the image based on information from a sensor <NUM>, the sensor <NUM> based in the aircraft (i.e., an avionics sensor). In some embodiments, the flight displays <NUM> update the image based on information from one or more of aircraft-based systems, ground-based systems, satellite-based systems, or from systems of another aircraft. In some embodiments, the flight displays <NUM> provide an output from aircraft-based weather radar systems, LIDAR systems, infrared systems, or other systems on the aircraft. For example, the flight displays <NUM> may include an avionics display, a joint display, an air traffic display, a weather radar map, and a terrain display. The flight displays <NUM> include an electronic display or a synthetic vision system (SVS). For example, the flight displays <NUM> may include a display configured to display a two-dimensional (<NUM>-D) image, a three-dimensional (<NUM>-D) perspective image, or a four-dimensional (<NUM>-D) display. Other views of air traffic information, terrain, and/or weather information may also be provided (e.g., plan view, horizontal view, and vertical view). The views shown on the flight displays <NUM> may include monochrome or color graphical representations of the displayed information. Graphical representations of the displayed information may include an indication of altitude of other aircraft, weather conditions, or terrain, or the altitude and/or location of such information relative to the aircraft.

The UI elements <NUM> may include, for example, dials, switches, buttons, touch screens, keyboards, a mouse, joysticks, cursor control devices (CCDs) or other multi-function key pads certified for use with avionics systems. The UI elements <NUM> may be configured to, for example, allow an aircraft crew member to interact with various avionics applications and perform functions such as data entry, manipulation of navigational maps, and moving among and selecting checklist items. For example, the UI elements <NUM> may be used to adjust features of the flight displays <NUM>, such as contrast, brightness, width, and length. The UI elements <NUM> may also (or alternatively) be used by an aircraft crew member to interface with or manipulate the displays of the flight displays <NUM>. For example, the UI elements <NUM> may be used by aircraft crew member to adjust the brightness, contrast, and information displayed on the flight displays <NUM>. The UI elements <NUM> may additionally be used to acknowledge or dismiss an indicator provided by the flight displays <NUM>. Further, the UI elements <NUM> may be used to correct errors on the flight displays <NUM>. Other UI elements <NUM>, such as indicator lights, displays, display elements, and audio alerting devices, may be configured to warn of potentially threatening conditions such as severe weather, terrain, and obstacles.

Referring now to <FIG>, a simplified control diagram of the system <NUM> is described, in accordance with one or more embodiments of the present disclosure. An exemplary embodiment of the system <NUM> may include the flight display <NUM> and a controller <NUM>. The controller <NUM> is configured to receive information from the sensor <NUM>. In some embodiments, the system <NUM> includes the sensor <NUM>, although this is not intended to be limiting. The controller <NUM> may further include a processor <NUM> and a memory <NUM>. It is noted herein that the one or more components of system <NUM> may be communicatively coupled to the various other components of system <NUM> in any manner known in the art. For example, the controller <NUM> may be communicatively coupled to other components (e.g., the flight display <NUM>, the user interface element <NUM>, the sensor <NUM>) via a wireline (e.g., copper wire, fiber optic cable, and the like) or wireless connection (e.g., RF coupling, IR coupling, data network communication (e.g., WiFi, WiMax, Bluetooth and the like). Moreover, different components of the system <NUM> (e.g., flight display <NUM>, user interface element <NUM>, sensor <NUM>) may include the controller <NUM>, processor <NUM>, or memory <NUM> for carrying out at least a portion of the steps described throughout the present disclosure. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

The processor <NUM> may include any one or more processing elements known in the art. In this sense, the processor <NUM> may include any microprocessor-type device configured to execute software algorithms and/or instructions. In general, the term "processor" may be broadly defined to encompass any device having one or more processing elements, which execute program instructions from memory <NUM>. It should be recognized that the steps described throughout the present disclosure may be carried out by the processor <NUM>.

The memory <NUM> may include any storage medium known in the art suitable for storing program instructions executable by the associated one or more processors <NUM>. For example, the memory <NUM> may include a non-transitory memory medium. For instance, the memory <NUM> may include, but is not limited to, a read-only memory (ROM), a random-access memory (RAM), a magnetic or optical memory device (e.g., disk), a magnetic tape, a solid-state drive and the like. It is further noted that memory <NUM> may be housed in a common controller housing with the one or more processors <NUM>. In an alternative embodiment, the memory <NUM> may be located remotely with respect to the physical location of the processor <NUM>. In another embodiment, the memory <NUM> maintains program instructions for causing the processor <NUM> to carry out the various steps described through the present disclosure. In another embodiment, the memory <NUM> maintains one or more circular buffers for storing signals received from the sensor <NUM>.

The sensor <NUM> may include a variety of avionics sensors. The sensor <NUM> may indicate information associated with a flight instrument, such as, but not limited to, attitude, heading, vertical speed, air speed, altimeter, or turn. The sensor <NUM> may also indicate information associated with an engine instrument, such as, but not limited to, a fuel quantity, oil quantity, oil pressure, oil temperature, tachometer, temperature, braking pressure, braking temperature, among others. The sensor <NUM> may further indicate information associated with an engine instrument where the aircraft is one or more of a fixed-wing aircraft, a rotorcraft, a reciprocating engine, or a turbine engine. The sensor <NUM> may also indicate information associated with outside temperatures, such as, but not limited to, a total air temperature (TAT), a static air temperature (SAT), an international standard atmosphere (ISA), or an outside air temperature (OAT). The sensor <NUM> may also indicate information associated with an electrical system, such as, but not limited to, a battery voltage or a battery stage of charge. Thus, the sensor <NUM> may include a variety of known avionics sensors. As may be understood, the sensor <NUM> is not intended to be limited to a specific sensor.

In some embodiments, the sensor <NUM> measures the information in an analog signal format. In some embodiments, the analog signal is converted into a digital signal, by an analog-to-digital converter. Such analog-to-digital converter may be included with the sensor <NUM> or may be performed by a module of the processor <NUM>. In some embodiments, the sensor <NUM> measures the information in a digital signal format. The processor <NUM> may receive the signal from the sensor <NUM>. In this regard, the signal received may be a digital signal or an analog signal which is then converted to a digital signal by the processor <NUM>.

The digital signal includes a sampling rate. The sampling rate of the digital signal may be dependent upon the type of the avionics sensor (e.g., where the avionics sensor measures the information in a digital signal with the period) or the type of the analog-to-digital converter (where the analog-to-digital converter includes a sampling rate by which the analog signal is converted). For example, the sampling rate may include a frequency between <NUM> and <NUM>.

The processor <NUM> is configured to store the digital signal in the memory <NUM>. The processor <NUM> stores the digital signal in memory according to a storage period. The storage period may indicate an amount of time between measurements stored in the memory <NUM>. The storage period may be at least partially based on the sampling rate. For example, each sample of the digital signal may be stored in the memory <NUM>, such that the storage period is equal to the inverse of the sampling rate. However, storing all the samples may result in memory overflow or excess power consumption due to processing requirements. By way of another example, a portion of the samples of the digital signal may be stored the storage period, with the portion being a factor (i.e., a factor other than one) of the sampling rate. As may be understood, appropriate conversions between period and frequencies may occur to determine an allowable storage period. In this present context, the samples are described with the storage period (as opposed to a storage frequency) because the storage period may directly indicate an amount of time between measurements, which may be easier to understand in regards to subsequently displaying the stored information on the flight display <NUM>.

A fixed number of data points is stored in memory. The oldest data point is overwritten by the newest data. Thus, the system <NUM> may support a storing a number of data points in memory. By the data points, processor <NUM> and memory <NUM> usage associated with storing the data points and/or causing the flight display <NUM> to display an image including the data points may be bounded to prevent inadvertent exceedance of an avionics application's allowed usage. In some embodiments, the controller <NUM> stores the information in a circular buffer (circular queue, or similar). By storing the information in the circular buffer, the memory <NUM> may be prevented from being overrun. This is particularly advantageous due to various memory or power constraints associated with avionics systems, especially where signals from multiple sensors are stored in multiple circular buffers in the memory <NUM>. The circular buffer includes a fixed-sized array. As may be understood, the size of the array may include any suitable size, such as, but not limited to, from six to one-hundred, or more. Once the array is full (i.e., each element in the array includes an associated sample from the digital signal) and a new measurement is received, the oldest measurement in the array may be overwritten. Thus, the array may be updated with the newest measurements while maintaining a reduced memory and processing requirement. As may be understood, the circular buffer may include one or more pointers for keeping track of the position in the array. Furthermore, the measurements is stored in the circular buffer according to the storage period. As may be understood, the size of the array together with the storage period may indicate a duration of time for which historical sensor readings are stored and displayed. In this regard, the duration of time represented by the data points may be inversely proportional to the storage period, such that more sensors measurements are displayed for a smaller duration of time. Similarly, the duration of time may be directly proportional to the size of the array.

During aircraft development it may be convenient to adjust the storage period of different sensors. Because some types of sensor parameters undergo meaningful changes at high rates while others change slowly, different periods of trend data may be necessary for different sensor applications. For example, showing a few seconds of history of engine temperature might be useful. However, a few seconds of history behind a fuel quantity scale may appear to be a flat line, even if there is a fuel leak. Therefore, controlling the storage period may be desirable.

In some embodiments, the storage period and the array size may be preloaded into the memory <NUM>. The preloading may occur by any suitable manner, such as, but not limited to, by a table. The table may provide a method for customization of the historical context provided on the flight display <NUM>. The table may be loaded into the memory <NUM>. For example, the table may be loaded into the memory <NUM> by a communication interface (not depicted). The communication interface may include wireline-based interface devices (e.g., DSL-based interconnection, cable-based interconnection, T9-based interconnection, and the like). Similarly, the communication interface may include a wireless-based interface device employing GSM, GPRS, CDMA, EV-DO, EDGE, WiMAX, LTE, WiFi protocols, RF, LoRa, and the like. For example, the preloading may occur by an original-equipment manufacturer (OEM) before the controller <NUM> is installed within the cockpit, by uploading a file to the processor <NUM> for storage in the memory <NUM>. The manufacturer may be provided with a tool for generating the table. For example, the tool may include the sampling rate of the sensor <NUM>. Based on the sampling rate, the storage period between points may be selectively controlled. In this regard, the tool may prevent the manufacturer from selecting a storage period which is off-frequency from the sampling rate. The table may be considered a Parameter Data Item (PDI) file that can be modified and loaded into the avionics. At run time, the avionics may then reference the table to know how frequently to update the measurements for each sensor.

One or more of the storage period or the array size is beselectively adjustable in the cockpit. By selectively adjusting the storage period or the array size, the amount of historical context stored in the memory <NUM> may be controlled. The storage period or the array size may be selectively adjusted in any suitable fashion. For example, the storage period or the array size may be selectively adjusted by a flight test interface. The flight test interface may allow authorized users (e.g., test pilots) to select the storage period or the array size. The flight test interface may be similar with regards to the previously described table. By way of another example, the storage period or the array size may be selectively adjusted in-flight by the user interface element <NUM>. In this regard, the processor <NUM> may receive an input from the user interface element <NUM>. In response to the input, the controller <NUM> may adjust the storage period and/or the array size. In some embodiments, the array size is not selectively adjustable in the cockpit. Where the array size is not selectively adjustable in the cockpit, the processor-executable code maintained on the memory <NUM> may be certified with a given number of memory allocations without regard to possible memory overflow due to adjustments of the array size by the pilot.

Thus, historical sensor readings from the sensor <NUM> may be stored in the memory <NUM>. The processor <NUM> may further cause the flight display <NUM> to generate an image (e.g., image 200a, image 200b, image <NUM>, image <NUM>, etc.). The image may include data points taken from historical sensor readings, together with an indicator of the current sensor reading from the sensor <NUM>. The data points may provide a visual indication to the pilot regarding the history of the associated sensor.

Throughout the flight duration, the processor <NUM> may continue to receive signals from the sensor <NUM>. The processor <NUM> may continually store the portions of the signal in memory <NUM> according to the storage period, and cause the flight display <NUM> to update the image. Updating the image may include periodically shifting previous data points away from a scale on the image, with the newest data points being added. The image may be periodically updated when the new data points are received. However, shifting the data points on the image when new data points are received may provide a disjointed or choppy viewing experience for the pilot. The processor <NUM> may optionally cause the flight display <NUM> to incrementally shift the data points away from the linear scale based on the refresh rate of the flight display <NUM>.

Referring now to <FIG>, exemplary images displayed by the flight display <NUM> are described, in accordance with one or more embodiments of the present disclosure. The system <NUM> may display an image 200a, 200b on the flight display <NUM>. The processor <NUM> may cause the image 200a, 200b to be displayed on the flight display <NUM>.

The image 200a may include a linear scale <NUM>. As may be understood, the term linear scale is not intended to be limited to a scale which represents data in a linear manner. In this regard, the linear scale <NUM> may represent data in a linear, logarithmic, or other manner. Rather, the term linear scale is meant to include scales with an axis which is linear, as opposed to dial scales with a curvilinear axis.

In some embodiments, the linear scale <NUM> may be fixed on the image 200a. In this regard, changes in the measurements from the sensor <NUM> may not affect the linear scale <NUM> relative to the image 200a. In some embodiments, the linear scale <NUM> may be a vertical linear scale. In this regard, the vertical linear scale may be oriented such that the linear scale is oriented in the vertical direction. For example, the linear scale 202a is depicted as a fixed-vertical linear scale.

The image 200a may further include a pointer <NUM>. The pointer <NUM> may include a triangle shape with a vertex oriented at a position on the linear scale <NUM>. The position of the vertex may indicate a current, or more recent measurement received from the sensor <NUM>. The pointer <NUM> may be a moving pointer, such that changes in the current measurement cause the moving pointer to move along the linear scale <NUM> (i.e., where the linear scale <NUM> is fixed). Alternatively, the pointer <NUM> may be fixed (i.e., where the linear scale is a rolling linear scale).

Although the linear scale <NUM> is described as being fixed on the image 200a, this is not intended as a limitation of the present disclosure. In this regard, various embodiments of the present disclosure may also extend to the linear scale being a rolling linear scale with a fixed pointer, such as for an airspeed indicator or an altitude indicator.

In some embodiments, the linear scale <NUM> includes one or more regions <NUM>. For example, the linear scale 202a is depicted as including a region 206a, region 206b, and region 206c. During flight, the image 200a may be represented in color. The regions <NUM> may include various colors representing various parameter indications to the pilot (i.e., safe, warning, danger, etc.). For example, the image 200a is representative of a brake temperature. The region 206a may be represented by a red color, in which the brake temperature is dangerous. The region 206b may be represented by an amber color, in which the brake temperature is approaching dangerous levels. The region 206c may be represented by a green color, in which the brake temperature is at an acceptable level. As depicted, the pointer <NUM> indicates the brake temperature measured by the sensor is within the region 206b near the dangerous temperature levels of the region 206a. However, the pointer <NUM> does not indicate historical information of the temperature by itself. As may be understood, the regions <NUM> may be dependent upon the type of sensor <NUM> for which the image <NUM> is being represented. Furthermore, the linear scale <NUM> is not intended to be limited to include regions <NUM>.

The image 200a may also include data points <NUM>. For example, the image 200a is depicted as including data points 208a-<NUM>. The data points <NUM> may be based on the information stored in the memory <NUM>. For the provided example, the data points 208a-<NUM> represent a brake temperature. The storage period between the data points 208a-<NUM> is one-second. The data points <NUM> may be represented on the linear scale 202a as a current measurement. Thus, a seven-second history of brake temperatures may be displayed to a pilot due to the storage period of one-second, the eight data points, and the data point <NUM> being the current measurement. By the data points 208a-<NUM>, trends associated with changes in the sensor measurements may be observed. Furthermore, parameters which are gradually approaching a dangerous threshold may be visually determined.

In some embodiments, the data points <NUM> are disposed adjacent to the linear scale <NUM> on the image <NUM>. The data points <NUM> may be disposed above, to the left of, below, or to the right of the linear scale <NUM>. The data points <NUM> may further be positioned and oriented relative to the linear scale. The position of the data points <NUM> may be from newest to oldest relative to the linear scale (e.g., the older data points further from the linear scale). The orientation of the data points <NUM> may be such that the value of the data points are represented on the linear scale. For example, the data points 208a-<NUM> are adjacent and left of the linear scale 202a, with a relative height corresponding to a value (and similarly region <NUM>) on the linear scale 202a. The data points 208a-208e are within the region 206c. The data points 208f-<NUM> are within the region 206b. Furthermore, the pointer <NUM> is within the region 206b and approaching the region 206a. In this regard, the image 200a may provide a visual indication that something is wrong with the brake temperature, due to the historical brake temperatures increasing towards dangerous levels. Where the flight display <NUM> is a color display, the data points <NUM> may be similarly colored to the associated regions <NUM>. For example, the data points 208a-208e may be colored green and the data points 208f-<NUM> may be colored amber.

In some embodiments, the data points <NUM> may further be connected by a line similar to a connected scatterplot (not depicted). The line may further be drawn to a point on the linear scale <NUM> at which the vertex of the pointer <NUM> is located. Where the flight display <NUM> is a color display, the lines connecting the data points <NUM> may include a color similar to the region <NUM> associated with the lines. For example, the lines connecting data points 208a-208e may be colored green. The line connecting data points 208e and 208f may be partially green and partially amber, where the transition from green to amber occurs at the boundary between the region 206c and the region 206b. The lines connecting data points 208f-<NUM> may be colored amber. Thus, trendline colors can be associated with the colors of the parameter indication.

In some embodiments, the processor <NUM> may selectively control the storage period and/or the number of data points stored in memory <NUM> (i.e., array size). Changes in the storage period and/or the number of data points may change the image. For instance, increasing the storage period may increases a time between the data points on the image. By way of another instance, increasing the number of data points stored in memory may similarly increase the number of data points displayed on the image. Where the time between data points increases or a number of data points displayed increases, a width taken up by the data points on the flight display <NUM> may similarly increase. In some embodiments, the processor <NUM> may fix the width of the region take up by the data points <NUM> on the image by changing a scale between the data points <NUM>. By fixing the width of the region taken up by the data points <NUM>, the data points <NUM> may be prevented from overlapping with other symbology on the image <NUM>. This may be advantageous where the pilot may selectively control the storage period and/or the number of data points stored in memory.

Referring now to <FIG>, the image 200b is described. The image 200b may be similar to the image 200a. Although the linear scale <NUM> is described as being a vertical linear scale, this is not intended as a limitation on the present disclosure. In this regard, various embodiments of the present disclosure may also extend to linear scales <NUM> which are oriented horizontally. For example, the linear scale 202b is depicted as a fixed-horizontal linear scale. The data points <NUM> of the linear scale 202b may similarly be positioned and oriented such that the value of the data points <NUM> correspond to the linear scale 202b.

The linear scale <NUM> may thus include various permutations of fixed linear scales with moving pointers or rolling linear scales with fixed pointers, together with horizontal orientation or a vertical orientation. In some embodiments, the linear scale <NUM> is a fixed-vertical linear scale with a moving pointer (as depicted in <FIG>) or a fixed-horizontal linear scale with a moving pointer (as depicted in <FIG>).

Referring now to <FIG>, an image <NUM> is described, in accordance with one or more embodiments of the present disclosure. As may be understood, the system <NUM> is not intended to be limited to the image 200a and the image 200b. The system <NUM> may further display a variety of information. In some embodiments, the processor <NUM> may receive information from multiple sensors. The processor <NUM> may further update the flight display <NUM> with an image based on the information received from such sensors. Such information may include a variety of information from a variety of sensors. In some instances, this image may be known as a synoptic image or a synoptic display. The image <NUM> may include multiple linear scales, where one or more of the linear scales includes associated data points. In this regard, the memory <NUM> may include multiple circular array by which measurements may be stored (i.e., a circular array for each sensor). An aircraft may include hundreds, thousands, or even tens-of-thousands of sensors. In some embodiments, historical data for each of those sensors are stored in an associated circular array. For example, the image <NUM> includes a linear scale <NUM>, including an axis for displaying brake temperatures. The linear scale <NUM> may include dual pointers, a first pointer <NUM> and a second pointer <NUM>. The first pointer <NUM> may be on a first side of the linear scale <NUM> and correspond to a current measurement from an out-board (OB) sensor. The second pointer <NUM> may be on a second side of the linear scale <NUM> and correspond to measurements from an in-board sensor. Data points <NUM> may be positioned and oriented relative to the axis of the linear scale <NUM>, to indicate measurements from the OB sensor. Data points <NUM> may be positioned and oriented relative to the axis of the linear scale <NUM>, to indicate measurements from the IB sensor.

Where a linear scale includes dual pointers on opposite sides of the linear scale and data points positioned and oriented to display historical data relative to the linear scale, the data points may be disposed on a same side as the associated pointer, as depicted in <FIG>. Such display may improve a pilot comprehension when viewing the data points for dual pointers with data points. Thus, although <FIG> depict the data points 208a-<NUM> as being on an opposite side of the pointer <NUM>, this is not intended as a limitation on the present disclosure.

Referring now to <FIG>, an image <NUM> is described, in accordance with one or more embodiments of the present disclosure. As may be understood, the system <NUM> is not intended to be limited to the previously described images. The system <NUM> may further display an image with non-linear scales. Although much of the present disclosure has described causing data points to be displayed adjacent to a linear scale, this is not intended as a limitation on the present disclosure. In some embodiments, the flight display <NUM> may display a dial scale <NUM>, such as for various flight instruments. The dial scale <NUM> may be a fixed type (as depicted) dial scale or a rolling type dial scale. The image <NUM> may further include a pointer <NUM>. Where the dial scale <NUM> is fixed, the pointer <NUM> may roll to indicate a current sensor measurement. Where the dial scale <NUM> rolls, the pointer <NUM> may be fixed to indicate the current sensor measurement. The dial scale <NUM> may further include one or more regions <NUM> (e.g., regions 406a, 406b, 406c), similar to the regions <NUM>. The image <NUM> may further include a digital readout <NUM> indicative of the current sensor measurement. The image <NUM> may further includes data points. The data points may be similar to the data points <NUM> and the data points <NUM>. In this regard the data points may be positioned and oriented relative to the dial scale <NUM> to provide an indication on the dial scale <NUM> of the historical sensor measurements. The data points of the image <NUM> may be similarly positioned from newest to oldest relative to the dial scale <NUM>. However, the axis of the dial scale <NUM> may be curvilinear, as opposed to the linear axis of the linear scale. In this regard, the processor <NUM> may cause the flight display to appropriately position and orient the data points relative to the curvilinear axis using a curvilinear coordinate system. Furthermore, the data points may be positioned along the dial scale <NUM> based on the measured values. In this regard, each data point may be disposed in a separate concentric circle. The data points may also be connected by a trendline <NUM>. The trendline <NUM> may provide an indication of historical information from the sensor stored in the memory. In particular, the trendline <NUM> may improve the readability of the image <NUM> by the pilot.

Referring now to <FIG>, a method <NUM> is described. The embodiments and the enabling technologies described previously herein in the context of the system <NUM> should be interpreted to extend to the method <NUM>. For example, the method <NUM> may be implemented by the processor <NUM>. In this regard, the memory <NUM> may be considered to include software for selectively storing sensor measurements and causing the sensor measurements to be displayed on the flight display <NUM>. It is further recognized, however, that the method <NUM> is not limited to the system <NUM>.

In a step <NUM>, a signal is received from an avionics sensor. The signal may be received by a processor. The signal may include a digital signal with a sampling rate.

In a step <NUM>, a portion of the signal is stored in a memory. The portion of the signal may be stored in the memory by the processor. The portion of the signal may be selectively stored based on a storage period. Such storage period may further be based, at least in part, on the sampling rate of the digital signal. In some embodiments, a fixed number of data points may be stored in the memory. For example, the memory may include a circular buffer with a fixed-sized array in which the data points may be stored. The newest data point may overwrite the oldest data point in the buffer.

In a step <NUM>, a flight display is caused to display an image. The flight display may be caused to display the image by the processor. The image may include one or more of a linear scale, a pointer, and a plurality of data points. The linear scale may include an axis. The linear scale may include a fixed linear scale. The linear scale may further include a vertical orientation or a horizontal orientation. The pointer may be positioned on the axis based on the signal received by the processor. The plurality of data points may be positioned and oriented relative to the axis to indicate the portion of the signal stored in the memory. As may be understood, the orientation of the linear scale may similarly change the orientation of the data points, where the data points are oriented relative to the axis. The flight display may further be caused to update the image when new data points are received and stored in the memory.

The method described herein may include storing results of one or more steps of the method embodiments in memory. The results may include any of the results described herein and may be stored in any manner known in the art. The memory may include any memory described herein or any other suitable storage medium known in the art. After the results have been stored, the results can be accessed in the memory and used by any of the method or system embodiments described herein, formatted for display to a user, used by another software module, method, or system, and the like. Furthermore, the results may be stored "permanently," "semi-permanently," temporarily," or for some period of time. For example, the memory may be random access memory (RAM), and the results may not necessarily persist indefinitely in the memory. It is further contemplated that each of the embodiments of the method described above may include any other step(s) of any other method(s) described herein. In addition, each of the embodiments of the method described above may be performed by any of the systems described herein.

Claim 1:
A system, comprising:
at least one flight display (<NUM>) configured to display an image;
a user interface element (<NUM>);
a memory (<NUM>); and
a processor (<NUM>) coupled to the flight display (<NUM>) and the memory (<NUM>); the processor (<NUM>) configured to execute instructions maintained on the memory causing the processor to:
receive a signal from an avionics sensor (<NUM>);
store a portion of the signal in the memory (<NUM>); wherein the signal received from the avionics sensor is a digital signal with a sampling rate; wherein the portion of the signal is stored according to a storage period, the storage period based at least in part on the sampling rate;
cause the flight display (<NUM>) to display the image; the image including a scale, a pointer, and a plurality of data points; the scale including an axis; the pointer positioned on the axis based on the signal; the plurality of data points based on the portion of the signal stored in the memory; wherein the plurality of data points are oriented relative to the axis to indicate a value of the data point on the axis; wherein the plurality of data points are positioned from newest to oldest relative to the axis;
wherein a fixed number of data points are stored in the memory, wherein an oldest data point is overwritten by a newest data point; wherein the data points are stored in a circular buffer of the memory, the circular buffer including a fixed-size array;
wherein the storage period is selectively adjusted in-flight by the user interface element.