Documentation Status

Cannot load information on name: qb_move_control, distro: electric, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: fuerte, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: groovy, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: hydro, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: indigo, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: jade, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: kinetic, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: qb_move_control, distro: lunar, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.

This package contains the ROS control node and its structures to control the qbroboticsĀ® qbmove device. It exploits the features provided by the base device-independent control library (cf. qb_device_control) and the specific hardware interface (cf. qb_move_hardware_interface).

Launch files

The two launch files start a ROS node for the qbmove respectively to control it through a GUI and through predefined configurable waypoints (stored in the config/qbmove_waypoints.yaml). In both cases the controllers setup can be found in the config/qbmove_controllers.yaml; it is recommended not to change the default settings though.

gui_control

This launch file calls the template qb_device_bringup#full_bringup with the default settings to bringup a full control node for the qbmove based on GUI inputs. It also starts the Communication Handler and therefore it is recommended not to start other driver nodes while using this one (cf. qb_multi_device to control several devices together).

waypoint_control

This launch file calls the template qb_device_bringup#full_bringup with the default settings to bringup a full control node for the qbmove based on waypoint inputs. It also starts the Communication Handler and therefore it is recommended not to start other driver nodes while using this one (cf. qb_multi_device to control several devices together).

Nodes and API

qb_move_control

This control library specifically designed for the qbmoveextends the qb_device_control and exploits the qb_move_hardware_interface, therefore it provides all the ROS resources and requires all the specifications of this two base packages.

Wiki: qb_move_control (last edited 2017-03-15 14:42:28 by AlessandroTondo)