Not working..

[niezifei]

rosrun ros_g29_force_feedback ros_g29_force_feedback_node --ros-args --params-file catkin_ws/src/ros_g29_force_feedback/config/g29.yaml
ERROR: cannot open device : /dev/input/event14

Already change the event number in .yaml file, but still not working...

[kuriatsu]

Did you publish the message?

$ ros2 topic pub /ff_target ros_g29_force_feedback/msg/ForceFeedback "{header: {stamp: {sec: 0, nanosec: 0}, frame_id: ''}, position: 0.3, torque: 0.5}"

If it doesn't work even after publishing ros topic,
please show me your config file, result of cat /proc/bus/input/devices etc.

[Farahihab]

Had the same problem. I'm guessing you're in the ros1 branch
you'll find the "/dev/input/event14" line in the g29_force_feedback.cpp file

when I changed my configuration it the g29_force_feedback.cpp file as well and it worked for me.

[kuriatsu]

Uhmm... It's strange, m_device_name is updated when the instance is created.
But anyway, thank you for your information.

[btessin]

Same here. I am using ROS Humble. The node seems to not load the parameters_file. At least the parameter device_name" and the field m_device_name are empty strings.

Setting the values hard coded works, but I don't like it xD

Btw.: Thank you for your work, it helps me a lot

[kuriatsu]

Thank you for the report.
I'm going to try to reproduce the phenomenon.

[Obandowski27]

@btessin By any chance can you show me how did you hardcore the parameters?
I'm currently facing the same issue with ROS foxy

[kuriatsu]

ros-g29-force-feedback/src/g29_force_feedback.cpp

Line 24 in 3bd1860

std::string m_device_name;

m_device_name = "event17"

You may need to comment out

ros-g29-force-feedback/src/g29_force_feedback.cpp

Line 78 in 3bd1860

get_parameter("device_name", m_device_name);

[Obandowski27]

Thanks a lot! It is working now

[btessin]

This is exacly what I did ;-) Sorry for the late reply.