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.0
License BSD 3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

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

Package Description

This package contains a device-independent bringup utilities for qbrobotics® devices.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

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

Changelog for package qb_device_bringup

2.1.0 (2019-05-28)

  • Improve inheritance for other devices
  • Update documentation
  • Add a simulator mode to debug joint trajectories
  • Add specific joint limits for the delta
  • Add interactive markers startup activation
  • Fix set/reset use_waypoints at each launch

2.0.3 (2018-08-09)

2.0.2 (2018-08-07)

2.0.1 (2018-06-01)

2.0.0 (2018-05-30)

  • Refactor launch files
  • Fix minors
  • Add a blocking setCommands method
  • Fix until ros_comm#889 is fixed
  • Refactor launch files and fix controllers spawner

1.2.2 (2017-11-30)

  • Fix launch file

1.1.0 (2017-11-24)

  • Fix control nodes type

1.0.8 (2017-06-27)

1.0.7 (2017-06-26)

1.0.6 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.5 (2017-06-22)

1.0.4 (2017-06-21)

1.0.3 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.2 (2017-06-20)

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/robot_bringup.launch
      • get_positions — Fake arg: ros_comm#889
      • standalone — Fake arg: ros_comm#889
      • max_repeats — Fake arg: ros_comm#889
      • activate_on_initialization — Fake arg: ros_comm#889
      • device_id — Fake arg: ros_comm#889
      • rescan_on_initialization — Fake arg: ros_comm#889
      • set_commands — Fake arg: ros_comm#889
      • set_commands_async — Fake arg: ros_comm#889
      • device_type — Fake arg: ros_comm#889
      • get_currents — Fake arg: ros_comm#889
      • get_distinct_packages — Fake arg: ros_comm#889
      • use_simulator_mode — Fake arg: ros_comm#889
      • device_name [default: ] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [$(arg device_name)/joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: true] — 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.
  • launch/robot_opt_bringup.launch
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_interactive_markers [default: false] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
  • launch/robot_control_node_bringup.launch
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • standalone — Fake arg: ros_comm#889
      • use_controller_gui — Fake arg: ros_comm#889
      • robot_package — Fake arg: ros_comm#889
      • use_waypoints — Fake arg: ros_comm#889
      • use_rviz — Fake arg: ros_comm#889
      • use_interactive_markers [default: Fake arg: ros_comm#889]
      • source_list — Fake arg: ros_comm#889
      • control_duration — Fake arg: ros_comm#889
      • robot_hardware — Fake arg: ros_comm#889
      • device_id — The ID of the device [1, 128].
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
      • 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: false] — 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: false] — 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.
      • use_simulator_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • has_delta_motor_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • has_gripper_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
  • launch/device_controllers_bringup.launch
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
  • launch/robot_description_bringup.launch
      • device_name [default: ] — The unique device name used in the urdf configurations (if not specified directly in the urdf).
      • frequency [default: 100] — The frequency of the two state publishers.
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_rviz [default: true] — Choose whether or not to use rviz.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at answers.ros.org

Package Summary

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

Repository Summary

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

Package Description

This package contains a device-independent bringup utilities for qbrobotics® devices.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

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

Changelog for package qb_device_bringup

2.1.0 (2019-05-28)

  • Improve inheritance for other devices
  • Update documentation
  • Add a simulator mode to debug joint trajectories
  • Add specific joint limits for the delta
  • Add interactive markers startup activation
  • Fix set/reset use_waypoints at each launch

2.0.3 (2018-08-09)

2.0.2 (2018-08-07)

2.0.1 (2018-06-01)

2.0.0 (2018-05-30)

  • Refactor launch files
  • Fix minors
  • Add a blocking setCommands method
  • Fix until ros_comm#889 is fixed
  • Refactor launch files and fix controllers spawner

1.2.2 (2017-11-30)

  • Fix launch file

1.1.0 (2017-11-24)

  • Fix control nodes type

1.0.8 (2017-06-27)

1.0.7 (2017-06-26)

1.0.6 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.5 (2017-06-22)

1.0.4 (2017-06-21)

1.0.3 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.2 (2017-06-20)

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/robot_bringup.launch
      • get_positions — Fake arg: ros_comm#889
      • standalone — Fake arg: ros_comm#889
      • max_repeats — Fake arg: ros_comm#889
      • activate_on_initialization — Fake arg: ros_comm#889
      • device_id — Fake arg: ros_comm#889
      • rescan_on_initialization — Fake arg: ros_comm#889
      • set_commands — Fake arg: ros_comm#889
      • set_commands_async — Fake arg: ros_comm#889
      • device_type — Fake arg: ros_comm#889
      • get_currents — Fake arg: ros_comm#889
      • get_distinct_packages — Fake arg: ros_comm#889
      • use_simulator_mode — Fake arg: ros_comm#889
      • device_name [default: ] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [$(arg device_name)/joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: true] — 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.
  • launch/robot_opt_bringup.launch
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_interactive_markers [default: false] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
  • launch/robot_control_node_bringup.launch
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • standalone — Fake arg: ros_comm#889
      • use_controller_gui — Fake arg: ros_comm#889
      • robot_package — Fake arg: ros_comm#889
      • use_waypoints — Fake arg: ros_comm#889
      • use_rviz — Fake arg: ros_comm#889
      • use_interactive_markers [default: Fake arg: ros_comm#889]
      • source_list — Fake arg: ros_comm#889
      • control_duration — Fake arg: ros_comm#889
      • robot_hardware — Fake arg: ros_comm#889
      • device_id — The ID of the device [1, 128].
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
      • 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: false] — 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: false] — 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.
      • use_simulator_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • has_delta_motor_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • has_gripper_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
  • launch/device_controllers_bringup.launch
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
  • launch/robot_description_bringup.launch
      • device_name [default: ] — The unique device name used in the urdf configurations (if not specified directly in the urdf).
      • frequency [default: 100] — The frequency of the two state publishers.
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_rviz [default: true] — Choose whether or not to use rviz.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at answers.ros.org

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

Package Summary

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

Repository Summary

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

Package Description

This package contains a device-independent bringup utilities for qbrobotics® devices.

Additional Links

Maintainers

  • Alessandro Tondo

Authors

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

Changelog for package qb_device_bringup

2.1.0 (2019-05-28)

  • Improve inheritance for other devices
  • Update documentation
  • Add a simulator mode to debug joint trajectories
  • Add specific joint limits for the delta
  • Add interactive markers startup activation
  • Fix set/reset use_waypoints at each launch

2.0.3 (2018-08-09)

2.0.2 (2018-08-07)

2.0.1 (2018-06-01)

2.0.0 (2018-05-30)

  • Refactor launch files
  • Fix minors
  • Add a blocking setCommands method
  • Fix until ros_comm#889 is fixed
  • Refactor launch files and fix controllers spawner

1.2.2 (2017-11-30)

  • Fix launch file

1.1.0 (2017-11-24)

  • Fix control nodes type

1.0.8 (2017-06-27)

1.0.7 (2017-06-26)

1.0.6 (2017-06-23)

  • Update cmake version to match Kinetic standards

1.0.5 (2017-06-22)

1.0.4 (2017-06-21)

1.0.3 (2017-06-21)

  • fix cmake settings to solve isolated builds

1.0.2 (2017-06-20)

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/robot_bringup.launch
      • get_positions — Fake arg: ros_comm#889
      • standalone — Fake arg: ros_comm#889
      • max_repeats — Fake arg: ros_comm#889
      • activate_on_initialization — Fake arg: ros_comm#889
      • device_id — Fake arg: ros_comm#889
      • rescan_on_initialization — Fake arg: ros_comm#889
      • set_commands — Fake arg: ros_comm#889
      • set_commands_async — Fake arg: ros_comm#889
      • device_type — Fake arg: ros_comm#889
      • get_currents — Fake arg: ros_comm#889
      • get_distinct_packages — Fake arg: ros_comm#889
      • use_simulator_mode — Fake arg: ros_comm#889
      • device_name [default: ] — The unique device name used in the yaml controller configurations (also in the urdf if not already specified there).
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [$(arg device_name)/joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_rviz [default: true] — 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.
  • launch/robot_opt_bringup.launch
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • use_controller_gui [default: false] — Choose whether or not to use the controller GUI.
      • use_interactive_markers [default: false] — Choose whether or not to use interactive markers on rviz.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
  • launch/robot_control_node_bringup.launch
      • control_duration [default: 0.01] — The duration of the control loop [s].
      • robot_hardware — The robot hardware interface names, e.g. [device1, device2, ...].
      • robot_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • standalone — Fake arg: ros_comm#889
      • use_controller_gui — Fake arg: ros_comm#889
      • robot_package — Fake arg: ros_comm#889
      • use_waypoints — Fake arg: ros_comm#889
      • use_rviz — Fake arg: ros_comm#889
      • use_interactive_markers [default: Fake arg: ros_comm#889]
      • source_list — Fake arg: ros_comm#889
      • control_duration — Fake arg: ros_comm#889
      • robot_hardware — Fake arg: ros_comm#889
      • device_id — The ID of the device [1, 128].
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
      • 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: false] — 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: false] — 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.
      • use_simulator_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • has_delta_motor_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • has_gripper_position_limits [default: false] — Choose whether or not to use custom joint limits, e.g. for delta motors.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
  • launch/device_controllers_bringup.launch
      • device_name — The unique device name used in the yaml controller configurations.
      • device_type — The type of the device [qbhand, qbmove, ...].
  • launch/robot_description_bringup.launch
      • device_name [default: ] — The unique device name used in the urdf configurations (if not specified directly in the urdf).
      • frequency [default: 100] — The frequency of the two state publishers.
      • robot_name — The unique robot name.
      • robot_package — The base package name prefix for the robot configurations [urdf, rviz, ...].
      • source_list [default: [joint_states]] — The joint_states source list for the joint_state_publisher.
      • use_rviz [default: true] — Choose whether or not to use rviz.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at answers.ros.org

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.