+2

Probe results – automatically alarm for excessive deviation from theoretical/previous measured results

Dbolt hace 6 años en Metrology Software / PC-DMIS actualizado por Neil Challinor hace 19 horas 8
It would be useful to have an alarm pop up on calibrating tip angles that would trigger when the deviation between the theoretical and the measured value exceeds a set limit (user defined by probe file) and/or the measured value changes more than a set amount (user defined by probe file) from the previous measured value.

This would make it easier for operators to notice and react to issue like bent tips or failed indexing of the probe head.

Auto probe Calibration Command: notify operator of any probe tip exceeding STD Deviation or Tip Ø Tolerance with a POP UP Dialog Box is a good Idea.

All too often operators forget to examine the results of the auto probe calibration(s) before running the CMM Program. They then waste time running the program and get erroneous results. 

A pop-up Dialog Box notifying the operator of the probe calibration error at the end of auto calibration command, but prior to running the program any further, would prevent this from happening

The problem that I am looking for a solution is:

operators run through the auto calibration for each probe used in the program but do not check to see if STD Deviation or Probe Ø limits have been exceeded. They continue to run the rest of the program. 

I want a Pop-Up DIALOG Box to come up on the computer screen to show the error so that they become aware of the problem. They would have to fix the problem before continuing if a dialog box opens up.

I know that the error shows either in the report screen or in the edit window. I have told operators many times to check results before continuing program... some of these operators want something to pop up to let them know and just cannot seem to take 30 seconds to check results before proceeding. I have done the same thing myself a couple of times over the years.

En revisión

I believe Inspect has a setting for std dev for calibration, and the ability to block operators running programs.

That's exactly the use case that check calibration limits functionality is designed for.  You can add the applicable commands to do exactly what you describe.


Alternatively, you could use the approach show in the "Auto Calibrate Rack" example from the "Example Routines" section of the "Discover" tab of the "Home page"...

Image 701

Or run PC-DMIS through Inspect: Calibrating Probe Tips

Neil et al,

????


I started looking at the example you referenced.

The example checks every probe tip angle for each slot. If you are using many probe tip angles the program code would be huge.

Is there a way to simply look at the results of the probe Cal for pass or fail:

What i mean is if there is a failure the results always show which tips failed at the bottom of the results output.

Instead of evaluating each tip for pass/fail can the autocalibration results output itself be examined for pass/fail and a comment pop up to notify operator regardless of 1 or 100 tips failing.

You would only examine each Slot for failure instead of individual tips

Then the operator can go look at the results to see which Tip(s) failed. 

I do not need the comment pop up to reference every tip failure ... only that it failed.

This code would be very short.

Thanks,

Robert Radley

CMM Programmer

Desk (360) 639-6471

Cell (253) 279-5179

20350 71st Avenue NE, Suite C
Arlington, WA 98223

Another solution would be to put an operator comment after the probe Cal to verify the results before proceeding if my earlier idea is not able to be done. This would remind the operator to check results. The comment could instruct the operator to open the report window and verify there is not any out of tolerance condition(s) before proceeding

I would prefer an error message before this option though.

As I've been trying to explain, the CHECKCALIBRATIONLIMITS/ toolkit command combined with the ONERROR functionality does exactly what you are requesting.  See the code example below:

 LOADPROBE/X1H_2BY50
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=90
L1 =LABEL/
ASSIGN/CAL_CHK=0
AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_MANUAL,
CHECK COLLISION=NO, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO
BEGIN AUTOCALIBRATE RESULTS FOR PROBE X1H_2BY50 USING SET ALL-TIPS-WITH-DEFAULTS
END AUTOCALIBRATE RESULTS FOR PROBE X1H_2BY50 USING SET ALL-TIPS-WITH-DEFAULTS
ONERROR/CALIBRATION_OUTSIDE_LIMITS,SET CAL_CHK
CHECKCALIBRATIONLIMITS/IF/CAL_CHK<>0
C1 =COMMENT/YESNO,NO,FULL SCREEN=YES,AUTO-CONTINUE=NO,OVC=NO,
Calibration failed!

Please check the results and remedy the problem

Do you want to try again?
IF_GOTO/C1.INPUT=="YES",GOTO = L1
ROUTINE/END
END_IF/
$$ NO,
.
.The main routine would begin here
.
.
.

The example uses an AUTOCALIBRATE/PROBE command to calibrate the ALL-TIPS-WITH-DEFAULTS parameter set (all tips associated to the active probe file using the default settings).  The CHECKCALIBRATIONLIMITS/ command checks if any of those tips failed calibration and, if so sets the CAL_CHK variable referenced by the ONERROR command to 1.  The IF/ statement then checks the value of the CAL_CHK variable and acts on it.  If it is 0, the IF/ block is skipped .  If it is anything other than 0, the If block is entered and the YES/NO comment is displayed.  If the operator clicks YES, the IF_GOTO command jumps back to label L1, resets the CAL_CHK variable to 0  and the process is repeated.  If the operator clicks NO, execution is cancelled by the ROUNTINE/END command.