-
Notifications
You must be signed in to change notification settings - Fork 481
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
Add a dead zone configuration for controllers #245
Comments
In Windows 7 the standard Joystick helper programs deadzone configuration is over ruled by the Crazyflie client. I have heavy noise on my new Joystick and my Xbox Controller is unusable. I cannot start the Crazyflie without drifting heavily to the noise middle. A deadzone control would really be appreciated. It's not just an overtime effect for me. I cannot use it like this. My XBox Controller has a neutral position somwhere between -/+ 10 in the X and Y axe (I cannot fly straight up). |
Yes, very useful because the precision of a joystick is highly variable, around null position. Very easy to implement. |
I am testing the implementation, see my branch "nexon" from a fork of python client. My repo is Mitteau/... Do I ask for a request to pull? I use also an xbxo360 controller. My dead zone is +- 0.08. A dead band is very confortable for stationnary flight and progressive take off. |
Bug if there is no input map... |
Looks OK now... |
Pull request proposed. |
Implemented in #332 |
Some joysticks/controllers have noise in the values which might cause drift over time. One solution would be to add a dead zone in which the input is ignored.
Preferably the zone should be configurable.
Related to #47
The text was updated successfully, but these errors were encountered: