Show EOL distros:
Package Summary
Messages exclusive to Warthog, especially for representing low-level motor commands and sensors.
- Maintainer status: developed
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>
- Author: Ryan Gariepy <rgariepy AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/warthog-cpr/warthog.git (branch: indigo-devel)
Package Summary
Messages exclusive to Warthog, especially for representing low-level motor commands and sensors.
- Maintainer status: maintained
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>
- Author: Ryan Gariepy <rgariepy AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/warthog-cpr/warthog.git (branch: kinetic-devel)
Package Summary
Messages exclusive to Warthog, especially for representing low-level motor commands and sensors.
- Maintainer status: maintained
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>
- Author: Ryan Gariepy <rgariepy AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/warthog-cpr/warthog.git (branch: kinetic-devel)
warthog_desktop: warthog_msgs | warthog_viz
Package Summary
Messages exclusive to Warthog, especially for representing low-level motor commands and sensors.
- Maintainer status: maintained
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>
- Author: Ryan Gariepy <rgariepy AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/warthog-cpr/warthog.git (branch: kinetic-devel)
Newly proposed, mistyped, or obsolete package. Could not find package "warthog_msgs" in rosdoc: /var/www/docs.ros.org/en/api/warthog_msgs/manifest.yaml
Notes
These messages are the low-level interface between Warthog's ARM MCU and integrated PC. Most users of Warthog should be able to use standard ROS interfaces (eg. geometry_msgs/Twist, diagnostics) to command and monitor the robot. Possible exceptions are:
If you wish to disable diff_drive_controller and command the motors directly to the MCU.
- To programmatically monitor system state such as voltage, current, battery, faults, etc.
