Vision Idea Exchange

Community Browser
About Vision Idea Exchange

Have a Vision Product Idea?
  1. 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!
  2. 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.
  3. Watch as the community gives your idea kudos and adds their input.
  4. 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.
  5. Give kudos to other ideas that you would like to see implemented!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 
Post an idea

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.



I noticed different cameras have different names for setting exposure time. Here's some examples:

  • CameraAttributes::AcquisitionControl::ExposureTime
  • CameraAttributes::Exposure::Value
  • CameraAttributes::AcquisitionTrigger::ExposureTimeRaw
  • etc

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

  • Vision Acquisition Software

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.

Imho this behaviour is more like a bug.

  • Vision Acquisition Software

This idea is something I have implemented in house and posting is motivated by the following discussion:


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.

  • Vision Acquisition Software

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

Setting My Camera Attributes Programmatically Does Not Permanently Change the Attributes


Currently, we cannot update .icd file through LabVIEW using IMAQ. The only way to do so is saving new values in MAX.

However, IMAQdx has this functionality. It would be very convenient if we can update .icd files using IMAQ as well.

How Do I Programmatically Load or Save a Configuration File with IMAQdx?

  • Vision Acquisition Software

The title says it all, but let me expand a little...


Since LabVIEW 8, trying to create a VI from a selection containing a reference to an Image Control fails. It does absolutely nothing, nada, nitchevo, nichts, rien...

There are at least TWO CARs about it: 54165 and 35835.

Yet, years after years, nothing is done about it.


A workaround for creating VI is to remove the connections to any of the image control references in the original selection, and once in the created subVI, drop a custom control that you will have strategically dropped in your Favorites Control Palette:


Screen Shot 2016-11-29 at 14.49.41.png

Then you need to add it to the connector pane, reconnect in the original calling VI...

Not the easiest but manageable.


Now, what about managing events using a Register Event node handling several controls, including a couple of Image controls? Usually, when not using images, I bundle references to the controls and do the Event Registration in a subVI (there are typically a lot of wires and large nodes involved, therefore this would take an undue amount of real estate in a main VI).

The problem is, any cluster containing a Image Control Reference can apparently not be created as a control in a "Create subVI" or even a "Create Control" operation:


Screen Shot 2016-11-29 at 14.56.09.png



Screen Shot 2016-11-29 at 14.57.20.png


Once again, it is possible to do all this manually, but if you have a bunch of Image Control references and other references to bundle, this is becoming rapidly tedious.

  • Vision Acquisition Software

I had a long lasting SRQ on this one but nothing came out of it and I'm left with the issue.


NI is aware of the issue and the work-around is : do not disconnet a USB device while you have triggered GigE (IMAQdx) acquisition in progress.

SRQ 7395589


I'm being forced to create an idea to try to get more momentum for a CAR to be created.

  • Vision Acquisition Software
0 Kudos


I've Labview 14.0,  i have to make project involving recognizing colours. I installed Vision Acquisition Software 14.0 but there is something wrong because i don't have this blocks like IMAQ Particle Analysis, Reject Border ect... Is that IMAQdx driver missinng or i need some driver for Windows 10. ? Thank You for help Smiley Happy

  • Vision Acquisition Software
0 Kudos

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 

  • Vision Acquisition Software
0 Kudos

Greetings Vision Idea Exchange Community,


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.


Regards, Scott


High Altitude Observatory Boulder, CO