Skip to content

Commit 6c65c11

Browse files
committed
Improved documentation of Bucharest decision.
Signed-off-by: Ralph Lange (CR/AEE1) <ralph.lange@de.bosch.com>
1 parent 8e2b531 commit 6c65c11

1 file changed

Lines changed: 34 additions & 22 deletions

File tree

  • _docs/client_library/decision_paper

‎_docs/client_library/decision_paper/index.md‎

Lines changed: 34 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Client Library -- Decision Paper
2+
title: Client Library - Decision Paper
33
permalink: /docs/client_library/decision_paper/
44
---
55

@@ -168,41 +168,53 @@ A discrimination of the usage of the workaround is still to be done. This should
168168

169169
See the modified rcl version at [https://github.com/micro-ROS/rcl/commit/cdb0cca50d49c5b5576bf88d2bb7a1d57ae1e00b](https://github.com/micro-ROS/rcl/commit/cdb0cca50d49c5b5576bf88d2bb7a1d57ae1e00b)
170170

171-
## High-level core features missing in rcl
171+
## Decision in the OFERA Project
172+
173+
* In a face-to-face meeting in Bucharest in March 2019, the partners from the OFERA project decided to take a double-tracked approach as follows:
174+
175+
1. Use rcl as C-based Client Library for micro-ROS by enriching it with small, modular libraries for parameters, graph, logging, clock, timers, execution management, lifecycle and system modes, TF, diagnostics, and power management.
176+
2. Analyze fitness of rclcpp for use on microcontrollers, in particular regarding memory and CPU consumption as well as dynamic memory management.
177+
178+
In this meeting, we decided explicitly against a separate client library in the style of rclc.
179+
180+
### Responsibilities for extensions to rcl
181+
182+
Parameters (eProsima)
172183

173-
Parameters
184+
* Optimized implementation planned, where MCU client queries agent specifically for parameter values rather than all values being sent to the node on the MCU
174185

175-
* eProsima plans optimized implementation, where MCU client queries agent specifically for parameter values rather than all values being sent to the node on the MCU.
186+
Graph (eProsima)
176187

177-
Graph
188+
* Similar to parameters
178189

179-
* Similar to parameters.
190+
Logging (eProsima)
180191

181-
Logging
192+
* Optimized implementation for MCU
182193

183-
* Optimized implementation for MCU by eProsima
194+
Time / Clock and Timers (eProsima, Bosch, Acutronic Robotics)
184195

185-
Time / Clock and Timers [eProsima+Bosch+Erle, in Turtlebot demo -- step 1]
186-
* Jan, looks into rcl time and clock interface
196+
* Bosch will analyze rcl time and clock interface
187197
* Synchronization with microprocessor -- message types already available in micro-XRCE-DDS
188-
* Adapter for RTOS required -- part of abstraction layer ?!
198+
* Adapter for RTOS required -- part of abstraction layer
189199

190-
Executor [Bosch, in Turtlebot demo -- step 1]
200+
Executor (Bosch)
191201

192-
Lifecycle / System modes [Bosch, in Turtlebot demo -- step 2]
202+
* Very simple mechanism will be developed in the micro-ROS Turtlebot demo until August 2019.
193203

194-
TF [Bosch, in Turtlebot demo -- step 3]
204+
Lifecycle / System modes (Bosch)
195205

196-
Diagnostics [Bosch, in Turtlebot demo -- step 2]
206+
* To be developed in a second step in the micro-ROS Turtlebot demo.
197207

198-
* Liveliness of node: Introduce mechanism in micro-XRCE-DDS similar to standard DDS?
199-
* Make PR for rmw extension with abstract interface to be informed about liveliness of other nodes?!
208+
TF (Bosch)
200209

201-
Power management
210+
* To be developed in a third step in the micro-ROS Turtlebot demo.
202211

203-
* RTOS dependant, it would require implementation for each one, AL
212+
Diagnostics (Bosch)
204213

205-
## Decision in the OFERA Project
214+
* To be developed in the second step in the micro-ROS Turtlebot demo.
215+
* Liveliness of node: Introduce mechanism in micro-XRCE-DDS similar to standard DDS?
216+
* Make PR for rmw extension with abstract interface to be informed about liveliness of other nodes?!
217+
218+
Power management (Acutronic Robotics)
206219

207-
* Do not go for rclc but directly for rcl + extensions
208-
* Try out rclcpp on a MCU and measure memory and CPU consumption
220+
* Highly dependent on RTOS, it would require implementation for each one

0 commit comments

Comments
 (0)