Vision Idea Exchange

In Vision Assistant 2014 SP1, the "Create LabVIEW VI" function does not create a calibration file path in the generated code, for the Image Calibration function.  Instead it reads in all of the calibration information and sets these to constants (or controls if selected it in the wizard) in the generated code.  It would be good if this maintained a reference to the template.

Binned images are very useful for reducing processing time when you are looking at the entire image.  It would be very useful to have a function that would perform binning on an image to generate a new image.  The binning factor could be anywhere from 2x2 to 32x32 or even larger.  I would be happy with powers of two, but any integer value would be even more useful.  Different values for the X and Y binning would also be useful.  The values could be simply added together and divided by a user specified divisor, much like the filter options.  It would be similar to the existing IMAQ Block Statistics, but the output would be a new image ready for processing.

Right now, binning can be accomplished by multiple steps - filtering with the appropriate size filter, then using IMAQ Extract to reduce the size of the image.  This is much slower and less efficient than a single binning function would be, since the filter must be applied to every pixel, instead of just the pixels you are keeping.  It could be done in place on the original image if desired.

Bruce

When Vision Assistant steps are converted to LabVIEW VI, the overlay of result (i.e. edge detect, particle counts) is lost.

Adding overlay function on VI requires not only LabVIEW skills, but Vision knowledge due to image memory handling.

So it'd be nice to have an option to keep the overlay functionality on Vision Assistant even when converting to LabVIEW VI to have a smooth transition.

Ryuji Kuwajima

I'd like to be able to import a DXF file and display it as an overlay on an image.