Den Söndag, Juni 26, 2022 18:18 CEST, skrev andy pugh :
On Sat, 25 Jun 2022 at 15:56, Nicklas SB Karlsson wrote:
>
> Expected movement to stop the "probe tripped during move" but this does
> not happen.
There is an issue on the tracker about this, though I don't know if
anyone is actively worki
On Sat, 25 Jun 2022 at 15:56, Nicklas SB Karlsson wrote:
>
> Expected movement to stop the "probe tripped during move" but this does
> not happen.
There is an issue on the tracker about this, though I don't know if
anyone is actively working on it:
https://github.com/LinuxCNC/linuxcnc/issues/368
On 6/25/22 14:21, Nicklas SB Karlsson wrote:
Den 2022-06-25 kl. 19:44, skrev ken.stra...@sympatico.ca:
I agree about stopping and I have the broken tips to prove it! IMHO
an even
better solution would be to:
* Allow jogging as usual if probe is not tripped
* If probe trips, reverse motion until
Den 2022-06-25 kl. 19:44, skrev ken.stra...@sympatico.ca:
I agree about stopping and I have the broken tips to prove it! IMHO an even
better solution would be to:
* Allow jogging as usual if probe is not tripped
* If probe trips, reverse motion until probe is untripped
Guess reverse direction m
tripped during move, machine does not
stop?
Expected movement to stop the "probe tripped during move" but this does not
happen. Risk to make a mistake bending the probe then jogging or using other
g-code commands to move it into place is to small so guess it would be a
good idea if machine
Expected movement to stop the "probe tripped during move" but this does
not happen. Risk to make a mistake bending the probe then jogging or
using other g-code commands to move it into place is to small so guess
it would be a good idea if machine stop then this happen?
Have also been thinking
