open-rmf / open-rmf/rmf

[Other issue]: RMF sending multiple identical goal with different orientation

Open
#485 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
438
Forks
89
PR merge metrics
No merged PRs in 30d

Description

Before proceeding, is there an existing issue or discussion for this?
Description

Hi All!

First of all I would like to congratulate you for the huge and amazing job you have done so far and what are you still doing!

I'm trying to solve an issue with RMF for my robotics project with multiple robots.
In this scenario I have a couple of huskies which are managed by a free fleet system and each one of them has a full control fleet adapter integrated.

Now, everything works correctly until, in the middle of simulation, the robot seems to receive multiple goals with the same x and y, but different yaw. The same behavior happens, not only in a waypoint, but in the middle of a lane.
See below.

It seems quite strange here since in the moment these goals are sent there's no conflict to solve and the robot could simply follow the other goals.

husky_rotations_issue

I tried to look for similar issues around the discussions, but, a part from the #429 (which didn't solve my problem because ResponsiveWait is set to False), there are no discussions at all.

At this point a few questions comes out:

  • Who can be the responsible of this behavior?
  • How can i solve this issue?

Required information:

  • Operating system and version: Ubuntu 22.04.
  • ROS distribution and version: Humble.
  • OpenRMF version branch: humble.
  • Fleet management system: Free fleet.
  • Fleet adapter: Full control fleet adapter.

Expected behavior:

The robot should remain still in whatever situation (conflicts or not).

Thank you for a possible answer!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read rmf_fleet_adapter/src/full_control/main.cpp first and compare the goals observed in the waypoint and lane cases with the Free Fleet output. Review issue #429 for related behavior and trace where differing-yaw goals are published. Done means identifying the responsible component and preventing duplicate goals, or documenting a confirmed upstream cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.