Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Odometry (/odom) Not Updating β€” Causes Waypoint Follower to Send FORWARD Indefinitely #6

Open
VinaySampath14 opened this issue Mar 29, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@VinaySampath14
Copy link
Collaborator

πŸ“Œ Issue Title

Odometry (/odom) Not Updating β€” Causes Waypoint Follower to Send FORWARD Indefinitely


πŸ“ Description

I’m working on a ROS 2-based waypoint-following robot. I have two nodes:

  • waypoint_follower_node β†’ publishes Twist to /cmd_vel based on waypoints
  • serial_motor_controller β†’ subscribes to /cmd_vel and sends motor commands like "FORWARD", "STOP" to Arduino

However, the robot keeps moving forward indefinitely and never switches direction or completes the waypoint sequence.


πŸ” Observations

βœ… Serial Controller Working

  • The serial_motor_controller logs show continuous "FORWARD" commands being sent:
    [INFO] Command sent: FORWARD
    [INFO] Command sent: FORWARD
    ...
    

❌ Odometry Not Updating

  • When I echoed /odom, I noticed the position is repeating and not changing:
    position:
      x: 110.93110205269798
      y: 67.64417217594637
      z: 0.0
  • This value remains constant across multiple time samples, which indicates that odometry is not being updated.

πŸ”„ Expected Behavior

  • The waypoint follower computes the distance to the goal using:
    distance = sqrt((goal_x - x)**2 + (goal_y - y)**2)
  • Since x and y are stuck, distance never goes below threshold β†’ robot keeps sending FORWARD.

πŸ§ͺ What I Tried

  • Verified /odom is being published β†’ βœ… yes, but values are constant
  • Changed distance threshold β†’ no effect
  • Added debug logs to print position and distance β†’ confirms pose is not changing
  • Echoed /odom β†’ shows no position updates

πŸ€” Likely Root Cause

  • The component responsible for publishing /odom (possibly Arduino or another odometry source) is not updating pose data.
  • This breaks waypoint logic that depends on updated pose to track progress.

βœ… Request

  • Please help verify or fix the odometry update mechanism.
  • If this is a hardware/sensor integration issue, suggestions for simulation or fallback approaches (like distance-based logic or mock odometry) would be appreciated.

odom.txt

@VinaySampath14 VinaySampath14 added the bug Something isn't working label Mar 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant