Home Community Idea Exchange Vision Idea Exchange : New Ideas

Vision Idea Exchange

Community Browser
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
0 Kudos
sevincom

Bug in Custom Overlay VBAI

Status: New Submitted by Member on 02-13-2022 10:24 AM Comment

There is a bug started after VBAI 2020. When user insert measurement on custom overlay text, it does not show up until you go to next line, put a space etc.

Furthermore, when you try to delete a previous measurement that you have inserted in one of your old inspection files, it does not allow you to delete only one measurement. Sometimes you have to delete all the measurements previously inserted.

0 Kudos
sevincom

Mean Caliper in VBAI

Status: New Submitted by Member on 03-21-2021 06:12 AM 1 Comment

Hi,

 

The caliper function does not create accurate results, in general, repeatability is very bad.

I think this can be improved by adding a "mean caliper" functionality.

Currently, there is only min-max caliper functionality which is not working when looking for average caliper measurement.

 

I use geometry step as a workaround, use Find Edge to locate edges, Distance function and finally Calculator step to calculate the average caliper/distance.

 

Mean Caliper function could be added to Caliper function for more repeatable results with ease of use.

15 Kudos
varga.sm

Python Scripting in VBAI

Status: New Submitted by Member on 11-06-2020 08:57 AM 2 Comment

Calling a python script from VBAI requires many steps.  Please make it simpler and more intuitive to run a Python script directly from VBAI.  Even if limiting the return types to the data types currently available in VBAI would be fine.  This would allow VBAI to easily utilize OpenCV more directly and more intuitively.

 

Today, the only way to call a Python script is to build the call through LabVIEW, then build the LV VI for distribution to VBAI, then use a call LV step in VBAI.  For simple Python scripts (e.g. manipulating text strings, move, rename or delete files, getting values from dictionaries) this is a lot of unnecessary steps that prevent people from using Vision Builder.  Even seasoned LabVIEW users often have difficulting building a LV step such that it can be accessed by VBAI.

 

Critical for Debugging: During run, the VBAI step should also return the name and path of the environment being used.

 

 

Bonus: A simple Python editor launched from VBAI would be ideal (such as the free version of Visual Studio Code).

 

 

 

1 Kudos
JN_23

Multi Level Password in VBAI

Status: New Submitted by Member on 01-10-2020 03:33 AM Comment

Dear Team.

 

It would be great to have multi - level password in VBAI.

 

This Direct option would be very helpful to limit accessible features in inspection interface for operators, line in-charge, supervisor and for managers.

 

Thanks and Regards,

NJ

1 Kudos
nestorl

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

Status: Already Implemented Submitted by on 06-04-2019 04:09 PM 1 Comment

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.

0 Kudos
sevincom

Find Edge Annulus Improvement

Status: New Submitted by Member on 01-01-2019 12:42 PM Comment

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)1)workaroundworkaround2)2)

2 Kudos
NIToTH

Deleting Multiple State Diagrams At Once in VBAI

Status: Under Review Submitted by Member on 06-20-2018 11:44 AM 1 Comment

After checking with support, it appears that as of VBAI 2015 f2 there's no ability to delete multiple VBAI state diagrams at once. I have an inspection with multiple states, and would like to modularize/strip off a small subset of the states to import to another inspection. I can delete one at a time, but would be useful to do this easily.

View All (2)
3 Kudos
Telecentric

Ability to display more than two places past the decimal in Vision Builder!

Status: Completed Submitted by Member on 05-04-2018 02:50 PM 7 Comment

Problem Description :
I am unable to enter more than two places past the decimal when entering in
tolerance into the pass inspection if.....
is there an update that can fix this issue? I believe this has never been addressed in any of the new
versions of VB. I can hold micron tolerances but cant do any pass fail because
when i put the numbers in they round up or down. they may be going in but i
cant see them and therefor cant refer back to what was put in because they do
not show past the 2nd decimal place. 

View All (4)
1 Kudos
Amend_H

Problem withe the OPC-UA client in NI Vision Builder 2015 for Automated Inspection

Status: Under Consideration Submitted by Member on 03-23-2018 02:42 AM 2 Comment

Problem:

 When the OPC-UA client make a connection to the server, the client brows all items what he find at the server. In my case, I have more than 3000 Items. Then the software needs about 20 min to show the items. (I need the number of items, then the SPS is just from more systems)

When I start the aplikation, the used memory of the VB goes up to 1,990 MB and the soft ware have no reaction.

When I modify the OPC-UA server to 30 Items is no problem with the used memory.

Normaly when a client brows the Items, they don't look at all, they look only on the item what they need.

Is it posisble to modify the OPC-UA client from the VB that they look only to the needs items?

 

The Problem is in WIN7 32/64bit, Win10 32/64bit.

I need only the Vision Builder to evaluation of images of a camera.

I don't need Labview.

 

 

Best regards

Amend Harald

 

 

Download All
2 Kudos
varga.sm

Configuration Mode Ease of Use for VBAI

Status: New Submitted by Member on 02-08-2018 03:25 PM Comment

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)

 

1 Kudos
varga.sm

System Variables for VBAI

Status: New Submitted by Member on 02-05-2018 03:13 PM Comment

Please include more default VBAI System Variables.

Common and useful system variables would include:

1) Disk Space Remaining on Target default volume (or by drive letter would be even better) in MB

     Target_C_Free = 2203

     Target_U_Free = 435000

... VBAI crashes systems too often when people fill up the hard drive.  Currently the only way to prevent this is with call LabVIEW steps even though the info is already in VBAI under the Target Info menu, just not in the system variables.

2)  Target Temperatures (very useful for NI targets but could be skipped for PC targets)

3)  CPU Utilization %

4)  Pretty much anything you already have in System Info under NIMax would be very useful ... Port IP Addresses, MAC Addresses, Firmware Versions, OS , serial #,  network devices, etc. 

 

 

No need to kill the CPU updating these every 10msec. 

 

5)  And finally an "on event" Boolean flag to snapshot the event log into a string array would be fantastic for troubleshooting.  Currently I can only see the event log when in Config mode which isn't nearly as useful.

 

 

 

View All (2)
1 Kudos
sevincom

Keeping last preferences as default in VBAI

Status: Completed Submitted by Member on 01-24-2018 01:36 PM 3 Comment

I think just like most of other software, VBAI should take the last selection as the default value for this type. This what I mostly require in Custom Overlay steps.

 

Mostly we are using the same text type-color etc. for different elements but because VBAI changes the color randomly, and making the size 13 every time, we have to change it for all elements. Since generally I use one color for most of the text list on the screen, it would be really helpful if VBAI could remember my last choice as default for the next selection.

View All (5)
0 Kudos
sevincom

Set Coordinate System Functionality

Status: Declined Submitted by Member on 11-13-2017 08:20 AM 2 Comment

Hello,

A Coordinate System is not actually functional in measurement applications.

 

When we define a coordinate system, it should set the x axis and the origin as 0,0 in mm or pixels depending on the calibration. Currently coordinate system is only working to define a ROI with changing positions. It always get the positions based on the camera's axis. But it also should work like a real coordinate system where you can get X,Y positions of a circle based on a defined coordinate system.

 

Currently, I am trying to create my own coordinate system by calculating angles, cosines etc. but this function needs to be implemented in standard coordinate system functions.

1 Kudos
varga.sm

Programmatic Control for Enable / Disable States

Status: Under Consideration Submitted by Member on 08-08-2017 12:45 PM 2 Comment

This would help reduce complexity and overhead of VBAI state diagrams.  Often states are created empty with the only purpose is to use transitions to skip or bypass other states.  When a state is disabled, VBAI would skip the steps in the state and immediately evaluate the transitions.   Any transitions which rely on results from a disabled state would be "results unavailable".

 

 

4 Kudos
sevincom

Specify Limits based on Variables/Measurements

Status: New Submitted by Member on 05-18-2017 02:47 PM 3 Comment

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.

 

idea.png

0 Kudos
varga.sm

Calculator step - Compute Results, Expandable Window

Status: Completed Submitted by Member on 04-12-2017 10:20 AM 2 Comment

Long names may get cut off in Measurement window, allow for a separate window, like the View Measurements dialog box, to fully display names and values with resizeable fields, instead of just relying on tool tips

View All (2)
2 Kudos
wkeifenheim

Update VBAI APIs

Status: Completed Submitted by Member on 04-04-2017 04:27 PM 3 Comment

Hello,

 

The updates I'd like to see boil down to the following:

1. Parity between the C and .NET APIs.  There are methods available in the C API that did not make it to the .NET offering most importantly the ability to set VBAI parameters at runtime.

2. 64bit DLLs.

 

I've been using VBAI through the .NET API in production for about a year now, the above requests would make future expansion much easier.

 

Thanks for the consideration.

View All (2)
7 Kudos
Andi_S

officially support again the APID file format

Status: New Submitted by Member on 02-22-2017 12:18 AM 2 Comment

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.

 

 

View All (4)
17 Kudos
Andi_S

Support for U32, I32 and RGB128 Images / Image Type

Status: New Submitted by Member on 02-22-2017 12:03 AM 3 Comment

Current situation:

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.

 

Improvement:

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.

View All (3)
5 Kudos
Hatef.fouladi

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

Status: New Submitted by Active Participant on 09-17-2016 07:57 AM 8 Comment

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
help.png