We run the ds4drv to handle joystick events in user space and we use ros2 joy_node to read from dev/input/js0 This device is created by ds4drv when a joystick is paired.
The values of the axis contains bogus values
The original Stanford controller does not run ds4drv as a service but runs PS4Joystick which uses the code from ds4drv and produces correct values.
I am not sure if ros2 joy_node cab run reliable with ds4drv but we can write a ros node to produce the /joy topic using the Stanford code.
I need someone to confirm the issue and maybe someone knows how to fix is using just ds4drv
We run the ds4drv to handle joystick events in user space and we use ros2 joy_node to read from dev/input/js0 This device is created by ds4drv when a joystick is paired.
The values of the axis contains bogus values
The original Stanford controller does not run ds4drv as a service but runs PS4Joystick which uses the code from ds4drv and produces correct values.
I am not sure if ros2 joy_node cab run reliable with ds4drv but we can write a ros node to produce the /joy topic using the Stanford code.
I need someone to confirm the issue and maybe someone knows how to fix is using just ds4drv