Axis Camera responding in the Vision Assistant but not in WindRiver

[DanDon]

Hey all-

The camera is responding perfectly when connected to the computer by crossover in the Vision Assistant, but when it's plugged into port 2 on the CRIO with the crossover and running the SimpleTracker code with HSL thresholds widened enough to catch an image, the code fails to find any particle.

I've already run the Axis Camera Setup Utility, and both FRC/FRC and root/admin users exist. The camera is setup with IP 192.168.0.90. I don't know what I'm missing, but I'm sure that I'm missing something as teams HAVE been able to track particles with the WindRiver SimpleTracker example.

Any help would be greatly appreciated-
Dandon

[kyungjin]

I think this is a problem many of us, including myself, are having. I haven't tried running any code when the camera is connected to the PC (I'll try it when I go to school in a few hours) but it all feels useless to me if it's not going to work when connected to the cRIO.

It's bad enough that there is poor documentation for the implementation of cameras in WindRiver... Hopefully FIRST or someone else will figure out this irritation and post step-by-step instructions sometime soon...

[jacobhurwitz]

When we connect the camera directly to the computer with a crossover cable (and set the computer's IP to 192.168.0.6), we can open up the NI Vision Assistant, set the Axis' IP as 192.168.0.90, and acquire photos.

When we connect the camera to port 2 on the cRIO (and change the computer's IP back to 10.xx.yy.6 and connect all the cables properly), we can "see" the camera image by running LabVIEW, but we can't connect using the NI Vision Assistant no matter what IP we try for the Axis.

I guess this just means that, to use the Vision Assistant, you have to connect the camera directly?

[Mark McLeod]

Yes, the Vision assistant will only work directly with the camera while it's connected to your PC.