[Mark McLeod]

Originally Posted by cpapplefamily

I wonder if this has something similar to do with our experiences a few weeks ago with our robot, driver station, and Kangaroo. This is a alink to the start of the discussion. https://www.chiefdelphi.com/forums/s...1&postcount=19
It starts at post #19 and continues from there
https://www.chiefdelphi.com/forums/s...=149295&page=2

I can't say this was the problem, but each of the IPs you chose for your Kangaroo are incorrect for field use.

Keep the last numbers .5 or greater and less than or equal to .19. 5<=IP<=19
The field begins assigning DHCP addresses at .20, but is not necessarily assigning them sequentially. Any static IP you use between .20 and .200 can randomly produce a conflict.
It's quite likely that your Driver Station or roboRIO was receiving a duplicate .20 address.

Static IPs for the Kangaroo, but dynamic IPs for the Driver Station and roboRIO will also prevent it from working with the competition pit/home dynamic IPs of 169....
For your use case I would recommend that you keep everything at consistent 10.TE.AM static IPs, both for at home and for competition.
Don't worry about your robot radio IP. You can leave it at the setting given it by the home or competition radio kiosk.