[Mr. Lim]

Originally Posted by nickpeq

It will need to be connected to the cRIO to use tracking code on the robot. And it worked last year connected through the cRIO, as well as there being an option in the Axis camera utility specifically for connected through the cRIO.
Also, we have had the same error when connected through the router, however I haven't tested this as extensively.

If you have advice on using the router (should it start working on router only) for vision tracking, preferably without the involvement of LabView, I would still be grateful for that as well.

This is a change that has been made from last year. Our robot last year was plugged into port 2 of the cRIO. This year, the new 4-slot cRIO only HAS one ethernet port. The camera implementation has changed, and routing your camera through port 2 does not appear to be supported anymore.

Last year, the camera was also kept on the 192.168.x.x domain, which has also changed. The 2012 setup utility will change the IP address to 10.xx.yy.11.

Even though the camera is connected through the router, the cRIO will still be able to capture images from it using the same WPILib functions as last year. We are running vision code on our 2012 cRIO in this manner.

Hooking it up this way will also improve your driverstation video feed, and reduce load on your cRIO. The cRIO is no longer running a video server that relays the images from the camera to the driver station. Your driverstation can now retrieve video directly from the camera.