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
{{ message }}
Repository navigation
Commit a9d8505
Browse filesBrowse the repository at this point in the historyBrowse files
Juan Flores
committed
Merge remote-tracking branch 'origin/master' into nuttx-6lowpan
Copy file name to clipboardExpand all lines: _docs/FIROS2/index.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
title: microROS & FIWARE
2
+
title: micro-ROS & FIWARE
3
3
permalink: /docs/FIROS2/
4
4
redirect_from: /FIROS2/
5
5
---
6
6
7
7
8
8
## Interoperability
9
9
10
-
This subsection will explain all the design alternatives for the interoperability of FIROS2 with microROS.
10
+
This subsection will explain all the design alternatives for the interoperability of FIROS2 with micro-ROS.
11
11
12
12
### Mechanisms for the deserialisation of incoming data in the transformation library
13
13
@@ -25,7 +25,7 @@ For solving this issue, various methods to get it are proposed:
25
25
26
26
#### Use serialisation/deserialisation method provided by the middleware layer
27
27
28
-
This is currently the method used in microROS - FIROS 2 integration.
28
+
This is currently the method used in micro-ROS - FIROS 2 integration.
29
29
30
30
In this case, the transformation library will use user selected middleware interface to serialise/deserialise the bridged ROS2 messages.
31
31
This method requires to get the message typesupport for the bridged message type.
@@ -63,25 +63,25 @@ Note the call to ROS 2 interface __rosidl_typesupport_cpp::get_message_type_supp
63
63
#### Use serialisation/deserialisation method for an specific type support
64
64
65
65
In this case, the transformation library will use one specific type support to serialise/deserialise the bridged ROS2 messages.
66
-
In microROS case, the implementation to be used will be rosidl_typesupport_microxrcedds.
66
+
In micro-ROS case, the implementation to be used will be rosidl_typesupport_microxrcedds.
67
67
This method is trivial to develop as it does not require additional source code on the micro-ROS side.
68
68
69
-
In the case of microROS, the transformation library should use the serialisation/deserialisation API exposed by its typesupport, rosidl_typesupport_microxrcedds.
69
+
In the case of micro-ROS, the transformation library should use the serialisation/deserialisation API exposed by its typesupport, rosidl_typesupport_microxrcedds.
70
70
This mechanism requires the user to have access to the typesupport API, which sometimes is not always possible.
71
71
72
72
#### Used serialisation/deserialisation method generated from IDL file
73
73
74
74
In this case, transformation library will use generated code to serialise/deserialise the bridged ROS2 messages.
75
75
The generated code may be made using an IDL parser tool.
76
-
In the microROS case, Micro XRCE-DDS provides with Micro XRCE-DDS code generator, which accepts an IDL file as input and generates type code.
76
+
In the micro-ROS case, Micro XRCE-DDS provides with Micro XRCE-DDS code generator, which accepts an IDL file as input and generates type code.
77
77
This IDL files should correspond with those messages types the transformation is wanted.
78
78
This is the [integration service](https://github.com/eProsima/Integration-Service) native method.
79
79
Integration services uses this method, but it makes the development of the library slower as it needs to be generated per each message to be bridged.
In the case of ROS2/microROS workspaces, there are tools which generate those IDL files.
84
-
The rosidl_gen package is the package microROS/ROS2 could use to create IDL from ROS2 interfaces.
83
+
In the case of ROS2/micro-ROS workspaces, there are tools which generate those IDL files.
84
+
The rosidl_gen package is the package micro-ROS/ROS2 could use to create IDL from ROS2 interfaces.
85
85
86
86
### Integration proposals
87
87
@@ -90,7 +90,7 @@ This section presents all the integrations possibilities.
90
90
91
91
#### Direct integration
92
92
93
-
In this case, microROS Agent will act as a bridge between DDS-XRCE and NGSIv2.
93
+
In this case, micro-ROS Agent will act as a bridge between DDS-XRCE and NGSIv2.
94
94
95
95
Selected bridged topics and their corresponding transformations must be configured on the micro-ROS Agent node.
96
96
@@ -106,7 +106,7 @@ This proposal requires micro-ROS Agent changes, but it is the direct native inte
106
106
107
107
#### Indirect integration with a single FIROS2 node
108
108
109
-
In this case, microROS nodes will publish the configured topics on DDS, and a FIROS2 node will subscribe to those topics and convert them into NGSIv2 protocol.
109
+
In this case, micro-ROS nodes will publish the configured topics on DDS, and a FIROS2 node will subscribe to those topics and convert them into NGSIv2 protocol.
110
110
Selected bridged topics must be configured on that single FIROS2 node.
111
111
Each ROS 2 topic type should have a corresponding transformation library configured on that FIROS2 node.
112
112
@@ -124,11 +124,11 @@ This proposal requires transformation library development, but the integration w
124
124
125
125
#### Indirect integration with multiple FIROS2 nodes
126
126
127
-
In this case, microROS nodes will publish the configured topic on DDS and multiple FIROS2 nodes, one for each set topic, will subscribe to those topics and convert them into NGSIv2 protocol.
127
+
In this case, micro-ROS nodes will publish the configured topic on DDS and multiple FIROS2 nodes, one for each set topic, will subscribe to those topics and convert them into NGSIv2 protocol.
128
128
129
129
This approach would require more nodes on the network and individual configurations.
130
130
131
-
This approach is the one followed by microROS, and it is limited due to current FIROS 2 implementation.
131
+
This approach is the one followed by micro-ROS, and it is limited due to current FIROS 2 implementation.
132
132
133
133
This proposal requires transformation library development, but the integration will be the same as a regular ROS2 node, so no micro-ROS specific development should be expected.
Copy file name to clipboardExpand all lines: _docs/embedded_tf/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Table of contents
18
18
19
19
The TF transform graph, with its support for both a temporal history, and distributed information sources, has been a novel tool for robotics frameworks when it was released in 2008. Functionally, it is based in scene graph concepts known from computer graphics [[Foote 2013]](https://ieeexplore.ieee.org/document/6556373), but these only rarely offer distribution, and did not offer temporal histories at all (mainly, because this is not needed for frame-based rendering applications like in computer graphics). Distributed scene graphs have become more widely available also in computer graphics. In robotics, work by de Laet et al. [[De Laet et al. 2013]](https://ieeexplore.ieee.org/document/6696693) has extended transforms graphs to also contain twist (i.e., angular motion) information, and to provide more compile-time error checking. This is currently not integrated with distribution mechanisms, but could be used on a single system.
20
20
One persistent issue with transform graphs has been their resource use. ROS TF works through replicated copies of the entire transform tree at every node that uses it, and is implemented through unicast TCP connections between nodes. In systems with many dynamic parts, this has sometimes been called the ``TF firehose``, because of the large stream of incoming messages.
21
-
micro-ROS will go beyond this state of the art by running the dynamic transform tree in an embedded device, while keeping resource use to a minimum based on an analysis of the spatial and temporal details actually necessary. Further, enabling real-time queries even in the face of concurrent updates through integration will be realized through integration with the microROS real-time executor. It is also planned to integrate the embedded TF will with the node lifecycle to achieve further power-savings
21
+
micro-ROS will go beyond this state of the art by running the dynamic transform tree in an embedded device, while keeping resource use to a minimum based on an analysis of the spatial and temporal details actually necessary. Further, enabling real-time queries even in the face of concurrent updates through integration will be realized through integration with the micro-ROS real-time executor. It is also planned to integrate the embedded TF will with the node lifecycle to achieve further power-savings
This page lists the hardware platforms that we use to test and develop micro-ROS, and also accessories that we frequently refer to, such as add-on boards, and JTAG probes.
6
+
7
+
## Reference Platforms {#evaluation-boards}
8
+
9
+
Even that micro-ROS technology can be ported to many targets, we have decided to select development platforms to support them. This page describes the main characteristic of those boards.
The [Olimex LTD STM32-E407](https://www.olimex.com/Products/ARM/ST/STM32-E407/open-source-hardware) is an open-hardware low-cost entry board for developing custom applications with the STM32F407ZGT6 Cortex-M4F microcontrollers from STMicroelectronics.
16
+
17
+
It contains 196KB of RAM and 1MB of Flash. It is a very complete board thanks to the wide variety of communication interfaces it offers: USB OTG, Ethernet, SD Card slot, SPI, CAN or I2C buses are exposed. The board contains various expansion options available: Arduino-like headers for attaching daughter boards, many pins exposed, as well as a UEXT connector. This connector is a custom pin-out bus and is used to attach sensor breakouts sensors that manufacturer sells.
18
+
19
+
### Development tools
20
+
21
+
In order to flash and debug the board, it is required to get a JTAG probe. We recommend getting on of the next JTAG probes:
4
22
5
-
This page lists the hardware that microROS currently supports, and also accessories that we frequently refer to, such as add-on boards, and JTAG probes.
The (STM32L1 Discovery Kit)[https://www.st.com/en/evaluation-tools/32l152cdiscovery.html] is an open hardware design, ultra low power and low-cost entry board for developing custom applications. It contains an STM32L152RCT6 Cortex-M3 microcontroller manufactured by ST Microelectronics. This part number contains 32KB of RAM and 256KB of flash memory. It also includes an ST-Link in-circuit debugger that allows flashing and debugging the target microcontroller.
16
38
17
-
This is a JTAG probe with a USB and RS232 port that can also power the board. It looks as follows:
18
-

39
+
### Resources
19
40
20
-
See the [Olimex product page for ARM-USB-OCD-H](https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/) for details.
41
+
+[Vendor main page](https://www.st.com/en/evaluation-tools/32l152cdiscovery.html)
Copy file name to clipboardExpand all lines: _docs/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ permalink: /docs/home/
3
3
title: Overview
4
4
---
5
5
6
-
[microROS](https://cordis.europa.eu/project/rcn/213167_en.html) puts ROS2 onto microcontrollers, making them first class participants of the ROS 2 environment.
6
+
[micro-ROS](https://cordis.europa.eu/project/rcn/213167_en.html) puts ROS2 onto microcontrollers, making them first class participants of the ROS 2 environment.
Changed all functions that expect a vector of nodes to the just mentioned map.
142
142
143
-
* [include/rclcpp/node.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node.hpp) and [include/rclcpp/node_interfaces/node_base.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node_interfaces/node_base.hpp)
143
+
* [include/rclcpp/node.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node.hpp) and [include/rclcpp/node_interfaces/node_base.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node_interfaces/node_base.hpp)
144
144
145
145
Extended arguments of create\_callback\_group function for the real-time class.
146
146
@@ -153,7 +153,7 @@ In this section, we describe the necessary changes to the Executor API and repor
153
153
154
154
Removed the get\_associated\_with\_executor\_atomic function.
155
155
156
-
All the changes can be found in the branches [cbg-executor-0.5.1](https://github.com/microROS/rclcpp/tree/cbg-executor-0.5.1/rclcpp) and [cbg-executor-0.6.1](https://github.com/microROS/rclcpp/tree/cbg-executor-0.6.1/rclcpp) for the corresponding version 0.5.1 and 0.6.1 of the rclcpp in the fork at [github.com/microROS/rclcpp/](https://github.com/microROS/rclcpp/).
156
+
All the changes can be found in the branches [cbg-executor-0.5.1](https://github.com/micro-ROS/rclcpp/tree/cbg-executor-0.5.1/rclcpp) and [cbg-executor-0.6.1](https://github.com/micro-ROS/rclcpp/tree/cbg-executor-0.6.1/rclcpp) for the corresponding version 0.5.1 and 0.6.1 of the rclcpp in the fork at [github.com/micro-ROS/rclcpp/](https://github.com/micro-ROS/rclcpp/).
157
157
158
158
159
159
### Meta-Executor Concept
@@ -175,7 +175,7 @@ With the test bench, we validated the functioning of the approach - here on ROS
175
175
176
176

177
177
178
-
The test bench is provided in the [bg-executor_ping-pong_cpp](https://github.com/microROS/microROS_experiments/tree/experiment/cbg-executor-0.6.1/cbg-executor_ping-pong) package of the [microROS_experiments](https://github.com/microROS/microROS_experiments) repository.
178
+
The test bench is provided in the [bg-executor_ping-pong_cpp](https://github.com/micro-ROS/micro-ROS_experiments/tree/experiment/cbg-executor-0.6.1/cbg-executor_ping-pong) package of the [micro-ROS_experiments](https://github.com/micro-ROS/micro-ROS_experiments) repository.
0 commit comments