|
Re: Yet Another Vision Processing Thread
Our history with vision:
2009: Could not get it to work with the given targets, no vision on dashboard
2010: Vision through Axis 206 through cRio for driver display only. Only use ever was to take pictures at the beginning of auton to verify driver setup.
2011: Tested vision code using Axis 206 on cRio, vision was not useful at all
2012: Developed robust vision tracking system. Specifics:
Driver Station laptop
Axis 206 with LED ring
UDP from Dashboard to Robot
Framerate was 20fps, although the pipelined design meant ~100ms total latency.
2013: Vision not even attempted. Axis M1013 camera on robot for drivers, who never used it. Eventually removed camera for weight.
2014:
???
Plans include driver station laptop, Axis M1013, and UDP. Similar in design to 2012 code.
IMHO we really only need to process 1 image per match this year.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor
"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack
|