DualShock 4 driver for ROS.
- Get information such as IMU, battery, and touchpad from your DualShock 4.
- Use feedback such as rumble, LED color, and LED flash via ROS topics.
- Connect to your controller via Bluetooth.
- Utility node included to publish velocity commands from inputs
This driver depends on ds4drv. Some features of this driver depend on pull
requests have not yet been merged upstream. Until they are merged, use
naoki-mizuno/ds4drv
(devel branch).
$ git clone https://github.com/naoki-mizuno/ds4drv --branch devel
$ cd ds4drv
$ mkdir -p ~/.local/lib/python3.10/site-packages
$ python3 setup.py install --prefix ~/.local
# Note: udev directory is in the ds4drv repo, not ds4_driver (this repo)
$ sudo cp udev/50-ds4drv.rules /etc/udev/rules.d/
$ sudo udevadm control --reload-rules
$ sudo udevadm triggerCompile and source this package just like any other ROS package. To run,
$ ros2 launch ds4_driver ds4_driver.launch.xml
# Or
$ ros2 run ds4_driver ds4_driver_node.pyGet a glimpse of some of the features of ds4_driver including touchpad,
rumble, and LED control:
$ ros2 launch ds4_driver demo.launch.xml
# See the messages that are published
$ ros2 topic echo /status
Moving the left/right stick controls the rumble. Sliding left and right on the touchpad while pressing circle, triangle, cross buttons controls the brightness of the red, green, blue LED, respectively (you can tell from the color of the button). Pressing the PS button triggers the flashing of the LED.
A docker image is provided on Docker Hub, as well as a Dockerfile that can
be used to build an image.
$ ./run_docker.bash
# Takes you into the container's interactive shell
$ ros2 launch ds4_driver demo.launch.xml
Or if you want to build the image,
docker build ./docker
This is the main node that interacts with DualShock 4.
~device_addr: hardware address of the device. If unspecified, will use the first device found.~backend(default:hidraw): what backend to use to connect to the device via Bluetooth.bluetoothis only there for legacy support and has not been tested. Refer to the docs inds4drvfor details.~use_standard_msgs(default:false): use ROS-standard messages such assensor_msgs/Joy.~autorepeat_rate(default:0(disabled)): rate in Hz at which a joystick that has a non-changing state will resend the previously sent message. This parameter is only effective whenuse_standard_msgsistrue.~deadzone(default: 0.1): amount by which the joystick has to move before it is considered to be off-center.~frame_id: (default:ds4): frame ID to be used for the messages.~imu_frame_id(default:ds4_imu): frame ID to be used for the IMU messages.
/status(ds4_driver_msgs/Status): current state of the device.
/set_feedback(ds4_driver_msgs/Feedback): feedback for the device such as LED color, rumble, and LED flash.
Note: To disable flash, send message with set_led_flash: true and
led_flash_off: 0.
/raw_report(ds4_driver_msgs/Report): raw, uninterpreted report that the device sends./battery(sensor_msgs/BatteryState): battery state of the device./joy(sensor_msgs/Joy): joypad state./imu(sensor_msgs/Imu): IMU state.
/set_feedback(sensor_msgs/JoyFeedbackArray): feedback for the device.
A node to convert joypad inputs to velocity commands is included in this
package. This node is something similar to
teleop_twist_joy but is specifically
for a DualShock 4.
~stamped(default:false): whether to publishTwistorTwistStampedfor the output velocity command. For robots such as TurtleBot, Husky, and PR2/cmd_velis not stamped (i.e.Twistis used) but stamped velocity commands may be required for some applications.~inputs: what buttons and axes to use for the value of each velocity vector. Expressions can be used to combine values of multiple keys (seeconfig/twist_6dof.yamlfor examples).~scales: scaling factor for each velocity vector.
/cmd_vel(geometry_msgs/Twistorgeometry_msgs/TwistStamped): velocity command.
/status(ds4_driver_msgs/Status): joypad state.
Note: You can skip this section if you use the forked version of ds4drv
(i.e. naoki-mizuno/ds4drv) because the following line is included in the
udev rules by default.
By default the touchpad of the DualShock 4 is recognized as an input device.
Because of this, the mouse moves to the location on screen that corresponds to
the location touched, making it very hard to track the mouse cursor (and
worse, it automatically clicks at that location). If you want to prevent the
touchpad from being recognized as an input device, add the following to the
udev rules and run the udevadm commands (you will still be able to use the
touchpad from this driver):
SUBSYSTEM=="input", ATTRS{name}=="*Wireless Controller Touchpad", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""
MIT
Naoki Mizuno ([email protected])
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent