Vision Idea Exchange

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

undo is really a must-have function

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.

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.





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.


After checking with support, it appears that as of VBAI 2015 f2 there's no ability to delete multiple VBAI state diagrams at once. I have an inspection with multiple states, and would like to modularize/strip off a small subset of the states to import to another inspection. I can delete one at a time, but would be useful to do this easily.

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. 



Source Control.   Need some way to compare two inspections to show where the differences between two inspections (especially changes to settings) are.

It may be easier to export each inspection to an xml file with all settings, region of interest (if manual), etc.

if VBAI could automatically generate a documentation that show :

- the step liste with the type for each step

- the dependencies between the steps (e.g. when the result of a step is re-used as a parameter in a subsequent step)

- the steps that procude results upon which the final decision is based


here is a basic example made in Excel, feel free to suggest a different model



having VBAI in other languges would helps us pushing it in more companies.

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

Using the image operators ADD or MAX or AVERAGE, even if both the images in the VI are calibrated, the output image is no longer calibrated.


To get around this, I have to separately copy the calibration to the output image. This is not possible from Vision Assistant (within VBAI) so I have to instead use a Run Labview VI step to re-calibrate the image. The same is also true for these VIs in Labview VDM, so I am posting this on both forums.

Need the ability to operate using local inspection variables quickly without the slow process of checking the value over the network each time; but the varaibles would be updated as needed from / to the remote location.    Dan R



One power of the custom VI in Vision Builder is to be able to distribute code but sometimes the custom VI is just to execute special LabVIEW code for capability that isn't native in Vision Builder.  In the later case, it would be very helpful to enable the .VBAI inspection to include the custom VI ( .vi or .llb ) so that the code travels automatically when saving, copying, and sharing the .VBAI file.  There is already a check box to set the path to be "relative" but it would be ideal to have an option to In Line the custom VI directly into the .VBAI inspection so there is no chance to lose / break the code when sharing the .VBAI file.


Instead of a only check box for "relative path" include a second check box which says "embed into .VBAI inspection".  This would not be available in Start Up, Select Produt, or Clean Up parts of the state diagrams, only available in the Inspection State since that is the only state that loads from the .VBAI file.  Checking this box would copy the code into the .VBAI container and the sytem would know that's where to extract the code from.


The "embed" check box would be grayed out unless you first check the "use relative path".


Caution would be needed if copying a Custom VI step from the Inspection state diagram to the startup, select, or clean up states.


Optionally, an "open" option would also be great when you open a Custom VI step that someone else saved.  This way when editing the .VBAI inspection, someone could open the .vi or .llb which was embedded into the .VBAI file.


Perhaps speed would be a concern if trying to run directly out of the .VBAI container?







Simulate acquisition

Import an image in from a .csv format (8 bit, 16 bit, float)



Image Filter: horizontal and vertical projections based on stats (mean, max, stdev).