Patent Description:
Flight recorders such as aviation cockpit voice and flight data recorders (sometimes called 'black box' recorders) are used to acquire and store information about the operation and status of an aircraft during a flight. This information can be analyzed in response to an unexpected event or accident involving the aircraft. Flight recorders are installed on certain aircraft, typically large or passenger carrying aircraft, and conform to international aviation authority standards. For example, flight recorders are mandated for commercial aircraft by the Federal Aviation Administration (FAA) in the United Stated (U. ), and the European Union Aviation Safety Agency (EASA) in the European Union,.

Typically, the flight recorders used in large commercial aircraft continually monitor the current operating conditions and performance of the aircraft via a large number of sensors located around the aircraft. Data from these sensors can be fed into a flight data acquisition unit (FDAU) which provides the data to the flight data recorder. Some sensor data can also be provided directly to the flight recorder. Typical examples of information stored on the flight data recorder include position, speed, altitude, engine speed and rudder position, however modern flight data recorders can often track, store, and analyze hundreds of parameters.

<CIT> relates to an integrated system for improved vehicle maintenance and safety. <CIT> relates to a data collection and reproduction system. <CIT> relates to onboard maintenance system network optimization. <CIT> relates to a re-configurable multipurpose analog interface.

The invention is defined by a flight recorder system according to claim <NUM>.

In another aspect, the invention is defined by a method according to claim <NUM>.

A full and enabling disclosure of the present description, including the best mode thereof, directed to one of ordinary skill in the art, is set forth in the specification, which refers to the appended FIGS. , in which:.

For purposes of illustration and discussion, the present disclosure will be described with respect to a flight recorder system for an aircraft. It will be understood that the disclosure can have applicability in other vehicles or systems, and can be used to provide benefits in industrial, commercial, and residential applications that use or require recorded data.

The exemplary drawings are for purposes of illustration only and the dimensions, positions, order and relative sizes reflected in the drawings attached hereto can vary.

As used herein, all directional references (e.g., radial, axial, upper, lower, upward, downward, left, right, lateral, front, back, top, bottom, above, below, vertical, horizontal, clockwise, counterclockwise) are only used for identification purposes to aid the reader's understanding of the disclosure, and do not create limitations, particularly as to the position, orientation, or use thereof. Connection references (e.g., attached, coupled, connected, and joined) are to be construed broadly and can include intermediate members between a collection of elements and relative movement between elements unless otherwise indicated. As such, connection references do not necessarily infer that two elements are directly connected and in fixed relation to each other. In non-limiting examples, connections or disconnections can be selectively configured to provide, enable, disable, or the like, an electrical connection or communicative connection between respective elements. Furthermore, as used herein, the term "set" or a "set" of elements can be any number of elements, including only one.

As used herein, a "controller" or "controller module" can include a component configured or adapted to provide instruction, control, operation, or any form of communication for operable components to affect the operation thereof. A controller module can include, without limitation, any known processor, microcontroller, System-on-Chip (SoC), or logic devices. Such logic devices can include but are not be limited to: Field Programmable Gate Arrays (FPGA), a Complex Programmable Logic Device (CPLD), an Application-Specific Integrated Circuit (ASIC), a Full Authority Digital Engine Control (FADEC), a Proportional Controller (PC), a Proportional Integral Controller (PI), a Proportional Derivative Controller (PD), a Proportional Integral Derivative Controller (PID), a hardware-accelerated logic controller (e.g. for encoding, decoding, transcoding, etc.), the like, or a combination thereof.

Non-limiting examples of a controller module can be configured or adapted to run, operate, or otherwise execute program code to effect operational or functional outcomes, including carrying out various methods, functionality, processing tasks, calculations, comparisons, sensing or measuring of values, or the like, to enable or achieve the technical operations or operations described herein. The operation or functional outcomes can be based on one or more inputs, stored data values, sensed or measured values, true or false indications, or the like. As used herein, the terms "program code" "software", and "firmware" can be used interchangeably, and can be used to describe operable or executable instruction sets that can include routines, programs, code, bit streams, objects, components, data structures, algorithms, etc., that have the technical effect of performing particular tasks or implementing particular abstract data types. When implemented in software or firmware, various aspects as described herein can include code segments or instructions that perform the various tasks. It should be appreciated that the various block components shown in the figures can be realized by any number of hardware, software, or firmware components, or combinations thereof, configured to perform the specified functions.

In another non-limiting example, a controller module can also include a data storage component accessible by the processor, including memory, whether transition, volatile or non-transient, or non-volatile memory. Additional non-limiting examples of the memory can include Random Access Memory (RAM), Read-Only Memory (ROM), flash memory, or one or more different types of portable electronic memory, such as discs, DVDs, CD-ROMs, flash drives, Universal Serial Bus (USB) drives, the like, or any suitable combination of these types of memory. In one example, the program code can be stored within the memory in a machine-readable format accessible by the processor. Additionally, the memory can store various data, data types, sensed or measured data values, inputs, generated or processed data, or the like, accessible by the processor in providing instruction, control, or operation to affect a functional or operable outcome, as described herein.

Flight recorder devices are typically electronic recording devices or modules installed in an aircraft to facilitate the investigation of aviation accidents and incidents. The flight recorder devices can include a set of fixed aircraft components, such as a set of line-replaceable units (LRUs). Typically, the flight recorder LRU can comprise a combined cockpit voice and flight data recorder with an integrated crash survivable recording subsystem. Alternatively, the flight recorder LRU can comprise a flight data acquisition unit that receives and processes audio and flight data, and a separate LRU containing the crash survivable recording subsystem. Flight recorder devices can typically include a flight data recorder (FDR) which saves or stores data relevant to the recent history of a flight by recording of dozens of parameters collected several times per second. For example, during normal flight operations, the FDR captures specific aircraft performance parameters such as airspeed, altitude, vertical acceleration, time, nose heading, steering wheel position, rudder pedal position, steering wheel position, horizontal stabilizer, and fuel flow. Flight recorder devices can also include a cockpit voice recorder (CVR) which saves the recent history of the sounds in the cockpit during a flight, including conversations between ground controllers and aircraft crew. The FDR and CVR devices can be combined into a single unit. The FDR and CVR can include an electronic interface and a housing that encloses each circuit, and can include a crash survivable memory unit (CSMU). The CSMU typically includes has a non-volatile memory for storing flight data and voice data. Other flight recorder devices or modules such as data analytics modules (DA) can be arranged to receive flight data corresponding to various predetermined flight parameters from various devices including other flight recorder modules in the flight recorder system, and can include a dedicated processor to perform an analysis of the data. The analysis can be conducted during flight by the DA, or post-flight. Flight recorder devices can include any number of devices or modules configured to capture data indicative of any desired number of parameters relative to the aircraft, including detected, measured, sensed, calculated, derived, or otherwise determined data.

<FIG> depicts an aircraft <NUM> that provides an environment for different aspects of the disclosure. The aircraft <NUM> can fly a route from one location to another (i.e., a flight) and can include one or more propulsion engines <NUM> coupled to a fuselage <NUM>. A cockpit <NUM> can be positioned in the fuselage <NUM> and wing assemblies <NUM> can extend outwardly from the fuselage <NUM>. Further, a set of aircraft systems <NUM> that enable proper operation of the aircraft <NUM> can be included as well as a controller or computer <NUM>, and a communication system having a communication link <NUM>. A first user interface is illustrated, by way of non-limiting example, as a display <NUM> that is communicatively coupled to or formed with the computer <NUM>. The display <NUM> can be any user interface, screen, or known computer system or combination or computer systems that can communicate or otherwise provide an output to one or more users (e.g., a pilot) of the computer <NUM>. It is contemplated that the display <NUM> can also obtain or receive input from the one or more users of the computer <NUM>. In non-limiting aspects, the computer <NUM> can comprise a Flight Management System (not shown).

The set of aircraft systems <NUM> can reside within the cockpit <NUM>, within the electronics and equipment bay (not shown), as well as in other locations throughout the aircraft <NUM>. Such aircraft systems <NUM> can include but are not limited to an electrical system, an oxygen system, hydraulics or pneumatics system, a fuel system, a propulsion system, FMS, flight controls, audio/video systems, an Integrated Vehicle Health Management (IVHM) system, and systems associated with the mechanical structure of the aircraft <NUM>. As discussed in more detail herein, in aspects, the set of aircraft systems <NUM> can include a flight recorder system <NUM>.

The computer <NUM> can be operably coupled to the set of aircraft systems <NUM> and it is contemplated that the computer <NUM> can aid in operating the set of aircraft systems <NUM> and can receive information from the set of aircraft systems <NUM>. The computer <NUM> can also be connected with other controllers or computers of the aircraft <NUM>.

The computer <NUM> can include memory <NUM>, the memory <NUM> can include Random Access Memory (RAM), Read-Only Memory (ROM), flash memory, or one or more different types of portable electronic memory, such as discs, Digital Versatile disks (DVD), Compact Disc- Read-Only Memory (CD-ROMs), etc., or any suitable combination of these types of memory. The computer <NUM> can include one or more controller modules or processors <NUM>, which can be running any suitable programs. It will be understood that the computer <NUM> can include or be associated with any suitable number of individual microprocessors, power supplies, storage devices, interface cards, auto flight systems, flight management computers, controller modules, and other standard components and that the computer <NUM> can include or cooperate with machine executable code, any number of software (also sometimes called "firmware") programs (e.g., flight management programs), or other instructions designed to carry out the various methods, process tasks, calculations, and control/display functions necessary for operation of the aircraft <NUM>. While not illustrated, it will be understood that any number of sensors or other systems can also be communicatively or operably coupled to the computer <NUM> to provide information thereto or receive information therefrom.

The flight recorder system <NUM> can include a set of fixed aircraft components, such as a set of line-replaceable units (LRUs) <NUM> which can define networking end nodes (also referred to as "end stations" and "end systems"), or modular components of the aircraft <NUM>. The LRUs <NUM> can include respective control modules and be configured to operate according to a particular operation, interoperability, or form factor standards, such as those defined by ARINC664 series or Mil-Std-1553B, standards, for example. In the exemplary aspects illustrated, the aircraft computer <NUM> can be positioned near the nose or cockpit of the aircraft <NUM> while the LRUs <NUM> can be positioned throughout the aircraft <NUM>. The aircraft computer <NUM> and LRUs <NUM> can be configured to be communicatively coupled by way of a data communication network <NUM>. The data communication network <NUM> can comprise a series of data transmission pathways <NUM>, including network bridges or switches (not shown). The data transmission pathways <NUM> can include a physical connection between the respective components or end nodes of the network <NUM> such as the computer <NUM> and LRUs <NUM>. In non-limiting aspects, the physical connection can comprise a wired connection such as Ethernet, or can include wireless transmission connections including, but not limited to, WiFi (e.g. <NUM> networks), Bluetooth, and the like. Collectively, the aircraft computer <NUM>, LRUs <NUM>, data transmission pathways <NUM>, and network switches can form the avionics data network for the aircraft <NUM>.

The LRUs <NUM> can include, for example, entirely contained systems, sensors, instruments, cameras, recorders, processors, or other auxiliary equipment to manage or operate flight recorder functions. At least a set of LRUs <NUM> can, for example, generate data, which can be modified, computed, or processed prior to, or in preparation for, packaging the data into data frames to be transmitted over the avionics data network by way of the data transmission pathways <NUM>. In non-limiting aspects another set of LRUs <NUM> can consume the data transmitted over the avionics data network. In some instances, the aircraft computer <NUM> or LRU <NUM>, or both, can operate to generate or consume data, or both. As used herein, "consume," "consuming," or "consumption" of data will be understood to include, but is not limited to, performing or executing a computer program, routine, calculation, analysis, function, or process on at least a portion of the data, storing the data in memory, or otherwise making use of at least a portion of the data.

The communication link <NUM> can be communicably coupled to the computer <NUM> or other control modules or processors of the aircraft to transfer information to and from the aircraft <NUM>. It is contemplated that the communication link <NUM> can be a wireless communication link and can be any variety of communication mechanism capable of wirelessly linking with other systems and devices and can include, but is not limited to, satellite uplink, SATCOM internet, very high frequency (VHF) Data Link (VDL), ACARS network, Automatic Dependent Surveillance-Broadcast (ADS-B), Wireless Fidelity (WiFi), WiMax, <NUM> wireless signal, Code Division Multiple Access (CDMA) wireless signal, Global System for Mobile communication (GSM), <NUM> wireless signal, Long Term Evolution (LTE) signal, <NUM> wireless signal or any combinations thereof. It will also be understood that the particular type or mode of wireless communication is not critical to the disclosure, and later-developed wireless networks are certainly contemplated as within the scope of the current disclosure. Further, the communication link <NUM> can be communicably coupled with the computer <NUM> through a wired link without changing the scope of the aspects as described herein. Although only one communication link <NUM> has been illustrated, it is contemplated that the aircraft <NUM> can have multiple communication links <NUM> communicably coupled with the computer <NUM>. Such multiple communication links can provide the aircraft <NUM> with the ability to transfer information to or from the aircraft <NUM> in a variety of ways.

<FIG> illustrates a functional block diagram of a non-limiting aspect of a flight recorder system <NUM>. The flight recorder system <NUM> can include the LRU <NUM> comprising a set of flight recorder modules (FRM) <NUM>. As depicted, in some aspects, the set of FRM <NUM> can include at least one of a cockpit voice recorder module (CVR) <NUM>, a flight data recorder module (FDR) <NUM>, and a data analytics module (DA) <NUM>. In some aspects the set of FRM <NUM> can include a crash-survivable recorder module (CSR) <NUM>. It is contemplated that in other aspects, the set of FRM <NUM> can optionally include any number of other FRM (not shown) directed to data collection and recording of other desired aircraft performance and operational data. It will be appreciated that, in non-limiting aspects, the set of FRM <NUM> can comprise individual LRUs. In other aspects the set of FRM <NUM> can be combined into fewer physical entities, for example by combining the respective functions of the FRM <NUM> onto one or more circuit card assemblies (not shown).

A resource controller module (RCM) <NUM> can be communicatively coupled, via a data communication network <NUM> comprising a switch fabric <NUM>, and a set of communication links <NUM> to the set of FRM <NUM>. The RCM <NUM> can also be communicatively coupled to a data bus (not shown) of the aircraft via a data bus interface <NUM>. In non-limiting aspects, the data communications network <NUM> can comprise a data communications network of the flight recorder system <NUM>. According to the invention, the data communications network <NUM> comprises a data communications network of the aircraft <NUM>. For example, in non-limiting aspects, the set of FRM <NUM> can comprise a CSR that is arranged as a separate LRU. In non-limiting aspects, another FRM <NUM>, such as one or more of the CVR, FDR, or DA can be communicatively coupled to the CSR via the aircraft data communication network.

Each FRM <NUM> includes a respective local memory. For example, the CVR <NUM> can include a local CVR memory <NUM>, the FDR <NUM> can include a local FDR memory <NUM>, the DA <NUM> can include a local DA memory <NUM>, and the CSR <NUM> can include a local CSR memory <NUM>. Each respective local memory <NUM>, <NUM>, <NUM>, <NUM> is arranged as a sharable memory. For example, each respective local memory <NUM>, <NUM>, <NUM>, <NUM> can be configured to provide a uniform memory access (UMA), non-uniform memory access (NUMA), or cache-only memory architecture (COMA) access. The respective local memory <NUM>, <NUM>, <NUM>, <NUM> can include Random Access Memory (RAM), Read-Only Memory (ROM), flash memory, or one or more different types of portable electronic memory, such as discs, Digital Versatile disks (DVD), Compact Disc- Read-Only Memory (CD-ROMs), etc., or any suitable combination of these types of memory.

Each FRM <NUM> includes a respective control module or processor. For example, the CVR <NUM> can include a CVR control module <NUM>, the FDR <NUM> can include a FDR control module <NUM>, the DA <NUM> can include a DA control module <NUM>, and the CSR <NUM> can include a CSR control module <NUM>. Each respective control module <NUM>, <NUM>, <NUM>, <NUM> can be configured to run any suitable programs or program code. While not shown, it will be understood that each FRM <NUM> can include or be associated with any suitable number of individual microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components and that the respective FRM <NUM> can include or cooperate with machine executable code, any number of software programs (e.g., data recording programs), or other instructions designed to carry out the various methods, process tasks, calculations, and control/display functions necessary for the intended operation of the respective FRM <NUM>. The respective control module <NUM>, <NUM>, <NUM>, <NUM> can include any known processor, microcontroller, or logic device, including, but not limited to: Field Programmable Gate Arrays (FPGA), a Complex Programmable Logic Device (CPLD), an Application-Specific Integrated Circuit (ASIC), a Full Authority Digital Engine Control (FADEC), a Proportional Controller (P), a Proportional Integral Controller (PI), a Proportional Derivative Controller (PD), a Proportional Integral Derivative Controller (PID), a hardware-accelerated logic controller (e.g. for encoding, decoding, transcoding, etc.), the like, or a combination thereof. For example, in non-limiting aspects, the respective controller module <NUM>, <NUM>, <NUM>, <NUM> can comprise a respective set of FPGA (not shown) having addressable memory-mapped registers.

Each FRM <NUM> comprises a respective set of input and output (I/O) ports communicatively coupled to the switch fabric <NUM>. For example, the CVR <NUM> can include a set of CVR I/O ports <NUM>, the FDR <NUM> can include a set of FDR I/O ports <NUM>, the DA <NUM> can include a set of DA I/O ports <NUM>, and the CSR <NUM> can include a set of CSR I/O ports <NUM>. Each of the respective I/O ports <NUM>, <NUM>, <NUM>, <NUM> is communicatively coupled to the data communication network <NUM>. In aspects, each respective I/O ports <NUM>, <NUM>, <NUM>, <NUM> can comprise a memory-mapped I/O port.

In non-limiting aspects, the data communication network <NUM> can define a network mesh or switch fabric <NUM> comprising a set of communicatively coupled network switches or bridges (not shown) such as Ethernet switches. In non-limiting aspects, the data communication network <NUM> can be configured in accordance with time-sensitive network (TSN) schema to communicate data using standard methods for time synchronization and traffic management, allowing deterministic communication over a standard Ethernet network. The data communication network <NUM> can comprise any desired communication bus or bus topology that would enable aspects to operate as described herein. For example, in non-limiting aspects, the data communication network <NUM> can comprise a high-speed serial bus compliant with a Peripheral Component Interconnect Express (PCIe) schema. In such non-limiting aspects having a PCIe compliant point-to-point topology, the set of separate respective links <NUM> can communicatively couple each FRM <NUM> to the switch fabric <NUM> to enable full-duplex communication of data packets between any two end nodes (e.g., the FRM <NUM> or RCM <NUM>), with no inherent limitation on concurrent access between multiple end nodes. In non-limiting aspects, the set of links <NUM> can communicatively couple one or more FRM <NUM> to the RCM <NUM>, the switch fabric <NUM>, data bus interface <NUM>, the data bus (not shown) of the aircraft, various data acquisition devices (not shown) of the aircraft, or any combination thereof. The set of links <NUM> can comprise any one or more of serial links, parallel data bus links, or other conventional communication links. It will be understood that aspects employing a PCIe schema can be programmed to detect and configure the FRM <NUM> devices when communicatively coupled to the data communication network <NUM>. It will be further understood that in some instances, the FRM <NUM> devices can comprise a "pre-configured" or default functionality or operation, and aspects can be programmed to automatically detect and re-configure the FRM <NUM> devices via the RCM <NUM> when communicatively coupled to the data communication network <NUM>.

The RCM <NUM> can comprise a respective local memory <NUM> and a controller module <NUM>. The RCM memory <NUM> can include Random Access Memory (RAM), Read-Only Memory (ROM), flash memory, or one or more different types of portable electronic memory, such as discs, Digital Versatile disks (DVD), Compact Disc- Read-Only Memory (CD-ROMs), etc., or any suitable combination of these types of memory. In some aspects, the RCM local memory <NUM> can be configured as a shareable memory.

The RCM <NUM> control module <NUM> can be configured to run any suitable programs or program code to enable aspects to operate as described herein. While not shown, it will be understood that each RCM <NUM> can include or be associated with any suitable number of individual microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components and that the respective RCM <NUM> can include or cooperate with machine executable code, any number of software programs (e.g., data recording programs), or other instructions designed to carry out the various methods, process tasks, calculations, and control/display functions necessary for the intended operation of the respective RCM <NUM>. The RCM <NUM> can include any known processor, microcontroller, or logic device, including, but not limited to: Field Programmable Gate Arrays (FPGA), a Complex Programmable Logic Device (CPLD), an Application-Specific Integrated Circuit (ASIC), a Full Authority Digital Engine Control (FADEC), a Proportional Controller (P), a Proportional Integral Controller (PI), a Proportional Derivative Controller (PD), a Proportional Integral Derivative Controller (PID), a hardware-accelerated logic controller (e.g. for encoding, decoding, transcoding, etc.), the like, or a combination thereof.

The RCM <NUM> can be communicatively coupled to a data bus or data communication network (not shown) of the aircraft <NUM> via a data bus interface <NUM>. The flight recorder system <NUM> can receive or collect data from the data bus or data communication network of the aircraft <NUM> and provide the data to one or more of the FRM <NUM>. For example, in non-limiting aspects the data can be provided via the RCM <NUM> or the switch fabric <NUM> or a combination thereof. In non-limiting aspects, the RCM <NUM> can receive or collect data from the data bus or data communication network of the aircraft <NUM> during a flight of the aircraft. For example, the RCM <NUM> can receive data from the data bus of the aircraft <NUM> that is indicative of a current phase or stage of a flight of the aircraft. In such aspects, the RCM <NUM> can be programmed to configure an operation of the switch fabric <NUM> based on the indicated phase or stage of a flight of the aircraft. Further, in such aspects, the RCM <NUM> can optionally be programmed to configure a first operation of at least one of the switch fabric <NUM> and a first FRM <NUM> based on a first phase of a flight, and to configure a second operation of at least one of the switch fabric <NUM> and the first FRM <NUM> based on a second phase of a flight. As used herein, the term "configure an operation" (such as a first operation or a second operation) can include "re-configuring an operation", for example in an instance where a particular FRM comprises a default operation or pre-configured function or operation. In some aspects, the flight recorder system <NUM> can receive commands from the computer <NUM> via the data bus or data communication network of the aircraft <NUM> to which it can respond. In some aspects, the flight recorder system <NUM> can provide data from one or more of the FRM <NUM> to the cockpit display <NUM>.

The RCM <NUM> is communicatively coupled, via the data communication network <NUM>, to the set of FRM <NUM>. The RCM <NUM> is configured to detect a FRM <NUM> connected to the switch fabric <NUM>. In response to the detection of a particular FRM <NUM> connected to the switch fabric <NUM>, the RCM <NUM> can be programmed to execute (e.g., via a "plug-and-play" process or executable program code) to configure an operation of the detected FRM <NUM>. It will be appreciated that because the configuration of the operation of the FRM <NUM> by the RCM <NUM> can be based on the detection of the FRM <NUM> by the RCM <NUM>, the operation of the FRM <NUM> can be dynamically configured by the RCM <NUM> during a flight of the aircraft, and need not necessarily be done only during a pre-flight or post-flight scheduled maintenance.

The detection by the RCM <NUM> of a particular FRM <NUM> connected to the switch fabric <NUM> can further include a determining, by the RCM <NUM>, of the detected FRM <NUM> type. For example, in the event the RCM <NUM> detects that a particular FRM <NUM> has been communicatively coupled to the switch fabric <NUM>, the RCM <NUM> can be programmed to determine whether the detected FRM <NUM> is one of a CVR <NUM>, FDR <NUM>, DA <NUM>, CSR <NUM>, or some other type of FRM <NUM>. In still other aspects, the detection or determination of a particular FRM <NUM> connected to the switch fabric <NUM> can further include a determining, by the RCM <NUM> of a count or number of the available respective I/O ports <NUM>, <NUM>, <NUM>, <NUM> of the detected FRM <NUM>. In an aspect, based on the detection of the particular detected FRM <NUM> communicatively coupled to the switch fabric <NUM>, and the determination of the detected FRM <NUM> type and number of available memory-mapped I/O ports <NUM>, <NUM>, <NUM>, <NUM> of the detected FRM <NUM>, the RCM <NUM> can be further programmed to dynamically configure the operation of the detected FRM <NUM>. Additionally, the RCM <NUM> can be programmed to configure an operation of the switch fabric <NUM> based on the detected FRM <NUM> type. In other non-limiting aspects, the RCM <NUM> can be further programmed to direct or command the detected particular FRM <NUM> to load software or firmware (e.g., FPGA firmware) stored in local non-volatile memory (e.g., flash memory) of the detected particular FRM <NUM>.

In some aspects, the respective local memory <NUM>, <NUM>, <NUM>, <NUM> of each FRM <NUM> communicatively coupled to the data communication network <NUM> can be readable by the RCM <NUM> via the switch fabric <NUM>. Additionally, in non-limiting aspects, at least some data in the respective local memory <NUM>, <NUM>, <NUM>, <NUM> of each FRM <NUM> can be shareable with other FRMs <NUM> communicatively coupled to the data communication network <NUM>. In non-limiting aspects, the RCM <NUM> can be programmed to configure the switch fabric <NUM> to enable access by each FRM <NUM> to any memory-mapped computing resource of the other FRMs <NUM>, such as the respective local memory <NUM>, <NUM>, <NUM>, <NUM>, the respective I/O ports <NUM>, <NUM>, <NUM>, <NUM>, or combination thereof. In this way, the respective local memory <NUM>, <NUM>, <NUM>, <NUM>, or respective ports I/O <NUM>, <NUM>, <NUM>, <NUM> of a first FRM <NUM> can be accessible by a second FRM <NUM> without a cooperation or participation of the respective control module <NUM>, <NUM>, <NUM>, <NUM> of the first FRM <NUM>. For example, in non-limiting aspects, the FRM <NUM> can include a DA <NUM> configured to analyze data received from the respective local memory of the at least one of the CVR <NUM> and FDR <NUM> during a flight of the aircraft, using the DA control module <NUM> without need of cooperation with the respective control module <NUM>, <NUM> of the CVR <NUM> and FDR <NUM>.

<FIG> illustrates a non-limiting example of a method <NUM> of operating the flight recorder system <NUM> of an aircraft <NUM>. The method <NUM> can be performed while the aircraft <NUM> is in-flight, pre-flight (e.g., prior to executing a flight plan), or post-flight (e.g., subsequent to a flight). Although described in terms of a flight recorder system <NUM>, it will be appreciated that the method <NUM> can be applied to any suitable avionics device configured to save data to a memory and communicate with any other suitable other avionics device.

The flight recorder system can include a first FRM <NUM> having a first local memory <NUM>-<NUM> and a first set of memory-mapped I/O ports <NUM>-<NUM> and a second FRM <NUM>, having a second local memory <NUM>-<NUM> and a second set of memory-mapped I/O ports <NUM>-<NUM>. In non-limiting aspects, the first FRM <NUM> can include at least one of a CVR <NUM>, a FDR <NUM>, a DA <NUM>, and a CSR <NUM>. In non-limiting aspects, the second FRM <NUM> can include at least one of a CVR <NUM>, a FDR <NUM>, a DA <NUM>, and a CSR <NUM>. It is contemplated that in other aspects, first FRM <NUM>, or the second FRM <NUM>, or both, can optionally include any number of other FRM <NUM> configured for data collection or recording of other desired aircraft performance and operational data. An RCM <NUM> can be communicatively coupled, via a data communication network <NUM> comprising a switch fabric <NUM>, to the first FRM <NUM> and second FRM <NUM>. The RCM <NUM> can also be communicatively coupled to a data bus of the aircraft (not shown) via a data bus interface <NUM>.

The method <NUM> can include communicatively coupling the RCM <NUM> to the switch fabric <NUM> of a data communications network <NUM>, and communicatively coupling the first FRM <NUM> and second FRM <NUM> to the switch fabric, at <NUM>. In a non-limiting aspect, the data communications network <NUM> can comprise a data communications network <NUM> of the flight recorder system <NUM>. According to the invention, the data communications network <NUM> comprises a data communications network of the aircraft <NUM>. For example, in non-limiting aspects, one of the first FRM <NUM> and second FRM <NUM> can comprise a CSR <NUM> that is arranged a separate LRU. In such aspects, the other of the first FRM <NUM> and second FRM <NUM> can be communicatively coupled to the CSR <NUM> via the aircraft data communication network <NUM>. In still other aspects, the first FRM <NUM> can be communicatively coupled to other discrete sensors or devices, such as but not limited to, tachometers, strain gauges and the like, to receive data therefrom. The method <NUM> includes, at <NUM>, detecting by the RCM <NUM>, the first FRM <NUM>, and at <NUM>, reading, by the RCM <NUM> at least one of the first local memory and the first memory-mapped I/O ports of the first FRM <NUM>. The detecting by the RCM, of the first FRM at <NUM> can include at least one of a determination of the first FRM <NUM> type and a number of I/O ports of the first FRM <NUM>.

Next, the method <NUM> includes configuring, by the RCM <NUM>, an operation of the first FRM <NUM>, at <NUM>, providing data to the first FRM210, at <NUM>, and saving a first portion of the data to the local memory of the first FRM, at <NUM>. In various non-limiting aspects, the data can be provided to the first FRM <NUM> via the RCM <NUM>, the switch fabric <NUM>, the data communication network <NUM>, other devices or sensors, or any combination thereof. The method <NUM> can also include providing, by the first FRM <NUM>, a second portion of the data to the second FRM <NUM> at <NUM>.

In non-limiting aspects, the method <NUM> can include instructing, by the RCM <NUM>, the first FRM <NUM> to load firmware stored in a local memory <NUM>-<NUM>, at <NUM>, and at <NUM>, configuring the switch fabric <NUM> to enable the first FRM <NUM> to access the local memory <NUM>-<NUM> of the second FRM <NUM>. In aspects, the configuring the switch fabric at <NUM> can optionally be done during a flight of the aircraft.

Non-limiting aspects of the method <NUM> can further include configuring, by the RCM <NUM>, an operation of the switch fabric <NUM> based on the determined FRM <NUM> type, at <NUM>. The configuring, by the RCM <NUM>, of an operation of the switch fabric <NUM> based on the determined FRM <NUM> type, at <NUM> can optionally be done during a flight of the aircraft.

The sequences depicted are for illustrative purposes only and is not meant to limit the method <NUM> in any way as it is understood that the portions of the method can proceed in a different logical order, additional or intervening portions can be included, or described portions of the method can be divided into multiple portions, or described portions of the methods can be omitted without detracting from the described method. For example, the method <NUM> can include various other intervening steps. The examples provided herein are meant to be non-limiting.

It is contemplated that aspects of this disclosure can be advantageous for use over conventional systems or methods for configuring and operating a flight recorder. Aspects of this disclosure reduce workload of a pilot or maintenance crew in configuring a flight recorder. For example, when adding, installing or reconfiguring a flight recorder module in-flight. This is particularly advantageous in the case of Single Pilot Operations (SPO) or Reduced Crew Operations (RCO).

It is further contemplated that aspects of this disclosure can advantageously provide a more adaptable structure over conventional flight recorders and systems. Aspects as described herein can more readily support multiple configurations of flight recorders modules using a standardized structure, for example, using a common chassis and common backplane. Aspects as described herein can thus advantageously provide a more scalable flight recorder system as compared to conventional systems.

It is additionally contemplated that aspects as described herein more readily enable dynamic configuration of a flight recorder system during a flight than conventional flight recorder systems. For example, flight recorder modules can be added and configured for operation during a flight of the aircraft. Alternatively, flight recorder modules can optionally be configured for different operations based on a phase of flight of the aircraft.

To the extent not already described, the different features and structures of the various embodiments can be used in combination with each other as desired. That one feature is not illustrated in all of the embodiments is not meant to be construed that it may not be included, but is done for brevity of description. Thus, the various features of the different embodiments may be mixed and matched as desired to form new embodiments, whether or not the new embodiments are expressly described. All combinations or permutations of features described herein are covered by this disclosure.

Claim 1:
A flight recorder system (<NUM>) of an aircraft (<NUM>), comprising:
a set of flight recorder system modules, FRM (<NUM>);
a resource controller module, RCM, (<NUM>) communicatively coupled, via a data communication network of the aircraft (<NUM>) defining a switch fabric (<NUM>), to the of flight recorder system modules (<NUM>);
each FRM (<NUM>) comprising a respective control module (<NUM>), (<NUM>), (<NUM>), (<NUM>) a respective local memory (<NUM>), (<NUM>), (<NUM>), (<NUM>), and a respective set of input and output (I/O) ports (<NUM>), (<NUM>), (<NUM>), (<NUM>) communicatively coupled to the switch fabric (<NUM>),
wherein the RCM (<NUM>) is configured to detect a respective FRM (<NUM>) coupled to the switch fabric (<NUM>), and based on the detection, configure an operation of the FRM (<NUM>), and wherein the respective local memory (<NUM>), (<NUM>), (<NUM>), (<NUM>), of the FRM (<NUM>) is readable by the RCM (<NUM>), and shareable with the other FRMs (<NUM>) via the switch fabric (<NUM>).