Gcode lines per second?

[MRob]

Realising this may be a difficult (or impossible) question to definitively answer, and likely depends on the complexity of each line, but is there any ballpark figure for the number of gcode lines / second that the duet3 can handle? I run a rotary axis carving machine, also building a lathe in the next few weeks, just wondering how much to future proof it in case RR gets G93 moves in the future! I probably reach 200-300 lines / sec at the moment, 4 axis (but mostly A and Z moving for these runs).

[dc42]

@mrob you can get an idea of the rate at which commands can be handled by simulating a long job and dividing the time taken to run the simulation by the number of GCode lines in the file. When you simulate a job it does all the GCode processing except for generating the steps; except that on machines whose kinematics use segmentation (e.g. SCARA) it omits the segmentation because that slows down the simulation and doesn't usually affect the result.

[MRob]

@dc42 Thanks, although I dont have a duet 3 to test with at the moment :). Best I have is an old maestro running 2.03 for my 3d printer. Perhaps I could update, and then create a high details file to get a feel for it, if there are no known benchmarks.

[oliof]

@mrob just to add, simulation is about 5 to 20 times faster than actual printing, so unless you go beyond 2000mm/sec or super microscopic moves per line you should be fine. Also consider that at some point the performance of the SD card may bottleneck you in case this isn't for a 3d printer.

[MRob]

@oliof Thanks, good to know! Yes, I'm looking to build a CNC lathe / 4th axis carving machine, possibly based on duet3, just trying to iron out uncertainties before making final a decision on which system to use as control.

[dc42]

@oliof said in Gcode lines per second?:

@mrob just to add, simulation is about 5 to 20 times faster than actual printing...

I find it about 60 times faster than actual printing. It depends on how fast you print.