Skip to main content
  • Log in
  • Manage Cookies
projects.eclipse.org
Download
  • Projects
  • Working Groups
  • Members
  • Community
    • Marketplace
    • Events
    • Planet Eclipse
    • Newsletter
    • Videos
    • Blogs
  • Participate
    • Report a Bug
    • Forums
    • Mailing Lists
    • Wiki
    • IRC
    • Research
  • Eclipse IDE
    • Download
    • Learn More
    • Documentation
    • Getting Started / Support
    • How to Contribute
    • IDE and Tools
    • Newcomer Forum
  • More
      • Community

      • Marketplace
      • Events
      • Planet Eclipse
      • Newsletter
      • Videos
      • Blogs
      • Participate

      • Report a Bug
      • Forums
      • Mailing Lists
      • Wiki
      • IRC
      • Research
      • Eclipse IDE

      • Download
      • Learn More
      • Documentation
      • Getting Started / Support
      • How to Contribute
      • IDE and Tools
      • Newcomer Forum
    • Search

  1. Home
  2. Projects
  3. Eclipse Automotive
  4. Eclipse Chariott
  5. Eclipse Chariott
×

Informative message

This proposal has been approved and the Eclipse Chariott project has been created.
Visit the project page for the latest information and development.

Go to Project

Eclipse Chariott

Basics
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project: 
Eclipse Automotive
Background: 

The Eclipse Chariott project provides:

Middleware: Centralized middleware layer to connect to different providers in the vehicle, as well as host the vehicle twin store, Access Control List (ACL), and other middleware services. Abstracts the vehicle specific providers implementation through a common and agnostic set of vehicle interfaces between providers and the applications that need to consume the data.

Application: The business logic component talking through the client/provider library to receive events and execute lower-level functions. Applications are envisioned as providing a specific set of Quality Management (QM) level functionality in the vehicle, for example, seat adjustment or interior climate control.  Applications describe their ACLs and their capabilities that other applications can consume. 

Providers: The vehicle has different lower-level protocols it uses to communicate with the different Electronic Control Units (ECUs) in the vehicle (e.g. SOME/IP, DDS, UDS, etc.). These providers connect the exposed services and state from the ECUs to the middleware and eventually the application. Providers are intended to be created by the suppliers, except for a reference provider that is generated for the purpose of testing and development.

Scope: 

The Eclipse Chariott project aims to develop a metadata-driven middleware/abstraction layer that allows modern programming models to target in-vehicle functions, providing a common way to access the vehicle hardware and sensors, while enhancing the developer journey.

Description: 

The Eclipse Chariott project aims to develop a metadata-driven middleware/abstraction layer that allows modern programming models to target in-vehicle functions, providing a common way to access the vehicle hardware and sensors, while enhancing the developer journey.

Automotive original equipment manufacturers (OEMs), partners and software providers require a consistent and well-architected experience that allows them to continuously develop and deploy new software capabilities, new features, new services and new applications to vehicles without having to re-architect and reducing or eliminating system integration effort.  The metadata-driven middleware/abstraction model is thus a key building block to provide a common way to access the vehicle hardware and sensors that eventually will be adopted by automotive customers and partners to enhanced developer journey. At core, the programming model should provide a service interface that 3rd party software providers can rely upon to access services and features of the vehicle.

 

Licenses: 
The MIT License (MIT)
People
Project Leads: 
Filipe Prezado
Roel Fauconnier
Sean Selitrennikoff
Committers: 
Filipe Prezado
Roel Fauconnier
Sean Selitrennikoff
Patrick Schuler
Atif Aziz
Mentors: 
Jay Billings
Source Code
Initial Contribution: 

The plan for the initial contribution, here described as Community Technical Preview (CTP), is to deliver a working proof of concept of the middleware/abstraction layer, written in Rust, that can send instructions to and receive state from a reference implementation that simulates a vehicle resource provider.
•    Client/Provider Library to communicate with the middleware through an abstract interface  
•    Middleware to route function calls and provide an event system over registered provider
•    Provider service API to extend/add vehicle provided services and data
•    In memory vehicle store with point reads on the keys.
 

Source Repository Type: 
GitHub
  • Sign in to post comments.
Incubating - Eclipse Chariott

Related Projects

Related Projects:

  • Eclipse Automotive
    • Eclipse Ibeji

Project Hierarchy:

  • Eclipse Automotive
  • Eclipse Chariott

Tags

Technology Types
  • Automotive
Other Tags
  • automotive

Eclipse Foundation

  • About Us
  • Contact Us
  • Sponsor
  • Members
  • Governance
  • Code of Conduct
  • Logo and Artwork
  • Board of Directors
  • Careers

Legal

  • Privacy Policy
  • Terms of Use
  • Copyright Agent
  • Eclipse Public License
  • Legal Resources

Useful Links

  • Report a Bug
  • Documentation
  • How to Contribute
  • Mailing Lists
  • Forums
  • Marketplace

Other

  • IDE and Tools
  • Projects
  • Working Groups
  • Research@Eclipse
  • Report a Vulnerability
  • Service Status

Copyright © Eclipse Foundation. All Rights Reserved.

Back to the top