-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Navigator: fix RTL_TYP=2 with NAV_CMD_CONDITION_GATE #25648
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Silvan <silvan@auterion.com>
Signed-off-by: Silvan <silvan@auterion.com>
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 80 byte (0 %)]
px4_fmu-v6x [Total VM Diff: 80 byte (0 %)]
Updated: 2025-10-06T10:40:33 |
@sfuhrer sorry for the late reply. I checked it and your solution was a patch fix. The issue was that in the on_actuvation function, we did not check, if the mission item is actually a position item, when RTL was triggered during a mission. I added now my alternativ solution which fixes this instead of fixing the condition gate specifically. Happy for feedback. Maybe we should add another reviewer for this then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why all of the explicit type casts with the macro? Looks really bad and appears unnecessary
Solved Problem
The setpoint gets invalid (IDLE) during RTL with RTL_TYPE=2 and a mission containing NAV_CMD_CONDITION_GATE.
Solution
Skip NAV_CMD_CONDITION_GATE.
Changelog Entry
For release notes:
Alternatives
I don't understand why the GATE is even considered, it should already not be considered as not being in the list of
MissionBlock::item_contains_position()
.Test coverage
SITL tested.