The screensteps live page lists the following caveat for the new OM5P-AC router:
Note: It is not possible to modify the configuration manually for the OM5P-AC
(from https://wpilib.screenstepslive.com/s/4485/m/13503/l/144986?data-resolve-url=true&data-manual-id=13503 ).
For our team, this is the first year we are trying to use a coprocessor (Beaglebone) and one or two axis cameras. Historically, I’ve assigned static IP’s to everything and added IP reservations for their MAC addresses on the router, this appears to be very robust on our test board.
However, it would appear we can’t set up reserved IP addresses on the OM5P-AC (no website, no ssh).
So far, things seem to be working ok… about one in five power cycles the cameras and BBB don’t show up on the network (easiest solution seems to be to reboot). I am presuming this is related to the OM5P-AC not assigning the IP addresses requested, but I haven’t fully confirmed it yet…
FYI, I’m presently using 10.17.36.11 and .12 for the cameras, and .20 for the BBB.
So, for any other teams who have many network devices, what sort of setup are you using for maximum robustness?
You might want to rethink your numbering scheme based on the home AP settings this year.
From For the 2020 season software documentation has been moved to https://docs.wpilib.org. Documentation for KOP items can still be found here. | FRC KOP Documentation
In AP mode only:
- DHCP server enabled. Serves out 10.TE.AM.11 - 10.TE.AM.111 on the wired side, 10.TE.AM.130 - 10.TE.AM.230 on the wireless side, subnet mask of 255.255.255.0, broadcast address 10.TE.AM.255
You wouldn’t be able to touch the radio settings at competition under any circumstances.
I’d set them in the 10.te.am.50-99 range. If I remember right, the DHCP only hands out 10.te.am.100-199 range.
On most devices, you can just set the device to use a static IP, no matter what the network wants it to do. I’d probably just set the BeagleBone to use a static IP that is outside of the range that the AP assigns.
Cool, thanks folks! I’ll move them out of the DHCP range tonight and confirm it all works.
Give the roborio a fixed IP of 10.TE.AM.002 (the standard prior to mDNS), and then you can use 10.TE.AM.11 - 10.TE.AM.111 for everything else on the wired side.