View Single Post
  #25   Spotlight this post!  
Unread 14-03-2015, 20:46
FrankJ's Avatar
FrankJ FrankJ is offline
Robot Mentor
FRC #2974 (WALT)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2009
Location: Marietta GA
Posts: 1,931
FrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond repute
Re: RoboRIO / FMS / mDNS / lessons learned

Not sure what the 2015 FMS DHCP does, but in years past with static IPs... Every thing except the crio had 255.0.0.0 subnet masks (the older robot routers didn't, that is a special case & they didn't have to talk to anybody.) That means FMS, driver stations could see and talk to each other. crios had a subnet mask of 255.255.255.0 puts them in a different sub net class & they should not talk to anybody in a different subnet. But one quirkieness of IP subnets 10.te.am.xx subnet mask 255.0.0.0 looks be the same subnet as 10.te.am.xx subnet mask 255.255.255.0. So the CRIO will see and talk to the team driver station, camera, anything 10.te.am.xx and nothing else. Which is generally why you or not supposed to mix subnet classes on the same network.

Back in the pit, if you somehow have not cycled power to the radio, the roborio will hold its IP. Or if they are slow reconfiguring the field radio & it reconnects to the robot. It also takes a while for your computer to drop to the default IP address because it is hoping that a DHCP will assign one to it. You could really confuse things and run a DHCP server on your drive station.
__________________
If you don't know what you should hook up then you should read a data sheet
Reply With Quote