Vision Idea Exchange

Community Browser
Top Authors
Showing results for 
Search instead for 
Did you mean: 
Post an idea

In Vision Development Module, it seems new functions are being created to replace older versions from time to time. ie: IMAQ Set Calibration Axis --> IMAQ Set Calibration Axis Info  This is fine, however, the Vision Examples still use the older versions of these VIs, ie. they don't seem to have been updated also. 


For instance: Using Vision Development Module 2014 SP1, example Simple  In this example, the following VIs are being used: IMAQ Setup Match Pattern, IMAQ Match Pattern, IMAQ Set Calibration Axis  However when you look at the LabVIEW functions pallette, the following VIs are available: IMAQ Learn Pattern, IMAQ Match Pattern, IMAQ Set Calibration Axis Info


This tends to confuse things.  It would be great if the examples were also updated to use these new functions available


Also, the help files do not seem to differentiate between these older and newer functions.

Problem Description :
I am unable to enter more than two places past the decimal when entering in
tolerance into the pass inspection if.....
is there an update that can fix this issue? I believe this has never been addressed in any of the new
versions of VB. I can hold micron tolerances but cant do any pass fail because
when i put the numbers in they round up or down. they may be going in but i
cant see them and therefor cant refer back to what was put in because they do
not show past the 2nd decimal place. 



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.

 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 updates I'd like to see boil down to the following:

1. Parity between the C and .NET APIs.  There are methods available in the C API that did not make it to the .NET offering most importantly the ability to set VBAI parameters at runtime.

2. 64bit DLLs.


I've been using VBAI through the .NET API in production for about a year now, the above requests would make future expansion much easier.


Thanks for the consideration.



Option to exclude “default” columns for data logging step


The current data logging step includes many colums of default data which very often gets deleted when sharing data with others.   It's great having the data by default but is undesired in many roll out installations.




Apply color lookup table (convert grayscale to a false color image).  Color pallets are very useful – would be helpful for saving images for external displays (e.g. web browsers or windows explorer)


When saving images with VBAI using the save image option under file in the configuration interface, it would be nice to be able to create a new folder.

I think just like most of other software, VBAI should take the last selection as the default value for this type. This what I mostly require in Custom Overlay steps.


Mostly we are using the same text type-color etc. for different elements but because VBAI changes the color randomly, and making the size 13 every time, we have to change it for all elements. Since generally I use one color for most of the text list on the screen, it would be really helpful if VBAI could remember my last choice as default for the next selection.

I did a test :

- develop an inspection in VBAI 2014

- benchmark it in VBAI : ~300ms

- export to LabVIEW code

- benchmark in LabVIEW 2014 32bit : ~90ms

- benchmark in a full 64bit environnement (LV, VAS, VDM) : ~55ms


That's a huge performance gap!

In the VBAI Dev environment, we currently have the ability to enable/disable overlays using the "setup overlay" button.  This request is to provide access to access the overlay enables programmatically.  The use case is for when operators are required to show/hide specific overlays.  When many overlays are involved, the overhead for programming these using the state diagrams becomes overwhelming.   Below is an example for only 6 overlays.  You can see how 30+ overlay groups would be a nightmare.  There is also a overhead performance hit.









Add the ability to ‘add a variable’ when working inside the Vision Assistant step window.

Long names may get cut off in Measurement window, allow for a separate window, like the View Measurements dialog box, to fully display names and values with resizeable fields, instead of just relying on tool tips

Is there a way to "get camera extra information from image" when I'm using the Simulate Acquisition step?  It seems like if the information is in the image it should be gettable from either the Acquire Image or Simulate Acquisition step.



Allow data logging to shared drives or server paths just as to local drives.  Image and data logging steps do not accept a server path such as //

Currently you have to first map a network path to a drive letter in Windows to save images to a network path.  This is for network locations which are shared locations, not FTP.



Histogram head / tail by percent

Currently the pixel counter returns the % of the histogram which is above/below a gray value but this tool would do the reverse:  return the gray value of an ROI which is at the x% of a histogram.  In addition to % head/tail, it would be very helpful to have an optional check box (disabled for speed when you don’t need it) to return other common distribution stats such as # of modes, normality test, skew, etc.



Advanced Edge, Multi-edge mode: When expecting N edges, SNR noise needs to be calculated based on the residual RMS signal level to avoid inappropriately low SNR reporting.

Currently, the edge #1 SNR is based on strength of edge #2 which will result in a very low SNR for edge #1 if #2 has a similar strength. 



VBAI step for programmatic control for grayscale operator (e.g.  Subtract a gray level based on the results of a previous step histogram).   – OR – Update the Vision Assistant tools to use inspection variables for all their set points.

Basic functionality missing from VBAI; available on the lowest cost smart cameras from most major competitors.



16 bit support for thresholds, detect objects, etc. 

Advanced edge tool will not work on low contrast 16 bit images unless the Straight Edge Settings; Minimum Score is set to 0 (make 0 default then?)  Also the Advanced edge tool max score is 1024 so it cannot find edges with stronger transitions which often occur in high contrast 16 bit images.




Image FOV balance with a reference image or by a polynomial fit.

Common functionality available in most compettitors’ systems