Page 1 of 1

getting estimate tool time into the gcode comments

PostPosted: Sat Apr 30, 2011 4:13 am
by John
Hi

Is there a way to put the estimated toolpath time into the comments of the gcode? My interest is for the emc2 one, but I suspect other people might also be interested.

thanks

John

Re: getting estimate tool time into the gcode comments

PostPosted: Mon May 02, 2011 1:15 am
by Randy
Not that I know of, John. There isn't a variable listed in the help section on the postprocessor that has anything to do with the estimated time. I'd suggest emailing Robert at the MeshCAM support email address and asking him to include that.

Randy

Re: getting estimate tool time into the gcode comments

PostPosted: Mon May 02, 2011 3:29 pm
by jeffD
John,

I don't know how to do it either. Do remember that the estimated time is a rather rough number, no acceleration compensation for your machine. You can open the g-code file with a dumb text editor and add a comment line with the reported time. Personally I just figure about an hour per meg of g-code. Not accurate but close enough. :)

jeffD

Re: getting estimate tool time into the gcode comments

PostPosted: Tue Jul 26, 2011 12:15 am
by cnczane
What I just now did was to make pencil marks with times noted aligned with the parallel-finish rows every so often.

"No matter what," those marks will say, "THIS is what MY machine could do with this model."

It will function as a large grain of salt for any time estimates with similar models.
--
David

Re: getting estimate tool time into the gcode comments

PostPosted: Thu Aug 17, 2017 7:04 pm
by cnczane
cnczane wrote:What I just now did was to make pencil marks, with a Real Pencil btw, with times noted aligned with the parallel-finish rows every so often.


But that's lame. I discovered in LinuxCNC, what I use, that one can define one's own "G-code" command, so I created one, M144, called like this:
M144 P<modelnumber.fraction> Q[0|1]
which I then told LxCNC, somehow (I forgot) to execute by calling a simple Linux shell script to get the system time and store it in a log file, named after the model number.

For example:
M144 P303.031 Q0
creates a file M303.031.log (or similar, I forget)
and stores a line like:
START time hh:mm:ss
and M144 P303.031 Q1
appends a line like this to the same file:
STOP time hh:mm:ss

I still have to edit the file and, worse, calculate the elapsed time, but the times are EXACTLY how long between M144 commands.

BTW, the fractional part of the model number ".031" tells me this is the finish pass (1) of the 3rd iteration of model 303. 303.03 is the logfile for roughing times.