Middleware

In aircraft industry, after labour and fuel costs, maintenance costs are the third largest expense item for both regional and national carriers. By implementing IVHM technologies not only the maintenance costs can be reduced, also it can provide more specific scheduled maintenance, on-board diagnostics and prognostics services. Maintenance department can be notified about the fault in advance and can arrange for components while aircraft is in mid-air. IVHM technologies minimize the physical diagnostics costs and provide more realistic condition based maintenance (CBM). The aim of this project is to investigate, using simulation and optimization, how IVHM network architecture can be built and implemented in aircraft (or IVHM applications), to support interoperability between multiple vendors’ IVHM components and insertion of new IVHM capabilities. IVHM consists of subsystems, sensors, model based reasoning systems for subsystem and system level managers, diagnostic and prognostics software for subsystems. In IVHM systems, usually there is large amount of data (collected from sensors), which needs to be delivered to right places at the right time so communication paradigm is the first and very essential design consideration which impacts many key properties such as scalability, reliability, availability, timeliness and configuration of overall system. The OSA-CBM (Open System Architecture for Condition Based Maintenance) defines an open architecture for moving information in a condition-based maintenance system. Typically, companies developing condition-based maintenance systems must develop software and hardware components, in addition a framework for these components to integrate. OSA-CBM is a standard architecture and framework for implementing condition-based maintenance systems. It not only describes the six functional blocks of condition based maintenance systems but also the interfaces to establish communication.

 

Organization:

Modeling the QoS parameters of DDS for event-driven real-time applications

The Data Distribution Service (DDS) standard defines a data-centric distribution middleware that supports the development of distributed real-time systems. To this end, the standard includes a wide set of configurable parameters to provide different degrees of Quality of Service (QoS). This paper presents an analysis of these QoS parameters when DDS is used to build reactive applications normally designed under an event-driven paradigm, and shows how to represent them using the real-time end-to-end flow model defined by the MARTE standard.

Publication Year: 
2015
Conference or Venue:

Automatic Vehicle Location and Monitoring System Based on Data Distribution Service

This paper proposes a real time Automatic Vehicle Location (AVL) and Monitoring system for pilgrims road transport coming towards city of Makkah in Saudi Arabia based on Data Distribution Service (DDS). This service is a real time publish/subscribe middleware. Using this middleware approach, we are able to locate and track a huge number of mobile vehicles and identify pilgrims for an annual Islamic gathering in the Holy City of Makkah. Performance results are demonstrated for LAN, WLAN and Bluetooth over DDS.

Publication Year: 
2014
Organization:

CRIAQ AVIO-509 project is a research project on the design of modular avionics architectures and integrated commonly called IMA (Integrated and Modular Avionics). The main purpose of this research project aims to explore the design methodologies IMA systems and evaluate the impact of architectural decisions. A platform for experimentation will be developed to enable prototyping IMA systems. An application of synthetic vision increased (ESVS) will be implemented on this demonstrator IMA. CMC Electronics Inc. and CAE companies. are partners in this project and the École Polytechnique de Montreal. The project has a duration of three years (2011-2014).

Within this project, we are analysing the benefits of using Connext DDS for communications between different nodes of an avionic system.

Author:

The main objective of PLANET project is the design, development and validation of an integrated platform to enable the deployment, operation and maintenance of large-scale/complex systems of heterogeneous networked Cooperating Objects, including Wireless Sensor and Actuator Networks and mobile objects. The platform supports optimal and adaptive deployment and operation by means of mobile cooperating objects, i.e. vehicles, networked with static nodes. The platform is validated in two complementary scenarios: the monitoring of the Doñana Biological Reserve with very high ecological value and very sensitive to the impact of pollution, and the highly automated airfield scenario in which security plays an important role and where wireless communication and cooperative techniques pose significant challenges.

PLANET addresses the design methodology and development of the platform as well as the algorithms required to support the deployment and maintenance of heterogeneous systems with mobile and static nodes. 

We use RTI DDS as the middleware for the communication between heterogeneous Cooperating Objects, such as UAVs, UGVs and ground sensor networks. Upon RTI DDS we build a set of PLANET services to ease the deployment, operation and maintenance of heterogeneous networked Cooperating Objects. 

For more information of the Project PLANET, you are welcome to visit the website: http://www.planet-ict.eu/

Author:

Designing High Performance Factory Automation Applications on Top of DDS

DDS is a recent specification aimed at providing high‐performance publisher/subscriber middleware solutions. Despite being a very powerful flexible technology, it may prove complex to use, especially for the inexperienced. This work provides some guidelines for connecting software components that represent a new generation of automation devices (such as PLCs, IPCs and robots) using Data Distribution Service (DDS) as a virtual software bus.

Publication Year: 
2013

The Robot Application Programming Interface Delegate (RAPID) is a set of software data structures and routines that simplify the process of communicating between multiple diverse robots and their command and control systems. RAPID is not intended to be an all-encompassing API for robot communication, but rather it’s a compatibility layer that permits tools and robotic assets to exchange data and information and allows operators to communicate with heterogeneous robots in a uniform way. RAPID is a compatibility layer that delegates information between robots that speak different languages.

The RAPID specification includes definitions and APIs for messages and services that support supervisory telerobotics operations over near-Earth time delay. RAPID is not a middleware specification, although safety and time-delay capabilities do imply requirements on implementing middleware systems. As currently implemented, the RAPID system can be considered a software reference implementation for remote operations.

For more information, contact David.S.Mittman@jpl.nasa.gov.

RAPID Logo

A QoS Policy Configuration Modeling Language for Publish/Subscribe Middleware Platforms

ABSTRACT: Publish/subscribe (pub/sub) middleware platforms for event- based distributed systems often provide many configurable policies that affect end-to-end quality of service (QoS). Although the flexibility and functionality of pub/sub middle- ware platforms has matured, configuring their QoS policies in semantically compatible ways has become more complex.

Publication Year: 
2007
Organization:
Conference or Venue:

Design and Performance of DDS-based Middleware for Real- Time Control Systems

Abstract: Data-centric design is emerging as a key tenet for building advanced data-critical distributed real-time and embedded systems. These systems must find the right data, know where to send it, and deliver it to the right place at the right time. Data Distribution Service (DDS) specifies an API designed for enabling real-time data distribution and is well suited for such complex distributed systems and QoS-enabled applications. It is also, widely known that Control Area Networks (CAN) are used in real-time, distributed and parallel processing.

Publication Year: 
2007
Organization:

Middleware solutions for automation applications - case RTPS

Abstract: This thesis has been written as a part of a research project, whose goal is to define the architecture and communication requirements of next-generation process automation systems. We focus on defining appropriate communication mechanisms for components that communicate with each other using Ethernet.

Author:
Publication Year: 
2005

Pages

Subscribe to RSS - Middleware