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!
One of my problem for creating image processing project is to make a special overlay that should be rotate expand shrink or change in size, based on processed data in many times creating code for such overlay waste so many time for calculation and test because of so many geometry concept that we should regard and I have to allocate most of my time to solve this problem instead of using this time to solve processing problems that are more important than overlay I think if we have a assistant software in Labview like file ,daq,imaqdx and ... assistant in labview that we could use it for design special overlay and also define variant that should be change based on processing data we will be save so many time to allocate solve image processing issue instead of making an overlay I think it is possible to make such assistant and also I could help to NI to production of this assistant software
i'm looking forward to average images (number is 2 to the power of n). I've got a solution but it is slow, so having labview compute the shift on the image itself would be nice, since all the other basic operations are there already. my slow solution attached (U32 RGB and I16 GrayScale), the image logical shift does not necessarily need to preserve the "missing" bits
We have a critical need to apply a 4096 element U32 Lookup Table to our IMAQ images and were really hoping that it wouldn't be to hard to modify the existing shipped VI from the VDM package (IMAQ UserLookup 2 VI to be able to handle LUT's of greater bit depth.
This is of course a proprietary code from NI so we can't work directly from it. Has anyone one the community been able to write an (optimized) look up table VI/DLL which can take as input a 16 bit image and lookup to a 32-bit image depth?
Our application is correcting machine vision camera output frames for bit error and non-linearity corrections for which we need at least 22 bits of LUT so we decided to simply go to four byte pixel depths.
in the case of own software development with VDM it is usefull to write and read in the border. Now I copy my images in a larger image to create my own border. That costs performance. A additional boolean variable for the set/get pixel value vi which references the origin to the image (without border) origin left top (implemented) or the border+image origin left top outside of the image (not implemented).
In Vision Assistant 2014 SP1, the "Create LabVIEW VI" function does not create a calibration file path in the generated code, for the Image Calibration function. Instead it reads in all of the calibration information and sets these to constants (or controls if selected it in the wizard) in the generated code. It would be good if this maintained a reference to the template.
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.
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.
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.
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.