Hey Stirling,
I have a probing issue like yours, (here is my post on the yahoo group), did you find a work around??
When the probing cycle starts, i.e. G31 -Z1 F2, when it hits the
probe plate (I am using Zarzuls most excellent probe/tool setter), I
get the Digitize signal on the diagnostics page, lighting up, so I
know I am seeing the setter signal comin into mach.
The problem is, that once the tool hits the setter and the signal
goes hot, the Z axis CONTINUES down, I have to hit the Estop, or it
will crush my setter........... I was under the impression that once
the Digitize signal went hot that the G31 function would stop the
downward probing before reaching final destination of (in this case),
Z-1.
I am brining in the signal through the modbus, through the Brains,
(I noted the only input signal you can use in brains is Digitize,
there is no "Probe" input signal. BUT!!, in ports and pins input
signal there is only a "Probe" Signal Input, and there is no Digitize
input signal. I suspect that Probe and Digitize is the same signal
but called different things depending on if your using Brains, or PP
inputs. The VB "IsActive(DIGITIZE) will show the input as well in
the scripter window.
Also, the code I am writing when the tool hits and makes the signal,
it was suppossed to use the value of "getVar(2002), and set that in
the Tool library for tool hieghth offset. But when checking the value
of var2002, there is no value stored in it after the hit. thus the
table H offset will not update.
*Ron I tried your code, but the Z still continued to move down, after
the hit.*
Any clues? (I noticed Stirling from the support group has noted this
exact same problem as well).
scott