The Automotive Reference Architecture demonstrates RTI's best practices and quick-starter projects for building automotive systems using RTI Connext Drive. This repository contains documentation and demo applications showcasing different capabilities and benefits of Connext in an automotive context. The goal is to provide a comprehensive guide to help developers leverage Connext for building robust, scalable, and interoperable automotive systems.
- Introduction
- Getting Started
- Cloning the Repository
- System Architecture
- DDS Topics and QoS
- Hands-On: Demos
- Additional References
RTI Connext Drive is a leading connectivity framework designed to facilitate real-time data distribution in distributed automotive systems. This project illustrates how Connext Drive can be used to build a robust Automotive Reference Architecture that ensures data interoperability, scalability, and reliability.
By following the examples and best practices outlined in this documentation, architects and developers can find inspiration to create automotive applications.
Here are some links that complement this repository:
- RTI Automotive Overview
- Capability Brief PDF: RTI Connext for Next Gen EE and Zonal Architecture
- Capability Brief PDF: RTI Connext for SDV
- Case+Code page on rti.com
RTI strongly recommends proceeding in the following order:
- Setup: Clone the repository.
- Run: Run the demos.
- Learn: Understand the architecture.
To clone the repository, run the following command to download both the repository and its submodule dependencies:
git clone --recurse-submodule https://github.com/<your-repo>/automotive-reference-architecture.gitThe Automotive Reference Architecture is designed to support various use cases within the zonal control and EE architecture, as well as the V2X use cases. This reference architecture ensures that data flows seamlessly from the zonal controllers to the cockpit and the mobile app, enabling real-time monitoring, decision-making, and reporting.
The RTI Automotive Reference Architecture consists of the following key components:
- In-vehicle applications for Window Control
- Cloud relay
- Mobile applications for Window Control (external device)
Please find a diagram of the Window Zonal Controller demo below:
- Purpose: Send control commands for a specific window with the target position.
- QoS: Reliable and volatile.
- Purpose: Provide updates on the current position of the windows.
- QoS: Best-effort and volatile.
RTI recommends following along the demo-specific READMEs before returning here and learning more about the designed system architecture.
This example demonstrates a local deployment of the automotive window control system. It includes two zonal controllers, one cockpit application, and one mobile app. It highlights the easy deployment and easy integration with multiple OS and subsystems.
The system consists of:
- Zonal Controllers: Directly control the position of two windows each.
- Cockpit/Dashboard: Provides a GUI for controlling and monitoring window positions.
- Mobile Application: Offers remote control of windows.
The communication is designed around RTI Connext, focusing on interfacing with the data in the system rather than the devices or applications.
For more details, see the Demo 1 README.
This example focuses on the V2X use case, highlighting the use of a single technology to communicate from the leave to the cloud. For that, it extends Demo 1 by introducing cloud-based communication that relies on the information to a remote component over WAN, which acts as an additional mobile app.
The system architecture remains similar to Demo 1 but includes:
- Routing Service: Deployed on an AWS EC2 instance to enable communication between Domain 0 and Domain 1 using RTI WAN Transport.
- Dockerized Routing Service: The Routing Service is packaged as a Docker image for easy deployment.
- AWS Integration: Terraform scripts are provided to set up the necessary AWS infrastructure.
For more details, see the Demo 2 README.