Hi Dezsoe,
What CL_MotoTech and Rob describe is what I did in my old Mach3 wizard.
Using a known ring-gauge, the bore was probed at 10 degree increments and a table of 'effective' ball tip diameters was created (ie, values that would produce a perfect measurement on the ring gauge). Later during probing, the probe routine would determine what vector direction machine was traveling in, grab or interpolate the effective ball radius for that direction from the table, then use it to determine 'hit location'. This did also require the probe to be consistently mounted, but the compensation accounted for all the errors at once (backlash, axis calibration error, probe tip deflection/spring load, etc).
A pic on the page Rob links shows the table, which would probably look more meaning full if the diameters were shown to 4 or 5 decimal places instead of 3.
I could dig up some of that VB code if it helped, but it's pretty basic.
PS. I Still wish UCCNC would support G31 with x/y axis combinations
I'd still like to try to replicate 'ProbeIt' for UCCNC. I've thought about making use of the 'jog safe probe' ability of UCCNC, then drive the spindle around with jog moves to do probing, but.... that seems iffy
regards,
Eric