-
Notifications
You must be signed in to change notification settings - Fork 46
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
Controller issues #14
Comments
Can you try the following:
|
Thanks! I'll try that tomorrow. |
Since there was no signal of life (LED was always off) from the controller, I decided to investigate it. After opening it, the battery turned out to be at 4.16V. Unplugging the battery for 3 seconds brought the controller back to life. Tried before to get that by pressing the reset button, but that again did not work. Probably a power management issue with that controller. I will further investigate the connection stability and ability to control the robot. |
Quite frequently, the controller does not pair with the robot. Even when holding it right next to the robot. |
Same with my controller. It was not showing any sign of life. The reset button saved its life. |
I've encountered difficulties too: EDIT: it worked for a second, the controller turns off 10 seconds later automatically. So basically not working. Can't get it to pair and connect. |
Closing as stale. |
Something seems to be wrong with our gamepad controller. When I first too it out of the box and started charging it, it turned amber which seemed fine. However after some time I disconnected it and it stayed amber. Even pressing the pairing key combo, nothing changed. Only the reset button on the back helped.
Now connecting often fails, as does driving the robot. We are still investigating if this is an issue with this particular controller or with the raspi bluetooth module.
It could well be that the controller is just not charged. When I connected to USB for charging today evening, it did not light up at all. Different cables/different USB outlets did not affect the behavior.
The text was updated successfully, but these errors were encountered: