Jump to content

calibration disk stylus & getProbe()


Recommended Posts

  • 2 weeks later...
These should be enough to get you started...

getProbe([styli,system]) Access to probe.


getProbe()

Instance Variables;
.confName
.radius
.diameter
.probeName
.probeType
.probeDate
.probeIdent
.ident
.technology
.calibMode
.anglePosA1
.anglePosA2
.rotAngle
.rotationHead
.stdProbeDev
.sigma
.shaftLen
.shaftRadius
.stylusID
.refProbeLen
.probeConfiguration
.probeCorr
.probeName
.probeNameNumber
.probeRadius
.probeTemp
.probeType
.probeVector
.nx
.ny
.nz
.x
.y
.z
  • Like! 2
  • 7 months later...
Jeff, and all,

I'm on 2023 7.6.0402. I'd love to be able to get the calibration limit value for each stylus tip with PCM.

The .sigma instance variable doesn't seem to do anything for me, I've tried getProbe().sigma, getProbe("A1-3","A1").sigma getProbe("A1-3","A1").sigma.limit ; and have scoured the forums and 'other locations' 😉

Any idea why this is not available via PCM ? I mean any damage you could do with it via PCM would be easy enough to do in stylus system management window.

We have lots of styli all with different limits, I'd like to make a qualification program that uses PCM to get the limits in case they ever 'randomly' change, etc.

Thank you.
Clarke,

Correct. What I was after was the calibration LIMIT value.

I've been digging pretty deep, not coming up with much.

I've put a few requests in MyVoice. For example, if I want to see the calibration limit for a stylus while I'm on the CMM of a probe that is not on the active stylus system, I have to pick up that probe to be able to see the limit value.

I do not see any reason why they would not allow access to the calibration limit value with PCM.

If anyone knows of the file location where each probe limit values are stored that would be helpful also - I don't mean to de-rail the thread .. but I don't think they are in a file, rather perhaps a #Dictionary or some similar container.

Thanks.
  • 2 years later...

What if you make a program with only only Result Elements to retrieve the std deviations of all your probes or whatever you unmask? Without having the Probe Qualification parameters? Just an idea I might try myself. Compare it to Ctrl+F to look them up and report them.

×
×
  • Create New...