View Single Post
  #7   Spotlight this post!  
Unread 19-02-2013, 04:27
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Vision: IMAQ Area Filter crashes cRIO

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
Reply With Quote