Quote:
Originally Posted by Greg McKaskle
please report the issues that caused you to go static.
Greg McKaskle
|
Here is a list of issues that my team was having that went away when we gave the robot a static ip address.
- Driver Station sometimes does not connect to the robot after a Java code deploy (Communications and Robot Code status are both red in the Driver Station). Rebooting the RoboRIO temporary resolves this.
- A Java deploy from Eclipse on Windows sometimes can not find the robot at roboRIO-3928-FRC.local. Again, rebooting the RoboRIO temporary resolves this.
- Riolog in Eclipse is empty, it does not show any printouts or messages from the roboRIO.
Quote:
Originally Posted by Greg McKaskle
I understand that static IPs are a solution of sorts, but they introduce other issues, especially when that robot shows up at an event. The robot won't connect to the field, so the CSA or FTA discovers and changes the roboRIO and DS laptop settings. But that may break the programming laptop connectivity, so the team may change it back again, ...
Greg McKaskle
|
My team went to multiple competitions last year with a static ip and had no issues. There are multiple people on my team that know how to change the roboRIO's network settings if problems do arise.
Before 2015 the cRIO had a static ip address of 10.te.am.2 by default. Does anyone know why this was changed? I can not think of any case where two robots with the same team number would be on the same network.