Flight recorder system and method

The main clock signal synchronizes the sampling frequency of multiple flight recorder modules, and solves the problem of inconsistent sampling frequency in traditional systems, realizes efficient and accurate data transmission of flight recorder systems, and simplifies system design.

CN119028041APending Publication Date: 2024-11-26GENERAL ELECTRIC CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410499360.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-23
Filing Date
2024-04-24
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In traditional flight recorder systems, the sampling frequency between multiple flight recorder modules (FRMs) is not synchronized, resulting in a deviation in audio stream playback during long flights, making it difficult to meet industry standards, and real-time sampling rate conversion consumes a large amount of processing bandwidth and Inaccurate data may be generated.

Method used

Synchronize the internal clocks of multiple FRMs through the main clock signal, ensuring that all FRMs are consistent in the sampling frequency during data transmission, avoid real-time sampling rate conversion, and directly sample and transmit based on the main clock signal.

Benefits of technology

The sampling frequency synchronization between multiple FRMs is achieved, which reduces the error and discontinuity of post-processing, releases the computing bandwidth, simplifies the construction and programming of CVFDR, and improves the stability and efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119028041A_ABST
    Figure CN119028041A_ABST
Patent Text Reader

Abstract

A flight recorder system of an aircraft includes a cockpit voice and flight data recorder communicatively coupled to a first flight recorder module (FRM) via a data communications network. The first FRM includes a first sensor configured to generate a first analog signal, a first controller, and a first analog-to-digital converter (ADC) configured to sample the analog signal based on a received master clock signal and convert the first analog signal into a first digital data signal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to aircraft flight recorders and, more particularly, to flight recorder systems and methods of operating flight recorders. Background Art

[0002] A flight recorder (sometimes called a "black box" recorder) is a device used to capture and store information about the operation and status of an aircraft during flight. This information can be analyzed in response to an unexpected event or accident involving an aircraft, and can help reconstruct the events leading up to the event. Flight recorders are installed on certain aircraft (usually large aircraft or passenger aircraft) and meet international aviation authority standards. For example, the Federal Aviation Administration (FAA) in the United States (US) and the European Aviation Safety Agency (EASA) in the European Union require the use of flight recorders on commercial aircraft.

[0003] Typically, a cockpit voice recorder (CVR) is provided to record the voices of the crew members and other sounds in the cockpit of the aircraft. The CVR includes a "cockpit area microphone" to capture sounds of interest, such as engine noise, stall warnings, landing gear extension and retraction, and other clicks and pops. From these sounds, parameters such as engine revolutions per minute (rpm), system failures, speed, and the time when certain events occurred can usually be determined. Communications with air traffic control, automatic radio weather briefings, and conversations between pilots and ground or cabin crew are also recorded. Other examples of information captured and 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A full and enabling disclosure of the present specification, including the best mode thereof, to one of ordinary skill in the art is set forth in the specification with reference to the accompanying drawings, in which:

[0005] Figure 1 is a schematic diagram of an aircraft and ground systems according to aspects described herein.

[0006] Figure 2 According to the aspects described herein, Figure 1 A block diagram of an example flight recorder system for use with an aircraft and ground systems.

[0007] Figure 3 is a flow chart illustrating a method of operating a flight recorder system according to aspects described herein. DETAILED DESCRIPTION

[0008] For purposes of illustration and discussion, the present disclosure will be described with respect to a flight recorder system for an aircraft. It should be understood that the present disclosure may be applicable to other vehicles or systems and may be used to provide benefits in industrial, commercial, and residential applications where recorded data is used or required.

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

[0010] 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 used only for identification purposes to help the reader understand the present disclosure, and do not create limitations, especially limitations on their position, orientation or use. Unless otherwise specified, connection references (e.g., attachment, connection, connection and engagement) will be interpreted broadly and may include intermediate members between sets of elements and relative movement between elements. Therefore, connection references do not necessarily infer that two elements are directly connected and have a fixed relationship to each other. In a non-limiting example, connections or disconnections can be selectively constructed to provide, enable, disable, etc. electrical connections or communication connections between corresponding elements. In addition, as used herein, the term "group" or a "group" of elements can be any number of elements, including only one element.

[0011] As used herein, a "controller" or "controller module" may include a component that is configured or adapted to provide instructions, control, operation, or any form of communication to an operable component to affect its operation. A controller module may include, but is not limited to, any known processor, microcontroller, system on chip (SoC), or logic device. Such logic devices may 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 controls (FADECs), proportional controllers (PCs), proportional integral controllers (PIs), proportional differential controllers (PDs), proportional integral differential controllers (PIDs), hardware accelerated logic controllers (e.g., for encoding, decoding, transcoding, etc.), etc., or a combination thereof.

[0012] Non-limiting examples of controller modules may be constructed or adapted to run, operate or otherwise execute program code to achieve operations or functional results, including performing various methods, functions, processing tasks, calculations, comparisons, sensing or measurement values, etc., to enable or achieve the technical operations or operations described herein. The operations or functional results may be based on one or more inputs, stored data values, sensing or measurement values, true or false indications, etc. As used herein, the terms "program code", "software" and "firmware" may be used interchangeably and may be used to describe an operable or executable instruction set, which may include routines, programs, codes, bit streams, objects, components, data structures, algorithms, etc., that have the technical effects of performing specific tasks or implementing specific abstract data types. When implemented in software or firmware, various aspects as described herein may include code segments or instructions for performing various tasks. It should be understood that the various block components shown in the figure may be implemented by any number of hardware, software or firmware components or combinations thereof that are constructed to perform specified functions.

[0013] In another non-limiting example, the controller module may also include a data storage component accessible by the processor, including a memory, whether a transition memory, a volatile or non-transient memory, or a non-volatile memory. 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 a disk, DVD, CD-ROM, flash drive, universal serial bus (USB) driver, etc., or any suitable combination of these types of memory. In one example, the program code may be stored in a memory in a machine-readable format accessible to the processor. In addition, the memory may store various data, data types, sensed or measured data values, inputs, generated or processed data, etc., accessible to the processor when providing instructions, controlling or operating to affect functions or operational results, as described herein.

[0014] A conventional flight recorder is an electronic recording device or module installed in an aircraft to facilitate the investigation of aviation accidents and incidents. Typically, a flight recorder continuously monitors the current operating conditions and performance of an aircraft via a large number of sensors or other data sources located around the aircraft. Data from the sensors may be provided to a flight recorder module (FRM), which provides data to a cockpit voice recorder (CVR) or a flight data recorder (FDR) via the aircraft's data communications system. The CVR records radio transmissions and sounds in the cockpit, such as the pilot's voice and engine noise. The flight data recorder (FDR) monitors specific aircraft performance parameters, such as altitude, airspeed, heading, vertical acceleration, time, nose heading, steering wheel position, rudder pedal position, steering wheel position, horizontal stabilizer, and fuel flow. Some sensor data may also be provided directly to the flight recorder. In some cases, the CVR and FDR may be combined into a single unit, namely a cockpit voice and flight data recorder (CVFDR). As will be used herein, for ease of description and understanding, the term "CVFDR" will refer to one or more devices including a CVR or FDR or both. The CVFDR may include an electronic interface and a housing enclosing each circuit, and may include a crash surviving memory unit (CSMU). The CSMU typically includes non-volatile memory for storing flight data and voice data. Other flight recorder devices or modules, such as a data analysis module (DA), may 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 may include a dedicated processor for data analysis. The analysis may be performed by the DA during the flight or after the flight. The flight recorder device may include any number of devices or modules configured to capture data indicating any desired number of parameters relative to the aircraft, including data detected, measured, sensed, calculated, derived, or otherwise determined.

[0015] The flight recorder device may be constructed as a set of fixed aircraft components, such as a set of line replaceable units (LRUs). In many cases, the flight recorder LRU may include an FRM that receives and processes audio or other flight data from various data sources, such as sensors, monitors, instruments, etc. The FRM may be communicatively coupled to the CVFDR via the aircraft's communications network to provide data to the CVFDR according to known protocols.

[0016] Some traditional FRMs can be audio data sources. For example, such audio data sources can be one or more cockpit area microphones (CAM) and / or aircraft intercom systems (ICS). Traditional flight data audio sources (e.g., CAM, ICS) use one or more audio transducers or sensors to detect, measure or otherwise provide corresponding audio parameter data, and generate corresponding analog signals indicating audio parameters relative to time. Traditional FRMs generally include local or dedicated analog-to-digital converters (ADCs) (sometimes referred to as "encoders") that sample corresponding analog signals to convert them into digitized signals. Traditional ADCs generally use corresponding independent internal clocks to sample corresponding analog signals at predetermined sampling frequencies. For example, traditional ADCs may include an internal oscillator that is operable to generate a sampling rate clock signal based on a predetermined sampling frequency. In other traditional technologies, a local FRM host controller generates a sampling rate clock signal (e.g., a bit clock (BCLK) or a word clock (WCLK)) from an internal clock master frequency. Once sampled and digitized, a digital signal protocol (e.g., Inter-ICSound (I2S)) is used to provide the digitized signal to the FRM host controller for transmission to the CVFDR on the aircraft's data communication network. For example, each digitized signal may be sent from a particular FRM to the CVFDR as a set of data packets or frames transmitted sequentially.

[0017] The digitized signals (e.g., data packets) from the audio data source FRM to the CVFDR must be synchronized with each other relative to the transmission time on the aircraft data communication network. Each transmission may include any number of digitized data samples. The data packet typically includes information indicating the transmission time, i.e., a timestamp. The FRM can timestamp the data packet at the transmission time, for example, in the datagram header. In some cases, for example, in a communication network that adopts a more modern time-sensitive network (TSN) or conforms to the time-triggered Ethernet (TTE) protocol, the transmission synchronization to the FDR can be based on a master clock referenced by all network devices. The master clock is usually automatically selected from the local network based on the clocks connected to and available in the network and their specifications. Based on the master clock, synchronization packets are sent to other devices on the network. These packets measure the distance from the master device to all slave devices or nodes, and when the corresponding slave clock is synchronized with the master clock, the information is used to adjust the corresponding slave clock to timestamp. In this way, the communication network can take into account differences in cable lengths, as well as differences in response times and other defects in the network, in order to achieve synchronous network communication.

[0018] However, even if the data packets transmitted from the respective FRMs are synchronized with respect to the transmission time (e.g., referenced to a timestamp from a master clock), data synchronization problems between the multiple FRMs may still occur when the analog signals are converted by the ADCs in the multiple FRMs due to variations in the respective sampling rates. For example, although the respective internal clocks used by the ADCs of conventional FRMs are nominally operated to sample the respective analog signals at a common predetermined frequency (fs) (such as 8 kilohertz (kHz), 16 kHz, or 32 kHz), there may be slight variations between the actual internal clock frequencies of some devices. In addition, even if the respective FRM internal clocks operate at a common predetermined frequency, the actual clock frequency of each respective FRM may vary slightly during the lifetime of a particular FRM.

[0019] In addition, the accuracy of the corresponding internal clocks of different FRMs may differ from each other under different environmental parameters (such as temperature). As an example, in one instance, two conventional FRMs including conventional ADCs on an aircraft in flight may be constructed to sample corresponding analog audio signals at a nominally equal sampling frequency of 16kHz. However, in operation, the corresponding ADCs may actually operate based on slightly different sampling clock frequencies of 16000.0 Hz and 15980.0 Hz, respectively, to independently sample the corresponding audio signals at two slightly different sampling frequencies. This difference in actual sampling frequency may then cause the data packets transmitted by different FRMs to contain different numbers of samples from each other. That is, in this particular example, even if the data packets from different FRMs are transmitted to the CVFDR with a synchronized timestamp indicating the transmission time, the ADC operating at an actual sampling clock frequency of 15980.0 Hz will have a data packet with 20 fewer data samples for each second of sampling than the ADC operating at an actual sampling clock frequency of 16000.0 Hz.

[0020] For recordings or flights of short duration, such relatively slight changes in the sampling frequency may not be a problem. However, for recordings or flights of relatively long duration (e.g., 20 hours), even slight changes in the corresponding actual sampling frequency, and the resulting changes in the sampling frequency between the two FRMs, will cause the simultaneous playback of the data or audio streams at their nominal sampling frequency (e.g., 16kHz) to deviate more and more over time, so that they will not be synchronized.

[0021] Lack of sample rate synchronization of multiple ADCs can cause a number of problems. For example, EUROCAE ED-112A, an aircraft industry standard for CVR devices, requires that audio streams be "derived to within 4 milliseconds of the recording period." In many cases, especially for very long flights, the audio recording period can be as long as 25 hours. The variation in the respective sampling frequencies between the two FRMs will cause the simultaneous playback of the audio streams at their nominal sampling frequencies (e.g., 16kHz) to deviate more and more, so that they will not be synchronized within the required 4 milliseconds of the recording period. In order to meet the industry standard, the audio streams from the two FRMs will then need to be further processed to calculate or estimate a common sampling rate and convert the data based on the calculated common sampling rate. Typically, this further processing requires calculating the actual sample rate conversion (SRC), either in real time by the FDR or by another computing device for subsequent processing and then conversion to data or audio streams based on the calculated sampling rate (e.g., 16kHz). Such processing and conversion, especially if performed in real time, can consume a large amount of processing bandwidth, especially for systems with multiple FRMs. Additionally, the processing and conversion of the sampled data may produce other inaccuracies (e.g., spurious noise or artifacts) in the processed data stream. For a CVFDR that receives and records multiple data or audio streams from an FDR, it is desirable to have the FDR employ respective ADCs operating based on sampling rates that are synchronized relative to each other prior to transmitting the data.

[0022] Figure 1 An aircraft 10 is depicted, which provides an example of an environment in which aspects of the present disclosure may be implemented. The aircraft 10 may 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 positioned in the fuselage 14 and a wing assembly 18 may extend outwardly from the fuselage 14. In addition, a set of aircraft systems 20 and a controller or computer 22 capable of properly operating the aircraft 10 may be included, as well as a data communications network 12 with a communications link 24. The aircraft computer 22 may include a master clock computing function 29. The master clock computing function may form part of the computer 22, or may be embodied in a separate device or system that is communicatively coupled to the computer 22, for example, via the data communications network 12 or the communications link 24, or both. The aircraft computer 22 may also include a display (not shown) or be communicatively coupled to a display. The display may be any user interface, screen, or known computer system or combination, or a computer system that may communicate or otherwise provide output to one or more users of the computer 22 (e.g., a pilot). In non-limiting aspects, aircraft computer 22 may include a flight management system (not shown).

[0023] The set of aircraft systems 20 may reside within the cockpit 16, within an electronics and equipment bay (not shown), and in other locations throughout the aircraft 10. Such aircraft systems 20 may include, but are not limited to, electrical systems, oxygen systems, hydraulic or pneumatic systems, fuel systems, propulsion systems, FMS, flight controls, audio / visual systems, integrated vehicle health management (IVHM) systems, and systems associated with the mechanical structure of the aircraft 10. As discussed in greater detail herein, in some aspects, the set of aircraft systems 20 may include a flight recorder system 21.

[0024] The aircraft computer 22 may be operably coupled to the set of aircraft systems 20, and it is contemplated that the aircraft computer 22 may assist in operating the set of aircraft systems 20 and may receive information from the set of aircraft systems 20. The aircraft computer 22 may also be connected to other controllers or computers of the aircraft 10. Additionally or alternatively, the computer 22 may be communicatively coupled to a remote server (not shown) or a designated ground station 32, or both. The ground station 32 may be any type of communication ground station 32, such as a ground station operated by an air navigation service provider (ANSP) / air traffic control (ATC).

[0025] The aircraft computer 22 may include memory (not shown) that may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic memory, such as disks, digital versatile disks (DVDs), compact disk read-only memories (CD-ROMs), etc., or any suitable combination of these types of memory. The aircraft computer 22 may include one or more controller modules or processors 28 that may run any suitable program. It should be understood that the aircraft computer 22 may include or be associated with any suitable number of separate microprocessors, power supplies, storage devices, interface cards, autoflight systems, flight management computers, controller modules, and other standard components, and the aircraft 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 or cooperate with various methods, processing tasks, calculations, and control / display functions required for the operation of the aircraft 10. Although not shown, it should be understood that any number of sensors or other systems may also be communicatively or operatively coupled to the aircraft computer 22 to provide information to it or receive information from it.

[0026] The flight recorder system 21 may include a set of fixed aircraft components (e.g., a set of line replaceable units (LRUs) 31) that may define networked end nodes (also referred to as "end stations," "end points," or "end systems"), or modular components of the aircraft 10. For example, the LRUs 31 may include corresponding control modules and be configured to operate according to specific operating, interoperability, or form factor standards (e.g., those defined by the ARINC 664 series or the Mil-Std-1553B standard). In the exemplary aspect shown, the aircraft computer 22 may be located near the nose or cockpit of the aircraft 10, while the LRUs 31 may be located throughout the aircraft 10. The aircraft computer 22 and the LRUs 31 may be configured to be communicatively coupled via a data communications network 12. The data communications network 12 may include a series of data transmission paths 13, including bridges or switches (not shown). The data transmission paths 13 may include physical connections between corresponding components or end nodes (e.g., the aircraft computer 22 and the LRUs 31) of the data communications network 12. In non-limiting aspects, the physical connection may include a wired connection (such as Ethernet), or may include a wireless transmission connection, including but not limited to Wi-Fi (e.g., 802.11 network), Bluetooth, etc. The aircraft computer 22, LRU 31, data transmission path 13, and network switch may collectively form a data communication network of the aircraft 10. It is contemplated that in various aspects, the data communication network 12 may be arranged and operated according to any desired data communication scheme (e.g., but not limited to, TSN, TTE, Peripheral Component Interconnect Express (PCIe), Ethernet 10 / 100, etc.) without departing from the scope of the present invention.

[0027] LRU 31 can include, for example, fully contained systems, sensors, transducers, instruments, cameras, recorders, processors or other auxiliary equipment to manage or operate flight recorder functions. For example, at least one group of LRU 31 can generate data, which can be modified, calculated or processed before or when preparing to package the data into data frames or data packets to be transmitted on the data communication network 12 through the data transmission path 13. In non-limiting aspects, another group of LRU 31 can consume data transmitted on the avionics data network. In some cases, the aircraft computer 22 or LRU 31 or both can operate to generate or consume data, or both. As used herein, the "consumption" of data will be understood to include but is not limited to performing or executing a computer program, routine, calculating, analyzing, function or processing at least a portion of the data, storing the data in a memory, or otherwise utilizing at least a portion of the data.

[0028] The communication link 24 may be communicatively coupled to the aircraft computer 22 or other control modules or processors of the aircraft to transmit information to and from the aircraft 10. It is contemplated that the communication link 24 may be a wireless communication link, and may be a variety of communication mechanisms capable of wirelessly linking with other systems and devices, and may include, but is not limited to, satellite uplinks, SATCOM Internet, very high frequency (VHF) data links (VDL), ACARS networks, automatic dependent surveillance broadcast (ADS-B), wireless fidelity (Wi-Fi), 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 the specific type or mode of wireless communication is not critical to the present disclosure, and wireless networks developed later are certainly contemplated within the scope of the present disclosure. In addition, the communication link 24 may be communicatively coupled to the aircraft computer 22 via a wired link without changing the scope of the aspects as described herein. Although only one communication link 24 is shown, it is contemplated that the aircraft 10 may have multiple communication links 24 communicatively coupled to the aircraft computer 22. Such multiple communication links may provide the aircraft 10 with the ability to transmit information to or from the aircraft 10 in a variety of ways. Additionally or alternatively, the computer 22 may communicate with a remote server (not shown) located at or communicatively coupled to a designated ground station 32. Communications may be sent or received between the ground station 32 and the computer 22 via the communication link 24.

[0029] Figure 2 A functional block diagram of a non-limiting aspect of a flight recorder system 200 is shown. The flight recorder system 200 may include a CVFDR 250 and an LRU 31, the LRU 31 including a set of flight recorder modules (FRMs) 210. The CVFDR 250 may include a corresponding CVFDR memory 255 and a CVFDR controller 256. In non-limiting aspects, the CVFDR 250 may be coupled to the set of flight recorder modules (FRMs) 210 via a data communications network 220. As shown, in non-limiting aspects, the CVFDR 250 may be additionally communicatively coupled to the set of FRMs 210 via the data communications network 220 and a set of communications links 218. The CVFDR 250 may also be communicatively coupled to a data bus (not shown) of the aircraft via a data bus interface 202. In non-limiting aspects, the data communications network 220 may include a data communications network of the flight recorder system 200. In other aspects, the data communications network 220 may additionally or alternatively include a data communications network of the aircraft 10.

[0030] In some aspects, the set of FRMs 210 may include a first FRM 211 and a second FRM 212. For example, in one non-limiting aspect, the first FRM 211 may be a CAM 211 and the second FRM 212 may be an ICS 212. Although aspects of the first FRM 211 and the second FRM 212 are described herein, other aspects are not limited thereto with respect to the CAM 211 and the ICS 212 for ease of understanding. It is contemplated that the first FRM 211 and the second FRM 212 may include any desired FRM 210 directed to data collection and recording of other desired aircraft performance and operational data without departing from the scope of the present disclosure. It is further contemplated that in other aspects, the set of FRMs 210 may optionally include any number of other FRMs (not shown) directed to data collection and recording of other desired aircraft performance and operational data. In non-limiting aspects, the set of FRMs 210 may include a single LRU 31. In other aspects, the set of FRMs 210 may be combined into fewer physical entities, such as by combining the respective functionality of one or more FRMs 210 onto one or more circuit card assemblies (not shown).

[0031] Each FRM 210 may include a corresponding transducer or sensor to measure, detect or otherwise sense a predetermined parameter. For example, the first FRM 211 may include a first sensor 231 configured to sense a first parameter, and the second FRM 212 may include a second sensor 232 configured to sense a second parameter. The first and second sensors 231, 232 are arranged to provide corresponding analog output signals indicating the measured or sensed parameter (e.g., audible sound). For example, the first sensor 231 is configured to generate a first analog signal 235, and the second sensor 232 is configured to generate a second analog signal 236. Although non-limiting aspects will be described herein for ease of understanding, such as including a first FRM 211 having a first sensor 231 and a second FRM 212 having a second sensor 232, other aspects are not limited thereto. It is contemplated that the first sensor 231 or the second sensor 232 or both may include a corresponding set of first and second sensors (not shown), wherein each sensor in the set of first and second sensors is arranged to provide a corresponding analog output signal indicating the measured or sensed parameter (e.g., audible sound). In addition, it is contemplated that when so arranged in a non-limiting aspect, each respective sensor in the first and second sets of sensors can be configured to generate a respective first or second analog signal that can be mixed or combined with other respective first or second analog signals of other first and second sensors to provide a resulting first or second analog output signal 235, 236. For example, a specific example of a first FRM arranged as a CAM 211 with a CAM sensor 231 can include a first transducer (not shown) in the cockpit area, the first transducer being configured to output a respective analog signal indicative of ambient sound in the cockpit, and also including a second transducer (not shown) configured to output a respective analog signal indicative of sound generated in a crew headset or intercom during flight. The analog signals from the first and second transducers can be mixed or combined by the CAM 211 to provide the first analog signal 235.

[0032] In addition, each FRM may include a corresponding ADC. For example, the first FRM 211 may include a first ADC 221, and the second FRM 212 may include a second ADC 222. The first ADC 221 and the second ADC 222 are configured to independently perform periodic sampling of the corresponding first and second analog signals from the first and second transducers, and convert the sampled first and second analog signals 235, 236 into first digital data signals 226 and second digital data signals 227. The periodic sampling is triggered by a periodic clock signal at a predetermined sampling frequency. In non-limiting aspects, each FRM may optionally include an internal clock. For example, the first FRM 211 may include an internal first clock 221a, and the second FRM 212 may include an internal second clock 222a. The internal first and second clocks 221a, 222a may be communicatively coupled to the first and second controllers 241, 242, respectively, or communicatively coupled to the first and second ADCs 221, 222, respectively, or both.

[0033] Each FRM 210 may also include a set of corresponding input and output (I / O) ports 248 that are communicatively coupled to the data communication network 220. For example, the first FRM 211 may have a set of first I / O ports 248a, and the second FRM 212 may have a set of second I / O ports 248b. Each of the corresponding I / O ports 248 may be communicatively coupled to the data communication network 220. In various aspects, the sets of first and second I / O ports 248a, 248b may include corresponding memory-mapped I / O ports. In non-limiting aspects, each set of first and second I / O ports 248a, 248b may include corresponding first or second I / O ports 248a, 248b associated with or dedicated to a set of channels. For example, in some aspects, a particular first or second I / O port 248a, 248b may be associated with or dedicated to the receipt of a clock signal including time synchronization information, while another particular first or second I / O port 248a, 248b may be associated with or dedicated to the receipt of a sensing or analog signal.

[0034] Each FRM 210 may also include a corresponding controller or processor. For example, the first FRM 211 may include a first controller 241 (such as a CAM controller 241), and the second FRM 212 may include a second controller 242 (such as an ICS controller 242). Each respective first and second controller 241, 242 may be configured to run any suitable program or program code. Although not shown, it should be understood that each FRM 210 may include or be associated with any suitable number of separate microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components, and the respective FRM 210 may include machine executable code, any number of software programs (e.g., data logging programs), or other instructions designed to perform or cooperate with various methods, processing tasks, calculations, and control / display functions required for the intended operation of the respective FRM 210. The respective first and second controllers 241, 242 may include any known processor, microcontroller or logic device, including but not limited to: field programmable gate array (FPGA), complex programmable logic device (CPLD), application specific integrated circuit (ASIC), full authority digital engine control (FADEC), proportional controller (P), proportional integral controller (PI), proportional differential controller (PD), proportional integral differential controller (PID), hardware accelerated logic controller (e.g., for encoding, decoding, transcoding, etc.), etc., or a combination thereof. For example, in non-limiting aspects, the respective first and second controllers 241, 242 may include a respective set of field programmable gate arrays (FPGA) (not shown) with addressable memory mapped registers.

[0035] In non-limiting aspects, the data communication network 220 can define a network grid or switch structure, which includes a set of communicatively connected network switches or bridges (not shown), such as Ethernet switches. In other non-limiting aspects, the data communication network 220 can be constructed according to the TSN mode or TTE mode to communicate data using standard methods for time synchronization and traffic management, thereby allowing deterministic communication over standard Ethernet. It is envisioned that the data communication network 220 may include any desired mode, communication bus or bus topology, which will enable various aspects to operate as described herein without departing from the scope of the present disclosure. For example, in non-limiting aspects, the data communication network 220 may include a high-speed serial bus that complies with the PCIe mode. In such non-limiting aspects with a point-to-point topology that complies with PCIe, the group of separate corresponding communication links 218 can communicatively connect each FRM 210 to the data communication network 220 to achieve full-duplex communication of data packets between any two end nodes (e.g., FRM210 or CVFDR 250), where there is no inherent limitation on concurrent access between multiple end nodes. In non-limiting aspects, the set of communication links 218 can communicatively couple one or more FRMs 210 to the CVFDR 250, the data communications network 220, the 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 set of communication links 218 can include any one or more of 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 configure FRM 210 devices when communicatively coupled to the data communications network 220.

[0036] The CVFDR memory 255 may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic memory, such as a disk, a digital versatile disk (DVD), a compact disk read-only memory (CD-ROM), etc., or any suitable combination of these types of memory. In some aspects, the CVFDR memory 255 may be configured as a shareable memory.

[0037] The CVFDR 250 controller 256 may be configured to run any suitable program or program code to enable the various aspects to operate as described herein. Although not shown, it is understood that each CVFDR 250 may include or be associated with any suitable number of separate microprocessors, power supplies, storage devices, interface cards, controller modules, and other standard components, and the corresponding CVFDR 250 may include or cooperate with machine executable code, any number of software programs (e.g., data logging programs) or other instructions designed to perform the various methods, processing tasks, calculations, and control / display functions required for the intended operation of the corresponding CVFDR 250. The CVFDR 250 may include any known processor, microcontroller, or logic device, including, but not limited to, a field programmable gate array (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 differential controller (PD), a proportional integral differential controller (PID), a hardware accelerated logic controller (e.g., for encoding, decoding, transcoding, etc.), etc., or a combination thereof.

[0038] CVFDR 250 may be communicatively coupled to a data bus or data communications network (not shown) of aircraft 10 via data bus interface 202. Flight recorder system 200 may receive or collect data from first FRM 211 or second FRM 212 via data bus or data communications network 220 and provide the data to CVFDR 250.

[0039] The flight recorder system 200 may also receive or collect data from the data bus or data communications network 220 and provide the data to one or more of the first and second FRMs 211 , 212 .

[0040] In various aspects, the master clock computing function 260 can be communicatively coupled to the data communications network 220. In non-limiting aspects, the master clock computing function 260 can be embodied in a separate device or system that is communicatively coupled to the aircraft computer 22. In other aspects, the master clock computing function 260 can include or cooperate with the master clock computing function 29 of the aircraft computer 22. The master clock computing function 260 is configured to provide a master clock signal 265 to the LRU 31 via the data communications network 220 according to a known protocol. The master clock signal 265 can be a timing signal indicating a predetermined sampling frequency (e.g., 16kHz). In various aspects, the master clock signal 265 can include a waveform, a pulse, a timestamp, or a combination thereof. The master clock computing function 260 can include an internal clock 261.

[0041] In some non-limiting aspects, the master clock calculation function 260 can include a network time protocol (NTP) server (not shown). It is contemplated that in non-limiting aspects, the NTP server can be coupled to another server, such as a local time server or a public time server (not shown), to receive a clock signal therefrom. For example, in non-limiting aspects, the other server can be communicatively coupled to a U.S. GPS satellite constellation, a network time protocol server, a CDMA cellular telephone network, a modem connection to a time source, etc. In some aspects, the master clock calculation function 260 can be configured to adjust or correct the internal clock 261 based on a clock signal received from another server.

[0042] In operation, the first sensor 231 of the first FRM 211 and the second sensor 232 of the second FRM 212 can independently sense audio or sound. For example, in non-limiting aspects, the first sensor 231 may include a conventional CAM sensor 231 configured to sense sound events in the cockpit. In another example, the second sensor 232 may include a conventional ICS sensor 232 configured to sense voice events. The first sensor 231 may generate a first analog signal 235 indicating a first parameter (e.g., cockpit sound) and provide the first analog signal 235 to the first ADC 221. The second sensor 232 may generate a second analog signal 236 indicating a second parameter (e.g., voice in the cockpit) and provide the second analog signal 236 to the second ADC 222. The first ADC 221 is configured to sample the first analog signal 235 at a predetermined frequency (e.g., 16kHz) and then digitize the sampled first analog signal 235 to generate a first digital data signal 226. More specifically, the first ADC 221 is configured to sample the first analog signal 235 based on a corresponding clock signal indicating a predetermined frequency.

[0043] Similarly, the second ADC 222 is configured to sample the second analog signal 236 at a predetermined frequency (e.g., 16 kHz), and then perform an operation of digitizing the sampled second analog signal 236 to generate a second digital data signal 227. More specifically, the second ADC 222 is configured to sample the second analog signal 236 based on a corresponding clock signal indicating the predetermined frequency.

[0044] Unlike conventional techniques, which typically use the corresponding internal clocks of the ADC as internal sampling rate clocks, which independently generate corresponding clock signals without any synchronization therebetween, thereby triggering corresponding sampling of the analog signal at a predetermined sampling frequency, in some aspects, the first and second FRMs 211, 212 instead receive the master clock signal 265 and synchronize the corresponding sampling operations of the first and second clocks 221a, 221b based on the master clock signal 265.

[0045] For example, in operation, the master clock calculation function 260 can send or transmit the master clock signal 265 to one or more devices (such as the computer 22, or the first and second controllers 241, 242, or the first and second ADCs 221, 222, or a combination thereof) via the data communication network 220. In some aspects, the master clock calculation function 260 can transmit the master clock signal 265 to the computer 22, which can then send the master clock signal 265 to other devices connected to the data communication network 220, such as the first and second controllers 241, 242, or the first and second FRMs 211, 212. The first FRM 211 and the second FRM 212 can receive the master clock signal 265 at their respective I / O ports 248a, 248b, for example, via the communication link 218. The master clock calculation function 260 can be configured to encode the master clock signal 265 to indicate to a recipient or consumer device (such as the first FRM 211 and the second FRM 212) that the master clock signal 265 includes time synchronization information. The time synchronization information may include data indicating a reference time (such as a local time). In some non-limiting aspects, the master clock signal 265 may include a carrier wave. In non-limiting aspects, the master clock signal 265 may include one or more pulses. In some aspects, at least a portion of the master clock signal 265 may be modulated or amplitude shift keyed. In other non-limiting aspects, the master clock signal 265 may be provided from the master clock 260 as a timestamp to the first or second controller 241, 242, or both. The first and second controllers 241, 242 may compensate or adjust the internal first and second clocks 221a, 222a, respectively, based on the timestamp of the received master clock signal 265, such as by using an oscillator tuning circuit, to control or adjust the sampling frequency of the first and second ADCs 221, 222 based on the received master clock signal 265. By adjusting the internal first and second clocks 221a, 222a based on the received master clock signal 265, the sampling frequencies of the first and second ADCs 221, 222 are synchronized with each other based on the received master clock signal 265.

[0046] Regardless of the waveform or encoding of the master clock signal 265, in non-limiting aspects, the first and second FRMs 211, 212 synchronize the respective sampling operations of the first and second ADCs 221, 222 based on the master clock signal 265 without requiring local or internal first and second ADC clocks 221a, 222a to generate the respective clock signals. For example, in non-limiting aspects, the first and second ADCs 221, 222 can sample the first and second analog signals 235, 236 at a predetermined common multiple of the master clock signal 265 frequency (e.g., 16kHz).

[0047] The first ADC 221 may then convert the first analog signal 235 into a first digital data signal 226 and then provide the first digital data signal 226 to the first controller 241. Similarly, the second ADC 222 converts the second analog signal 236 into a second digital data signal 227 and then provides the second digital data signal 227 to the second controller 242.

[0048] In a non-limiting aspect, the first controller 241 transmits the first digital data signal 226 as a set of first data packets 246 or data frames to the CVFDR 250 via the data communication network 220. The first data packets 246 can have any desired size and contain any desired number of digitized data samples. Each first data packet 246 can indicate a portion (e.g., 20 milliseconds (ms)) of the first digital data signal 231 based on a predetermined sampling frequency (e.g., 16kHz) and the desired size of the first data packet 246 (e.g., 320 samples). In a non-limiting aspect, the second controller 242 transmits the second digital data signal 227 as a set of second data packets 247 or data frames to the CVFDR 250 via the data communication network 220. The second data packets 247 can have any desired size and contain any desired number of digitized data samples. Each second data packet 247 can indicate a portion (e.g., 20ms) of the second digital data signal 227 based on a predetermined sampling frequency (e.g., 16kHz) and the desired size of the second data packet 247 (e.g., 320 samples).

[0049] The first and second data packets 246, 247 may include information indicating a transmission time, i.e., a timestamp. The first controller 241 and the second controller 242 provide timestamp information in the first data packet 246 and the second data packet 247, respectively, at the transmission time to the CVFDR 250 (e.g., in the data header of each of the first and second data packets 246, 247). In various aspects, the first controller 241 and the second controller 242 may determine the timestamp information based on the master clock signal 265 received from the master clock calculation function 260. In non-limiting aspects, the transmission time may indicate the start time of a sampling period of the data in the corresponding first data packet 246 or second data packet 247. In other non-limiting aspects, the transmission time may indicate the end time of the sampling period of the data in the corresponding first data packet 246 or second data packet 247. Regardless of the specific sampling period indicated by the timestamp information, the transmission time indicated by the timestamp is based on the master clock signal 265 received from the master clock calculation function 260.

[0050] In this way, synchronization of the sampling frequencies of the first and second ADCs 221, 222, and synchronization of the transmission times of the first and second digital data signals 226, 227 of the first and second ADCs 221, 222 to the CVFDR 250 via the data communication network 220 are based on the master clock signal 265 from the master clock calculation function 260, without the need for local or internal first and second ADC clocks 221a, 222a to generate corresponding clock signals.

[0051] Figure 3 A non-limiting example of a method 300 for operating the flight recorder system 200 of the aircraft 10 is shown. The method 300 may be performed while the aircraft 10 is in flight, pre-flight (e.g., before executing a flight plan), or post-flight (e.g., after a flight). Although described in terms of the flight recorder system 200, it should be understood that the method 300 may be applied to any suitable avionics device configured to sample and transmit data to any other suitable avionics device. Although for ease of understanding herein, the method 300 will be described in terms of the flight recorder system 200. Figure 1 Aircraft 10 and Figure 2 The method is described with reference to the flight recorder system 200 of FIG. 1 , but is otherwise not limited thereto, and the method 300 may be implemented with any desired flight recorder system on any desired aircraft without departing from the scope of the present disclosure.

[0052] The flight recorder system 200 may include a CVFDR 250 and an LRU 31, the LRU 31 including a set of flight recorder modules (FRMs) 210. The CVFDR 250 may be coupled to the set of FRMs 210 via a data communications network 220. In non-limiting aspects, the data communications network 220 may include a data communications network of the flight recorder system 200. In other aspects, the data communications network 220 may additionally or alternatively include a data communications network 220 of the aircraft 10. A master clock computing function 260 may also be communicatively coupled to the data communications network 220. In non-limiting aspects, the master clock computing function 260 may be embodied in a separate device or system communicatively coupled to the aircraft computer 22. In other aspects, the master clock computing function 260 may include or cooperate with the master clock computing function 29 of the aircraft computer 22. The master clock computing function 260 may provide a master clock signal 265 to the LRU 31 via the data communications network 220 according to a known protocol. The master clock signal 265 may be a timing signal indicating a predetermined sampling frequency (eg, 16 kHz). In various aspects, the master clock signal 265 may include a waveform, a pulse, a timestamp, or a combination thereof. The master clock calculation function 260 may include an internal clock 261 .

[0053] In some aspects, the set of FRMs 210 may include a first FRM 211 and a second FRM 212. For example, in one non-limiting aspect, the first FRM 211 may be a CAM 211 and the second FRM 212 may be an ICS 212. The first FRM 211 may include a first sensor 231 configured to sense a first parameter (e.g., ambient sound) and generate a first analog signal 235 indicative of the sensed first parameter. The second FRM 212 may include a second sensor 232 configured to sense a second parameter (e.g., intercom sound) and generate a second analog signal 236 indicative of the second sensed parameter.

[0054] The first FRM 211 may include a first controller 241, and the second FRM 212 may include a second controller 242. Each respective first and second controller 241, 242 may be configured to run any suitable program or program code. The first FRM 211 and the second FRM 212 may optionally include a first clock 221a and a second clock 222a, respectively. The first and second clocks 221a, 222a may be communicatively coupled to the first and second controllers 241, 242, respectively, or communicatively coupled to the first and second ADCs 221, 222, respectively, or both. The first FRM 211 and the second FRM 212 may have the group of first I / O ports 248a and the group of second I / O ports 248b, respectively, which are communicatively coupled to the data communication network 220.

[0055] The method 300 may include, at 310, communicatively coupling the CVFDR to the first FRM 211 via the data communication network 220. The first FRM 211 may include a first sensor 231 configured to generate a first analog signal 235, the set of input and output (I / O) ports 248 communicatively coupled to the data communication network 220, a first controller 241, and a first ADC 221.

[0056] The method 300 may include, at 320, receiving a master clock signal 265 from the data communication network 220 by the first FRM 211, the second FRM 221, or both. The method 300 may also include, at 330, generating a first analog signal 235 by the first sensor 231. The method 300 may include, at 340, sampling the first analog signal 235 by the ADC 221 based on the master clock signal 265 to convert the first analog data signal 235 into a first digital data signal 226. In non-limiting aspects, the master clock signal 265 indicates a predetermined sampling frequency (e.g., 16kHz). In other non-limiting aspects, the master clock signal 265 may be provided as a timestamp from the master clock 260 to the first or second controller 241, 242, or both. The first and second controllers 241, 242 may compensate or adjust the first and second clocks 221a, 222a, respectively, based on the timestamp of the received master clock signal 265. In some aspects, sampling the first analog signal 235 by the ADC 221 can include adjusting the first clock 221a based on the received master clock signal 265. For example, the master clock signal 265 can be provided as a timestamp from the master clock 260 to the first or second controller 241, 242, or both. The first and second controllers 241, 242 can compensate or adjust the first and second clocks 221a, 222a, respectively, based on the timestamp of the received master clock signal 265.

[0057] The method 300 may also include, at 350, transmitting the first digital data signal 226 from the first controller 241 to the CVFDR 250 via the data communication network 220. In non-limiting aspects, the first digital data signal 226 may be transmitted as a set of first data packets 246. In some non-limiting aspects, the method 300 may include, at 360, including in each first data packet 247 an indication of a first transmission time based on the master clock signal 265.

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

[0059] For example, in non-limiting aspects, the CVFDR 250 can be communicatively coupled to the second FRM 212 via the data communication network 220. In such non-limiting aspects, the method 300 can further include, for example, generating a second analog signal 236 by the second sensor 232. The method 300 can also include providing the master clock signal 265 to the second FRM 212 via the data communication network 220, and sampling the second analog signal based on the master clock signal 265 by the second ADC 212 to convert the second analog signal 236 into a second digital data signal 227. In some aspects, sampling the second analog signal 236 by the second ADC 212 can include adjusting the second clock 222a based on the received master clock signal 265. For example, the master clock signal 265 can be provided as a timestamp from the master clock 260 to the second controller 242. The second controller 242 can compensate or adjust the second clock 222a based on the timestamp of the received master clock signal 265. The method 300 may include synchronizing the first clock 221a and the second clock 222a based on the master clock signal 265. For example, by adjusting the first or second clock 221a, 222a, or both based on the received master clock signal 265, the sampling frequency of the first ADC 221 may be synchronized with the sampling frequency of the second ADC 222 based on the received master clock signal 265.

[0060] The method 300 may also include transmitting the second digital data signal 227 from the second controller 242 to the CVFDR 250 via the data communication network 220. In non-limiting aspects, the first digital data signal 226 may be transmitted as a set of second data packets 247. In some non-limiting aspects, the method 300 may include including in each second data packet 247 an indication of a second transmission time based on the master clock signal 265.

[0061] It is contemplated that aspects of the present disclosure may be advantageous for use over conventional systems or methods for constructing and operating flight recorders. Aspects of the present disclosure enable audio streams to have synchronized sampling rates without the need for computationally intensive sampling rate conversion or additional post-recording processing in real time to convert all streams to the sampling rate (or a factor thereof). For example, aspects disclosed herein may enable real-time synchronization of the sampling frequencies of the ADCs in multiple FRMs to eliminate the need for post-processing of the digitized data streams received from the FRMs. Such synchronization may reduce errors and discontinuities associated with such post-processing. Additionally, such synchronization may free up computational bandwidth that would otherwise be required for real-time processing of multiple audio streams.

[0062] It is further contemplated that aspects of the present disclosure may advantageously provide synchronized sampling rates over the life of the LRU and over a wide operating temperature range because all conversions are synchronized by the master clock rather than by individual LRU internal clocks that may exhibit variations over time and temperature.

[0063] It is further contemplated that aspects of the present disclosure may enable simpler and less expensive CVFDR construction because the disclosed aspects eliminate the need to construct and program the CVFDR to determine and perform sample rate conversion in real time as required by conventional systems.

[0064] To the extent not yet described, the different features and structures of the various embodiments may be used in combination with each other as desired. A feature not shown in all embodiments is not meant to be interpreted as it may not be included, but is done so for the sake of brevity of description. Therefore, the 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 the present disclosure.

[0065] 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 combined method. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. These other examples are intended to fall within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims.

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

[0067] A flight recorder system of an aircraft, comprising: a cockpit voice and flight data recorder (CVFDR), which is communicatively connected to a first flight recorder module (FRM); and the first FRM includes a first sensor configured to generate a first analog signal, a first controller and a first analog-to-digital converter (ADC), the first ADC being configured to sample the first analog signal based on a received master clock signal and convert the first analog signal into a first digital data signal, and the first controller being configured to provide the first digital data signal to the CVFDR.

[0068] A flight recorder system as in any preceding clause, wherein the first ADC comprises a first clock, and wherein the controller is further configured to adjust the first clock based on the received master clock signal.

[0069] A flight recorder system according to any preceding clause, wherein the first controller is configured to transmit the first digital data signal to the CVFDR as a first set of data packets, each first data packet indicating a portion of the first digital data signal, the portion being based on a predetermined sampling time period.

[0070] A flight recorder system as claimed in any preceding clause, wherein each first data packet comprises an indication of a first transmission time of the respective first data packet.

[0071] A flight recorder system as in any preceding clause, wherein the first transmission time indicates a time of one of a start of a predetermined sampling time period or an end of the predetermined sampling time period.

[0072] A flight recorder system as described in any preceding clause, wherein the first transmission time is based on the master clock signal.

[0073] A flight recorder system as described in any preceding clause, wherein the first FRM is configured to receive the master clock signal from a data communications network.

[0074] A flight recorder system as claimed in any preceding clause, wherein the master clock signal is provided by a master clock computing function communicatively coupled to the data communications network.

[0075] A flight recorder system according to any of the preceding clauses, wherein the CVFDR is further communicatively connected to a second FRM, the second FRM comprising a second sensor configured to generate a second analog signal, a second controller and a second ADC, the second ADC being configured to sample the second analog signal based on a received master clock signal and convert the second analog signal into a second digital data signal, the second controller being configured to provide the second digital data signal to the CVFDR.

[0076] A flight recorder system as in any preceding clause, wherein the first and second clocks are synchronized based on the master clock signal.

[0077] A method for operating a flight recorder system of an aircraft, the flight recorder system including a CVFDR, the CVFDR being communicatively connected to a first FRM, the first FRM including a first sensor, a first controller and a first ADC configured to generate a first analog signal, the method including: receiving a master clock signal from a master clock calculation function by the first FRM; generating a first analog signal by the first sensor; sampling the first analog signal by the first ADC based on the master clock signal to convert the first analog signal into a first digital data signal; and transmitting the first digital data signal to the CVFDR.

[0078] A method as in any preceding clause, wherein the first ADC comprises a first clock, the method further comprising adjusting the first clock based on the received master clock signal.

[0079] A method according to any preceding clause, wherein transmitting the first digital data signal to the CVFDR includes providing the first digital data signal as a set of first data packets, each first data packet indicating a respective portion of the first digital data signal, the respective portion being based on a predetermined sampling time period.

[0080] The method according to any preceding clause, further comprising including in each first data packet an indication of a first transmission time of the corresponding first data packet; wherein the first transmission time indicates one of the beginning of the predetermined sampling time period or the end of the predetermined sampling time period.

[0081] A method as in any preceding clause, wherein the first transmission time is based on a received master clock signal.

[0082] A method according to any of the preceding clauses, wherein the CVFDR is communicatively connected to a second FRM, the second FRM comprising a second sensor, a second controller and a second ADC configured to generate a second analog signal, the method further comprising: receiving the master clock signal by the second FRM; generating a second analog signal by the second sensor; sampling by the second ADC based on the received master clock signal to convert the second analog signal into a second digital data signal; and transmitting the second digital data signal from the second controller to the CVFDR.

[0083] A method as in any preceding clause, wherein the second ADC comprises a second clock, the method further comprising adjusting the second clock based on the received master clock signal.

[0084] A method as in any preceding clause, further comprising synchronizing the first clock and the second clock based on the master clock signal.

[0085] A method as in any preceding clause, further comprising communicatively coupling the first FRM to a data communications network.

[0086] A method as in any preceding clause, wherein the master clock signal is received by the first FRM from the data communications network.

Claims

1. A flight recorder system for an aircraft, It is characterized in that include: a cockpit voice and flight data recorder (CVFDR) communicatively coupled to a first flight recorder module (FRM); and The first FRM includes a first sensor configured to generate a first analog signal, a first controller, and a first analog-to-digital converter (ADC), wherein the first ADC is configured to sample the first analog signal based on a received master clock signal and convert the first analog signal into a first digital data signal, and the first controller is configured to provide the first digital data signal to the CVFDR.

2. The flight recorder system according to claim 1, It is characterized in that in, The first ADC includes a first clock, and wherein the controller is further configured to adjust the first clock based on the received master clock signal.

3. The flight recorder system according to claim 1, It is characterized in that in, The first controller is configured to transmit the first digital data signal to the CVFDR as a first set of data packets, each first data packet indicating a portion of the first digital data signal, the portion being based on a predetermined sampling time period.

4. The flight recorder system according to claim 3, It is characterized in that in, Each first data packet includes an indication of a first transmission time of the corresponding first data packet.

5. The flight recorder system according to claim 4, It is characterized in that in, The first transmission time indicates a time of one of a start of a predetermined sampling period or an end of the predetermined sampling period.

6. A method of operating a flight recorder system of an aircraft, the flight recorder system comprising a CVFDR, the CVFDR communicatively coupled to a first FRM, the first FRM comprising a first sensor configured to generate a first analog signal, a first controller, and a first ADC, It is characterized in that The method comprises: Receiving, by the first FRM, a master clock signal from a master clock calculation function; generating a first analog signal by the first sensor; The first ADC samples the first analog signal based on the master clock signal to convert the first analog signal into a first digital data signal; and The first digital data signal is transmitted to the CVFDR.

7. The method according to claim 6, It is characterized in that in, The first ADC includes a first clock, and the method further includes adjusting the first clock based on the received master clock signal.

8. The method according to claim 6, It is characterized in that in, Transmitting the first digital data signal to the CVFDR includes providing the first digital data signal as a set of first data packets, each first data packet indicating a respective portion of the first digital data signal, the respective portion being based on a predetermined sampling time period.

9. The method according to claim 8, It is characterized in that Further comprising including in each first data packet an indication of a first transmission time of the corresponding first data packet; wherein the first transmission time indicates a time of one of a beginning of the predetermined sampling time period or an end of the predetermined sampling time period.

10. The method according to claim 9, It is characterized in that in, The first transmission time is based on a received master clock signal.