Camera Communication Error

[Pirate programe]

I ran the Setup Axis Camera tool on our 2011 Axis 206 camera, set the accounts and such, then attempted to run the Camera Performance Example project on the robot, but got this error:

Watchdog Expiration: System 3, User 2
ERROR<code> -44003 occured at WPI_CameraIssue HTTP Request with Authentication.vi>>WPI_CameraIssueGet Enum Sensor Property.vi>>WPI_CameraGet Exposure.vi>>WPI_Camera Registry.vi>>WPI_CameraOpen>>Camera Performance Example.vi
<time>16:26:47 01/13/2012
FRC: Operation failed due to a communication failure with the camera.

What could be causing this?

[Alan Anderson]

That error could be caused by many things. What is the camera connected to? What color is the ring around the lens? Is it mounted in a way that will keep the reset button from being accidentally pressed? What IP address is the camera set to, and does that match the address being looked for in the example?

[ProgrammerMatt]

By set accounts did you mean User: FRC Pass: FRC and Ip: 10.xx.xx.11
if so you are correct

[cgmv123]

Issues have been confirmed with the setup utility by the NI rep here. Manual setup is recommended.

[Pirate programe]

Originally Posted by Alan Anderson

That error could be caused by many things. What is the camera connected to?

The 2nd crossover port on the cRIO.

What color is the ring around the lens?

Solid green.

Is it mounted in a way that will keep the reset button from being accidentally pressed?

There shouldn't be anything touching the button, if there is the camera isn't showing any signs of resetting.

What IP address is the camera set to, and does that match the address being looked for in the example?

Since it's plugged into the cRIO, it's set to 192.168.0.90, and I've set that in the code as well.

Also, we can get an image from the camera in the Front Panel of the Camera Performance Example.vi, and now we need to get it to display on the FRC Dashboard.

[cgmv123]

Originally Posted by Pirate programe

now we need to get it to display on the FRC Dashboard.

I believe that the dashboard expects the camera to be plugged into the D-Link at 10.te.am.11. Running through the cRIO may require configuration.

[Pirate programe]

Running through the cRIO may require configuration.

What kind of configuration would this require?

[Mark McLeod]

To run it through the cRIO instead of the normal DLink connection, you'd need to add a vi to forward the image on to the Dashboard.

And of course modify the Dashboard to accept images from the cRIO instead of directly from the camera.

The Dashboard camera display will run more slowly coming through the cRIO than through normal network channels.

[rachelholladay]

I believe we are having a similar if not the exact same problem. The main goal for our controls team today was to set up our camera. We worked through the “2012 FRC Getting Started with the 2012 FRC Controls System: How to Configure Your Camera” instructions exactly. And it all seemed to go splendidly. We had a green power light on the camera so we know the hardware was set up correctly. We then loaded the basic framework code on to the robot. However, we saw no image in the Dashboard screen, just a blank white space. We then opened Begin.vi and put on execution highlighting. An error popped up under ‘Open FPS’ (Frames Per Second). We had not changed the framework so it was set to the default of 12. We even swapped out the crossover cable to eliminate the possibility of that problem. We would like to see the camera image in the Dashboard but are currently unable to. Could anyone point out where we erred or what else we need to do to accomplish this task?

[Wendy Holladay]

We were plugged into the 8 port crio and not the dlink. we will rework, having more closely read the instructions. (this is in the first line of the instructions, we should have seen this)