Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Motor output usage larger than simulation #94

Closed
airopti opened this issue Jan 8, 2021 · 1 comment
Closed

Motor output usage larger than simulation #94

airopti opened this issue Jan 8, 2021 · 1 comment

Comments

@airopti
Copy link

airopti commented Jan 8, 2021

In the real flight test part of your thesis, the 4 motors output around 50% usage to track desired angular speed [0, 0, 0] rad/s at the first few seconds as shown in Figure 5.23. While in simulation as shown in Figure 5.19, the motor usage is around 0.1 to track [0, 0, 0] rad/s .

Why would this mismatch happen? In real flight test, the high motor usage to track [0, 0, 0] rad/s when no stick input will make the drone climb?

@airopti airopti added the bug Something isn't working label Jan 8, 2021
@wil3 wil3 removed the bug Something isn't working label Jan 8, 2021
@wil3
Copy link
Owner

wil3 commented Jan 8, 2021

Hi @airopti, the simulation environment does not have gravity thus less power is required. See Issue: #78 for more information.

During training the agent is penalized for too high control outputs (to prevent the aircraft from climbing). You can identify the control signal required to hover (overcome gravity) in a real flight test and then use this within the reward function.

In the beginning of development this was one of the biggest challenges: how to teach the quad when idle on the ground (setpoint of 0 deg/s) to minimize control signal output and not punch it (which happened alot....). I talk about this a bit in my thesis presentation.

@wil3 wil3 closed this as completed Jan 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants