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

Controller issues #14

Closed
alexswerner opened this issue Jul 20, 2022 · 7 comments
Closed

Controller issues #14

alexswerner opened this issue Jul 20, 2022 · 7 comments
Assignees
Labels
bug Something isn't working requiring changes to this package

Comments

@alexswerner
Copy link

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.

@alexswerner alexswerner added the bug Something isn't working requiring changes to this package label Jul 20, 2022
@roni-kreinin
Copy link
Contributor

Can you try the following:

  • SSH into the RPI and call sudo bluetoothctl --agent=NoInputNoOutput
  • In the CLI type devices. This should show the MAC of the paired controller
  • Type in remove <MAC> to remove the controller. Also type untrust <MAC> to untrust it.
  • Follow the controller setup instructions to re-pair.

@alexswerner
Copy link
Author

Thanks! I'll try that tomorrow.

@alexswerner
Copy link
Author

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.

@alexswerner
Copy link
Author

Quite frequently, the controller does not pair with the robot. Even when holding it right next to the robot.

@Tanjim13
Copy link

Tanjim13 commented Sep 1, 2022

Same with my controller. It was not showing any sign of life. The reset button saved its life.

@teufelweich
Copy link

teufelweich commented Oct 26, 2022

I've encountered difficulties too:
I couldn't connect after I've paired successfully. The PI stated it was connected but the controller was blinking still.
I just tried trust and then connect without the pair, which worked for me.

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.

@roni-kreinin
Copy link
Contributor

Closing as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working requiring changes to this package
Projects
None yet
Development

No branches or pull requests

4 participants