Gamepad Topic interferes with rosbag playback

[NLS-04]

When playing back a rosbag while connected to a rover, the messages published by the connected gamepad try to publish on the vel control topic interfering with rosbag vel control topics.

[NLS-04]

Two possible solutions:

1. dont start gamepad_driver node
2. add new functionality to gamepad_driver to enable/disable velocity message publishing

@maxgmoe what do you think?

[nuechter]

Tha's why in the old / ROS1 volksbot you had to start the joystick in a separate fashion. We should switch to this as well. This would also enable a remote joystick.

[NLS-04]

The same still applies as in ROS1.

The gamepad_driver node is a standalone node of the gamepad_driver packages and can be omitted at any time. However, we suspect that students do not realize that the node can be omitted as it is included in the launch script praktium_launch.py and started by default.

The question now is, do we segregate the gamepad_driver node outside the praktikum_launch.py (like in the old ROS1 version), or do we create a separate launch script which does not include the gamepad_driver node.

@nuechter as you mentioned, i would also lean towards removing the gamepad_driver node from the launch script.

[NLS-04]

@nuechter should this be fixed after AMS or ASAP?
I am currently also working on a revised README/Documentation for this project and would add this detail as soon as this fix is effective.

[nuechter]

After AMS.

[nuechter]

Yes, but the launch files for ROS1 did not include the joystick (messtechnikpraktikum.launch) and therefore this behavior was not observed. Thus, I recommend to remove the joystick from praktikum_launch.py and launch it separately.

…

On 5/13/26 13:00, Nico Schubert wrote: *NLS-04* left a comment (JMUWRobotics/volksbot#11) <https://github.com/ JMUWRobotics/volksbot#11#issuecomment-4440213240> The same still applies as in ROS1. The |gamepad_driver| node is a standalone node of the |gamepad_driver| packages and can be omitted at any time. However, we suspect that students do not realize that the node can be omitted as it is included in the launch script |praktium_launch.py| and started by default. The question now is, do we segregate the |gamepad_driver| node outside the |praktikum_launch.py| (like in the old ROS1 version), or do we create a separate launch script which does not include the | gamepad_driver| node. @nuechter <https://github.com/nuechter> as you mentioned, i would also lean towards removing the |gamepad_driver| node from the launch script. — Reply to this email directly, view it on GitHub <https://github.com/ JMUWRobotics/volksbot#11#issuecomment-4440213240>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ AAWJLZJOF6JNHVGYFPZPTDT42RIWPAVCNFSM6AAAAACY3GHMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINBQGIYTGMRUGA>. Triage notifications on the go with GitHub Mobile for iOS <https:// apps.apple.com/app/apple-store/id1477376905?ct=notification- email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/ details?id=com.github.android&referrer=utm_campaign%3Dnotification- email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>