Eclipse Software Defined Vehicle

The Eclipse Software Defined Vehicle (SDV) Working Group provides a forum for individuals and organizations to build and promote open source software, specifications, and open collaboration models needed to create a scalable, modular, extensible, industry-ready open source licensed vehicle software platform to support in-vehicle and around the vehicle applications development and deployment.

Working Group ID
sdv
Status
Active
Eclipse Leda Incubator logo.

Eclipse Leda Incubator

Eclipse Leda Incubator provides a place for experimental components from the software-defined vehicle ecosystem.

Eclipse Ambient Light Services

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.
Project
Eclipse Ambient Light Services
Parent Project
Eclipse Automotive
Working Group
Eclipse Software Defined Vehicle
Proposal State
Created
Background

Project was initially generated in order to gain know-how when it comes to the definition of Autosar-Standards with the goal to create a functional show-case.

Scope

Eclipse Ambient Light Services provide an expandable SW core-stack implementing Autosar interfaces and allowing to visualize specific ambient light service. This project can be extended with additional functions, like e.g. Apps or other additional functions/ alternatives. Also it is intended that the developer has the option to e.g. vizualize quickly different options and or combinations.  

Description

The Eclipse Ambient Light Services showcase vizualizes possible new lighting concepts which are adaptive to different specific driving scenarios, like e.g. coming and leaving but also further options are possible. It was developed as an AUTOSAR SW component in order to be easiliy transferable to other different vehicle platforms based on AUTOSAR classic. It plays light animation scenes for welcoming and leaving scenarios of the driver. It uses a dataset which contains different animation scenarios. The described scenarios are expandeble through our developed easy data set creation scenario modifier. 

Why Here?

This type of SW-stack is unique in terms of control of light functions. This is the bridge to the SDV. The existing 7 projects of Eclipse SDV may be subdivided in 3 groups: middleware projects, SW-development surfaces und pedagogical/distribution activities. Eclipse Ambient light services would provide a 4th pillar of Eclipse SDV namely an application software stack dealing with an illumination functions of a car. We do expect that future interested members will contribute new application ideas for the illuminating automotive elements. Furthermore we expect the SW-structure of Eclipse Ambient Light Services to be transferred to other existing automotive elements using them in completely new ways.

Licenses
Apache License, Version 2.0
Legal Issues

no legal issues

Project Scheduling

The currently available source code shall be made accessible in the 4th quarter of 2022. The first build may be expected during 1st quarter of 2023.

Future Work

We do expect that future interested members will contribute new application ideas for the illuminating automotive elements. Furthermore we expect the SW-structure of Eclipse Ambient Light Services to be transferred to other existing automotive elements using them in completely new ways. 

People
Project Leads
Jesus Galan
Benjamin Weidenfeld
Committers
Edgar Hindemith
Johannes Eulitz
Benjamin Weidenfeld
Jesus Galan
Benjamin Weidenfeld
Mentors
Wayne Beaton
Interested Parties

OEMs

Source Code
Initial Contribution

To be defined

Source Repository Type
GitHub
Source Repositories
https://github.com/telekom

Eclipse Ibeji

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.
Project
Eclipse Ibeji
Parent Project
Eclipse Automotive
Working Group
Eclipse Software Defined Vehicle
Proposal State
Created
Scope

Eclipse Ibeji provides a prototype that demonstrates and encourages community collaboration in defining what a in-vehicle digital twin should look like and support multiple technical implementations:

  • A sample vehicle represented in Digital Twins Definition Language (DTDL)
  • Rust based code implementation showing how to ingest a sample vehicle DTDL into the in-vehicle digital twin, an in-vehicle digital twin in-memory object model and methods to obtain signals from the in-vehicle digital twin.  
Description

The automotive and mobility ecosystem is facing major challenges in modernizing and streamlining in-vehicle software development as well as in software life cycle management. The Eclipse Ibeji project provides the capability to express a digital representation of vehicle state and its capabilities through an extensible and dynamic architecture to model and access the vehicle hardware, sensors and capabilities. The models for in-vehicle digital twin are defined using Digital Twins Definition Language (DTDL), a programming-language independent based on JSON-LD. This capability when combined with modern application programming models like the proposed by Eclipse Chariott project can bootstrap, simplify and enhance  automotive OEM software developers towards programming next-gen software-defined in-vehicle applications.

Licenses
The MIT License (MIT)
People
Project Leads
Filipe Prezado
Sean Selitrennikoff
Committers
Filipe Prezado
Sean Selitrennikoff
Ash Beitz
Mentors
Michael Scharf
Source Code
Initial Contribution

This initial community contribution aims to provide a prototype that demonstrates and encourages community collaboration in defining what a in-vehicle digital twin should look like and support multiple technical implementations:

  • A sample vehicle represented in Digital Twins Definition Language (DTDL)
  • Rust based code implementation showing how to ingest a sample vehicle DTDL into the in-vehicle digital twin, an in-vehicle digital twin in-memory object model and methods to obtain signals from the in-vehicle digital twin.  
Source Repository Type
GitHub
Eclipse Backend function Bindings (BfB) logo.

Eclipse Backend function Bindings (BfB)

  • Archived

The Eclipse BfB project provides a protocol and technology agnostic interface specification in the ecosystem of mobility and automotive applications. The Eclipse BfB specification is maintained in a

Eclipse ArchE

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.
Project
Eclipse ArchE
Parent Project
Eclipse Automotive
Working Group
Eclipse Software Defined Vehicle
Proposal State
Created
Background

The current state of practice in the field of Architecture Modeling Tools in the automotive domain is using chains of heterogeneous tools which are only loosely integrated with each other. As a consequence, these various Tools lead to a huge accidental complexity due to redundancy of information, inconsistencies between the redundant content captured in the tools, lack of automation. The development effort is increased, silos of information are formed around the tools and this leads to lack of transparency and communication, developers waste precious brain cycles in searching for information or keeping information consistent instead of doing engineering work. Furthermore its highly complex to perform Change Impact Analysis across the borders of tools, as well as Safety or Security analysis over the entire architecture stack.

From a CARIAD perspective the motivation to contribute with the 'ArchE' (Architecture Engineering) Project is to work towards industry standards in the field of Architecture Modeling and benefiting from the market momentum, by providing one single tool, that combines the functionalities of the various tools that are currently be used instead.

Scope

Eclipse ArchE provides a tool for Architecture Modeling following a Model-Based-Systems-Engineering (MBSE) approach.

In Scope:

  • Holistic Architecture Modeling including linkage to
    • resource estimation,
    • timing,
    • safety,
    • security
  • Generation of ARXMLs

Out of Scope

  • Requirements Management
  • Actual development of the software of the software components
Description

Eclipse ArchE provides a tool for Architecture Modeling following a Model-Based-Systems-Engineering (MBSE) approach.

Instead of having a heterogeneous environment of various tools to break High-Level Stakeholder Requirements all the way down to modeled software components that shall run in the car.

In that sense ArchE is:

  • Single Source of Truth for architecture
  • supporting all architecture activities and related processes
  • tightly integrating special engineering disciplines like resource estimation, timing, safety, security in your architecture process
  • tightly integrating into software development lifecycle
  • enabling Diff/Branch/Merge, testing/integration, ...
Why Here?

With the rapidly increasing complexity due to Autonomous Driving Level 3, 4 & 5 coming up, the former approach of Systems Engineering based on multiple tools for various tasks and various suppliers is not feasible anymore. By creating standards on how to model architecture in a single Model the community enables the automotive industry to build more advanced and safe vehicles.

From sharing this project with the community we are hoping to jointly shape the future of architecture modeling in the field of SDV.

Licenses
Eclipse Public License 2.0
Project Scheduling

First Contribution including current release is planned for Autumn 2022. There is new releases coming on a monthly basis.

Future Work
  • Incorporate functionality from the currently used Tooling in order to be able to fully integrate them in a single tool -> ArchE
  • Ensure consistency across different domains
  • Functionality for creating of Classic Autosar ARXML as well as Adaptive Autosar ARXML
  • Ability to further customize and extend based on user needs
  • Incorporation Testing and simulation functionality
Description

Eclipse ArchE provides a tool for Architecture Modeling following a Model-Based-Systems-Engineering (MBSE) approach.

Instead of having a heterogeneous environment of various tools to break High-Level Stakeholder Requirements all the way down to modeled software components that shall run in the car.

In that sense ArchE is:

  • Single Source of Truth for architecture
  • supporting all architecture activities and related processes
  • tightly integrating special engineering disciplines like resource estimation, timing, safety, security in your architecture process
  • tightly integrating into software development lifecycle
  • enabling Diff/Branch/Merge, testing/integration, ...
People
Project Leads
Andreas Looft
Felix Reimann
Committers
Andreas Looft
Daniel Ratiu
Michael Langhammer
Manuel Huber
Felix Reimann
Mentors
Eike Stepper
Source Code
Initial Contribution

The ArchE Tool is currently in the rollout phase to product teams within CARIAD, meaning it is in a mature enough development state, so that teams can start modeling their SWC in the tool. Besides Architecture Modeling, one can also perform related tasks like Security evaluation and HARA.

A Feature Improvement Timeline is available.

List of Third-party libraries to be added according to the Blackduck Scan

 

Source Repository Type
GitHub
Eclipse SommR logo.

Eclipse SommR

Eclipse SommR provides an automotive grade implementation of the SomeIP specification for embedded Linux systems together with the required tools to support developers. Eclipse SommR fosters

Eclipse Muto logo.

Eclipse Muto

Eclipse Muto provides an adaptive framework and a runtime platform for dynamically composable model-driven ROS software stacks. Eclipse Muto can be used to introspect, monitor and manipulate the actively running ROS graph (the network of ROS nodes).

Eclipse ADAAA (Adaptive Cruise Control Demo Application for Adaptive AUTOSAR) logo.

Eclipse ADAAA (Adaptive Cruise Control Demo Application for Adaptive AUTOSAR)

ADAAA is example application for Adaptive AUTOSAR with the following goals: * Provide a tutorial with simple examples code base for getting involved with AUTOSAR methodology and each functional

Eclipse Chariott logo.

Eclipse Chariott

The Eclipse Chariott project aims to simplify and enhance in-vehicle software developer productivity by providing a metadata-driven middleware/abstraction layer that allows modern application

Eclipse eCAL (enhanced Communication Abstraction Layer) logo.

Eclipse eCAL (enhanced Communication Abstraction Layer)

Eclipse eCAL™ (enhanced Communication Abstraction Layer) provides a middleware that enables scalable, high performance interprocess communication on a single computer node or between different nodes

Subscribe to Eclipse Software Defined Vehicle