SITL test is failing: copter mode stuck on STABILIZE
See original GitHub issueThe SITL tests are currently failing on the master branch, both for Python 2 and Python 3. The cause is a SITL test that’s not passing: test_goto.py.
The apparent reason of the error is that the test times out when setting the mode to GUIDED
.
I managed to run the unit test locally, and I can’t get the SITL to switch to GUIDED
: the vehicle remains stuck on STABILIZE
. The GPS and the global location seem to be ok. The Vehicle is periodically receiving heartbeat updates containing the mode flag, so it’s not a reception problem.
My hypothesis is that some update on the ArduPilot side, or in some dependencies, made the tests fail. From the commit history it’s easy to see that the previous commits (that worked) are identical to the latest ones, which were simple documentation changes.
Any hints?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:14 (5 by maintainers)
yes this reverting back to older version of pymavlink worked for me, i was having trouble in DO_SET_MODE change while executing the python script as it was stuck at stabalize, even now i can’t change the mode in mavproxy but it works when i run the script
i was having pymavlink 2.4.12 and reverted back to pymavkink 2.4.8 for now at least im able to run the script and need to find the issue with mavproxy
Hi, in the meantime should we revert to using 2.9.1? (I noticed there’s a 2 year gap on pypi)
Nevermind. I was able to uninstall pymavlink with
and then reinstall the older version with