dingo_desktop: dingo_msgs | dingo_viz
Package Summary
Released
Documented
Messages exclusive to Dingo, especially for representing low-level motor commands and sensors.
- Maintainer status: developed
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>, Jason Higgins <jhiggins AT clearpathrobotics DOT com>
- Author: Jason Higgins <jhiggins AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/dingo-cpr/dingo.git (branch: melodic-devel)
dingo_desktop: dingo_msgs | dingo_viz
Package Summary
Released
Documented
Messages exclusive to Dingo, especially for representing low-level motor commands and sensors.
- Maintainer status: maintained
- Maintainer: Tony Baltovski <tbaltovski AT clearpathrobotics DOT com>, Jason Higgins <jhiggins AT clearpathrobotics DOT com>
- Author: Jason Higgins <jhiggins AT clearpathrobotics DOT com>
- License: BSD
- Source: git https://github.com/dingo-cpr/dingo.git (branch: melodic-devel)
ROS Message Types
Notes
These messages are the low-level interface between Dingo's MCU and integrated PC. Most users of Dingo 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.