Hello @Letho.
Thanks for your effort, I was going the same way:
and got to your post the hard way.
Your solution is better than mine as it evaluates the effect of speed on detail, but I will propose 2 improvements:
-
closed boundaries in each “even” line/column intersection (like my ellipse approach)
(this way it is possible to understand the “full cut” limit, which is useful many times) -
units on the speed
This is relevant on another discussion where units are being confused: mm/s or mm/min
Luban version 3.12.3 displays 3000 mm/min
Can you share your saved Gcode?
(want to try before changing process again for all items, one by one…)