Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Axis camera IP changes during the game (http://www.chiefdelphi.com/forums/showthread.php?t=145775)

ROULT 15-03-2016 18:17

Axis camera IP changes during the game
 
We have configured the axis camera according to the instructions in WPILib 2016.

At the beginning of matches, the camera has effectively an IP corresponding to our team's number (10.44.3.5) but at the half of the game, it changes to something like 192.168...

Has anybody faced the same issue or knows how to solve it?

Thanks in advance for your help and time.

TylerS 15-03-2016 18:19

Re: Axis camera IP changes during the game
 
Are you using DHCP to assign the axis camera IP or is it static? I recommend going static and retesting to see if that resolves the issue.

kiettyyyy 15-03-2016 18:37

Re: Axis camera IP changes during the game
 
There's a setting in there that has it fall back to a 192.168 IP by default if it can't acquire or loses its DHCP assignment.

You can turn that off. Make it either DHCP only or Static IP only.

mhaeberli 15-03-2016 19:08

Re: Axis camera IP changes during the game
 
When making it static only, should one specify a router (like 10.30.45.1, or 10.30.45.129)?
Thanks,
Martin Haeberli
(de-)mentor, FRC 3045 Gear Gremlins (formerly SWAT)

kiettyyyy 15-03-2016 19:32

Re: Axis camera IP changes during the game
 
I've had good luck of setting it to 10.xx.yy.250 on actual fields at events I've CSA'd at.

Static IPs are the last resort. We're typically able to get them all fixed up while using mDNS and DNS.

Mark McLeod 15-03-2016 20:02

Re: Axis camera IP changes during the game
 
The field DHCP serves addresses in the .20 to .199 range if I remember correctly.
So static addresses for cameras or other IP devices can use .10 to .19 safely.

mhaeberli 15-03-2016 20:25

Re: Axis camera IP changes during the game
 
The Axis camera setup page:

http://wpilib.screenstepslive.com/s/...an-axis-camera

for the 2016 control system says you can use the range .3 to .19 safely for fixed IP addresses.

Quote:

Originally Posted by Mark McLeod (Post 1557921)
The field DHCP serves addresses in the .20 to .199 range if I remember correctly.
So static addresses for cameras or other IP devices can use .10 to .19 safely.

Martin Haeberli
(de-)mentor, FRC 3045 Gear Gremlins (formerly SWAT)

Mark McLeod 15-03-2016 21:16

Re: Axis camera IP changes during the game
 
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.

BenjaminWard 15-03-2016 22:05

Re: Axis camera IP changes during the game
 
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.

Poseidon5817 15-03-2016 22:08

Re: Axis camera IP changes during the game
 
Quote:

Originally Posted by BenjaminWard (Post 1558004)
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.

hardcopi 15-03-2016 23:24

Re: Axis camera IP changes during the game
 
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.

Chris Hibner 16-03-2016 08:12

Re: Axis camera IP changes during the game
 
[minor rant]

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.

[/minor rant]


[important part]

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:

1) 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).

RufflesRidge 16-03-2016 09:27

Re: Axis camera IP changes during the game
 
Quote:

Originally Posted by mhaeberli (Post 1557945)
for the 2016 control system says you can use the range .3 to .19 safely for fixed IP addresses.

It's wrong (slightly). You should not use .4.

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.

Joe Ross 16-03-2016 09:38

Re: Axis camera IP changes during the game
 
Quote:

Originally Posted by Chris Hibner (Post 1558120)
[minor rant]

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.

[/minor rant]

It's documented in this years documentation. http://wpilib.screenstepslive.com/s/...g-at-the-event

Quote:

Originally Posted by Chris Hibner (Post 1558120)
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).

As documented at the link above, the driver station netmask must be 255.0.0.0 or else it won't connect to FMS.

tr6scott 16-03-2016 09:40

Re: Axis camera IP changes during the game
 
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)


Thanks for the info on the static IP's


All times are GMT -5. The time now is 01:31.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi