By FRC convention static IP addresses use .1 for the radio, .2 for the roboRIO, .4 for an AP to work with the robot radio as bridge, .5 for the DS laptop Ethernet port, .6 for a separate programming PC, .9 for at home DS wireless port, .11 for the first IP camera.
staying somewhat with the conventions makes it easier for others to help you debug, but that’s all.
I want to point out that your Axis should always be available at axis-camera.local. It uses a similar mDNS setup as the robot, so anyone who has the driver station or any other mDNS software (Bonjour through ITunes, etc) will see the camera there.
This is what worked for us. Prior to us figuring this out (but after our IP address that we used in the shop stopped working) we would scan the IP range before every match, find the camera, and enter it in the camera feed. This worked, although it was just another annoying thing on our already huge list of annoying things to do to set up for a match.
Ours didn’t work the entire first day. The FTA’s tried to get it working but it needed a static ip and we had to set up the windows host file to force axis-camera.local to 10.29.59.11 (our camera’s static ip). Just wouldn’t be seen on the dashboard until we forced windows to see it. Mdns just wasn’t cutting it.
It’s very unfortunate that using static IPs is has become obfuscated. It pretty much cost us the first 3/4 of our first event as I stupidly believed that static IPs wouldn’t work and/or were against the rules. It would be nice if the documentation was explicit, or at least it said somewhere that it is okay to do it if you follow these guidelines.
After I read on chiefdelphi.com that people were using static IDs and it was indeed allowed, I then looked for what IDs we could use. That wasn’t easy to find. When I finally found what I was looking for, it is stupidly simple. So here it goes:
Find the documentation for the FRC control system from 2014 (or earlier). 2) Set the IPs as described. 3) Profit
[sub minor rant]What bothered me is that they could have just said “you can continue to use the same static IP ranges from past years”.[/sub minor rant]
For those without past years’ documentation, here it is:
Set roboRIO to 10.xx.yy.2
Set driver station to 10.xx.yy.5
Set camera 1 to 10.xx.yy.11
Set camera 2 to 10.xx.yy.12
(where xx.yy is your team number, so 2112’s roboRIO would be 10.21.12.2 and team 51’s would be 10.00.51.2).
This is the address of something on the field (router, AP interface, etc.) that is set as the gateway for the roboRIO as part of the DHCP address served by the field (you can see this if you USB tether to the robot and pull up the web interface without turning the robot off after a match.
Another observation from this, and also having major pain in the a$$ with mdns in our setup, still to be “working” but no root cause of why Aaron spent two hours in our pit on Thursday at Waterford… I feel for you Chris.
Please note that once your radio is programmed at the event, the DHCP server is turn off on your robot radio. The field is the only DHCP server while at the event.
So when you are in your pit, and testing there is no DHCP server to hand out IP addresses, so everything kind of defaults back to the 169. address space. For others this seems to work… For us, not so much…
When we were in the pit at Waterford, I used an old dlink configured to our home settings, when I needed to test and program. (which was all the time)
Another important thing to note is that if you specify a the default gateways as 10.TE.AM.1 it appears that all traffic goes to the fms. This caused for significant delays to be introduced only when we connected to the field as data was being passed from the Rio to the FMS, then from the FMS to the Kangaroo, then from the Kangaroo to the FMS, and finally from the FMS to the Rio. In reality it was probably also going through the Driver Station as the FMS does not connect directly to the robot, but short of doing a traceroute I couldn’t tell you definitively.
In reality this traffic should have been able to stay local and should not have been subject to the bandwidth limitations the FMS imposes.
In windows you can leave that gateway empty and be all right. On the rio, it can be configured via the web dashboard and should probably be set to 0.0.0.0 as suggested by the images in the screensteps document you listed.
we had our own problems (added a second camera, but had trouble seeing it on the field).
But as to the Field radio configuration, our own ad-hoc solution was to have two new radios, one for “Field” configuration, one configured for use just as back home for “Pit / Build”. We would just switch out the radio in the pit (and use the same test radio on the practice field).
(de-)mentor, FRC 3045 Gear Gremlins (formerly SWAT).
Parroting what Mark said. PLEASE don’t do this. None of us (CSAs, FTA[A]s, Robot Inspectors, etc.) like having to track down rogue wireless access points at events, but we will if we see them. It’s against the rules(Mark quoted them already) and has potential to disrupt the game in one form or another.
And no, simply refusing to broadcast the SSID does NOT mean we can’t find it