Static IPs on the field

[Alan Anderson]

Originally Posted by dvanvoorst

Using static IPs was not an issue last year. As CSA I helped a handful of teams switch everything to static to resolve issues with communicating with their Axis cameras. This was done after consulting with FIRST technical support. This provided consistent camera operation both in the pits and on the field.

A counterpoint from another CSA:

I too helped a few teams go full-static IP in order to get their Axis cameras to work in the pit. In some cases this caused them to fail to get an FMS connection on the field until they set the Driver Station back to dynamic, though we never pinned down exactly why it wouldn't work. The defaults and fallbacks should have made everything happy.

The more stable fix was to keep everything dynamic and reconfigure the camera with the expected "axis-camera" name. This never failed on the field. It was only an issue off the field if the team's computer was one of the few to be unreasonably reluctant to release a DHCP-assigned ID, and the workaround of disabling/reenabling the Ethernet device always worked in that case.

[Fauge7]

yeah last year was funny...I made my team use a static ip because my vision program didnt like the non static. we NEVER had any connection problem but some of the other teams did when they had a non static ip. I told them to switch to static and helped them do it and boom, they had a working robot again! I was even told by a fms guy that if we had any connection problems it would be our fault...well we didnt...I would go with the static ip and will probably encourage my team to do so...

[cbf]

People -- the OpenMesh OM5P-AN radio can run a DHCP server. Enable it!

Then set a DHCP reservation to put your Robrio at the .2 address (e.g. for us that's 10.28.77.2). Set a reservation for your IP camera, if you have one (I think the old convention was the use the .5 address for the camera, or was it .11?). The OM5P-AN should be at the .1 address of course.

This is much better than statically assigned addresses because you don't have to worry about manually changing the Robrio, drive laptop, and/or camera back and forth between static and dynamic address assignment when you're testing, or at the competition -- or simply moving the laptop connection from the robot to your local WiFi because you to look something up on the Internet.

[RufflesRidge]

Originally Posted by cbf

People -- the OpenMesh OM5P-AN radio can run a DHCP server. Enable it!

Then set a DHCP reservation to put your Robrio at the .2 address (e.g. for us that's 10.28.77.2). Set a reservation for your IP camera, if you have one (I think the old convention was the use the .5 address for the camera, or was it .11?). The OM5P-AN should be at the .1 address of course.

This is much better than statically assigned addresses because you don't have to worry about manually changing the Robrio, drive laptop, and/or camera back and forth between static and dynamic address assignment when you're testing, or at the competition -- or simply moving the laptop connection from the robot to your local WiFi because you to look something up on the Internet.

This will not work at the event. Your radio will be programmed with a password by the radio kiosk at the event and you won't be able to enable the DHCP server.

[fsilberberg]

Originally Posted by RufflesRidge

This will not work at the event. Your radio will be programmed with a password by the radio kiosk at the event and you won't be able to enable the DHCP server.

Not only will this not work at the event, it will actually break your connection to the field. FMS runs it's own dhcp server.