[cstelter]

Has this changed much this year?

I was hoping to have the kids install the camera at our next practice and play with the axisCamera sample code as well as the vision processing examples. Do they just not work? Or are the problems encountered the same as the past 3 years?

We had some success 2 years ago with NI Vision libs running on the cRIO-- we had a separate thread running at low priority to do all the vision and once a pic was done it would update a global value that we could read each time through a pid loop. Essentially we used the global var to set our gyro setpoint and the image processing updated it about once every 0.3s maybe iirc. It wasn't great, but it kept us on track. We eventually went to dashboard side processing, but those involved with that part have left the team. I figured I'd start with the on-RIO solution and the separate thread idea which I can teach to the students how it fully works. But if things are broken this year with respect to past years, I want to try a different direction from the start.

But if the concerns raised are the same old issues, then I think I'll try the old approach as it was pretty easy to get up and running. And if the roboRIO is truly 100x faster than the cRIO as I thought I saw advertised, then that update every 0.3s could be every 3ms which is more than fast enough. I also thought I'd investigate roboRealm as that looked like it had good how-to info to incorperate it, and it looks like it did what our previous solution was doing.