The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Personally I would analyse what the functionality is the SDK offers and then try to map that to well-know ROS interfaces. Example: Spot probably offers an interface which allows you to command it to walk with a certain velocity. If that would also include a direction, this would probably map to a regular geometry_msgs/Twist interface, which would be the standard interface for a "mobile platform".
As Spot is a quadruped, you could perhaps take a look at other quadrupeds with ROS compatibility/interfaces. One example would be ANYmal. You may find their Github organisation at github/ANYbotics.
For an overview of the architecture of its software, you could refer to the presentation one of their engineers gave at ROSCon 2016: ANYmal at the ARGOS Challenge: Tools and Experiences from the Autonomous Inspection of Oil & Gas Sites with a Legged Robot (video, slides).
You would not need to implement all of those pieces of course, as Spot comes with quite a large part of that "built-in", but it would give you an idea of the ROS API that your wrappers could provide on-top of Spot's SDK.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
