Telekinesis Agentic Skill Library

Appearance

Unlock Protective Stop ​

SUMMARY

Unlock Protective Stop sends an unlock command to the robot controller to clear a protective stop state and allow the robot to resume normal operation.

A protective stop is triggered automatically by the safety system — for example, after a joint limit violation, excessive force, or watchdog timeout. This skill clears that state programmatically, equivalent to pressing the "Unlock" button in the PolyScope interface.

SUPPORTED ROBOTS

This skill is currently supported on Universal Robots only. Calling this method on other robot brands will raise a NotImplementedError.

The Skill ​

python
robot.unlock_protective_stop()

The Code ​

Example: Unlock a Protective Stop ​

Connect to the robot and unlock the protective stop.

python
from loguru import logger
from telekinesis.synapse.robots.manipulators import universal_robots

robot_ip = "192.168.1.2"  # replace with your robot's IP

robot = universal_robots.UniversalRobotsUR10E()
# Connect
robot.connect(ip=robot_ip)

robot.unlock_protective_stop()
logger.success("Protective stop unlocked.")

# Disconnect
robot.disconnect()

The Explanation of the Code ​

unlock_protective_stop sends the unlock command to the robot controller, clearing the protective stop state so that the robot can receive motion commands again. Always verify the cause of the protective stop before unlocking. Do not use this call to silently suppress repeated protective stops — investigate and resolve the underlying cause first. Returns None on completion.

How to Tune the Parameters ​

This skill takes no parameters.

Return Value ​

TypeDescription
NoneReturns when the unlock command has been sent.

Where to Use the Skill ​

  • Automated recovery sequences — Programmatically clear a protective stop as part of a supervised error-recovery routine
  • Test and integration harnesses — Reset the robot state after a planned stop during testing

When Not to Use the Skill ​

Do not use Unlock Protective Stop when:

  • The cause of the stop has not been identified — always determine why the protective stop was triggered before unlocking
  • A hardware safety condition is still active — the controller may re-trigger a protective stop immediately if the fault condition persists