Getting my machine up and running, it handles long straight lines without a problem, but when doing a non-circular curve composed of many small G1 line segments (each ~1.5 mm in length), it stops (or nearly stops) for every single point.
Is there a setting or configuration I’m missing?
Here’s a video of it:
I’ve attached the g-code (created by our in-house CAD/CAM, that I wrote the post processor for) - it’s the top surface of a foot orthotic.
Thanks for any insight - we’re in a bit of a bind here, needing to get this machine working ASAP.
As a first quick test I would strip the comments from every line that contains motion commands. try to use comments before sections of moves but not in a line with motion commands. it is not a very powerful processor and parsing all this extra text could be an issue. I’ve run 13+ hour v-carve jobs that had hundreds of thousand of short line segments without having this behavior and I’m running a 2019 3XXL.
Another area to check if it happens in the future is if your computer is updating Windows for the 100th time that week. Every time I get odd or jerky behavior, Windows is hogging resources with it’s umpteenth security update.
