View Single Post
  #7   Spotlight this post!  
Unread 12-09-2009, 16:06
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,756
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: LabView/C++ equally capable?

I'll see if I can find the test code. It was basically pointing the camera at the cRIO LEDs, the ones near the power and ethernet plugs. There is an RT function for controlling the LED, and I figured it was close to instantaneous compared to the camera, so I turned it off, and started the camera to acquiring.

At some point, I'd turn the LED on, record the time on the cRIO, then loop inspecting images until one showed up with the LED lit. To detect the LED being lit, I use the regular Camera Get which uncompresses the image, then I measured the intensity of a pixel over the LED. A that point, turn the LED back off, wait for things to settle, and do it over again. I decided to wait a random amount with the LED off. This gave me a pretty good statistical picture of the latency. It shows the minimum, the typical and the maximum time you could expect for a given camera setup.

Greg McKaskle