Hi,

On Freitag, 10. April 2020, 04:26:04 CEST andy pugh wrote:
> On Tue, 7 Apr 2020 at 15:14, Rene Hopf via Emc-developers
> <[email protected]> wrote:
> > Retain G43
> > Almost anybody that has ever used any other controller,
> 
> I have created a branch where RETAIN_G43 defaults to on:
> andypugh/persistentG43
> 
> But I can't decide if it actually works. I don't see the Z offset for
> the new tool in the halui HAL pin, or on the offset display without a
> G43.
> If I add a G43 after each tool change then I do see it.

I don't consider it a good idea to try to avoid G43 like retaining it.
Not in DIN-like gcode systems like linuxcnc.

For me, the best and most elegant way is by far Heidenhain. On every 
toolchange the toollength is applied automatically. The user does not need to 
tell which varset to use, as the machine knows the tool number.
But for this behaviour becoming useful, its necessary to be able to change 
tool-variables at tool-definition time (T-command).
In Heidenhain you have the TD- and TL-words to change Diameter and/or Length. 
That way it is easy to achieve same tool with different tool-parameters without 
having to change tooltable or create fake-tool-entries. 
The latter is common in Siemens and Fanuc controllers, which work with G43 and 
the user has to tell the machine, which varset to use for the current tool.
That's poor intelligent controllers force the users to do stupid things :(
(Same is true for G40/G41/G42 - Heidenhain shows, how to do things right :D )

Anyway - all gcode-coders know that dumb behaviour and for so are used to code 
G43.

So for me, its a wrong behaviour, allow to retain G43 without the possibility 
to change toollength and tooldiameter in GCode. 
And even if you implement that toolvar offsets at tool definition.
Use G43 once is wrong. At least for me.
If you want to retain G43, make it an INI-option and never use it again in 
gcode files.

... but than you have to change G40/G41/G42 too.


cheers Reinhard




_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to