On Thursday 24 May 2018 10:50:07 Kurt Jacobson wrote: > Gene, Rene is working on a new implementation of the tool table that > removes the 56 tool limit. > I don't know when it will be complete enough to merge to master, but I > hope it is relatively soon. > Thats good news.
> In the mean time, it would be fairly easy to write a little bit of > python code and add to your VCP so you could select from multiple > tool.tbl files. While I have been lurking on the python mailing list for several years, I have not learned enough to do that, and at my age, its doubtfull I will. But I keep hoping osmosis still works. :) How about just changing the $TOOL_TABLE in the env, and reloading from that name in the env? > > In the first (GTK2) version of hazzy I experimented with a combo box > to select which tool table to use. > Basically, I had LCNC load an active_tool.tbl file, and when the user > changed the selection in the combo box it would copy the selected tool > table over as active_tool.tbl and then tell LCNC to reload the tool > table. It worked, and as long as you make sure you do not repeat any > tool numbers it is safe, since even if you selected the wrong tool > table by accident LCNC would not find that tool in the table. That sounds like something I might be able to do. I seem to be getting a grasp of the xml to do that in my post.gui scripts. > > If you don't have a tool changer, having multiple tool tables allows > you to categorize your tools. I don't have a tool changer. started on one once but after making a 6 pocket wheel, intended to be on a swing mount, intending to load it on a job needed basis, I found a miss-calc had placed the pockets too close to each other, and recycled most of what I had cut into other things. Never started again. And with these things, the pocket count is very quickly exceeding the available room for a chain driven arrangement such as I've seen on a machining center. > For example you could have endmills.tbl, which could contain up to 56 > end mills starting at T1 and going thru T56. > You could also have drills.tbl, which would start at T57 and have up > to T112 etc. Good idea. Once I need more than a single table can handle, I'll do that. Thanks Kurt. > Each tool table does not have to span 56 tools, so you could have > countersinks.tbl, that goes from T113 to T123. I wonder if grep could somehow be used to make it search and load the correct table? And obviously a printout should be maintained so that the correct tool could be mix&matched in the code? Interesting concept. > They key is not to have any tool number repeat in different tables > (pocket numbers can repeat), that is what makes it safe to have > multiple tool tables. > > Now, if you have an ATC it becomes more difficult, because all the > tools you use in a given program must be in the same tool table. > In this case it would probably be best to have a separate tool table > per tool tray, or per part. > > Cheers, > Kurt > ---------------------------------------------------------------------- >-------- Check out the vibrant tech community on one of the world's > most engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
