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!
I have run into this problem with the Vision run time, Vision Acquisition run time since I began using Labview. The problem here is that every time I upgrade my development software for example Vision Development Module 2016 to 2017 then update my customers they need to actively re-license both the VD run time and VA run times. This seems to make no sense since both run times were already activated in the previous version. This is a real issue when you are updating software on customers machines that have no internet access. The Vision Development run times need to automatically transfer from version to version since the Vision run time keys are good indefinitely for updates. This would prevent customers from having to re-license yearly like they do now which in my opinion does not make sense. At the very least there could be a way to add a 20 character code problematically when updating versions so users don't have to work their way through NI's license manager.
With the release of LV 2017 and therefore Vision 2017 I expected the 2GB limit to be gone.
Unfortunately and with great diappointment I have found out that this was not the case and it's still not possible to create or handle image files greater than 2GB even in LV 64bit 2017.
Latest linear image sensors can go up to 32.000 pixels (per line and per channel) and we currently use a 16K sensor in our camera and easily can exceed the 2GB limit when we scan long materials specially if 16bit precision is required and RGB color is also needed. This means that we had to implement several tricks in order to break down the image size (we process each RGB color layer as a separate image file and divide the image in several chunks) but we are still anyway experiencing many bottlenecks and are frustrated in the software development because we cannot use many of the exhisting Vision tools that are limited to 2GB. And of course VISION/IMAQ libraries cannot handle image processing when image information is distributed into different images and therefore we had to write our own libraries (even for image viewing) so as to handle the images properly.
Furthermore, despite the TIFF format is limited to 4GB (not 2 GB) it's relatively easy to split the image file into separate TIFF files while it's not easy to handle or process image data in separate chunks or channels. Furthermore there are also other image formats that allows for very large file sizes (i.e. BigTIFF which is extremely easy to implement as it's only a 64bit extension of the currently 32bit limit in the TIFF format).
So my suggestion is: to break the 2GB limit and finally allow handling very large image files directly into Labview and the Vision libraries !!!
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.
The zoom tool of the image display control is antiquated. Currently (Vision 2016), you select it and then click in the image to zoom by a fixed amount.
Consider upgrading its capabilities to match modern UIs:
- Selecting a rectangular ROI with the zoom tool should zoom to that ROI, i.e., the ROI should be expanded to fill the imag display control.
- support mouse wheel (and touch screen if needed) to act as a zoom in and out no matter which tool is selected.
- support fixed aspect ratio hot key (e.g. Ctrl key): zooming with the above ROI selection while the hot key is pressed will zoom the image to fill the display with the largest (or smallest) dimension of the ROI.
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)
Functions* that insert overlay's into images can define a Group, so later you can e.g. delete the whole overlay group at once. Currently there is no VI that would be able to get a list af all Group names preset/used in the image (if you e.g. load an image saved with overlay's and you want to know the Group names, so you can access theyr properties). It could look like this:
Then it would be also easy to get properties if all of the overlay group's (with IMAQ Get Overlay Properties VI)... This VI could also return a array of integers, that would give information about how many Bytes each overlay group uses in memory - for debuging puposes, or if you have some memory shortage problems...
IMAQ Overlay Arc IMAQ Overlay Closed Contour IMAQ Overlay Line IMAQ Overlay Oval IMAQ Overlay Points IMAQ Overlay Rect IMAQ Overlay Text
It would be _really_ helpful if LabView could read/write mp4 / h.264 files, so please could that be added to a future version? I'm working with a company who generate long mp4 files that are quite efficiently compressed. These need to be analysed using LabVIEW but to create an mjpeg version just so that LabVIEW can open it wastes a lot of time and space + needs another software install. It's embarassing to say that LabVIEW just can't do it.
ps please can we have the ability to read / write data fields on AVI files put back in to the latest versions?
It would be really great if there was a way to have one function "Set Exposure" that would work for most cameras. This is analogous to how in IVI, you can have generic instruments and use the generic drivers to control them. Maybe we could assemble some sort of user driven database file we could download to provide a look up for the correct attribute for a given camera.
Another option is to iterate through the list and see if any of those attributes are present on the given camera and apply the setting to the one that's matched.
There's other really common settings like exposure mode (auto vs manual), gamma, gain, pixel format, etc
When a camera is not present in MAX, it disappears. I'd prefer if they would show but show disconnected, so that they can be managed a bit and allow us to change some items (at least in the database, I know changes will not be saved to the camera). For example, in the image I'm upgrading a camera, but I cannot rename this camera because the previous camera had the same name, and now I need to go find the old camera, rename it to something else, THEN I can name the new camera with the original name.
In Vision Development Module, it seems new functions are being created to replace older versions from time to time. ie: IMAQ Set Calibration Axis Info.vi --> IMAQ Set Calibration Axis Info 2.vi. This is fine, however, the Vision Examples still use the older versions of these VIs, ie. they don't seem to have been updated also.
For instance: Using Vision Development Module 2014 SP1, example Simple Calibration.vi. In this example, the following VIs are being used: IMAQ Setup Match Pattern 2.vi, IMAQ Match Pattern 3.vi, IMAQ Set Calibration Axis Info.vi. However when you look at the LabVIEW functions pallette, the following VIs are available: IMAQ Learn Pattern 4.vi, IMAQ Match Pattern 4.vi, IMAQ Set Calibration Axis Info 2.vi.
This tends to confuse things. It would be great if the examples were also updated to use these new functions available
Also, the help files do not seem to differentiate between these older and newer functions.
I would like to have the ability to add a simulated imaq camera in max to use with the imaqdx driver.
The camera should be able to specify wither it is linescan or area scan, as well as sensor size and specifications. The simulated device should support the basic property nodes (AOI, exposure line or frame rate ..... could even have a xml for iGenCam). Ideally the source of the image (directory) could be specified so that grabs or snaps would play back previously acquired images or a test pattern could be selected instead.
I might be asking for too much, but this allows for offline testing on vision systems, something that is common after deployment.
When merge overlay is performed on image with multiple overlay groups, it merges selected group (correct) and clears all others (wrong!).
It seems that it should affect only what has been said to it (selected group), and do not touch what belongs to somebody else. If you need to kill all other overlays, use clear overlay after it. Or new version needs a switch to not kill other groups - for compatibility.
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
Supporting only binary images as input type for the particle analysis is reducing the use cases where this functionality can be used. In many segemtation methods, e.g. superpixel segmentation or watershed segementation, the segmentation result is a labeled image. Being able to perform particle analysis on labeled images would enhance the modularity of this function. Since the particle analysis in internally performing probably a labeling anyway, and in many cases, the label of an object which is to be analysed is known too, it could also reduce the computational cost of this function.