aerostack2 / aerostack2/aerostack2.github.io

Weird behavior with 'hover()'

Offen
#69 9 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Keine Sprachdaten
Sterne
15
Forks
9
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.