Patent Application
20160217095
The present invention relates generally to aircraft electronic systems, and in particular to a modular system for aircraft electronic components.
Aircraft systems, such as engine control systems, fuel control systems, lighting systems, and other control systems are often implemented electronically and communicate over aircraft data buses. These aircraft may implement, for example, network based backbone systems to send and receive data to and from signal interface units (SIU) to system level computers. In the past, the SIUs have been implemented as unique devices that accomplish a single task and are tailored for specific aircraft. This design can become quite costly because every new aircraft requires a new set of boxes regardless of whether functionality remains the same. It is desirable to create electronic systems that are modular and may be utilized in multiple aircraft.
A signal interface unit for use on an aircraft includes a microcontroller, at least one connector, and first and second communication links. The first communication link is connected between the microcontroller and the at least one connector. The microcontroller is configured to transmit and receive data on the first communication link. The second communication link is connected to the microcontroller. The microcontroller is configured to send and receive data on an aircraft data bus using the second communication link.
A modular signal interface unit (SIU) is disclosed herein that may be utilized to interface with any aircraft subsystem module. An aircraft electronics system may include a plurality of modular SIUs connected to, for example, aircraft data buses. A plurality of subsystem modules may be connected to each modular SIU. The subsystem modules may be used, for example, to provide control, or perform other critical functions, for aircraft systems. Each subsystem module may be removed, replaced, and/or repaired at any time.
Each SIU may interface with any subsystem module through multiple communication links. These may include, for example, high speed deterministic and non-deterministic links as well as low-speed links. Power may also be controlled and supplied to each subsystem module through the SIU. The SIU may communicate with other electronic systems on the aircraft over the aircraft data buses. The SIU may communicate with the aircraft bus using, for example, a triplex time-deterministic communication link to ensure data integrity to and from control systems. Configuring aircraft electronic systems in this way is advantageous in that aircraft control systems may be easily removed, repaired, and/or replaced. This also provides system redundancy by allowing, for example, multiple redundant subsystem control modules to be attached to separate SIUs onboard the aircraft.
SIU 12 may be implemented, for example, as a generic interface that acts as a gateway for subsystem modules 14a-14n to aircraft data bus 16. Aircraft data bus 16 may be, for example, an Aeronautical Radio, Incorporated (ARINC®) bus, a Controller Area Network (CAN) bus, or any other data bus utilized onboard aircraft. For example, subsystem modules 14a-14n may be utilized for landing gear systems, fuel systems, avionics systems, and/or any other aircraft electronic systems.
Subsystem modules 14a-14n provide, for example, specific control or monitoring for aircraft systems. Connectors 20a-20n of subsystem modules 14a-14n are connectable to any of connectors 18a-18n of any SIU 12. This allows any subsystem module 14a-14n to be swapped with any other subsystem module 14a-14n at any time. This makes removal, repair, and replacement of aircraft electronic systems more convenient, cheaper, and timelier.
In an embodiment, subsystem module 14a may, for example, read vibration channels for engine vibration. Subsystem module 14a may, for example, quantify the vibration data, perform signal processing (such as analog-to-digital and/or digital-to-analog conversion), determine faults, and/or perform any other function relating to the monitored vibration data. Subsystem 14a may then send the data to SIU 12 through connector 20a. SIU 12 may then, for example, relay the data to a health monitoring control unit (not shown) over aircraft data bus 16. Because all of the hardware utilized to sample and convert the vibration data is contained within subsystem module 14a, subsystem module 14a may be easily moved from one SIU 12 to another. This way, subsystem modules 14a-14n may all have a common interface through respective connector 20a-20n, as opposed to requiring the ability to interface with each aircraft bus as well as other aircraft electronic systems directly. This provides the ability to remove and replace subsystem modules 14a-14n without needing to remove, repair, and/or replace entire avionics systems.
With continued reference to
External power may be received through power connector 26. This power may be received from any aircraft power source such as, for example, alternating current (AC) or direct current (DC) power buses powered by aircraft generators. Diode OR module 42 may be utilized, for example, to select the input power line having the highest signal quality. Local power supply 44 may condition and provide power for the local components of SIU 12. Module power supply 46 may condition and provide power to, for example, external systems such as subsystem modules 14a-14n. Power is provided to these external systems through individual hot-swap controllers 48. Hot-swap controllers 48 may be utilized to allow external components that receive power to be removed or replaced without shutting off power to SIU 12.
Controller 30 may be implemented as any communication based processor such as, for example, a Freescale® Qor1Q T1040, or any other suitable microcontroller. In an embodiment, controller 30 may perform no computations for specific aircraft functions. Rather, SIU 12 may provide an industry standard interface, such that any subsystem module 14a-14n may interface with any SIU 12, regardless of the aircraft in which SIU 12 is installed. Memory 34 may be implemented for use with controller 30 and may be any suitable memory such as, for example, double data rate type three (DDR3) synchronous dynamic random-access memory (SRAM). Controller 30 may also interface with data logger 38 which may be, for example, a sixty-four gigabyte (GB) non-volatile memory that interfaces with controller 30 through a universal serial bus (USB) connection.
In the embodiment shown in
In addition to interface 22, SIU 12 may include additional communication through interface 28, which may be a peripheral component interface (PCI) mezzanine card (PMC) interface which may also communicate with controller 30 through a PCIe interface. Communication interface 28 may also be implemented as any other communication link capable of communicating with an aircraft communication bus.
In the embodiment illustrated in
SIU 12 may interface with subsystem modules 14a-14n using communication links 50, 52, and 54. Communication link 50 may be implemented as, for example, a high speed non-deterministic communication link such as Ethernet. Controller 30 may include an Ethernet switch that allows communication between each connector 18a and controller 30. The Ethernet switch may also provide a connection between controller 30 and test interface 24 such that data may be accessed from controller 30 through test interface 24.
Communication link 52 may be, for example, a high speed deterministic bus, such as a time-triggered protocol (TTP) bus. With a high speed deterministic bus, each message is scheduled at a specific time using, for example, time division multiplex access (TDMA). This provides high-integrity data communication with subsystem modules 14a-14n. Communication link 52 may be provided to connectors 18a-18n through TTP hub 56. TTP hub 56 may include a high speed port for high speed deterministic communication between controller 30 and subsystem modules 14a-14n. TTP hub 56 may also provide a low speed deterministic port for providing further deterministic communication with external systems on communication link 58 through interfaces 36.
Communication link 54 may be, for example, a low speed bus such as an inter-integrated circuit (I2C) bus. Link 54 may be utilized for status information, configuration information, built-in-test, or any other lower-priority communication. Controller 54 may also include a separate I2C bus for communication with components 32 and test connector 24, such that data from controller 30 and components 32 may be accessed through test connector 24.
Subsystem modules 14a-14n may therefore, regardless of function, be designed to include a generic interface that communicates with any SIU 12 through communication links 50, 52, and 54. While illustrated with three communication links 50, 52, and 54, SIU 12 may be configured to provide any number of communication links to each connector 18a-18n. Subsystem modules 14a-14n may also be configured to generically receive power through connectors 18a-18n from module power supply 46. Module power supply 46 may also be configured to provide power scheduling for subsystem modules 14a-14n. For example, module power supply 46 may prioritize power based upon which subsystem modules 14a-14n are connected to SIU 12. In the event of a fault or other power condition, module power supply 46 may provide prioritized power to subsystem modules 14a-14n having highest priority.
With continued reference to
In an embodiment, an aircraft may include, for example, twenty SIUs 12, three VMSCs 70, and one hundred sixty subsystem modules 14a-14n with, for example, eight subsystem modules 14a-14n connected to each SIU 12. In addition to providing improved removal, replacement, and repair for aircraft electronic systems, this implementation provides the ability for redundancy and distributed control. For example, three subsystem modules 14a-14n may be implemented for fuel control, with each module connected to a separate SIU 12. Each fuel control module may report data, through a connected SIU 12, to a VMSC 70. VMSC 70 may implement the fuel control laws and provide instructions back through SIUs 12 to the respective fuel control modules. The fuel control modules may then provide control for the respective fuel pumps, and/or valves accordingly. Although described for a fuel control system, any aircraft electronic system may be implemented in this way.
The following are non-exclusive descriptions of possible embodiments of the present invention.
A signal interface unit for use on an aircraft includes a microcontroller, at least one connector, and first and second communication links. The first communication link is connected between the microcontroller and the at least one connector. The microcontroller is configured to transmit and receive data on the first communication link. The second communication link is connected to the microcontroller. The microcontroller is configured to send and receive data on an aircraft data bus using the second communication link.
The signal interface unit of the preceding paragraph can optionally include, additionally and/or alternatively, any one or more of the following features, configurations and/or additional components:
A further embodiment of the foregoing signal interface unit, wherein the first communication link is a high speed non-deterministic data link and the second communication link is a time deterministic link.
A further embodiment of any of the foregoing signal interface units, wherein the first communication link is an Ethernet link and the second communication link is a time-triggered Ethernet link.
A further embodiment of any of the foregoing signal interface units, further including a third communication link connected between the microcontroller and the at least one connector, and a fourth communication link connected between the microcontroller and the at least one connector.
A further embodiment of any of the foregoing signal interface units, wherein the third communication link is an inter-integrated circuit link, and the fourth communication link is a high speed deterministic link.
A further embodiment of any of the foregoing signal interface units, further including a power supply unit configured to provide power through the at least one connector.
A further embodiment of any of the foregoing signal interface units, further including a data logger and a plurality of sensors.
An aircraft system comprising includes a first interface unit and a first subsystem module. The first interface unit includes a controller, a first communication link, and a second communication link. The controller is configured to transmit and receive data through the first communication link. The second communication link is configured to send and receive data to an external aircraft data bus. The first subsystem module is configured to communicate with the first interface unit through the first communication link.
The system of the preceding paragraph can optionally include, additionally and/or alternatively, any one or more of the following features, configurations and/or additional components:
A further embodiment of the foregoing system, wherein the first communication link is a high-speed non-deterministic communication link, and wherein the second communication link is a time deterministic communication link.
A further embodiment of any of the foregoing systems, wherein the first interface unit further comprises a third communication link and a fourth communication link, and wherein the first subsystem module is further configured to communicate with the interface unit through the third and fourth communication links.
A further embodiment of any of the foregoing systems, wherein the third communication link is an inter-integrated circuit link, and the fourth communication link is a high speed deterministic link.
A further embodiment of any of the foregoing systems, further including a second interface unit, wherein the first interface unit is configured to communicate with the second interface unit over the external aircraft data bus through the second communication link.
A further embodiment of any of the foregoing systems, further including a plurality of second subsystem modules configured to communicate with the first interface unit through the first communication link.
A further embodiment of any of the foregoing systems, further including a vehicle management system computer. The vehicle management system computer includes a controller configured to execute control software, and a fifth communication link configured to communicate with the external aircraft data bus, wherein the first interface unit communicates with the vehicle management system computer over the external aircraft data bus.
While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.
