Re: 2013 Lessons Learned for a Vision Co-Processor
 

We did this as well. It was great for tuning purposes. :)

Re: 2013 Lessons Learned for a Vision Co-Processor
 

Chapter and Verse:

You could even go so far as to have a shell command program on the cRIO that took commands from the co-processor.

As for the ROS, I haven't played with it too much, but our current vision processor is the ODROID-U2 does have an ROS software version: http://forum.odroid.com/viewtopic.php?f=8&t=2096

Re: 2013 Lessons Learned for a Vision Co-Processor
 

Also, save off all your variable that you need to a logfile. I've done this the past 2 years. You can write an octave script that will make graphs out of the solutions. Also, you can REPRINT your solutions onto the corresponding image. This was really cool. We went out with a cart with a computer and camera during calibration and saved images 10 times a second, then created a "video" that we could show in the pits to curious students and mentors and show the judges it working on the field.

Also, if you can, go to another regional you are not competing at and take pictures so you can get an idea of what to expect at your regional. We have also done this for the past 2 years.

Re: 2013 Lessons Learned for a Vision Co-Processor
 

Since we are talking about logging data for review, has anyone played with the dashboard template that includes the ability to record and playback a match? It logs an avi and another file that includes the contents of the network table, joystick data, I/O values, etc. It would also work to test out changes to dashboard-based vision processing. Your code under development would be processing the AVI instead of the live version.

Greg McKaskle

Re: 2013 Lessons Learned for a Vision Co-Processor
 

That sounds like a nice capability. However, not useful for anyone not using the LabVIEW dashboard.

I have been thinking about logging all of the data and doing something with it for awhile now, but I've never actually gotten around to doing it.

Re: 2013 Lessons Learned for a Vision Co-Processor
 

My understanding is that the 2.0 version of SD also has this feature.

So the teams who use LV dashboard have this capability, the teams using SD 2.0 have it, and teams to do something entirely different can look at those implementations if they would like to have it.

My point is -- we got around to it. I hope teams know about the feature and use it to improve their robot, their gameplay, and help with debugging and diagnosis.

Greg McKaskle