-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Commander: don't reset home position if landed during a mission #24902
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
Conversation
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.
Nice! I like this solution better than the proposed alternatives
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.
Can you adapt the parameter description of COM_HOME_EN (add a note that Home is not reset if mission is not complete)?
And do I get it correctly that now if you fly a mission, then take over in a manual mode, land somewhere, takeoff off again --> Home is not updated?
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 104 byte (0.01 %)]
px4_fmu-v6x [Total VM Diff: 88 byte (0 %)]
Updated: 2025-05-28T13:45:58 |
cfeba18
to
4093122
Compare
@sfuhrer When you take over the |
4093122
to
dbf6903
Compare
dbf6903
to
9ceff18
Compare
Solved Problem
If
COM_HOME_EN
is enabled, the home position will reset when landed.However, during mission execution, we want to prevent the home position from resetting if an intermediate landing occurs. Instead, the home position should remain fixed at the one set at the beginning of the mission.
Solution
To have multiple takeoff items in a mission: I found that this feasibility check fails and prevents you from uploading the mission. Commenting it out works for now, but is probably not a very robust solution.
Changelog Entry
For release notes:
Alternatives
We briefly discussed whether this should be a configuration option. These are the alternative options:
Extending
COM_HOME_EN
(or introducing a new parameter) that only sets the home_position once in a boot cycle (position where the vehicle was armed the very first time).Creating a mission parameter that enables multiple takeoffs. If enabled, home_position doesn't update upon each landing. Something like:
MIS_MULTI_TKO_LND
?Test coverage
Tested in SITL: