[computergeek125]

We don't have two cameras to use, but our robot is configured to do so. I've actually got our camera and vision processing to run directly from the dashboard, while [attempting] to send the vision state back to the robot for processing. The ReadMJPEG.vi is helpful in this process! Before I came to this, i figured out that the Open Camera.vi will target a connection on cRIO port 1 when I changed the IP of the camera to 10.xx.yy.8. So, the camera was on the D-LINK for access from a computer if need be. As for power, the Axis camera ended up next to the 5v converter for the D-LINK physically, so it got tied in to that circut. THIS PASSED INSPECTION. If we ever added another camera, it could be put on the 5v regulated output on the power distribution board, and be connected to the D-LINK for net access, probably on 10.xx.yy.9. Images that come through on Read MJPEG.vi also are more in real-time, rather than a slight delay. Modifying the Image Processing.vi was as simple as getting rid of the access camera Device Reference, changing the "Original" display to be a control (right-click menu), and connecting the new control to one of the pins on the Vision Processing.vi icon. Then wire the output of Read MJPEG.vi to that pin (assuming that Vision Processing is now in the loop on the dashboard that has all of the vision stuff)

As for simultaneous image requests, I have not experimented with the Read MJPEG.vi either, but I do know that the cRIO image stream (Open Camera.vi / Get On PC.vi) stops when I log in as an HTML user with a web browser, however, 2 computers using HTML can simultaneously view the image stream. I assume the Read MJPEG.vi works similarly.