Patent Description:
During operations, such as flight operations in an aircraft, the aircraft often includes multiple displays in a cockpit with each display including data related to the aircraft or a flight plan. The displays may include different layers of displays such as vertical situation displays, lateral situation displays, synthetic vision displays, and the like. However, there is a need for a system and method for generating an animated aircraft display that avoids abrupt transitions between layers.

<CIT> discloses an interactive record keeping system includes a display system, a user input device, an input-output interface and a controller. The controller is configured to receive user input data indicative of a user display preference and a known waypoint location from the user input device, receive aircraft data indicative of a current aircraft operating parameter and receive environmental data indicative of a current environmental condition, both correlating with the known waypoint location. The controller is further configured to calculate an aircraft performance parameter based on the received aircraft data; generate display data based on the calculated aircraft performance parameter, the received environmental data, and the user display preference; provide the display data to the display system; and store the calculated aircraft performance parameter and the environmental data in a memory. The display system of <CIT> does include the features that the opaqueness of a map layer is gradually increased or decreased by a predetermined fade delta value which represents a rate of change to the opaqueness and that the predetermined rate of change of opaqueness is overridden in case of a threat condition.

<CIT> discloses a display method, a computer program for performing the steps of the display method and a display system, the display system having for example: at least one display unit arranged to present at least one display image, at least one memory unit comprising information related to for example descriptions of a set of default graphics display objects and configuration data. The configuration data is arranged to define: at least one transparent display layer, at least one transparent display container associated to the at least one transparent display layer and at least one display mode. Each of said at least one display mode comprising a predetermined selection of one or more of said at least one transparent display container of one or more of said at least one display layer.

The present invention in its various aspects is as set out in the appended claims.

A system is provided for generating an animated display for an aircraft. The system comprises: a flight management system (FMS) configured to control one or more control systems of the aircraft based upon flight plan data for the aircraft; and a map layer display system that is controlled by the FMS, comprising, a plurality of displays, where each of the plurality of displays shows a different view of the flight plan data; a user interface (UI) system configured to receive user input; and a processor communicatively coupled to the plurality of displays and the UI, the processor configured to: determine when the user input received by the UI corresponds to a layer on one of the plurality of displays; increase, when the user input includes a request to add the layer to one of the plurality of displays, opaqueness of the layer from zero percent to one-hundred percent; decrease, when the user input includes a request to remove the layer from one of the plurality of displays, opaqueness of the layer from one-hundred percent to zero-percent; and generate instructions to display the layer at the opaqueness of the layer.

Furthermore, other desirable features and characteristics of the system will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the preceding background.

A method and system has been developed for generating an animated display. The method comprises receiving a user request for a change in a layer shown on a display that shows a view of relevant data. The user request is received by a user interface (UI) that is part of a map layer display system. The system determines which specific layer corresponds to user request for a change to the display. When the user request is to add the layer to the display, the opaqueness of the layer gradually increases from zero percent to one-hundred percent. When the user request is to remove the layer from the display, the opaqueness of the layer gradually decreases from one-hundred percent to zero percent. Finally, the system generates instructions to display the layer at the opaqueness on the display.

Before proceeding further, it is noted that, for convenience, the following description is in the context of an aircraft environment.

Turning now to <FIG>, a diagram <NUM> is shown of an in-flight aircraft <NUM> that contains an onboard flight management system (FMS) <NUM> along with a visual data system <NUM> that is accessed by the FMS <NUM> in accordance with one embodiment. In alternative embodiments, the visual data system <NUM> may be integrated as part of the FMS <NUM>. The FMS <NUM>, as is generally known, is a specialized computer that automates a variety of in-flight tasks such as in-flight management of the flight plan. Using various sensors such as global positioning system (GPS), the FMS <NUM> determines the aircraft's position and guides the aircraft along its flight plan using its navigation database. From the cockpit, the FMS <NUM> is normally controlled through a visual display device such as a control display unit (CDU) which incorporates a small screen, a keyboard or a touchscreen. The FMS <NUM> displays the flight plan and other critical flight data to the aircrew during operation.

The FMS <NUM> may have a built-in electronic memory system that contains a navigation database. The navigation database contains elements used for constructing a flight plan. In some embodiments, the navigation database may be separate from the FMS <NUM> and located onboard the aircraft while in other embodiments the navigation database may be located on the ground and relevant data provided to the FMS <NUM> via a (non-illustrated) communications link with a (non-illustrated) ground station. The navigation database used by the FMS <NUM> may typically include: waypoints/intersections; airways; radio navigation aids/navigation beacons; airports; runway; standard instrument departure (SID) information; standard terminal arrival (STAR) information; holding patterns; and instrument approach procedures. Additionally, other waypoints may also be manually defined by pilots along the route.

The flight plan is generally determined on the ground before departure by either the pilot or a dispatcher for the owner of the aircraft. It may be manually entered into the FMS <NUM> or selected from a library of common routes. In other embodiments the flight plan may be loaded via a communications data link from an airline dispatch center. During preflight planning, additional relevant aircraft performance data may be entered including information such as: gross aircraft weight; fuel weight and the center of gravity of the aircraft. The aircrew may use the FMS <NUM> to modify the plight flight plan before takeoff or even while in flight for variety of reasons. Such changes may be entered via the CDU. Once in flight, the principal task of the FMS <NUM> is to accurately monitor the aircraft's position. This may use a GPS, a VHF omnidirectional range (VOR) system, or other similar sensor in order to determine and validate the aircraft's exact position. The FMS <NUM> constantly cross checks among various sensors to determine the aircraft's position with accuracy.

Additionally, the FMS <NUM> may be used to perform advanced vertical navigation (VNAV) functions. The purpose of VNAV is to predict and optimize the vertical path of the aircraft. The FMS <NUM> provides guidance that includes control of the pitch axis and of the throttle of the aircraft. In order to accomplish these tasks, the FMS <NUM> has detailed flight and engine model data of the aircraft. Using this information, the FMS <NUM> may build a predicted vertical descent path for the aircraft. A correct and accurate implementation of VNAV has significant advantages in fuel savings and on-time efficiency.

In exemplary embodiments, an existing flight management computer (FMC) (or flight management system (FMS)) onboard an aircraft is utilized to communicate data between existing onboard avionics systems or line-replaceable units (LRUs) and another module coupled to the FMC, which supports or otherwise performs new flight management functionality that is not performed by the FMC. For example, a multifunction control and display unit (MCDU) may support or otherwise perform new flight management functionality based on data from onboard avionics or LRUs received via the FMC. In this regard, the FMC is configured to receive operational or status data from one or more avionics systems or LRUs onboard the aircraft at corresponding avionics interfaces and convert one or more characteristics of the operational data to support communicating the operational data with the MCDU. For purposes of explanation, the subject matter may primarily be described herein in the context of converting operational data received from onboard avionics or LRUs in a first format (e.g., an avionics bus format) into another format supported by the interface with the MCDU, the subject matter described herein is not necessarily limited to format conversions or digital reformatting, and may be implemented in an equivalent manner for converting between other data characteristics, such as, for example, different data rates, throughputs or bandwidths, different sampling rates, different resolutions, different data compression ratios, and the like.

<FIG> depicts an exemplary embodiment of an aircraft system <NUM> suitable for implementation onboard an aircraft <NUM> shown previously in <FIG>. The illustrated aircraft system <NUM> includes a flight management computing module <NUM> communicatively coupled to a plurality of onboard avionics LRUs <NUM>, one or more display devices <NUM>, and a multifunction computing module <NUM>. It should be appreciated that <FIG> depicts a simplified representation of the aircraft system <NUM> for purposes of explanation, and <FIG> is not intended to limit the subject matter in any way.

The flight management computing module <NUM> generally represents the FMC, the FMS, or other hardware, circuitry, logic, firmware and/or other components installed onboard the aircraft and configured to perform various tasks, functions and/or operations pertaining to flight management, flight planning, flight guidance, flight envelope protection, four-dimensional trajectory generation or required time of arrival (RTA) management, and the like. Accordingly, for purposes of explanation, but without limiting the functionality performed by or supported at the flight management computing module <NUM>, the flight management computing module <NUM> may alternatively be referred to herein as the FMC. The FMC <NUM> includes a plurality of interfaces <NUM> configured to support communications with the avionics LRUs <NUM> along with one or more display interfaces <NUM> configured to support coupling one or more display devices <NUM> to the FMC <NUM>. In the illustrated embodiment, the FMC <NUM> also includes a communications interface <NUM> that supports coupling the multifunction computing module <NUM> to the FMC <NUM>.

The FMC <NUM> generally includes a processing system designed to perform flight management functions, and potentially other functions pertaining to flight planning, flight guidance, flight envelope protection, and the like. Depending on the embodiment, the processing system could be realized as or otherwise include one or more processors, controllers, application specific integrated circuits, programmable logic devices, discrete gate or transistor logics, discrete hardware components, or any combination thereof. The processing system of the FMC <NUM> generally includes or otherwise accesses a data storage element (or memory), which may be realized as any sort of non-transitory short or long term storage media capable of storing programming instructions for execution by the processing system of the FMC <NUM>. In exemplary embodiments, the data storage element stores or otherwise maintains code or other computer-executable programming instructions that, when read and executed by the processing system of the FMC <NUM>, cause the FMC <NUM> to implement, generate, or otherwise support a data concentrator application <NUM> that performs certain tasks, operations, functions, and processes described herein.

The avionics LRUs <NUM> generally represent the electronic components or modules installed onboard the aircraft that support navigation, flight planning, and other aircraft control functions in a conventional manner and/or provide real-time data and/or information regarding the operational status of the aircraft to the FMC <NUM>. For example, practical embodiments of the aircraft system <NUM> will likely include one or more of the following avionics LRUs <NUM> suitably configured to support operation of the aircraft: a weather system, an air traffic management system, a radar system, a traffic avoidance system, an autopilot system, an autothrottle (or autothrust) system, a flight control system, hydraulics systems, pneumatics systems, environmental systems, electrical systems, engine systems, trim systems, lighting systems, crew alerting systems, electronic checklist systems, and/or another suitable avionics system.

In exemplary embodiments, the avionics interfaces <NUM> are realized as different ports, terminals, channels, connectors, or the like associated with the FMC <NUM> that are connected to different avionics LRUs <NUM> via different wiring, cabling, buses, or the like. In this regard, the interfaces <NUM> may be configured to support different communications protocols or different data formats corresponding to the respective type of avionics LRU <NUM> that is connected to a particular interface <NUM>. For example, the FMC <NUM> may communicate navigation data from a navigation system via a navigation interface <NUM> coupled to a data bus supporting the ARINC <NUM> (or A424) standard, the ARINC <NUM> (or A629) standard, the ARINC <NUM> (or A422) standard, or the like. As another example, a datalink system or other communications LRU <NUM> may utilize an ARINC <NUM> (or A619) compatible avionics bus interface for communicating datalink communications or other communications data with the FMC <NUM>.

The display device(s) <NUM> generally represent the electronic displays installed onboard the aircraft in the cockpit, and depending on the embodiment, could be realized as one or more monitors, screens, liquid crystal displays (LCDs), a light emitting diode (LED) displays, or any other suitable electronic display(s) capable of graphically displaying data and/or information provided by the FMC <NUM> via the display interface(s) <NUM>. Similar to the avionics interfaces <NUM>, the display interfaces <NUM> are realized as different ports, terminals, channels, connectors, or the like associated with the FMC <NUM> that are connected to different cockpit displays <NUM> via corresponding wiring, cabling, buses, or the like. In one or more embodiments, the display interfaces <NUM> are configured to support communications in accordance with the ARINC <NUM> (or A661) standard. In one embodiment, the FMC <NUM> communicates with a lateral map display device <NUM> using the ARINC <NUM> (or A702) standard.

In exemplary embodiments, the multifunction computing module <NUM> is realized as a multifunction control and display unit (MCDU) that includes one or more user interfaces, such as one or more input devices <NUM> and/or one or more display devices <NUM> (shown previously as <NUM> in <FIG>), a processing system <NUM>, and a communications module <NUM>. The MCDU <NUM> generally includes at least one user input device <NUM> that is coupled to the processing system <NUM> and capable of receiving inputs from a user, such as, for example, a keyboard, a key pad, a mouse, a joystick, a directional pad, a touchscreen, a touch panel, a motion sensor, or any other suitable user input device or combinations thereof. The display device(s) <NUM> may be realized as any sort of monitor, screen, LCD, LED display, or other suitable electronic display capable of graphically displaying data and/or information under control of the processing system <NUM>.

The processing system <NUM> generally represents the hardware, circuitry, logic, firmware and/or other components of the MCDU <NUM> configured to perform the various tasks, operations, functions and/or operations described herein. Depending on the embodiment, the processing system <NUM> may be implemented or realized with a general purpose processor, a microprocessor, a controller, a microcontroller, a state machine, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by the processing system <NUM>, or in any practical combination thereof. In this regard, the processing system <NUM> includes or accesses a data storage element (or memory), which may be realized using any sort of non-transitory short or long term storage media, and which is capable of storing code or other programming instructions for execution by the processing system <NUM>. In exemplary embodiments described herein, the code or other computer-executable programming instructions, when read and executed by the processing system <NUM>, cause the processing system <NUM> to implement with an FMS <NUM> (shown previously as <NUM> in <FIG>) additional tasks, operations, functions, and processes described herein.

The communications module <NUM> generally represents the hardware, module, circuitry, software, firmware and/or combination thereof that is coupled between the processing system <NUM> and a communications interface <NUM> of the MCDU <NUM> and configured to support communications between the MCDU <NUM> and the FMC <NUM> via an electrical connection <NUM> between the MCDU communications interface <NUM> and the FMC communications interface <NUM>. For example, in one embodiment, the communications module <NUM> is realized as an Ethernet card or adapter configured to support communications between the FMC <NUM> and the MCDU <NUM> via an Ethernet cable <NUM> provided between Ethernet ports <NUM>, <NUM>. In other embodiments, the communications module <NUM> is configured to support communications between the FMC <NUM> and the MCDU <NUM> in accordance with the ARINC <NUM> (A429) standard via an A429 data bus <NUM> provided between A429 ports <NUM>, <NUM> of the respective modules <NUM>, <NUM>. In yet other embodiments, the communications module <NUM> is configured to support communications between the FMC <NUM> and the MCDU <NUM> in accordance with the ARINC <NUM> (A422) standard via an A422 data bus <NUM> provided between A422 ports <NUM>, <NUM> of the respective modules <NUM>, <NUM>. In yet other embodiments, the communications module <NUM> is configured to support communications between the FMC <NUM> and the MCDU <NUM> in accordance with the ARINC <NUM> (A739) standard via an A739 data bus <NUM> provided between A739 ports <NUM>, <NUM> of the respective modules <NUM>, <NUM>.

In various embodiments, the FMC <NUM> and MCDU <NUM> communicate using a different communications protocol or standard than one or more of the avionics LRUs <NUM> and/or the display devices <NUM>. In such embodiments, to support communications of data between the MCDU <NUM> and those LRUs <NUM> and/or display devices <NUM>, the data concentrator application <NUM> at the FMC <NUM> converts data from one format to another before retransmitting or relaying that data to its destination. For example, the data concentrator application <NUM> may convert data received from an avionics LRU <NUM> to the A429 or Ethernet format before providing the data to the MCDU <NUM>, and vice versa. Additionally, in exemplary embodiments, the FMC <NUM> validates the data received from an avionics LRU <NUM> before transmitting the data to the MCDU <NUM>. For example, the FMC <NUM> may perform debouncing, filtering, and range checking, and/or the like prior to converting and retransmitting data from an avionics LRU <NUM>.

It should be noted that although the subject matter may be described herein in the context of the multifunction computing module <NUM> being realized as an MCDU, in alternative embodiments, the multifunction computing module <NUM> could be realized as an electronic flight bag (EFB) or other mobile or portable electronic device. In such embodiments, an EFB capable of supporting an FMS <NUM> application may be connected to an onboard FMC <NUM> using an Ethernet cable <NUM> to support flight management functionality from the EFB in an equivalent manner as described herein in the context of the MCDU.

In one or more embodiments, the MCDU <NUM> stores or otherwise maintains programming instructions, code, or other data for programming the FMC <NUM> and transmits or otherwise provides the programming instructions to the FMC <NUM> to update or otherwise modify the FMC <NUM> to implement the data concentrator application <NUM>. For example, in some embodiments, upon establishment of the connection <NUM> between modules <NUM>, <NUM>, the MCDU <NUM> may automatically interact with the FMC <NUM> and transmit or otherwise provide the programming instructions to the FMC <NUM>, which, in turn, executes the instructions to implement the data concentrator application <NUM>. In some embodiments, the data concentrator application <NUM> may be implemented in lieu of flight management functionality by the MCDU <NUM> reprogramming the FMC <NUM>. In other embodiments, the FMC <NUM> may support the data concentrator application <NUM> in parallel with flight management functions. In this regard, the FMC <NUM> may perform flight management functions, while the FMS <NUM> application on the MCDU <NUM> supplements the flight management functions to provide upgraded flight management functionality within the aircraft system <NUM>.

<FIG> illustrates an MCDU <NUM> (shown previously as <NUM> in <FIG>), in accordance with an embodiment. The MCDU <NUM> may be used onboard an airplane, a helicopter, a spacecraft, a drone, or the like, or any combination thereof. The aircraft includes multiple controls systems <NUM> for controlling the movement of the MCDU <NUM>. The controls systems <NUM> will vary depending upon the type of aircraft, but may include, for example, one or more engines, rudders, wings, vertical stabilizers, flaps, landing gear, propellers, and the like.

The MCDU <NUM> further includes a flight management system (FMS) <NUM>. The flight management system <NUM> manages a flight plan of the aircraft and may use sensors <NUM> to guide the aircraft along the flight plan utilizing one or more of the control systems <NUM>. The sensors <NUM> may include, for example, a global positioning system (GPS) sensor, an altitude sensor, a wind speed sensor, a wind direction sensor, or the like. The MCDU <NUM> further includes a map layer display system <NUM>. The map layer display system <NUM> controls the presentation of various map layers to improve a user's experience with a display on the MCDU <NUM>. The map layer display system <NUM> may include one or more displays <NUM> on the MCDU <NUM>. The displays <NUM> may include, for example, a lateral situation display, a vertical situation display, a synthetic vision display, or any other display on the aircraft and any combination thereof.

The map layer display system <NUM> further includes a processor <NUM> and a memory <NUM>. The processor <NUM> may be, for example, a central processing unit (CPU), a physics processing unit (PPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a microcontroller, or any other logic unit or combination thereof. The memory <NUM> may be any combination of volatile and non-volatile memory. The memory <NUM> may store non-transitory computer-readable instructions for implementing the map layer display system <NUM>, as discussed in further detail below. The processor <NUM> and a memory <NUM> may be dedicated to the map layer display system <NUM> or may be shared by one or more other systems in the MCDU <NUM>.

The memory <NUM> may further store data corresponding to different layers on a map. The layers may include, for example, terrain data, traffic data, flight plan data, fixes (airports, VHF omnidirectional range (VOR), non-directional beacon (NDB) locations, intersections, VOR courses), airspaces, boundaries, gridlines, and the like. Different displays <NUM> may have different layers depending upon what each display is capable of displaying. The map layer display system <NUM> fades-in and fades-out layers on the display during range changes, pan changes and display option changes. The display option changes may occur when a user adds or removes a layer from the map using a user interface <NUM>. The user interface <NUM> may include any combination of a touch screen, a mouse, a trackpad, a trackball, a microphone, buttons, switches, or the like.

As an example, a user could select to remove traffic data from a lateral situation display map. Instead of a sudden shift reflecting the new option, the layer corresponding to the traffic data would fade-out. This fading-in and fading-out improves the user's experience by giving them a better appreciation of the change by giving them enough time to visualize the data that is fading in or out. Visual Aesthetics or "look and feel" is one of the most important features of any graphical user interface. Better aesthetics makes the interface user-friendlier and more popular. Better aesthetics helps the user to understand the meaning of various components and memorize the navigation paths. A better look and feel ultimately makes a GUI more efficient and effective.

The processor <NUM> may perform the gradual fade-in and fade-out of layers using an animated fade-in or fade-out technique, where previous state/scene/layers gets faded in or out slowly and a new scene is rendered smoothly. This makes the whole state/scene/layer smoothly transition. To achieve the smooth fade-in or fade-out transition, the processor <NUM> decreases opaqueness and size of a layer (e.g., last icon/symbol) gradually while the same time opaqueness and size of any new layer (e.g., layer which was underneath a removed layer or new icon/symbol/layers) increases gradually until it reaches to a desired opaqueness and size. The rate at which the layer transparency transitions from one state to the other can be a constant or the rate of transition can be controlled by an event such as a threat condition that becomes present within one of the layers.

For any terrain changes from, for example, a pan or a zoom request, the processor <NUM> generates instructions for the display <NUM> to fade out the old terrain data and gradually introduce the new terrain data with some blurriness effect to provide a smooth fade in fade out transition during abrupt terrain scene changes. In one embodiment, for example, the processor <NUM> may blend the existing terrain layer with the new terrain layer to achieve the effect. The change in opaqueness of each layer may be performed on a frame-by-frame basis. In other words, the processor <NUM> may increase/decrease the opaqueness of a layer gradually over multiple frames of a display.

<FIG> show flowcharts for a method for generating an animated display with layers in accordance with one embodiment. Specifically, the flow diagrams illustrate how the system may add or remove a layer. As seen in <FIG>, the process starts upon receiving a request to change a layer that is being displayed <NUM>. The change may be to pan a display, zoom a display, or add or remove layers from a display. <FIG> reflects the process <NUM> of adding a layer, while <FIG> reflects the process <NUM> of removing a layer.

When a layer is to be added <NUM>, the transparency of the layer is initially set to zero <NUM>. By initially setting the transparency to zero (corresponding to <NUM>% transparent), abrupt changes to the display are prevented. The processor processes a logic loop where each time through the logic loop, the opaqueness of the respective layer is increased <NUM> by a predetermined fade delta (i.e., rate of change by a predetermined amount of increase) until the transparency equals one (corresponding to <NUM>% opaqueness) <NUM>. As the processor goes though the loop, the processor continually displays the respective layers according to their transparency values <NUM>.

Likewise, when a layer is to be removed <NUM> as shown <FIG>, the transparency of the layer is initially set to one <NUM>. By initially setting the transparency to one (corresponding to <NUM>% opaqueness), abrupt changes to the display are prevented. The processor then processes a logic loop where each time through the logic loop, the opaqueness of the respective layer is decreased <NUM> by a predetermined "fade delta" (i.e., rate of change by a predetermined amount of decrease) until the transparency equals zero <NUM> (corresponding to <NUM>% opaqueness). As the processor goes though the loop, the processor continually displays the respective layers according to their transparency values <NUM>.

By controlling the fade delta, the processor can control how quickly the respective layer is added or removed from the display. For example, the fade delta may be user specific. In other words, each pilot or operator can define the rate at which layers are added or removed to the display. Fade delta values can be a constant or can be event driven based on events during aircraft operations. In other examples, some display features such as a traffic symbol may not be displayed when flight crews are performing long range planning tasks on a map since these types of targets are not typically discernable on map at long range. When a traffic alert event is present, the fade delta for turning on traffic display in response to the event will become instantaneous, thus allowing immediate visualization of the layer.

Techniques and technologies may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. Such operations, tasks, and functions are sometimes referred to as being computer-executed, computerized, software-implemented, or computer-implemented. In practice, one or more processor devices can carry out the described operations, tasks, and functions by manipulating electrical signals representing data bits at memory locations in the system memory, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions.

When implemented in software or firmware, various elements of the systems described herein are essentially the code segments or instructions that perform the various tasks. The program or code segments can be stored in a processor-readable medium or transmitted by a computer data signal embodied in a carrier wave over a transmission medium or communication path. The "computer-readable medium", "processor-readable medium", or "machine-readable medium" may include any medium that can store or transfer information. Examples of the processor-readable medium include an electronic circuit, a semiconductor memory device, a ROM, a flash memory, an erasable ROM (EROM), a floppy diskette, a CD-ROM, an optical disk, a hard disk, a fiber optic medium, a radio frequency (RF) link, or the like. The computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels, optical fibers, air, electromagnetic paths, or RF links. The code segments may be downloaded via computer networks such as the Internet, an intranet, a LAN, or the like.

The following description refers to elements or nodes or features being "connected" or "coupled" together. As used herein, unless expressly stated otherwise, "coupled" means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically. Likewise, unless expressly stated otherwise, "connected" means that one element/node/feature is directly joined to (or directly communicates with) another element/node/feature, and not necessarily mechanically. Thus, additional intervening elements, devices, features, or components may be present in an embodiment of the depicted subject matter.

Claim 1:
A system for generating an animated display for an aircraft (<NUM>), comprising:
a flight management system (<NUM>) configured to control one or more control systems of the aircraft (<NUM>) based upon flight plan data for the aircraft (<NUM>); and
a map layer display system (<NUM>) that is controlled by the flight management system (<NUM>), comprising:
a plurality of displays (<NUM>) installed onboard the aircraft, in the cockpit, where each of the plurality of displays (<NUM>) shows a different view of the flight plan data;
a user interface system (<NUM>) configured to receive user input; and
a processor (<NUM>) communicatively coupled to the plurality of displays (<NUM>) and the user interface system (<NUM>), the processor (<NUM>) configured to:
determine when the user input received by the user interface system (<NUM>) corresponds to a layer on one of the plurality of displays (<NUM>);
increase opaqueness of the layer from zero percent to one-hundred percent at a predetermined rate of change when the user input includes a request to add the layer to one of the plurality of displays (<NUM>), where the opaqueness is increased at the predetermined rate of change by processing a logic loop, wherein each time through the logic loop the opaqueness increases by a predetermined fade delta which represents the rate of change to the opaqueness of a value of less than <NUM>%;
decrease opaqueness of the layer from one-hundred percent to zero-percent at a predetermined rate of change when the user input includes a request to remove the layer from one of the plurality of displays (<NUM>), where the opaqueness is decreased at the predetermined rate of change by processing a logic loop, wherein each time through the logic loop the opaqueness decreases by the predetermined fade delta which represents the rate of change to the opaqueness of a value less than <NUM>%; and wherein the processor is further configured to override the predetermined rate of change of opaqueness when a threat condition to the aircraft is detected in one of the layers such that the change in opaqueness is instantaneous and the layer in which the threat condition is detected is visualized immediately; and
generate instructions to display the layer at the opaqueness of the layer.