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!
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.
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.
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.
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.
Create an array to output the intensity profile for a line, path, or area (see Filter above).
This is currently available only as a display and manual export in the Vision Assistant mode but it cannot be used in any VBAI automated step. The array is not available for export in an automated method.
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.