-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
controller_type:="analog" causes crash #50
Comments
If you run the ros joy node and echo the /joy topic, what values change when you press the left trigger and the right trigger? This is probably an issue with a different button/axis mapping on the ros topic. We use either a logitech wireless gamepad or a wired Xbox 360 gamepad. If the mapping is different, you'll need to remap the button configuration with something like joystick_remapper. |
What I get is: "axes: [0.0, 0.0, 1.0, -0.0, 0.0, 1.0]", so axis 2 and 5 (if counting starts on 0). |
Ah, I see. The controllers we've tested add the cross keys to the axes array instead of the buttons array, so the teleop code is polling for out of range values. For now I can upload a quick fix so it doesn't crash on you. The cross key functionality (displaying help in the terminal) won't work, but you should be able to control the arm. |
Try pulling from the develop branch now. I can do a more complete fix later! |
Thank you! I have tried it and it works for me. |
I'm trying to run jaco_teleop with jaco2 as follows, with a Xbox 360 wireless gamepad:
roslaunch jaco_teleop joystick_teleop.launch controller_type:="analog"
After calibrating I get the following error:
_terminate called after throwing an instance of 'std::out_of_range'
what(): vector::M_range_check
This does not happen with "digital", but the I can't control the arm properly.
(this is for the version through apt-get, I'm in the process of testing it after compiling from source)
The text was updated successfully, but these errors were encountered: