QDriverStation detects joysticks but doesn't send to robot

Question

QDriverStation detects joysticks but doesn't send to robot

retrodaredevil opened this issue 7 years ago · comments

Information on what I'm running:
Log created on: Jan 24 2018 - 18:34:53 PM
LibDS version: 2.2
Operating System: Ubuntu 16.04.3 LTS
Application name: QDriverStation
Application version: 18.01

The problem is the same as this: #46 except on linux. The log connects, enables, disable the robot fine and the SmartDashboard even works perfectly except when I try to use a joystick on it, it detects it, but doesn't send it and I get an error when I call a joystick.getButton() in my code.

The log doesn't have any errors in it, just debug although I'd be happy to add other log files if that would help.

Another thing that would be nice is to be able to see the ports that the joysticks are on since right now it just shows a list of joysticks. I've tried this with a ps4 controller and a generic joystick. I've only tested this on my computer but I have yet to get the controllers working.

Alex Spataru · Answer 1 · Thu Jan 25 2018 23:40:53 GMT+0800 (China Standard Time)

Could you try to use the virtual joystick to control your robot (and report back the results)? This can help me to know if this is an issue with SDL, or with the LibDS library itself.

Thanks!

Lavender Shannon · Answer 2 · Sun Jan 28 2018 05:15:50 GMT+0800 (China Standard Time)

Tested it with virtual joystick and nothing.

Skylar Gray · Answer 3 · Wed Jan 31 2018 08:13:30 GMT+0800 (China Standard Time)

Same problem here, on Elementary OS Loki.

Alex Spataru · Answer 4 · Sun Feb 04 2018 10:24:15 GMT+0800 (China Standard Time)

Sorry for the late reply. Maybe the communication protocol has changed a little bit since last year, hopefully this is not the case.

Skylar Gray · Answer 5 · Sun Feb 04 2018 10:28:31 GMT+0800 (China Standard Time)

I think it probably is the case, because the robots I tested it with were 2018 robots -Gabriel McMillan On Sat, Feb 3, 2018 at 6:24 PM -0800, "Alex Spataru" <notifications@github.com> wrote: Sorry for the late reply. Maybe the communication protocol has changed a little bit since last year, hopefully this is not the case. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Alex Spataru · Answer 6 · Sun Feb 04 2018 10:34:23 GMT+0800 (China Standard Time)

Does your team still have access to 2015-2017 robots? If so, could you please try controling those robots with the QDriverStation?

Unfortunately, I am not into FRC anymore due to college, which makes testing LibDS and QDriverStation very difficult for me.

Skylar Gray · Answer 7 · Sun Feb 04 2018 10:35:31 GMT+0800 (China Standard Time)

I do, however it will be a while before I can test it, I will get back to you on that. -Gabriel McMillan On Sat, Feb 3, 2018 at 6:34 PM -0800, "Alex Spataru" <notifications@github.com> wrote: Does your team still have access to 2015-2017 robots? If so, could you please try controling those robots with the QDriverStation? Unfortunately, I am not into FRC anymore due to college, which makes testing LibDS and QDriverStation very difficult for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Eamon Niknafs · Answer 8 · Sun Feb 04 2018 10:39:42 GMT+0800 (China Standard Time)

I have a 2016 robot and a current one. I’ll check on that on Monday, if no one has by then.

…

On Feb 3, 2018, at 6:35 PM, fearxzombie ***@***.***> wrote: I do, however it will be a while before I can test it, I will get back to you on that. -Gabriel McMillan On Sat, Feb 3, 2018 at 6:34 PM -0800, "Alex Spataru" ***@***.***> wrote: Does your team still have access to 2015-2017 robots? If so, could you please try controling those robots with the QDriverStation? Unfortunately, I am not into FRC anymore due to college, which makes testing LibDS and QDriverStation very difficult for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Skylar Gray · Answer 9 · Sun Feb 04 2018 10:42:12 GMT+0800 (China Standard Time)

Got it. -Gabriel McMillan On Sat, Feb 3, 2018 at 6:39 PM -0800, "Eamon Niknafs" <notifications@github.com> wrote: I have a 2016 robot and a current one. I’ll check on that on Monday, if no one has by then.

On Feb 3, 2018, at 6:35 PM, fearxzombie ***@***.***> wrote: I do, however it will be a while before I can test it, I will get back to you on that. -Gabriel McMillan On Sat, Feb 3, 2018 at 6:34 PM -0800, "Alex Spataru" ***@***.***> wrote: Does your team still have access to 2015-2017 robots? If so, could you please try controling those robots with the QDriverStation? Unfortunately, I am not into FRC anymore due to college, which makes testing LibDS and QDriverStation very difficult for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Alex Spataru · Answer 10 · Fri Aug 10 2018 12:07:26 GMT+0800 (China Standard Time)

We'll move discussion of this issue to #58, which deals with the 2018 protocol implementation. Thanks for the reports!