Flight recorder system and method

Abstract

A flight recorder system of an aircraft includes a resource controller module (RCM) communicatively coupled to a set of flight recorder system modules (FRMs) via a switch fabric. Each FRM includes a respective control module, a respective local memory, and a respective set of input and output (I / O) ports communicatively coupled to the switch fabric. The RCM is configured to detect respective FRMs coupled to the switch fabric and configure operation of the FRMs based on the detection, and wherein the respective local memories of the FRMs are readable by the RCM and are shareable with other FRMs via the switch fabric.

Description

[0001] This application is a divisional application of the invention patent application filed on June 6, 2022, with application number 202210628669.X and invention title "Flight Recorder System and Method". Technical Field

[0002] This disclosure generally relates to aircraft flight recorders, and more specifically to flight recorder systems and methods of operating flight recorders. Background Technology

[0003] Flight data recorders (such as cockpit voice and flight data recorders, sometimes called "black box" recorders) are used to acquire and store information about the aircraft's operation and status during flight. This information can be analyzed in response to unexpected events or accidents involving the aircraft. Flight data recorders are installed on certain aircraft (typically large aircraft or passenger aircraft) and comply with international aviation authority standards. For example, the Federal Aviation Administration (FAA) of the United States and the European Aviation Safety Agency (EASA) of the European Union require commercial aircraft to use flight data recorders.

[0004] Typically, flight recorders used in large commercial aircraft continuously monitor the aircraft's current operating conditions and performance via numerous sensors located around the aircraft. Data from these sensors can be fed to the Flight Data Acquisition Unit (FDAU), which then provides the data to the flight data recorder. Some sensor data can also be provided directly to the flight data recorder. Typical examples of information stored on a flight data recorder include position, speed, altitude, engine speed, and rudder position, but modern flight data recorders can typically track, store, and analyze hundreds of parameters. Summary of the Invention

[0005] This disclosure relates to a flight recorder system for an aircraft. The flight recorder system may include a resource controller module (RCM) communicatively connected to a set of flight recorder system modules (FRMs) via a data communication network defining a switching structure. Each FRM may include a corresponding control module, a corresponding local memory, and a corresponding set of input and output (I / O) ports communicatively connected to the switching structure. The RCM is configured to detect the corresponding FRM connected to the switching structure and to construct the operation of the FRM based on the detection, wherein the corresponding local memory of the FRM can be read by the RCM and can be shared with other FRMs via the switching structure.

[0006] In another aspect, this disclosure relates to a method for operating a flight recorder system of an aircraft, the flight recorder system including a first flight recorder module (FRM) having a first local memory and a first set of memory-mapped I / O ports, and a second FRM having a second local memory and a second set of memory-mapped I / O ports. The method includes: communicatively connecting a resource control module (RCM) to a switching structure; communicatively connecting the first FRM and the second FRM to the switching structure; detecting the first FRM by the RCM; reading at least one of the first local memory and the first memory-mapped I / O ports of the first FRM by the RCM; constructing operations of the first FRM by the RCM; providing data to the first FRM; saving a first portion of the data to the local memory of the first FRM; and retrieving a second portion of the data from the first FRM to the second FRM by the second FRM. Attached Figure Description

[0007] The complete and practical disclosure of this specification, including its best mode, is set forth in the description with reference to the accompanying drawings, for those skilled in the art, wherein:

[0008] Figure 1 This is a schematic diagram of the aircraft and ground systems described in this article.

[0009] Figure 2 Based on the aspects described in this article, it is possible to... Figure 1 A block diagram of a flight recorder system used in conjunction with aircraft and ground systems.

[0010] Figure 3 This is a flowchart illustrating a method for operating a flight recorder system according to the aspects described herein. Detailed Implementation

[0011] For illustrative and discussion purposes, this disclosure is described in relation to a flight recorder system for aircraft. It should be understood that this disclosure is applicable to other vehicles or systems and can provide benefits for industrial, commercial, and residential applications where data is used or required to be recorded.

[0012] The exemplary drawings are for illustrative purposes only, and the dimensions, positions, order, and relative sizes reflected in the accompanying drawings may vary.

[0013] As used herein, all directional references (e.g., radial, axial, up, down, upward, downward, left, right, lateral, front, back, top, bottom, above, below, vertical, horizontal, clockwise, counterclockwise) are for identification purposes only to aid the reader in understanding this disclosure and do not impose limitations, particularly regarding their location, orientation, or purpose. Unless otherwise stated, connection references (e.g., attachment, coupling, connection, and engagement) are to be interpreted broadly and may include intermediate members between sets of elements and relative movement between elements. Therefore, a connection reference does not necessarily imply that two elements are directly connected and have a fixed relationship with each other. In non-limiting examples, connections may be selectively constructed or disconnected to provide, enable, disable, etc., electrical or communication connections between individual elements. Furthermore, as used herein, the term "group" or a "set" of elements can be any number of elements, including a single element.

[0014] As used herein, a “controller” or “controller module” can include components configured or adapted to provide instructions, control, operation, or any form of communication to an operable component to influence its operation. A controller module can include, but is not limited to, any known processor, microcontroller, system-on-a-chip (SoC), or logic device. Such logic devices can include, but are not limited to: field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), application-specific integrated circuits (ASICs), full-authority digital engine control (FADECs), proportional controllers (PCs), proportional-integral controllers (PIs), proportional-derivative controllers (PDs), proportional-integral-derivative controllers (PIDs), hardware-accelerated logic controllers (e.g., for encoding, decoding, transcoding, etc.), and combinations thereof.

[0015] Non-limiting examples of controller modules may be constructed or adapted to run, operate, or otherwise execute program code to achieve operational or functional results, including performing various methods, functions, processing tasks, calculations, comparisons, sensing or measuring values, etc., to enable or implement the technical operations or actions described herein. Operational or functional results may be based on one or more inputs, stored data values, sensed or measured values, true or false indications, etc. As used herein, the terms "program code," "software," and "firmware" are used interchangeably and can be used to describe an operational or executable set of instructions that may include routines, programs, code, bitstreams, objects, components, data structures, algorithms, etc., having the technical effect of performing a particular task or implementing a particular abstract data type. When implemented as software or firmware, the various aspects described herein may include code segments or instructions performing various tasks. It should be understood that the various block components shown in the figures can be implemented by any number of hardware, software, or firmware components, or combinations thereof, configured to perform the specified functions.

[0016] In another non-limiting example, the controller module may also include data storage components accessible to the processor, including memory, whether transient, volatile or non-transient, or non-volatile. Other non-limiting examples of memory may 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, etc., or any suitable combination of these types of memory. In one example, program code may be stored in memory in a processor-accessible, machine-readable format. Furthermore, memory may store various types of data, sensed or measured data values, input, generated or processed data, etc., accessible to the processor when providing instructions, control, or operations to affect functionality or operational outcomes, as described herein.

[0017] Flight recorder devices are typically electronic recording devices or modules installed in aircraft to facilitate the investigation of aviation accidents and incidents. A flight recorder device may include a set of fixed aircraft components, such as a set of line-replaceable units (LRUs). Typically, a flight recorder LRU may include a combined cockpit voice and flight data recorder with an integrated crash survival recording subsystem. Alternatively, a flight recorder LRU may include a flight data acquisition unit that receives and processes audio and flight data, and a separate LRU containing a crash survival recording subsystem. A flight recorder device may typically include a flight data recorder (FDR), which saves or stores data related to the most recent flight history by recording dozens of parameters collected multiple times per second. For example, during normal flight operations, the FDR captures specific aircraft performance parameters such as airspeed, altitude, vertical acceleration, time, heading, steering wheel position, rudder pedal position, horizontal stabilizer position, and fuel flow. A flight recorder device may also include a cockpit voice recorder (CVR), which saves the most recent historical record of sound in the cockpit during flight, including conversations between ground controllers and the aircraft crew. FDR and CVR devices can be combined into a single unit. The FDR and CVR may include electronic interfaces and a housing surrounding each circuit, and may include a crash survival memory unit (CSMU). The CSMU typically includes non-volatile memory for storing flight data and voice data. Other flight recorder devices or modules (e.g., a data analysis module (DA)) may be arranged to receive flight data corresponding to various predetermined flight parameters from various devices that include other flight recorder modules in the flight recorder system, and may include a dedicated processor for data analysis. Analysis may be performed by the DA during flight or after flight. Flight recorder devices may include any number of devices or modules configured to capture data indicating any desired number of parameters associated with the aircraft, including detected, measured, sensed, calculated, derived, or otherwise determined data.

[0018] Figure 1An aircraft 10 is depicted providing an environment for various aspects of this disclosure. The aircraft 10 can fly a route from one location to another (i.e., a flight) and may include one or more propulsion engines 11 coupled to a fuselage 14. A cockpit 16 may be located within the fuselage 14, and wing assemblies 18 may extend outward from the fuselage 14. Furthermore, a set of aircraft systems 20 capable of properly operating the aircraft 10, along with a controller or computer 22, and a communication system having a communication link 24 may be included. As a non-limiting example, a first user interface is shown as a display 29 communicatively coupled to or formed together with the computer 22. The display 29 may be any user interface, screen, or known computer system or combination thereof, or a computer system that can communicate or otherwise provide output to one or more users (e.g., pilots) of the computer 22. It is contemplated that the display 29 may also receive or obtain input from one or more users of the computer 22. In a non-limiting aspect, the computer 22 may include a flight management system (not shown).

[0019] The group of aircraft systems 20 can reside within the cockpit 16, the electronics and equipment bay (not shown), and other locations throughout the aircraft 10. This aircraft system 20 may include, but is not limited to, electrical systems, oxygen systems, hydraulic or pneumatic systems, fuel systems, propulsion systems, FMS, flight control, audio / video systems, integrated vehicle health management (IVHM) systems, and systems associated with the mechanical structure of the aircraft 10. In some aspects, as discussed in more detail herein, the group of aircraft systems 20 may include a flight recorder system 21.

[0020] Computer 22 can be operatively connected to the group of aircraft systems 20, and it is conceivable that computer 22 can assist in operating the group of aircraft systems 20 and can receive information from the group of aircraft systems 20. Computer 22 can also be connected to other controllers or computers of aircraft 10.

[0021] Computer 22 may include memory 26, which may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic storage, such as disks, digital multifunction disks (DVDs), optical disc read-only memory (CD-ROMs), or any suitable combination of these types of storage. Computer 22 may include one or more controller modules or processors 28 capable of running any suitable program. It should be understood that computer 22 may include any suitable number of individual microprocessors, power supplies, storage devices, interface cards, automatic flight systems, flight management computers, controller modules, and other standard components or associated therewith, and computer 22 may include machine-executable code, any number of software (sometimes also referred to as "firmware") programs (e.g., flight management programs), or other instructions designed to perform the various methods, processing tasks, calculations, and control / display functions required to perform the operation of aircraft 10, or cooperate therewith. Although not shown, it should be understood that any number of sensors or other systems may also be communicatively or operatively coupled to computer 22 to provide information to or receive information from it.

[0022] Flight recorder system 21 may include a set of fixed aircraft components (e.g., a set of line replaceable units (LRUs) 31) that can define networked end nodes (also referred to as “end stations” and “end systems”), or modular components of aircraft 10. For example, LRU 31 may include corresponding control modules and be configured to operate according to specific operational, interoperability, or form factor standards (e.g., those defined by the ARINC 664 series or Mil-Std-1553B standards). In the exemplary aspect shown, aircraft computer 22 may be located near the nose or cockpit of aircraft 10, while LRU 31 may be located at various locations on aircraft 10. Aircraft computer 22 and LRU 31 may be configured to be communicatively coupled via data communication network 12. Data communication network 12 may include a series of data transmission paths 13, including bridges or switches (not shown). Data transmission paths 13 may include physical connections between corresponding components or end nodes of network 12 (e.g., computer 22 and LRU 31). In a non-limiting aspect, the physical connection may include a wired connection (such as Ethernet) or a wireless transmission connection, including but not limited to WiFi (e.g., 802.11 network), Bluetooth, etc. The aircraft computer 22, LRU 31, data transmission path 13, and network switch may together form the avionics data network of the aircraft 10.

[0023] LRU 31 may include, for example, fully encompassed systems, sensors, instruments, cameras, recorders, processors, or other auxiliary equipment to manage or operate flight recorder functions. For example, at least one set of LRUs 31 may generate data that may be modified, calculated, or processed before or during the preparation for packaging the data into a data frame for transmission over the avionics data network via data transmission path 13. In a non-limiting aspect, another set of LRUs 31 may consume data transmitted over the avionics data network. In some cases, the aircraft computer 22 or LRUs 31, or both, may operate to generate or consume data, or both. As used herein, “consumption” of data will be understood to include, but is not limited to, performing or executing computer programs, routines, calculations, analyses, functions, or processing at least a portion of the data, storing the data in memory, or otherwise utilizing at least a portion of the data.

[0024] Communication link 24 can be communicatively connected to computer 22 or other control modules or processors of the aircraft to transmit information to and from aircraft 10. It is envisioned that communication link 24 can be a wireless communication link and can be various communication mechanisms capable of wirelessly linking with other systems and devices, including but not limited to satellite uplink, SATCOM Internet, VHF data link (VDL), ACARS network, Automatic Dependent Surveillance-Broadcast (ADS-B), WiFi, WiMax, 3G wireless signals, Code Division Multiple Access (CDMA) wireless signals, Global System for Mobile Communications (GSM), 4G wireless signals, Long Term Evolution (LTE) signals, 5G wireless signals, or any combination thereof. It will also be understood that a particular type or mode of wireless communication is not critical to this disclosure, and wireless networks developed thereafter are naturally envisioned within the scope of this disclosure. Furthermore, communication link 24 can be communicatively connected to computer 22 via a wired link without altering the scope of the aspects described herein. Although only one communication link 24 is shown, it is envisioned that aircraft 10 can have multiple communication links 24 communicatively connected to computer 22. Such multiple communication links can provide the aircraft 10 with the ability to transmit information to or from the aircraft 10 in a variety of ways.

[0025] Figure 2A functional block diagram of a non-limiting aspect of a flight recorder system 200 is shown. The flight recorder system 200 may include an LRU 31, which includes a set of flight recorder modules (FRMs) 210. As shown, in some aspects, the set of FRMs 210 may include at least one of a cockpit voice recorder module (CVR) 211, a flight data recorder module (FDR) 212, and a data analysis module (DA) 213. In some aspects, the set of FRMs 210 may include a collision survivor recorder module (CSR) 214. In other aspects, it is contemplated that the set of FRMs 210 may optionally include any number of other FRMs (not shown) for the collection and recording of other desired aircraft performance and operational data. It should be understood that, in a non-limiting aspect, the set of FRMs 210 may include individual LRUs. In other aspects, the set of FRMs 210 may be combined into fewer physical entities, for example, by combining the corresponding functions of the FRMs 210 onto one or more circuit card assemblies (not shown).

[0026] Resource Controller Module (RCM) 215 can be communicatively connected to the group of FRMs 210 via a data communication network 219 including a switching structure 220 and a set of communication links 218. RCM 215 can also be communicatively connected to the aircraft's data bus (not shown) via a data bus interface 202. In a non-limiting aspect, data communication network 219 may include the data communication network of flight recorder system 200. In other aspects, data communication network 219 may additionally or alternatively include the data communication network of aircraft 10. For example, in a non-limiting aspect, the group of FRMs 210 may include a CSR arranged as a separate LRU. In a non-limiting aspect, another FRM 210 (e.g., one or more of CVR, FDR, or DA) may be communicatively connected to the CSR via the aircraft's data communication network.

[0027] Each FRM 210 may include a corresponding local memory. For example, CVR 211 may include local CVR memory 221, FDR 212 may include local FDR memory 222, DA 213 may include local DA memory 223, and CSR 214 may include local CSR memory 224. In a non-limiting aspect, each corresponding local memory 221, 222, 223, 224 may be arranged as a shareable memory. For example, each corresponding local memory 221, 222, 223, 224 may be configured to provide unified memory access (UMA), non-unified memory access (NUMA), or cache-only memory architecture (COMA) access. The corresponding local memories 221, 222, 223, 224 may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic storage, such as disks, digital multifunction disks (DVDs), optical disc read-only memory (CD-ROMs), etc., or any suitable combination of these types of storage.

[0028] Each FRM 210 may include a corresponding control module or processor. For example, CVR 211 may include CVR control module 231, FDR 212 may include FDR control module 232, DA 213 may include DA control module 233, and CSR 214 may include CSR control module 234. Each corresponding control module 231, 232, 233, 234 may be configured to run any suitable program or program code. Although not shown, it should be understood that each FRM 210 may include any suitable number of individual microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components or associated therewith, and the corresponding FRM 210 may include machine-executable code, any number of software programs (e.g., data logging programs), or other instructions designed to perform the intended operation of the corresponding FRM 210, including methods, processing tasks, calculations, and control / display functions, or in cooperation with them. The corresponding control modules 231, 232, 233, and 234 may include any known processor, microcontroller, or logic device, including but not limited to: field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), application-specific integrated circuits (ASICs), full-authority digital engine control (FADECs), proportional controllers (P), proportional-integral controllers (PI), proportional-derivative controllers (PD), proportional-integral-derivative controllers (PID), hardware-accelerated logic controllers (e.g., for encoding, decoding, transcoding, etc.), and combinations thereof. For example, in a non-limiting aspect, the corresponding controller modules 231, 232, 233, and 234 may include a corresponding set of FPGAs (not shown) with addressable memory-mapped registers.

[0029] Each FRM 210 may also include a corresponding set of input and output (I / O) ports communicatively connected to the switching structure 220. For example, CVR 211 may include a set of CVR I / O ports 241, FDR 212 may include a set of FDR I / O ports 242, DA 213 may include a set of DA I / O ports 243, and CSR 214 may include a set of CSR I / O ports 244. Each of the corresponding I / O ports 241, 242, 243, and 244 may be communicatively connected to the data communication network 219. In some aspects, each corresponding I / O port 241, 242, 243, and 244 may include a memory-mapped I / O port.

[0030] In a non-limiting aspect, the data communication network 219 may define a network mesh or switching fabric 220 comprising a set of communicatively connected network switches or bridges (not shown), such as Ethernet switches. In a non-limiting aspect, the data communication network 219 may be configured according to a Time-Sensitive Networking (TSN) pattern to communicate data using standard methods for time synchronization and traffic management, thereby allowing deterministic communication over standard Ethernet. The data communication network 219 may include any desired communication bus or bus topology that will enable the parties to operate as described herein. For example, in a non-limiting aspect, the data communication network 219 may include a high-speed serial bus conforming to the Peripheral Component Interconnect Fast (PCIe) pattern. In such a non-limiting aspect with a PCIe-compliant point-to-point topology, the set of separate corresponding links 218 may communicatively connect each FRM 210 to the switching fabric 220 to enable full-duplex communication of data packets between any two end nodes (e.g., FRM 210 or RCM 215), where there is no inherent limitation on concurrent access between multiple end nodes. In a non-limiting aspect, the group of links 218 can communicatively connect one or more FRM 210s to RCM 215, switching structure 220, data bus interface 202, the aircraft's data bus (not shown), various data acquisition devices of the aircraft (not shown), or any combination thereof. The group of links 218 may include any one or more serial links, parallel data bus links, or other conventional communication links. It should be understood that aspects employing PCIe mode can be programmed to detect and construct FRM 210 devices when communicatively connected to data communication network 219. It will be further understood that, in some cases, FRM 210 devices may include "pre-constructed" or default functions or operations, and aspects can be programmed to automatically detect and reconstruct FRM 210 devices via RCM 215 when communicatively connected to data communication network 219.

[0031] RCM 215 may include a corresponding local memory 225 and a controller module 235. RCM memory 225 may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic storage, such as a disk, digital multifunction disc (DVD), optical disc-read-only memory (CD-ROM), or any suitable combination of these types of storage. In some aspects, RCM local memory 225 may be configured as a shareable memory.

[0032] The RCM 215 control module 235 can be configured to run any suitable program or program code to enable the aspects to operate as described herein. Although not shown, it should be understood that each RCM 215 may include any suitable number of individual microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components or associated therewith, and the corresponding RCM 215 may include machine-executable code, any number of software programs (e.g., data logging programs), or other instructions designed to perform the intended operation of the corresponding RCM 215, including or cooperating with them, various methods, processing tasks, calculations, and control / display functions. The RCM 215 may include any known processor, microcontroller, or logic device, including but not limited to: field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), application-specific integrated circuits (ASICs), full-authority digital engine control (FADECs), proportional controllers (P), proportional-integral controllers (PI), proportional-derivative controllers (PD), proportional-integral-derivative controllers (PID), hardware-accelerated logic controllers (e.g., for encoding, decoding, transcoding, etc.), or combinations thereof.

[0033] RCM 215 can be communicatively connected to the data bus or data communication network (not shown) of aircraft 10 via data bus interface 202. Flight recorder system 200 can receive or collect data from the data bus or data communication network of aircraft 10 and provide the data to one or more of FRM 210. For example, in a non-limiting aspect, data can be provided via RCM 215 or switching structure 220 or a combination thereof. In a non-limiting aspect, RCM 215 can receive or collect data from the data bus or data communication network of aircraft 10 during flight of the aircraft. For example, RCM 215 can receive data from the data bus of aircraft 10 indicating the current stage or progress of the aircraft's flight. In such an aspect, RCM 215 can be programmed to construct the operation of switching structure 220 based on the indicated stage or progress of the aircraft's flight. Furthermore, in this respect, RCM 215 may optionally be programmed to construct a first operation of at least one of the exchange structure 220 and the first FRM 210 based on a first phase of flight, and a second operation of at least one of the exchange structure 220 and the first FRM 210 based on a second phase of flight. As used herein, the term "construction operation" (e.g., the first operation or the second operation) may include "reconstruction operation," for example, where a particular FRM includes default operations or pre-constructed functions or operations. In some aspects, the flight recorder system 200 may receive commands from computer 22 via a data bus or data communication network of the aircraft 10 to which it is responsive. In some aspects, the flight recorder system 200 may provide data from one or more of the FRMs 210 to cockpit displays 29.

[0034] RCM 215 can also be communicatively connected to the group of FRMs 210 via data communication network 219. RCM 215 can be configured to detect FRMs 210 connected to switching structure 220. In response to the detection of a specific FRM 210 connected to switching structure 220, RCM 215 can be programmed to execute (e.g., via "plug-and-play" processing or executable program code) to construct the operation of the detected FRM 210. It should be understood that because the construction of the operation of FRM 210 by RCM 215 can be based on the detection of FRM 210 by RCM 215, the operation of FRM 210 can be dynamically constructed by RCM 215 during flight of the aircraft, not necessarily only during pre-flight or post-flight routine maintenance.

[0035] The detection of a specific FRM 210 connected to the switching fabric 220 by the RCM 215 may further include determining the type of the detected FRM 210 by the RCM 215. For example, if the RCM 215 detects that a specific FRM 210 is communicatively connected to the switching fabric 220, the RCM 215 may be programmed to determine whether the detected FRM 210 is one of CVR 211, FDR 212, DA 213, CSR 214, or some other type of FRM 210. In other aspects, the detection or determination of a specific FRM 210 connected to the switching fabric 220 may further include determining, by the RCM 215, a count or number of available corresponding I / O ports 241, 242, 243, 244 of the detected FRM 210. On one hand, based on the detection of a specific detected FRM 210 communicatively connected to the switching structure 220, and the determination of the type of the detected FRM 210 and the number of available memory-mapped I / O ports 241, 242, 243, and 244 of the detected FRM 210, the RCM 215 can be further programmed to dynamically construct the operation of the detected FRM 210. Furthermore, the RCM 215 can be programmed to construct the operation of the switching structure 220 based on the type of the detected FRM 210. In other non-limiting aspects, the RCM 215 can be further programmed to instruct or command the detected specific FRM 210 to load software or firmware (e.g., FPGA firmware) stored in the local non-volatile memory (e.g., flash memory) of the detected specific FRM 210.

[0036] In some aspects, the respective local memories 221, 222, 223, 224 of each FRM 210 communicatively connected to the data communication network 219 can be read by the RCM 215 via the switching structure 220. Furthermore, in a non-limiting aspect, at least some data in the respective local memories 221, 222, 223, 224 of each FRM 210 can be shared with other FRMs 210 communicatively connected to the data communication network 219. In a non-limiting aspect, the RCM 215 can be programmed to construct the switching structure 220 such that each FRM 210 can access any memory-mapped computing resources of the other FRMs 210, such as the respective local memories 221, 222, 223, 224, the respective I / O ports 241, 242, 243, 244, or combinations thereof. Thus, the corresponding local memories 221, 222, 223, 224 or the corresponding port I / Os 241, 242, 243, 244 of the first FRM 210 can be accessed by the second FRM 210 without the cooperation or participation of the corresponding control modules 231, 232, 233, 234 of the first FRM 210. For example, in a non-limiting aspect, FRM 210 may include DA 213, which is configured to analyze data received from the corresponding local memory of at least one of CVR 211 and FDR 212 during flight of the aircraft using DA control module 233, without cooperation with the corresponding control modules 231, 232 of CVR 211 and FDR 212.

[0037] Figure 3 A non-limiting example of a method 300 for operating a flight recorder system 200 of an aircraft 10 is shown. Method 300 can be performed while the aircraft 10 is in flight, before flight (e.g., before executing a flight plan), or after flight (e.g., after flight). Although described according to flight recorder system 200, it should be understood that method 300 can be applied to any suitable avionics device configured to save data to memory and communicate with any other suitable avionics device.

[0038] The flight recorder system may include a first FRM 210 having a first local memory 221-224 and a first set of memory-mapped I / O ports 241-244, and a second FRM 210 having a second local memory 221-224 and a second set of memory-mapped I / O ports 241-244. In a non-limiting aspect, the first FRM 210 may include at least one of CVR 211, FDR 212, DA 213, and CSR 214. In a non-limiting aspect, the second FRM 210 may include at least one of CVR 211, FDR 212, DA 213, and CSR 214. It is contemplated that, in other respects, the first FRM 210 or the second FRM 210, or both, may optionally include any number of other FRMs 210 configured for data collection or recording of other desired aircraft performance and operational data. RCM 215 can be communicatively connected to the first FRM 210 and the second FRM 210 via a data communication network 219 including a switching structure 220. RCM 215 can also be communicatively connected to the aircraft's data bus (not shown) via a data bus interface 202.

[0039] Method 300 may include a switching structure 220 communicatively connecting RCM 215 to data communication network 219, and communicatively connecting the first FRM 210 and the second FRM 210 to the switching structure at 320. In a non-limiting aspect, data communication network 219 may include the data communication network 219 of flight recorder system 200. In other aspects, data communication network 219 may additionally or alternatively include the data communication network of aircraft 10. For example, in a non-limiting aspect, one of the first FRM 210 and the second FRM 210 may include a CSR 214 arranged as a separate LRU. In these aspects, the other of the first FRM 210 and the second FRM 210 may be communicatively connected to CSR 214 via aircraft data communication network 219. In other aspects, the first FRM 210 may be communicatively connected to other discrete sensors or devices, such as, but not limited to, tachometers, strain gauges, etc., to receive data from them. Method 300 includes detecting the first FRM 210 by RCM 215 at 325, and reading at least one of the first local memory and the first memory-mapped I / O port of the first FRM 210 by RCM 215 at 330. Detecting the first FRM by RCM at 325 may include at least one of determining the type of the first FRM 210 and the number of I / O ports of the first FRM 210.

[0040] Next, method 300 includes the operation of constructing a first FRM 210 by RCM 215 at 335, providing data to the first FRM 210 at 340, and saving a first portion of the data to the local memory of the first FRM at 345. In various non-limiting aspects, the data may be provided to the first FRM 210 via RCM 215, switching structure 220, data communication network 219, other devices or sensors, or any combination thereof. Method 300 may also include providing a second portion of the data from the first FRM 210 to the second FRM 210 at 350.

[0041] In a non-limiting aspect, method 300 may include, at 355, instructing the first FRM 210 by RCM 215 to load firmware stored in local memory 221-224, and at 360, configuring the switching structure 220 to enable the first FRM 210 to access the local memory 221-224 of the second FRM 210. In some aspects, configuring the switching structure at 360 may optionally be done during flight of the aircraft.

[0042] A non-limiting aspect of method 300 may further include the operation at 365 of constructing the exchange structure 220 by RCM 215 based on a determined FRM 210 type. The operation at 365 of constructing the exchange structure 220 by RCM 215 based on a determined FRM 210 type may optionally be performed during flight of the aircraft.

[0043] The described order is for illustrative purposes only and is not intended to limit method 300 in any way, as it should be understood that parts of the method may be performed in different logical orders without departing from the described method, may include additional or intermediate parts, or the described parts of the method may be divided into multiple parts, or the described parts of the method may be omitted. For example, method 300 may include various other intermediate steps. The examples provided herein are non-limiting.

[0044] It is conceivable that the aspects of this disclosure may be advantageous for conventional systems or methods used in constructing and operating flight recorders. The aspects of this disclosure reduce the workload for pilots or maintenance personnel when constructing flight recorders, for example, when adding, installing, or reconstructing flight recorder modules during flight. This is particularly advantageous in single-pilot operation (SPO) or reduced crew operation (RCO) scenarios.

[0045] Furthermore, it is envisioned that the aspects of this disclosure can advantageously provide a more adaptable architecture than conventional flight recorders and systems. The aspects described herein can more easily support various configurations of flight recorder modules using standardized structures (e.g., using a common rack and a common backplane). Therefore, the aspects described herein can advantageously provide a more scalable flight recorder system compared to conventional systems.

[0046] Furthermore, it is conceivable that, compared to traditional flight recorder systems, the aspects described herein allow for easier dynamic configuration of the flight recorder system during flight. For example, flight recorder modules can be added and constructed to operate during the aircraft's flight. Alternatively, flight recorder modules can be optionally configured for different operations based on the aircraft's flight phase.

[0047] Within the scope not described herein, various features and structures of the various embodiments may be combined with each other as needed. A feature not shown in all embodiments is not to be construed as possibly being excluded, but is done for the sake of brevity. Therefore, various features of different embodiments may be mixed and matched as needed to form new embodiments, whether or not the new embodiments are explicitly described. All combinations or permutations of the features described herein are covered by this disclosure.

[0048] This written description uses examples to disclose the invention, including the best mode, and also enables any person skilled in the art to practice the invention, including making and using any device or system and performing any combination of methods. The patent scope of the invention is defined by the claims, but may include other examples that would occur to a person skilled in the art. These other examples are intended to fall within the scope of the claims if they have structural elements that are not indistinguishable from the literal language of the claims, or if they include equivalent structural elements that are not substantially different from the literal language of the claims.

[0049] The various features, aspects, and advantages of this disclosure can also be embodied in any arrangement of aspects of this disclosure, including but not limited to the following technical solutions as defined in the enumerated aspects:

[0050] A flight recorder system for an aircraft includes: a resource controller module (RCM) communicatively connected to a set of flight recorder system modules (FRMs) via a data communication network defining a switching structure; each FRM includes a corresponding control module, a corresponding local memory, and a corresponding set of input and output (I / O) ports communicatively connected to the switching structure; wherein the RCM is configured to detect the corresponding FRM connected to the switching structure and to construct the operation of the FRM based on the detection, and wherein the corresponding local memory of the FRM is readable by the RCM and can be shared with other FRMs via the switching structure.

[0051] According to the flight recorder system described in the foregoing clause, each FRM can be dynamically constructed by the RCM.

[0052] According to any of the foregoing clauses, the flight recorder system wherein the RCM is configured to instruct the FRM to load software from local memory.

[0053] According to any of the preceding clauses, the flight recorder system wherein the corresponding local memory includes at least one of random access memory (RAM), memory-mapped I / O ports, and registers.

[0054] According to any of the foregoing clauses, the flight recorder system wherein the local memory of the first FRM can be accessed by the second FRM without the cooperation of the corresponding processor of the first FRM.

[0055] According to any of the preceding clauses, the flight recorder system wherein the RCM is programmed to construct the switching structure such that the control module of the second FRM can access the local memory of the first FRM.

[0056] According to any of the preceding clauses, the flight recorder system wherein the RCM's detection of the corresponding FRM includes at least one of determining the FRM type and the number of I / O ports of the corresponding FRM.

[0057] According to any of the foregoing clauses, the flight recorder system wherein the RCM is further configured to construct the exchange structure based on the determined FRM type.

[0058] According to any of the foregoing clauses, the operation of at least one of the exchange structure and the FRM can be constructed by the RCM during the flight of the aircraft.

[0059] The flight recorder system according to any of the foregoing clauses, wherein the RCM is communicatively coupled to the data bus of the aircraft and is configured to receive data therefrom.

[0060] According to any of the preceding clauses, the flight recorder system wherein the data received by the RCM indicates the current flight phase of the aircraft, and wherein the RCM is further programmed to construct the operation of the exchange structure based on the indicated flight phase of the aircraft.

[0061] According to any of the preceding clauses, the flight recorder system wherein the RCM is further programmed to construct a first operation of at least one of the exchange structure 220 and the first FRM during a first phase of flight of the aircraft, and to construct a second operation of at least one of the exchange structure and the first FRM during a second phase of flight of the aircraft.

[0062] According to any of the preceding clauses, the flight recorder system, wherein the set of FRMs includes a data analysis module (DA) and at least one of a cockpit voice recorder module (CVR) and a flight data recorder module (FDR), and wherein the DA is configured to analyze data received from the respective local memory of the at least one of the CVR and FDR during flight of the aircraft.

[0063] The flight recorder system according to any of the foregoing clauses, wherein the set of FRMs includes at least one of CVR, FDR, DA and crash survival recording subsystems.

[0064] A method for operating a flight recorder system of an aircraft, the flight recorder system including a first flight recorder module (FRM) having a first local memory and a first set of memory-mapped I / O ports, and a second FRM having a second local memory and a second set of memory-mapped I / O ports, the method comprising: communicatively connecting a resource control module (RCM) to a switching structure; communicatively connecting the first FRM and the second FRM to the switching structure; detecting the first FRM by the RCM; reading at least one of the first local memory and the first memory-mapped I / O ports of the first FRM by the RCM; constructing operations of the first FRM by the RCM; providing data to the first FRM; saving a first portion of the data to the local memory of the first FRM; and retrieving a second portion of the data from the first FRM to the second FRM by the second FRM.

[0065] The method according to any of the foregoing clauses further includes the RCM instructing the FRM to load software from local storage.

[0066] The method according to any of the foregoing clauses further includes constructing the switching structure to enable the first FRM to access the local memory of the second FRM.

[0067] According to any of the foregoing clauses of the method, the operation of constructing the first FRM by the RCM is during the flight of the aircraft.

[0068] According to any of the foregoing clauses of the method, wherein the RCM detects at least one of the determination of the first FRM type and the number of I / O ports of the first FRM.

[0069] The method according to any of the foregoing clauses further includes the operation of constructing the exchange structure by the RCM based on the determined FRM type.

Claims

1. A flight recorder system for an aircraft, characterized in that, include: A Resource Controller Module (RCM) is configured to communicatively connect to a set of Flight Recorder Modules (FRMs) via a data communication network with a defined switching structure; and Each FRM includes a corresponding control module, a corresponding local memory, and a corresponding set of input and output (I / O) ports, which are communicatively connected to the exchange structure suitable for recording data related to aircraft operation. Each FRM in the set includes one of a cockpit voice recorder module (CVR), a flight data recorder module (FDR), or a collision survival recorder module (CSR). The RCM is configured to detect the corresponding FRM connected to the switching structure and to construct the operation of the FRM based on the detection. The corresponding local memory of the FRM can be read by the RCM and can be shared with other FRMs via the switching structure, such that the local memory of the first FRM can be accessed by the second FRM without the cooperation of the corresponding control module of the first FRM. The RCM is also programmed to construct the switching structure so that the control module of the second FRM can access the local memory of the first FRM.

2. The flight recorder system according to claim 1, characterized in that, Each FRM can be dynamically constructed from the RCM.

3. The flight recorder system according to claim 2, characterized in that, The RCM is configured to instruct the FRM to load software from local memory.

4. The flight recorder system according to claim 1, characterized in that, The corresponding local memory includes at least one of random access memory (RAM), memory-mapped I / O ports, and registers.

5. The flight recorder system according to claim 1, characterized in that, The detection of the corresponding FRM by the RCM includes at least one of determining the FRM type and the number of I / O ports of the corresponding FRM.

6. The flight recorder system according to claim 5, characterized in that, The RCM is further configured to construct the exchange structure based on the determined FRM type.

7. The flight recorder system according to claim 1, characterized in that, The operation of at least one of the exchange structure and the FRM can be constructed by the RCM during the flight of the aircraft.

8. The flight recorder system according to claim 1, characterized in that, The RCM is communicatively connected to the aircraft's data bus and configured to receive data from it.

9. The flight recorder system according to claim 8, characterized in that, The data received by the RCM indicates the current flight phase of the aircraft, and the RCM is further programmed to construct the operation of the exchange structure based on the indicated flight phase of the aircraft.

10. The flight recorder system according to claim 9, characterized in that, The RCM is further programmed to perform a first operation of constructing at least one of the exchange structure and the first FRM during the first phase of the flight of the aircraft, and a second operation of constructing at least one of the exchange structure and the first FRM during the second phase of the flight of the aircraft.

11. The flight recorder system according to claim 1, characterized in that, The set of FRMs includes a data analysis module (DA) and at least one of a CVR and an FDR, wherein the DA is configured to analyze data received from the respective local memory of the at least one of the CVR and FDR during the flight of the aircraft.

12. A method for operating a flight recorder system of an aircraft, the flight recorder system comprising a first flight recorder module (FRM) having a first local memory and a first set of memory-mapped I / O ports, and a second FRM having a second local memory and a second set of memory-mapped I / O ports, characterized in that, The method includes: Connect the Resource Control Module (RCM) to the switching structure for communication. The first FRM and the second FRM are communicatively connected to the switching structure; The first FRM is detected by the RCM; The RCM reads at least one of the first local memory and the first set of memory-mapped I / O ports of the first FRM; The operation of constructing the first FRM from the RCM; Provide the data to the first FRM; The first portion of the data is saved to the local memory of the first FRM; The switching structure is constructed by the RCM to enable the control module of the second FRM to access the local memory of the first FRM; and The second FRM retrieves a second portion of the data from the first local memory of the first FRM; The first FRM and the second FRM respectively include one of CVR, FDR or CSR.

13. The method according to claim 12, characterized in that, This further includes the FRM being instructed by the RCM to load software from local storage.

14. The method according to claim 12, characterized in that, The method further includes constructing the switching structure to enable the first FRM to access the local memory of the second FRM.

15. The method according to claim 12, characterized in that, The operation of constructing the first FRM by the RCM occurs during the flight of the aircraft.

16. The method according to claim 12, characterized in that, The determination of the first FRM by the RCM includes at least one of the determination of the first FRM type and the number of I / O ports of the first FRM.

17. The method according to claim 16, characterized in that, It further includes the operation of constructing the switching structure by the RCM based on the determined FRM type.

Images