Camera not working properly...

[SudoSammich]

This is our first year running the camera on the cRIO, and we're having problems troubleshooting the camera networking.

We've completely wiped our wireless setup from last year and re-set up everything so it interfaces nicely, but the camera won't connect when we plug it into the cRIO. If we plug the camera into the router, we can connect, login and view the camera feed, but once we plug the crossover cable into the second port on the cRIO, nothing. We can't draw data, connect or even ping the camera, it just times out.

Our static IP setup is as follows:
10.5.14.1 = Gaming Adapter
10.5.14.2 = cRIO Port 1
10.5.14.3 = Open (camera is set to this static IP, but it won't return a ping)
10.5.14.4 = Linksys router
10.5.14.5 = Competition PC
10.5.14.6 = Open

Anybody else run into this problem? Any troubleshooting info? Thanks.

[Zme]

you can ping the camera normally when it is plugged into the router?
that seems a bit odd to me as with an ip of 192.168.0.90, you shoouldn't be able to access it from the same subnet that the robot is on.
the camera code provided should be able to access it on port two with the above ip
also if it is in port two then you should not be able to ping it as i don't believe that the crio will forward packets between the two ports unless explicitly told to do so, but i an by no means an expert on what it will or will not do

how is the camera setup?

[Mark McLeod]

Yea, your camera IP address is incorrect for use on port 2 of the cRIO.

The IP address you have it set to will only work through a router connection or directly to your PC.

For cRIO use : IP=192.168.0.90
For network use: IP = 10.xx.yy.zzSee the camera setup instructions (http://www.usfirst.org/uploadedFiles/Robotics_Programs/FRC/Game_and_Season__Info/2011_Assets/Kit_of_Parts/How_to_Configure_Your_Camera.pdf), but read them carefully. The note on the IP difference kind of blends in.

[SudoSammich]

Thanks, found the problem! We had been using the camera as if it were any other part of the network, so we had the IP address set incorrectly. Gotta read the docs a bit more closely in the future.:yikes: