Those familiar with
micro-ROS
, know that the transport protocols supported by default are Serial (UART) and UDP (over WiFi and Ethernet) – of course depending on the technologies offered by the specific hardware.
However, due to the variety of the communication peripherals exposed by the platforms it supports, there might be users willing to use micro-ROS over their own transport. In order to address these cases, we offer these users the possibility to create their own desired
Custom transport
. This relies on a mechanism we have lately refactored so as to abstract the library as much as possible from the underlying OS.
micro-ROS inherits its new profile for Custom transports from its middleware
Micro XRCE-DDS
, which provides a user API that allows interfacing with the lowest level transport layer at runtime and to implement Custom transports in both the Client and the Agent. Thanks to this, the Micro XRCE-DDS wire protocol can be transmitted over virtually any protocol, network, or communication mechanism.
<p align="center">
<img width="40%" src=".images/renesas_logo.gif">
<img width="40%" src=".images/microros_logo.png">
# micro-ROS transports for Renesas e<sup>2</sup> studio
Depending on which transport is used for micro-ROS specific configurations, the following should be done.
- [micro-ROS transports for Renesas e<sup>2</sup> studio](#micro-ros-transports-for--renesas-esup2sup-studio)
- [USB-CDC transport](#usb-cdc-transport)
- [Serial UART transport](#serial-uart-transport)
- [UDP transport (FreeRTOS + TCP)](#udp-transport-freertos--tcp)
- [UDP transport (ThreadX + NetX)](#udp-transport-threadx--netx)
- [CAN FD transport](#can-fd-transport)