Quote:
Originally Posted by GeeTwo
Problems getting the vision software itself to work, problems with the rest of the robot because so much CPU is tied up in vision processing, or something else?
|
I'm not him or her but I'm willing to wager that they were suggesting there will be issues with the rest of the robot due to the intensity and resources used during vision processing on the rather meager RoboRIO, for which that I agree with.
I recommend you check out DaisyCV from 2012 or 2013 as they have been an incredibly useful resource for me (and other programmers) regarding vision tracking. Storm (2729) also publishes their code on GitHub each year and has a well-documented OpenCV driver-based solution from last year they published. If you run into any specific issues, let me know -- the documentation for OpenCV is greatly lacking and getting started was the hard part.