Don’t own an Elite Series yet, doing my research. Can anyone link me to a video or written source that shows the process on the Masso controller for a multiple tool path multiple tool change and what that might look like on the screen. I’m familiar with creating gCode files in Carbide Create and running a Shapeoko with Carbide Motion. I know what the on-screen commands look like in Motion, like to know what its like on the Masso for the Elite machine.
Let me try rephrasing my question. Can anyone here with an Elite series machine tell me if the Masso shuts down the machine and prompts (pop up message or otherwise) to change tools on multi tool cut file?
Yes it does that exactly, and moves the spindle to your pre set location for tool changes and if you populate the tool table it will tell you what tool by description to load, then hit cycle start, you do need ( I Think) the tool setter to fully use this option.
Pat
I just got my elite machine up and running and I am trying to process a file with multiple tool paths.
I have a tool setter installed and configured, and I am using Fusion360. I have the latest versions of the Masso, and Onefinity, Post Configuration files loaded, and I have tried both.
The gcode shows the three tools in the top comment section, and there are three separate tool paths. But there is nothing to actually change the tool.
I am struggling to understand if this is a Fusion post processing issue, a Onefinity/Masso configuration file issue, or the physical Masso Configuration.
Can you share your solution, or the steps you used? Or even what the gcode commands are that get emitted by the PP to go through the tool change sequence?
My newly-installed Elite stops and spins down the router after the first tool’s paths are finished, but only for a couple seconds before spinning right back up again and starting the next tool’s path. It doesn’t travel to the tool change location, or give me any prompts.
In the gcode there’s a comment indicating there should be a tool change there, but otherwise nothing special that would seem to tell the machine to wait for a tool change.
The video series linked higher up on the thread explains how to set the tool change location and how to set up the z-probe (both of which I’ve done) but not how to create a gcode file that will actually stop for tool changes
So, according to the Masso gcode reference, there should be a T command, an M06 command, and possibly a MSG command prompting for the tool change. The head of each of my path sections looks like this, with a parenthetical comment about changing tool, but no TXX, M06, or MSG command:
@TMToronto as it turns out, the link you sent leads to the exact same revision of the postprocessor code I’m using. My copy has a Onefinity-branded header at the top and the one you linked has a Masso-branded header at the top, but that’s just the comments. The code is bytewise identical.
So I still haven’t gotten it to work via the postprocessor. It still just emits a spindle off command followed by a comment like “(Manual tool change to T3)”, which, being a comment, of course doesn’t do anything.
I’m working around it for now by manually inserting a Tx M6 command at every tool change location in the gcode. This does the job, but it’s tedious and annoying to edit the gcode by hand for every project.
Also, I can’t test your multiple tool change gcode file as a whole, as I do not have the paid Fusion version, but if you send me your Fusion CAD file, I could run the toolpath - each separately - with my PP and see what gcode is produced.