Skip to content

Commit 02bacfc

Browse files
committed
Changed several figures alt in the blogposts.
1 parent ef5a9c1 commit 02bacfc

3 files changed

Lines changed: 5 additions & 5 deletions

File tree

_posts/2020-07-17-EWG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,4 @@ Please find [here](http://meet.google.com/saf-gjix-swf) the link to the Google m
2020
the first meeting.
2121
Everyone is welcome to add items that they consider relevant in the form of comments.
2222

23-
<img alt="micro-ROS display" src="/img/posts/2020-07-17-EWG.jpg" width="100%"/>
23+
<img alt="EWG advertisement" src="/img/posts/2020-07-17-EWG.jpg" width="100%"/>

_posts/2020-08-27-esp32.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: francesca-finocchiaro
55

66
The micro-ROS team is glad to announce that the pool of boards officially supported by the project has widened! The [ESP32 MCU](https://www.espressif.com/en/products/socs/esp32) is now part of the family. ESP32 is a series of low-cost, low-power microcontrollers with integrated Wi-Fi and dual-mode Bluetooth, widely used for both commercial and industrial purposes.
77

8-
<img alt="micro-ROS display" src="/img/posts/esp32_cut.png" width="70%"/>
8+
<img alt="ESP32 board" src="/img/posts/esp32_cut.png" width="70%"/>
99

1010
micro-ROS targets mid-range and medium-to-high performance 32-bits microcontrollers families. Up to now, the boards officially supported by the project were solely based on the STM32 series from ST, MCUs featuring ARM Cortex-M processors. On the other hand, the ESP32 is an ultra-low power consumption dual-core system with two Xtensa LX6 CPUs, exposing a large collection of peripherals.
1111

_posts/2020-09-03-memo-prof-xrcedds.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ The results for this analysis are summarized in the graphs below for publisher a
1313

1414
* **Publisher Applications**:
1515

16-
<img alt="micro-ROS display" src="/img/posts/overall_pub.png" width="80%"/>
16+
<img alt="Results for Micro XRCE-DDS publisher application" src="/img/posts/overall_pub.png" width="80%"/>
1717

1818
* **Subscriber Applications**:
1919

20-
<img alt="micro-ROS display" src="/img/posts/overall_sub.png" width="80%"/>
20+
<img alt="Results for Micro XRCE-DDS subscriber application" src="/img/posts/overall_sub.png" width="80%"/>
2121

2222

2323
On the server side, we have investigated the memory consumption of an Agent communicating with a mock Client application on Linux that is publishing and subscribing to topics of known size, by measuring the binary size of the compiled agent (which resulted to be of 385 KB) and analysing heap and stack usages. The results for the latter are summarized in the plot below.
2424

25-
<img alt="micro-ROS display" src="/img/posts/Memory_usage_XRCE-DDS_Agent.png" width="60%"/>
25+
<img alt="Results for Micro XRCE-DDS agent" src="/img/posts/Memory_usage_XRCE-DDS_Agent.png" width="60%"/>
2626

2727
For more information regarding the methodology employed for performing these profilings, refer to the full report published on [eProsima](https://www.eprosima.com/)'s webpage.

0 commit comments

Comments
 (0)