Skip to content

Conversation

@ggoretkin-bdai
Copy link
Collaborator

@ggoretkin-bdai ggoretkin-bdai commented Mar 22, 2024

Change Overview

We would like to trigger a lease release, so that the tablet can then control the robot without needing to "hijack", but the existing "release" service also combines both the Lease and EStop release. This provides a service that leaves the EStop alone.

Testing Done

  • power on Spot from the tablet
  • start the driver
  • ros2 service call /Spot/stand std_srvs/srv/Trigger
  • observe the tablet no longer has control ("hijack" button appears)
  • ros2 service call /Spot/lease/release std_srvs/srv/Trigger

the driver then crashes :( The robot goes to sit down, but stops midway and tablet control resumes

[spot_ros2-1] [INFO] [1711148477.849324824] [Nyla.spot_ros2]: Starting ROS driver for Spot for Nyla
[spot_ros2-1] [INFO] [1711148480.749066212] [Nyla.spot_ros2]: Found estop!
[spot_ros2-1] [INFO] [1711148480.954829316] [Nyla.spot_ros2]: Driver successfully started!

[spot_ros2-1] [INFO] [1711148509.073868606] [Nyla.spot_ros2]: Shutting down ROS driver for Spot
[spot_ros2-1] [wrapper.py:1037] Unable to execute robot command: No lease for resource "body"

@ggoretkin-bdai
Copy link
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ggoretkin-bdai and the rest of your teammates on Graphite Graphite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants