Skip to content

moving to an impossible location breaks further calls to ROS services #3890

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

Open
zimmy87 opened this issue Jul 19, 2021 · 1 comment
Open
Labels

Comments

@zimmy87
Copy link
Contributor

zimmy87 commented Jul 19, 2021

Bug report

  • AirSim Version/#commit: master
  • UE/Unity version: 4.25.4
  • autopilot version: n/a
  • OS Version: Windows 10 / WSL2 (Ubuntu 20.04)

What's the issue you encountered?

If you call the /airsim_node/local_position_goal ROS service with a position underground such that the drone cannot ever reach it, any further calls to the service will fail and the drone will be stuck trying to move to the original impossible goal.

Settings

follow configuration described here

How can the issue be reproduced?

  1. apply fix ROS topic names #3880
  2. follow repro steps in How to call ros service #3805
  3. call the /airsim_node/local_position_goal ROS service again with a valid location, i.e. rosservice call /airsim_node/local_position_goal 0 0 -- -5 2 drone_1

Include full error message in text form

What's better than filing an issue? Filing a pull request :).

@zimmy87 zimmy87 added the ros label Jul 19, 2021
@leoborgnino
Copy link

Hi!

I think with topic "/airsim_node/local_position_goal/override" you can change the goal and get over the problem.

However, I think that could be added a check for unsupported positions in local_position_goal_srv_cb ( I don't know if a position underground would be required in some case, I don't think so ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants