Vision Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Ozfarmboy

Vision Assistant Code Generator to maintain Calibration File Reference

Status: Already Implemented

Since all calibration methods except simple calibration use a calibration file path as you suggested, I am marking this as complete since we don't plan to do this for the simple calibration case, but all others already do what you want.

In Vision Assistant 2014 SP1, the "Create LabVIEW VI" function does not create a calibration file path in the generated code, for the Image Calibration function.  Instead it reads in all of the calibration information and sets these to constants (or controls if selected it in the wizard) in the generated code.  It would be good if this maintained a reference to the template.

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

2 Comments
ChristopheC
Active Participant

There is no reference to the calibration file and we calibrate "on the fly", when the calibration method is "Point Distance Calibration" (Simple Calibration), because there is no learning associated with this method and the time it takes to calibrate the image with this method is instantaneous.

If you choose any of the other methods, the code generated will point to the calibration file saved, and the code generated will apply the calibration from the template file to the current image, without relearning it, for optimization purposes.

This was a design decision, and unfortunately, there is no workaround at this time for the simple calibration case.

Brad
Active Participant
Status changed to: Already Implemented

Since all calibration methods except simple calibration use a calibration file path as you suggested, I am marking this as complete since we don't plan to do this for the simple calibration case, but all others already do what you want.