View Single Post
  #7   Spotlight this post!  
Unread 23-02-2016, 15:00
Thad House Thad House is offline
Volunteer, WPILib Contributor
no team (Waiting for 2021)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2010
Location: Thousand Oaks, California
Posts: 1,068
Thad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond reputeThad House has a reputation beyond repute
Re: Static IPs on the field

Quote:
Originally Posted by JohnGilb View Post
I concur - throughout the season, while using MDNS, I have seen situations where one or more of the below things working while the others don't:
- Ping via CMD window
- Ping via Powershell window
- FRC Driver Station
- SmartDashboard
- SFX (SmartDashboard 2.0)
- Deploy code via Eclipse
- roboRIO web portal

It's really a mess. mDNS is great when it's working, but when it isn't, we have to just continuously reboot the robot/computer/disconnect & reconnect adapters/plug in a cable, then unplug it and wait 10 seconds/etc... and just hope that something will work.

Static IPs were inconvenient but relatively bulletproof - and in the world of FRC robotics I often value robustness over feature richness.
Plus if you do have a DHCP server on the radio, you get most of the convenience back. IP's would still get handed out to the DS. Plus mDNS never really has worked on things like camera's and offboard processors, which we just set static anyway.
__________________
All statements made are my own and not the feelings of any of my affiliated teams.
Teams 1510 and 2898 - Student 2010-2012
Team 4488 - Mentor 2013-2016
Co-developer of RobotDotNet, a .NET port of the WPILib.