On Tue, 7 Apr 2020 at 16:36, Reinhard <[email protected]> wrote:
> I believe, that its a big overshoot to put the tooltable in the nml-status- > area. Tooltable-properties are quite seldom requested by ui, so it would be > sufficient, if the table or parts of it would be served at request only. I agree. I think that there should only ever be one set of tool offsets in the motion module, and that it is perfectly OK to break blending and pop out to user space to get the new tool data on toolchange But, I disagree that LinuxCNC should _necessarily_ leave it all to the tool table. There is room to be flexible and allow more than one solution. As it stands LinuxCNC can be configured so that the tool changer only uses the tool number, as you describe. No changes are needed to make that work. But, very often, the tool change process is handled by HAL components and G-code remaps, and in that case it is useful for LinuxCNC to help out with remembering where each tool is, as neither HAL nor G-code are well suited to persistent data storage. I tend to agree that a major overhaul of tool handling is needed, but I think your proposal is too limiting. Of course, of you want to configure it your way, iocontrol is a pluggable module, and you already have a choice of iocontrol or iocontrolv2. [EMCIO] EMCIO = io or EMCIO = iov2 (And, perhaps, that should be documented?) -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
