Replies: 2 comments
-
@Sharrrrk Great idea, it's exactly the concept of Autoware Universe. I feel it's not only for vehicle drivers but also for other Autoware components (Perception/Planning/etc.).
I think it's good to simply start with the Line 78 in cc441e7 Later, we can consider more efficient ways to share Autoware components. |
Beta Was this translation helpful? Give feedback.
-
@Sharrrrk Would it be possible for you to tell me a bit more details about this layer? |
Beta Was this translation helpful? Give feedback.
-
Background:
Inspired by the recent discussion of bus odd vehicle driver-by-wire protocol open source, it came into mind to have a vehicle protocol "hub" which is an open place for all Autoware users to upload and share their specific vehicle DBW protocol to all other Autoware users.
Currently, we do not have any vehicle DBW driver integrated in Autoware compared with other open source AD/ADAS project, which means users who wants to integrate Autoware into real vehicle will have to develop their own driver or seek for third party providers. And this may bring repeated effort.
However, it is also difficult for Autoware to maintain a vehicle DBW driver in the main stream, based on the fact that the vehicle models used by Autoware developer varies among each other , also I don't think we have resource for the adaptation, verification for lots of vehicle models.
So If we could have some kind of vehicle protocol "hub" -- the idea comes from docker hub, where the docker images are maintained by all developers around the world. In this way, All Autoware users, like the universities, or companies, could share their own vehicle DBW driver freely, and others could benifit from the "hub", to easily integrate Autoware into the available vehicle models.
Some concept of vehicle protocol "hub":
Beta Was this translation helpful? Give feedback.
All reactions