Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions _data/docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@

- title: Client Library
docs:
- concepts/client_library
- concepts/client_library/real-time_executor
- concepts/client_library/system_modes
- concepts/client_library/decision_paper
- concepts/client_library/rcutils_analysis
- concepts/client_library/introduction
- concepts/client_library/features
- concepts/client_library/execution_management
- concepts/client_library/lifecycle_and_system_modes
- concepts/client_library/diagnostics

- title: Middleware
docs:
Expand Down
Binary file not shown.
Binary file not shown.
213 changes: 0 additions & 213 deletions _docs/concepts/client_library/decision_paper/index.md

This file was deleted.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
18 changes: 18 additions & 0 deletions _docs/concepts/client_library/diagnostics/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: Diagnostics
permalink: /docs/concepts/client_library/diagnostics/
---

Although diagnostics is not part of the ROS 2 Client Library packages (i.e., rclcpp, rclpy), it definitely can be counted to the extended client library as it provides very generic and application-independent functionalities.

That's why the micro-ROS Client Library also comes with basic diagnostics functionalities. These are compatible with ROS 2 diagnostics, but comprise three features only:

* Diagnostic message types (optimized for Micro-XRCE-DDS - no dynamic arrays)
* Updater mechanisms for rclc
* Selected basic diagnostic monitors

The micro-ROS diagnostics packages do not provide any aggregation mechanisms as we assume that such aggregation takes place on a microprocessor running standard ROS 2. Hence, we assume the following typical architecture:

<img src="diagnostics_architecture.png" style="display:block; width:60%; margin-left:auto; margin-right:auto;"/>

For more information, please see [https://github.com/micro-ROS/micro_ros_diagnostics/](https://github.com/micro-ROS/micro_ros_diagnostics/).
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
---
title: Real-Time Executor
redirect_from: /real-time_executor/
permalink: /docs/concepts/client_library/real-time_executor/
title: Execution Management
permalink: /docs/concepts/client_library/execution_management/
redirect_from:
- /real-time_executor/
- /docs/concepts/client_library/real-time_executor/
---


Expand Down
16 changes: 16 additions & 0 deletions _docs/concepts/client_library/features/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
title: Feature List
permalink: /docs/concepts/client_library/features/
---

The micro-ROS Client Library, formed by standard [ROS 2 Client Support Library (rcl)](https://github.com/ros2/rcl/) and the new [ROS 2 Client Library package (rclc)](https://github.com/ros2/rclc/), is going to feature all major ROS concepts such as

* Nodes
* Publishers/subscriptions
* Services/clients
* Graph
* Executor
* Lifecycle
* Parameters

Most features are already available in the Foxy release. Please see our [Feature Overview page](/docs/overview/features/) for details on the status. To learn developing your own application nodes with rcl + rclc, please head to the corresponding [programming tutorial](/docs/tutorials/core/programming_rcl_rclc/).
29 changes: 0 additions & 29 deletions _docs/concepts/client_library/index.md

This file was deleted.

Loading