Probe Program

[[Lo...]]

Hello everyone,

I have a few days to "play" on the CMM boss is gone. I been wanting to write a probe program. I have one that was written for me but want to learn for myself. For the most have one running smoothly. Other than the Master probe is red and when I do a Results Element is comes up red and the numbers are 9999.9999 on a 8MM probe. Obliviously when qualifying with this program the I don't get error. But my other probes qualify fine without errors. What am I missing from this? Thanks for any info.

 

Lou

[[Cl...]]

 

Are you speaking about the sigma value result element? Make sure syntax is correct and matches the stylus system and stylus exactly. 

getProbe("Down","0.7mm").stdProbeDev/25.4

Edited May 19, 2025

[[Lo...]]

Please sign in to view this quote.

Even before the results element. When I qualified the master probe, it fails qualification being red, I guess. But my other probe come out green, passing qualification. But the master probe will pass when I qualify it out of the program.

[[Ma...]]

What values are you trying to report? Just the Sigma value or something more?

Have you tried locating the RS out of the program then running the program in "Current alignment" after.

[[Lo...]]

Please sign in to view this quote.

Yes just a Sigma value, have been running current alignment. Not sure what I did but seems to be working fine, other than the probe is now traveling in the Z+ till it stops at the top after a run. Not sure why it is doing that. 

 

[[Ch...]]

Just a note if you are using PCM to get values of a probe that is not the current one, I have issues where it doesn't read it until the probe is loaded or re-calibrated.

As a related topic : try to find the sigma/qual limit of a probe that is not the current one loaded.... then you'll see what I mean.

[[Je...]]

Please sign in to view this quote.

I take the x-, y- and z-values and the radius of all probes in the inspection_start_pcm.txt of my qualifying-program to compare before and after qualifying without any issues

for example:

D2T_01radius=getProbe("01_-Z","D2T").radius
D2T_01vec=getProbe("01_-Z","D2T").probeVector
D2T_01x=val(strElement(1,"@",text(D2T_01vec)))
D2T_01y=val(strElement(2,"@",text(D2T_01vec)))
D2T_01z=val(strElement(3,"@",text(D2T_01vec)))

that works fine

 

[[Lo...]]

Sounds good thanks for the information, I will look into all this soon. But I am still having an issue with the program going to end position in the Z+ axis after the last probe is qualified and I can't figure that one out. 

[[De...]]

Please sign in to view this quote.

I'm not sure if this is related, but are you navigating using clearance planes  or use position points only? I was always told to use position points only for probe qualification programs.

[[Lo...]]

Please sign in to view this quote.

I was using clearance planes and position points only fixed that. I have a program written by someone else and they used clearance planes just not sure what they did differently and haven't heard back from them. 

Thanks!

[[An...]]

Typically if you are getting a bunch of 99999s in a formula/result element just means the syntax is wrong or reading in a non-existing value.

Here is a link to our result element variables for styli. I would double check your syntax. Sometimes the wrong caps or a missed period could be causing the issue. 

https://portal.zeiss.com/knowledge-base?id=522752