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!
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.
Watch as the community gives your idea kudos and adds their input.
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.
Give kudos to other ideas that you would like to see implemented!
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.
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?
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.