Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
OpenADx
The OpenADx Working Group wants to serve in the field of software tools for the realization of autonomous driving (AD) by defining open interfacing standards for software for use in vehicle based systems and in testing environments, where the second will typically be realized by means of cloud services doing at least software builds, virtual test runs and collecting results. The name OpenADx thus stands for "Open, Autonomous Driving Accelerator". The group is formed by a multitude of parties from various parts of the world and supported by several well-known industry companies. The OpenADx Working Group is set up as a working group under the governance of the Eclipse Foundation.
Please find the home page and the news ticker of the OpenADx Working Group here (https://openadx.eclipse.org).
Contents
Welcome to OpenADx
Automated Driving (AD) is clustered into three equally important technology areas:
1) In-vehicle technology
2) Cloud technology (backend)
3) Design, development, test and validation tools (tool chain)
OpenADx is focused on the AD tool chain. The goal is to accelerate AD development through open collaboration and open source.
OpenADx' vision is to ensure transparency and make the complex AD tool landscape more easily accessible for enterprise users.
Watch the video on OpenADx here on YouTube: https://youtu.be/7gHLkSzWNKA
Pitch Deck
Pitch deck to be used inside of respective organizations File:OpenADxInformationDeck.zip
News
Please have a look to our latest news on our official OpenADx web site
Members
Have a look also to the OpenADx website.
Company | Role |
---|---|
ADLINK Technology | Driver Member |
Arm | User Member |
AVL List GmbH | Driver Member |
DENSO Corporation | User Member |
EclipseSource | User Member |
eteration A.S. | Development Member |
itemis AG | Development Member |
JC Information Management GmbH | Driver Member |
Microsoft | User Member |
Open Robotics | Guest Member |
Robert Bosch GmbH | Driver Member |
Science+ Computing AG | Development Member |
Siemens AG | Driver Member |
The Autoware Foundation | Guest Member |
University of Applied Science and Arts Dortmund | Guest Member |
Steering Committee 2022
Company | Name | Role |
---|---|---|
ADLINK Technology | Joe Speed | Driver Member |
AVL List GmbH | Josko Balic | Driver Member |
JC Information Management GmbH | Michael Hahn | Driver Member |
Robert Bosch GmbH | Andreas Riexinger (SC Chair) | Driver Member |
Siemens AG | Robin van der Made | Driver Member |
eteration A.S. | Naci Dai | Development Member |
itemis | Andreas Graf | Development Member |
Microsoft | Robert Nahm | User Member |
Steering Committee Meeting Minutes
Link to the Meeting Minutes
Related Projects and Project Proposals
Please find the overview about OpenADx hosted projects here.
OpenADx Toolchain Proposal
I started to fill the OpenADx blueprint with life and I would like to improve this proposal together with you, to get further examples / solutions and insights in the proposal. Please check what is missing. Appreciate your feedback!
Awesome Robotic Tooling
Just a bunch of powerful robotic resources and tools for professional robotic development with ROS in C++ and Python.
A bit more related to Robotics, but there are some tools, which are also used in AD development.
GitHub repository: Awesome Robotic Tooling
eCAL - enhanced communication layer
"The enhanced communication abstraction layer (eCAL) is a middleware that enables scalable, high performance interprocess communication on a single computer node or between different nodes in a computer network. The design is inspired by known Data Distribution Service for Real-Time Systems (see Data distribution service on wikipedia). The current eCAL implementation realizes a subset of such a DDS system, there is only a basic support for Quality of Service (QoS) driven data transport (best effort and reliable).
eCAL is designed for typical cloud computing scenarios where different processes exchange their I/O's using a publisher/subscriber pattern. The data exchange is based on so called topics. A topic wraps the payload that should be exchanged with additional informations like a unique name, a type and a description. A topic can be connected to more than one publisher and/or subscriber. These are the basic elements of the eCAL API."
eCAL uses Eclipse iceoryx. ;-)
GitHub repository: eCAL
openGADES - currently in proposal edit phase
openGADES is a customizable, lightweight toolchain for systems and software engineering. It can support you in fulfilling process requirements such as arising from ASPICE and ISO26262. openGADES stands for:
- open
- Generic
- Ascii-based
- Documentation and
- Engineering
- System
Find more information here.
Challenge
AD is a complex challenge and therefore requires a multifaceted development process incorporating a variety of software tools. The tools the industry currently uses are very good, but they don’t seamlessly work with one another. This is a result of the tools not being designed to work together. This is an industry-wide issue that slows us down in the race to AD development. By pooling resources, we can remove the “friction” between widely used tools. We can create something of use to all of us: open, compatible and accessible.
Problem and benefits for OEMs and Tier1s
User insight: "Developing automated driving functions is extremely complicated and requires the use of many complex software tools which do not work efficiently with one another. What I need is a set of tools which work with each other seamlessly so that my teams can move through the development process more quickly and efficiently."
Benefit: The automated driving tool chain allows your team to work together more efficiently with a suite of highly integrated tools by enabling seamless transfer of data and code through each step of the automated driving development process.
Problem and benefits for tool and technology providers
User insight: "Currently, tools used to create automated driving applications do not work efficiently with one another. If our tool/technology is compatible with other widely used technologies and tools, it will ease the development process for our customers and make our products even more attractive to them."
Benefit: The seamless integration of your technology in the automated driving tool chain makes it more attractive to organizations developing automated driving applications by increasing their development efficiency.
Integrated tool chain for AD system development
Leveraging the current tool landscape and tying in players from industry and academia is a must. Therefore, our approach is two-fold. First, we will fine-tune the development tool chain to the needs of our industry. We do this by integrating existing products in the market, adjusting existing tools to our needs, and developing additional tools through Open Source Software (OSS) where none today currently exist. Second, we will bring areas of expertise together in order to make the complex AD tool landscape more easily accessible for all stakeholders.
Approach
We believe an initiative like this should be inclusive, not exclusive. It’s about removing barriers to efficient development with widely established tools. It’s about bundling industry competencies and sharing development. We plan to demonstrate our ability to work together on joint testbeds in an open source setting. This allows potential partners to engage with a limited initial investment. The testbeds produce demonstrable results and strengthen confidence in the approach.
The Idea of Testbeds
Testbeds are setup to produce demonstrable results that incubate potential open source projects. To realize a testbed the idea is to prepare a use case/topic in a series of workshops and to execute so called Hack-Fests which assemble developers from the cooperation partners for a defined period of time, e.g. 3-4 days, in which they realize a demonstrator or prototype.
To identify testbed candidates, everybody is invited to propose ideas here to build a starting point for development of the idea towards the requirements for the execution of a Hack-Fest and for winning further interested parties.
To execute a Hack-Fest, we have identified these minimum requirements to make this a fruitful event:
- A minimum of two partners collaborating on the testbed, be it companies, universities or research organizations
- A minimum of 5 committed participants
Workflow for testbed candidates
- Verbalization of a task in use case form, which has potential for further work
- Contribution of the use cases by interested partners as testbed candidates
- Preparation of the testbed candidates in one or a series of workshops to a state that is sufficient for the participants of a HackFest to produce results
- Execution of the Hack-Fest
- Evaluation of the Hack-Fest results to decide on whether to follow the idea or to stop the effort
- Reworking the Hack-Fest results to build a contribution either to an existing project or as an initial contribution of a new open source project
Who We Are and How to Join
As we have a public website it would be nice to give newcomers an understanding who is involved and how to interact with us.
How to participate in OpenADx?
OpenADx is in normal operation mode, means, since 25th June 2019 we are an official Eclipse Working Group which consists of more than 10 member companies, who are shaping the Working Group, which is done in the Steering Committee.
OpenADx is an open working group so everyone can participate!
Feel free to use our mailing list to start a discussion or to be part of one, to get answers to your questions around OpenADx and of course to stay tuned! You can use the solutions we provide in compliance with the open source license of the specific product.
From time to time, there will be also some workshops, which will be announced via our website, wiki and mailing list. So feel free to participate!
If you would like to engage more, e.g. to shape the working group together with us, you have to fulfil some prerequisites:
- You / your company has to be at least an Eclipse Contributing Member
- You / your company has to sign the OpenADx Working Group Participation Agreement and to decide your current membership level (explained in the Working Group Charter)
Our recommendation is “Driver Member” after the incubation phase to have the biggest possible influence in the working group.
For further questions, you can use our mailing list. ;-)
Interested Parties
Please add the name of your organization if you are interested in OpenADx or tell us to do it for you.
- ADLINK Technology
- AITAD
- AVL
- Bosch
- CEA
- Continental (ITS)
- Dassault Systemes (3DS)
- DENSO
- EclipseSource
- Elektrobit
- Eteration
- Fachhochschule Dortmund
- German Aerospace Center (DLR)
- IBM
- IPG Automotive GmbH
- itemis
- JC Information Management GmbH
- Kontrol GmbH
- Maeve Automation
- MathWorks
- Microsoft
- Open Robotics
- Red Hat
- Renesas
- Samsung
- science + computing ag (s+c)
- Seagate CORTX
- Siemens
- TESIS DYNAware GmbH
- Vattenfall AB
- ZF Friedrichshafen AG
Communication
- We have a mailing list: Subscribe for news and discussions: Mailing list
- We have workshops with introduction sessions and have just started to work on concrete testbeds to identify topics that we agree to collaborate on. Currently these workshops are weekly telecons. Please check the mailing list for invitations or ask questions regarding content or participation
Presentations
- see also OpenADx resources
Upcoming Presentations
- see also OpenADx events
Press releases
- see also OpenADx resources
Blog posts
- see also OpenADx resources
OpenADx logo
Our logo design contest is finished, please find here the winning design.
Copyright Eclipse Foundation
Testbed Candidates
Link to the Testbed Candidates
Events
- see also OpenADx Events
- see also OpenADx Events Archive
EclipseCon 2021 - Community Day - October, 25th 2021 - virtual event
Find out more about the EclipseCon and have a look to the session recordings! (will come soon)
Find here the presentation material from the "Automotive@Eclipse" Community Day
Presentation list - Automotive@Eclipse Community Day
Meet the Automotive@Eclipse Community |
Welcome, Agenda |
Introduction to openMobility |
Introduction to openPASS |
Introduction to openMDM |
Introduction to OpenADx |
The Automotive Top Level Project |
Welcome to OpenMCx |
[Indy Autonomous Challenge] |
[Software defined vehicle] |
[Automotive Edge Computing Consortium AECC] |
Assets
Pitch deck to be used inside of respective organizations File:OpenADxInformationDeck.zip