Axis 206 camera not streaming

[willishf]

Based on advice from Michael Tid via email we updated with the latest axis firmware, added the FRC userid and set the camera to get IP via DHCP. The camera is plugged into port 2 via crossover cable. All of the problems we had experienced with v28 and the camera not working went away. Axis provides software for autodiscovery so it sounds like this is part of the cRIO library for finding the camera.

We ended up taking the camera completely out of the robot config because we were having problems during practice at regionals with a non-responsive robot. I have seen on more than one occasion the video lag live by 3-5 seconds which tells me the cRIO will buffer and send all the video. If you are having bandwidth/communication issues then critical commands for driving the robot are probably getting stuck in the queue behind the video.

We also moved the radio, got rid of the radio shack power connector on the radio to try and address the problem. We did manage to get reliable communication but not sure what fixed the problem. I think it is a combination of factors.

[byteit101]

Originally Posted by willishf

Based on advice from Michael Tid via email we updated with the latest axis firmware, added the FRC userid and set the camera to get IP via DHCP.

Where is this updated firmware you speak of located?

DHCP? does the cRIO have a DHCP server on it?

[Robby Unruh]

We have our camera on port 2 in the cRIO, with it's default IP 192.168.0.90. We're able to see our camera just fine with the original dashboard. I'll tell you if it works for us at our meeting tonight with ZomB, it could be another bug.

[Greg McKaskle]

The cRIO does not have a DHCP server on it, but once the camera times out waiting for a DHCP server, it will self-assign to 192.168.0.90.

If you had the camera statically set to 0.90 and the cRIO port two also set to 0.90, that would cause a problem with camera communications.

I believe that both ports on the cRIO have link LEDs. Use them to determine if the cRIO may have a loose enet connector. Also test a different crossover cable and wiggle the connector at the camera.

Swapping cRIO and seeing a temporary improvement doesn't really convince me of what the problem is.

As for the lag, TCP buffers don't wait in line. The lag would be per port. If you have large images and lots of them, you could put a bigger CPU load on the cRIO, but other than that, the UDP packets from the DS and the TCP packets to and from the camera and DS have little to do with one another.

Greg McKaskle