Kind code of ref document : A1. Effective date : Ref country code : GB. Ref legal event code : FG4D. Kind code of ref document : B1.
|Country:||Bosnia & Herzegovina|
|Genre:||Health and Food|
|Published (Last):||4 January 2010|
|PDF File Size:||12.81 Mb|
|ePub File Size:||16.43 Mb|
|Price:||Free* [*Free Regsitration Required]|
Aeronautical Radio, Incorporated ARINC is a data bus architecture that was designed for use on aircraft and that can operate with multiple transmitting and receiving devices on a common medium. Temporary access to data transmitted using the ARINC protocol is often obtained by installing test equipment that records the data in the ARINC protocol prior to a flight and then post-processing such data once the aircraft has landed.
The addition of temporary or permanent equipment for interfacing to ARINC buses requires time for installation and troubleshooting, which is time that the aircraft cannot be used for flights, and therefore increases costs and reduces the revenue that the aircraft can generate.
Typically receiving equipment on an ARINC bus is programmed to receive a specific subset of information controlled by the device configuration. Receiving equipment may sample that data at lower than line rates and may not sample data in all flight phases. Therefore, existing avionics equipment does not provide access to all the data provided on all the buses. This lack of complete data can hinder root cause analysis and effective design improvement solutions to in-service issues or future component enhancements.
Illustrative examples of the present invention include, without limitation, a method, device, and computer-readable storage medium. The Ethernet frame may then be transmitted to a recipient device. In another aspect, an avionics device may be configured to transcode data, where the device includes a receiver configured to receive data from at least one ARINC bus, where the data is in an ARINC protocol.
The device may also include a processor configured to transcode the data and insert the data into an Ethernet frame. The device may further include a transceiver configured to transmit the Ethernet frame to a recipient device. In another aspect, a non-transitory computer-readable storage device may have computer-readable instructions stored thereon that cause a processor to receive data from at least one ARINC bus, where the data is in an ARINC protocol, and transcode the data and insert the data into an Ethernet frame.
The instructions may further cause the processor to transmit the Ethernet frame to a recipient device. Other features of the inventive systems and methods are described below.
The features, functions, and advantages can be achieved independently in various examples or may be combined in yet other examples, further details of which can be seen with reference to the following description and drawings. Examples of techniques in accordance with the present disclosure are described in detail below with reference to the following illustrations:.
This transcoded data may then be transmitted to other devices onboard the aircraft. In such examples, an ARINC Ethernet converter may function as an avionics-grade network appliance, facilitating data exchange between other devices configured onboard an aircraft. Transcoding and other processing may be performed by processor ARINC Ethernet converter may be configured with one or more processors that may perform transcoding and other tasks.
Processor configured in ARINC Ethernet converter may be a field-programmable gate array FPGA , microprocessor, programmable logic device PLD , programmable array logic PAL , electronically programmed logic devices EPLD , application specific integrated circuit ASIC , gate array, or any other type of processor, integrated circuit, or processing element that may be capable of performing one or more of the processing tasks disclosed herein.
An ARINC Ethernet converter as described herein may have any type and quantity of processing elements and any combination thereof. In FIG. In an example, onboard ARINC buses - represent a flight controls left bus, flight controls center bus, flight controls right bus, systems left bus, systems center one bus, systems center two bus, and systems right bus.
All such configurations are contemplated as within the scope of the present disclosure. Each of inputs - may be a serial interface module coupled with a terminal controller designed to receive ARINC data. Each of inputs - may be configured to process data at line speed. Each input may be configured to receive data only and not to transmit data, or may be incapable of transmitting data. In other examples, other numbers of inputs and buses may be used, and all such inputs and buses are contemplated as within the scope of the present disclosure.
In one example, a bit parallel bus may be configured between each of the inputs - and processor However, any other method or means of providing the data to processor may be used. In an example, the data may be packetized in one or more higher layer protocols e. In an example, communication between ARINC Ethernet converter and one or both of onboard devices and may be secured. A key-based security protocol may be used to authenticate communications sessions between these devices.
A system log may record all attempts to communicate with ARINC Ethernet converter and the results of such attempts. This data may be transcoded and inserted into Ethernet frames and transmitted, in an example using a security protocol, to network file servers and Note that in some examples, an aircraft may be configured with a single network file server, while in others and aircraft may be configured with more than two network file servers.
In some examples, transcoded ARINC data may be transmitted to other devices instead of, or in addition to, one or more network file servers. All such examples are contemplated as within the scope of the present disclosure. Network file servers and may be part of an onboard network system ONS that hosts applications for and provides services to users and other devices onboard an aircraft.
Thus, network file server may host applications - and network file server may host applications - Each of applications - and applications - may also, or instead, represent a service. The applications and services hosted by each of network file servers and may be distinct or network file servers and may host some or all of the same applications and services, for instance to provide redundancy.
The applications and services hosted by each of network file servers and may be any applications and services that may be configured on an ONS. Hosted applications and services may be accessed by various onboard or offboard devices, including devices - configured to communicate with network file server and devices - configured to communicate with network file server Each of these devices - and - may be a display, a terminal, a printer, a handheld device, a wireless hub, a satellite communications device, a network device, a docking station, a laptop or other computer, or any other device that may be part of, or configured to interact with, an ONS.
Each of these devices - and - may communicate directly with one of both of network file servers and , or may communicate via a network extension device NED that provides interfaces for such devices to one or both of network file servers and All such configurations, and any variations thereof, are contemplated as within the scope of the present disclosure.
Note that access to such data may be restricted or limited by network file servers and for security or any other reason. Network file servers and may store transcoded ARINC data for uploading to another device between flights or for later retrieval. Network file servers and may be configured to maintain a limited amount of transcoded ARINC data or to store such data for a limited amount of time. For example, network file servers and may be configured to retain only transcoded ARINC data received during the most recent 48 hours, one week, etc.
When permanently installed, ARINC Ethernet converter may be a line replaceable module capable of quick and easy replacement. All such configurations and any variations thereon are contemplated as within the scope of the present disclosure. Communication between ARINC Ethernet converter and network file servers and may use a key-based security protocol to authenticate communications sessions between these devices. A system log on one or both of network file servers and may record all attempts to communicate with ARINC Ethernet converter and the results of such attempts.
In an example, the data stream between ARINC Ethernet converter and each of network file servers and may be established and terminated using the session management protocol SMP. Note that ARINC Ethernet converter may be configured to establish and maintain separate and independent communications sessions with each of network file servers and simultaneously.
Method , and the individual actions and functions described in method , may be performed by any one or more devices, including those described herein. Processor-executable instructions for performing some or all of method may be stored in a memory or other storage device accessible by a processor, such as any processor described herein or otherwise, and may be executed by such a processor to create a device implementing an example of the present disclosure.
In many examples, this device may be a network file server that is part of an ONS. In other examples, this device may be some other device, such as an AIMS device. Either the ARINC Ethernet converter or the device with which it is attempting to communicate may initiate the attempt to establish a communications session.
Note that method may be performed while another communication session is ongoing with another network file server or other device. While the devices may attempt to establish any type of communications session, in one example, the session may be an SMP session using TLS for security.
At block , a determination may be made at the ARINC Ethernet converter as to whether the session has been successfully established.
If not, method may return to block to await another attempt to establish a communications session with a device. If the session is successfully established, the ARINC Ethernet converter may proceed to communicate with the network file server or other device with which it has established the session. While any ports and protocols may be used to exchange communications, in one example, data may be exchanged on UDP port At block , a determination may be made as to whether an instruction has been received to stop transmitting transcoded ARINC data to the network file server or other device with which the ARINC Ethernet converter is communicating.
So, upon session establishment and receipt of instruction to transmit transcoded ARINC data, at block the ARINC Ethernet converter may determine if a heartbeat packet has been received from the network file server or other device with which the ARINC Ethernet converter is communicating. In some examples there is a preconfigured or specified time limit within which a heartbeat packet must be received e. If a heartbeat packet has been received in due time, at block , operation may continue.
If not, the ARINC Ethernet converter may return to block , assuming that the session must be down or will soon be down due to loss of contact with the network file server or other device with which the ARINC Ethernet converter is communicating. Alternatively, the ARINC Ethernet converter may be configured to continue operation until the communications session is definitively determined to be down. While heartbeat methods and mechanisms of any type are contemplated, in an example, a network file server may transmit heartbeat packets using the session control protocol SCP and communicating over TCP port It will be appreciated that, while processor-executable instructions are described as being stored in memory or on storage while being used, these instructions or portions of them may be transferred between memory and other storage devices.
Alternatively, in other examples some or all of the instructions may execute in memory on another device and communicate with the described systems via inter-computer communication. Some or all of the instructions, systems and data structures may also be stored e. The systems, instructions, and data structures may also be transmitted as generated data signals e.
Such computer program products may also take other forms in other examples. Accordingly, the present invention may be practiced with other computer system configurations. In some examples, a system memory may be used that is a computer-readable storage medium configured to store program instructions and data as described above for FIGS.
Generally speaking, a computer-readable storage medium may include non-transitory and tangible storage media or memory media such as magnetic or optical media, e. A computer-readable storage medium may also include any volatile or non-volatile media such as RAM e. Portions or all of the systems such as those illustrated herein may be used to implement the described functionality in various examples. For example, software components running on a variety of different devices and servers may collaborate to provide the disclosed functionality.
It will be appreciated that in some examples the functionality provided by the routines discussed above may be provided in alternative ways, such as being split among more routines or consolidated into fewer routines. Similarly, in some examples, illustrated routines may provide more or less functionality than is described, such as when other illustrated routines instead lack or include such functionality respectively or when the amount of functionality that is provided is altered.
In addition, while various operations may be illustrated as being performed in a particular manner e. Similarly, the data structures discussed above may be structured in different ways in other examples, such as by having a single data structure split into multiple data structures or by having multiple data structures consolidated into a single data structure, and may store more or less information than is described e. In general, the various features and processes described above may be used independently of one another, or may be combined in different ways.
All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate.
For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example examples.
US9369548B2 - Arinc 629 ethernet converter - Google Patents
Aeronautical Radio, Incorporated ARINC is a data bus architecture that was designed for use on aircraft and that can operate with multiple transmitting and receiving devices on a common medium. Temporary access to data transmitted using the ARINC protocol is often obtained by installing test equipment that records the data in the ARINC protocol prior to a flight and then post-processing such data once the aircraft has landed. The addition of temporary or permanent equipment for interfacing to ARINC buses requires time for installation and troubleshooting, which is time that the aircraft cannot be used for flights, and therefore increases costs and reduces the revenue that the aircraft can generate. Typically receiving equipment on an ARINC bus is programmed to receive a specific subset of information controlled by the device configuration. Receiving equipment may sample that data at lower than line rates and may not sample data in all flight phases.
Subscribe to RSS
The opening of the skies with the development of the first real commercial aircraft in the year was a milestone in the history of civilization and the cornerstone for the emergence of complex systems and high-value technologies that even offered the highest possible level of safety above the clouds. However nowadays, when looking normally at an aircraft, it is hardly possible to see the many thousands of mosaic parts that make it possible for such a means of transportation to take off. These also include the ARINC , a bi-directional bus system of multiple transmitters, specially developed by Boeing for one of their aircraft, the Boeing In the meantime, terminals can now be connected thanks to this technology. This is a term used for all the electronic instruments in an aircraft - excluding the cabin. Here, the data transmission takes place at exactly specified time intervals and via a two-wire line that may be either optical or electrical. ARINC has become indispensable in avionics, as thanks to several improvements, it now reliably ensures safety and problem-free functionality of the devices in an aircraft.