Closed EdwardAbrosimov closed 4 years ago
Thanks for reporting! Hmm, I've never had this problem myself, but that could be because I wasn't using docker. Could you share a minimal Dockerfile
to reproduce this problem and also the revision of ds4_driver
that you're using?
A similar bug regarding formatting error (i.e. TypeError: not all arguments converted during string formatting
) was fixed in 34974eccedf5c2ddc70f178ad63e7f6cc2504408, FYI.
I think the docker has nothing to do with it, because I can’t even start the host to the host machine (ubuntu 18.04, ros melodic).
ds4drv --version
show ds4drv 0.5.1
But I noticed that using the driver in hidrav mode:
ds4drv --hidraw
also does not allow me to connect to the joystick. I think you need to deal with this problem first, as it says in your package that support for the Bluetooth mode was not tested
That is strange. You are using the forked version of ds4drv instead of the upstream repo, correct?
it says in your package that support for the Bluetooth mode was not tested
I don't remember writing anything like that, since I have extensively tested using Bluetooth. Was that written in ds4drv
or in ds4_driver
?
That is strange. You are using the forked version of ds4drv instead of the upstream repo, correct?
it says in your package that support for the Bluetooth mode was not tested
I don't remember writing anything like that, since I have extensively tested using Bluetooth. Was that written in
ds4drv
or inds4_driver
?
I mean https://github.com/naoki-mizuno/ds4_driver#parameters parametr ~backend
I use forked version, but earlier i use simple ds4drv
. I will try to reinstall everything and possibly run in a clean container.
I mean https://github.com/naoki-mizuno/ds4_driver#parameters parametr ~backend
Okay, that makes sense. That parameter may be confusing, since you don't need to set backend
to bluetooth
to use Bluetooth connection. In general, you don't need to change the parameters to connect to your DualShock 4 (whether via USB or Bluetooth).
Since #4 seems to have fixed this problem, I'll close this issue :)
I have a very similar issue now but running on ROS Humble that's running on a Docker container. Specifically, I'm able to connect the ds4 by using the command ds4drv
but not ds4drv --hidraw
or ros2 launch ds4_driver ds4_driver.launch.xml
(it just stays stale). Any idea on how to fix this?
Would it be possible to use ds4drv
to connect to the bluetooth device, and then use some parameter in ros2 launch
file?
Update: I forgot to mention that I tried it out on the Dockerfile from the repo and it still didn't work.
Faced a problem - I can’t connect the joystick using bluetooth. I run
roslaunch ds4_driver ds4_driver.launch
before uncommenting line 8 in the fileds4_driver/config/params
:backend: bluetooth
Here is what I get:
In general, I want to use the joystick in a docker container. At the same time, when I launch just a driver, it finds a joystick (both in the container and on the host machine): ds4drv
Maybe controller.py dont create device in /dev/input ?
I will be grateful for any ideas what could be the problem.