diff --git a/_posts/2020-06-03-fiware_video.md b/_posts/2020-06-03-fiware_video.md index fb8e7c97..79fe65b4 100644 --- a/_posts/2020-06-03-fiware_video.md +++ b/_posts/2020-06-03-fiware_video.md @@ -12,4 +12,4 @@ straightforwardly. Find the video below: - \ No newline at end of file + diff --git a/_posts/2020-09-23-snap-XRCEDDS.md b/_posts/2020-09-23-snap-XRCEDDS.md new file mode 100644 index 00000000..1a9b8289 --- /dev/null +++ b/_posts/2020-09-23-snap-XRCEDDS.md @@ -0,0 +1,31 @@ +--- +title: Micro XRCE-DDS Agent now on snap! +author: francesca-finocchiaro +--- + +In collaboration with [Canonical](https://canonical.com/), we took the liberty to wrap the [Micro XRCE-DDS Agent](https://micro-xrce-dds.docs.eprosima.com/en/latest/agent.html) as a [snap](https://snapcraft.io/) package, which sets an important milestone for easing the use of Micro XRCE-DDS. + +Canonical + +Snap is a package manager designed to bundle and handle applications and their dependencies on several Linux distros, among which Ubuntu. + +Snap + +The snap packaging of the Agent comes with two ways of running it: as a simple executable or by means of a Linux service. + +The first implies the usage of the Agent’s built-in CLI, where you can specify the standard configuration parameters (such as transport, port…) directly, as follows: +``` +micro-xrce-dds-agent +``` + +The second launches the Agent as a Linux service running in the background; to do so, simply execute: +``` +snap set micro-xrce-dds-agent daemon=true +``` +In this case, instead of specifying the Agent’s launch parameters via the CLI, users can configure them thanks to the `snap services` interface, using the `snap set micro-xrce-dds-agent =` command. These parameters’ values are only valid when the `daemon` option is set to `true`, while they are ignored in `snap run` mode. + +To have a look at the full list of configurable parameters, click [here](https://snapcraft.io/micro-xrce-dds-agent). + +Given the closeness of the two Agents libraries, a snap release of the micro-ROS Agent is just one step away! + +{% include logos_disclaimer.md %} diff --git a/_posts/2020-09-24-microROS_and_FIWARE.md b/_posts/2020-09-24-microROS_and_FIWARE.md new file mode 100644 index 00000000..01ee8a33 --- /dev/null +++ b/_posts/2020-09-24-microROS_and_FIWARE.md @@ -0,0 +1,19 @@ +--- +title: micro-ROS and FIWARE - Enabling Robotics Systems on Microcontrollers +author: francesca-finocchiaro +--- + +On September 23rd, the [FIWARE Foundation](https://www.fiware.org/foundation/) held a webinar titled “Enabling Robotics Systems on Microcontrollers”, as a part of its series of free webinars about open source platform components for Smart Solutions. + +The webinar focused on the interoperability between micro-ROS and FIWARE, made possible by [eProsima Integration-Service](https://integration-service.docs.eprosima.com/en/latest/) and its core [SOSS](https://soss.docs.eprosima.com/en/latest/). SOSS is a platform that acts as a centralizing bridge to communicate incompatible protocols that speak different languages. Its working principle rests on System-Handles, plugins that put the core into communication with each of the protocols that are meant to be integrated into the platform. Once a system is integrated by means of a dedicated System-Handle, it can speak with any other system that is already integrated into the SOSS world. +The SOSS-ROS2 and the SOSS-FIWARE System-Handles serve as key enablers to integrate micro-ROS into the FIWARE ecosystem, a framework of open source platform components which can be assembled together and with other third-party platform components to accelerate the development of Smart Robotics Solutions. + +Key contributions of Powered by FIWARE architectures to micro-ROS applications are: + +* Interfacing with the Internet of Things (IoT), Robots and third-party systems, for capturing updates on context information and translating required actuations. +* Context Data/API management, publication, and monetization, bringing support to usage control and the opportunity to publish and monetize part of managed context data. +* Processing, analysis, and visualization of context information implementing the expected smart behavior of applications and/or assisting end users in making smart decisions + +Find the full presentation below: + + diff --git a/_posts/2020-09-30-discovery.md b/_posts/2020-09-30-discovery.md new file mode 100644 index 00000000..16a78c0e --- /dev/null +++ b/_posts/2020-09-30-discovery.md @@ -0,0 +1,20 @@ +--- +title: A brand new discovery mechanism in micro-ROS +author: francesca-finocchiaro +--- + +micro-ROS is now implementing client/server handshaking by discovery! + +The discovery mechanism allows micro-ROS Clients to discover Agents in the network by UDP. If a Client doesn’t know of any Agent beforehand, it sends a discovery call by multicast and the reachable Agents respond by sending information about them, such as their IP and port. The Client matches automatically with the first Agent that provides information, and the communication between the matched entities proceeds in the usual way. + +Discovery + +micro-ROS inherits its discovery mechanism from the [Micro XRCE-DDS library](https://micro-xrce-dds.docs.eprosima.com/en/latest/client.html#discovery-profile), which is then implemented in the RMW layer. Discovery is accessible by default at the Client level when using UDP transport, and can be activated in the Agent by using the `-d` flag when running it from terminal with the [snap command](https://discourse.ros.org/t/micro-xrce-dds-agent-now-on-snap/16523): +``` +micro-xrce-dds-agent udp4 -d +``` +If you’re running instead the daemonized version of the Agent via the provided snap service, you can turn on the discovery mechanism like this: +``` +snap set micro-xrce-dds-agent discovery="true" +``` +Find [here](https://github.com/micro-ROS/micro-ROS-demos/tree/foxy/rclc/autodiscover_agent) an example showing how to use this new feature! diff --git a/_posts/2020-10-01-zephyr_partnership.md b/_posts/2020-10-01-zephyr_partnership.md new file mode 100644 index 00000000..d4beb585 --- /dev/null +++ b/_posts/2020-10-01-zephyr_partnership.md @@ -0,0 +1,14 @@ +--- +title: micro-ROS is now Associate Member of the Zephyr Project +author: francesca-finocchiaro +--- + +micro-ROS is now an Associate Partner of the [Zephyr Project](https://www.zephyrproject.org/)! + +Zephyr + +Zephyr is a scalable open source Real-Time Operating System (RTOS) designed to fit resource constrained and embedded systems, with safety and security in mind. It forms part of [the Linux Foundation](https://www.linuxfoundation.org/), which supports a wide range of open source projects. Zephyr targets the same range of systems and applications with deterministic and time-critical constrains as micro-ROS, such as connected sensors and actuators, microcontrollers and small IoT devices of all kinds. micro-ROS and Zephyr complement each other by allowing to easily create heterogeneous distributed robotic systems and also integrate these devices seamlessly into the ROS 2 ecosystem. + +For additional information and the official press release by the Zephyr Project, follow this [link](https://www.zephyrproject.org/google-and-facebook-select-zephyr-rtos-for-next-generation-products/). + +{% include logos_disclaimer.md %} diff --git a/img/posts/canonical.png b/img/posts/canonical.png new file mode 100644 index 00000000..f5f155f9 Binary files /dev/null and b/img/posts/canonical.png differ diff --git a/img/posts/discovery.png b/img/posts/discovery.png new file mode 100644 index 00000000..d589f557 Binary files /dev/null and b/img/posts/discovery.png differ diff --git a/img/posts/snap.png b/img/posts/snap.png new file mode 100644 index 00000000..4109c306 Binary files /dev/null and b/img/posts/snap.png differ diff --git a/img/posts/snap2.png b/img/posts/snap2.png new file mode 100644 index 00000000..7b0d63d0 Binary files /dev/null and b/img/posts/snap2.png differ