Search Results

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.

The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

ARINC 814 defines an XML encoding and compression standard for aviation. It is based on the Open Geospatial Consortium (OGC) Binary XML document. Binary XML encoding is extended in a way that is both flexible and robust. Compression is added on top of the binary encoding. ARINC 814 is expected to be used with Aeronautical Databases, in particular, ARINC Specification 813: Embedded Interchange Format for Terrain Databases, ARINC Specification 815: Embedded Interchange Format for Obstacle Databases, and ARINC Specification 816: Embedded Interchange Format for Airport Mapping Database.

"Spotlight on Design" features video interviews and case study segments, focusing on the latest technology breakthroughs. Viewers are virtually taken to labs and research centers to learn how design engineers are enhancing product performance/reliability, reducing cost, improving quality, safety or environmental impact, and achieving regulatory compliance. Fuel efficiency, or simply put, how to get more mileage out of the same amount of fuel has become one of the main goals to be achieved by new automotive technologies in the future, thanks in part to new government regulations. In the episode "Fuel Efficiency: Racing toward CAFE 2025" (21:24) AVL engineers show simulation and testing being used to design more fuel efficient vehicles, including the equipment that actually analyzes fuel economy.

"Spotlight on Design: Insight" features an in-depth look at the latest technology breakthroughs impacting mobility. Viewers are virtually taken to labs and research centers to learn how design engineers are enhancing product performance/reliability, reducing cost, improving quality, safety or environmental impact, and achieving regulatory compliance. As global concerns about the negative consequences of greenhouse gases on the environment increase, regulatory agencies around the world are taking serious steps to address the issue of tailpipe emissions In the episode "Fuel Efficiency: Fuel Economy Testing" (12:01), engineers at the EPA’s National Vehicle and Fuel Emissions Laboratory demonstrate how different vehicles are tested for emissions, and AVL’s technical team shows how accurate tailpipe emissions can be measured and reported.

Given the fast changing market demands, the growing complexity of features, the shorter time to market, and the design/development constraints, the need for efficient and effective verification and validation methods are becoming critical for vehicle manufacturers and suppliers. One such example is fault-tree analysis. While fault-tree analysis is an important hazard analysis/verification activity, the current process of translating design details (e.g., system level and software level) is manual. Current experience indicates that fault tree analysis involves both creative deductive thinking and more mechanical steps, which typically involve instantiating gates and events in fault trees following fixed patterns. Specifically for software fault tree analysis, a number of the development steps typically involve instantiating fixed patterns of gates and events based upon the structure of the code. In this work, we investigate a methodology to translate software programs to fault trees.

Rapid control prototyping (RCP) is a widely used technique for verifying a controller's functional behavior. Typically, RCP uses a target processor with ample processing power and memory, which makes the technique attractive for engineers exploring new concepts. Presenter Thomas Erkkinen, MathWorks Inc.

Software content within commercial vehicles is growing exponentially. Emissions requirements, multiplexed communications, hybrid-electric technologies, active suspensions and smart sensors are amongst the technologies driving the increase in embedded code. Presenter Christoph Braeuchle , MKS Software, Inc.

The amount of software, computation and logic embedded into the vehicle systems is increasing. Testing of complex real time embedded systems using Hardware in Loop (HIL) simulations across different vehicle platforms has been a challenge. Data driven testing enables a qualitative approach to test these complex vehicle systems. It consists of a test framework wherein the test logic and data are independent of the HIL test environment. The data comprises variables used for both input values and output verification values. This data is maintained in a database or in the form of tables. Each row defines an independent test scenario. The entire test data is divided into three categories, High, Medium and Low. This feature gives the advantage of leveraging the same set of test data from Unit Level Testing phases to the Integration Test phase in the V-Cycle of software development. A data driven test approach helps the reuse of tests across vehicle platforms.

These advanced checks have resulted in development of many new diagnostic monitors, of varying types, and a whole new internal software infrastructure to handle tracking, reporting, and self-verification of OBD related items. Due to this amplified complexity and the consequences surrounding a shortfall in meeting regulatory requirements, efficient and thorough validation of the OBD system in the powertrain control software is critical. Hardware-in-the-Loop (HIL) simulation provides the environment in which the needed efficiency and thoroughness for validating the OBD system can be achieved. A HIL simulation environment consisting of engine, aftertreatment, and basic vehicle models can be employed, providing the ability for software developers, calibration engineers, OBD experts, and test engineers to examine and validate both facets of OBD software: diagnostic monitors and diagnostic infrastructure (i.e., fault memory management).

Edgewater Computer Systems Inc. product RTEdge Platform 1.2 is a software toolset supporting proof based engineering, implementation and deployment of software components, built using the RTEdge AADL Microkernel modeling subset. This is a small subset of the AADL component model and execution semantics, covering threads and thread-groups communicating solely through asynchronous event ports and through explicitly shared data ports. Threads behavior is expressed as state machines and dispatch run time semantics is encoded in a Run-time Executive, enforcing pre-emptive priority dispatch based on statically assigned event priorities, with ceiling priority protocol access to shared data. This simple AADL microkernel semantic core can support all dispatch policies, communication and synchronization mechanisms of a fully fledged AADL run time environment, permitting the systematic use of the RTEdge static analysis tools for AADL compliant software components.

The use of Engine Health Management (EHM) systems has been growing steadily in both the civilian and the military aerospace sectors. Barring a few notable exceptions (such as certain temperature and thrust margin monitoring) regulatory authorities around the world have not required these systems to be certified in any way. This is changing rapidly. New airframes and engines are increasingly being designed with the assumption that EHM will be an integral part of the way customers will operate these assets. This leads to a need for better guidelines on how such systems should be certified. The SAE E-32 committee on Propulsion System Health Monitoring is leading an industry-wide effort to develop a set of guidelines for certifying EHM systems.

This presentation shows the SCADE System product line for systems modeling and generation based on the SysML standard and the Eclipse Papyrus open source technology. SCADE System has been developed in the framework of Listerel, a joint laboratory of Esterel Technologies, provider of the SCADE�, and CEA LIST, project leader of the Eclipse component, Papyrus. From an architecture point of view, the Esterel SCADE tools are built on top of the SCADE platform which includes both SCADE Suite�, a model-based development environment dedicated to critical software, and SCADE System enabling model-based system engineering. SCADE System includes Papyrus, an open source component (under EPL license), integrated in the modeling platform of Eclipse. Using this integrated modeling platform, both system and software teams share the same environment for system development. Furthermore, other model-based tools can be added to the environment, due to the use of Eclipse.

Cyber security in the aviation industry, especially in relation to onboard aircraft systems, presents unique challenges in its implementation and management. The cyber threat model is constantly evolving and will continually present new and different challenges to the aircraft operator in responding to new cyber threats without either invoking a lengthy software update and re-certification process or limiting aircraft-to-ground communications to the threatened system or systems. This presentation discusses a number of system architectural options and developing technologies that could be considered to enhance the aircraft cyber protection and defensive capabilities of onboard systems as well as to minimize the effort associated with certification/re-certification. Some of these limit the aircraft?s vulnerabilities or in cyber terms, its ?threat surface?.

Many manufacturing companies want to apply AFP technology to complex high-curvature part shapes. As new AFP machine technologies are developed to specifically apply material over complex shapes, new and innovative NC programming approaches are needed to successfully, reliably, and accurately apply material with good consolidation, while meeting the fiber direction and coverage requirements. A big issue with AFP is the production rate vs. part complexity. Most complex shapes can be created with a single .125? wide strip (tow) of material. But the production time would be impractically long. So machine builders create 6, 8, 16, even 32 tow AFP heads, and use the widest tow possible for the highest laydown rates. But then wide compaction rollers on these systems have difficulty consolidating material over curved surfaces, and the minimum steering radius of wider tows challenge the software?s ability to meet the layup requirements.

In recent years, all major microprocessor manufacturers are transitioning towards the deploymenet of multiple processing cores on every chip. These multi-core architectures represent the industry consensus regarding the most effective utilization of available silicon resources to satisfy growing demands for processing and memory capacities. Porting off-the-shelf software capabilities to multi-core architectures often requires significant changes to data structures and algorithms. When developing new software capabilities specifically for deployment on SMP architectures, software engineers are required to address specific multi-core programming issues, and in the ideal, must do so in ways that are generic to many different multi-core target platforms. This talk provides an overview of the special considerations that must be addressed by software engineers targeting multi-core platforms and describes how the Java language facilitates solutions to these special challenges.

This paper presents an extension of our earlier work on Cummins Vehicle Mission Simulation (VMS) software. Previously, we presented VMS as a Windows based analysis tool to simulate vehicle missions quickly and to gauge, communicate, and improve the value proposition of Cummins engines to customers. Presenter Nagesh Belludi, Cummins Inc.