Package Summary

Tags No category tags.
Version 3.0.6
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 2023-04-26
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

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

Additional Links

Maintainers

  • qb Support Team

Authors

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

Changelog for package qb_device_bringup

3.0.6 (2023-04-26)

  • FIX: gazebo entity name setted as device_name (not device type). This caused errors when devices gazebo nodes start
  • MINOR FIX: Changed the name of the package maintainer

3.0.5 (2022-09-07)

  • MINOR FIX: Changed cmake version required in all packages (current version 3.0.2).
  • Bug fixed when executing the waypoint movement and different controller with different number of controller joints are loaded.
  • Changed device controller bringup to load properly the device controller.

3.0.4 (2022-07-18)

3.0.3 (2022-07-15)

3.0.2 (2022-07-07)

3.0.1 (2022-07-06)

3.0.0 (2022-07-05)

  • Added loading motors control for SH2R

2.3.4 (2022-04-08)

2.3.3 (2022-04-08)

2.3.2 (2022-04-08)

2.3.1 (2022-04-08)

2.3.0 (2022-04-08)

  • BUG FIX when a generic qbrobotics device roslaunch is grouped in a namespace

2.2.1 (2021-08-27)

2.2.0 (2021-08-27)

  • Fixed reconnection on killing nodes.
  • Refactor control structures initialization
  • Add Gazebo SoftHand and SoftHand 2 Motors plugin skeletons
  • Refactor Gazebo plugin to prepare for SoftHand simulation
  • Add hardware interface for SoftHand 2 Motors
  • Set a better name for fake joint simulation variables
  • Added the control mode switch service. Added a parameter to choose to use .yaml limits or firmware ones.
  • Add Gazebo support for qbmove devices
  • Fix hardcoded params in launch files since ros_comm#1354 has been backported to kinetic
  • Fix \'pass_all_args\' workaround since ros_comm#889 has been backported to kinetic
  • Added compatibility to qb SoftClaw in .launch files
  • Update arg description
  • Added a parameter to use the device with or without other robots. Added some motor limits when the qbmoves are used in kinematic configs.

2.1.1 (2019-10-07)

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
      • 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_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
      • use_without_robot [default: true] — Choose whether or not to bring up robot description (e.g. when using with other robots is better to set it apart).
  • 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, qbclaw, ...].
      • robot_namespace — The unique robot namespace.
  • 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.
  • 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_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • 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_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • 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, qbclaw, ...].
      • 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_fake_measurement_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • use_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 2.2.1
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 2021-08-27
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

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.2.1 (2021-08-27)

2.2.0 (2021-08-27)

  • Fixed reconnection on killing nodes.
  • Refactor control structures initialization
  • Add Gazebo SoftHand and SoftHand 2 Motors plugin skeletons
  • Refactor Gazebo plugin to prepare for SoftHand simulation
  • Add hardware interface for SoftHand 2 Motors
  • Set a better name for fake joint simulation variables
  • Added the control mode switch service. Added a parameter to choose to use .yaml limits or firmware ones.
  • Add Gazebo support for qbmove devices
  • Fix hardcoded params in launch files since ros_comm#1354 has been backported to kinetic
  • Fix \'pass_all_args\' workaround since ros_comm#889 has been backported to kinetic
  • Added compatibility to qb SoftClaw in .launch files
  • Update arg description
  • Added a parameter to use the device with or without other robots. Added some motor limits when the qbmoves are used in kinematic configs.

2.1.1 (2019-10-07)

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
      • 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_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
      • use_without_robot [default: true] — Choose whether or not to bring up robot description (e.g. when using with other robots is better to set it apart).
  • 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, qbclaw, ...].
      • robot_namespace — The unique robot namespace.
  • 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.
  • 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_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • 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_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • 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, qbclaw, ...].
      • 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_fake_measurement_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • use_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 3.0.6
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 2023-04-26
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

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

Additional Links

Maintainers

  • qb Support Team

Authors

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

Changelog for package qb_device_bringup

3.0.6 (2023-04-26)

  • FIX: gazebo entity name setted as device_name (not device type). This caused errors when devices gazebo nodes start
  • MINOR FIX: Changed the name of the package maintainer

3.0.5 (2022-09-07)

  • MINOR FIX: Changed cmake version required in all packages (current version 3.0.2).
  • Bug fixed when executing the waypoint movement and different controller with different number of controller joints are loaded.
  • Changed device controller bringup to load properly the device controller.

3.0.4 (2022-07-18)

3.0.3 (2022-07-15)

3.0.2 (2022-07-07)

3.0.1 (2022-07-06)

3.0.0 (2022-07-05)

  • Added loading motors control for SH2R

2.3.4 (2022-04-08)

2.3.3 (2022-04-08)

2.3.2 (2022-04-08)

2.3.1 (2022-04-08)

2.3.0 (2022-04-08)

  • BUG FIX when a generic qbrobotics device roslaunch is grouped in a namespace

2.2.1 (2021-08-27)

2.2.0 (2021-08-27)

  • Fixed reconnection on killing nodes.
  • Refactor control structures initialization
  • Add Gazebo SoftHand and SoftHand 2 Motors plugin skeletons
  • Refactor Gazebo plugin to prepare for SoftHand simulation
  • Add hardware interface for SoftHand 2 Motors
  • Set a better name for fake joint simulation variables
  • Added the control mode switch service. Added a parameter to choose to use .yaml limits or firmware ones.
  • Add Gazebo support for qbmove devices
  • Fix hardcoded params in launch files since ros_comm#1354 has been backported to kinetic
  • Fix \'pass_all_args\' workaround since ros_comm#889 has been backported to kinetic
  • Added compatibility to qb SoftClaw in .launch files
  • Update arg description
  • Added a parameter to use the device with or without other robots. Added some motor limits when the qbmoves are used in kinematic configs.

2.1.1 (2019-10-07)

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
      • 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_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.
      • use_interactive_markers [default: $(arg use_rviz)] — Choose whether or not to use interactive markers on rviz.
      • use_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • use_waypoints [default: false] — Choose whether or not to use the waypoint references.
      • use_without_robot [default: true] — Choose whether or not to bring up robot description (e.g. when using with other robots is better to set it apart).
  • 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, qbclaw, ...].
      • robot_namespace — The unique robot namespace.
  • 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.
  • 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_joint_limits [default: false] — Choose whether or not to use the robot joint limits.
      • 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_activate_control [default: true] — Choose whether to activate robot_control or not (e.g. for sensor devices).
  • launch/device_bringup.launch
      • 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, qbclaw, ...].
      • 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_fake_measurement_mode [default: false] — Choose whether or not to use previous command values instead of device measurements.
      • robot_name — The unique robot name.
      • robot_namespace [default: $(arg robot_name)] — The unique robot namespace.
      • use_gazebo [default: false] — Choose whether or not to use Gazebo instead of real devices.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged qb_device_bringup at Robotics Stack Exchange