Quote:
Originally Posted by Levansic
Our team had the same error, with the same setup (8-slot + M1011). We wasted a few hours trying to fix it, and eventually moved our vision processing into a custom dashboard, sending the boiled down output to the cRIO through UDP (port 1130).
Even the wimpy classmates have more processing power than the cRIO, allowing us to use a higher resolution image. This also cuts down on processor contention on the cRIO, where a blocked teleop loop can halt your drive.
We're you, by chance, feeding a grayscale image to the vision processing vi?
-- Len
|
So the GetImage error is related to the speed of the processing on the cRIO? That hadn't occurred to me, I figured there was some other internal sort of problem going on. I'll have to take a look at it. And yes, I am using greyscale images.
Thanks for the quick reply!