Hello, I’ve asked this elsewhere but it seemed like an important enough topic to address separate.
For context I’m using Easel for design so if your program does this on it’s own, you likely don’t care.
Talking about optimizing the toolpaths/g-code for efficiency and controlling the order in which objects are cut in case of having a lot of small cuts on a larger piece you want to throughcut. We all know you don’t want the machine cutting through and placing the tabs first, before then moving all around on a potentially destabilized inner portion.
Also, I conducted a ~6 hour cut yesterday of a map diagram for a kid’s school project. I watched a large portion of the cut and was awestruck by how inefficient the path was. It would move roughly 36" across the sheet, lower z axis, cut a tiny indent and then raise, move up ~24" and cut another little thing, no rhyme or reason.
In the same “object” even (like an eight letter word for example) six of the letters were cut to full depth before two of the inner letters were even starting to form. There were some shallow passes on the two non-fully cut letters, but the machine went and did a ton of other stuff before returning and finishing those letters. Just a head scratcher and resulted in probably 100 unneeded slow full z-axis lifts and plunges.
What say we, Maslow community?