No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 2.1.2
License BSD 3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://bitbucket.org/qbrobotics/qbmove-ros.git
VCS Type git
VCS Version production-melodic
Last Updated 2019-06-11
Dev Status DEVELOPED
Released RELEASED

Package Description

This package contains the ROS control node for qbrobotics® qbmove device.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

  • qbrobotics®
README
No README found. See repository README.
CHANGELOG

Changelog for package qb_move_control

2.1.2 (2019-06-11)

2.1.1 (2019-06-11)

2.1.0 (2019-05-28)

  • Add an interactive marker to control the device
  • Fix minor style issues

2.0.2 (2018-08-09)

2.0.1 (2018-08-07)

  • Set safer default values

2.0.0 (2018-05-30)

  • Update README
  • Refactor launch files
  • Remove control node
  • Add blocking setCommands method support
  • Refactor launch files
  • Fix destructor calls on ROS shutdown

1.0.6 (2017-11-24)

1.0.5 (2017-06-27)

  • Fix C++11 support for cmake version less than 3.1

1.0.4 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.3 (2017-06-22)

  • fix dependencies

1.0.2 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.1 (2017-06-19)

  • first public release for Kinetic

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

Deps Name
1 catkin

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/control.launch
      • device_id [default: 1] — The ID of the device [1, 128].
      • device_name [default: $(arg device_type)$(arg device_id)] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.001] — The duration of the control loop [s].
      • robot_hardware [default: [$(arg device_name)]] — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name [default: $(arg device_type)] — The unique robot name.
      • robot_namespace [default: $(arg device_name)] — The unique robot namespace.
      • robot_package [default: qb_move] — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [control/joint_states]] — The joint_states source list for the joint_state_publisher.
      • get_currents [default: true] — Choose whether or not to retrieve current measurements from the device.
      • get_positions [default: true] — Choose whether or not to retrieve position measurements from the device.
      • get_distinct_packages [default: true] — Choose whether or not to retrieve current and position measurements from the device in two distinct packages.
      • max_repeats [default: 3] — The maximum number of consecutive repetitions to mark retrieved data as corrupted.
      • set_commands [default: true] — Choose whether or not to send command positions to the device.
      • set_commands_async [default: true] — Choose whether or not to send commands without waiting for ack.
      • activate_on_initialization [default: false] — Choose whether or not to activate the motors on node startup.
      • rescan_on_initialization [default: false] — Choose whether or not to rescan the serial ports on node startup.
      • standalone [default: false] — Choose whether or not to start the Communication Handler.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: false] — Choose whether or not to use rviz.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_move_control at answers.ros.org

Package Summary

Tags No category tags.
Version 2.1.2
License BSD 3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://bitbucket.org/qbrobotics/qbmove-ros.git
VCS Type git
VCS Version production-lunar
Last Updated 2019-06-11
Dev Status DEVELOPED
Released RELEASED

Package Description

This package contains the ROS control node for qbrobotics® qbmove device.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

  • qbrobotics®
README
No README found. See repository README.
CHANGELOG

Changelog for package qb_move_control

2.1.2 (2019-06-11)

2.1.1 (2019-06-11)

2.1.0 (2019-05-28)

  • Add an interactive marker to control the device
  • Fix minor style issues

2.0.2 (2018-08-09)

2.0.1 (2018-08-07)

  • Set safer default values

2.0.0 (2018-05-30)

  • Update README
  • Refactor launch files
  • Remove control node
  • Add blocking setCommands method support
  • Refactor launch files
  • Fix destructor calls on ROS shutdown

1.0.6 (2017-11-24)

1.0.5 (2017-06-27)

  • Fix C++11 support for cmake version less than 3.1

1.0.4 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.3 (2017-06-22)

  • fix dependencies

1.0.2 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.1 (2017-06-19)

  • first public release for Kinetic

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

Deps Name
1 catkin

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/control.launch
      • device_id [default: 1] — The ID of the device [1, 128].
      • device_name [default: $(arg device_type)$(arg device_id)] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.001] — The duration of the control loop [s].
      • robot_hardware [default: [$(arg device_name)]] — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name [default: $(arg device_type)] — The unique robot name.
      • robot_namespace [default: $(arg device_name)] — The unique robot namespace.
      • robot_package [default: qb_move] — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [control/joint_states]] — The joint_states source list for the joint_state_publisher.
      • get_currents [default: true] — Choose whether or not to retrieve current measurements from the device.
      • get_positions [default: true] — Choose whether or not to retrieve position measurements from the device.
      • get_distinct_packages [default: true] — Choose whether or not to retrieve current and position measurements from the device in two distinct packages.
      • max_repeats [default: 3] — The maximum number of consecutive repetitions to mark retrieved data as corrupted.
      • set_commands [default: true] — Choose whether or not to send command positions to the device.
      • set_commands_async [default: true] — Choose whether or not to send commands without waiting for ack.
      • activate_on_initialization [default: false] — Choose whether or not to activate the motors on node startup.
      • rescan_on_initialization [default: false] — Choose whether or not to rescan the serial ports on node startup.
      • standalone [default: false] — Choose whether or not to start the Communication Handler.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: false] — Choose whether or not to use rviz.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_move_control at answers.ros.org

Package Summary

Tags No category tags.
Version 2.1.2
License BSD 3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://bitbucket.org/qbrobotics/qbmove-ros.git
VCS Type git
VCS Version production-kinetic
Last Updated 2019-06-11
Dev Status DEVELOPED
Released RELEASED

Package Description

This package contains the ROS control node for qbrobotics® qbmove device.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

  • qbrobotics®
README
No README found. See repository README.
CHANGELOG

Changelog for package qb_move_control

2.1.2 (2019-06-11)

2.1.1 (2019-06-11)

2.1.0 (2019-05-28)

  • Add an interactive marker to control the device
  • Fix minor style issues

2.0.2 (2018-08-09)

2.0.1 (2018-08-07)

  • Set safer default values

2.0.0 (2018-05-30)

  • Update README
  • Refactor launch files
  • Remove control node
  • Add blocking setCommands method support
  • Refactor launch files
  • Fix destructor calls on ROS shutdown

1.0.6 (2017-11-24)

1.0.5 (2017-06-27)

  • Fix C++11 support for cmake version less than 3.1

1.0.4 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.3 (2017-06-22)

  • fix dependencies

1.0.2 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.1 (2017-06-19)

  • first public release for Kinetic

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

Deps Name
1 catkin

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/control.launch
      • device_id [default: 1] — The ID of the device [1, 128].
      • device_name [default: $(arg device_type)$(arg device_id)] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.001] — The duration of the control loop [s].
      • robot_hardware [default: [$(arg device_name)]] — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name [default: $(arg device_type)] — The unique robot name.
      • robot_namespace [default: $(arg device_name)] — The unique robot namespace.
      • robot_package [default: qb_move] — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [control/joint_states]] — The joint_states source list for the joint_state_publisher.
      • get_currents [default: true] — Choose whether or not to retrieve current measurements from the device.
      • get_positions [default: true] — Choose whether or not to retrieve position measurements from the device.
      • get_distinct_packages [default: true] — Choose whether or not to retrieve current and position measurements from the device in two distinct packages.
      • max_repeats [default: 3] — The maximum number of consecutive repetitions to mark retrieved data as corrupted.
      • set_commands [default: true] — Choose whether or not to send command positions to the device.
      • set_commands_async [default: true] — Choose whether or not to send commands without waiting for ack.
      • activate_on_initialization [default: false] — Choose whether or not to activate the motors on node startup.
      • rescan_on_initialization [default: false] — Choose whether or not to rescan the serial ports on node startup.
      • standalone [default: false] — Choose whether or not to start the Communication Handler.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: false] — Choose whether or not to use rviz.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_move_control at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.