Vision Idea Exchange

Community Browser
About Vision Idea Exchange

Have a Vision Product Idea?
  1. Browse by label or search in the Vision Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. Be sure to submit a separate post for each idea.
    Note: Please post technical vision support questions to the Machine Vision forum, not the Vision Idea Exchange.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As Vision R&D considers the idea, they will change the idea status.
    Note: Vision R&D is committed to reviewing every idea posted in the Vision Idea Exchange. However, the implementation of any Vision Idea Exchange submission cannot be guaranteed.
  5. Give kudos to other ideas that you would like to see implemented!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 
Post an idea

there are some vi in vision toolkit that their controls have not any useful information in labview help for user  so many ability of these vi are not discovered by LV user like  me 
for example IMAQ Particle Filter have input control with name of  selection value  inside this cluster we have item with name of Measurement Parameter  that have many mode to select but no detail information for them to know what kind of ability they have 
I think in next version of this toolkit it should be release  with enough information about these controls of  such vis

Supporting only binary images as input type for the particle analysis is reducing the use cases where this functionality can be used. In many segemtation methods, e.g. superpixel segmentation or watershed segementation, the segmentation result is a labeled image. Being able to perform particle analysis on labeled images would enhance the modularity of this function. Since the particle analysis in internally performing probably a labeling anyway, and in many cases, the label of an object which is to be analysed is known too, it could also reduce the computational cost of this function.

The Image Display control (IMAQ Image.ctl) allows the user to change the color palette.

Like for the Intensity Chart and Graph objects in LabVIEW, it would be useful to add a color scale object to the control in order for the user to be able to visualize the color <-> value correspondance.

Like for the Intensity Chart and Graph objects in LabVIEW, the color scale should also allow the user to set the display range (min and max value) as well as the out of range color values.

Setting My Camera Attributes Programmatically Does Not Permanently Change the Attributes


Currently, we cannot update .icd file through LabVIEW using IMAQ. The only way to do so is saving new values in MAX.

However, IMAQdx has this functionality. It would be very convenient if we can update .icd files using IMAQ as well.

How Do I Programmatically Load or Save a Configuration File with IMAQdx?

I don't know if anyone else has requested this: It would be great if VA kept a track of the Template folder and Image file folder separately. I have to constantly load new templates and images and the program only remembers the last folder used, which means constantly navigating.

It would be nice if NI can provide Reset to default Values for settings in Vision assistant for many functions for e.g., Shape Detection etc. Currently either the developer should be getting default values from context help or delete the fuction and add it again.

it would be handy if the VBAI "Threshold Image" step could operate on just a selected region of interest instead of only working on the full image.

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.



 When we create some geometries like circle, rectangle etc. in Custom Overlay step, we can not arrange the thickness of that geometry. We can not make something to be more apparent with changing the thickness.


The worst part comes out when you try to save/log an image while working with a high resolution camera. It is quite visible in VBAI Image Display window, but when you look at a logged image, you can not see any overlays because it has very small thickness(probably 1 pixel).


So, I think this feature can be added very easily and can help us create better visualization.

The title says it all, but let me expand a little...


Since LabVIEW 8, trying to create a VI from a selection containing a reference to an Image Control fails. It does absolutely nothing, nada, nitchevo, nichts, rien...

There are at least TWO CARs about it: 54165 and 35835.

Yet, years after years, nothing is done about it.


A workaround for creating VI is to remove the connections to any of the image control references in the original selection, and once in the created subVI, drop a custom control that you will have strategically dropped in your Favorites Control Palette:


Screen Shot 2016-11-29 at 14.49.41.png

Then you need to add it to the connector pane, reconnect in the original calling VI...

Not the easiest but manageable.


Now, what about managing events using a Register Event node handling several controls, including a couple of Image controls? Usually, when not using images, I bundle references to the controls and do the Event Registration in a subVI (there are typically a lot of wires and large nodes involved, therefore this would take an undue amount of real estate in a main VI).

The problem is, any cluster containing a Image Control Reference can apparently not be created as a control in a "Create subVI" or even a "Create Control" operation:


Screen Shot 2016-11-29 at 14.56.09.png



Screen Shot 2016-11-29 at 14.57.20.png


Once again, it is possible to do all this manually, but if you have a bunch of Image Control references and other references to bundle, this is becoming rapidly tedious.

Hi there!


I wanted to propose a new tool to draw a ROI in the Vision Development Module and in the VBAI: maybe using the spline, the ROI will be more accurate for some particular inspections.


Tank you so much,




When working with LabVIEW Files, there are two ways to get the File Path back from the File Refnum -- one is to use the Close File function (which takes Refnum in and returns Path out) and the other is to use the Refnum to Path function (which I didn't know existed until today).


However, this very convenient "inverse transform" is not present in the NI Vision for AVI2 Files -- IMAQ AVI2 Close doesn't return the Path, and the Refnum to Path function won't accept an AVI Refnum as an input.  Assuming that the original Path information is contained in the DLL at the time that AVI2 Close is called, please return it (as a Path or as a String) when the AVI is close.  Alternatively, provide an AVI2 function (perhaps an extension to the existing IMAQ AVI2 Get Info) that returns the File Path.



1) Add a standard image overlays like rulers, gridlines and reticles.


2) Slave the position for an image overlay to the Set Coordinate System step.




Many times in computer vision, specifically when applied to field of robotics, it may be useful to perform an affine perspective transform on an image based on the robot's roll, pitch, and yaw angles coming in from an IMU. These VI's can be used to project input images into naider view which were originally taken at some alternate roll, pitch, and yaw angle. Applications include improved object recoginition, gimbal replacement, and more accurate visual servoing. 



Sub-state import / export in VBAI

Use standard / template states across multiple VBAI inspections.  Especially useful for communications methods and data / image logging formatting.


Think subroutines.




Is it possible to programtically validate the license status of the NI Viison Run Time Engine and Vision Acquistion, and alert the user few days before so that the license can be updated. Is there specific VIs which would perform the license check of the NI products?.



Saranya Venkattaraman.

I am using NI Myrio FPGA to do image processing. With the help of NI Vision Assistant 2014, i am able to get the image from usb webcam. I want to use FPGA to convert the image to HSV. However the functions provided in NI Vision Assistant only allow me to get either H, S, or V image at once.

In order to solve it, i try to create one more FIFO to store the image. Here is my FPGA coding.

fpga code.jpg


However, I do not know how to access these FIFO. Here is Labview coding.

code 1.jpg

code 2.jpg

All these coding are actually generated by NI Vision Assistant and i cant find where can specify which FIFO i am accessing. Any can help me?

In Labview, we have an option for saving the VI for a previous version. I think it would be good if we have this feature in VBAI, too. 



Inspection documentation. 

Display them in the table view and give an option to display them in the diagram view.

Important for documentation.   There is currently a comment field in the table view but no way to populate it.

I had a long lasting SRQ on this one but nothing came out of it and I'm left with the issue.


NI is aware of the issue and the work-around is : do not disconnet a USB device while you have triggered GigE (IMAQdx) acquisition in progress.

SRQ 7395589


I'm being forced to create an idea to try to get more momentum for a CAR to be created.