Probe Qualification Results/Statistics

In the PC-DMIS folder (I am using 3.7, 2010 may be different) there are .RESULTS files.
These are updated every time you calibrate.

When opened with MS Notepad the text looks like this:


Probe file=NO EXT Date=8/3/2010 Time=3:56:25 PM

T1A75B180 THEO X -0.0000 Y -3.9169 Z 4.0810 D 0.0787
T1A75B180 MEAS X -0.0000 Y -3.9169 Z 4.0810 D 0.0787 StdDev 0.0000

T1A90B0 THEO X 0.0000 Y 4.0551 Z 3.0315 D 0.0787
T1A90B0 MEAS X 0.0000 Y 4.0551 Z 3.0315 D 0.0787 StdDev 0.0000

T1A90B90 THEO X -4.0551 Y 0.0000 Z 3.0315 D 0.0787
T1A90B90 MEAS X -4.0551 Y 0.0000 Z 3.0315 D 0.0787 StdDev 0.0000

I am sure there are ways to use this info. I have not had the need, so have never learned.
Maybe with 2010 this data is available in a way that is easy to access....

Yep, I know of the .RESULTS file, and have been reviewing them for quite some time. What I'd like to do is get the measured data from those files into a stats program, so that I can further analyze them there, and also use the stats program to create alerts for when standard deviation is exceded, etc. If I were able to get those measurement results into a dimension within PC-Dmis, then I'd be able to transfer them using the stats out command.

Yep, I know of the .RESULTS file, and have been reviewing them for quite some time. What I'd like to do is get the measured data from those files into a stats program, so that I can further analyze them there, and also use the stats program to create alerts for when standard deviation is exceded, etc. If I were able to get those measurement results into a dimension within PC-Dmis, then I'd be able to transfer them using the stats out command.

You can set up the probe-cal routine to give a warning when the STD-DEV is too much and also when the SIZE deviates too much.

I've set up all of the warnings as you mentioned, but from what I've seen, and I should have specified this, when using the STI interface, the warnings don't appear for whatever reason. I know you can also setup some requirements for how often it qualifications need to happen, and those don't work either. I'm running 3 machines with the STI interface, and have operators that are doing daily qualifications, checking their own parts, etc. I'd like to transfer this information to a stats program, just so that I can use it to monitor how the qualifications are going, or, lets say for instance, if they're even bothering to clean things before qualifying, or even qualifying the CMM. I'm thinking about trying to pull the data in from the .results file, but am just curious if there's a better way.

I've set up all of the warnings as you mentioned, but from what I've seen, and I should have specified this, when using the STI interface, the warnings don't appear for whatever reason. I know you can also setup some requirements for how often it qualifications need to happen, and those don't work either. I'm running 3 machines with the STI interface, and have operators that are doing daily qualifications, checking their own parts, etc. I'd like to transfer this information to a stats program, just so that I can use it to monitor how the qualifications are going, or, lets say for instance, if they're even bothering to clean things before qualifying, or even qualifying the CMM. I'm thinking about trying to pull the data in from the .results file, but am just curious if there's a better way.

I've not done it myself, but I think you CAN access those values from within Pcdmis and using CODE, have it STOP and pop-up a warning telling the operator that they have a problem with the calibration. This should get past the STI issue. BUT, I can't tell you what the coding would be, but I am almost certain that it has cropped up here before. Someone wanted the info in the CMM report and I think there was a way to get it there.

PROBEDATA can get you mmuch info.

assign/v1=PROBEDATA() this gives active probe tip

assign/v2=PROBEDATA("TOFFSET") this gives THEO offset

assign/v3=PROBEDATA("OFFSET") this gives actual offset

assign/v4=PROBEDATA("VECTOR") this gives vector

assign/v5=PROBEDATA("A") this gives "A" angle of wrist

assign/v6=PROBEDATA("B") this gives "B" angle of wrist

assign/v7=PROBEDATA("TDIAM") this gives THEO tip diam

assign/v8=PROBEDATA("DIAM") this gives actual tip diam

assign/v9=PROBEDATA("DATE") this gives date of last qual

assign/v10=PROBEDATA("TIME") this give time of last qual

assign/v11=PROBEDATA("STANDARDDEVIATION") this gives STDDEV



For any other (not current tip rotation in use) ex. T1A9045B0

assign/v2=PROBEDATA("TOFFSET","T1A9045B0") this gives THEO offset

assign/v3=PROBEDATA("OFFSET","T1A9045B0") this gives actual offset

assign/v4=PROBEDATA("VECTOR","T1A9045B0") this gives vector

assign/v5=PROBEDATA("A","T1A9045B0") this gives "A" angle of wrist

assign/v6=PROBEDATA("B","T1A9045B0") this gives "B" angle of wrist

assign/v7=PROBEDATA("TDIAM","T1A9045B0") this gives THEO tip diam

assign/v8=PROBEDATA("DIAM","T1A9045B0") this gives actual tip diam

assign/v9=PROBEDATA("DATE","T1A9045B0") this gives date of last qual

assign/v10=PROBEDATA("TIME","T1A9045B0") this give time of last qual

assign/v11=PROBEDATA("STANDARDDEVIATION","T1A9045B0") this gives STDDEV


Hope this helps you

Steve

Steve, that is exactly what I was looking for, and I can handle it from there. Thanks for your help!!

Your welcome.

Let us know how your code comes out.

PROBEDATA can get you mmuch info.

yada yada yada

Hope this helps you

Steve

It would if I could get V3.2 to even accept it into the code.

Is there a specific insertion point?

QUIET Ironhoe, let the man think.

It would if I could get V3.2 to even accept it into the code.

Is there a specific insertion point?

QUIET Ironhoe, let the man think.

Tab A.
Slot A, B or C depending on what she'll allow.
Perhaps all three.