Hallo,
here my 2 cents:
First we should distinguish in two parts:
- What information does linuxcnc need to work (current level)
* tool number
* pocket number
* tool diameter
* tool length
- What information do the user want:
* I already mentioned some I would like to see
If we would use a database solution, the GUI maker like me, can easy
communicate with that base tool table, add information and get all
relevant stuff.
If someone have his CAM on Windows, I small Python Script can solve the
synchronization.
If you want a barcode reader (I use in the company on datamatrix code
for measuring instruments), a small script is the solution.
If you mention now, that all that can be done also with a text file, you
are right. But please take in mind, that modern machines do not handle
only 5 to 10 tools, the handle a hundert tools.
I support the idea of toolsets for workpieces. Actually I just use
different tool files for different parts. Handling all in one file /
database will make thinks easier.
IMHO the first step should be to eliminate the limit in the number of
tools and describe in detail, what information linuxcnc do need and how
to submit that information. I am pretty sure, that the first tool tables
will be presented after that.
Norbert
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
