[Documentation] [TitleIndex] [WordIndex

This is part of the Robotics in Concert project.


  Show EOL distros: 

rocon_app_platform: rocon_app_manager | rocon_app_manager_www | rocon_apps

Package Summary

Robot application platform for ros robots with a default implementation in python.

rocon_app_platform: rocon_app_manager | rocon_apps

Package Summary

Robot application platform for ros robots with a default implementation in python.

rocon_app_platform: rocon_app_manager | rocon_app_utilities | rocon_apps

Package Summary

Robot application platform for ros robots with a default implementation in python.

rocon_app_platform: rocon_app_manager | rocon_app_utilities | rocon_apps

Package Summary

Robot application platform for ros robots with a default implementation in python.

The Appable Robot

About

Robots in the scenarios and contexts that we often deploy (real world scenarios) are often just another kind of person. It goes to work, will sometimes work within a team and sometimes autonomously. In almost all of these situations, the work is task driven and this is the focus we wanted for interaction with the robots. It is familiar and a natural extension of the way we think and approach tasks as a human.

The hard part of a task driven approach is to step back and let the robot do the task to the best of its ability without trying to interfere with their autonomy as much as possible. This is a difficult balance, but without this in mind, higher level orchestration can quickly become overly complex.

So if a robot is taskable, it should almost certainly in many cases be retaskable to maximise its potential. Multitasking would be nice, but is a pandora's box of problems to open. To enable our retaskable robots, we iterated on the robot app platform initially instigated by Ken and others at Willow as it was a convenient fit. This is less about 'apps' than it is about providing a very convenient way to deploy, start, stop and manage your robot in a task driven way.

The appable robot is intended to be a complete framework intended to simplify:

and provide useful means of interacting with the robot over the public interface via two different modes:

Capabilities

Capabilities are a means of providing an abstraction layer at the bootstrap level. This makes writing robot agnostic "apps" easier. If a robot can declare that it implements the standardized interface for the navigation capability, then an app can rely on the the ROS interface used to utilize that capability. A more detailed explanation of what capabilities are about and the api documentation can be found on the capabilities wiki page.

  1. Capabilities Demo

    Demonstrating the capabilities of the capability server.

.

Rapps

Applications that utilise and run on top of both capabilities and some bootstrap layer for the robot we refer to as rapps (aka rocon apps, or robot apps - to be easily distinguishable from mobile phone apps). These are essentially launchers with no code. Where capabilities are designed to reflect some sub-functionality of the robot that can be run in parallel with their own conflict management, rapps should represent the launch environment and its configuration for the robot's current activity, or task, e.g. beer delivery. Given this conceptual constraint, only one rapp should ever be running on a robot at one time.

This decision was made primarily to simplify the way the robot interacts at a higher level. Just like humans in a team, our robots in a higher level framework (such as the concert which we introduce later) are designed to be retaskable resources. For the appable robot, this means stopping and starting the appropriate rapp. This lets us tune configuration of launched software or rerun entirely different software as needed. This is especially important on robots which do not have the computational capacity of a pr2.

Specifications

Tutorials

  1. Standalone App Manager

    Launching and running a standalone app manager with no connections to the outside world.

  2. Pairing Mode

    Launching the robot app manager for pairing through a public master.

  3. Pairing with Androids

    Pairing the robot app manager with android smart phones/tablets.

  4. Customising - Robot Icon

    How to add a custom robot icon to represent your robot in remote applications.

  5. Create a Robot App

    How to create and install a robot application (rapp) for pairing or concert modes.

  6. Create an Android App

    How to create an android app for robot-android pairing.

Beginners Tutorials

Make Your Robot Appable

  1. Install Rocon App Manager

    Installing the rocon_app_platform environment.

  2. Configure Rapp Manager for Robot

    describes how to setup rapp manager for the robot

  3. Bring up Rapp Manager

    describes what happens when you start rapp manager.

  4. Start Rapp via QT Rapp Manager

    shows starting rapps via rocon_qt_app_manager

Rocon URI

  1. Add Your Robot Type

    how to add your own robot type in rocon_uri rule.

  2. Make Your Robot Type Official

    how to add your own robot type in rocon_uri official rule.

Pairing Mode

  1. Pairing

    Launching rapps in tandem with rocon interactions.

  2. Run Interactions with QT Remocon

    shows start interactions via rqt remocon

  3. Run Interactions with Android Remocon

    shows start interactions via android remocon

  4. Run Interactions with Web Remocon

    shows start interactions via web remocon

Android pairing is a common configuration (also used by the TurtleBot). The android pairing tutorials are best viewed within the entire context of the android tutorials.

Intermediate Tutorials

Rocon App Utilities

  1. Introspect Rapps

    How to use the rapp tools

  2. Create a Robot App

    How to create and install a robot application (rapp) for pairing or concert modes.

  3. Troubleshooting Rapps

    How to troubleshooting an invalid rapp

Interactions

  1. Getting Started

    A walkthrough of the rocon interactions concepts.

  2. Documentation Interactions

    Defining interactions pointing to documentation on the web.

  3. Qt Interactions

    Defining interactions for qt based frontends.

  4. Rviz Interactions

    Defining interactions for rviz configurations.

  5. Web App Interactions

    Defining interactions for web apps.

  6. Android Interactions

    Defining interactions that can launch android activities.

Advanced Tutorials

Capabilities

TODO

  1. No Title

    No Description

Rapp Indexer

  1. Create a Rapp Index

    How to create a Rapp index

  2. Install Rapps

    How to install rapp from rapp index

  3. Start Rapp From Indexer

    Enable to app manager to automatically install rapps

Appendix

Reference Robot


2019-08-17 13:09