Documentation Status

schunk_modular_robotics: schunk_description | schunk_libm5api | schunk_powercube_chain | schunk_sdh | schunk_simulated_tactile_sensors

Package Summary

Documented

This packages provides a configurable driver of a chain of Schunk powercubes. The powercube chain is configured through parameters. Most users will not directly interact with this package but with the corresponding launch files in other packages, e.g. schunk_bringup, cob_bringup, ...

schunk_modular_robotics: schunk_description | schunk_libm5api | schunk_powercube_chain | schunk_sdh | schunk_simulated_tactile_sensors

Package Summary

Documented

This packages provides a configurable driver of a chain of Schunk powercubes. The powercube chain is configured through parameters. Most users will not directly interact with this package but with the corresponding launch files in other packages, e.g. schunk_bringup, cob_bringup, ...

schunk_modular_robotics: schunk_description | schunk_libm5api | schunk_powercube_chain | schunk_sdh | schunk_simulated_tactile_sensors

Package Summary

Documented

This packages provides a configurable driver of a chain of Schunk powercubes. The powercube chain is configured through parameters. Most users will not directly interact with this package but with the corresponding launch files in other packages, e.g. schunk_bringup, cob_bringup, ...

schunk_modular_robotics: schunk_description | schunk_libm5api | schunk_powercube_chain | schunk_sdh | schunk_simulated_tactile_sensors

Package Summary

Released Continuous integration Documented

This packages provides a configurable driver of a chain of Schunk powercubes. The powercube chain is configured through parameters. Most users will not directly interact with this package but with the corresponding launch files in other packages, e.g. schunk_bringup, cob_bringup, ...

Cannot load information on name: schunk_powercube_chain, 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: schunk_powercube_chain, 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.

Hardware Requirements

To use this package you need one or more powercubes www.schunk-modular-robotics.com. Alternatively you can use a simulated version without any hardware, see schunk_bringup_sim.

Software Requirements

The installation is tested for Ubuntu 10.04, 10.10, 11.04 and 11.10 using ROS electric. If you discover problems installing them on other platforms, please tell us.

ROS API

The schunk_powercube_chain package provides a configurable node for operating a chain of powercube modules.

schunk_powercube_chain

The schunk_powercube_chain node takes in brics_actuator/JointVelocities messages and sends this directly to the hardware. The chain can be initialized, stopped or recovered via services.

Subscribed Topics

command_vel (brics_actuator/JointVelocities)
  • Receives velocity commands.

Published Topics

/joint_states (sensor_msgs/JointState)
  • Joint state information for all modules in chain.
state (pr2_controllers_msgs/JointTrajectoryControllerState)
  • Controller state information for all modules in chain.
current_operationmode (std_msgs/String)
  • Current operation mode for chain.
/diagnostics (diagnostic_msgs/DiagnosticArray)
  • Diagnostics information about chain.

Services

init (cob_srvs/Trigger)
  • Initializes the node and connects to the hardware.
stop (cob_srvs/Trigger)
  • Stops immediately all hardware movements.
recover (cob_srvs/Trigger)
  • Recovers the hardware after an emergency stop.
set_operation_mode (cob_srvs/SetOperationMode)
  • Sets the operation mode for the node.

Parameters

can_module (string, default: Required)
  • Can module specifier, e.g. PCAN, ESD
can_device (string, default: Required)
  • Device address of can module, e.g. /dev/can0, /dev/pcan2,...
can_baudrate (int, default: Required)
  • Baudrate of can module, e.g. 1000, 500,...
module_ids (list of ints, default: Required)
  • Modul IDs of the powercubes, e.g. [10,11,12,13,...]
force_use_movevel (bool)
  • Forces using the M5API moveVel command instead of moveStep.
joint_names (list of strings, default: Required)
  • List of joint names corresponding to urdf description, e.g. [arm_1_joint, arm_2_joint, arm_3_joint,...]
max_accelerations (list of doubles, default: Required)
  • List of maximal accelerations for the modules in rad/sec^2, e.g. [0.8,0.8,0.8,...]
/robot_description (urdf model, default: Required)
  • Urdf model of the robot, including the joints and links describing the chain of powercubes
frequency (double)
  • Controller frequency.
min_publish_duration (double)
  • Minimum duration of publishing joint states if no command is received, otherwise for each received command one joint state message is published.

Usage/Examples

This package is not intended to be used directly, but with the corresponding launch and yaml files from e.g. schunk_bringup in the schunk_robots stack. For starting only the lwa use

roslaunch schunk_bringup lwa_solo.launch

For including the lwa in your overall launch file use

<include file="$(find schunk_bringup)/components/lwa.launch" />

All hardware configuration is done in the schunk_hardware_config package. A sample parameter file in "schunk_hardware_config/lwa/config/lwa.yaml" could look like this

can_module: PCAN
can_device: /dev/pcan1
can_baudrate: 1000
modul_ids: [1,2,3,4,5,6,7]
joint_names: [arm_1_joint, arm_2_joint, arm_3_joint, arm_4_joint, arm_5_joint, arm_6_joint, arm_7_joint]
max_accelerations: [0.8,0.8,0.8,0.8,0.8,0.8,0.8]
frequency: 68
OperationMode: position
ptp_vel: 0.4 # rad/sec
ptp_acc: 0.1 # rad/sec^2
max_error: 0.2 # rad

Wiki: schunk_powercube_chain (last edited 2012-08-22 07:03:02 by FlorianWeisshardt)