Post feed rate issue

There are other post issues to sort out also. I'll see if I can get a video for you. On a simple cut I've been able to use JetCAD but the other day with a bunch of artsy fire pit pieces on a sheet, I needed to go back to sheetcam. My table threw errors with the g-code output. I'll send you a video soon as I get a chance to shoot one.

Okay, I'll take a look at the cut chart issue here shortly. Yeah, please show me the errors qtPlasmaC surfaced with the artsy stuff. I'm betting it's probably complaining about small arcs where leads got reduced but maintained an arc. LinuxCNC and most of the streaming controllers use an arc endpoint check tolorance that is like 5%-10% and depending on your step scale the closest grid point (where the machine can physically be vs where the program actually puts something). The error collapses on small arc checks and can put them out of that tolerance range and it throws and error even though the arc IK (or R) words are calculated correctly. I used to see it a lot from Fusion posted Gcode running on Tormach PathPilot Controls. You could have continued on with JetCad3 by checking "Linearize Arcs" in the post settings if this was the problem. I'll look forward to seeing the errors for sure because I can guard against it in the post to a point but for machines with a resolution of around 0.001"/step (not actually that uncommon for old LPT-port driven machines) it's pretty much unavoidable with small arcs

I went to repro the error just 5 minutes ago here, and didn't get the same errors again. Only difference, I was doing a dry run with torch disabled. But I shot video and it shows how the same job takes about a minute to load when posted from JetCAD and probably less than 5 seconds when posted from sheetcam. I'll send this to you privately, along with the g-code files from sheetcam and JetCAD for the same job, same layout.

30 seconds vs 5 seconds to load a gcode program is pretty stark lol. Yeah, looking forward to seeing the difference between those two nc files. They should be comparatively close to the same size. I think the JetCad3 post is introducing more comments than the sheetcam post just to keep the Gcode easier to read and aid jump ins by line. qtPlasmaC uses comments for other features so it's probably parsing a bunch of extra comments and it's adding a whole bunch of needless time waste for essentially no-op.

G code file samples and video sent. File sizes are quite different for same part nest.

I'll go to bed and let you sort this out through the night, ha!