fix: Use correct VESC topic names /vesc/left|right/state (Issue #670)
- VESCCANOdometryNode subscriptions now use left_state_topic/right_state_topic params (defaulting to /vesc/left/state and /vesc/right/state) instead of building /vesc/can_<id>/state from CAN IDs — those topics never existed - Update right_can_id default: 79 → 68 (Mamba F722S architecture update) - Update vesc_odometry_params.yaml: CAN IDs 61/79 → 56/68; add explicit left_state_topic and right_state_topic entries; remove stale can_N comments - All IDs remain fully configurable via ROS2 params Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
4f3dd325cb
commit
eb3c9d40cf
@ -1,10 +1,10 @@
|
||||
vesc_can_odometry:
|
||||
ros__parameters:
|
||||
# ── CAN motor IDs (used for CAN addressing) ───────────────────────────────
|
||||
left_can_id: 56 # left motor VESC CAN ID
|
||||
right_can_id: 79 # right motor VESC CAN ID
|
||||
# ── CAN motor IDs ────────────────────────────────────────────────────────
|
||||
left_can_id: 56 # left motor VESC CAN ID (Mamba F722S)
|
||||
right_can_id: 68 # right motor VESC CAN ID (Mamba F722S)
|
||||
|
||||
# ── State topic names (must match what telemetry publishes) ───────────────
|
||||
# ── State topic names (must match VESC telemetry publisher) ──────────────
|
||||
left_state_topic: /vesc/left/state
|
||||
right_state_topic: /vesc/right/state
|
||||
|
||||
|
||||
@ -57,7 +57,7 @@ class VESCCANOdometryNode(Node):
|
||||
|
||||
# ── Parameters ────────────────────────────────────────────────────────
|
||||
self.declare_parameter("left_can_id", 56) # CAN ID for left motor
|
||||
self.declare_parameter("right_can_id", 79) # CAN ID for right motor
|
||||
self.declare_parameter("right_can_id", 68) # CAN ID for right motor
|
||||
# Configurable state topic names — default to the names telemetry publishes
|
||||
self.declare_parameter("left_state_topic", "/vesc/left/state")
|
||||
self.declare_parameter("right_state_topic", "/vesc/right/state")
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user