I would like to create a push button system to change tools. I’m not sure how to go about doing this and I was wondering if anyone has attempted this. I envision 7 buttons, one for each tool I have. I would push the tool 1 button and the system would go and grab tool one. Pushing tool 2 button would grab tool two, etc. I’m already tired of entering G-code to do this.
I don’t think that’s possible. The physical button needs to be tied into an input for it to work. There are a few inputs that are not obvious what they mean and have a lack of documentation on it
Why are you entering in the tool change command so often? You might be able add a tool change at the end of your gcode in your post processor so it’s ended on the same one
I think, because I’m new to this ATC business, I have not worked through a work flow process yet. Maybe that’s why I’m entering G-Code for tool changes.
Yesterday I finally ran a production file using the ATC and it worked great. Only a minor annoyance with the order in which the cuts took place. On that topic, what determines the order of cuts? I assumed it was in what order I select them prior to saving the file but I suspect it was more based on the order of the toolpaths in Aspire.
The order the post processor puts them in. I know aspire the order the tool paths are in, is the order it executes.
The only real reason to use the mdi to change bits is if your like me and too lazy to adjust the bit diameter dimensions on your probe… well i used to use a probe for xy, now i don’t have to unless i want to
The “A” in ATC stands to “auto” or “automatic” - you don’t need any buttons to change to specific tools. Tool change commands specifying which tool to change to need to be included in your GCODE program.
A manual tool change button can make some sense, but that is going to require you to select the tool at the controller manually as well.
LOL, that’s what the A stands for!
I think I just need to figure out my workflow and start trusting the machine.
Put it this way. Even if you had unique buttons to call for a specific tool change (which is doable by the way), you can’t use them in the middle of a running program. If there are no tool change calls in your program then the machine is never going to stop, it’s just going to cut from start to end.
So the only time you’d be able to use these buttons is while your machine is idle and not in the middle of a cycle/program. At that point is there any use besides the tactile experience of touching buttons and then watching the robot jump to action? No, there isn’t.
The same commands that you’d need to attach to each button will go into the gcode program, put there by the CAM software and post processor as needed to make the desired cuts. You’ll define all your tools on the controller and give them all unique tool numbers. You’ll also include the same information in your CAD/CAM software.
If you wanted to “start off easy” without all the tool info, then you’d call for “manual tool change” and you’d have the controller set up to support that ahead of time. In this case when it comes time to change tools, the machine will move the spindle to pre-determined location and wait for you to manually change the tool and then press a button to continue the cycle. You should still have a tool setter in this case so the controller can check the tool offset of what you just loaded onto the spindle.
My current dilemma is when I have a carve that calls for my large 1/2" DC bit and a smaller TBN bit, I have dust boot issues. The 1/2" bit calls for a much longer dust boot than the TBN. I’m currently trying to find a one dust boot solution and I’ll work through that. So for those carves I have to change the bits and dust boot options manually, hence the need for the tool change buttons.
Ultimately I’d like to find a single dust boot solution that works with all of my bits. I’ve purchased some 3" long bristles that I’m testing out to help with this situation. The 1/'2 bit has a 2" long cut depth for thick stock.
So you need to have manual tool change set up in Masso and then call for a tool change in the gcode (specifying a specific and defined tool). The machine will move to your tool change location and stop. You then change out the dust boot and tool as needed, then continue. If you have already previously done tool measurements everything will be fine. Otherwise you’ll have to take an offset measurement of the new tool using the tool setter.
Or, you can save them as seperate gcode files
Or that. 
Which is how you can also work around not having a tool setter.
I do love the idea of having a variety of tool buttons… but I’m not sure it’d be useful for ATC-capable CNC Controllers.
The biggest power of an ATC is g-coding the tool changes so all you need to do is hit go and when you come back the carve is completely done.
A tool-buttons bank would be nice on this Shapeoko 5 Pro (used exclusively in MTC mode), but the controller doesn’t support several of the required tool-changing commands. Even if i could write a gcode that says go to xyz drop tool, then go to xyz and pickup new tool… the controller has no outputs capable of triggering the solenoid to release and pickup the tool.
If i were to swap out the controller to one capable of this… then it’s now an ATC capable controller and thus invalidates it.
Now… i can definitely see the benefit on my Onefinity w/Masso controller… of having onscreen buttons that say go get tool 3. ATM i have to go into mdi and trigger the T3M6 command manually. This would make them “shortcut” commands and i don’t remember if this is possible.