Lacking a G68 coordinate system rotation I would use a mirror image command.
On Tue, Sep 7, 2021 at 1:36 AM Andy Pugh wrote:
>
>
> > On 6 Sep 2021, at 22:55, Viesturs Lācis
> wrote:
> >
> > Is there a way to reverse the direction? I tried playing with Z and R
> > values, but got only error mes
> On 6 Sep 2021, at 22:55, Viesturs Lācis wrote:
>
> Is there a way to reverse the direction? I tried playing with Z and R
> values, but got only error message that R has to be larger than Z.
It might be worth looking in the code for the error message to see if there is
any condition around i
Oh, thank you for pointing that out, I definitely had missed that! I
have absolutely no experience with canned cycles so far, always
managed simply with G1, G2 and G3
Is there a way to reverse the direction? I tried playing with Z and R
values, but got only error message that R has to be larger tha
On Monday 06 September 2021 15:38:12 Chris Radek wrote:
> Canned cycles work in all six planes, XY YZ ZX UV VW WU
>
> http://linuxcnc.org/docs/2.8/html/gcode/g-code.html#gcode:g80-g89
And I can verify that rigid tapping works with the head laid level and
using X instead of Z, in fact it works be
Canned cycles work in all six planes, XY YZ ZX UV VW WU
http://linuxcnc.org/docs/2.8/html/gcode/g-code.html#gcode:g80-g89
On Mon, Sep 06, 2021 at 07:44:42AM +0100, Andy Pugh wrote:
>
> I think that both can work, actually. Probably worth experimenting in a sim.
___
Before writing to mail list, I had posted this same question in forum.
According to Dewey Garrett, there was some bug about expanding the
subroutines and a fix has been committed to 2.8 branch for the next
release. I managed to get it to work without expanding it, so all is
good now.
Viesturs
pir
> On 5 Sep 2021, at 14:32, Viesturs Lācis wrote:
>
> I do not
> know, if canned cycles, like G81 work in XZ and YZ plane, but I feel
> pretty sure that they would not work both directions
I think that both can work, actually. Probably worth experimenting in a sim.
___
I'm not good enough with python to be sure, but it might have something to
do with how the loops and conditionals are named in the original subroutine.
I would try changing o and o to o100 and o1100, respectively.
Maybe pyngcgui.py is getting confused by the named o-labels.
On Sun, Sep 5, 2021 at
