What does the Camera Slow Down?

[Dave Scheck]

Originally Posted by ErichKeane

Is there any way to disable the sending of the video over the wire to the dashboard? We used the stock dashboard and only enabled the camera (at 320x240), and found that our controls were ~1 second delayed when we got on the field at portland.

We ended up just disabling all our camera code and just leaving the initialization and still saw a huge slow down, so we just decided to just give up ont eh camera entirely.

When you instantiate the AxisCamera object, it creates the video server task behind the scenes. If you comment out the instantiation the server won't be started and video won't be sent.

EDIT: After rereading your post it sounds like you might be trying to use the camera onboard without sending video back. If that's the case you would need to specifically update the WPILib code to not start the server automatically.

[ErichKeane]

Originally Posted by Dave Scheck

When you instantiate the AxisCamera object, it creates the video server task behind the scenes. If you comment out the instantiation the server won't be started and video won't be sent.

I guess my point is: I want to be able to use the data from the camera on the cRio without streaming it to the Dashboard, which I suspect is the reason for the huge delay we saw when we got on the field.

[synth3tk]

Don't know if you saw this yet:

Originally Posted by Dave Scheck

EDIT: After rereading your post it sounds like you might be trying to use the camera onboard without sending video back. If that's the case you would need to specifically update the WPILib code to not start the server automatically.

[ErichKeane]

Originally Posted by synth3tk

Don't know if you saw this yet:

I didn't, thanks! He edited after I replied and was done. I was afraid of that answer... At least it'll give me something to do next year

[TubaMorg]

You really should be able to get it to work fine. Take a look at these threads:

http://www.chiefdelphi.com/forums/sh...ht=java+camera

But, seriously, if you haven't tried compressing the image, you will find that it will solve most lag issues (unless there are problems elsewhere in your code).

[ErichKeane]

Interesting points in that Tuba, thanks.

I doubt it was the rest of the code, it was extremely simple code, particularly since the camera stuff wasn't there. Basically we got to Portland for a practice round, found it was really slow, so we disabled OUR camera code (left the initialization) and it was still really slow. So we removed the initialization and everything was fine.

We had compression at 80 (i think that was the recommended number last year?).

We were fine with the rest of the stuff on that list (other than resolution), since we didn't ever even use the developer account.

It worked perfectly either wired or on the practice field, but once we got to the actual field, there was a huge delay according to the driver.