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!
More and more image sensors do support bit depths of more than 16Bit.
Just two examples: Aptina MT9M034, Omni Vision OV10640
Currently it is not possible to handle image from those sensors within LabVIEW except as a 2D-Array / Matrix.
Using the SGL image type would be possible on the first sight but it has several disadvantages: storing of those image is not possible and a lot of image processing and calculation function do not support SGL.
Add support for the image types U32, I32 and RGB128. Personally I see the priority at U32 and I32 because those types are needed to handle the RAW data from the sensors.
Very important: Do not just add those types to your typedef! There must be a real support from all basic functions!! Basic functions are in my opinion / for my usage: write to file, read from file, all functions in the palettes "Vision Utilites", "Processing", "Filters", "Operators" and the functions "Histogram", "Histograph", "Line Profile", "ROI Profile", "Linear Averages" and all other statics functions.
I don't know what the current official status of AIPD is, but the polymorphic "IMAQ Write File 2" VI which is in the LV palette does not offer AIPD in its selector. For me this means that there is no official support for AIPD anymore.
Unfortunately there is also no alternative for storing SGL or complex images.
My request: Add the AIPD format as an officially supported file format to "IMAQ Write File 2" or offer an appropriate alternative for all image types.
This could be a good improvement to create good programs in VBAI.
It could be very good if we can set the limits of functions based on variables or previous measurements. It is like how we can use the previous measurements when we Create ROI, select the position of a Custom Overlay.
Without this option, creating a user interface is not really functional, because whenever there is anything new, you need to go to programming interface and change the limits. But if we can enter variables for the limits of a function, we can create a good program to automate the inspections much more.
With this way, the operator can make everything without going to programming.
And it can also be very helpful to create operator independent automated inspections, which is very important for Quality Management System.
Use case : I create inspection templates in VBAI so that my customers have a base to start from.
I'd love to be able to "lock" a state, just like I can lock a VI in LabVIEW (with the same options : with or without password).
It would be practital if locked states could have a different colour and if we could put some text next to them on the diagram to explain why they are locked.
This way, it would be much easir for my customers to know what part of the inspection they can work on and the part that they are not supposed to modify (sometimes they modify things by mistake, but the undo will one day take care of that)
there are some vi in vision toolkit that their controls have not any useful information in labview help for user so many ability of these vi are not discovered by LV user like me for example IMAQ Particle Filter have input control with name of selection value inside this cluster we have item with name of Measurement Parameter that have many mode to select but no detail information for them to know what kind of ability they have I think in next version of this toolkit it should be release with enough information about these controls of such vis
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.