it could be that the g-code will come back and finish these sections
That was my thought as well… which is why I let it run 5 hours, but I can clearly tell that each ‘section’ fits in the previous one, like a puzzle piece, plus the overall location of the sled (as seen in GC) wasn’t jiving with where it was on the workpiece. So then I ran the gcode through several different simulators to verify.
It starts at upper right and and moves back and forth line by line toward the lower left.
Last night late, I started making a few modifications to the chain slack tension setup to try to keep things a bit more in line, but I may just end up, this evening, cutting out one of the chain guides that has already been shared herein, to eliminate that as a possibility.
To get around the issues with the large file in Ground Control I’m currently running from source with 64-bit Python 2.7.14. Still slow, but no crashes unless I redefine home. I also tried packaging with Pyinstaller but it seems that the .exe. that it delivers is really more about packaging up the python binaries and not really compiling the script. i.e. the script is still being interpreted at runtime and thus has no performance improvements over running from source (at least that I can see). If you know differently then please share.
I started messing around with Cython which does compile the python script. I got a build compiled. The exe starts like the portable one (loading SDL and such) but it does not recognize the ‘import’ modules… more to understand there.
Thanks for everyone’s input. Truly great contributors on this forum!!!
Attaching the gcode…Portrait.gcode (547.1 KB)