Vision Idea Exchange

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)

View All (1)

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

View All (1)

This is probably not a simple thing for NI to implement but I always thought it would make sense to make the IMAQ image a native data type. When I first started using LabVIEW, it took me a while to get used to the image data type and understand that it is just a pointer to a named image in memory and the pointer is passed between image operators. I am used to it now but it still seems clunky to me. Why can't an image constant or control implicitly create an image and they can be implicitly destroyed at the end of a program. Branching a wire would create two copies of an image that could be operated on independently. At the moment my imaging code always looks quite messy because I often need to create temporary image buffers for intermediate operations.

I think this would make the imaging tools a more wholistic addition to labVIEW and make it feel less like something that was adapted from another language. Sure there would be some impact on performance, but isn't that why we use LabVIEW? Simpler programming at a higher level.

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:

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:

FAIL!

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.

View All (3)

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

View All (1)

Hello,

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.

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.

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.

View All (1)

View All (3)

1) Allow us to easily comment each step

2) Allow us to easily see comments as we step through the program in config mode

3) Allow us to comment the state diagrams

4) Give a record button in the tool bar in config mode to record acquired images (without having to put down an image logging step in the code)

5) Give a film strip view option (perhaps between the main window and the steps) to show the last n images. The strip would show the short history of acquired or selected images so it would also work with a multi-camera setup.

6) Give an option when image logging to save the image as shown by the color pallet lookup table displays. (especially good for 3D or thermal images)

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

Add a Rotated Ellipse ROI tool... heck, add a Rotate any ROI ability!

Ability to lock states in Vision Builder AI

Multiple File Paths In Vision Assistant

Affine Transformations to Rotate an Image Based on Roll, Pitch, and Yaw Angles

ROI editable with a spline

IMAQ Overlay Line Style

Make IMAQ image a native data type

Fix the Create Control from Image Control Reference bug!

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

NI Vision Template Editor as Express VI

Specify Limits based on Variables/Measurements

Particle Analysis Input Image Type

File Close functions should return File Path (from Refnum)

Ni-IMAQdx skip error

Reset to default in Vision Assistant

Add Vision Development Module to LabVIEW Community Edition

Labview Should create a photometric stereo VI

Support for MAC OS for Vision

Configuration Mode Ease of Use for VBAI

NI Vision Run Time Engine License check