Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No Comms on 2016 protocol w/ 2017 robot #7

Open
benjaminmcd opened this issue Feb 14, 2017 · 2 comments
Open

No Comms on 2016 protocol w/ 2017 robot #7

benjaminmcd opened this issue Feb 14, 2017 · 2 comments

Comments

@benjaminmcd
Copy link

With all settings configured, I am getting no Comms on a new router and roboRio.
@alex-spataru
Copy link
Member

Hi, I completely missed your issue report. Sorry for that. Can you try to install the latest version (from the Play Store) and check if your issue is still present? Also, try to input your robot's static IP if you still don't get comms, mDNS is not supported on all Android devices AFAIK...

@HeroCC
Copy link

HeroCC commented Mar 28, 2019

I was able to get our 2019 bot to connect for a second, very intermittently, but it only moved when the joystick was all the way forward, no in-between

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@HeroCC @alex-spataru @benjaminmcd