This is exactly the solution we needed.
The Camera Background Loop VI (located in the Vision Processing VI) does two things; it handles some required processes for the IP camera to reduce lag, and it also runs the Send Images to PC VI, which, as it sounds, sends the camera to the dashboard.
In our case, we have two cameras on our robot; one functions for vision processing and one functions for driver vision. We were only getting the former on our dashboard, even though both were connected.
Our final solution was to, in Vision Processing,
define both cameras, (we spent a while on this part) and run the Camera Background Loop VI on each. To reduce bandwidth consumption, we created an alternative version of the Camera Background Loop with the Send Images to PC VI removed.
Now we can see on the robot with one camera and perform vision processing with the other! Thanks so much, we wouldn't have figured this out without this post!
