need "simple vision" help

[emusteve]

Trying to get started with vision in this year's environment. Figured I'd start with the "Simple Vision" example. (supposed to push an image to the dashboard.) Started by using the NI Axis Camera Tool to configure the camera. RoboRio finds the camera and lists it as "Cam0". I build and deploy the example code, but the RoboRio log reports "Error when getting image from camers: IMAQdxError:-1074360306: No acquisition in progress, at edu.wpi.first.wpilibi.CameraServer.capture(CameraS erver.java:182)"

Anyone have any idea what is going on here? I should mention that I'm using the Axis 206, same camera as described in the documentation (or what passes for such). I"ve also tried all options for Live View, thinking that the problem might be in how the camera is serving up the image, but no luck regardless of setting for ActiveX, Java Applet, or Still Image.

Thanks for any help.

[RufflesRidge]

There's no reason to run the CameraServer to serve up an image from the Axis camera. Just use the LV Dashboard or Simple Camera Viewer in the Smart Dashboard to connect directly to the camera.

The Simple Vision example is meant for USB cameras like the Microsoft Lifecam HD-3000

[emusteve]

We're using Java, and thus Smart Dashboard. Reading through the Smart Dasboard documentation, I couldn't find any mention of "Simple Camera Viewer". If you could point me to the documentation on that, I'd appreciate it. Vision Processing documentation seems to be essentially non-existent. ("More coming soon" couldn't be soon enough!)

I did see some stuff about RoboRealm, but we're trying to keep the Driver Station as generic as possible, in case we have to switch out, or use a borrowed DS in a pinch.

Thanks.

[nickmcski]

Originally Posted by emusteve

I did see some stuff about RoboRealm, but we're trying to keep the Driver Station as generic as possible, in case we have to switch out, or use a borrowed DS in a pinch.

This may be extreme for some teams but you are actually allowed to have a laptop mounted on the robot running RoboRealm and use it as a co-processor. That way its independent of your driver station, and you don't have to worry about the bandwidth cap between the robot and the driver station.

[Fauge7]

Originally Posted by nickmcski

This may be extreme for some teams but you are actually allowed to have a laptop mounted on the robot running RoboRealm

the only problem is the laptop has to start up, and be powered by the battery in that time...minor detail

i would suggest using a coprocessor such as a Odroid c1, or beaglebone esk board. They are relatively easy to set up. Imho Do not bother with vision this year unless your willing to research it, DO NOT use the first libraries as they have very little documentation and if your having simple vision trouble then your definitely going to have problems with others.

[mmaunu]

Originally Posted by Fauge7

the only problem is the laptop has to start up, and be powered by the battery in that time...minor detail

Just to be clear, the laptop can be solely powered by the laptop's battery and does not have to be powered by the robot's battery; the laptop can be booted and setup in the pit or in queue. This is probably what you meant, but the part about starting up "in that time" gave me pause. R20 is the relevant rule and this is just below the big blue box:

Additionally, batteries integral to and part of a COTS computing device or self-contained camera are also permitted (e.g. laptop
batteries, GoPro style camera, etc.), provided they’re only used to power the COTS computing device and any peripheral COTS
USB input devices connected to the COTS computing device and they are securely fastened to the ROBOT.

[Fauge7]

I didn't actually know that, but seems a lot more complicated then solutions that already exist