how to set Axis camera IP address for FRC PC Dashboard

[Arhowk]

Are you running an m1013? I've had some problems with these. Can you confirm that your roborio is 10.te.am.2 and ds is 10.te.am.5? M1013s dont work well with mDNS.

I also had an issue where a team recompiled the dashboard and overrode the default camera ip finder to specifically use axis-camera.local which causes issues because the default LV dashboard has other camera finding techniques built in

[Greg McKaskle]

The Axis camera is connected into the bridge and unless you are doing onboard images processing, which is unlikely this year, the roboRIO isn't even involved. You are using the PCs mDNS services. You should be able to ping with the axis host name, log in from a web page using the name, and connect from he dashboard using the name. In many cases, the Axis camera host name is actually Axis-serialNumber. I'd recommend setting it to Axis-camera. Then you can access easily when devices are set to use DHCP and link-local IPs. It will also work with static, but at that point all devices will need to use static.

The default dashboard uses the camera name, as sent back by the robot code. If you hard-code that in the dashboard, it should cause no harm and in fact works around some pesky TCP reconnect bugs that can happen in the kickoff code.

Greg McKaskle

[wireties]

Originally Posted by Greg McKaskle

The Axis camera is connected into the bridge and unless you are doing onboard images processing, which is unlikely this year, the roboRIO isn't even involved. ...

...The default dashboard uses the camera name, as sent back by the robot code.

Hey Greg, if we are doing no vision processing on the roboRio how do we "send back" the camera name from the robot code?

TIA