what is the right command(sequence) for adding new tool?

Hi,

I was able to do a quick test. Good news: it works.

Then I tested the "reload" of a complete different file. This worked too, but had the side effect, that the original tool table was overwritten with the content of the other file. That was unwanted.

So bug or feature?

I'd like the idea of loading different tool-table sets. But I'd like to preserve each file - same as with gcode files. So what about adding path of tool-table-file to Tool-stats and change persistence handling with a given new filename?

You could have four tool tables, say tools.0, tools.1, tools.2 and tools.1

tools.0 would be empty and it would be the one you specified in your .ini file

tools.1, tools.2 & tools.3 would be your real tool table sets

Create (or add to an existing) a GladeVCP panel with three buttons to load the tool tables

In the python handler file for each button have something like:

This would load the contents of tools.1 into the current tool table (tools.0) as the startup tool table

You wouldn't be able to edit tools.1, tools.2 or tools.3 from the GUI as it would only edit the current contents of tools.0

Hi Phil,

I kept thinking about tool management too and I finally came to the conclusion, that my conception of tool management is not appropriate for a cnc machine/controller.
So I probabely will create a standalone tooleditor with hierarchical tool definitions and lots of properties, so that you can share your tool definitions between cam and cnc-machine.
Then I will enable the tooleditor to generate a tool table file for linuxcnc (and another for a cam) and then a reload-button in the UI (together with single file handling) will suffice.

Thanks anyway

Reinhard wrote: I kept thinking about tool management too and I finally came to the conclusion, that my conception of tool management is not appropriate for a cnc machine/controller.

It probably is. But LinuxCNC itself is far too simplistic in its tool handling.

Some time ago I came up with this, and even got some way in to making LinuxCNC work that way:
wiki.linuxcnc.org/cgi-bin/wiki.pl?ToolDatabase

Hi Andy,

It probably is.

Well, you're right

As I don't know much about lathe, I asked a friend, who recently became teamleader of multi-axis machines, to show me toolmanagement at a multi-axis machine.
Surprise!
He just established the tool-management I had in mind
He shares my opinion, that uses should not have to bother with slots or slot types.

The multiaxis machine has a carussel with static mounted tools and one or more milling spindle(s) with connection to atc.
The machine offers a separate tool-management editor for each spindle/carussel.

And my friend established the "standard", that the machine knows every tool, that is mounted in an adapter/tool holder - no matter wether the tool is inside the machine or outside.
This way the "operator" just cares about tool number - and the machine knows all values related to the tool number. Each tool keeps its tool-number, even outside of the machine.
The places for the toolholders are numbered according the tool numbers.

Yeah - I love it

And the tool is identifyable by comment and picture
Very nice.

So I try to go for it ...

Ah - by the way:
Even in the multiaxis machine, each tool is identified by the known parameters from basic machines, which means: length, radius and head radius for turning tools and X-, Z- and Orientation for static lathe tools.
No tool has parameters for UVWABC axis.
May be, linuxcnc did too much on that area.

I fully agree with you here Reinhard.
I come from using commersial systems at work, and a tool list with all necesary data that is easily shared with the CAM is a must.

So as Fusion 360 is used by a large portion of us as it is available at no cost it should be supported.
Also, Autodesk are open on their formats.

The question is if this is much work to be implemented. And also, who can do it. I can say I don't have the skills to do that.

Then there is the freecam world, which is another good initiative. I haven't looked to deeply in to that yet, but I assume they also have some form of tool management system?

Either way any CAM software needs more data than what you describe here. Geometry of the tool and holder is probably the most importent part. This is needed for colision testing, and is as such essential. This is already freely available in Fusion 360, so there is no reasons not to use it. And I strongly recommend using it!
The question is whether this is part of the library that LinuxCNC is seeing or not.