Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search


< Papyrus‎ | customizations/robotics
Revision as of 03:00, 29 May 2021 by (Talk | contribs) (Manual Installation)

Installation instructions

Installation through the Virtual Box Appliance

We provide a virtual machine that comes with everything needed pre-installed to develop ROS2 applications using Papyrus for Robotics.

For this virtual machine, username is “user” and password is “p”. User “user” is allowed to use “sudo”.

Manual Installation

Binary installation

Alternatively, Papyrus for Robotics can be installed either in form of an RCP (a self contained Eclipse installation) or added to an existing Eclipse installation by using an update site. Both can be downloaded from referring to the current 0.8 release.

  • If you use the RCP, make sure that a JRE is already installed in your system and contained in the system PATH.
  • If want to extend an existing Eclipse, add the update-site via Help->Install New Software->Add (release update-site (for 2020-06) or one of the nightly update sites below)
  • Nightly builds with the latest changes are available on the Eclipse continuous integration server, see 2020-06 (nightly update site), and 2021-03 (nightly update site), 2021-03 (nightly RCP builds).

Source code installation

See Developer installation.

ROS2 Dependencies

ROS2 Environment

If you plan to use Papyrus for Robotics to design and deploy ROS2-based systems, you need to install ROS2. The current release 0.8 supports ROS2 Foxy Fitzroy and ROS2 Eloquent Elusor

Behavior Tree Execution

In addition to ROS2, if you plan to use Papyrus for Robotics to execute task specifications in form of behavior trees, you need to install:

  • the bt_sequencer package. This package is a slightly modified version of nav2_bt_navigator with the following changes:
    • commented default plugin_libs
    • added a ZMQ logger from BehaviorTree.CPP
    • forced the execution of BT at activation (and not as response to a NavigateToPose goal request)

Back to the top