smartprobe - configuration questions

N24 (LOGEOPEN/home/operator/gcode/PROBE DATA/proberesults1.txt)
was added to my file and ended with the (LOGCLOSE) at the end of the file. No data entered into PROBE DATA/proberesults.txt.
I don't understand what your comment "magic comment" refers to. Is it sarcasum? What wold be the syntax be for your (LOG,...) "magic comment"

Thank you. I have poked around the the G code and I begin to understand the structure. The LOG would not write to my chosen directory of PROBE DATA but when I changed the destination to logdata,viola. Now I believe I'll have to try to change smartprobe. I think to probe a shaft radius, I would need to probe from the Y direction and step Z up from a start position. Probing down causes all kinds of unknown deflection as the tip moves into the radius. I think i would also need to change the Z 0 to half the dia. of the tip. to get an approximate location. Then there is the matter of the diameter of the tip as it hits Y. Would doubling the dia in the tool table have the effect of measuring actual Y or would making it Zero be better?

With you help I can use this program as it was intended and I just tried using an edge finder to find the radius of a shaft with just three points. I used a known shaft and found the edge finder got it right-on. I did get to learn more about the linuxcnc program from which Pathplot is based. So I think this is a win win.

Thanks again for the pointers.
Tom

I don't understand where probing up will make contact. I have tried manually probing Y at different heights using the probe Y function in pathpilot which does touch a second time very slowly. Compaired to the three points with my edge finder, the results were very dissapointing (the plot of the 6 points I struck was near .02 off in radius. I have no idea at what point on the ruby tip the actual contact is being made.