Hello Guest it is January 25, 2020, 12:57:10 AM

Author Topic: Machining time or run time  (Read 2432 times)

0 Members and 1 Guest are viewing this topic.

Machining time or run time
« on: June 06, 2011, 01:52:12 AM »
Is there a way to get an estimate of the runtime for a file once it is loaded into Mach3?

Offline BR549

*
  •  6,925 6,925
    • View Profile
Re: Machining time or run time
« Reply #1 on: June 06, 2011, 02:43:51 AM »
SURE is go to the toolpath page and press simulate program run. That should give you the estimated run time.
(;-)TP
Re: Machining time or run time
« Reply #2 on: June 06, 2011, 02:55:17 AM »
Doh! :) Thats good - I knew it had to be there somewhere, but there isnt any reference I could find in the documentation. Thanks.
Re: Machining time or run time
« Reply #3 on: February 24, 2018, 04:49:32 AM »
Hi,

is there a way to get an estimate of the runtime for a file once it is loaded into Mach4?

I cannot find simulate option on Toolpath page in any screen.

Thanks.
Re: Machining time or run time
« Reply #4 on: February 24, 2018, 05:39:30 AM »
Hi,
if there is a way I haven't found it yet.

I think it might be possible to use 'Dry Run', if you select the end of the job as the point to run to....whether it keeps track of cycle time I'm not sure.

I dearsay it could be programmed to do so.

Craig
My wife left with my best friend...
     and I miss him!
Re: Machining time or run time
« Reply #5 on: February 24, 2018, 07:00:46 AM »
I daresay it is a shame that simulation option was removed from M4.
With all information about machine and gcode available, what else is needed to output very precise runtime estimation?!

Thanks Craig.
Re: Machining time or run time
« Reply #6 on: February 24, 2018, 07:12:11 AM »
Hi,
Mach4 is a totally different animal than Mach3.

Additionally Mach3 had problems with runtime simulation when it came to subroutines and probing. While you may think it straightforward I rather doubt it is.

Not sure how I'd go about coding it....

Craig
My wife left with my best friend...
     and I miss him!