[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

stdr_simulator: stdr_gui | stdr_launchers | stdr_msgs | stdr_parser | stdr_resources | stdr_robot | stdr_samples | stdr_server

Package Summary

Provides robot, sensor implementation, using nodelets for stdr_server to load them.

stdr_simulator: stdr_gui | stdr_launchers | stdr_msgs | stdr_parser | stdr_resources | stdr_robot | stdr_samples | stdr_server

Package Summary

Provides robot, sensor implementation, using nodelets for stdr_server to load them.

stdr_simulator: stdr_gui | stdr_launchers | stdr_msgs | stdr_parser | stdr_resources | stdr_robot | stdr_samples | stdr_server

Package Summary

Provides robot, sensor implementation, using nodelets for stdr_server to load them.

stdr_simulator: stdr_gui | stdr_launchers | stdr_msgs | stdr_parser | stdr_resources | stdr_robot | stdr_samples | stdr_server

Package Summary

Provides robot, sensor implementation, using nodelets for stdr_server to load them.

Overview

The stdr_robot package implements a simulated robot, all simulated sensors and its simulated motion controller. Till now the following sensors are implemented:

Available motion controllers:

The robot class is available using the nodelet interface, named stdr_robot/Robot. To load a new robot a STDR Server has to be running. New robots/nodelets can be loaded only from stdr_server, using either stdr_gui or command-line tools described below.

A parser for YAML and XML files is also provided, to load or save robots, sensors etc. More details on how to use YAML and XML files with stdr_simulator here.

Tf frames

A robot provides tf transforms for the pose of itself and its sensors. All transforms are relative to map_static frame. For more details about map tf frames see STDR Server tf frames. An example with one spawned robot follows (using rqt_tf_tree):

alt text

Sensor transforms

The frame_id for each sensor is defined on loading a robot from GUI or when using a YAML/XML file to describe a sensor. Each sensor frame_id has to have a unique name per robot. To avoid naming collisions with other robots it is also (automatically) prefixed with robot's name. Example: robot0_laser_1.

Robot transform

Each robot provides a tf transform with its current pose. The frame_id is automatically assigned and has the format robot<ID>. Example: robot2.

Topics

All topic names are prefixed with robot name. Example robot1/cmd_vel.

Subscribed Topics

cmd_vel (geometry_msgs/Twist)

Published Topics

<laser_sensor_frame_id> (sensor_msgs/LaserScan)

<sonar_sensor_frame_id> (sensor_msgs/Range)

Services

All services are prefixed with the name robot_manager. This is the name of the nodelet manager and should not change.

load_nodelet (nodelet/NodeletLoad)

unload_nodelet (nodelet/NodeletUnload)

Command-Line Tools

robot_handler

With the robot_handler command-line tool you can add, delete and move a robot directly from the terminal. The following sections describe the available commands.

robot_handler add

robot_handler delete

robot_handler replace

Tutorials

For tutorials see stdr_simulator/Tutorials.


2019-10-12 13:10