-
Notifications
You must be signed in to change notification settings - Fork 5
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
Issues with 2019-2020 robots #8
Comments
I have not touched this project in 2 years and I currently do not have access to any FRC team or their bots so all testing I am doing is on a simulator. |
Sorry I had misinterpreted |
The issues actually come from connecting to the robot. Using either roborio-xxxx-frc.local or the direct ip to it, it's extremely inconsistent on whether it will actually connect. |
I wonder if you should call 'client.destroy' on unsuccessful connections? Right now you're just creating a new client object -- not sure when node will decide to destroy it. |
I am currently rewriting this library to change how the socket is handled internally and to stop it from being recreated on every This version will also be much easier to read and work on so feel free to have a look at the source code once it is done. Also, all current function calls will remain the same so an upgrade will be easy. |
It might be useful for you to implement a driver station client too? The driver station provides information about where the robot is when it connects to it. The python implementation is here: https://github.com/robotpy/pynetworktables/blob/master/_pynetworktables/_impl/ds_client.py |
@rakusan2 Did you end up finishing version 2? I am wishing to use this In my team's electron dashboard but need to ensure that we won't be having issues with the client |
Hey, great work on the library! It seems that this has a lot of issues when used on bots that are 2019-2020
Is there any fix?
The text was updated successfully, but these errors were encountered: