On Tue, Feb 12, 2019 at 09:38:10PM -0500, Ken Strauss wrote:
> G43 appears to only apply the Z-offset from the tool table. For example,
> running the program below displays the Z values as expected but the X values
> are identical. Would having LinuxCNC also apply the X offset cause problems?
>
>
Running PathPilot in lathe mode applies offsets for X, Y and Z.
> -Original Message-
> From: andy pugh [mailto:bodge...@gmail.com]
> Sent: Wednesday, February 13, 2019 9:08 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] G43 question
>
> On Wed,
On Wed, 13 Feb 2019 at 13:18, Ken Strauss wrote:
>
> Yes, Tool 1 has a new entry for X after running the posted gcode (unset
> offsets are not present). Note that this was tested using Tormach's PathPilot
You would _definitely_ expect X offsets to work on a lathe. Especially
as the Tormach lathe
From: andy pugh [mailto:bodge...@gmail.com]
> Sent: Wednesday, February 13, 2019 7:41 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] G43 question
>
> On Wed, 13 Feb 2019 at 02:40, Ken Strauss wrote:
> >
> > G43 appears to only apply the Z-offset fro
On Wed, 13 Feb 2019 at 02:40, Ken Strauss wrote:
>
> G43 appears to only apply the Z-offset from the tool table.
That seems wrong, G43 should definitely also apply the XYABCUVW offsets too.
Do you see the new numbers for X appear in the actual tool table?
--
atp
"A motorcycle is a bicycle
On 02/12/2019 08:38 PM, Ken Strauss wrote:
G43 appears to only apply the Z-offset from the tool table. For example,
running the program below displays the Z values as expected but the X values
are identical. Would having LinuxCNC also apply the X offset cause problems?
Assuming we are talking
G43 appears to only apply the Z-offset from the tool table. For example,
running the program below displays the Z values as expected but the X values
are identical. Would having LinuxCNC also apply the X offset cause problems?
g10 L1 P1 Z0 X0 R.25
t1 m6
g43 h1
(debug,#<_X> x with X offset=0)
