Vision: IMAQ Area Filter crashes cRIO

[nickcvet89]

Originally Posted by tilky

never ever do camera tracking on cRio, it is way to resource intensive. Instead, do it on driver station.

I'm was wondering, how would you camera track on the DS? Any info will help our team, because it is currently giving our team a lot of frustration with the CPU being overloaded.

[Greg McKaskle]

The CPU usage is related to the pixels processed. If the image size goes down, the pixels drops by 4x. If the frame rate drops, the pixels drops linearly. So, if you want to process it on the cRIO, process fewer pixels in a given period of time.

If you want to process it on the DS, the initial LV example project has VIs for both the cRIO and the host computer. The example has a loop for getting the camera image, processing, and displaying it. Locate the similar code in the dashboard that just gets the image and displays, and merge in the processing code or the portion of it that you need.

To communicate results back to the robot, I'd suggest using SmartDashboard. Write the values in the dashboard vision loop and read them on the robot where you need them.

Greg McKaskle