Hi all
Yep, g31 again. I am trying to use a Z axis touch probe to level up some machining jigs.
Dedicated WXP, R3.043.022, ESS
The touch probe has a resolution of about 10 microns. It gets sensed quite happily by the ESS diagnostics and the Mach diagnostics. In fact, I can run the following program quite happily and create a data file as expected.
m1 (Go when ready)
f10
m40 % open log file
g0 z0
m98 p10 L5 % probe 5 times
m41 % close log file
g0 z20
m30
%------------
o10
g4 p0.2 % redundant delay
g31 z-2 % probe downwards
g4 p0.2
g0 z0
m99
The program runs, the touch probe creeps down and touches/stops at about -1.2 mm, the Z axis retreats to 0, and the whole thing repeats. A log file is created. So far, so good.
The PROBLEM: the data recorded is the position at Z=0 in machine coordinates! All 5 entries too.
Well, most of the time. A few times the file has contained actual program coordinates for the trigger point.
I have checked #2000-2 and they usually do contain the machine coords as listed in the data file.
Has anyone met this one???
This is all with Probe on 2/15, Active Low, which fits with the diagnostic screens. Interestingly, if I flip the active state to Hi, the subroutine does not even execute. It would seem that m40 or opendigfile() may do a sanity check on the state of the probe input, and abort if it is asserted.
Cheers
Roger