You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Their arguments are centered around the danger of using privileged containers to talk to external hardware, the lack of transactional and delta updates as well as complaining about the difficulty of configuring networking.
This talk will not only give technical counter-arguments on why they are wrong but also give a few arguments on why it’s easier, more secure and in general a better experience to use docker containers to prototype and deploy ROS-based robotics solutions.
2. ros-io, a hardware abstraction layer for electronics
We are living on a global chip shortage. Some of the under development ROS projects do not have some specific sensors or actuators due the shortage. We aim to solve that by creating a hardware abstraction layer for modules that are connected to I2C, UART and GPIO interfaces. This allows makers to prototype much faster, and companies the ability to replace hardware with available options, without changing their code-base. This reduces friction by eliminating the need to write low-level code, firmware or ROS nodes and replaces it with a config file similar to the way docker-compose works.
3. Using balenaBlocks to simplify prototyping and deployment of robot solutions
In this talk we are going to explore how using balenaBlocks can speed up prototyping, make your code more reusable, and bring in network effects in the community, all while making it extremely easy to deploy and provision devices. We are going to go through the advantages of using containers for robotics, and how to do that in the most efficient way possible. We are also going to show you how to develop and configure robots using just one file: docker-compose.yaml
Full content of all three talks available on google docs
Hardware Needed
Not sure yet
The text was updated successfully, but these errors were encountered:
Prerequisites
Event Name
ROSCon2022
Type
Conference
Focus / Event Nice / Target Audience
Robotics Developer
Medium
Hybrid
Location
Kyoto, Japan
Date
19-21 October 2022
CFP and last date
Yes (Applied) - June 9th, 2022
Talk title
Duration
Description
1. Canonical was wrong ! ROS and docker ARE indeed a good fit, here's why
Last year, Canonical published an article called "ROS Docker; 6 reasons why they are not a good fit" https://ubuntu.com/blog/ros-docker
Their arguments are centered around the danger of using privileged containers to talk to external hardware, the lack of transactional and delta updates as well as complaining about the difficulty of configuring networking.
This talk will not only give technical counter-arguments on why they are wrong but also give a few arguments on why it’s easier, more secure and in general a better experience to use docker containers to prototype and deploy ROS-based robotics solutions.
2. ros-io, a hardware abstraction layer for electronics
We are living on a global chip shortage. Some of the under development ROS projects do not have some specific sensors or actuators due the shortage. We aim to solve that by creating a hardware abstraction layer for modules that are connected to I2C, UART and GPIO interfaces. This allows makers to prototype much faster, and companies the ability to replace hardware with available options, without changing their code-base. This reduces friction by eliminating the need to write low-level code, firmware or ROS nodes and replaces it with a config file similar to the way docker-compose works.
3. Using balenaBlocks to simplify prototyping and deployment of robot solutions
In this talk we are going to explore how using balenaBlocks can speed up prototyping, make your code more reusable, and bring in network effects in the community, all while making it extremely easy to deploy and provision devices. We are going to go through the advantages of using containers for robotics, and how to do that in the most efficient way possible. We are also going to show you how to develop and configure robots using just one file: docker-compose.yaml
Full content of all three talks available on google docs
Hardware Needed
Not sure yet
The text was updated successfully, but these errors were encountered: