Working on some runtime info..

[cnckeith]

our g code backplot actually runs the job with accel/decel taken into account (and including smoothing if you are using G64!) it does the actual motion planning for the g code graph, not just drawing some lines. thats why CNC12's drilling job time estimates are so accurate compared to a cad/cam system's stab at it. if you set the range (F3 Set Range) in the g code backplot you will notice the run time estimate has also changed. Tip: leave the END value blank and it defaults to the end of the program using your start line number to start at and finish the rest of the job.

Awesome! Is there any way to get that estimate from the API?

yeah! thru our output pipe coming out in v5.40.0 public beta test period will begin soon.

[Onawa220]

our g code backplot actually runs the job with accel/decel taken into account (and including smoothing if you are using G64!) it does the actual motion planning for the g code graph, not just drawing some lines. thats why CNC12's drilling job time estimates are so accurate compared to a cad/cam system's stab at it. if you set the range (F3 Set Range) in the g code backplot you will notice the run time estimate has also changed. Tip: leave the END value blank and it defaults to the end of the program using your start line number to start at and finish the rest of the job.

Awesome! Is there any way to get that estimate from the API?

yeah! thru our output pipe coming out in v5.40.0 public beta test period will begin soon.

cnckeith I swear I've seen more info on your graph screen in videos when you are demonstrating something while your machine is running than we have on ours. Is there a walkthrough somewhere on how we can add more info on while it's running?