Thread: Vision Tracking from the Dashboard
View Single Post
  #11   Spotlight this post!  
Unread 02-02-2013, 19:39
Phalanx's Avatar
Phalanx Phalanx is offline
Formerly Team 1089 (Mercury)
AKA: Michael Reffler
FRC #5431 (Titan Robotics)
Team Role: Mentor
  
Join Date: Jun 2005
Rookie Year: 1999
Location: Lewisville, TX (previously NJ)
Posts: 384
Phalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond reputePhalanx has a reputation beyond repute
Re: Vision Tracking from the Dashboard
Quote:
Originally Posted by Greg McKaskle View Post
The code that didn't work on the classmate ... Can you describe what camera resolution and what frame rate you were using with the default code?
Greg McKaskle
Greg,

It was 320 x 240, 30fps, 30% compression. We basically copied the Vision Processing sample into the Driver Station, and sent the targeting array only back to the CRIO via UDP. That's a pretty common setup so I hear.

Lowering the frame rate and/or image size eases the problem, but doesn't eliminate it. What we eventually restored to was a turning the tracking on/off as needed. But when it was on, it did increase the cpu load, and the robot was sluggish.

I can't recall if any watch dogs were triggered or not. But I do remember looking at the log, and when the CPU use was high packet loss was high as well.
__________________
Don't just ask the experts, become one!
Leadership is not about ability. It's about responsibility!
Diagonally Parked in a Parallel Universe. It's okay we do Quantum Physics


Reply With Quote