Skip to content

Add robot-specific operational command limits - #10

Merged
s2015-turtle merged 2 commits into
mainfrom
safety/add-operational-command-limits
Jul 24, 2026
Merged

Add robot-specific operational command limits#10
s2015-turtle merged 2 commits into
mainfrom
safety/add-operational-command-limits

Conversation

@s2015-turtle

Copy link
Copy Markdown
Owner

Summary

  • add optional ROS joint-coordinate limits for position, velocity, and effort commands
  • clamp commands before coordinate conversion and CAN encoding
  • reject non-finite, reversed, or out-of-wire-range configurations
  • expose the limits from every motor profile and document them in English and Japanese
  • add parser, clamping, and Xacro coverage

Validation

  • git diff --check
  • XML validation for changed Xacro files
  • expanded both the default profile fixture and explicit command-limit fixture with Xacro
  • local build intentionally not run on this PC; the ROS distribution matrix will run in GitHub Actions

Closes #7

@s2015-turtle s2015-turtle added enhancement New feature or request maintenance Refactoring, cleanup, and repository maintenance labels Jul 23, 2026
@s2015-turtle
s2015-turtle marked this pull request as ready for review July 24, 2026 05:08
@s2015-turtle
s2015-turtle merged commit fbfbb3e into main Jul 24, 2026
5 checks passed
@s2015-turtle
s2015-turtle deleted the safety/add-operational-command-limits branch July 24, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request maintenance Refactoring, cleanup, and repository maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add robot-specific command limits separate from CAN wire ranges

1 participant