Best practice for an RDS XXT Probe Qualification Program.

[[Ri...]]

Qualification programs are easy when you use a List in leu of an RDSCAA.

I can report many types of data to ensure the List qualifications are good.

My current program tends to show something is wrong with an RDSCAA probe as the Characteristic is RED and the sigma is GREEN (I set the max sigma value).

What can I do for a RDSCAA qualification where the software uses 12 pre-programed articulations. How do I define parameters to identify what may or may not be wrong after an RDSCAA qualification?

 

We are wanting to move away from having an operator run qualifications to use some type of automation.

Edited October 1

[[Ri...]]

This is typically all I see when I run a qualification on a single RDSCAA probe.

It says: OK

Ok what?

and if its ok, why would a Probe Qual characteristic show RED?

[[To...]]

deleted post

Edited October 1

[[Ka...]]

Please sign in to view this quote.

Hi Richard,

We use the "result element" to query the sigma value of a stylus just after automatic calibration. Insert a simple PCM command getProbe("StylusName","PlateName").characteristic and set your own tolerance. At 7.4.24 are 16 properties defined. Take a look to your PCM documentation which can be find here:
C:\Program Files (x86)\ZEISS\CALYPSO 7.4\userinfo\manuals\en-US\Calypso_02_pcm.pdf

Based on our experience with RDS CAA, we set the permitted sigma value to 0.004.
In general, it should also be possible to touch the reference sphere after (automatic) calibration.
Here, we output the position of the reference sphere with different CAA probe positions. Theoretically, the position deviation should be 0. This is a very good way of verifying the actual swivel offset with CAA.
Until now, we have been doing this manually as required. First, determine the position with the reference probe and then check it with a CAA probe. We have not yet managed to get it to work in automatic mode... Even though ZEISS Service claims that this is possible. 😞

Best regards
Karsten

[[Ri...]]

My initial program looks like your setup.

My issue, the Probe Qualification icon will be RED and the sigma value will be GREEN (I use 0.003 for Sigma and expect to see roughly, half that).

And then, when I run the qualification manually, it says "OK" across all 12 articulations.

So, how do I know what is wrong when the automatic qualification is RED?

 

What I would like to report.

1. After a qualification (example, 1 of 12) report the True Position relative to the MasterProbe. Same thing I do for all of our VAST XT(R) sensors.

2. Report the coordinates of X, Y and Z.

3. Retrieve data from 1 and 2 above without having to rerun on the Reference Sphere. The built in qualification routine already collected data from the reference sphere.

(Why isn't this available for all 12 articulations?)

I see using getProbe().probeVector will show a string of vectors. However, this will require a PCM license to dissect that string to report values, yet I do not see enough values to project for 12 articulations. And then, it appears that the above PCM only retrieves the active probe vectors (Probe name and or articulation assumed?), saying this because I do not see how to pass a specific probe name or articulation to that parameter.

If getProbe().probeVector is for the active probe, what happens when the system goes on to the next probe, do the last values get replaced making continuous reporting impossible? I ask this because after a "complete" qualification the stylus returns to A0B0, and I assume that is when getProbe().probeVector will report vectors, at end of its built-in routine.

Moving forward:

My plan is to use the existing program I have and add Sphere features for each of the 12 articulations used in the Qualification routine. Report TP, X, Y  and Z coords.

Report a spherical TP for each articulation and sigma to see what may or may not have caused a RED condition on the report.

On our XT(R) sensors I do the same using a TP of .0003 (inch) spherical for a volumetric testing CMM program.