Same probe different name.

[Tested]

I have a CMM program that is shared between my plant and our customer. To make things easy we created a probe name that we would both use. I have created the a probe using this name but is other wise the same probe that I use for 85% of all my CMM programs. But for some reason there is a differance in their std. the one with the shared name runs at about stdDev .0022 but, while my every day probe is lucky to be stdDev .0063. Does any konw why this might be.

[#2#]

Did you check to ensure that the parameters for the calibrations are the same? Prehit/retract, number of hits, etc.

[Tested]

Did you check to ensure that the parameters for the calibrations are the same? Prehit/retract, number of hits, etc.

Yes all of this is the same.

[Saliha]

1-) are you have the same type of the machine ? Depend on the machine type , calibration speed is different.
2-) are you using the same speed value ? Depend on the machine type , calibration speed is different.
3-) are you playing with the speed from the jogbox while calibrating the tips? Do not play with the speed , it may give different StdDev values.
4-) are you taking the first hit almost from the pole of the CalSphere? Mostly because of this , you can find big values of StdDev.
5-) if you are using TP20 or TP200 , check the magnetic surfaces of the probe and the module , both. (Any dirt or damage) .
6-) if you are using TP20 or TP200 , try to use another module. Maybe you need to replace the module with the new one.

and use the Qualification check option.

HTH
Saliha

[Tested]

1-) are you have the same type of the machine ? Depend on the machine type , calibration speed is different.
2-) are you using the same speed value ? Depend on the machine type , calibration speed is different.
3-) are you playing with the speed from the jogbox while calibrating the tips? Do not play with the speed , it may give different StdDev values.
4-) are you taking the first hit almost from the pole of the CalSphere? Mostly because of this , you can find big values of StdDev.
5-) if you are using TP20 or TP200 , check the magnetic surfaces of the probe and the module , both. (Any dirt or damage) .
6-) if you are using TP20 or TP200 , try to use another module. Maybe you need to replace the module with the new one.

and use the Qualification check option.

HTH
Saliha

Same machine probe never removed, speed never changed, same order of calibration, same number of hits, same order of hits.

[#2#]

I just want to make sure I am thinking about this correctly.

There are two CMM's - yours and your customer's.
There is one program you both use.
Their probe file is exactly the same as yours.
You calibrate your probe tipand get std dev of .0063.
They calibrate their probe tip(there are 2 different probe tips correct?) and get std dev of .0022.

If indeed there are two different probe tips, it could be theirs is rounder than yours. It could also just be minor differences in your probes. Perhaps their module is a little more sensitive than yours.

[Tested]

I am speaking of the calibrations I am doing here. I only mention them "the customer" so as to explane why I have the same probe with two names. I am calibrating both probes and I am finding this differance on one machine.

[#2#]

I am speaking of the calibrations I am doing here. I only mention them "the customer" so as to explane why I have the same probe with two names. I am calibrating both probes and I am finding this differance on one machine.

So are you calibrating two probes which are built the same with one probe file?

OR

Are you are calibrating one probe with two identical probe files?

OR

Are you calibrating two probes which are built the same with two identical probe files?

Sorry, I'm a bit confused (S.O.P.) and would like to get it straight before I start spewing possible causes/solutions which aren't related to the problem.

[Matthew D. Hoedeman]

Probe file #1 = PH9 + TP2 + 2x20
Probe file #2 = PH9 + TP2 + 2x20
(for example)
Getting different results without any change-over of any hardware.

Is that what you are saying?

[Tested]

Probe file #1 = PH9 + TP2 + 2x20
Probe file #2 = PH9 + TP2 + 2x20
(for example)
Getting different results without any change-over of any hardware.

Is that what you are saying?

Correct

sorry

[#2#]

Ok, so they should measure the same.

You say prehit/retract is set up the same. What about speed in the program?

Here is what I would do...

Create a program which uses both probe files. Simple program - load probe file #1. move point load probe file #2.

Put the cursor on probe file #1 and F9 to open probe file #1. Calibrate answering 'yes' to the sphere moving. Get all the way back to the program when it is done by clicking ok, etc. Re-open the probe file, re-calibrate answering 'no' to the sphere moving. Check the results. Get all the way back to the program when it is done.

Now, without moving the sphere, put the cursor on probe file #2 and hit F9 to open probe file #2 and calibrate answering 'no' to the sphere moving. Review those results.

Let us know what they are if they are different.

[Saliha]

1-) Please check the date of the result files from windows explorer window for the both file.

2-) Check the path for the probe files.

3-) Yesterday I have used Renishaw MH 20 manual head. At the end of calibration , I get strange values for X,Y,Z and StdDev. Usually I'm using "+" sign for the equipments like : MH20+2+20+10
Then I build up a new probe file like MH20_2_20_10 : reasonable results. Try to create a new probe file without any "special" characters.

HTH
Saliha