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

NAV_CMD_LOITER_TIME_LIMIT never reaches when altitude is different from last waypoint #8852

Closed
sanderux opened this issue Feb 8, 2018 · 5 comments

Comments

@sanderux
Copy link
Member

sanderux commented Feb 8, 2018

Corner case from actual flight:

WP1: Waypoint was set at 40m
WP2: Loiter (time) was set on time: 30 seconds, altitude: 55m, radius: 300m
The waypoint was placed exactly 300m from WP1
WP3 ...

The vehicle never reached the loiter altitude and never attempted to climb. The waypoint was never considered reached.

Reached check here:
https://github.com/PX4/Firmware/blob/bc3577bd60573b6c1e9f80024659805498e7608b/src/modules/navigator/mission_block.cpp#L215-L216

@sanderux
Copy link
Member Author

sanderux commented Feb 8, 2018

loiter_time_bug.plan.zip
Sitl reproducable

@dagar
Copy link
Member

dagar commented Feb 9, 2018

Seems to be FOH, investigating.

@sanderux sanderux added the bug label Feb 11, 2018
@dagar
Copy link
Member

dagar commented Feb 12, 2018

@stale
Copy link

stale bot commented Jan 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Feb 11, 2019

Closing as stale.

@stale stale bot closed this as completed Feb 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants