Quote:
Originally Posted by Greg McKaskle
I still think that the OP will be well served by looking at the examples and trying things on a single computer, single language, and doing the control using additional sensors. If they then feel the need to elaborate the system with two of everything, they are better prepared for the journey.
Greg McKaskle
|
For what it's worth, Greg's suggestion is a very good one. Try the examples before running off on the secondary system quest...
However, if you are undeterred and wish to forge ahead and you want to send data between two systems then I would look at Network Tables (which has been heavily revised for this year) and I would possibly look at ROS. I2C and serial are also possibilities. You could also just send raw streams but there are bandwidth limitations and port restrictions to keep in mind (Read the rules).
Our team (900) has been doing a lot with vision processing. Last year we included an Nvidia Jetson TK1 on our robot that used a webcam and OpenCV to process the data. We used NetworkTables to send the data between the Jetson and the RoboRIO. We also proudly program our RoboRIO in LabVIEW.
EDIT: One more point to make. You don't always NEED to process
video. Sometimes a single image or a set of images will work just fine. Single frames are minuscule in comparison to video streams and a lot faster to process. For instance, this auto aim was done using single frame captures:
https://www.youtube.com/watch?v=QT2OmzrAhPI