RatonLaveur wrote: ↑
Fri Jul 31, 2020 8:52 pm
change your postprocessor to remove all Z arguments.
That would actually be remarkably ineffective, since his machine totally ignores z commands in any case.
The problem is a bit different than I first understood. There is no way in the Path WB to specifically direct the rapid motion between arrayed objects. It may be possible to create an actual cutting path to replace the rapids, but I suspect that would take a lot of work with custom g-code. One can create "start points", but I don't think there is any way to create an "end point." The process of building the custom rapid-replacement needs to know the end point of the profile operation. Every design, even with rather small changes, might be quite different.
It might also be possible to create some dummy structures to make sure the "between" path did not blindly plow through the desired objects already processed or yet to be processed. Again, the difficulty is that there is no user control of the rapid path. I do not know if the avoidance strategy would be robust and trusted.