On Wed, 8 Apr 2020 at 03:04, Reinhard <reinha...@schwarzrot-design.de> wrote:
> So the solution to your problems is a tool-manager, that knows all tools and > which generates a tooltable for each job, which then gets transmitted to the > cnc-controller. Many years ago, and working with Tormach, we came up with a powerful database schema for a LinuxCNC tool catalogue. Amongst other things it supported a shared tool table for all machines in the factory (or, indeed, the World) with pre-configured carousel layouts and all sorts of other things. (and, being a database, users can add fields without breaking the built-in queries) http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ToolDatabase To make use of a database, though, the tool data has to be removed from motion / NML. All that needs (as far as I can tell, please tell me if I am wrong) is the data for the current tool. One of the larger tasks to make that database a reality is to hide it from the user, so nothing seems to have changed :-) At the time I created my tool database branch (which, incidentally, I have now totally re-thought) I had no Python experience, so was not in a position to teach tooledit how to handle the new backend complexity. Note that the andypugh/tooltable branch has seen no activity since 2013.... -- 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
