Skip to content
This repository was archived by the owner on Jun 11, 2026. It is now read-only.
This repository was archived by the owner on Jun 11, 2026. It is now read-only.

[Design] wrapper bypasses estop system completely. #12

Description

@mklingen-bd

with bosdyn.client.lease.LeaseKeepAlive(self.lease_client), bosdyn.client.estop.EstopKeepAlive(

The estop system was designed so that multiple devices (tablet, laptop, web interface, etc.) could become an authoratative emergency stop source, and stop the robot when triggered or when comms to the robot was lost. The ROS wrapper automatically acquires the estop and keeps it alive, negating this purpose.

This is another design question, because estops are not a ROS concept. The estop service could be made into it's own ROS service, or a 3rdparty estop system could be used in conjunction with ROS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions