Skip to content

Conversation

@leeminju531
Copy link
Contributor

Related Issue : #197

Description

At hardware initialization, the call to Drfl.set_safety_mode(SAFETY_MODE_AUTONOMOUS, SAFETY_MODE_EVENT_MOVE); was causing issues, so it has been removed.

Additional Information:

In general, motion APIs handle the safety state internally, so there's usually no need to manage it explicitly. As far as I know, the only exception is the servoj API used in MoveIt, which doesn't handle safety internally.

This case is already managed in the write section of the hardware interface.
To handle the safety mode transitions:

  • Set Drfl.set_safety_mode(SAFETY_MODE_AUTONOMOUS, SAFETY_MODE_EVENT_MOVE); only once, when detecting the initial change in joint positions.
  • Set Drfl.set_safety_mode(SAFETY_MODE_AUTONOMOUS, SAFETY_MODE_EVENT_STOP); only once, when detecting the initial point where joint positions stop changing.

@leeminju531
Copy link
Contributor Author

This changes might make side effects. we need to have more consideration.

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