Vision Idea Exchange

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

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.

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

This is about a debugging function in VBAI I miss. If I have a state diagram of some complexity, I might want to start some states combined with each other.

 

What I currently already can do:

  • Run the whole Inspection Once / in Loop / until Failure

Run Inspection

  • Run a single State Once / in Loop

Run State

 

What I would wish to do:

Think of the following diagram: I have two cameras, triggered and run with independent branches of the state machine, as in this picture:

State Diagram 2 Branches

I want to run only one of the branches, i.e. for debugging. Now I would like to do something like this:

 

Run States

Current workaround:

I can run „Set Camera Trigger 1“ once, then „Get and Process Image 1“ once, that would have the same effect (as „Run States Once“)

Is there a way to "get camera extra information from image" when I'm using the Simulate Acquisition step?  It seems like if the information is in the image it should be gettable from either the Acquire Image or Simulate Acquisition step.

4

VBAI

Simulate acquisition

Import an image in from a .csv format (8 bit, 16 bit, float)

3

VBAI

Allow data logging to shared drives or server paths just as to local drives.  Image and data logging steps do not accept a server path such as //162.198.1.23/Images

Currently you have to first map a network path to a drive letter in Windows to save images to a network path.  This is for network locations which are shared locations, not FTP.

3

VBAI

Enable right click on the image control to allow menu options normally under Tools->Options->Image Display

Set display pallet

Set 16bit mapping method options

 

3

VBAI

Histogram head / tail by percent

Currently the pixel counter returns the % of the histogram which is above/below a gray value but this tool would do the reverse:  return the gray value of an ROI which is at the x% of a histogram.  In addition to % head/tail, it would be very helpful to have an optional check box (disabled for speed when you don’t need it) to return other common distribution stats such as # of modes, normality test, skew, etc.

2

VBAI

Advanced Edge, Multi-edge mode: When expecting N edges, SNR noise needs to be calculated based on the residual RMS signal level to avoid inappropriately low SNR reporting.

Currently, the edge #1 SNR is based on strength of edge #2 which will result in a very low SNR for edge #1 if #2 has a similar strength. 

2

VBAI

Tool request:  Profile

Create an array to output the intensity profile for a line, path, or area (see Filter above).

 

This is currently available only as a display and manual export in the Vision Assistant mode but it cannot be used in any VBAI automated step.  The array is not available for export in an automated method.

 

2

VBAI

VBAI step for programmatic control for grayscale operator (e.g.  Subtract a gray level based on the results of a previous step histogram).   – OR – Update the Vision Assistant tools to use inspection variables for all their set points.

Basic functionality missing from VBAI; available on the lowest cost smart cameras from most major competitors.

2

VBAI

16 bit support for thresholds, detect objects, etc. 

Advanced edge tool will not work on low contrast 16 bit images unless the Straight Edge Settings; Minimum Score is set to 0 (make 0 default then?)  Also the Advanced edge tool max score is 1024 so it cannot find edges with stronger transitions which often occur in high contrast 16 bit images.

1

VDM

VBAI

Image FOV balance with a reference image or by a polynomial fit.

Common functionality available in most compettitors’ systems