garymcrobertpdx wrote:Thanks for the info
I looked the examples over this appears not to be a simple matter and I have yet to figure out
how this method works.
It's relatively straightforward, I think.
This line in the INI:
REMAP=M6 modalgroup=6 prolog=change_prolog ngc=rack_change epilog=change_epilog
Means that any "M6" command in the G-code calls the G-code subroutine called "rack_change.ngc"
That G-code uses that fact that in the 2.6 version there are predefined parameters called things like #<_tool_selected> which tell the G-code which tool is needed.
(There are lots of these, the most useful being things like #<_x> which returns the current X-position. )
It also calls the routines called "change_prolog" before the tool change, and "change_epilog" after the tool change. The first checks that the tool number is valid and raises an error if not, the second actually tells LinuxCNC that the tool change has happened. These routines already exist, so you only need to copy the rack_change.ngc code (and modify it to suit your system)
There are a few other settings in the example INI file, to load a GladeVCP control panel for example. However, I think all the hard work has been done. You could try installing 2.6 from the buildbot and having a play around with that simulated tool changer configuration (it's a sim config, so won't actually move hardware)