Maybe I'm overlooking something but is there any reason one master probe build cannot be used on multiple machines just simply to save on the number of modules needed on my machines?
I have shared regular probe builds between them with no issues, I just keep probe files local on the PC for each install so they can be calibrated on each machine and for each machine. Until recently there has never been a master probe in this building but my better machine has one in the rack now and I'm thinking it could just be used on both and the third machine when it is purchased... ?
EDIT: Holy debate... anyway yes I physically build a master probe, give it a probe file 'MASTER' and use it for nothing other than to set the sphere location when it is moved. Mine is a 4mm x 10mm and it always gives me a result of less than .0000 std dev when locating the ball.
It can do this because it never gets bumped/crashed... never any wear on the ruby from parts... the geometry of my master probe is pretty much guaranteed to never change and because of this my probes will relate to each other better. That is really the advantage to having an actual master probe... I think everybody understands that any probe previously calibrated at A0B0 can be used to set the sphere location... it is what others have done to that probe in the meantime that you have no idea. If that probe got bent a bit in use then you go set a sphere location with it you have error now in how that probe relates to others.
I'm going to stick to having a physical master probe... those of you saying use any odd probe to say yes the ball has moved... you risk introducing levels of error into your probe calibrations... yes the software can do it but it is not ideal.
Maybe it changes the game for me that there is no possible way to leave the ball on the table, it must be located for each probe calibration I do then removed... there is just no room for the part and sphere to be on the table at the same time.
I have shared regular probe builds between them with no issues, I just keep probe files local on the PC for each install so they can be calibrated on each machine and for each machine. Until recently there has never been a master probe in this building but my better machine has one in the rack now and I'm thinking it could just be used on both and the third machine when it is purchased... ?
EDIT: Holy debate... anyway yes I physically build a master probe, give it a probe file 'MASTER' and use it for nothing other than to set the sphere location when it is moved. Mine is a 4mm x 10mm and it always gives me a result of less than .0000 std dev when locating the ball.
It can do this because it never gets bumped/crashed... never any wear on the ruby from parts... the geometry of my master probe is pretty much guaranteed to never change and because of this my probes will relate to each other better. That is really the advantage to having an actual master probe... I think everybody understands that any probe previously calibrated at A0B0 can be used to set the sphere location... it is what others have done to that probe in the meantime that you have no idea. If that probe got bent a bit in use then you go set a sphere location with it you have error now in how that probe relates to others.
I'm going to stick to having a physical master probe... those of you saying use any odd probe to say yes the ball has moved... you risk introducing levels of error into your probe calibrations... yes the software can do it but it is not ideal.
Maybe it changes the game for me that there is no possible way to leave the ball on the table, it must be located for each probe calibration I do then removed... there is just no room for the part and sphere to be on the table at the same time.
Comment