From cf62b2197e8cd8174984973a81c8e1be7039dd4b Mon Sep 17 00:00:00 2001 From: Abe Tomoaki Date: Wed, 17 Jun 2026 12:24:06 +0900 Subject: [PATCH] Improve validation of `arm_type` GitHub: fixes GH-66 The launch script accepts several values. https://docs.openarm.dev/api-reference/description#supported-robot-versions Improve the xacro file checks to allow for these. Since `v10` was always passed downstream, it will be passed as a fixed value. Thanks for the report, sotanakamura!!! --- assets/robot/openarm_v1.0/urdf/openarm_v10.urdf.xacro | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/assets/robot/openarm_v1.0/urdf/openarm_v10.urdf.xacro b/assets/robot/openarm_v1.0/urdf/openarm_v10.urdf.xacro index c884159..23a1bad 100644 --- a/assets/robot/openarm_v1.0/urdf/openarm_v10.urdf.xacro +++ b/assets/robot/openarm_v1.0/urdf/openarm_v10.urdf.xacro @@ -36,8 +36,9 @@ limitations under the License. - - ${xacro.error('assets/robot/openarm_v1.0 only supports arm_type:=v10. Use assets/robot/openarm_v2.0 for newer hardware variants.')} + + + ${xacro.error('assets/robot/openarm_v1.0 supports arm_type in ' + str(accepted_arm_types) + ' (got: $(arg arm_type)). Use assets/robot/openarm_v2.0 for newer hardware variants.')} ${xacro.error('assets/robot/openarm_v1.0 only supports body_type:=v10.')} @@ -47,7 +48,7 @@ limitations under the License.