Presagis ARINC Development Suite is an integrated, end-to-end workflow environment for the entire lifecycle of ARINC systems development: from requirements specification, design, and development through deployment and maintenance. CDS developers can easily create or modify standard or custom widgets while developing a CDS and a widget library. UA developers can lay out and generate data definition files for the UA. The objective of the standard is to minimize both direct and indirect costs to the airlines by.
|Published (Last):||4 August 2016|
|PDF File Size:||4.81 Mb|
|ePub File Size:||11.28 Mb|
|Price:||Free* [*Free Regsitration Required]|
The task of creating aircraft cockpit displays has grown increasingly difficult over the past decade due to certifications rules DOB being applied more widely on military programs — along with the constant drive to deliver on shorter deadlines. To make things even more complicated, many players in the industry use their own development methodologies with little to no guidelines on content other than the instructions of their developers and human factors engineers.
This lack of a standards-based approach led to the proliferation of monolithic applications, either developed internally or through the use of commercial tools. These applications always need to be recertified as a whole, no matter which type of change is made. Exchanging data between commercial tools is also usually difficult, making it a challenge for aircraft manufacturers to think about switching providers for a system during the life cycle of an aircraft — or to reuse display elements between projects that are built using different software architectures.
This standard has been used in the military realm since its inception, with its most recent iteration published earlier this year.
While cockpit display software has traditionally been written as self-contained executables that present information and render graphics based on internal data, rules, and logic, ARINC introduces a clear separation between the code drawing the graphics and the code managing the logic and the position and state of all visual elements.
Furthermore, ARINC defines the CDS as a runtime interpreter capable of displaying one or more elements from a finite library of building blocks called widgets based on information contained in external layout files. Figure 1 shows the relation between the CDS and UA, along with their typical execution environments and the communications between these two applications. In that situation, each UA can be developed separately and is responsible for updating and reacting to events of a specific section of the display.
A direct benefit of this architecture is that updates to the display composition are done by creating new layout files instead of modifying code within a unified application. In a certified environment, this means that UA and CDS code does not need to be recompiled or recertified for visual layout changes such as repositioning or changing the visual attributes of display elements.
The same benefit applies to changes to the logic flow of the application, which will only result in changes to a specific user application, leaving the CDS code base and other user applications unaffected. Beyond isolation benefits, this approach also simplifies the distribution of application development between different teams within an organization or across subcontractors.
Each DF contains one or more layers, which are hierarchical listings of all widgets that need to be loaded along with their initial parameters such as position, size, and visibility. They are natively stored in a binary format that is loaded into the CDS application at runtime.
The standard also defines an XML interchange format to facilitate DF inspection, revision control, and sharing. Going down a level, the physical display attached to the CDS is divided into one or more subsections, simply called windows, which can each render one or more layers. These windows cannot have any overlaps and will stack the designated layers to create the final result that will be shown to the pilot or operator on-screen.
Figure 2: CDS visual hierarchy. In the latter case, an event is sent to the appropriate UA to determine a response based on the current system state and the event type. When it comes to certification, this detailed display architecture greatly simplifies the creation of high- and low-level requirements. This number went up to 50 with the first update to the standard, to 57 with supplement 2, to 65 in revision 3 and to 68 with its most recent incarnation published earlier this year.
Widgets vary in complexity from basic graphical elements such as the GpLine and GpRectangle widgets to complex objects such as the MapHorz widget, which displays maps from various data sources. There are also some widgets that do not have any visual representation that are used to group other elements together as well as apply transformations on them.
An example in this last category is the MutuallyExclusiveContainer widget that groups multiple elements under a single parent but only displays one of its immediate children at a time. While ARINC describes how widgets should function and what their parameters are, it does not define their visual appearance. This gives full liberty to the display manufacturers to implement their own look and feel for a given project. There is also a provision in the standard to allow developers to create custom widgets with tailored functionality and parameters that still follow general widget creation patterns.
Having a standard set of widgets to develop a display makes it easy for a developer to become familiar with the ARINC standard and to understand quickly how to develop new displays.
Also, similar to the overall ARINC architecture tying directly into high-level requirements, having a standard set of widgets with well-documented functionality helps accelerate the documentation of low-level detailed functional requirements for a certified project.
While the implementation of this architecture might seem a bit daunting — considering the need to put in place a compliant CDS runtime software architecture, a functional widget library that adheres to the specification, and tools to facilitate the creation of Definition Files and their output to standard binary files — it should be noted that COTS tools are available to provide these capabilities out of the box.
In some cases, these tools are even qualified development tools that can generate qualifiable code under DOB. After seeing a few large commercial aircrafts lead the way, many programs, both commercial and military, are considering or have already adopted ARINC for their upcoming projects, ensuring the success of this standard.
Yannick Lefebvre is a senior application developer at Presagis. With a background in computer sciences and 13 years of experience in modeling and simulation, Yannick has provided counsel on hundreds of simulation and embedded display programs globally and is considered an expert in the industry.
He can be reached at yannick. Yannick Lefebvre Presagis. The ARINC avionics display standard has been in existence and evolving for close to a decade — with its most recent iteration published earlier this year.
ARINC architecture overview While cockpit display software has traditionally been written as self-contained executables that present information and render graphics based on internal data, rules, and logic, ARINC introduces a clear separation between the code drawing the graphics and the code managing the logic and the position and state of all visual elements.
The future of ARINC While the implementation of this architecture might seem a bit daunting — considering the need to put in place a compliant CDS runtime software architecture, a functional widget library that adheres to the specification, and tools to facilitate the creation of Definition Files and their output to standard binary files — it should be noted that COTS tools are available to provide these capabilities out of the box.
Presagis www. Advertisement [ x ].
Mastering the ARINC 661 Standard
This project is maintained by Dassault Aviation. 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. See the architecture article for more information about the project architecture. See distribution if you want to know which files you need.
ANSYS SCADE Solutions for ARINC 661
The first version of the standard was adopted in The first supplement was adopted in , and added new widgets. The second supplement was adopted in June , and added supplementary widgets. Third supplement has been adopted in It should be released in 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. The widget library is similar to Widgets used in computing.
Understanding ARINC 661 and its benefits in a certified environment