Quote:
Originally Posted by Cr1spyBacon8r
I don't think we'll run it on the roboRIO anyway... We've had enough CPU troubles before, so just putting extra strain on it wouldn't go very well... Having a coprocessor to do vision would probably be the best way to go still.
|
I'd like to temper the prior statement with a very different experience. Our team (1967) used the OLD cRio processor which is way less powerful than roboRio to do live image processing using the NI library a number of years back with great success up to 13-15 fps without causing any other disturbances in the performance of the robot.
The biggest key here is in making sure the way you're handling your processing loop is done in such a way as to not HOG the CPU and all of its free resources. I would expect that the roboRio has more than sufficient processing resources to do quite a bit of realtime image processing.
Happy Programming!
RoboBob
While those ideals might exist in black and white perfection; in the real world, with very rare exception, they can only be implemented as compromises in shades of gray. - gblake [more] 
Threaded Mode