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
Improve offboard failsafe #18160
Improve offboard failsafe #18160
Conversation
The table is quite helpful, I'll review this. Any input here @Jaeyoung-Lim @bperseghetti? |
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.
I commented on small nitpicks for the MAVSDK tests part.
Other than that, I think your table make complete sense, and the implementation looks correct.
This is really well done and communicated, thanks a lot for the issue and PR!
Co-authored-by: Julian Oes <julian@oes.ch>
Co-authored-by: Julian Oes <julian@oes.ch>
The one CI error doesn't look related. |
My mistake that the result wasn't the most appropriate in all cases: @benjinne I fully agree with your intuitive resolution of failsafe cases. Thanks so much for the contribution of the correction, the tests and the very clear description. 👍 🙏 |
Hello. Where shall I change these parameters? |
In QGC there's a search option or they can be set in the mavlink console |
I'm running gazebo and PX4... So in QgroundControl shall I change those parameters? |
Yes, or if you're running |
thank you so much! it works!! |
@DiegoHerrera1890 Just for reference you can also change them using the QGC GUI like this: https://docs.qgroundcontrol.com/master/en/SetupView/Parameters.html on a real vehicle as well as the simulation (take care to connect to the right instance). |
@julianoes Hey, I'm trying to write MAVSDK tests for these cases, however there's no way to stop sending offboard setpoints abruptly. From what I see, only |
@benjinne I guess we need to add some functionality to MAVSDK which allows you to have more fine grained control over when the setpoint should be sent. I've created mavlink/MAVSDK#1630 to collect requirements around this, please add a note about the behavior that you would like to see there. |
Describe problem solved by this pull request
Closes #16534 using 2nd proposal of adding a new parameter to allow for failsafe on RC only.
Describe your solution
Change the following:
Describe possible alternatives
The outcomes in the table were picked by my intuition, but can change if needed.
Test data / coverage
All scenarios in table tested and verified using jmavsim and offboard_control example in px4_ros_com.