Jackal robot PS4 remote cannot pair using bluetooth with the robot?
I just got a jackal robot with a PS4 remote. According to the instructions it should automatically pair with the jackal robot however the pairing doesnt happen.
However, when I connect the remote to the USB inside the robot it works. Almost seems like I need to reinitialize the remote. I tried following the commands:
sudo sixpair sudo sixad --boot-yes
I get the following error: No controller found on USB busses. Please connect your joystick via USB.
Any advice?
Trying ds4drv-pair command. I get the following error:
Scanning for PS4 controller Found controller with address: 'AC:FD:93:E2:C2:0A'
Traceback (most recent call last): File "/usr/bin/bluez-simple-agent", line 102, in <module> manager = dbus.Interface(bus.get_object("org.bluez", "/"), File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Traceback (most recent call last):
File "/usr/bin/bluez-test-device", line 17, in <module> manager = dbus.Interface(bus.get_object("org.bluez", "/"), "org.bluez.Manager") File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
I don't have a fix, I just wanted to say that I also just received a jackal and the same thing happened to me. I ended up using a different controller connected to my laptop.
Did you receive it with a PS3 or PS4 controller?
I received it with a PS4 controller
Ashwin, did you get a chance to try re-pairing it with
ds4drv-pair?Airuno2L, did you also get a PS4 controller?
I got a PS4 controller but never got it working. Once I realized it wasn't working as described in the manual I threw it in storage and grabbed a controller I'm more familiar with. The manual is incorrect else where also, like it said the robot's IP was 192.168.1.1 but it was actually 192.168.1.11
Airuno2L, you are correct there are many discrepancies in the clearpath manual, but clearpath also sent us a "From the desk of the Robotsmiths" document which helped clear alot of the confusion created by the default clearpath manual. (Aside from the PS4 controller issue)