[jojoguy10]

Originally Posted by Thad House

You can use NetworkTables to send image data from the Pi to the RoboRIO. You would have to compile the ntcore library for Raspberry Pi, which isn't too hard to do, and then just link to that. You can also build a custom communication interface, which shouldn't be too hard, but NetworkTables is the easiest.

Is there a quick "getting started" guide for setting up network tables in C++ (for OpenCV)? I know where the blocks are in Labview, but I've never done them in C++

Originally Posted by Thad House

As long as you are using a Pi 2, you should be good. In fall 2013 I did alot of camera testing, and got about 9 fps out of a Pi 1, 16 out of a BeagleBone black, and a Pi 2 should be much quicker then the BBB, so it should get in the 25 or so range.

Awesome! I'll look into the Pi2 more specifically.

Originally Posted by Thad House

I've always found that OpenCV is much easier to work with then NIVision. In addition, since its not running on the RoboRIO you can have the RoboRIO only doing robot code. Having the processor on the robot is better then on the driver station IMO because I've seen FTAs request that teams turn off their dashboards to ease up field traffic, and if your processor is on board even if they ask you to do that you don't lose tracking.

Right, I have heard running vision processing code on the RoboRIO will slow it down. That's why I was wondering about how to transfer the image data from the board to the RoboRIO.

I'll suggest that you to run the existing vision examples and try the vision processing on the roboRIO. The roboRIO is many times faster than the PI2 and doesn't require you to coordinate several processors, different implementations of network tables, etc. Once you have some experience with that, you can run a similar experiment on the PI2.

We have run a few examples already. We thought the results were slow and laggy. So, we wanted to try to find a faster and more reliable solution.

Thanks everyone!