The Axis Camera Setup Utility is documented at
https://dylan-frc-docs.readthedocs.io/en/latest/docs/software/vision-processing/configuring-an-axis-camera.html
but the utility did not get installed with LabVIEW and the Game tools this year. Is the setup utility still available or is there a different procedure?
I know there are USB cameras but I’m more familar with these cameras for vision processing.
I think they ceased to support/upgrade it due to it’s age and the relative lack of AXIS cameras in the KOP for several years now.
You can probably install last seasons Game Tools to get it, then reinstall this year’s Game Tools.
P.S.
I have it on older netbooks if you want me to look for the old installer.
I looked up 2019 and 194 teams were still using an Axis camera that season.
Out of curiosity, why do you need to configure an Axis Camera? You haven’t been able to buy the cameras for years, so presumably any camera you already have would be configured.
The link you posted is not official documentation. It appears to be a very old copy of frc-docs from 2019, while it was being ported. The correct link is http://docs.wpilib.org
Thanks. We’ll use that next time.
I think it’s good to set it up each year to clear out any unknown network or image settings and to remind myself or teach a student how to use it in case something gets mis-configured later and needs a reset. This does go against the philosophy of ‘If it’s not broke, don’t fix it’ but if something get’s changed unintentionally during competition, I’ll be happy I posted this now. It would not be that hard for the reset button to get pressed accidentally at the wrong time. ‘What can go wrong, will go wrong.’
Also, 8069 was sponsored/inherited the camera from 1094 so at a minimum we need to change the IP address.
Gotcha.
FWIW, I don’t think (??) there was anything magical to the camera config utility itself. Doing a factory reset on the camera, putting it on a network where it could get its default IP address, going to its online settings page, and punching in a 10.TE.AM.XX address should work as well… at least it did on the three or so cameras I configured years ago.
One thing to potentially watch out for, the cameras I’ve used in the past have a noticeable amount of lag (~250-500ms?) in the streamed image (which makes sense, given their designed purpose. One alternate is a raspberry pi, running a Pi cam, and the WPILib Pi image - it’ll fit the same spot in the system architecture (broadcast the camera as an .mjpg stream with some web-based configuration), but is more purpose-built for the application. Not to say you have to switch (really just depends on your camera model and how much you care about latency), but just to point to the next step if needed…
Thanks, I had not considered the lag may be that long. That may be a consideration.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.