Launching the RobMoSys Academy

Dear Roboticist,

so far our RobMoSys Academy page included important links to the RobMoSys Wiki, the Pilot section and our YouTube channel. We have used the "Corona-times" to produce video tutorials for a broader public, explaining the tools and benefits of the RobMoSys approach. Visit the Academy page to watch the first of a series of tutorials.

We would also like to draw your attention to our new Papyrus for Robotics leaflet, which describes a clear migration path for a step-by-step integration of of existing model-driven software and tools.

In this newsletter we are taking a closer look at three ITPs of Instrument #2:

• MiRON - QoS Metrics-In-the-loop for better Robot Navigation

• SafeCC4Robot - Safety Component Composition for Robots

• Vericomp - Verifiable Composition of Dynamics and Control Algorithms for Robot Motion

Most events these days have been transformed into virtual events, such as the 2020 edition of the International Conference on Robotics and Automation. On June 11th, a live demo was organised by RobMoSys together with PAL Robotics, which can still be seen on icra2020.org/big-screen until the end of August.

We hope to meet you in person at automatica 2020 fair (new dates: December 8-11), in the meantime feel free to contact us via the RobMoSys Discourse platform if you have any questions.

Wishing you a great summer break - stay safe and healthy!

Anna Principato

on behalf of the RobMoSys Consortium

New video tutorials for the RobMoSys Academy

Whether you are a developer or a robotics’ entrepreneur - the RobMoSys approach allows you to create cost-effective, composable, predictable and flexible robotics software with better tools. Our first video "Overcoming the Boundaries of Today's Model-Driven Engineering" gives a good introduction to what RobMoSys is all about!

Take a look at the first of our Academy videos - and don't hesitate to give us your feedback.

More Academy videos will follow this summer!

What are the challenges in robotic software development?

The current robotics software development landscape is primarily code-centric and highly fragmented into numerous and often incompatible component-based frameworks. It is characterized by a series of stand-alone tools, written in different programming languages, with sometimes overlapping capabilities, ranging from specialized coding facilities to sophisticated simulation environments.

Download our Papyrus4 Robotics Use Case Story to find out which benefits you gain when using the Papyrus4Robotics RobMoSys solution.

ITPs at work

In our second open call, nine Integrated Technical Projects (ITPs) were selected in Instrument #2 Ecosystem Challenges for a runtime of 12 months, starting from October 2019. In this newsletter we would like to introduce three of them:

MiRON - QoS Metrics-In-the-loop for better Robot Navigation

MiRoN ITP is contributing to RobMoSys by developing a model-based framework for dealing with adaptive robot navigation. In particular, the proposal is built on the Flexible Navigation Stack[1] to provide a novel approach to adaptive navigation based on the systematic use of models for dynamically reconfiguring the robot behavior, defined in terms of Behavior Trees (BT), according to the runtime prediction and estimation of QoS metrics defined on NFPs.

Follow @MiRON_ITP on Twitter

SafeCC4Robot -

Safety Component Composition for Robots

The SafeCC4Robot project aims to create a methodology and tool support for integrating components for robotics ensuring safety at system level. It will enable suppliers’ robotic components to be used at different robot systems while ensuring system will remain safe after the composition. Read about their Design of safety compliance robotic systems methodology and of safe-aware compositional robotic systems.

VERICOMP -

Verifiable Composition of Dynamics and Control Algorithms for Robot Motion

VERICOMP aims at enabling developers to make verifiable statements about compositions in the robot motion domain. In particular, the project will focus on the non-functional requirements (i.e. timing) in addition to the functional ones, since neglecting the timing properties and requirements of a control algorithm can lead to a highly unstable, unpredictable and dangerous behavior.

The consortium consits of University of Bielefeld and Hochschule Bonn-Rhein-Sieg

Enjoy the summer and stay tuned!

P.S. The RobMoSys Wiki is continuously being updated, describing examples of composition using the RobMoSys methodology. You can easily keep track of changes in the Wiki in our Changelog.

This email was sent to subscriber. If you wish to not longer receive the RobMoSys newsletter, please unsubscribe by using the link below.