Skip to content

Fix unexpanded xacro expressions in IRB 4600 ros2_control limits - #100

Open
yishinli wants to merge 1 commit into
PickNikRobotics:rollingfrom
yishinli:fix/irb4600-ros2-control-limits
Open

yishinli wants to merge 1 commit into
PickNikRobotics:rollingfrom
yishinli:fix/irb4600-ros2-control-limits

Conversation

@yishinli

Copy link
Copy Markdown

Summary

The joint_1 and joint_3 position limits in irb4600.ros2_control.xacro were missing the $, so xacro left them as literal strings:

-          <param name="min">{-2*pi}</param>
-          <param name="max">{2*pi}</param>
+          <param name="min">${-2*pi}</param>
+          <param name="max">${2*pi}</param>

Evidence

Before: ros2_control_node skips those limits:

Error parsing the limits for the interface: position from the tags [min: '{-2*pi}' and max: '{2*pi}'] within ros2_control tag inside the URDF. Skipping it
Error parsing the limits for the interface: position from the tags [min: '{-2*pi}' and max: '1.308'] within ros2_control tag inside the URDF. Skipping it

After: xacro irb4600_60_205.xacro expands them to -6.283185307179586 / 6.283185307179586 and the warnings are gone.

Merge Danger

Door: two-way

Blast Radius: IRB 4600

ros2_control now applies the intended command limits for joint_1 and joint_3 on all three IRB 4600 variants. They are wider than the URDF joint limits, so the URDF limits still govern motion.

🤖 Generated with Claude Code

The joint_1 and joint_3 position limits were written as {-2*pi} and
{2*pi} instead of ${-2*pi} and ${2*pi}, so xacro left them as literal
strings and ros2_control skipped them:

  Error parsing the limits for the interface: position from the tags
  [min: '{-2*pi}' and max: '{2*pi}'] ... Skipping it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mergify

mergify Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@yishinli yishinli closed this Oct 26, 2026
@yishinli yishinli reopened this Oct 26, 2026
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.

1 participant