cmdFullState yaw not working #309
Replies: 5 comments
-
Which controller are you using? |
Beta Was this translation helpful? Give feedback.
-
Honestly, I would not be that surprised if there is a bug in our yaw control. The large majority of our experiments have been position control with 0 yaw all the time. |
Beta Was this translation helpful? Give feedback.
-
I was using PID for which the yaw control did not work. Mellinger on the other hand works just fine. Does this look like a bug to you or is the combination simply not supported? |
Beta Was this translation helpful? Give feedback.
-
This combination should be supported. I implemented the |
Beta Was this translation helpful? Give feedback.
-
Since the Mellinger controller anyways seems to be more stable this is not a big issue. Would still be great if it worked though. Do you have time to investigate or give me a hint where to look? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I am having trouble getting the
cmdFullState
command to work, especially the yaw part. It seems logic to me thatpos
andvel
have to be consistent. However, I am not sure whatomega
needs to be if I want to controlyaw
. @jpreiss suggests here thatomega
can be set to zero, but I guess this is only true ifyaw = 0
?I tried to turn a CF by 90 degrees (while hovering) with the code snippet below but it does not move/turn at all. Changing
yaw_rate
to degrees/s and havingyaw
andomega
with different signs or units did not help.During my tests I also found some incorrect docstrings:
yaw
argument ofcmdPosition()
seems to be in degrees and not in radians.yawRate
argument ofcmdVelocityWorld()
seems to be positive in clockwise direction which does not match with the coordinate system of the CF in my opinion.Beta Was this translation helpful? Give feedback.
All reactions