-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
delete NAVIGATION_STATE_AUTO_RTGS (OBC datalink loss) #14307
Conversation
@julianoes @bkueng @thomasgubler any objection to this (high level)? I still need to review some of the details carefully. |
No, this is great. We need to be having less code, but the code we have needs to be maintained well. I'm pretty sure that the "mainline failsafe code" can be made OBC compliant with a few tweaks if needed. |
Note to self, this has a few associated docs changes in https://docs.px4.io/master/en/config/safety.html#rc_loss_failsafe . This will need to be done before v1.11 branch gets taken. |
no |
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.
That's awesome! Do you understand what happens if someone still has this param set though?
If a user had it configured to that they will then get the same as having it disabled. Given that it states that it was for a competition and that competition is still months (or years) away, it is fine to remove this. |
Remove PX4_CUSTOM_SUB_MODE_AUTO_RTGS but retain the enum ordering / values as this is exposed externally (QGC).
@dagar Could you provide a test plan for @PX4/testflights ? That seems to be the last step to wrap this up. |
I'll add some logic in commander to manually migrate plus a mavlink message. We can drop it after a release or so. |
Added commander logic to migrate |
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.
Ok, that seems safe now!
Due to the weather, we did some Indoor Flights - Procedure Notes: Log: Pixhawk 4 mini v5 f-450 - Procedure Notes: Log: |
Tested on PixRacer V4Indoor Flight Test Procedure Notes Log https://review.px4.io/plot_app?log=7509c294-12e1-4107-8597-80572372fc31 Tested on CUAV nano V5Indoor Flight Test Procedure Notes Log https://review.px4.io/plot_app?log=160409ba-174e-4578-8d38-ad8569d46ec0 |
TODO:
NAV_DLL_ACT
andNAV_RCL_ACT
?