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
<h3class="feature_name">☑ Microcontroller-optimized client API supporting all major ROS concepts</h3>
47
-
<divclass="feature_teaser">
48
-
<p>Micro-ROS brings all major core concepts ...</p>
49
-
</div>
48
+
Micro-ROS offers **seven key features** that make it ready for use in your microcontroller-based robotic project:
49
+
50
+
<divclass="feature feature_is_active">
51
+
<divclass="feature_title">☑ Microcontroller-optimized client API supporting all major ROS concepts<spanclass="three_dots"> (...)</span></div>
50
52
<divclass="feature_description">
51
53
<p>Micro-ROS brings all major core concepts such as nodes, publish/subscribe, client/service, node graph, lifecycle, etc. onto microcontrollers (MCU). The client API of micro-ROS (in the C programming language) is based on the standard ROS 2 Client Support Library (rcl) and a set of extensions and convenience functions (rclc).</p>
52
54
<p>The combination rcl+rclc is optimized for MCUs. After an initialization phase, it can be used without any dynamic memory allocations. The rclc package provides advanced execution mechanisms allowing implementing well-proven scheduling patterns from embedded systems engineering.</p>
53
55
</div>
54
56
</div>
55
57
56
58
<divclass="feature">
57
-
<h3class="feature_name">☑ Seamless integration with ROS 2</h3>
<pclass="feature_title">☑ Seamless integration with ROS 2<spanclass="three_dots"> (...)</span></p>
61
60
<divclass="feature_description">
62
61
<p>The micro-ROS agent connects micro-ROS nodes (i.e. components) on MCUs seamlessly with standard ROS 2 systems. This allows accessing micro-ROS nodes with the known ROS 2 tools and APIs just as normal ROS nodes.</p>
63
62
</div>
64
63
</div>
65
64
66
65
<divclass="feature">
67
-
<h3class="feature_name">☑ Multi-RTOS support with generic build system</h3>
68
-
<divclass="feature_teaser">
69
-
<p>Micro-ROS supports three popular open-source ...</p>
70
-
</div>
66
+
<pclass="feature_title">☑ Multi-RTOS support with generic build system<spanclass="three_dots"> (...)</span></p>
71
67
<divclass="feature_description">
72
68
<p>Micro-ROS supports three popular open-source real-time operating sytems (RTOS): FreeRTOS, Zephyr, and NuttX. It can be ported on any RTOS that comes with a POSIX interface.</p>
73
69
<p>The RTOS-specific build systems are integrated into few generic setup scripts, which are provided as a ROS 2 package. Therefore, ROS developers can use their usual command line tools. In addition, micro-ROS provides selected integrations with RTOS-specific tool chains (e.g., for ESP-IDF and Zephyr).</p>
74
70
</div>
75
71
</div>
76
72
77
73
<divclass="feature">
78
-
<h3class="feature_name">☑ Extremely resource-constrained but flexible middleware</h3>
79
-
<divclass="feature_teaser">
80
-
<p>Micro XRCE-DDS by eProsima meets all requirements ...</p>
81
-
</div>
74
+
<pclass="feature_title">☑ Extremely resource-constrained but flexible middleware<spanclass="three_dots"> (...)</span></p>
82
75
<divclass="feature_description">
83
76
<p>Micro XRCE-DDS by eProsima meets all requirements for a middleware for deeply embedded systems. That is why micro-ROS has been one of the applications for this implementation of the new DDS for Extremely Resource Constrained Environments (XRCE) standard. For the integration with the ROS middleware interface (rmw) in the micro-ROS stack, static memory pools were introduced to avoid dynamic memory allocations at runtime.</p>
84
77
<p>The middleware comes with built-in support for serial transports, UDP over Ethernet, Wi-Fi, and 6LoWPAN, and Bluetooth. Furthermore, the Micro XRCE-DDS source code provides templates for implementing support for further transports.</p>
<p>Micro-ROS comes under the same permissive license as ROS 2, which is Apache License 2.0. This applies to the micro-ROS client library, the middleware layer, and tools.</p>
95
85
<p>When creating a project with an underlying RTOS, please take into account the license(s) of the RTOS project or vendor.</p>
96
86
</div>
97
87
</div>
98
88
99
89
<divclass="feature">
100
-
<h3class="feature_name">☑ Vibrant community and ecosystem</h3>
101
-
<divclass="feature_teaser">
102
-
<p>Micro-ROS is developed by a constantly growing ...</p>
103
-
</div>
90
+
<pclass="feature_title">☑ Vibrant community and ecosystem<spanclass="three_dots"> (...)</span></p>
104
91
<divclass="feature_description">
105
92
<p>Micro-ROS is developed by a constantly growing, self-organized community backed by the Embedded Working Group, a formal ROS 2 Working Group. The community shares entry level tutorials, provides support via Slack and GitHub, and meets in public Working Group video-calls on a monthly basis. As a matter of course, commercial support is provided for the Micro XRCE-DDS by eProsima.</p>
106
93
<p>This community also create tools around micro-ROS. For example, to optimize micro-ROS-based applications to the MCU hardware, specific benchmarking tools have been developed. These allow checking memory usage, CPU time consumption and general performance.</p>
107
94
</div>
108
95
</div>
109
96
110
97
<divclass="feature">
111
-
<h3class="feature_name">☑ Long-term maintainability and interoperability</h3>
112
-
<divclass="feature_teaser">
113
-
<p>Micro-ROS is made up of well-established components ...</p>
114
-
</div>
98
+
<pclass="feature_title">☑ Long-term maintainability and interoperability<spanclass="three_dots"> (...)</span></p>
115
99
<divclass="feature_description">
116
100
<p>Micro-ROS is made up of well-established components: Famous open-source RTOSs, a standardized middleware, and the standard ROS 2 Client Support Library (rcl). In this way, the amount of micro-ROS-specific code was minimized for long-term maintainability. At the same time, the micro-ROS stack preserves the modularity of the standard ROS 2 stack. Micro-ROS can be used with a custom middleware layer - and thus standard - or a custom ROS client library.</p>
117
-
<p>Furthermore, by the [System-Of-Systems Synthesizer](https://soss.docs.eprosima.com/) (SOSS), a fast and lightweight [OMG DDS-XTYPES standard](https://www.omg.org/spec/DDS-XTypes) integration tool, further middleware protocols can be connected. For example, we have developed the SOSS-FIWARE and SOSS-ROS2 System-Handles, which connect ROS 2 and micro-ROS with the [FIWARE Context Broker](https://www.fiware.org/) by the NGSIv2 (Next Generation Service Interface) standard by leveraging the integration capabilities of the SOSS core.</p>
101
+
<p>Furthermore, by the [System-Of-Systems Synthesizer](https://soss.docs.eprosima.com/) (SOSS), a fast and lightweight <ahref="https://www.omg.org/spec/DDS-XTypes">OMG DDS-XTYPES standard</a> integration tool, further middleware protocols can be connected. For example, we have developed the SOSS-FIWARE and SOSS-ROS2 System-Handles, which connect ROS 2 and micro-ROS with the <ahref="https://www.fiware.org/">FIWARE Context Broker</a> by the NGSIv2 (Next Generation Service Interface) standard by leveraging the integration capabilities of the SOSS core.</p>
118
102
</div>
119
-
</div>
103
+
</div>
104
+
105
+
## Layered and Modular Architecture
106
+
107
+
Micro-ROS follows the [ROS 2 architecture](https://index.ros.org/doc/ros2/) and makes use of its middleware pluggability to use [DDS-XRCE](https://www.omg.org/spec/DDS-XRCE/), which is optimized for microcontrollers. Moreover, it uses POSIX-based RTOS (NuttX) instead of Linux.
Dark blue components are developed specifically for micro-ROS. Light blue components are taken from the standard ROS 2 stack. We seek to contribute as much code back to the ROS 2 mainline codebase as possible.
0 commit comments