Vision Idea Exchange

Post an idea

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

ROI editable with a spline

Particle Analysis Input Image Type

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.

Support for MAC OS for Vision

View All (3)

Reset to default in Vision Assistant

View All (5)

Lines at quadrant angles are smooth. But lines with different angles are jagged. It would be better if the rough edges are smoothed.

Download All

View All (1)

It would be a useful feature addition to Vision software to add functionality to report coordinates of an object in a new coordinate system. A main use case would be if you needed your region of interest to be based off of one coordinate system, but once your object was located, you wanted to report the location based on a different coordinate system. Building in this functionality would eliminate the need to configure calculator steps to translate/rotate the coordinates.

CAD file to overlay function

Enumerate Cameras (à la MAX)

MAX will list all of the Cameras that are attached to the PC, along with attached DAQmx Devices, VISA Devices, and other Devices. There is a very useful DAQmx System property node that returns an I/O reference to all the DAQmx Devices, allowing the user (me) to "find the USB-6002 with serial number 12345 that I so carefully calibrated and am using in my Test". I'd like to be able to do the same thing for Cameras -- I have multiple cameras visible in MAX, but I want my code to use a particular Camera and would like to programmatically "discover" it by enumerating the Cameras and getting relevant properties (Name, Serial Number, other ID information, potentially IMAQdx parameters) to find the Camera I want to use.

Bob Schor

View All (2)

I want to view the camera image collected through the capture board through LabView.
The camera I'm using is a Fluke IR camera, and it doesn't support connection the same way as a regular camera. That's why I'm trying to do the display through the capture board.
When searching for previous experiences in the community, there were cases where VMS (Video Measurement Suite or Video master) solved this problem, but I couldn't find VMS.
This seems to be an unsupported feature already, is there any other way?

https://forums.ni.com/t5/NI-VideoMASTER-and-NI/Capture-Frame-with-PXIe-1491-and-videoMaster/m-p/2391296#M140

Snapshot option for Probes

IMAQ Overlay ROIs

Hi,

Say, I am going to build a system and control it using labview through DAQ.

For example, the system has stepper motors to move a heating chamber back and forth, a temperature monitoring system, a pressure controlling gauge etc.

Now, before diving into building the actual system, Is it possible to make a simulation of the whole device and integrate the necessary LV coding, where I can show on screen how the LV program controls the different parts of the system?

Thanks.

View All (1)

Find Edge Annulus Improvement

It can be improved in two ways:

1) It should work in radial direction with gap parameter in order to better apply different scenarios. Similar to Find Circular Edge function, but the aim is search for defects rather than a diameter. So, it could be implemented in the Annulus Tool of Find Edge function.

2) Many annulus should be added like a combination of image 1 and 2, with two gap parameters.

Current workaround is using a polygon tool, which is very time consuming and not fully functional.

1)workaround2)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

Vision Idea Exchange

enough description for IMAQ Particle Filter input control and other similar data

ROI editable with a spline

Labview Should create a photometric stereo VI

Particle Analysis Input Image Type

Support for MAC OS for Vision

Reset to default in Vision Assistant

IMAQ Is Vision Info Present / Remove Vision Info VIs should accept multiple types of Vision Info

Overlay Line Smoothness for different angles

An indicator for iteration time in IMAQ setup match pattern

Built-in Function to Report Coordinates of an Object in New Coordinate System

CAD file to overlay function

Enumerate Cameras (à la MAX)

Using Image Operators ADD MAX AVERAGE should maintain the image calibration info

Displaying the images collected by the capture board in LabVIEW

Image Display visible items to include image name

Snapshot option for Probes

IMAQ Overlay ROIs

Simulation of an actual device and coding

Find Edge Annulus Improvement

IMAQ Find Circular Edge should return an array of circles