View Single Post
  #1   Spotlight this post!  
Unread 10-02-2009, 09:19
TheOtherGuy's Avatar
TheOtherGuy TheOtherGuy is offline
Unregistered User
AKA: Kevin Forbes
FRC #4183 (Bit Buckets)
Team Role: Engineer
 
Join Date: Jul 2006
Rookie Year: 2006
Location: Tucson, AZ
Posts: 408
TheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond reputeTheOtherGuy has a reputation beyond repute
Re: Camera tracking at 110ms

Quote:
Originally Posted by Greg McKaskle View Post
I've done the LV timings hundreds of times. 640x480 is around 5fps, 320x240 is around 10fps, and 160x120 is around 25fps. If you decimate some, you can improve it further.

You can definitely get 110ms or better. What are your other constraints?

Greg McKaskle
I was wondering about this; my team is running the LabView tracking code and the best we get with 160x120 without decimation is 12 or 13 fps. Is there some trick to increasing this speed? We have yet to try tracking without live debugging (not sure how much time is lost in the communications with the laptop).
__________________