Known Issue: Time slip Estimator Error

We recently have had more and more cases, where people are not able to take off with an error message "Estimator Timeslip Error"

Insights

  • This can come up on sporadic boot-ups for different reasons. If a repower resolves it, proceed with flying with no worries.
  • Ask for flight logs for reported cases and always hand over to dev for investigation!

Correlation with Distance Sensor Issues

  • ONLY if it happens consistently on multiple boot-ups it points towards "the bigger issue" which is not yet understood and has some correlation to the distance sensor. (There you typically see a continuous increase in timeslip, see images below). This is also the reason why we currently have a pretty conservative threshold (0.1s) to protect against crashes until we understand it better.

What to do if problem persists

  • Try many repowerings and move the drone around and to another take off place. Phrase it nicer, but try to shake the drone --> routing of cables could make a difference.
  • Sometimes the issue is magically gone the next day.
  • If nothing helps, replace the wing or try replacing the distance sensor (chance that this solves it is only ~40% of cases). Discuss with another Wizard or Dev first

A sane timeslip signal looks like that:

sane

A bad timeslip looks like that:

faulty