Vision Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

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

I am using NI Myrio FPGA to do image processing. With the help of NI Vision Assistant 2014, i am able to get the image from usb webcam. I want to use FPGA to convert the image to HSV. However the functions provided in NI Vision Assistant only allow me to get either H, S, or V image at once.

In order to solve it, i try to create one more FIFO to store the image. Here is my FPGA coding.

fpga code.jpg

 

However, I do not know how to access these FIFO. Here is Labview coding.

code 1.jpg

code 2.jpg

All these coding are actually generated by NI Vision Assistant and i cant find where can specify which FIFO i am accessing. Any can help me?

VBAI is a nice tool for some vision program, but the interface language is english.   I know many engineers in China cann't understand it cause of English interface. but I can translate all of the interface words into chinese. If you wanna expland market in China, maybe i can help you to translate it.

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? Thanks

When working with LabVIEW Files, there are two ways to get the File Path back from the File Refnum -- one is to use the Close File function (which takes Refnum in and returns Path out) and the other is to use the Refnum to Path function (which I didn't know existed until today).

 

However, this very convenient "inverse transform" is not present in the NI Vision for AVI2 Files -- IMAQ AVI2 Close doesn't return the Path, and the Refnum to Path function won't accept an AVI Refnum as an input.  Assuming that the original Path information is contained in the DLL at the time that AVI2 Close is called, please return it (as a Path or as a String) when the AVI is close.  Alternatively, provide an AVI2 function (perhaps an extension to the existing IMAQ AVI2 Get Info) that returns the File Path.

 

 

What about the possibility of targetting PXI-RT (ETS or Linux-RT) from VBAI ?

According to the manual, only dedicated vision systems are actually supported as remote targets, but maybe in the future ?

 

Also, what about directly targetting FPGAs 🙂 ?

 

Thanks in advance,

 

I don't know if anyone else has requested this: It would be great if VA kept a track of the Template folder and Image file folder separately. I have to constantly load new templates and images and the program only remembers the last folder used, which means constantly navigating.

Affine_Transform.JPG

Many times in computer vision, specifically when applied to field of robotics, it may be useful to perform an affine perspective transform on an image based on the robot's roll, pitch, and yaw angles coming in from an IMU. These VI's can be used to project input images into naider view which were originally taken at some alternate roll, pitch, and yaw angle. Applications include improved object recoginition, gimbal replacement, and more accurate visual servoing. 

Download All

The type of barcode is ubiquitous and it is on all USPS letters.

It would be better if we can readily store a set of images in database using some vi, so that we can compare it with real time images.

Hi

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).

Binned images are very useful for reducing processing time when you are looking at the entire image.  It would be very useful to have a function that would perform binning on an image to generate a new image.  The binning factor could be anywhere from 2x2 to 32x32 or even larger.  I would be happy with powers of two, but any integer value would be even more useful.  Different values for the X and Y binning would also be useful.  The values could be simply added together and divided by a user specified divisor, much like the filter options.  It would be similar to the existing IMAQ Block Statistics, but the output would be a new image ready for processing.

 

Right now, binning can be accomplished by multiple steps - filtering with the appropriate size filter, then using IMAQ Extract to reduce the size of the image.  This is much slower and less efficient than a single binning function would be, since the filter must be applied to every pixel, instead of just the pixels you are keeping.  It could be done in place on the original image if desired.

 

Bruce

When Vision Assistant steps are converted to LabVIEW VI, the overlay of result (i.e. edge detect, particle counts) is lost.

no overlay.png

 

Adding overlay function on VI requires not only LabVIEW skills, but Vision knowledge due to image memory handling.

So it'd be nice to have an option to keep the overlay functionality on Vision Assistant even when converting to LabVIEW VI to have a smooth transition.

 

Ryuji Kuwajima

Hi there!

 

I wanted to propose a new tool to draw a ROI in the Vision Development Module and in the VBAI: maybe using the spline, the ROI will be more accurate for some particular inspections.

 

Tank you so much,

bye!

 

FBM

Setting My Camera Attributes Programmatically Does Not Permanently Change the Attributes

http://digital.ni.com/public.nsf/allkb/09794AF61D4CE35286256DBA0075150A

 

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?

http://digital.ni.com/public.nsf/allkb/1C2357D44FE7F25C862576C300509B13

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

 

http://forums.ni.com/t5/Machine-Vision/Simulate-GigE-Vision-Basler-Runner-Camera-ruL2098-10gc/m-p/3076940#M44384

 

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.

3

Linescan smart cameras

Speed and sensitivity critical.  48kHz line rate with excellent sensitivity from blue through NIR.  Blue is needed for online fluorescent applications, white light is for most applications, and NIR for inspections that need to avoid the influence of graphics.