> -----Original Message----- > From: Gene Heskett [mailto:ghesk...@shentel.net] > Sent: Tuesday, April 07, 2020 3:08 PM > To: emc-developers@lists.sourceforge.net > Subject: Re: [Emc-developers] Toolchange and tlo behaviour Assuming that you use > > premeasured tools (I have about 50 ready to go) > > Whereas I'd have to buy 40 more per machine,times 4 machines. Can I open > up a gofundme? :) > > > requiring multiple > > tool tables will create far more problems than it solves. For just two > > new problems: 1) Assume that I break, replace and remeasure tool #1. > > How do I ensure that the newly measured length is updated in all tool > > tables? > > 2) Assume that I have two tool tables and one contains tools #1, #2, > > #3 and another contains tools #1, #4, #5. How do I conveniently > > combine these into a table with tools #1, #2, #5? > > > To solve that, have a master list and a script that reads each entry from > the master list. That way you'd remeasure only that entry in the master > list and all that called for that tool would be updated as the list > would be reloaded everytime that bit of gcode was reloaded. > Atm I don't have an atc on anything, but several designs are kicking > about in my wet ram for the 6040 mill. One that uses the xy motors to > turn the er nut looks doable, but might need bigger motors to adequately > tighten the nut. > > Cheers, Gene. I can't afford to have 4 machines so 50 holders is sufficient for my single machine hobby usage.
Perhaps I'm just missing the point but... If you need a "master list" containing all tools plus a script (no UI?) to move a selection of tools to a sublist, what is the advantage? Providing a single, large, tool table gives the same capability without the complications of sub-tool tables and special scripts and additional processing for each gcode file. _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
