Camera problem: No Code

Technical C/C++
1

Since installing C++ team update 4.1 I’ve had an issue where the driver station says there is “No Code” on the robot. This only happens whenever I have the line “AxisCamera &camera = AxisCamera::GetInstance()” (or equivalent) in the code, when I remove all camera-related code it runs fine.

Previous to the update, I’ve been able to run the bot with the camera and get a live feed to the driver station, leading me to believe that it has something to do with one of the updates.

Has anyone else experienced this? How did you fix it?

(It’s worth mentioning that I never installed update 4.3, but it doesn’t seem to be relevant to this issue. Regardless, I’ll try it tomorrow along with anything else.)

2

Yes, you need the latest update. One of the intermediate updates was broken.

3

Hm, I forgot to try update 4.3 today, but I’ll take your word for it (especially since people mysteriously stopped responding to this thread (which I didn’t see earlier) after the update).

Is this the “issues with camera and image processing symbols not showing up in the library” mentioned in the update’s description? If so, it went right over my head (oops!). Cost us a working camera for SVR. Oh well.

4

Installed the update, but now we aren’t getting a dashboard feed. Everything else on the robot is working, so it’s not crashing the system. It’s just as if the camera code wasn’t there at all.

Right now I have something like:

AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(AxisCamera::k320x240);
camera.WriteBrightness(0);

in the robot constructor. That should be enough, right?

Workbench is v4.3, cRIO image is v20, camera is connected to ethernet port 2 and lights up green.

5

Are you running the latest version of the Dashboard? (with the gyro in the lower right) Did you make any modifications? Are there any firewalls running? Does the camera still not show images if you roll back to the first version for this year?

Also, if you haven’t already, install NetConsole (instructions are with the first WPILib update). It should give some major hints to what is wrong

6