The ARINC “Avionics Digital Video Bus” standard was released in January Even before its official release, major programs by both. The 8b/10b-encoded ARINC video interface and protocol draws heavily on the older FC-AV standard. ARINC manages high-bandwidth, low-latency. The ARINC Specification is an industry standard that defines a digital video interface link and protocol that is used for high-speed digital video display data.
|Genre:||Health and Food|
|Published (Last):||17 June 2016|
|PDF File Size:||16.53 Mb|
|ePub File Size:||13.23 Mb|
|Price:||Free* [*Free Regsitration Required]|
Even before its official release, major programs by both Airbus AM military stzndard and Boeing Dreamliner adopted the protocol for their critical video subsystems. Since it is now being used in military, commercial and business aircraft, many avionics vendors may need to implement the protocol in the 81 future to maintain compatibility.
Prior to the adoption of ARINCthere was no standard for avionics video, making each new cockpit design more expensive due to proprietary video formats required by displays and video systems. For the unfamiliar, there is a learning 88 associated with the FC-AV protocol and its terminology. The specification is available online from ARINC, and other readily available resources will help reduce the learning curve, including two industry Web sites — www.
Whereas the FC-AV standard intends to support a very broad set of industries and applications, ADVB focuses specifically on the needs of avionics video. ADVB is simplified over FC-AV because it is unidirectional, and has no requirements for link initialization, flow control or other Fibre Channel exchanges such as port log in. Although simplified, ADVB retains attributes of Fibre Channel that wtandard beneficial for mission critical video applications, such as high speed, high reliability, low latency and flexibility.
The protocol is packetized, video-centric and very flexible, supporting an array of complex video implementations including the multiplexing of multiple video streams onto a single link or the transmission of a single stream over a dual link for ultra-high bandwidth. Four different timing classes, A through D, are defined. Class A is asynchronous, like moving a. It is important to refer to these packets as “ADVB frames” rather than simply “frames” to eliminate potential confusion with video frames.
Every ADVB frame has a header comprised of six bit words. The “payload” contains either video or video parameters and ancillary data.
The payload can vary in size but is limited to 2, bytes maximum. In other words, a video image and data are encapsulated into a container that spans many ADVB frames. That is, certain ADVB frames within the container are part of an object. The four types of objects found within a container are: Implementations that use the Fibre Channel rates of 1.
Sticking to these rates will also eliminate potential hazards for using Fibre Channel chips and transceivers outside of their intended operational speed.
The ARINC Standard
The ARINC arinf itself does not place constraints on the timing of the ADVB frames during transmission or the methods of synchronizing at the pixel, line or frame level.
Adding the protocol overhead and blanking time, a standard link rate of 3. The payload of the first FC frame in a sequence contains container header data that accompanies each video image.
Therefore, each video line is divided evenly into two FC frames. Because the display that this transmitter drives requires “line synchronous” timing, this transmitter is classified as Class C, line synchronous. Additionally, a header frame is added, making a total of 2, FC frames. ARINC allows for flexibility in the implementation of the video interface. This flexibility is desirable, because of the diverse resolutions, grayscales, pixel formats and stanvard rates of avionics display systems.
However, this flexibility is a problem for equipment venders hoping for some degree of interoperability. The ICD will specify parameters of the link such as link speed, image resolution, synchronization scheme, frame rate, etc. Typically, a military program, or commercial avionics development program, will have an associated ICD.
Following the steps will save time in learning the protocol, and facilitate a smoother implementation. Johnson, of Rockwell Collins, chose a device with built-in support for Fibre Channel. As ARINC propagates through avionics systems for both military and commercial aircraft, investing a few days early-on to understand the protocol, create a draft ICD and investigate implementation options will save valuable time before a proposal is needed that requires an ARINC interface.
It is best to evaluate the effort to incorporate ARINC at least six months standarv it is needed in an avionics system.
Following the four steps outlined below will help one understand the time, cost and manpower that will be required to implement ARINC For those rainc familiar with Fibre Channel, it will take a couple of passes through the document to become familiar with the terminology and protocol.
Before reading the specification itself, it is good to look at a summary of the protocol, found at www. Understand other system elements. Typically, the cockpit multifunction or primary flight displays will determine the video resolution, timing and update rate for the entire video system.
If a Helmet-Mounted Display is the end display, video latency may be the key design parameter. The point is a downstream receiver typically drives the dtandard design parameters to an upstream ARINC transmitter. It provides practical advice on how to implement ARINC into an FPGA and includes many lessons learned from real implementers, as well as component compatibility information.
Charter Flights And Wi-Fi: How To Stay On Top.
The Transient Nature of Digital Design. Safe But Not Secure: The Changing Landscape of Cybersecurity in Aviation.
Flying Secure in Today’s Aviation Environment. Receive the latest avionics news right to your inbox. More On This Topic.