My discussion was to bring to light how Lathe tools are normally used so that a 
database might keep them in mind when hashing out a protocol.

My 'complaint' about linuxcnc offsets for lathes was to point out it's 
suboptimal, not that it wasn't possible. Using g43.2 to add wear offsets works 
for sure.. but it a hack and doesn't allow proper standard support in screens.

I certainly don't suggest we eliminate g43.2 functionality though.

________________________________
From: andy pugh <bodge...@gmail.com>
Sent: June 29, 2022 10:13 PM
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] tool database in python

On Fri, 24 Jun 2022 at 02:46, Chris Morley <chrisinnana...@hotmail.com> wrote:
>
> Different edges of the same tool is done by having different offsets, not 
> tool number.

It certainly _can_ be done that way, but I see no reason to preclude
doing it a different way.

And (as delivered) LinuxCNC does not handle T11 to mean anything other
than Tool 11.

If you allow more than one tool in one pocket then you can use M6 T1
G43 / M6 T2 G43 to get the same tool, same pocket, different edge,
without having to remember where you kept the second-edge offset (or,
more practically, without having to tell the CAM software to use an
offset that does not match the too)


--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to