aerostack2 / aerostack2/aerostack2.github.io

Weird behavior with 'hover()'

Aperta
#69 9 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Nessun dato sulla lingua
Stelle
15
Fork
9
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Hi

I took the movement functions that the teleopt module uses, i.e. speed.py.
With that speed module I can give the drone an order to go to a direction using velocity vector, and it keeps moving until I tell it to stop.
How do I tell it to stop? two options, both problematic.
1. I can set the velocity vector to zeros. It stops, after a drift caused by its movement. But it stops.
2. I can call the 'hover()' function. That stops the drone immediately which is what I need.

But if I use the second option, when performing another movement on another direction, I still get leftovers from the former movement.
For example, if I go 'forwards' (1,0,0), then call hover, and then go 'right' (0,1,0), the drone would go forwards, stops, then go forwards again for half a second and only then fixes its movement and go right.
That is not desirable at all...

Is that a bug?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.