This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Tactics deactivating on copters due to invalid altitudes #114
Comments
Debugging with Paul the invalid altitudes have also been observed on zephyrs causing deactivations.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm filing this ticket here since it's an observation of a overall system behavior and it's important to document. It will likely need to be refiled and fixed somewhere else eventually once it's root caused.
While running tests I observed several vehicles reporting invalid altitudes briefly.
I got a few screen shots of the conditions. The vehicles would be reporting invalid altitudes temporarily before returning to expect altutides in the FTI interface.
![invalid altitudes](https://cloud.githubusercontent.com/assets/447804/23573861/0afc58d4-002e-11e7-9e8b-6369c0e9f4ba.png)
![invalid altitudes_stil active](https://cloud.githubusercontent.com/assets/447804/23573862/0affe968-002e-11e7-831e-8e0df85c9995.png)
I was observing this during the ingress phase, documented it as above and then moved on. It did not appear to be effecting the actual flying. And going from 150m to single digit and back to 150m in a few seconds is not physically feasible.
After engaging some tactics I observed some of them drop out immediately and there seemed to be a correlation with the ones reporting bad altitudes.
After the run I dug into the logs and saw that in swarm_control Behaviors were self disabling.
Looking at the logs for Iris 3
And the swarm tracker gave a reason:
And I noticed the altitude of -0.24 looks a lot like some of the invalid altitude reports I had seen. Thus I believe that the copters are temporarily getting invalid states, and when they compute their target waypoints based on their current states they're deemed invalid as being too low.
A screen capture of the run can be seen here: https://youtu.be/acDmHkkub7I
I have a full log of the engagement period. Iris 3 only appeared to deactivate 2 times.
There was an event at ~ 2:35 where all blue vehicles deactivated: https://youtu.be/acDmHkkub7I?t=2m33s also that is undiagnosted.
It happened a 2nd time around 5:29 https://youtu.be/acDmHkkub7I?t=5m29s
The text was updated successfully, but these errors were encountered: