Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
How to pair PS3 controller after upgrading to 18.04 #66
PS4 controller does not work after we upgrade to 18.04. http://docs.fetchrobotics.com/indigo_to_melodic.html does not say anything but:
There is an old command here http://docs.fetchrobotics.com/in_the_box.html?highlight=pair
@umhan35 thanks for letting us know you're encountering these issues!
My guess is the following should get you into a working state for now:
If that doesn't work, a short-term workaround will be to run it manually with
FYI, you should not need to re-pair the controller, as the pairing is a hardware thing between the controller and the bluetooth chip, neither of which change when the OS upgrade/reinstall is done. But, I will need to update documentation to point out that the new command will be
Thanks, @erelson. I tried
I am reading the troubleshooting webpage now...
@erelson I just confirmed that, by connecting HDMI cable to the robot, the Bluetooth indicator is Off. When I open the bluetooth setting and try to turn it on, the switch UI elements turned green but the label is off, and the list is still empty. It seems the bluetooth driver is not installed properly?
I took a video, take a look: https://photos.app.goo.gl/x8S6k7zpjYTcH2Vs6
referenced this issue
Apr 19, 2019
We are having similar issues inhouse as well, sometimes.
A quick fix I found is that if the /joy topic is publishing, but the robot is not moving, you can do
Then to get around the need to create /dev/ps3joy (which ultimately seems to be due to udev rules not triggering), a hack that will work in the meantime is to edit your robot's
<!-- Teleop --> - <include file="$(find fetch_bringup)/launch/include/teleop.launch.xml" /> + <include file="$(find fetch_bringup)/launch/include/teleop.launch.xml"> + <arg name="joy_device" value="/dev/input/js0" /> + </include>
My testing is limited so far, but that may make the PS3 controller work at startup. Let me know what you find.
Finally, a related note: with the melodic release of fetch_teleop (? or similar package name), note that we changed the (undocumented) cartesian arm teleop control to also require the primary deadman button to be held down at the same time.
We specifically avoid changing any files in/etc/ros/melodic/ with new releases, so the change will persist.
I am hoping to find a overall better setup for PS3 controllers eventually. If anything, a proper setup might necessitate reverting this change later (but perhaps only if you move to using a different controller for teleop).
Thanks for confirming!