We have figured out how to run two cameras in LabView (display image from both cameras on Dashboard) at low resolution. But we are trying to figure out a way to use a button on our remote to toggle between cameras, in order to be able to run at a higher resolution. Does anybody have any ideas that could help???
The Search function of Chief Delphi would be very helpful here.
Can you give a little more detail about how you run two cameras in LabView? I followed the instruction from another thread “2 cameras”: duplicate the initial USB 0 camera setup in the default project code Vision Processing.vi for a second camera, change the values for the second camera like USB 1 and camera 2. At the Dashboard, I can see the images from either camera or camera 2, but not both at the same time.
Did you do anything special to get it working ?
Thanks!
You have to lower the FPS to 10 and set the Compression to 50% in the dashboard on each of the cameras.
We tried to do the toggle between two camera trick last year. After a lot of trials, we got a very twitchy solution that relied on magic to work correctly. Basically our best result was 50% probability of working, but very low likelihood of working beyond the second switch of streams. Our stream switching was done on the roboRIO, to minimize the impact on the bandwidth limits.
At championship, we cornered a NI developer who said that he had worked on the vision pipeline in the LabVIEW templates. He told us that it was impossible to set up and switch between two cameras, based on how the vision system was architected.
That we were able to get our system to switch at all between two cameras, indicates that we found an indeterminate bug. It was designed not to allow this.
–Len
By the way, the vision stuff was reworked for 2017 to allow numerous cameras and interop better with web browsers and various DS implementations.
What was said last year at champs hopefully has no impact on what you can do this season.
To the original question. Picking between different cameras in the list simply sends in a new name to be the current camera. You can rework this to be based on a button, timer, combo box, etc.
Greg McKaskle
That’s great to hear Greg! I welcome the new news.
By the way, the developer I talked with last year was not Greg, who has always been gracious with his time and assistance.