Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Papyrus/customizations/robotics/reverse

< Papyrus‎ | customizations/robotics
Revision as of 11:16, 29 March 2020 by Unnamed Poltroon (Talk) (Created page with "== ROS2 reverse == In order to start creating ROS2 compatible components with Papyrus for Robotics, it is important to enable referencing standard ROS2 messages. These have b...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

ROS2 reverse

In order to start creating ROS2 compatible components with Papyrus for Robotics, it is important to enable referencing standard ROS2 messages. These have been made available in a model library in form of RobMoSys compliant communication objects and service definitions. This library has been obtained by a reverse functionality within Papyrus for robotics that scans the available list of ros messages and services. If the message is not already existing, it will be created.

It is also possible to create a set of component definitions from the currently running ROS nodes. This reverse mechanism is currently limited to the structural part of a component, i.e. its ports along with the provided or required service definitions.

The following screenshots shows the context menus for starting reverse engineering.

Papyrus-customizations-robotics-menu-reverse.png
Context menu for generating code

Back to the top