Camera Vision and Dashboard at the same time

[Greg McKaskle]

The best indication that your processing is expensive would be to look at the CPU usage of the roboRIO on the DS chart. It is the center button on the right side, red plot.

The image you attached shows the same image being sent to what I assume is a processing function and to an image display. If the processing functions do not wire in a destination image, the input is reused, and this can affect the display. It often shows up as a flicker of good images and images that have been thresholded with at mostly black color palette.

Note that this is only the case with the Image datatype in LabVIEW. All other types that are displayed are treated as by-value types. The control would happen before or would copy the data. But because images are so large, and the vision API was developed in the early 90's, it is a by-reference type.

One easy thing you can try is to right-click on the image display control and set it to Snapshot. This will store the data when written instead of reading it while the processing is underway.

Greg McKaskle