View Single Post
  #12   Spotlight this post!  
Unread 04-01-2014, 12:49
jesusrambo jesusrambo is offline
Self-Proclaimed Programmer Messiah
AKA: JD Russo
FRC #2035 (Robo Rockin' Bots)
Team Role: Programmer
 
Join Date: Feb 2012
Rookie Year: 2010
Location: Carmel, CA
Posts: 114
jesusrambo is an unknown quantity at this point
Re: 2013 Lessons Learned for a Vision Co-Processor

Thanks for posting this!

Considering different coprocessors, last year we just did all our processing on the driverstation. The Axis camera feed is available directly to it, you can run the processing by just adding it into the VI for the dashboard, and then values can be sent back using NetworkTables. This also has the benefit of letting you use NIVison, and the Vision Assistant to develop your processing algorithms.

Many of your points ring very true -- particularly calibration, consistent exposure, and the config file. We had the new dashboard VI store a config file with the HSL thresholding values we used. A widget on the dashboard with sliders and text fields for upper/lower HSL thresholds would load from the config file when the dashboard was opened, and write to it whenever they were updated.