-
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
Failsafe triggering in SITL #11402
Comments
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. |
Closing as stale. |
Thanks for the issue and sorry for the late response. @MaEtUgR could you have a quick look? |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Closing because there was no follow up. |
During SITL test flight using 1.9.0 firmware, Drone executes setpoint command in offboard and then will show the following message
before auto-landing, ignoring any further setpoint commands. I have tried several ways to isolate the problem, and have now started stripping out all custom code & parameters to just run a single MAVROS demo script that should work, and am still getting the error.
Drone is Iris with optical flow.
Firmware tested has been 1.8.2 and 1.9.0 beta.
Using ROS Melodic and Gazebo 9 on Ubuntu 18.04 LTS.
This also happens when eliminating Mavros from the equation and sending standard mavlink offboard messages normally. While I have no PX4 logging, the behaviour of the the drone in real testflights suggests that it encountered the same bug.
There are three points in mc_pos_control_main.cpp that call failsafe, this is the first instance on line 678
https://github.com/PX4/Firmware/blob/504372f551d37d64141397c9add67c9d35b2338e/src/modules/mc_pos_control/mc_pos_control_main.cpp#L678
This failsafe appears when FlightTasks.cpp's update command returns true. This is triggered by having flight tasks that are still active after calling the internal _updateCommand() function. At this point I decided it's best to post a bug report as troubleshooting what task remains active and why is getting really opaque, perhaps someone on here knows what is causing this issue? I am just trying to get a very simple flight demo together in SITL for now and this is a major blocking issue.
The text was updated successfully, but these errors were encountered: