Thread: Sending Vision Processing Data to Dashboard (C++)
View Single Post
  #2   Spotlight this post!  
Unread 14-01-2012, 09:01
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,750
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: Sending Vision Processing Data to Dashboard (C++)
What size image were you processing, and how many images per second? It is possible to bog down any computer with image processing. The cRIO is pretty capable, but clearly has limits. If you use smaller images and limit the frames per second, you can process the images in a parallel thread and not interfere with teleop. If you put it into teleop, you will definitely slow teleop, as simply decoding the JPEG may take 20ms.

Processing the images on the laptop is also pretty straightforward. NIVision has the same entry points in a Windows DLL as on the .out library on the cRIO, in fact a superset of entry points.

As for viewing the image as you are processing it. This will also be easier on the PC. I don't know the details, but I'm pretty sure that NIVision has functions for drawing into a window. Your code can open the window and share the handle.

Greg McKaskle
Reply With Quote