ARINC 661

From Wikipedia, the free encyclopedia

ARINC 661 is a standard which aims to normalize the definition of a Cockpit Display System (CDS), and the communication between the CDS and User Applications (UA). The GUI definition is completely defined in binary definition files (DF) - except the Look and feel, such as the CDS software is constituted of a kernel which is able to create the GUI hierarchy specified in the DF during initialisation, thus not needing to be recompiled if the GUI definition changes (apart from the Look and feel).

Contents

[edit] History and Adoption In Industry

The first version of the standard was adopted in 2001. Its first use was for Airbus A380 CDS development. The first supplement was adopted in 2003, and added new widgets. The second supplement was adopted in June 2005, and added supplementary widgets.

The standard is known today to be used for Airbus A380 and A400M CDS development, and also Boeing 787 CDS development. It has also been said that AgustaWestland company will use ARINC 661 for its future helicopters' CDS.

[edit] Technical Overview

The standard normalizes :

  • the GUI definition of the CDS interface, in a binary file called DF (Definition File) defining the structure of the graphical interface tree. The GUI tree is instantiated at initialization time (called the Definition Phase in the standard) in the CDS, using the definition contained in the DF.
  • the communication at runtime between the User Applications (UA) and the CDS. This communication protocol is typically used for UAs to send widgets modifications to the CDS, and return user events (such as buttons selection) from CDS to UA.

In order to be compliant with the standard, a CDS must have a kernel that can create the Widgets tree during CDS initialization, using the Definition File, and communicate with UA in both ways using the runtime protocol.

ARINC 661 does not imply the use of a particular Data bus structure to perform the low-level communication between CDS and UA. For example, an ARINC 429 or ethernet protocol can be used, by it is not mandatory.

[edit] GUI Definition

Each DF binary file specify the GUI definition for one User Application (UA) User interface. Several UA user interface trees can be combined to constitute the CDS display definition.

A DF is composed of two parts : an optional symbol definition, and a widgets definition. The widget library is similar to Widgets used in computing. There are Containers, Lists, ScrollPanes, Buttons, Menus, Labels, EditBoxes, etc...

Although the DF File is binary, the standard has also defined an associated XML definition, which is easier to manipulate in tools.

[edit] Relationship with other UI languages

The concepts used by ARINC 661 are close to those used in User interface markup languages, except that the UI language is binary and not XML based[1].

Main similarities from other User interface markup languages :

  • The interface definition is not hard-coded in the CDS. Instead, the CDS use a kernel which instantiate the widget tree at initialization, using a predefined widget library
  • The widget list and the structure of the widget tree are similar to what can be found in common Widget toolkits
  • The Look and feel is separated from the definition of the interface

Main differences from other User interface markup languages :

  • The widget library defined in the standard does not really take advantage of its object nature, contrary to other User interface markup languages. For example, there is no notion of inheritance in the standard, although the same properties can be used more than once for several widgets.
  • Some Widget toolkits or User interface markup languages have the ability to layout widgets automatically in a container (see for example the box model in XUL, or the layouts in Java Swing). Widgets position and size in their container must always be defined exactly in an ARINC 661 definition. However, the next version of the standard will add some sort of "relative" layout capability between widgets (see Layout manager).
  • There is no equivalent of XBL, like what is used in XUL or SVG. There are symbols that can be reused, but they are mainly shapes that cannot have behaviors (apart from defining their position, rotation, and color), or specific bindings.
  • There is no equivalent of Cascading Style Sheets, as they are used in XUL or SVG for example. Instead, the Look and feel of the interface is hard-coded in the ARINC 661 kernel.
  • The standard does not have an equivalent of Javascript, as used in SVG and XUL, so all specific behavior associated with the widgets must be performed by the UAs.
  • The standard has defined specific "Map" widgets which allows to present elements such as Flight plans in CDS.

[edit] Development and Tools support

ARINC 661 GUI development includes tools for the specification of definition files and the kernel that use these files :

  • Thanks to ARINC 661 concepts, the specification tools have no dependency on the execution platform,
  • The kernel itself depends on the execution platform.

As of late 2006, There are currently two COTS specification tools for DF specification, but there are no embedded real-time COTS kernels for the moment. It must also be noted that because of the burden of Avionics software certification, the kernel must be embedded in a DO-178B-compliant environment.

[edit] References

  1. ^ The standard also specifies a XML format for the UI language, but it is mainly used to ease DF production by specification tools. The kernel is initialized with the binary version of DFs

[edit] See also

[edit] External links

Retrieved from "http://en.wikipedia.org../../../a/r/i/ARINC_661_cf67.html"