On 28 August 2016 at 00:54, wrote:
> So is there any way to signal from the .ngc back to the HAL?
Yes, that is what codes M62 to M68 do:
http://linuxcnc.org/docs/2.7/html/gcode/m-code.html#mcode:m62-m65
> Lemme see, is there a NEED for the .ngc to talk back? Can HAL logic alone
> launch the .
So is there any way to signal from the .ngc back to the HAL? I did resolve the
issue with G38.2 Z-target being work coords not machine, and got a nice
effective probing cycle going, just no deadmanning.
I am not "into" GUIs yet. I have whatever stock LinuxCNC panel it came with.
The Probe bu
On 25 August 2016 at 18:29, wrote:
> Can we have a combination of HAL and .ngc be set to this:
> Logic #1:
> if (button & !isProbing), then set isProbing=TRUE, execute myProbe.ngc, and
> set isProbing=FALSE when it returns
> and Logic #2:
> if(!button & isProbing), then issue a STOP (same as p
Where's the actual homing routine?
Was just thinking of this on a walk...
Can we have a combination of HAL and .ngc be set to this:
Logic #1:
if (button & !isProbing), then set isProbing=TRUE, execute myProbe.ngc, and
set isProbing=FALSE when it returns
and Logic #2:
if(!button & isProbing), th
On 25 August 2016 at 17:22, wrote:
> But, just to complicate things, I'd really like to have this deadman, so you
> must hold down the Probe-Z button or it will abort the process immediately
> and fail to set the Z-home.
You could consider driving motion.enable to false. Though that might
ove
Manual toolchanging here.
I have a wireless tool setter already wired in, and an XHC-HB04 wireless
pendant. I'd like to press the "Probe-Z" button and have it zero the work
coords on the touch.
But, just to complicate things, I'd really like to have this deadman, so you
must hold down the Pro
