Repository Summary
Checkout URI | https://github.com/joshnewans/joy_tester.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-11-16 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
joy_tester | 0.0.2 |
README
joy_tester
This is a very simple GUI program for testing joysticks in ROS.
More specifically, it displays the messages of a sensor_msgs/Joy
topic in a more user-friendly format.
Usage
ros2 run joy_tester test_joy
By default it subscribes to the /joy
topic, but this can be remapped as with any other ROS node (e.g. with --ros-args -r joy:=other_joy
).
Particularly helpful (compared to a topic echo
) is that it displays the axis/button numbers which saves time and errors in counting them manually.
To Do
- Clean up the code, particularly GUI element placement (was a very rough first go)
- Add functionality for sending
sensor_msgs/JoyFeedback
(e.g. LED, rumble) back to controllers - Some way to assist in calibration?
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Repository Summary
Checkout URI | https://github.com/joshnewans/joy_tester.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-11-16 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
joy_tester | 0.0.2 |
README
joy_tester
This is a very simple GUI program for testing joysticks in ROS.
More specifically, it displays the messages of a sensor_msgs/Joy
topic in a more user-friendly format.
Usage
ros2 run joy_tester test_joy
By default it subscribes to the /joy
topic, but this can be remapped as with any other ROS node (e.g. with --ros-args -r joy:=other_joy
).
Particularly helpful (compared to a topic echo
) is that it displays the axis/button numbers which saves time and errors in counting them manually.
To Do
- Clean up the code, particularly GUI element placement (was a very rough first go)
- Add functionality for sending
sensor_msgs/JoyFeedback
(e.g. LED, rumble) back to controllers - Some way to assist in calibration?
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Repository Summary
Checkout URI | https://github.com/joshnewans/joy_tester.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-11-16 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
joy_tester | 0.0.2 |
README
joy_tester
This is a very simple GUI program for testing joysticks in ROS.
More specifically, it displays the messages of a sensor_msgs/Joy
topic in a more user-friendly format.
Usage
ros2 run joy_tester test_joy
By default it subscribes to the /joy
topic, but this can be remapped as with any other ROS node (e.g. with --ros-args -r joy:=other_joy
).
Particularly helpful (compared to a topic echo
) is that it displays the axis/button numbers which saves time and errors in counting them manually.
To Do
- Clean up the code, particularly GUI element placement (was a very rough first go)
- Add functionality for sending
sensor_msgs/JoyFeedback
(e.g. LED, rumble) back to controllers - Some way to assist in calibration?
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Repository Summary
Checkout URI | https://github.com/joshnewans/joy_tester.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-11-16 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
joy_tester | 0.0.2 |
README
joy_tester
This is a very simple GUI program for testing joysticks in ROS.
More specifically, it displays the messages of a sensor_msgs/Joy
topic in a more user-friendly format.
Usage
ros2 run joy_tester test_joy
By default it subscribes to the /joy
topic, but this can be remapped as with any other ROS node (e.g. with --ros-args -r joy:=other_joy
).
Particularly helpful (compared to a topic echo
) is that it displays the axis/button numbers which saves time and errors in counting them manually.
To Do
- Clean up the code, particularly GUI element placement (was a very rough first go)
- Add functionality for sending
sensor_msgs/JoyFeedback
(e.g. LED, rumble) back to controllers - Some way to assist in calibration?
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
Repository Summary
Checkout URI | https://github.com/joshnewans/joy_tester.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-11-16 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
joy_tester | 0.0.2 |
README
joy_tester
This is a very simple GUI program for testing joysticks in ROS.
More specifically, it displays the messages of a sensor_msgs/Joy
topic in a more user-friendly format.
Usage
ros2 run joy_tester test_joy
By default it subscribes to the /joy
topic, but this can be remapped as with any other ROS node (e.g. with --ros-args -r joy:=other_joy
).
Particularly helpful (compared to a topic echo
) is that it displays the axis/button numbers which saves time and errors in counting them manually.
To Do
- Clean up the code, particularly GUI element placement (was a very rough first go)
- Add functionality for sending
sensor_msgs/JoyFeedback
(e.g. LED, rumble) back to controllers - Some way to assist in calibration?
CONTRIBUTING
Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.